[jbosstools-dev] Maven WTP Integration

[Max Rydahl Andersen]

> Sorry, I think you misunderstood me (or I've misunderstood your reply).  There is no problem with the Maven configuration.  It is the configuration for the other facets.  For example, the Java facet defaults to source=src, output=build/classes; the web facet defaults web resources=WebResources.  I was wondering if those could be set more appropriately when the Maven facet is selected in the new faceted project wizard.  It's not a big deal for me, just something I noticed.
> 
>> Also, please note that I'm trying to add a conversion API directly in
>> m2e-core : https://bugs.eclipse.org/bugs/show_bug.cgi?id=359340
> 
> Something like this in reverse is what I was thinking regarding the wizard (i.e. Maven setting the initial settings for Java source/output, web resources, etc.).  I certainly wouldn't put a high priority on it (not sure how many people use the faceted project wizard).  I just notice it when testing the facet stuff.

One of you guys should pickup the work Snjezana did for enabling Maven on projects at creation face - these kind of features would make sense to be part of this.

Snjezana - can you point in the right direction?

Right now I can't even seem to get the library provider stuff to work in 3.3.x?
/max
 
> 
> Thanks again,
> Rob
> 
>> HIH. Regards,
>> 
>> Fred Bricon
>> 
>> Le 07/01/2012 23:17, Rob Cernich a écrit :
>>> Hey all,
>>> 
>>> I just finished adding some basic WTP support for SwitchYard and
>>> had a couple of questions regarding WTP and Maven integration.
>>> The SwitchYard facet can be added to any JEE type (although it is
>>> not currently constrained in this fashion).  If the project is not
>>> already a JEE type project, the Utility Module facet is added.
>>> This effectively allows SY applications to be deployed to any JEE
>>> server.
>>> 
>>> Some of the issues:
>>> Adding the Utility Module facet causes the module nature to be
>>> added, which always creates a META-INF/MANIFEST.MF file within the
>>> project.  Is there a way to disable this behavior for Maven
>>> projects (e.g. where Maven may be generating the manifest)?
>>> 
>>> Maven project configurators run in the order they appear in the
>>> lifecycle processing.  There is a Utility Module configurator that
>>> configures projects containing the Utility Module facet.  However,
>>> this is executed during the compile phase and the SY configurator,
>>> which adds the Utility Module facet, runs during the
>>> process-classes phase.  Because of this, the "deployables" are not
>>> configured correctly on the project (i.e. the test sources and
>>> resources are included).  The current workaround is to run
>>> Maven->Update Project Configuration after the project is created
>>> or imported.  Is there a way to fix this?  (FYI, this is not a
>>> problem if the project is based on another JEE technology, e.g.
>>> WAR, EJB, etc.)
>>> 
>>> When running the new faceted project wizard and including the Maven
>>> facet, it would be nice if the other facets' configurations were
>>> defaulted appropriately (e.g. Java source and output folders, web
>>> resources, etc.).  Is there a way to provide more useful defaults?
>>> 
>>> Sorry for the barrage of questions.
>>> 
>>> Thanks in advance,
>>> Rob
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>> 
>> 
> 
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
> 
> 

/max
http://about.me/maxandersen