Android m2e issue

[ph...@darwino.com]

M2E Android has an issue when it fails reading a project, see the exception bellow. I even got this issue when one on my projects in the eclipse workspace are simply closed. Sometimes it is because of other issues that take me literally hours to figure out in a 100+ projects workspace. As a result, the classpath is not properly configured and the project does not compile.

Jesse, who is my co-worker, submitted to pull request on Github (https://github.com/rgladwell/m2e-android/pull/370) 2 years ago, but it never got merged in.

Can someone help merging the fix and make this plugin more robust? Not sure who owns it now. If it is in Andmore next, that's ok.

java.lang.NullPointerException
 at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenProject(MavenModelManager.java:268)
 at me.gladwell.eclipse.m2e.android.project.EclipseAndroidWorkspace.findOpenWorkspaceDependency(EclipseAndroidWorkspace.java:54)
 at me.gladwell.eclipse.m2e.android.project.EclipseAndroidWorkspace.findOpenWorkspaceDependencies(EclipseAndroidWorkspace.java:77)
 at me.gladwell.eclipse.m2e.android.configuration.classpath.PersistNonRuntimeClasspathConfigurer.configure(PersistNonRuntimeClasspathConfigurer.java:60)
 at me.gladwell.eclipse.m2e.android.AndroidMavenProjectConfigurator.configureClasspath(AndroidMavenProjectConfigurator.java:110)
 at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
 at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
 at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
 at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
 at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)

[Manfred Moser]

The plugin is currently unmaintained and up for adoption. Ricardo is still listening on the list and would be happy to give it to a new maintainer.

Manfred

ph...@darwino.com wrote on 08.04.2017 14:51:

>
> M2E Android has an issue when it fails reading a project, see the exception bellow. I even got this issue when one on my projects in the eclipse workspace are simply closed. Sometimes it is because of other issues that take me literally hours to figure out in a 100+ projects workspace. As a result, the classpath is not properly configured and the project does not compile.
>
>

