[
https://issues.apache.org/jira/browse/MECLIPSE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-355.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Allow to specify directory for exported dependencies
> ----------------------------------------------------
>
> Key: MECLIPSE-355
> URL: https://issues.apache.org/jira/browse/MECLIPSE-355
> Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)
