I'm prototyping some basic tooling for SwitchYard and have pieced together a crude faceted project preset to allow SwitchYard projects to be deployed to AS using the existing WTP support. The facets I'm using are: * Java * Utility Module

* JBoss Maven Integration My questions: Is the JBoss Maven facet required? What purpose does it serve? (Currently, SwtichYard projects are Maven projects, utilizing m2eclipse.)

On 23/09/2011 11:50, Max Rydahl Andersen wrote: >> I'm prototyping some basic tooling for SwitchYard and have pieced >> together a crude faceted project preset to allow SwitchYard projects >> to be deployed to AS using the existing WTP support. The facets I'm >> using are: >> * Java >> * Utility Module > Sounds about right yes. > > For the case of importing existing maven projects and have these > things enabled Fred Bricon should be able to tell you what the > m2e/wtp plugin needs to identify them. Indeed, to be deployed by WTP as a simple jar (in a war or ear), most projects need the Utility facet (and the Java one). However, if your projects need a special treatment for packaging (ex. sar projects can embed other libs) or need to be deployed standalone (not in ear nor war) Then one should : - create a dedicated facet - modify the server adapters to allow standalone deployment of these new modules (that's what Rob did for the new SAR support) Of course creating a dedicated facet can also be useful just in terms of tooling support (if you plan to create project wizards, eclipse builders ...) Anyway, as long as you use plain old jar

>> * JBoss Maven Integration >> >> My questions: Is the JBoss Maven facet required? What purpose does >> it serve? (Currently, SwtichYard projects are Maven projects, >> utilizing m2eclipse.) > JBoss Maven Integration is a feature we have had for a while but not > really used much since JBoss AS& EAP artifacts wasn't readily > available in maven repos. > > The intent of the jboss maven integration is to allow you to create > faceted projects and then use Maven as the Library provider. There > are code in jboss tools which > will look at the given facet and then add a list of dependencies into > the pom. This is actually something that should be in m2eclipse but > the m2e team prefer everything > is done maven first. > > Snjezana should be able to point you to this. This is one of the > areas where we might need to change things so it accommodate how > switchyard needs/wants things. > > /max > http://about.me/maxandersen > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

>> Then one should : >> - create a dedicated facet >> - modify the server adapters to allow standalone deployment of >> these >> new modules (that's what Rob did for the new SAR support) >> >> Of course creating a dedicated facet can also be useful just in >> terms >> of tooling support (if you plan to create project wizards, eclipse >> builders …)

>> >> Anyway, as long as you use plain old jar > ... using the Utility facet should be enough. Yes, I hope SwitchYard can just survive with that since it also means it gets possible to bundle it in a war, ear etc. "for free"

If you want to create a Maven project using a WTP project wizard (dynamic web project, ejb project, ear project, utility project ...), you have to add the JBoss Maven integration facet that will add the Maven builder/nature to the project. It will create pom.xml and the corresponding maven plugin (war, ejb, ear) and enable you to add Maven dependencies using Maven Library Provider (https://issues.jboss.org/browse/JBIDE-4565). The JBoss Maven Integration facet is also obliged if you want to use some of the JBoss Maven configurators (JSF, CDI, Seam 2, Portlet, Hibernate ...).

> Thanks Fred. I'll incorporate that into the SwitchYard > configurator once I create a true SwitchYard facet and runtime > component. I've got a much better idea of how all these pieces > fit together now. Another important thing is that Facet's are the best way of making something in eclipse that play well with rest of the JEE/Faceted dependent features, but Facet's should *not* be used (at least not by default) as a marker to detect if some feature should be enabled or not (since it prevents users with existing projects to get started) For that natures are much better since they are a core part of eclipse and will work on projects no matter if you have maven or facet on your project. i.e. Eclipse Dali's project for supporting JPA (java persistence) have for a long time required that the Dali Facet have to be installed on a project before their persistence.xml editor becomes useful (i.e. not just showing the source page). Their structured xml editor is deeply dependent on dali specific project generated data, even though 90% of the features they provide in the editor does not need it. Very annoying. Another example is if our VPE editor would only open html files if in a web project. Both cases would severely make it hard to get even the basic features in the IDE to work unless you have the perfectly configured project - which is hard for users trying to use their existing projects. Thus for example in case of Eclipse Dali - they should not check for Dali facet, they should just look if the needed metadata is available and if not just stub out those *few* features in their editor which is dependent on it. Similar for VPE we check if certain natures/builders and metadata is available and inform users about it so they can know the experience can be better - but otherwise we get out of their way and provide as many features we can without the collected metadata. Thus its important to realize Facet's are used to configure eclipse natures/builders/project content - much like m2e's project configurators are - except Facet's are maven independent. All your editors, wizards, etc. should be checking for natures/builders to know what can be enabled or not and try and be flexible to the user so he doesn't have to setup the perfect project to get started using the tools - in switchyard case, the editors and wizards should be able to work fine without any switchyard stuff enabled on the project IMO; at least for the basic artifact creation. /max