Re: [m2e-users] Introducing new dependency from code is broken

[Igor Fedorenko <igor@xxxxxxxxxxxxxx>]

It appears some other tool, possibly PDE but I am not sure, offers
adding org.eclipse.osgi_xxx.jar to the project build path bypassing
pom.xml. m2e has no control over this, so you need to contact developers
of that tool to disable such proposals for Maven projects.

Ability to search Maven repository index for classes and packages has
been removed from m2e 1.0 due to time/resources constraints and there
are not immediate plans to reintroduce this feature unless somebody
contributes a quality patch with adequate automated test coverage.

--
Regards,
Igor

On 11-07-28 11:07 AM, Sanjeeb Sahoo wrote:
> Create a new simple maven project, add a java class and introduce a new
> type (e.g. BundleContext) in code. There will be a quick fix option to
> "fix project setup" which will suggest to add org.eclipse.osgi_xxx.jar
> to build class path. But, it does not update the pom.xml, so while the
> project builds fine inside the IDE, it does not compile when maven is
> invoked outside the IDE. This is the behavior with m2e plugin in indigo.
>
> I switched back to my helios + m2eclipse environment. There also I found
> slightly different behavior. In helios environment, if I right click and
> chose "quick fix," it offers a new option called "search dependency for
> ..." Such option does not appear in indogo+m2e environment.
>
> The behavior of m2e+indigo is surely a bug. Either "fix project setup"
> should navigate user to maven dependency management wizard or there
> should be a new option take user to maven dependency management wizard
> from the editor. I have not filed a bug yet, because it looks like a
> very basic issue to me, so I want to collect feedback here first.
>
> Thanks,
> Sahoo
>
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users