You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2007/04/19 17:21:46 UTC
[jira] Moved: (MECLIPSE-260) Ignore artifact version mismatches on
creating references to sub-projects
[ http://jira.codehaus.org/browse/MECLIPSE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl moved MPECLIPSE-131 to MECLIPSE-260:
--------------------------------------------------
Workflow: Maven New (was: jira)
Key: MECLIPSE-260 (was: MPECLIPSE-131)
Project: Maven 2.x Eclipse Plugin (was: maven-eclipse-plugin)
> Ignore artifact version mismatches on creating references to sub-projects
> -------------------------------------------------------------------------
>
> Key: MECLIPSE-260
> URL: http://jira.codehaus.org/browse/MECLIPSE-260
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Reporter: Harald Braumann
> Priority: Minor
> Attachments: ignore_version-2.3.patch
>
>
> Currently the maven-eclipse-plugin only creates project references, if the version of the dependency equals exactly the version of the checked out artifact.
> This is inconvenient during development, where I want to keep the inter-project dependencies, even if I change some versions.
> The attached patch adds the parameter ignoreArtifactVersions. If this is set to true, the plugin will create inter-project dependencies, regardless of version mismatches.
> The patch is created against version 2.3 but applies (with warnings) also to current HEAD
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira