| Re: [nebula-dev] Failing build |
Yep, I was fixing the build as they were failling for quite a few days (since maven.eclipse.org went down actually)
As usual with this kind of things, It took a bit more tries than expected.
I moved the build to the cbi-signing plugin now that the dash plugin is decommissioned and maven.eclipse.org is offline.
As of now the build is using the cbi signing plugins http://git.eclipse.org/c/cbi/org.eclipse.cbi.maven.plugins.git/tree/README
The good news is : with this plugin you don't need to specify some server folder in the build file.
Notable change through :
The plugin has to be enable in the parent pom, not in the update-site poms like the dash plugin.
This led me to move the "build-server" profile in the parent pom. The good news is every jar is now signed and we don't have to specify anything, even if we add another update site. The less good news is that in doing so, when you enable the profile on the maven command line it will automatically disable the other profiles which are in the parent-pom.
You then have to invoke maven with, for instance
mvn package -P build-server,kepler
The nebula.incubation build is still in a broken shape, I'm working on it.
Le 20/09/2013 12:52, Wim Jongman a écrit :
I think Cedric fixed rm -r into rm -rf
The build is back to unstable ;)
On Fri, Sep 20, 2013 at 12:24 PM, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
The failing build is probably my fault. I am reorganizing it a bit.
Cheers,
Wim
_______________________________________________ nebula-dev mailing list nebula-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/nebula-dev
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev