You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Leonardo Quijano Vincenzi (JIRA)" <ji...@codehaus.org> on 2006/01/26 19:49:06 UTC

[jira] Created: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

Allow artifact resolution from workspace projects
-------------------------------------------------

         Key: MNGECLIPSE-59
         URL: http://jira.codehaus.org/browse/MNGECLIPSE-59
     Project: Maven 2.x Extension for Eclipse
        Type: New Feature

  Components: Dependency Resolver  
    Versions: 0.0.4    
    Reporter: Leonardo Quijano Vincenzi
 Assigned to: Eugene Kuleshov 


Provide artifact resolution from workspace projects, which override the same artifact from the local or remote repositories. This would allow to work with dependant Eclipse projects without specifying the Eclipse dependency manually.

The workspace artifact resolution would have to be specified manually, since several Maven-Enabled projects in the same workspace could have the same artifact and version Id. Or at least automatic resolution with an optional override would be nice.

More comments here:
http://jira.codehaus.org/browse/MNGECLIPSE-58

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

Posted by "Michael Mattox (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_58925 ] 

Michael Mattox commented on MNGECLIPSE-59:
------------------------------------------

We're really stuck on this.  So far the only solution we have is to have two pom.xml, a pom.xml for the maven eclipse plugin and a pom-server.xml.  The difference between the two is the pom.xml doesn't contain dependencies for the projects that are in the eclipse workspace.

Is there a better solution?  



> Allow artifact resolution from workspace projects
> -------------------------------------------------
>
>          Key: MNGECLIPSE-59
>          URL: http://jira.codehaus.org/browse/MNGECLIPSE-59
>      Project: Maven 2.x Extension for Eclipse
>         Type: New Feature

>   Components: Dependency Resolver
>     Versions: 0.0.4
>     Reporter: Leonardo Quijano Vincenzi
>     Assignee: Eugene Kuleshov
>      Fix For: 1.0.0

>
>
> Provide artifact resolution from workspace projects, which override the same artifact from the local or remote repositories. This would allow to work with dependant Eclipse projects without specifying the Eclipse dependency manually.
> The workspace artifact resolution would have to be specified manually, since several Maven-Enabled projects in the same workspace could have the same artifact and version Id. Or at least automatic resolution with an optional override would be nice.
> More comments here:
> http://jira.codehaus.org/browse/MNGECLIPSE-58

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

Posted by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=all ]

Eugene Kuleshov updated MNGECLIPSE-59:
--------------------------------------

    Fix Version: 1.0.0

> Allow artifact resolution from workspace projects
> -------------------------------------------------
>
>          Key: MNGECLIPSE-59
>          URL: http://jira.codehaus.org/browse/MNGECLIPSE-59
>      Project: Maven 2.x Extension for Eclipse
>         Type: New Feature

>   Components: Dependency Resolver
>     Versions: 0.0.4
>     Reporter: Leonardo Quijano Vincenzi
>     Assignee: Eugene Kuleshov
>      Fix For: 1.0.0

>
>
> Provide artifact resolution from workspace projects, which override the same artifact from the local or remote repositories. This would allow to work with dependant Eclipse projects without specifying the Eclipse dependency manually.
> The workspace artifact resolution would have to be specified manually, since several Maven-Enabled projects in the same workspace could have the same artifact and version Id. Or at least automatic resolution with an optional override would be nice.
> More comments here:
> http://jira.codehaus.org/browse/MNGECLIPSE-58

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

Posted by "maartenvisser (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_60335 ] 

maartenvisser commented on MNGECLIPSE-59:
-----------------------------------------

Is there any plan on including the functionality there was in the maven 1 plugin for setting eclipse project property in the pom file in the maven2 release? What I am looking for is the possibility for plugin to override the pom file dependency with eclipse workspace dependency that should be used when available. I It is a really awkard to manage the dependencies in two places.

Something like in the maven 1 release to set the following property in pom file:
<properties>
      <eclipse.dependency>true</eclipse.dependency>
</properties>

> Allow artifact resolution from workspace projects
> -------------------------------------------------
>
>          Key: MNGECLIPSE-59
>          URL: http://jira.codehaus.org/browse/MNGECLIPSE-59
>      Project: Maven 2.x Extension for Eclipse
>         Type: New Feature

>   Components: Dependency Resolver
>     Versions: 0.0.4
>     Reporter: Leonardo Quijano Vincenzi
>     Assignee: Eugene Kuleshov
>      Fix For: 1.0.0

>
>
> Provide artifact resolution from workspace projects, which override the same artifact from the local or remote repositories. This would allow to work with dependant Eclipse projects without specifying the Eclipse dependency manually.
> The workspace artifact resolution would have to be specified manually, since several Maven-Enabled projects in the same workspace could have the same artifact and version Id. Or at least automatic resolution with an optional override would be nice.
> More comments here:
> http://jira.codehaus.org/browse/MNGECLIPSE-58

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org