Using the standard JBoss Maven Settings template, I did not have to make
any changes.
S,
ALR
Ales Justin wrote:
Is there anything different in some settings, configuration, ...
(e.g.
settings.xml), which would prevent us to simply copy previous versions
(e.g. I would like to simply copy/override settings.xml in 2.0.9 with
the one I already use)?
Paul Gier wrote:
> The app server build now requires maven 2.0.9. Hopefully this doesn't
> break the build for anyone.
>
> By default the build will use the maven installation in the tools
> directory. If you want to use another version of maven (for example
> 2.0.10-SNAPSHOT) you can override the default one using the maven.dir
> property.
>
> ./build.sh -Dmaven.dir=/path/to/maven-2.0.10-SNAPSHOT
>
> I also added a check so that if maven fails to build the thirdparty
> directory the ant build will immediately fail, instead of failing at a
> later point when ant can't find the files it needs.
>
> Paul Gier wrote:
>> Hi Everyone,
>> Due to some issues with that were found in maven dependency
>> resolution prior to version 2.0.9, I'm going to update the app server
>> build to require maven 2.0.9 or higher.
>>
>> Please upgrade to 2.0.9 if you haven't already.
>>
>> Thanks!
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Andrew Lee Rubinger
Sr. Software Engineer
JBoss EJB3
JBoss, a division of Red Hat, Inc.
http://www.jboss.org/jbossejb3/
http://exitcondition.alrubinger.com