Done maven3 support branch in hudson has been merged in master : https://github.com/hudson/hudson .
The maven native plugin will now supports maven 3 builds too.
It will be part of the next release 1.392.
Until it's released you will find a build here : http://people.apache.org/~olamy/hudson/main-maven3-support/hudson.war
To test it it's as simple as :
wget http://people.apache.org/~olamy/hudson/main-maven3-support/hudson.war -O hudson.war
So have Fun and nice XMas !!
--
Olivier
French OpenSource addict living @Brisbane, Australia. Apache committer/Member, Jenkins committer and others. Also the father of some :-) (four) beautiful kids and husband of a wonderful wife. Also a Running addict http://home.apache.org/~olamy/ http://twitter.com/olamy https://about.me/olamy A bit old and still no rolex (but a Suunto ;-) ) neither Champion of nothing neither traveling all around the world to talk about himself in conferences. But like helping Open Source users as much he can.
Friday, 24 December 2010
Monday, 20 December 2010
Using gwt sdk 2.1.1 with Gwt Maven Plugin 2.1.0-1
In the last Gwt Maven Plugin, the gwt sdk used is now the one defined in the Maven plugin dependencies.
This means only update your pom dependencies to gwt 2.1.1 won't be enough to compile your project with the last Gwt Sdk version.
To override the Gwt Sdk version used by the Maven plugin, you must add the following configuration :
I'm sure you follow good pratices and have put the version in a property :P
Have Fun !
This means only update your pom dependencies to gwt 2.1.1 won't be enough to compile your project with the last Gwt Sdk version.
To override the Gwt Sdk version used by the Maven plugin, you must add the following configuration :
I'm sure you follow good pratices and have put the version in a property :P
<project>
....
<properties>
<gwt.version>2.1.1</gwt.version>
</properties>
...
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>2.1.0-1</version>
.....
<dependencies>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>${gwt.version}</version>
</dependency>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-dev</artifactId>
<version>${gwt.version}</version>
</dependency>
</dependencies>
.....
</project>
Have Fun !
Wednesday, 15 December 2010
Fast update with groovy to use maven 3.0 in Hudson
As you are an early adopter and want to try the maven3 native support branch in hudson.
See previous blog entry Maven 3 support in Hudson Maven Plugin
If you have a maven installation called maven-3.0, just run the simple groovy script in your console :
prjs = hudson.model.Hudson.getInstance().getItems( hudson.maven.MavenModuleSet.class );
prjs.each{module -> println(module.maven= "maven-3.0")}
And that's it all your maven native plugin hudson jobs will use your maven installation called maven-3.0 .
See previous blog entry Maven 3 support in Hudson Maven Plugin
If you have a maven installation called maven-3.0, just run the simple groovy script in your console :
prjs = hudson.model.Hudson.getInstance().getItems( hudson.maven.MavenModuleSet.class );
prjs.each{module -> println(module.maven= "maven-3.0")}
And that's it all your maven native plugin hudson jobs will use your maven installation called maven-3.0 .
Monday, 13 December 2010
Maven 3 support in Hudson Maven Plugin
You have developped hudson plugins using the maven-plugin or you are an early adopter user : so this blog entry is for you !
Some stuff has been done in a branch called main-maven3-support [1] in github to support maven 3 in the Hudson native maven plugin.
The plugin now supports both maven 2 and maven 3.
Note the pom parsing to detect modules now use the maven 3 apis. (ProjectBuilder maven component [2])
You don't have something to install (just choose the maven version for your maven build) the plugin will detect which maven version is used for the maven build and use differents implementation to "listen" the build.
To test it, you can build it .
First build the embedder (note this will move to github soon)
Then build hudson from the branch
And hudson.war is in war/target/hudson.war
I have pushed builds here : http://olamy.googlecode.com/files/hudson.war
Currently : maven2 build on master node doesn't work (under work !)
We need you for more testing and nice feedback (before merging this to master)
You can follow what's happened in the dedicated jira entry : http://issues.hudson-ci.org/browse/HUDSON-4988
Have Fun !
--
Olivier
[1] https://github.com/hudson/hudson/commits/main-maven3-support
[2] http://maven.apache.org/ref/3.0.1/maven-core/apidocs/org/apache/maven/project/ProjectBuilder.html
Some stuff has been done in a branch called main-maven3-support [1] in github to support maven 3 in the Hudson native maven plugin.
The plugin now supports both maven 2 and maven 3.
Note the pom parsing to detect modules now use the maven 3 apis. (ProjectBuilder maven component [2])
You don't have something to install (just choose the maven version for your maven build) the plugin will detect which maven version is used for the maven build and use differents implementation to "listen" the build.
To test it, you can build it .
First build the embedder (note this will move to github soon)
svn co https://svn.java.net/svn/hudson~svn/trunk/hudson/lib/hudson-maven-embedder
cd hudson-maven-embedder
mvn clean install -DskipTests
Then build hudson from the branch
git clone https://github.com/hudson/hudson.git
git checkout main-maven3-support
mvn clean install -DskipTests
And hudson.war is in war/target/hudson.war
I have pushed builds here : http://olamy.googlecode.com/files/hudson.war
Currently : maven2 build on master node doesn't work (under work !)
We need you for more testing and nice feedback (before merging this to master)
You can follow what's happened in the dedicated jira entry : http://issues.hudson-ci.org/browse/HUDSON-4988
Have Fun !
--
Olivier
[1] https://github.com/hudson/hudson/commits/main-maven3-support
[2] http://maven.apache.org/ref/3.0.1/maven-core/apidocs/org/apache/maven/project/ProjectBuilder.html
Monday, 6 December 2010
Gwt Maven Plugin 2.1.0-1 Released
The Gwt Maven Plugin 2.1.0-1 has been released.
38 issues has been fixed (full changelog).
New features :
* AppEngine Launch
* Css Interface Generator
* More Gwt compiler options : -compileReport, -optimize, -XsoycDetailed, -strict (see the mojo Compile Mojo)
* Compiler Report
* @RemoteServiceRelativePath annotation processing
To use it :
Web Site : http://mojo.codehaus.org/gwt-maven-plugin/
Have Fun !
--
Olivier
38 issues has been fixed (full changelog).
New features :
* AppEngine Launch
* Css Interface Generator
* More Gwt compiler options : -compileReport, -optimize, -XsoycDetailed, -strict (see the mojo Compile Mojo)
* Compiler Report
* @RemoteServiceRelativePath annotation processing
To use it :
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>2.1.0-1</version>
</plugin>
Web Site : http://mojo.codehaus.org/gwt-maven-plugin/
Have Fun !
--
Olivier
Friday, 3 December 2010
Gwt Maven Plugin 2.1.0-1 Staged
Yeah ! The Gwt Maven Plugin 2.1.0-1 has been staged (and release vote started [1] )
Release Notes : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11860&version=16878
Staging repo : https://nexus.codehaus.org/content/repositories/orgcodehausmojo-047/
Documentation site : http://mojo.codehaus.org/gwt-maven-plugin
What's new in this release : http://mojo.codehaus.org/gwt-maven-plugin/whats_new.html
If you have any trouble please load an issue in jira : http://jira.codehaus.org/browse/MGWT .
Have Fun and push a +1 !
[1] http://goo.gl/DeJue
Release Notes : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11860&version=16878
Staging repo : https://nexus.codehaus.org/content/repositories/orgcodehausmojo-047/
Documentation site : http://mojo.codehaus.org/gwt-maven-plugin
What's new in this release : http://mojo.codehaus.org/gwt-maven-plugin/whats_new.html
If you have any trouble please load an issue in jira : http://jira.codehaus.org/browse/MGWT .
Have Fun and push a +1 !
[1] http://goo.gl/DeJue
Subscribe to:
Posts (Atom)