In the words of John McEnroe, you cannot be serious!
Okay, it can be worked around, not by Frank's suggestion about using a
preprocessor, which is, I think, antithetical to Maven's design.
But it's still moderately restrictive.
I don't like it.
-K
On May 17, 2010, at 4:37 PM, Stephen Connolly
MYMVN.bat:
Preprocess.exe < mypom.xml > pom.xml
mvn %1 %2 %3 %4 %5 %6 %7
del pom.xml
Remember what happened when they started making C compilers more restrictive?
The C preprocessor was born.
Actually, these days, the above BAT file would probably run an ant script. :-)
"The harder you squeeze
you have to use the previously release version
On 17 May 2010 22:24, Kathryn Huxtable wrote:
> So how do I use my documentation-producing plugin in its own documentation
> without a variable version number?
>
> See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xmlfor
> an ex
So how do I use my documentation-producing plugin in its own documentation
without a variable version number?
See http://github.com/khuxtable/docbkx-wrapper-plugin/blob/master/pom.xml for
an example. It's in the "site" profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrot
Yes variable version names are not allowed as of Maven 3. I believe the
reason will be deploying into repositories, as pom with version as some
properties instead of a proper version could get deployed.
A quick fix is to configure Eclipse to use external installation of
Maven 2. But remember t
Hi,
At first, thanks for your attention and time to read.
In our enterprise applications we use MyEclipse 8.5 with
M2Eclipse maven3 plug-in support. Before begining to use maven3, with maven2 we
could specify a variable for the application version in the parent pom, so that
in the child
