Community
Participate
Working Groups
Name: turmeric-maven-plugin Description: Provides codegeneration services for the Turmeric SOA framework. Summary: Provides codegeneration services for the Turmeric SOA framework. Handles the generation of Services and Interfaces for type libraries, error libraries, consumers, and web services. License: Apache Public License 2.0 Provider: ebayopensource.org Steps and Examples: There are numerous examples within the turmeric soa project itself. In particular the integration tests for the runtime project. https://github.com/ebayopensource/turmeric-runtime/tree/master/integration-tests Source Repository: https://github.com/ebayopensource/turmeric-runtime Name: jaxb-episode-maven-plugin Description: used to generate jaxb bindings. Summary: the jaxb-episode-maven-plugin is used by the turmeric soa project during a build to generate JAXB binding information. It is primarly used by the runtime framework during compilation. It is mainly for internal development of the turmeric project. License: Apache Public License 2.0 Provider: ebayopensource.org Steps and Examples: It can be seen in use in the turmeric soa runtime build. Source Repository: https://github.com/ebayopensource/turmeric-releng While I have this request open, is there an extension point I can contribute additional discoveries too? While the discovery mechanism is helpful, it would be nice to be able to contribute a plugin contribution via an extension point.
I found the extension points but running into some problems trying to test them out. It seems that even if I add a confguration element to the lifecycleMappingMetaData it always expects this to be out in the Discovery marketplace. However, I'd prefer that it check to see if a plugin configuration is installed, and then if it isn't, go to the marketplace to find it. Am I doing something wrong? The particular commit and configuration can be viewed here: https://github.com/kingargyle/turmeric-eclipse/commit/2d70bdd30038fa613d4a547708fa67fa2157307d
What is p2 repository and installable unit id (or ids) of these extensions? I am not sure I understand your question about lifecycle mapping configuration. What are you trying to achieve? (m2e-dev is probably more appropriate for this kind of questions)
(In reply to comment #2) > What is p2 repository and installable unit id (or ids) of these extensions? > > I am not sure I understand your question about lifecycle mapping configuration. > What are you trying to achieve? (m2e-dev is probably more appropriate for this > kind of questions) I've sent a message on the wtp-dev. Right now there is no public version that works with 1.0.0. When I install our plugins into eclipse, I'd like the configurator to be picked up through the extension point, unfortunately the Discovery method only seems to want to pick it up if it's out in the m2e if you set a configurator. It may be several months before I have an official version ready for general download, so during this time I need a way to test and develop the plugin without having to have the discovery method involved for the m2e marketplace.
that should be m2e-dev not wtp-dev....sigh
m2e discovery catalog is a convenience meant to help users find m2e extensions. You don't need to publish Turmeric SOA Plugins to the catalog to be able to test them. p2 update site or downloadable archive are more appropriate to deliver test versions of the code.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
