maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenney Westerhof (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-158) Add the ability to selectively treat a referenced project as a local repository file
Date Tue, 10 Oct 2006 07:23:52 GMT
    [ ] 
Kenney Westerhof commented on MECLIPSE-158:

Okay, but there is no generic way to express this. This really only concerns the reactor,
or scope of projects
that the eclipse plugin operates on. Excluding the project on the commandline is IMHO cleaner
than creating yet another
config option in the eclipse plugin to exclude certain projects.

I see your point on me closing it, but
* this is not a bug, at least not in maven, and 
* there's at least 2 ways to solve this problem already, 
** the first being the reactor parameters 
** the second being profiles (put the problematic modules in a profile, that's enabled by
default; when running mvn eclipse:eclipse specify a property that disables that profile, effectively
excluding problematic modules).

Maybe I was too harsh when closing this, but there are just too many ways to do things already,
and providing specific workarounds for all sorts of bugs in 3rd party tools in maven will
only make the plugin configuration (and the plugin itself) more complex. The POM would blow
up in size because of all the 'exclude this because that has such and such a bug, and oh,
that environment, which may not be used at all, has this bug so we have to modify this and
that to do such and such'. At least, that's what I'm afraid of. I use eclipse, but people
that use another flavor IDE probably don't want to see POMs cluttered with this kind of info..

So, I've made my point, and leave this issue open for anyone who wants to fix it.

> Add the ability to selectively treat a referenced project as a local repository file
> ------------------------------------------------------------------------------------
>                 Key: MECLIPSE-158
>                 URL:
>             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:
For more information on JIRA, see:


View raw message