M2Eclipse and the filtered resource nightmare

[Robert Wittams]

We are attempting to use M2Eclipse, and we are finding it very difficult due to the insane behaviour wrt. resources:
 
a) M2Eclipse removes resources from the path of the java builder, so it does not copy them to the output folder. This is apparently to enable filtered resources, a maven feature we don't use.
b) The M2Eclipse provided maven builder very (very!) frequently fails to copy resources. This often needs multiple individual runs of Project->Clean to force this to occur. Project->Cleans of the entire workspace aren't guaranteed to work either.

Q1. Does anybody who uses M2Eclipse actually have resources in their projects that are required at run time?
Q2. If yes to the above, is there any sane procedure that can be followed to get rid of this issue?

I can not see how this is a problem with our maven project, because it works on the cmd line, and also after enough calls to Project->Clean, it will eventually work.

Can a configuration switch be provided to just completely abandon the idea of supporting filtered resources, given that it appears to be a very hard problem, and allow the java builder to behave normally? This doesn't seem to be a rare problem, it is spattered all over your JIRA, with the same inconclusive answers in each place.

I am really just looking for a way to keep using M2Eclipse. Otherwise we will have to go the route of generating eclipse projects and .classpaths, which would be a shame.

[Igor Fedorenko-4]

What you see is most likely MNGECLIPSE-823 [1], which is basically a bad
interaction between JDT and Maven builders. We are still looking for
universal solution, but with 0.9.9 I believe it is possible to configure
m2e to work well for any individual project.

Try configuring custom build lifecycle mapping for your project.
Unfortunately, we only have developer documentation of this feature [2],
but in nutshells, this tells m2e which mojos it should consider. You
can, tell m2e to only consider maven-compiler-plugin and
maven-resource-plugin [3]. Couple of real projects that use this
approach successfully -- Maven core [4] and Nexus [5].

[1] https://issues.sonatype.org/browse/MNGECLIPSE-823
[2]
https://docs.sonatype.org/display/M2ECLIPSE/Customizable+build+lifecycle+mapping+for+m2e+extensions+developers
[3] http://docs.sonatype.org/x/UwEt
[4] http://svn.apache.org/repos/asf/maven/maven-3/trunk/pom.xml
[5] http://svn.sonatype.org/nexus/trunk/nexus-parent/pom.xml

--
Regards,
Igor

Robert Wittams wrote:

> We are attempting to use M2Eclipse, and we are finding it very difficult due
> to the insane behaviour wrt. resources:
>  
> a) M2Eclipse removes resources from the path of the java builder, so it does
> not copy them to the output folder. This is apparently to enable filtered
> resources, a maven feature we don't use.
> b) The M2Eclipse provided maven builder very (very!) frequently fails to
> copy resources. This often needs multiple individual runs of Project->Clean
> to force this to occur. Project->Cleans of the entire workspace aren't
> guaranteed to work either.
>
> Q1. Does anybody who uses M2Eclipse actually have resources in their
> projects that are required at run time?
> Q2. If yes to the above, is there any sane procedure that can be followed to
> get rid of this issue?
>
> I can not see how this is a problem with our maven project, because it works
> on the cmd line, and also after enough calls to Project->Clean, it will
> eventually work.
>
> Can a configuration switch be provided to just completely abandon the idea
> of supporting filtered resources, given that it appears to be a very hard
> problem, and allow the java builder to behave normally? This doesn't seem to
> be a rare problem, it is spattered all over your JIRA, with the same
> inconclusive answers in each place.
>
> I am really just looking for a way to keep using M2Eclipse. Otherwise we
> will have to go the route of generating eclipse projects and .classpaths,
> which would be a shame.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Robert Wittams]

I finally got around to trying this. Number 3 on your list.  

I used the update-dev site to get 0.9.9.  The exact version is 0.9.9.200909092308

It seemed to "work" ( ie only do resources, no other build stages).
However, it is unusable, because now no projects seem to find transitive dependendencies from other projects within the workspace. Eg project A depends on joda time, project B depends on project A, project B can not see joda time.

This is a new issue that was not seen in previous versions.

I downgraded.

[Igor Fedorenko-4]

Will you be able to provide sample project that demonstrates the problem
with transitive dependencies?

--
Regards,
Igor

Robert Wittams wrote:

> I finally got around to trying this. Number 3 on your list.  
>
> I used the update-dev site to get 0.9.9.  The exact version is
> 0.9.9.200909092308
>
> It seemed to "work" ( ie only do resources, no other build stages).
> However, it is unusable, because now no projects seem to find transitive
> dependendencies from other projects within the workspace. Eg project A
> depends on joda time, project B depends on project A, project B can not see
> joda time.
>
> This is a new issue that was not seen in previous versions.
>
> I downgraded.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email