Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] m2e plugins for code generators?

Bugreport in m2e bugzilla is a good way to start. We generate m2e
marketplace catalog from this descriptor [1], which should give you an
idea of what information we will need. If you have any question, m2e-dev
is probably more appropriate place to ask.


[1] http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.discovery-directory/org.eclipse.m2e.discovery.oss/connectors.xml

--
Regards,
Igor

On 11-05-10 02:56 PM, Joel Rosi-Schwartz wrote:
How would I go about contributing to the marketplace?

On 10 May 2011, at 19:02, Igor Fedorenko wrote:

It provides m2e specific eclipse plugins/features. Unlike regular
Eclipse marketplace, m2e marketplace items are instrumented with
additional metadata that allows m2e match them to Maven projects. So,
for example, when user imports Maven webapp project in Eclipse
workspace, m2e is able to offer installation of m2e-wtp integration as
part of Maven project import wizard flow.

--
Regards,
Igor

On 11-05-10 12:50 PM, Joel Rosi-Schwartz wrote:
Where can I find more information on the M2E Marketplace?

Thanks,
Joel

On 10 May 2011, at 17:41, Igor Fedorenko wrote:

Extending AbstractJavaProjectConfigurator is the recommended way to add
support for code-generating maven plugins.

I believe m2e-wtp got little behind m2e-core API cleanup. You need to
wait until this is sorted out.

Please open new bugzilla bugreport about providing m2e source bundles
and feature.

Also, when you are done with your implementation, we can add it to m2e
marketplace. If you are interested, of course. This way installation of
your Eclipse plugin will be for all projects that use jaxws, jaxb2 and
jibx maven plugins as part of m2e project import flow and via code
assist on "not covered plugin execution" error markers.

--
Regards,
Igor

On 11-05-10 07:21 AM, Kristoffer Peterhaensel wrote:
Hey.

I have been messing a bit around with making a small m2e plugin to
(re-)enable jaxws and jaxb2 and jibx maven plugins.

For my purposes the jibx one is easy to just set to action "execute".
But jaxws and jaxb2 generates source that needs to be in the build
environment.

I've been looking at what is at the m2e extras github repo and
eventually came up with making a simple project configurator that
extends org.eclipse.m2e.jdt.AbstractJavaProjectConfigurator and just
returns the correct source folder when being asked (overwriting
getSourceFolders).

That seems to work just fine for a jar project (or bundle as it happens
to be). But for a WAR project I am getting an exception such as this:
java.lang.NoSuchMethodError:
org.eclipse.m2e.core.MavenPlugin.getMavenProjectManager()Lorg/eclipse/m2e/core/project/MavenProjectManager;

at
org.maven.ide.eclipse.wtp.AbstractProjectConfiguratorDelegate.<init>(AbstractProjectConfiguratorDelegate.java:70)

at
org.maven.ide.eclipse.wtp.WebProjectConfiguratorDelegate.<init>(WebProjectConfiguratorDelegate.java:72)

at
org.maven.ide.eclipse.wtp.ProjectConfiguratorDelegateFactory.getProjectConfiguratorDelegate(ProjectConfiguratorDelegateFactory.java:35)

at
org.maven.ide.eclipse.wtp.WTPProjectConfigurator.mavenProjectChanged(WTPProjectConfigurator.java:74)

at
org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:753)

at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:724)

at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:847)

at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob.run(ProjectRegistryRefreshJob.java:93)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Now the question is if I should be adding generated source folders this
way? Or am I doing something wrong that triggers issues with the wtp
integration?

As a side question I'd ask if perhaps some optional source bundles could
be made available for m2e. So writing these things would be a bit easier
(at least if there happens to be a bit of JavaDoc in the source)? I'd
attact the source manually. But it seems PDE won't allow you to attach
source to plug-in dependencies.

/Kristoffer Peterhänsel
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users


_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users


_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users


Back to the top