| Re: [m2e-dev] JavaProjectConfigurator |
Hi, There is support for secondary (yours) configurator that will be call after their primary (java one) configurator. "Imagination is more important than knowledge.": Albert Einstein Le 10 août 2011 à 14:15, Ricardo Gladwell <ricardo.gladwell@xxxxxxxxx> a écrit : > Hey Guys > > Sorry to *bump* but can anyone help with this? Please let me know if I'm not being clear. > > TIA... > > -- > Ricardo Gladwell <ricardo.gladwell@xxxxxxxxx> > http://www.google.com/profiles/ricardo.gladwell > Twitter: @rgladwell - MSN: axonrg@xxxxxxxxx > > On 09/08/11 13:16, Ricardo Gladwell wrote: >> Hi Guys >> >> My project configurator[1] inherits from the internal >> JavaProjectConfigurator class. >> >> Obviously inheriting or using internal classes isn't desirable. However, >> my project configurator does need to configure a project as though it >> were a Java project, and then decorate that behaviour. >> >> Is there some other approach I should be using to leverage the default >> Java project configuration code? Should JavaProjectConfigurator be moved >> to an external OSGi package? >> >> [1] >> https://raw.github.com/rgladwell/m2e-android/master/me.gladwell.eclipse.m2e.android/src/main/java/me/gladwell/eclipse/m2e/android/AndroidMavenProjectConfigurator.java >> >> >> TIA... >> > _______________________________________________ > m2e-dev mailing list > m2e-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/m2e-dev