Benjamin Lerman wrote:
Hi,
Until this version, I had no problems having the 2 tools compile to 2
different locations, but now the launcher does not get the right class
path.
I am not sure what "this version" is referred to.
this version == 0.9.4
If you have issues with launch configuration in m2eclipse 0.9.4
(though you may need to run "update project configuration" and
recreate or reset classpath in the launch config after that), then
please open a JIRA issue and provide test project that would allow us
to reproduce. See the following wiki page for some hints.
http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues
Well, for example:
When I update my project configuration, m2eclipse add a Excluded: ** to
all resources folder. The reason, if I understand it correctly, is that
resources must not be put in target/classes. Now when I launch my test
or application, they need to have access to META-INF/services/foo.bar
(cf javax.imageio.spi.ServiceRegistry) and that does not work. So I have
to remove the Excluded from the classpath, but now, the target/classes
is incoherent with maven.
If this should be the default behavior, that won't be a problem with
me, *if* I can have an option to allow separate classpath.
First, let me explain how 0.9.4 and previous versions deal with resources.
Resources *source* folders is and has always been a pure "eye candy".
They made resources folders easier to spot in Package Explorer view, but
they always had "Excluded: **" regardless of separate/same output folder.
Before 0.9.4, m2eclipse sometimes added resources folders to classpath
and sometimes tried to copy/filter resources to appropriate output
folder. Unfortunately, this never worked reliably and was actually the
main reasons we decided to get rid of separate output folders (I tried
to explain this in better details here
http://markmail.org/message/733lqtw5moa4cim4).
In 0.9.4, m2eclipse is always uses maven-resource-plugin to copy/filter
resources to maven output folder. This is supposed to happen both on
full eclipse builds and incrementally on resource changes. Actual
resource copy/filter logic did not change in 0.9.4, but we call this
code more often now.
Since this obviously does not work for you, I think it is safe to assume
m2eclipse has a bug in this area ;-) At the same time I really do not
know what might be going on and would like to see a sample project with
steps to reproduce the problem before I can suggest anything.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
