Posts Tagged 'build'

Apache Maven copy local file to a remote server server using SSH

Details

Category: Apache Maven

Published on Thursday, 12 April 2012 20:20

Written by Administrator

Hits: 1819

I will show you in an Apache Maven configuration file how to copy files to server each time the package phase is executed.

Solution with Ant SCP task

This snippet of code is a ready to use code that make use of Apache Ant task scp, Just put this snippet of code in your Maven module where the assembly is executed or anywhere else to push all tar.gz files to a server just run a maven mvn package, you can add as many ant task and push to many server the same file during the reactor build.

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
    <id>server-copy</id>
    <goals>
        <goal>run</goal>
    </goals>
    <phase>package</phase>
    <configuration>
        <target>
            <echo message="Push to server/home/"/>
            <scp trust="yes"
                todir="user:password@server:/home/">
                <fileset dir="${basedir}/target">
                    <include name="**/*.tar.gz"/>
                </fileset>
            </scp>
        </target>
    </configuration>
</execution>
</executions>
<dependencies>
<dependency>
    <groupId>org.apache.ant</groupId>
    <artifactId>ant-jsch</artifactId>
    <version>1.8.2</version>
</dependency>
</dependencies>
</plugin>

Solution with maven-deploy-plugin

The maven-deploy-plugin allows you to configure the deploy phase to deploy to a server using scp. There is a page in the documentation that describes how it can be done.

Deploy maven artifact using Maven Wagon SCP

Another alternative would be to use Maven Wagon SCP like described in this post for example

Apache Maven 3 Cookbook

Details

Category: Apache Maven

Published on Wednesday, 16 November 2011 21:04

Written by Administrator

Hits: 1888

First a big thanks to Packt Publishing for having sent me this book to review! I did enjoy going through this book, while I did not learn a lot of new stuff (I am using Apache Maven daily since 2006!), I found it to be concise and would recommend it anytime to any of my colleagues. But let’s go through my review of this cookbook of over 50 recipes towards optimal Java Software Engineering with Maven 3:

Apache Maven 3 Cookbook is a clear, precise, well-written book that gives readers clear recipes for the release process using Apache Maven 3. The authors give a step-by-step account of expectations and hurdles for software development.

The first few chapters quickly bring you to the point to be comfortable using Maven on straightforward projects, and the later chapters provide even more recipes examples on subjects like running a Repository Manager, Writing Plugins, and details on various techniques. The book also covers numerous real world software delivery issues such as multi-module projects, web/enterprise projects, dependency management, automatic testing and documentation.

To sum up key points from this 224 pages book in a few bullets:

The author Srirangan go into detail in describing each of these themes. 

I recommend you this book if

if you want to be able to deliver your software to any target environment, using continuous delivery processes, chances are high that Apache Maven is the right tool for this job, and this book should be part of your technical library, beside also of course the free online book of Sonatype Maven: The Complete Reference

Apache Maven 3 Cookbook Review

Details

Category: Apache Maven

Published on Saturday, 01 October 2011 09:08

Written by Administrator

Hits: 2727

Thanks to Packt Publishing for having sent me this book to review. I will publish a review in the next coming days

• Grasp the fundamentals and extend Apache Maven 3 to meet your needs
• Implement engineering practices in your application development process with Apache Maven
• Collaboration techniques for Agile teams with Apache Maven
• Use Apache Maven with Java, Enterprise Frameworks, and various other cutting-edge technologies
• Develop for Google Web Toolkit, Google App Engine, and Android Platforms using Apache Maven

You may also consider reading all my articles related to Apache Maven

Apache Maven Cargo deploy with Tomcat 7

Details

Category: Apache Maven

Published on Friday, 27 May 2011 20:33

Written by Administrator

Hits: 3667

Following the post about Deploy to Tomcat 6 using Maven, here is a ready to use example with the main differences explained in the table below

And finally a snippet of an Apache Maven pom.xml ready to use in a profile, so you can reuse this profile like a method call

<profile>
 <id>deployTomcat</id>
<activation>
  <activeByDefault>false</activeByDefault>
</activation>
<build>
 <plugins>
    <plugin>
     <groupId>org.codehaus.cargo</groupId>
     <artifactId>cargo-maven2-plugin</artifactId>
     <version>1.1.0</version>
    <configuration>
     <wait>true</wait>
     <container>
      <containerId>tomcat7x</containerId>
      <type>remote</type>
     </container>
     <configuration>
      <type>runtime</type>
      <properties>
       <cargo.remote.uri>
         ${tomcat.url}
       </cargo.remote.uri>
       <cargo.remote.username>
          ${tomcat.user}     
       </cargo.remote.username>
        <cargo.remote.password>
          ${tomcat.pwd}
        </cargo.remote.password>
      </properties>
      </configuration>
      <deployer>
       <type>remote</type>
       <deployables>
       <deployable>
        <groupId>${deploy.groupid}</groupId>
        <artifactId>${deploy.artifactid}</artifactId>
        <type>war</type>
        <properties>
         <context>${deploy.context}</context>
        </properties>
       </deployable>
      </deployables>
     </deployer>
    </configuration>
    <executions>
     <execution>
      <id>verify-deploy</id>
      <phase>pre-integration-test</phase>
      <goals>
       <goal>deployer-undeploy</goal>
       <goal>deployer-deploy</goal>
      </goals>
     </execution>
    </executions>
    </plugin>
 </plugins>
