I just configured my netbook to do android development in netbeans. So just sharing my experience here. Before I start below is the details of the hardware and software Hardware: Acer Aspire One Software: OS: Ubuntu Netbook Remix 10.10 Others: Netbeans IDE 7 M2,Android SDK There is a nice plugin for Netbeans available called nbandroid and can be found at http :// kenai . com / projects / nbandroid / . I installed this plugin to my Netbeans IDE from the update center. To do so you can follow the instructions at http :// kenai . com / projects / nbandroid / pages / Install . Once installed next I need to download and install the Android SDK from http :// developer . android . com / sdk / index . html . In my case I have chosen the linux sdk. You can choose the one appropriate to your platform. Once downloaded do exract it to a folder.Next you can follow the steps given in http :// developer . android . com / sdk / installing . html . But you can easily skip all the steps ...
Apache TomEE is a nice small fully certified JavaEE 6 web profile container. In this blog I will show you how to configure netbeans IDE 7.3 beta 2 to work with TomEE Web Profile 1.5. To learn more about TomEE and to download the server you can visit the following link http://tomee.apache.org/apache-tomee.html And you can get the latest version of Netbeans from its site at http://netbeans.org Now first of all I would like to tell you both TomEE works great Netbeans. There are couple of posts which shows about creating things like EJB and CDI beans in TomEE and Netbeans. But what I could not found in the web is a guide to how to make JPA work in TomEE with Netbeans. So I would try to demonstrate the same in this post. So to begin lets just create a Java Web project in Netbeans (I am assuming you have basic working knowladge with netbeans and you know how to create and run a web project in netbeans). In the server screen we can add TomEE like the given screenshot below....
This article describes the process of creating a CI (Continuous Integration) pipeline for PHP projects using Jenkins server. The Architecture The above diagram shows a graphical representation of the whole process. Here we have a git repo, the Jenkins CI server, and its build agent. The Process The process begins when the user checks in the code in the git repo. The git repo via its commit hook calls the build URL of Jenkins server. The Jenkins server pulls the code from the git repo and sends it to build agent. The build agent then executes the ant script and builds and validates the PHP code via various validations mentioned the ant script The successful build can be deployed in a deployment server to complete the CD part of the process. The configuration To configure this solution, we have used a Microsoft Team Foundation Server Online git repo and a Bitnami Jenkins server VM from Azure. I am ass...
Comments