Brett Porter wrote:
On 9/28/05, Mike Perham <[EMAIL PROTECTED]> wrote:
Can dependency scopes solve most of this problem? Maybe the only jars
to appear in the eclipse .classpath should be those in the compile, test
and provided scopes? Or should the eclipse classpath reflect the full
set of libraries required at runtime?
IIRC, you need to include the runtime libraries so that you can run
unit tests and debugger.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi there,
I found this reported as a bug in jira and it says it is already in cvs.
The solution seems to be not adding the jar to eclipse's classpath if an
artifact with the same name is in the reactor already. Is this bug fix
included in the most recent version of the eclipse plugin?
Thanks
Erick.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
