Status: New
Owner: ----
Labels: Package-EclipSLEE
New issue 37 by [email protected]: Eclipse classpath not updated
after editing pom.xml
http://code.google.com/p/jain-slee/issues/detail?id=37
What steps will reproduce the problem?
1. Create an EclipSLEE project.
2. Add an external library as dependency to a module's pom.xml
3. Add a reference to a class from the external library in a source file
within the module.
What is the expected output? What do you see instead?
Expected - Eclipse classpath updated automatically, no errors shown.
Actual - classpath not updated, Eclipse shows an error (cannot resolve the
class), even though maven build is successful.
What version of the product are you using? On what operating system?
EclipSLEE 2.0.0.v20121003-1449
m2e 1.2.0.20120903-1050 (embedded maven 3.0.4)
Eclipse 4.2.1
Debian GNU/Linux 6.0.6
Please provide any additional information below.
A workaround is to add an additional dependency using the context menu,
which updates the .classpath to include the library that has been added by
directly editing pom.xml. The redundant dependency can then be removed, the
dependency that has been manually included into pom.xml remains
in .classpath. This forces doing unnecessary manual actions and regenerates
pom.xml potentially introducing false differences with VCS (indentation,
line wrapping).
Automatic .classpath updating after editing a pom.xml works fine for
standard maven projects (non-EclipSLEE) using the aforementioned versions
of Eclipse and m2e.
ML thread:
https://groups.google.com/forum/?fromgroups#!topic/mobicents-public/s315O1b2Ubg
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
