(reposting for all) 

No m2e(-tycho) doesn't support pom-less projects, because well, they're pom-less :-)

m2e lacks native support for polyglot maven (more generally Maven extensions), this is something I need to discuss with Igor and JVZ at some point but, according to igor, it will be very hard to implement.

On Wed, Sep 30, 2015 at 3:52 AM, Max Rydahl Andersen <manderse@redhat.com> wrote:
On 29 Sep 2015, at 20:21, Nick Boldt wrote:

> ... well, NEARLY pomless. Still need a root pom or parent pom.
>
> And might need to refactor your test plugins to end with ".tests" in
> their Bundle-SymbolicName (in MANIFEST.MF).
>
> But hey, less crufty metadata!
>
> Details:
>
> http://wiki.eclipse.org/Tycho/Release_Notes/0.24
>
> Sample project:
>
> http://git.eclipse.org/c/tycho/org.eclipse.tycho.extras.git/tree/tycho-extras-its/src/test/resources/testpomless

Anyone tried if this work without issues in m2e yet ?

How about the mvn plugin for bumping of versions ? Does it change the
manifest.mf when no pom.xml present ?

If that works then a loose count [1] indicates we can delete about 433
files.


[1] `grep -Rl --include "pom.xml" "packaging>eclipse" jbosstools-* |
xargs -n 1 grep -lL "module" | xargs -n 1 grep -lL "build" | xargs -n 1
grep -1L "dependency"`

The above simply try locate all pom.xml, that has custom eclipse
packaging enabled, don't have module listed and do not have custom build
or dependency instructions.

>
>
>
> --
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev