[ 
http://jira.codehaus.org/browse/MECLIPSE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Heritier closed MECLIPSE-32.
-----------------------------------

         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 :
{code}
    <profile>
      <id>apache.snapshots</id>
      <repositories>
        <repository>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots/>
          <id>apache.snapshots</id>
          <name>Maven Snapshots</name>
          <url>http://people.apache.org/maven-snapshot-repository</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <releases>
            <enabled>false</enabled>
          </releases>
          <snapshots/>
          <id>apache.plugin.snapshots</id>
          <name>Maven Plugin Snapshots</name>
          <url>http://people.apache.org/maven-snapshot-repository</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
{code}
Then you have to call this command :
{code}
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse
{code}
If you think that your problem isn't resolved, please give us your feedback and 
we'll reopen the issue.

> Allow for forcing the creation of direct project references for dependencies
> ----------------------------------------------------------------------------
>
>                 Key: MECLIPSE-32
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-32
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: Multi-projects
>    Affects Versions: 2.0
>            Reporter: Barry Kaplan
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
>
>
> For some thirdparty dependencies, it is common (for me at least) that an 
> eclipse project for that dependency does/will exist in the workspace. It 
> would be nice if dependencies in eclipse projects can be forced to use a 
> direct project reference.  eg:
>    <dependency>
>         <groupId>backport-util-concurrent</groupId>
>         <artifactId>backport-util-concurrent</artifactId>
>         <version>2.0_01_pd</version>
>         <scope>runtime</scope>
>         <properties>
>             <property name="eclipse.dependencyType" value="XXXX"/>
>         </properties>
>     </dependency>
> Where XXXX can be: 
>  - 'project' -- always create a project reference
>  -  'jar' -- always create a jar reference as in MNG-955
>  - 'auto' -- the behavior prior to MNG-955

-- 
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

        

Reply via email to