[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-2971:
Description:
Variables are not replaced into installed pom file.
Here is a sample pom file
{code:xml}
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
{code}
The installed pom is into
$\{localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is $\{prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
was:
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
{code:xml}
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
{code}
The installed pom is into
$\{localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is $\{prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=347643#comment-347643
]
Jörg Hohwiller commented on MNG-2971:
-
2nd release is out in central repo. Just add this to your build section:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdflatten-maven-plugin/artifactId
version1.0.0-beta-2/version
/plugin
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343842#comment-343842
]
Jörg Hohwiller commented on MNG-2971:
-
Plugin had to be renamed:
http://mojo.codehaus.org/flatten-maven-plugin/
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342545#comment-342545
]
Jörg Hohwiller commented on MNG-2971:
-
There is great news for this issue:
https://svn.codehaus.org/mojo/trunk/sandbox/consumer-maven-plugin
Please note that the plugin will move out of sandbox in the future so try mojo
instead of sandbox if the link stopped working:
https://svn.codehaus.org/mojo/trunk/mojo/consumer-maven-plugin
Simply check-out and install this plugin. Then add this to your toplevel POMs
build-section:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdconsumer-maven-plugin/artifactId
version1.0.0-beta-1-SNAPSHOT/version
/plugin
I hope that the plugin will move out of sandbox and be released soon.
If you have any feedback please let us know (ideally on MOJOs dev mailing list).
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305891#comment-305891
]
Mike Gould commented on MNG-2971:
-
We need this for a multi-module build. We want to specify that some sibling
module dependencies have the same version as the parent or current project. If
we do this:
dependency
groupIdcom.example/groupId
artifactIdcommon/artifactId
version${project.version}/version
scopecompile/scope
/dependency
then the varible appears in the installed pom and then can't be used by
anything.
Currently - like most people - we have a pre-build step which sets all versions
accross the whole tree.
Putting this functionality into the release plugin would be completely useless
as the release plugin simply doesn't do the right thing for CI style builds
where the version is set from the build number/scm revision etc.
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305654#comment-305654
]
Ravi Luthra commented on MNG-2971:
--
I'm recommending an alternative syntax for to-be-replaced variables at
install/deploy time. There are now projects that heavily depend on variables
now because of the glitch.
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305666#comment-305666
]
abhijith nagarajan commented on MNG-2971:
-
Is there any rationale beyond placing the same pom in the repository instead of
effective pom?
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305237#comment-305237
]
Shawn Carrillo commented on MNG-2971:
-
@Christian Bauer - Just wanted to say thanks, just what I needed.
In case others are having the same problems with multi-module projects, I
needed to make one small change for ear/war pom configs.
Under maven-install-plugin configuration, be sure to change file/file to
the proper ear/war locations respectively.
ex:
configuration
filetarget/${project.artifactId}-${project.version}.war/file
pomFiletarget/modified-pom-replacePomPlaceholder/modified-pom/pom.xml/pomFile
/configuration
Please also consider this replay a +1 for substitutions in the parent
configuration.
parent
groupIdcom.example/groupId
artifactIdartifact/artifactId
version${currentVersion}/version
/parent
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305237#comment-305237
]
Shawn Carrillo edited comment on MNG-2971 at 8/1/12 8:32 PM:
-
@Christian Bauer - Just wanted to say thanks, just what I needed.
In case others are having the same problems with multi-module projects, I
needed to make one small change for ear/war pom configs.
Under maven-install-plugin configuration, be sure to change file/file to
the proper ear/war locations respectively.
ex:
configuration
filetarget/${project.artifactId}-${project.version}.war/file
pomFiletarget/modified-pom-replacePomPlaceholder/modified-pom/pom.xml/pomFile
/configuration
Please also consider this reply a +1 for substitutions in the parent
configuration.
parent
groupIdcom.example/groupId
artifactIdartifact/artifactId
version${currentVersion}/version
/parent
was (Author: carrillos):
@Christian Bauer - Just wanted to say thanks, just what I needed.
In case others are having the same problems with multi-module projects, I
needed to make one small change for ear/war pom configs.
Under maven-install-plugin configuration, be sure to change file/file to
the proper ear/war locations respectively.
ex:
configuration
filetarget/${project.artifactId}-${project.version}.war/file
pomFiletarget/modified-pom-replacePomPlaceholder/modified-pom/pom.xml/pomFile
/configuration
Please also consider this replay a +1 for substitutions in the parent
configuration.
parent
groupIdcom.example/groupId
artifactIdartifact/artifactId
version${currentVersion}/version
/parent
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=294132#comment-294132
]
Gustavo Chaves commented on MNG-2971:
-
Hi. I noticed that MNG-4223, which is already related to this issue, seems to
be much more researched. Strictly speaking it is a restricted version of this,
because it cares only about the artifact coordinate tags with regards to
property expansion and not the whole POM. However, since the description of
this issue exemplifies the problem with the version tag I think that probably
the artifact coordinates are all this issue's reporter cares about.
Is that so?
If it is, I think it would be a good idea to close this issue marking it as a
duplicate of MNG-4223 in order to focus the efforts towards a solution.
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=293765#comment-293765
]
Seth Call commented on MNG-2971:
Since this issue is 6 years old, maybe it's useful to give use-cases as to why
one would want to do this.
This thread discusses why myself and others would like to variablize the
version field (summary; to create a scheme where the SCM is the primary source
of version info)
http://maven.40175.n5.nabble.com/Is-it-possible-to-tie-current-git-branch-to-project-version-tc5543110.html
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Atienza updated MNG-2971:
Attachment: pom.xml
my archetype pom
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=290880#comment-290880
]
Julian Atienza edited comment on MNG-2971 at 2/6/12 7:06 AM:
-
That happens to me creating a project from an archetype from my company. Even
having the parameters required in the archeype-metadata.xml and passing them on
mvn archetype:generate, the resulting pom has not the parameters (groupId,
artifactId...) replaced
This is the output from mvn archetype:generate:
Using following parameters for creating project from Archetype:
mygroup-archetype:1.0-SNAPSHOT
[INFO]
[INFO] Parameter: groupId, Value: org.myorg.mygroup.myproject
[INFO] Parameter: artifactId, Value: myproject
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: package, Value: org.myorg.mygroup
[INFO] Parameter: packageInPathFormat, Value: org/myorg/mygroup
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: package, Value: org.myorg.mygroup
[INFO] Parameter: groupId, Value: org.myorg.mygroup.myproject
[INFO] Parameter: artifactId, Value: myproject
this is the generated project's pom file:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupId$org.myorg.mygroup/groupId
artifactId$mygroup-archetype/artifactId
version$1.0-SNAPSHOT/version
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
/project
this is a section of the archetype-metadata.xml for my company's archetype
archetype-descriptor
xmlns=http://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/1.0.0
http://maven.apache.org/xsd/archetype-descriptor-1.0.0.xsd;
name=mygroup-archetype partial=false
requiredProperties
requiredProperty key=artifactId /
requiredProperty key=groupId /
requiredProperty key=package /
/requiredProperties
fileSets
fileSet filtered=true packaged=true
directorysrc/main/java/directory
includes
include**/*.java/include
/includes
/fileSet
fileSet filtered=true packaged=true
directorysrc/test/java//directory
includes
include**/*.java/include
/includes
/fileSet
fileSet filtered=true packaged=true
directory/src/main/generated/directory
includes
include**/*.java/include
/includes
/fileSet
...
/archetype-descriptor
was (Author: julianah):
my archetype pom
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=289789#comment-289789
]
Jorge Agudo Praena commented on MNG-2971:
-
I have this problem in my project. Is there any fix for this issue?
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
