maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-40) Multi project dependencies should not require eclipse project names to be the artifactId
Date Sat, 07 Oct 2006 02:30:27 GMT
    [ http://jira.codehaus.org/browse/MECLIPSE-40?page=comments#action_76882 ] 
            
Kenney Westerhof commented on MECLIPSE-40:
------------------------------------------

you should indeed use the artifactId, not the module name.

But if more people want this, we could do one of 2 things:

1) use the module name (meaning the directory name of the pom.xml)
2) add configuration for eclipse plugin that specifies the desired name in the eclipse workspace.
   When creating project references, the dependent pom would be scanned for such a configuration
   (same as checking for source/target in maven-compiler-plugin or use the IdeDependency object)
and use that.

> Multi project dependencies should not require eclipse project names to be the artifactId
> ----------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-40
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-40
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>          Components: multiproject
>    Affects Versions: 2.0
>            Reporter: Dave Sann
>
> Multi project dependencies should not require eclipse project names to be the artifactId
> eg:
> eclipse workspace:
> > Project1 -> creates artifact-x
> > Protect2 -> creates artifact-y, depends on artifact-x
> > MultiBuild - to build a selected collection of checked out projects
> >> pom.xml includes,
> ...
> <modules>
>  <module>../Project1</module>
>  <module>../Project2</module>
> <modules>
> ...
> eclipse:eclipse will create a depencency to a project named artifact-x, where it should
create a dependency to Project1

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

        

Mime
View raw message