About Maven3 M2Eclipse plug-in versioning problem
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 poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out the version tag or
swapping the expressions between projectVersion and version
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService /description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
Re: About Maven3 M2Eclipse plug-in versioning problem
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 that variable versions will not be supported in
the future releases. I personally use version number derived out of
properties for our Continuous Integration server to generate the tick
part of version (1.0.0.[123]). I haven't personally found a solution yet
using Maven 3.
Thanks,
Kalpak
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 poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: About Maven3 M2Eclipse plug-in versioning problem
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 wrote:
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 that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
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 poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: About Maven3 M2Eclipse plug-in versioning problem
you have to use the previously release version
On 17 May 2010 22:24, Kathryn Huxtable kath...@kathrynhuxtable.org 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 example. It's in the site profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote:
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 that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
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 poms we could able to specify the version by the same
variable.
That helps us saving our time for updating version number in each
project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have
been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc..
However,
the solution never comes up.. Maybe I am doing something wrong, but
could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: About Maven3 M2Eclipse plug-in versioning problem
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 people into a mold, the more violent and sudden will be
the leap to the next plateau of people getting what they want.
!-- Frank Gorham-Engard →
Be kinder than necessary.
Everyone you work here with is fighting some kind of battle.
-Original Message-
From: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org]
Sent: Monday, May 17, 2010 5:24 PM
To: Maven Users List
Subject: Re: About Maven3 M2Eclipse plug-in versioning problem
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 wrote:
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 that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
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 poms we could able to specify the version by the same variable.
That helps us saving our time for updating version number in each project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc.. However,
the solution never comes up.. Maybe I am doing something wrong, but could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: About Maven3 M2Eclipse plug-in versioning problem
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 wrote:
you have to use the previously release version
On 17 May 2010 22:24, Kathryn Huxtable kath...@kathrynhuxtable.org 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 example. It's in the site profile near the bottom.
-K
On May 17, 2010, at 12:48 PM, Kalpak Gadre wrote:
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 that variable versions will not be supported in the future
releases. I personally use version number derived out of properties for our
Continuous Integration server to generate the tick part of version
(1.0.0.[123]). I haven't personally found a solution yet using Maven 3.
Thanks,
Kalpak
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 poms we could able to specify the version by the same
variable.
That helps us saving our time for updating version number in each
project
upgrade and for reusability.
I hope I can clearly demonstrate the problem as the
following piece of code for pom.xml’s.
Now the problem is in maven3 (m2eclipse) it gives a warning
that says “version must be a constant instead of a variable”. I have
been
trying lots of variations such as moving out theversion tag or
swapping the expressions betweenprojectVersion andversion
tags or the other suggestions from the different forum sites, etc..
However,
the solution never comes up.. Maybe I am doing something wrong, but
could not
find out yet.
Any help would be appreciated,
Many thanks in advance,
Bariscan
BTW, you can check the case from here:
PARENT:
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservices/artifactId
namen3gservices Maven
Main/name
packagingpom/packaging
descriptionVersion Alias:
MemberProfitLocalService/description
version${projectVersion}/version
properties
projectVersion2.4/projectVersion
/properties
Child;
project
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
modelVersion4.0.0/modelVersion
groupIdcom.gg.n3gservices/groupId
artifactIdn3gservicesBugfix/artifactId
namen3gservices Bugfix/name
parent
artifactIdn3gservices/artifactId
groupIdcom.gg.n3gservices/groupId
relativePath../n3gservices/pom.xml/relativePath
version${projectVersion}/version
/parent
version${projectVersion}/version
_
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
