[m2e-users] We need documentation on what is supported and not yet suppo

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[m2e-users] We need documentation on what is supported and not yet supported in pom.xml for WAR POM

From: "Sebastien Tardif" <SebTardif@xxxxxx>
Date: Fri, 8 Jul 2011 11:00:37 -0400
Delivered-to: m2e-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/m2e-users>
List-help: <mailto:m2e-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=unsubscribe>
Thread-index: Acw9fyW6Rh1sCONxRuiemBvVDp2kJA==

It’s very hard to find information about what is expected to work with m2Eclipse when importing a WAR pom.xml without any .classpath/.project around.

We could have a complex pom.xml somewhere, with each sections marked with:

· Supported since release x.y.z

· Assigned for release x.y.z, see bug 123

· Bug 234, not yet assigned

I tried to use archetype to give me some info, but archetypes are always so simple, they are a joke.

I looked at some open source Maven book and I didn’t see any mention of this.

Follow-Ups:
- Re: [m2e-users] We need documentation on what is supported and not yet supported in pom.xml for WAR POM
  - From: Matthew Piggott

Prev by Date: [m2e-users] The reasons I feel disappointed with m2e 1.0
Next by Date: Re: [m2e-users] The reasons I feel disappointed with m2e 1.0
Previous by thread: [m2e-users] The reasons I feel disappointed with m2e 1.0
Next by thread: Re: [m2e-users] We need documentation on what is supported and not yet supported in pom.xml for WAR POM
Index(es):
- Date
- Thread

Back to the top