[jira] Commented: (MECLIPSE-158) Add the ability to selectively treat a referenced project as a local repository file

["Barrie Treloar (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MECLIPSE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113968 ] 

Barrie Treloar commented on MECLIPSE-158:
-----------------------------------------

I have the same problem with XML beans.

Kenney, would you be able to explain how the second option of using profiles works?

I think I'd like to see these options documented in the FAQ or something so that people who bump into this problem can easily find a solution.

> Add the ability to selectively treat a referenced project as a local repository file
> ------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-158
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-158
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: multiproject
>    Affects Versions: 2.2
>            Reporter: Tim O'Brien
>
> The issue is that I have a large project with many interdependent submodules.   One of the submodules uses XML Beans to generate a set of objects from an XML Schema.   This works perfectly, but Eclipse has a problem with the class names used in XMLBeans, and I have to close that particular project for Eclipse not to complain.  But, if I close that project, all of the projects that depend on it directly (through a referenced project), then complain that they are missing a referenced project.
> The solution is to relate the project via the local repository (M2_REPO/...) not via a project reference, but in EclipseClasspathWriter, all projects available via the reactor are treated as referenced projects:
>         if ( dep.isReferencedProject() && !config.isPde() )
>         {
>             path = "/" + dep.getArtifactId(); //$NON-NLS-1$
>             kind = ATTR_SRC;
>         }
> One solution would be to not use project references, but the problem only happens with specific projects, and I want to be able to selectively mark dependencies as not being referenced.
> Something as simple as, this:
> <config>
>   <localReference>
>      <groupId>blah</groupId>
>      <artifactId>blah</artifactId>
>   </localReference>
> </config>
> Where the dependency identified by that groupId and artifactId would be treated not as a direct project reference but as a link to the local repository.
> Does that make any sense?

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