You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Felix Knecht (JIRA)" <ji...@codehaus.org> on 2007/11/26 07:27:57 UTC
[jira] Created: (MECLIPSE-355) Export classpath entries to specific
directory
Export classpath entries to specific directory
----------------------------------------------
Key: MECLIPSE-355
URL: http://jira.codehaus.org/browse/MECLIPSE-355
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: PDE support
Environment: All
Reporter: Felix Knecht
Using pde=true flag to generate .classpath all dependencies not scoped 'provided' are added to the classpath and copied to the projects root directory as well as added in the MANIFEST.MF Bundle-ClassPath.
The plugin should give to possibility to set a path where these dependencies shall be copied to and also add this relative path to the MANIFEST.MF
E.g. in pom.xml
...
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<pde>true</pde>
<dependencyExportPath>lib</dependencyExportPath>
</configuration>
</plugin>
</plugins>
</build>
...
<dependencies>
<dependency>
<groupdId>foo</groupId>
<artifactId>bar</groupId>
<version>1.0</version>
</dependency>
</dependencies>
Should be reflected in a .classpath entry
<classpathentry kind="lib" path="lib/bar-1.0.jar"/>
and in a MANIFEST.MF entry
Bundle-ClassPath: lib/bar-1.0.jar
And the dependencies shall be copied to {project.root}/lib instead of {project.root}.
--
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
[jira] Updated: (MECLIPSE-355) Allow to specify directory for
exported dependencies
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-355:
-------------------------------------
Summary: Allow to specify directory for exported dependencies (was: Export classpath entries to specific directory)
> Allow to specify directory for exported dependencies
> ----------------------------------------------------
>
> Key: MECLIPSE-355
> URL: http://jira.codehaus.org/browse/MECLIPSE-355
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: PDE support
> Environment: All
> Reporter: Felix Knecht
>
> Using pde=true flag to generate .classpath all dependencies not scoped 'provided' are added to the classpath and copied to the projects root directory as well as added in the MANIFEST.MF Bundle-ClassPath.
> The plugin should give to possibility to set a path where these dependencies shall be copied to and also add this relative path to the MANIFEST.MF
> E.g. in pom.xml
> ...
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <pde>true</pde>
> <dependencyExportPath>lib</dependencyExportPath>
> </configuration>
> </plugin>
> </plugins>
> </build>
> ...
> <dependencies>
> <dependency>
> <groupdId>foo</groupId>
> <artifactId>bar</groupId>
> <version>1.0</version>
> </dependency>
> </dependencies>
> Should be reflected in a .classpath entry
> <classpathentry kind="lib" path="lib/bar-1.0.jar"/>
> and in a MANIFEST.MF entry
> Bundle-ClassPath: lib/bar-1.0.jar
> And the dependencies shall be copied to {project.root}/lib instead of {project.root}.
--
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
[jira] Commented: (MECLIPSE-355) Export classpath entries to
specific directory
Posted by "Felix Knecht (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114888 ]
Felix Knecht commented on MECLIPSE-355:
---------------------------------------
Better title would be
Allow to specify directory for exported dependencies
but I submitted too fast and see how I can change the title now.
Sorry, Felix
> Export classpath entries to specific directory
> ----------------------------------------------
>
> Key: MECLIPSE-355
> URL: http://jira.codehaus.org/browse/MECLIPSE-355
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: PDE support
> Environment: All
> Reporter: Felix Knecht
>
> Using pde=true flag to generate .classpath all dependencies not scoped 'provided' are added to the classpath and copied to the projects root directory as well as added in the MANIFEST.MF Bundle-ClassPath.
> The plugin should give to possibility to set a path where these dependencies shall be copied to and also add this relative path to the MANIFEST.MF
> E.g. in pom.xml
> ...
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-eclipse-plugin</artifactId>
> <configuration>
> <pde>true</pde>
> <dependencyExportPath>lib</dependencyExportPath>
> </configuration>
> </plugin>
> </plugins>
> </build>
> ...
> <dependencies>
> <dependency>
> <groupdId>foo</groupId>
> <artifactId>bar</groupId>
> <version>1.0</version>
> </dependency>
> </dependencies>
> Should be reflected in a .classpath entry
> <classpathentry kind="lib" path="lib/bar-1.0.jar"/>
> and in a MANIFEST.MF entry
> Bundle-ClassPath: lib/bar-1.0.jar
> And the dependencies shall be copied to {project.root}/lib instead of {project.root}.
--
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