maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Heritier (JIRA)" <>
Subject [jira] Closed: (MECLIPSE-260) Ignore artifact version mismatches on creating references to sub-projects
Date Thu, 31 Jan 2008 14:08:00 GMT


Arnaud Heritier closed MECLIPSE-260.

         Assignee: Arnaud Heritier
       Resolution: Duplicate
    Fix Version/s: 2.5

This issue is considered as fixed with MECLIPSE-344.
To try the latest SNAPSHOT (2.5-20080131.135640-18) of the incoming version you have to define
and activate this profile :
          <name>Maven Snapshots</name>
          <name>Maven Plugin Snapshots</name>
Then you have to call this command :
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
If you think that your problem isn't resolved, please give us your feedback and we'll reopen
the issue.

> Ignore artifact version mismatches on creating references to sub-projects
> -------------------------------------------------------------------------
>                 Key: MECLIPSE-260
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: Dependencies resolution and build path
>            Reporter: Harald Braumann
>            Assignee: Arnaud Heritier
>            Priority: Minor
>             Fix For: 2.5
>         Attachments: ignore_version-2.3.patch, 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message