Yes, for the cases where I am a commiter of that project.
What if I checkout the project from SVN and need to switch the versions
as simply as possible, but still reliably?
Ondra
David M. Lloyd píše v Po 14. 12. 2009 v 10:42 -0600:
You can use version properties like this:
<properties>
<version.foo.bar.baz>1.2.0.GA</version.foo.bar.baz>
</properties>
Then you can refer to it later (I think in children as well) as
${version.foo.bar.baz}. This gives you a single point where the version
can be set. (Even if I'm wrong about the parent/child thing, since the
version is on the same line as the property name, search/replace can be
more specific.)
- DML
On 12/14/2009 10:42 AM, Ondřej Žižka wrote:
> Hi,
>
> I have a multi-module Maven project, some modules again have modules,
> plus there are some subdirs with "child" artifact.
>
> === What's the best way to change a version of certain artifact in the
> whole tree? ===
>
> This was discussed some time ago on some mailing list, and IIRC, the
> unspoken conclusion was to use something like
>
> perl -pi -e 's/1.1.0.GA-SNAPSHOT/1.1.0.GA-HTMLUnit26/g' `find . -name
> pom.xml`
>
> See
http://community.jboss.org/wiki/DavidsMavenReleaseProcess
>
> But there's a danger of replacing a version for some other artifact. I
> don't want to create some crazy bash script to handle this case. XSLT
> would help.
>
> === But first - is there some Maven plugin or tool to do this? (EXCEPT
> MAVEN RELEASE PLUGIN, see the discussion.) ===
>
>
> Thanks for tips,
> Ondra
>
>
>
> _______________________________________________
> 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