[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Calling JavaProjectConfigurator.configure() in m2e 1.6
|
Try declaring android configurator as secondary to java configurator. This way m2e will always run android configurator after java.
On Tue, Jun 23, 2015, at 12:13 PM, Csaba Kozák wrote:
There is an
issue we encountered with m2e 1.6 in m2e-android.
So basically, in our configurator, we call JavaProjectConfigurator.configure() so the Java classpath is set up before our configurator is doing anything. I am not sure this is a good approach, but worked so far.
However in m2e 1.6, when we call JavaProjectConfigurator.configure(), the java configurator is in an uninitialized state, so it produces
this exception.
It also turned out that JavaProjectConfigurator.configure() is already called by m2e. So i removed our call to JavaProjectConfigurator.configure(), which resolves the problem with m2e 1.6, but it makes since worse in m2e 1.5: we fail with an exception when try to get the Java classpath in our configurator: Java Model Status [android-application does not exist].
So what should be done here? Thanks in advance!
_______________________________________________
m2e-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
