Re: [m2e-users] A bundle dilemma

[Benson Margulies <bimargulies@xxxxxxxxx>]

On Sun, Aug 28, 2011 at 10:40 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> m2e-tycho does not resolve pom-first dependencies from maven
> repositories directly. it needs "stepping-stone" workspace bundle
> project, which apparently does not work for you.

So, now, what's the shortest path to putting a bundle somewhere else
(not pom-first) that tycho can find it? Do I have to wrap it up as a
product to publish it as p2? Is there some OSGI-ish 'obr' alternative
to P2?

>
> in more technical term, PDE target platform implementation is quite
> limited on both what it can do, i.e. single target platform for entire
> workspace, and how it can be extended, i.e. pretty much not at all, so
> m2e-tycho works by making workspace maven project visible to pde but
> can't make maven dependencies visible to pde directly, without such
> intermediate maven-pde project.
>
> --
> Regards,
> Igor
>
> On 11-08-28 7:44 AM, Benson Margulies wrote:
>>
>> Igor,
>>
>> A specific question: what if I used the shade plugin to make a jar of
>> all this, and then the bundle to add in the  manifest? Should I expect
>> m2e to cope with it as a pom-first dependency? What m2e configuration
>> would I need?
>>
>> --benson
>>
>>
>> On Sat, Aug 27, 2011 at 10:24 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>
>>  wrote:
>>>
>>> m2e by itself knows nothing about maven-bundle-plugin and pde, you need
>>> to have m2e-tycho to make it understand packaging=bundle. Also, as I
>>> already mentioned, current version of m2e-tycho does NOT support
>>> Embed-Dependency. This support lives on a branch [1] and waits
>>> for [2], [3] and [4] to be reviewed and accepted by respective project
>>> development teams.
>>>
>>> [1] https://github.com/sonatype/m2eclipse-tycho/tree/mbp-embed-dependency
>>> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=353442
>>> [3] https://issues.apache.org/jira/browse/FELIX-3061
>>> [4] https://github.com/bnd/bnd/pull/71
>>>
>>> --
>>> Regards,
>>> Igor
>>>
>>> On 11-08-27 9:01 PM, Benson Margulies wrote:
>>>>
>>>> I've found, I think, a bug in the maven-bundle-plugin.
>>>>
>>>> In my particular case, it generated the correct manifest into
>>>> target/classes/META-INF ... and then sticks a *different* manifest
>>>> into the result jar.
>>>>
>>>> So I tried to work around this by avoiding the 'bundle' packaging. By
>>>> using the 'manifest' goal and some jar plugin config, I succeeded in
>>>> getting it to leave the right manifest in place.
>>>>
>>>> Unfortunately, I can't seem to persuade M2E to pay attention to the
>>>> embedded jars in the resulting artifact. In fact, M2E seems to not
>>>> recognize my project as a bundle at all.
>>>>
>>>> In eclipse, I get errors like:
>>>>
>>>> Bundle 'org.apache.maven.doxia.ide.dependencies' cannot be resolved
>>>> _______________________________________________
>>>> m2e-users mailing list
>>>> m2e-users@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>