5:52 p.m.
I thought I might just have to change the jboss-as/pom.xml version to
affect the overall build version, but it seems I need to update all 108
pom.xml/*<version>7.0.0.Beta4-SNAPSHOT</version> references in order for
the build to work. Is that correct?
6:05 p.m.
Yeah that's a really annoying maven problem.
I do:
for i in `find . -name pom.xml | xargs`; do sed 's/oldver/newver/g' $i >
$i.new; mv $i.new $i; done
On 5/25/11 5:52 PM, Scott Stark wrote:
I thought I might just have to change the jboss-as/pom.xml version
to
affect the overall build version, but it seems I need to update all 108
pom.xml/*<version>7.0.0.Beta4-SNAPSHOT</version> references in order for
the build to work. Is that correct?
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss, a division of Red Hat
12:55 a.m.
With maven 3, can you not remove the version declaration in the child module
pom.xml and it will inherit the version from the parent (if that's the
desired behaviour)?
Regards
Rich
On 26 May 2011 00:05, Jason T. Greene <jason.greene(a)redhat.com> wrote:
Yeah that's a really annoying maven problem.
I do:
for i in `find . -name pom.xml | xargs`; do sed 's/oldver/newver/g' $i >
$i.new; mv $i.new $i; done
On 5/25/11 5:52 PM, Scott Stark wrote:
> I thought I might just have to change the jboss-as/pom.xml version to
> affect the overall build version, but it seems I need to update all 108
> pom.xml/*<version>7.0.0.Beta4-SNAPSHOT</version> references in order
for
> the build to work. Is that correct?
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
8:54 a.m.
I do
find . -name pom.xml | xargs sed -i "s/old/new/"
On 05/26/2011 01:05 AM, Jason T. Greene wrote:
Yeah that's a really annoying maven problem.
I do:
for i in `find . -name pom.xml | xargs`; do sed 's/oldver/newver/g' $i>
$i.new; mv $i.new $i; done
On 5/25/11 5:52 PM, Scott Stark wrote:
> I thought I might just have to change the jboss-as/pom.xml version to
> affect the overall build version, but it seems I need to update all 108
> pom.xml/*<version>7.0.0.Beta4-SNAPSHOT</version> references in order
for
> the build to work. Is that correct?
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
4:23 a.m.
If the project is well-formed the versions plugin does all this gymnastics for you.
http://mojo.codehaus.org/versions-maven-plugin/
/max
On May 26, 2011, at 24:52, Scott Stark wrote:
I thought I might just have to change the jboss-as/pom.xml version to
affect the overall build version, but it seems I need to update all 108
pom.xml/*<version>7.0.0.Beta4-SNAPSHOT</version> references in order for
the build to work. Is that correct?
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
5016
days inactive
5017
days old
4 comments
5 participants
participants (5)
-
Jason T. Greene -
Max Rydahl Andersen -
Rich Midwinter -
Scott Stark -
Thomas Diesler