You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2010/11/21 03:01:19 UTC
[jira] Created: (OODT-63) Use hard coded version numbers in shared
component POMs so that MVN install works
Use hard coded version numbers in shared component POMs so that MVN install works
---------------------------------------------------------------------------------
Key: OODT-63
URL: https://issues.apache.org/jira/browse/OODT-63
Project: OODT
Issue Type: Improvement
Affects Versions: 0.1-incubating
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Priority: Critical
Fix For: 0.2-incubating
As it turns out, good ol' Maven doesn't allow POMs with ${variables} for version #s to allow their ${version}s to be resolved dynamically at runtime. In practical terms what this means it that currently the OODT jars can't be published, e.g., to Maven Central, because you get a whole bunch of warnings about not being able to download oodt-core-${oodt.version}.
This can be remedied by not being as slick when it comes to variable management in the POMs, and simply by putting the actual POM version in all dependent POMs within the OODT build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-63) Use hard coded version numbers in
shared component POMs so that MVN install works
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934357#action_12934357 ]
Brian Foster commented on OODT-63:
----------------------------------
- you can't do it with oodt-core . . . all the other projects can use a variable based version number . . . it's a chicken and the egg problem: oodt-core is specifying the version numbers and also wants to use the version numbers.
> Use hard coded version numbers in shared component POMs so that MVN install works
> ---------------------------------------------------------------------------------
>
> Key: OODT-63
> URL: https://issues.apache.org/jira/browse/OODT-63
> Project: OODT
> Issue Type: Improvement
> Components: build proces
> Affects Versions: 0.1-incubating
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Critical
> Fix For: 0.2-incubating
>
>
> As it turns out, good ol' Maven doesn't allow POMs with ${variables} for version #s to allow their ${version}s to be resolved dynamically at runtime. In practical terms what this means it that currently the OODT jars can't be published, e.g., to Maven Central, because you get a whole bunch of warnings about not being able to download oodt-core-${oodt.version}.
> This can be remedied by not being as slick when it comes to variable management in the POMs, and simply by putting the actual POM version in all dependent POMs within the OODT build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-63) Use hard coded version numbers in
shared component POMs so that MVN install works
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934373#action_12934373 ]
Chris A. Mattmann commented on OODT-63:
---------------------------------------
Yep, I'm going to upgrade all the project's pom.xml's to use a specific version #, not a variable one (in this case, 0.2-SNAPSHOT, the next version of OODT). That way, we can use the Maven release plugin (and follow Maven conventions more closely since we're out of the Incubator) but more importantly, we can actually put a dependency on e.g., oodt-commons in a project and not have it complain about ${oodt.version} during version resolution during dependency checking. It's a little more hassle to bump the version #s, but well worth it for its downstream effect.
> Use hard coded version numbers in shared component POMs so that MVN install works
> ---------------------------------------------------------------------------------
>
> Key: OODT-63
> URL: https://issues.apache.org/jira/browse/OODT-63
> Project: OODT
> Issue Type: Improvement
> Components: build proces
> Affects Versions: 0.1-incubating
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Critical
> Fix For: 0.2
>
>
> As it turns out, good ol' Maven doesn't allow POMs with ${variables} for version #s to allow their ${version}s to be resolved dynamically at runtime. In practical terms what this means it that currently the OODT jars can't be published, e.g., to Maven Central, because you get a whole bunch of warnings about not being able to download oodt-core-${oodt.version}.
> This can be remedied by not being as slick when it comes to variable management in the POMs, and simply by putting the actual POM version in all dependent POMs within the OODT build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-63) Use hard coded version numbers in
shared component POMs so that MVN install works
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934222#action_12934222 ]
Chris A. Mattmann commented on OODT-63:
---------------------------------------
Note, this is what I think we're seeing:
http://jira.codehaus.org/browse/MNG-3782
> Use hard coded version numbers in shared component POMs so that MVN install works
> ---------------------------------------------------------------------------------
>
> Key: OODT-63
> URL: https://issues.apache.org/jira/browse/OODT-63
> Project: OODT
> Issue Type: Improvement
> Components: build proces
> Affects Versions: 0.1-incubating
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Critical
> Fix For: 0.2-incubating
>
>
> As it turns out, good ol' Maven doesn't allow POMs with ${variables} for version #s to allow their ${version}s to be resolved dynamically at runtime. In practical terms what this means it that currently the OODT jars can't be published, e.g., to Maven Central, because you get a whole bunch of warnings about not being able to download oodt-core-${oodt.version}.
> This can be remedied by not being as slick when it comes to variable management in the POMs, and simply by putting the actual POM version in all dependent POMs within the OODT build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OODT-63) Use hard coded version numbers in shared
component POMs so that MVN install works
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-63:
----------------------------------
Component/s: build proces
- classify
> Use hard coded version numbers in shared component POMs so that MVN install works
> ---------------------------------------------------------------------------------
>
> Key: OODT-63
> URL: https://issues.apache.org/jira/browse/OODT-63
> Project: OODT
> Issue Type: Improvement
> Components: build proces
> Affects Versions: 0.1-incubating
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Critical
> Fix For: 0.2-incubating
>
>
> As it turns out, good ol' Maven doesn't allow POMs with ${variables} for version #s to allow their ${version}s to be resolved dynamically at runtime. In practical terms what this means it that currently the OODT jars can't be published, e.g., to Maven Central, because you get a whole bunch of warnings about not being able to download oodt-core-${oodt.version}.
> This can be remedied by not being as slick when it comes to variable management in the POMs, and simply by putting the actual POM version in all dependent POMs within the OODT build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.