Re: [m2e-dev] AbstractJavaProjectConfigurator not exposed.

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

You most like would need to copy&paste entire m2e.jdt bundle. I think "ignore the warnings" is your only choice. In practical terms this means that you need to retest your extension with every new m2e versions (which you need to do anyways) and possibly make changes to your AbstractJavaProjectConfigurator subclass in the unlikely event we need to make incompatible changes to m2e core.

 

--

Regards,

Igor

 

 

On Sun, Jul 5, 2015, at 03:45 PM, Olivier NOUGUIER wrote:

Hi all,

  I'm trying to add support for wisdom [0] in m2e [2].

  Wisdom defines its own packaging (wisdom) and its own lifecycle [1]. This lifecycle does not use maven-compiler-plugin, but relies on it for the jdk settings.

  Because wisdom is all about java, I'd like to be able to use about 90% of org.eclipse.m2e.jdt.internal.AbstractJavaProjectConfigurator. It looks like for the moment I have either to ignores the "Discouraged access" warning or cut & paste the content of this class.

 

 Is there an alternative ?

 

Thanks,

Olivier

 

 

[0]: http://wisdom-framework.org/

[1]: https://github.com/wisdom-framework/wisdom/blob/master/core/wisdom-maven-plugin/src/main/resources/META-INF/plexus/components.xml#L27

[2]: https://github.com/cheleb/org.wisdom.m2e

 

-- 

"Computers are useless. They can only give you answers."

- Pablo Picasso -

_______________________________________________

m2e-dev mailing list

m2e-dev@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/m2e-dev