(reposting for all)
No m2e(-tycho) doesn't support pom-less projects, because well, they're
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(a)redhat.com>
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!
> Sample project:
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  indicates we can delete about 433
 `grep -Rl --include "pom.xml" "packaging>eclipse" jbosstools-*
xargs -n 1 grep -lL "module" | xargs -n 1 grep -lL "build" | xargs -n
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
> jbosstools-dev mailing list
jbosstools-dev mailing list