</build>
</profile>

Place as many profiles as you have machine to deploy in settings.xml and declare some variables as properties, as shown below:

<profile>
 <id>serverA</id>
 <activation>
    <activeByDefault>false</activeByDefault>
 </activation>
 <properties>
    <tomcat.url>http://host.com/manager/text</tomcat.url>
    <tomcat.user>admin</tomcat.user>
    <tomcat.pwd>admin</tomcat.pwd>
    <!-- these properties must be defined
       as system property or -D -->
    <!-- - deployable.artifactid:
         artifactId of web application to be deployed -->
    <!-- - deployable.context: web context name -->
 </properties>
</profile>

So you can run, and traget multiple host by just exchanging the name of the profile serverA to something else.

mvn integration-test –PdeployTomcat,serverA
   –Ddeployable.artifactid=demo
   -Ddeploy.groupid=com.mycompany
   –Ddeployable.context=showcase

Speeding up Apache Maven Builds

Details

Category: Apache Maven

Published on Thursday, 23 September 2010 19:59

Written by Administrator

Hits: 7247

The obvious things to do first in no particular order

• Use a better build server, CPU power is cheap today,
• Throw more memory, as Maven run in a JVM the more you have the better it may behave, you may want also to increased the perm gen space,
• Use the latest  version of JVM!
• Switch as many plugins as possible as long as there are not needed in the main build loop: Use profile to modularize your build and trigger some additional build/reporting plugins when needed. You want your build to be fast to provide fast feedback to your developers.
• Optimize your test cases, some may take longer than other, use @BeforeClass or Lazy initialization to cache some heavy to create objects,
• Tune the garbage collector according to your build behavior, number of CPU core:  use parallel garbage collector for example,
• Carefully review your dependencies as the less Apache Maven has to load while building the faster it will get.
  • Are they all needed?
  • No duplicates dependencies?
  • Do you miss some <exclusions>? are all these transitive dependencies to your 3rd party needed?
  • No dependencies cycles? check the order in reactor. A developer should understand, and not be surprised by  the order of the modules calculated by Maven (as long as you have layers in your software, you expect some modules to be build before some others) .
• Review ALL logs files
  • The one created by Maven to avoid any warnings and
  • All your application logs (do you log too much data during the build?)

Read more: Speeding up Apache Maven Builds

Technology management using artifact life cycles

Details

Category: Apache Maven

Published on Saturday, 28 August 2010 16:23

Written by Administrator

Hits: 4891

I forgot to blog about this presentation at JAZOON 2008, but I did never forget the added value of this plugin. It is not currently in Apache Maven  core but will for sure find its way as an official plugin one day, since it solve elegantly a common problem: technology management

Maven does not know the concept of an artifact life cycle. Such life cycle status information would allow to extend the dependency management in a new dimension. One could declare whether certain dependencies are actually allowed/forbidden/restricted to be used in a project, enabling effective technology management.

Currently a plugin is available to achieve this goal:The AssertDepend plugin. It work by adding metadata, additional xml files in artifact group directory.

The AssertDepend plugin is a Maven extension to perform effective technology management. The plugin checks at build time against lifecycle states defined in metadata on remote repositories in order to inform the developer about inappropriate technology usage (dependency enforcement). Based on a flag the build would either fail or print a warning.

Technology management benefits and means

The capability to manage dependencies and technologies on a mature level is essential for software organizations of a certain size. Technology management becomes a key discipline and must be introduced in a careful way to allow for mutual benefits among its stakeholder including developer, management, and customers.

Artifact lifecycle management

To perform effective technology management, you should keep the number of approved artifacts as small as possible. You cannot remove artifacts from the repository if you want to sustain reproducible builds. Therefore, each artifact in the repository should be marked with a corresponding lifecycle state.

The proposed main states are (but the plugin is not limited, you can create your own)

• approved
• prohibited
• investigating

With these states, it solve elegantly the following use cases.

Scenario 1: Flawed versions
It turns out that my-app-1.4.2.jar contains a serious security issue and is therefore flawed. Clients of this JAR should actually switch to a newer version my-app-1.4.3.jar which fixes the bug and which is safe to use.

