Re: [m2e-dev] [m2eclipse-dev] m2eclipse extensions that modify project c

[Ricardo Gladwell <ricardo.gladwell@xxxxxxxxx>]

Hey Igor

Thanks for the information and good look with the move to become part
of the Eclipse release, sounds like a big job.

My Android lifecycle mapping appears to be successfully binding to the
"apk" build type, but the JavaProjectConfigurator no longer seems to
be running on my Android projects before running custom my
ADTProjectConfigurator. How do I specify this in my lifecycle mapping
class?

TIA...

--
Ricardo Gladwell <ricardo.gladwell@xxxxxxxxx>
http://www.google.com/profiles/ricardo.gladwell
Twitter: @rgladwell - MSN: axonrg@xxxxxxxxx

On 22 November 2010 21:05, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> I don't know, sorry. It is relatively rare to have plugin version
> missing, so it is not a priority atm. Also note, that unless we find
> problems serious enough to justify 0.12.1, the next version will be
> built off Eclipse Foundation infra, with new package names, bundle id
> and much reworked core. Official release will be part of Eclipse Indigo
> (3.7) next June, but we obviously will have integration and milestone
> builds way before that.
>
> And as I mentioned, it is better to lock all versions regardless of m2e.
> You can do this from
> org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping, assuming you
> have commit privileges on maven-android-plugin.
>
> --
> Regards,
> Igor
>
> On 10-11-22 03:28 PM, Ricardo Gladwell wrote:
>>
>> Hi Igor
>>
>> Thanks, using a lifecycle mapping seemed to resolve a lot my issues,
>> your help is  much appreciated.
>>
>> I appreciate you guys have just released a new version, but when do you
>> think you guys will release a new version of m2eclipse with
>> MNGECLIPSE-2555 fixed?
>>
>> TIA...
>>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>