Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Resolve external bundle dependencies

Thanks a lot for guiding me into the right direction. I will try to setup my own p2 repository and see where that brings me. 

-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Oliver Pfau
Sent: dinsdag 18 oktober 2011 16:25
To: 'Tycho user list'
Subject: Re: [tycho-user] Resolve external bundle dependencies

I have also created my own p2 repository form the tycho build. But the dependencies are only defined in the manifest.mf files.

-----Ursprüngliche Nachricht-----
Von: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] Im Auftrag von Igor Fedorenko
Gesendet: Dienstag, 18. Oktober 2011 16:13
An: tycho-user@xxxxxxxxxxx
Betreff: Re: [tycho-user] Resolve external bundle dependencies

p2 repositories are certainly the easiest and the most mature way of resolving Tycho project dependencies.

There is also a limited support for bundles available from maven repositories (does springsource provides their bundles via a maven repository?). It works okay if you have small number of such dependencies, but gets cumbersome if number as number of dependencies grows. You can read more about dependencies on bundles from maven repositories in [1]

Tycho does not support any other repository formats.

[1]
https://docs.sonatype.org/display/TYCHO/Dependency+on+pom-first+artifacts

--
Regards,
Igor

On 11-10-18 9:29 AM, De Backer Frederik (DBB) wrote:
> The springsource EBR is not a p2 repository (at least not that i know).
> Is this necessary? Can Tycho only work with p2 repositories?
>
> If yes, is there another way to solve the dependency?
>
> Kr,
>
> Frederik.
>
> -----Original Message-----
> From: tycho-user-bounces@xxxxxxxxxxx
> [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
> Sent: dinsdag 18 oktober 2011 14:53
> To: tycho-user@xxxxxxxxxxx
> Subject: Re: [tycho-user] Resolve external bundle dependencies
>
> Does springsource provide their bundles via a p2 repository?
>
> --
> Regards,
> Igor
>
> On 11-10-18 3:34 AM, De Backer Frederik (DBB) wrote:
>> Dear,
>>
>> I am a new user to tycho and I am faced with the following problem.
>>
>> I have developped an OSGi bundle in Eclipse and this bundle has a 
>> dependency on com.springsource.org.apache.commons.io. This is a 
>> bundle
>
>> which is present in the SpringSource Enterprise bundle repository.
>>
>> In the manifest of my bundle is the following :
>> *Require-Bundle*:
>> com.springsource.org.apache.commons.io;/bundle-version/="1.4.0"
>>
>> I use tycho 0.13.0 to do the build of this bundle via maven. However 
>> I
>
>> get the following error when doing a mvn clean install
>>
>> Bundle com.dexia.sample.HelloService - Missing Constraint:
>> Require-Bundle: co
>> m.springsource.org.apache.commons.io; bundle-version="1.4.0"
>>
>> What is the recommended way to resolve this dependency? I see things 
>> like p2 repositories and target platform definitions but I don't 
>> quite
>
>> understand well of any of these concepts need to be used to solve 
>> this
>
>> problem.
>>
>> We are using nexus to manage our repositories and the springsource 
>> bundle repositories have been added to nexus.
>>
>> Thx a lot for the assistance,
>>
>> Frederik.
>>
>> ---------------------------------------------------------------------
>> -
>> --- Dexia
>> disclaimer: http://www.dexia.com/maildisclaimer.htm
>> ---------------------------------------------------------------------
>> -
>> ---

_______________________________________________
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
</pre>

-------------------------------------------------------------------------
Dexia disclaimer:

http://www.dexia.com/maildisclaimer.htm
-------------------------------------------------------------------------
<pre>



Back to the top