Scenario 2: Decommissioning
Let's assume that my-app-1.4.2.jar is not supported anymore and projects should actually switch to a new release stream
(my-app-2.x.y.jar).

Scenario 3: Restricted usage
Consider a library which has a restricted set of client projects, e.g. only certain projects are allowed to depend on a specific artifact.

Usage

Artifact lifecycle metadata must be placed in a file named maven-artifact-lifecycle.xml in the corresponding group directory. For instance, if you want to define lifecycle information for struts, the corresponding metadata file is located here: struts/struts/maven-artifact-lifecycle.xml

This plugin can be downloaded at http://madp.sourceforge.net/index.html

Keep your software stack up to date with the Apache Maven Versions Plugin

Details

Category: Apache Maven

Published on Saturday, 28 August 2010 13:57

Written by Administrator

Hits: 5428

It is not unusual in a project to have a huge number of third party artifacts and Plug-in. Apache Maven help you keep track of them, along with their transitive dependencies.

But how do you know when a new version of an artifact is available?  This is where the Maven Versions plug-in come hand in.

The Versions Plug-in is used when you want to manage the versions of artifacts in a project's POM.

By running

mvn versions:display-dependency-updates

in any Apache Maven project or modules, you’ll get for example (we have a lot of 25 Maven modules, here is only one presented as an example, the list being too long)

[INFO] --------------------------------------------------------------------------------------------------
[INFO] Building Unnamed - com.innoveo:skye-services-api:jar:2.2.0-M-06
[INFO] --------------------------------------------------------------------------------------------------
[INFO]
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO]   junit:junit ............................................. 4.4 -> 4.8.1
[INFO]   log4j:log4j ......................................... 1.2.15 -> 1.2.16
[INFO]   org.springframework:spring ...................... 2.5.6 -> 2.5.6.SEC02
[INFO]   org.springframework:spring-test ............... 2.5.6 -> 3.0.4.RELEASE

Read more: Keep your software stack up to date with the Apache Maven Versions Plugin

Apache Maven profiles order in multi modules projects

Details

Category: Apache Maven

Published on Saturday, 07 August 2010 17:27

Written by Administrator

Hits: 9784

In which order are Apache Maven profiles executed? are Apache Maven profiles ordered? how can you insured that Apache Maven profiles are activated in the right order?

You normally don’t end up with these questions, issues may only appear if

• Some profiles are dependent each other,
• Some profiles can not run in any order,

The use case behind this article is very simple, as I have a a continuous build were:

• 5 web applications have  to be deployed into a remote tomcat in phase pre-integration-test,
• 2 databases are created for test cases in phase generate-test-resources
• 1 more database is created and needed for runtime, done in phase pre-integration-test
• One of these web applications is able to inject data into database using web services, a profile do this in a profile in phase pre-integration-test
• Selenium test cases are run in phase integration-test

All these steps are done using several Apache Maven pom profiles.

As it is a bit complicated to explain, lets first refresh some Apache Maven concepts

Read more: Apache Maven profiles order in multi modules projects

Auto deployment of Maven artifacts to Oracle Weblogic

Details

Category: Apache Maven

Published on Sunday, 04 July 2010 15:43

Written by Administrator

Hits: 11214

I found  this time a  new way to deploy Maven artefacts using the Oracle Weblogic Ant API!

If you remember my previous post, there is many ways to deploy your war/ear to Oracle Weblogic

1. Using Oracle Weblogic development mode, a mode in which a simple copy of your files in a specific autodeploy directory trigger the update/install of these
2. Using Maven Cargo, this work only if your Oracle Weblogic container is local (see here) on the same machine, where Apache Maven is running
3. Using a very old Maven plugin (2008), local and remote container are supported, but our builds were sometimes hanging during pre integration phase for no apparent reasons.

And now using the official ANT API of Oracle, by far the MOST stable of all!

Read more: Auto deployment of Maven artifacts to Oracle Weblogic

Maven project filtering

Details

Category: Apache Maven

Published on Saturday, 05 September 2009 00:00

Written by Administrator

Hits: 15280

Depending on your project requirements/number of customers, you may have to support different target environment. This article will help you to make your Maven build a bit more portable in that sense. Maven can help you avoiding having stage dependent data across all your Maven projects/ modules very easily thanks to resources filtering.

Let’s imagine you want to build your software against many different runtime stack:

• One is against your developer environment: eclipse, Tomcat, Mysql
• One is running in a server with Tomcat, Mysql.
• One is running in JBOSS 

And that your software is somehow configurable, can be through properties files, xml files, environment variables. Some of your configurations files are containing data that are depending on runtime (paths, password, login, connection settings to database, profiling/tuning settings)

Read more: Maven project filtering