[ http://jira.codehaus.org/browse/MNG-1605?page=comments#action_52123 ]
fabrizio giustina commented on MNG-1605: ---------------------------------------- Hi Barry, would you mind opening a separate issue for the problems you reported and with some more explanations? > When the eclipse project is generated from the leaf project directory, the > output path is created correctly as "target/eclipse-classes". > However, when I generated eclipse projects via the root project using > multi-project, the output path has a drive letter prepended, eg > "R:target/eclipse-classes". I tried reproducing this with a unit test, and I'm going to fix some issues, but I'm not sure if it's the same problem you are seeing with the drive letter... can you post the eclipse plugin configuration in both the parent and module pom.xml + a description of your directory layout? > A correct output path would have the project prepended, eg: > "iris-infra/target/eclipse-classes" why? Shouldn't the output simply be <classpathentry kind="output" path="target/eclipse-classes"/> ? > This caused the following warnings: > [WARNING] This plugin currently doesn't support include patterns for > resources. Adding the entire directory. I wasn't unable to reproduce this problem, the warning should be issued only if you are using include/exclude patters in resource dirs, are you sure this is related to the path with the // prepended? > Allow eclipse source to be specified at the dependency level > ------------------------------------------------------------ > > Key: MNG-1605 > URL: http://jira.codehaus.org/browse/MNG-1605 > Project: Maven 2 > Type: New Feature > Components: maven-eclipse-plugin > Versions: 2.0 > Reporter: Barry Kaplan > Assignee: fabrizio giustina > > > Many (most?) projects do not have sources uploaded. And in any case, most > projects only need a small subset of the sources. Source downloading, even > (especially?) for sources that don't exist, is very time consuming. > Therefore, it would be nice to specify this eclipse plugin specific option as > the dependency level. Maybe something like: > <dependency> > <groupId>backport-util-concurrent</groupId> > <artifactId>backport-util-concurrent</artifactId> > <version>2.0_01_pd</version> > <scope>runtime</scope> > <properties> > <property name="eclipse.downloadSources" value="true"/> > </properties> > </dependency> > (For this to be general, it would of course require a much different model > than the simple plugin-level property injection. ) -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
