You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Benson Margulies (JIRA)" <ji...@apache.org> on 2010/10/18 00:21:22 UTC
[jira] Assigned: (CXF-3051) Rename all POM properties that change
dependency versions
[ https://issues.apache.org/jira/browse/CXF-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benson Margulies reassigned CXF-3051:
-------------------------------------
Assignee: Benson Margulies
> Rename all POM properties that change dependency versions
> ---------------------------------------------------------
>
> Key: CXF-3051
> URL: https://issues.apache.org/jira/browse/CXF-3051
> Project: CXF
> Issue Type: Bug
> Components: Build system
> Affects Versions: 2.2.10, 2.3.0
> Reporter: Benson Margulies
> Assignee: Benson Margulies
>
> The maven gang discourages:
> <version>${blah}</version>
> One reason is that maven does *not* resolve these references before publishing a pom in the release process. Our released poms contain property definitions and dependencies that use them.
> If, for example, a user innocently create a setting for jetty.version that is, oh, for jetty version 8, maven will forget, entirely that we carefully declared a dependency on version 7.
> The fix we can live with is to make all of these properties have names of the form cxf-*, so that other people won't accidently set them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.