|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Anders Hammar (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)
- [mojo-dev] [jira] (MOJO-1851) Use version property f... Tony Chemit (JIRA)

@Tony: These warnings come from Maven core. Maven core can't know how the m-site-p do version resolution. But these warnings will confuse devs so we can't have them I think.
What I think we should do is revert the old configuration with version number declared twice. IMHO it's not the end of the world.