> Jesse, who is my co-worker, submitted to pull request on Github (https://github.com/rgladwell/m2e-android/pull/370 <https://github.com/rgladwell/m2e-android/pull/370> ) 2 years ago, but it never got merged in.

>
>
> Can someone help merging the fix and make this plugin more robust? Not sure who owns it now. If it is in Andmore next, that's ok.
>
>
> java.lang.NullPointerException
> at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenProject(MavenModelManager.java:268)
> at me.gladwell.eclipse.m2e.android.project.EclipseAndroidWorkspace.findOpenWorkspaceDependency(EclipseAndroidWorkspace.java:54)
> at me.gladwell.eclipse.m2e.android.project.EclipseAndroidWorkspace.findOpenWorkspaceDependencies(EclipseAndroidWorkspace.java:77)
> at me.gladwell.eclipse.m2e.android.configuration.classpath.PersistNonRuntimeClasspathConfigurer.configure(PersistNonRuntimeClasspathConfigurer.java:60)
> at me.gladwell.eclipse.m2e.android.AndroidMavenProjectConfigurator.configureClasspath(AndroidMavenProjectConfigurator.java:110)
> at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
>
>

> --
> You received this message because you are subscribed to the Google Groups "Maven Android Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to maven-android-deve...@googlegroups.com <mailto:maven-android-deve...@googlegroups.com> .
> For more options, visit https://groups.google.com/d/optout <https://groups.google.com/d/optout> .

[ph...@darwino.com]

Thanks, Ricardo is already aware of the issue.

I understand, and really value, the involvement of individuals like Ricardo. I spent, and still spend, a lot of time on other open source projects (OpenNTF). But I cannot take this ownership. We need a company to support this effort, the same way you guys support the Android/Maven plug-in. Else it is just going to die.

BTW, we are using Android/Maven because our main dev environment is Eclipse. I'll be curious to know what the other Android/Maven consumers are using, do you know?

Phil.

> To unsubscribe from this group and stop receiving emails from it, send an email to maven-android-developers+unsub...@googlegroups.com <mailto:maven-android-developers+unsubscribe@googlegroups.com> .

[Manfred Moser]

The Android Maven Plugin is sponsored by simpligility .. but that is my one man company that is not even involved in Android development at this stage anymore. If I had more time I would pick up Me2 Android myself as I have good connections to the rest of the M2e team.

Personally I use M2e for my development and used both M2E as well as IntelliJ with Android Maven Plugin in the past. I also know that it is used with Netbeans successfully.

manfred

ph...@darwino.com wrote on 10.04.2017 17:46:

> Thanks, Ricardo is already aware of the issue.
>
>
> I understand, and really value, the involvement of individuals like Ricardo. I spent, and still spend, a lot of time on other open source projects (OpenNTF). But I cannot take this ownership. We need a company to support this effort, the same way you guys support the Android/Maven plug-in. Else it is just going to die.
>
>
> BTW, we are using Android/Maven because our main dev environment is Eclipse. I'll be curious to know what the other Android/Maven consumers are using, do you know?
>
>
> Phil.
>
> On Monday, April 10, 2017 at 12:46:34 PM UTC-4, Manfred Moser (simpligility) wrote:
>> The plugin is currently unmaintained and up for adoption. Ricardo is still listening on the list and would be happy to give it to a new maintainer.
>>
>> Manfred
>>

>> ph...@darwino.com <%20target=> wrote on 08.04.2017 14:51:
>>
>> >
>> > M2E Android has an issue when it fails reading a project, see the exception bellow. I even got this issue when one on my projects in the eclipse workspace are simply closed. Sometimes it is because of other issues that take me literally hours to figure out in a 100+ projects workspace. As a result, the classpath is not properly configured and the project does not compile.
>> >
>> >

>> > Jesse, who is my co-worker, submitted to pull request on Github (https://github.com/rgladwell/ <https://github.com/rgladwell/m2e-android/pull/370> m2e-android/pull/370 <https://github.com/rgladwell/ <https://github.com/rgladwell/m2e-android/pull/370> m2e-android/pull/370> ) 2 years ago, but it never got merged in.

>> >
>> >
>> > Can someone help merging the fix and make this plugin more robust? Not sure who owns it now. If it is in Andmore next, that's ok.
>> >
>> >
>> > java.lang.NullPointerException
>> > at org.eclipse.m2e.core.embedder.MavenModelManager.readMavenProject(MavenModelManager.java:268)
>> > at me.gladwell.eclipse.m2e.android.project.EclipseAndroidWorkspace.findOpenWorkspaceDependency(EclipseAndroidWorkspace.java:54)
>> > at me.gladwell.eclipse.m2e.android.project.EclipseAndroidWorkspace.findOpenWorkspaceDependencies(EclipseAndroidWorkspace.java:77)
>> > at me.gladwell.eclipse.m2e.android.configuration.classpath.PersistNonRuntimeClasspathConfigurer.configure(PersistNonRuntimeClasspathConfigurer.java:60)
>> > at me.gladwell.eclipse.m2e.android.AndroidMavenProjectConfigurator.configureClasspath(AndroidMavenProjectConfigurator.java:110)
>> > at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
>> > at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
>> > at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
>> > at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
>> > at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
>> >
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups "Maven Android Developers" group.

>> > To unsubscribe from this group and stop receiving emails from it, send an email to maven-android-developers+ <%20target=> unsub...@googlegroups.com <mailto:maven-android- <%20target=> developers+...@googlegroups.com> .
>> > For more options, visit https://groups.google.com/d/ <https://groups.google.com/d/optout> optout <https://groups.google.com/d/ <https://groups.google.com/d/optout> optout> .

>
>
> --
> You received this message because you are subscribed to the Google Groups "Maven Android Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to maven-android-deve...@googlegroups.com <mailto:maven-android-deve...@googlegroups.com> .