Hi Richard,
There are several JIRA issues in the JBBUILD project related to the refactoring.
I already closed the issue specifically related to running the full build from
the root directory using maven (JBBUILD-518), so you can change your Hudson jobs
whenever you like.
I changed the configuration of the JBossAS 6 testsuite run yesterday, so you can
look at that one for an example if you like.
The only difference is that instead of calling this:
JBossAS/build/build.sh -Dthirdparty.maven.opts="-Dskip-download-sources -U"
It now uses:
JBossAS/build.sh install -Dskip-download-sources
Richard Opalka wrote:
Hi Paul,
what is the associated JIRA issue? We'd like to monitor it and switch
to different build procedure in our hudson jobs once it's fixed.
Cheers,
Richard
Paul Gier wrote:
> All of the app server modules in trunk are now migrated to maven.
> Today I will be making a couple of updates to the build that will
> allow a full distribution build from a "mvn install" or
"build.sh" in
> the root directory. Starting next week, this will be the preferred
> way to build the app server.
>
> Running "build.sh" from the build directory will still work also, but
> this should be considered deprecated, and it will eventually be
> removed. Next week, I will also start changing the Hudson builds to
> use the new build commands.
>
> The next steps for the app server build will be to do more refactoring
> to remove a ant/maven integration parts that are no longer needed.
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development