REISSUING: It should be possible to add additional classpath entries in plugin
configuration (MECLIPSE-41)
----------------------------------------------------------------------------------------------------------
Key: MECLIPSE-205
URL: http://jira.codehaus.org/browse/MECLIPSE-205
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Affects Versions: 2.2
Reporter: Amit Kasher
The following scenario demonstrates the issue:
1. Project A is managed by maven and it depends on project B which is not
managed by maven. The dependency is with the logical scope of "compile".
2. Using maven's install:install-file plugin, project B's JAR file is installed
in the repository.
3. Project A is set to depend on this JAR file in its POM (compile scope).
4. Both projects are developed in the same eclipse repository.
The problem is that when classes in project B are changed, the only way to see
these changes when developing project A is to regenerate project B's jar,
install it in maven's repository and refresh project A.
The ideal solution would be to set eclipse's plugin's configuration in project
A's pom to something like this:
......
......
<configuration>
<additionalClasspathEntries>
<kind>src</kind>
<path>/projectB</path>
<replacesDependencies>
<dependency>
<groupId>com.myprojects</groupId>
<artifactId>projectB</artifactId>
<version>1.0</version>
</dependency>
</replacesDependencies>
</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
