Re: [tycho-user] Using Tycho to Build Custom Target Platform

[Timo Rohrberg <rti.init@xxxxxxxxxxxxxx>]

Hello Igor,

I know that's not common practice on a public mailinglist, but I would
like to thank you for your help. With all the hints you gave me, I
finally got my custom targetplatform build to work. Thank you.

If anyone is interested in the result, I can easily provide sample code.

Regards
Timo


2011/10/11 Igor Fedorenko <igor@xxxxxxxxxxxxxx>:
> Generated com.thoughtworks.xstream bundle jar does not have
> expected manifest. [1] explains how to use custom manifests.
>
> [1] http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
>
> --
> Regards,
> Igor
>
> On 11-10-11 11:11 AM, Timo Rohrberg wrote:
>>
>> Thank you for that hints. Unfortunately, using PDE Juno is not an
>> option for us. For that, I will need to continue creating the wrapper
>> plugin the way I did it in the attached sample project until m2e-tycho
>> is released.
>>
>> But still, I do not get what I'm doing wrong: I tried to solve my
>> original problem by "helping" Tycho to resolve the dependency to the
>> wrapper plugin as it is done in the documentation you send me. But
>> still, Tycho cannot resolve the dependency.
>>
>> Can you quickly have a look at the updated version of my sample
>> projects attached and give me further hints to solve that issue?
>>
>> Thank you very much.
>> Timo
>>
>>
>> 2011/10/11 Igor Fedorenko<igor@xxxxxxxxxxxxxx>:
>>>
>>>
>>> On 11-10-11 10:22 AM, Timo Rohrberg wrote:
>>>>
>>>> But one question still remains right now:
>>>>
>>>>> As a side note, maven-bundle-plugin<Embed-Dependency>    provides much
>>>>> cleaner alternative to dependency:unpack when "wrapping" non-OSGi jars
>>>>> in bundles. At least I find it much easier to use.
>>>>
>>>> This indeed sounds much cleaner, but is it possible to also unpack
>>>> sources of the wrapped non-OSGi jars with this approach? In my case,
>>>> we do have a lot of "old" artifacts in our Maven repository which are
>>>> with sources. I would like to wrap those to later allow navigation
>>>> into the source from the Eclipse workbench while using those wrappers.
>>>>
>>>
>>> Source code lookup works inside Eclipse workspace provided correct
>>> versions of m2e-tycho, pde and maven-bundle-plugin are used.
>>>
>>> Currently, this means PDE Juno M2 or better, maven-bundle-plugin 2.4.0,
>>> not released yet, but SNAPSHOTS are available.
>>>
>>> No special configuration is required, just import all relevant projects
>>> in Eclipse workspace. This is how we develop m2e 1.1.
>>>
>>> --
>>> Regards,
>>> Igor
>>> _______________________________________________
>>> tycho-user mailing list
>>> tycho-user@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>>>
>>>
>>>
>>> _______________________________________________
>>> tycho-user mailing list
>>> tycho-user@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
>