[jira] Commented: (MECLIPSE-41) There sould be possible to add additional classpath entry in plugin configuration

["Barry Kaplan (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MECLIPSE-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150922#action_150922 ] 

Barry Kaplan commented on MECLIPSE-41:
--------------------------------------

Brett, is there a concrete example of this? I cannot seem to get this to work. I am trying to add some directories from one project as classpath entries of a second project (see example below). It seems that the eclipse plugin is ignoring these dependencies as I have specified them.

  <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-eclipse-plugin</artifactId>
        <configuration>
          <downloadSources>true</downloadSources>
          <downloadJavadocs>false</downloadJavadocs>
        </configuration>
        <dependencies>
          <dependency>
             <groupId>com.its</groupId>
             <artifactId>deployment-common-conf-properties</artifactId>
             <version>[0.0,)</version>
             <scope>system</scope>
             <systemPath>${basedir}/../deployment/common/conf/properties</systemPath>
         </dependency>
    </plugin>

> There sould be possible to add additional classpath entry in plugin configuration
> ---------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-41
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-41
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>            Reporter: Kaare Nilsen
>            Assignee: Brett Porter
>   Original Estimate: 2 hours
>          Time Spent: 45 minutes
>  Remaining Estimate: 0 minutes
>
> In the case of using a code generation plugin like e.g. XmlBeans. There should be a way of adding the generated artifact as an additional classpath entry in the eclipse project.
> As it is today no projects using xmlbeans will be a valid eclipse project due to some files are just in the generated jar.
> Hopefully this will be fixed in the xmlbeans plugin, but it would anyhow be a nice feature to the eclipseplugins.
> example :
> ...
> <configuration>
>   <additionalClasspathEntries>
>       <entry>target/schemas.jar</entry>
>   </additionalClasspathEntries>
> </configuration>

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