Igor Fedorenko <[EMAIL PROTECTED]> wrote on 18/06/2008 00:06:00:
> [EMAIL PROTECTED] wrote:
> > Igor Fedorenko <[EMAIL PROTECTED]> wrote on 16/06/2008 11:43:31:
> >
> >> Maven projects with packaging=war will be automatically configured as
> >> Dynamic Web WTP project during project import or update configuration
> >> action. All relevant project dependencies will be added to WTP J2EE
> >> Module Dependencies (and removed from Maven Dependencies) and J2EE
> >> Module Dependencies and Maven Dependencies will be automatically
updated
> >
> >> as projects dependencies change.
> >>
> >> There is still some bugs/limitations in this area, but this mostly
works
> >
> >> ;-) You may want to try to create/import WAR project in WTP 2.0.x and
> >> see how changes to dependencies in POM get reflected in J2EE Module
> >> Dependencies.
> >
> > Ok, so in essence you are doing the same job as the
maven-eclipse-plugin,
> > in that you read the pom, and generate the .project, .classpath,
.settings
> > folder and any other eclipse related meta data.
> >
> > Is that essentially correct?
>
> Yes, this is correct, except m2eclipse uses public APIs to manipulate
> eclipse metadata and provides real-time synchronization of Eclipse
> metadata where feasible/practical.
I've seen in the console the m2eclipse using the eclipse:m2eclipse mojo,
which uses the same config information.
So, what is the relationship between your plugin and the maven plugin:
maven-eclipse-plugin:m2eclipse?
> > So where do you/can you set the facets for a project?
> >
> > In some instances, this is mandatory meta data that needs to be there
for
> > certain features that I use, to work.
> >
> > The maven-eclipse-plugin covers this via:
> >
> > <build>
> > <plugins>
> > <plugin>
> > <artifactId>maven-eclipse-plugin</artifactId>
> > <configuration>
> >
> > <additionalProjectFacets>
> > <com.ibm.websphere.extended.web>6.1</
> > com.ibm.websphere.extended.web>
> > <com.ibm.websphere.coexistence.web>6.1</
> > com.ibm.websphere.coexistence.web>
> > <web.jstl>1.1</web.jstl>
> > <jsf.base>7.0</jsf.base>
> > <jsf.ibm>7.0</jsf.ibm>
> > </additionalProjectFacets>
> >
> > </configuration>
> > </plugin>
> > </plugins>
> > </build>
> >
> > How can I accomplish this using m2eclipse?
>
> m2eclipse WTP integration does not currently allow configuration of
> arbitrary project facets.
Which kind of severly limits it's usefulness.
> WTP faceted project manipulation APIs take facet id, version and
> optional configuration object, so I suppose it is theoretically possible
> to use maven-eclipse-plugin or similar configuration to create facets
> that do not require explicit configuration object. Unfortunately, I
> can't tell if this will work for Rational project facets.
**********************************************************************
CAUTION - This message is intended for the addressee named above. It may
contain privileged or confidential information.
If you are not the intended recipient of this message you must:
- Not use, copy, distribute or disclose it to anyone other than the addressee;
- Notify the sender via return email; and
- Delete the message (and any related attachments) from your computer
immediately.
Internet emails are not necessarily secure. Australian Associated Motors
Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not
accept responsibility for changes made to this message after it was sent.
Unless otherwise stated, views expressed within this email are the author's own
and do not represent those of AAMI.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
