[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [soa-pmc] Managing Depencies
|
CC'ing Stardust development.
-----Original Message-----
From: soa-pmc-bounces@xxxxxxxxxxx [mailto:soa-pmc-bounces@xxxxxxxxxxx] On Behalf Of Oliver Kopp
Sent: Mittwoch, 18. Dezember 2013 08:15
To: SOA PMC mailing list
Subject: [soa-pmc] Managing Depencies
Hi SOA team,
I'm still in the process to shape the initial code contribution of Winery. Thinking of the next steps, I wonder, what a good practice of managing libraries ist.
I'm currently refusing to create a winery-local git repository for third-party libraries: Maven can also work with p2 and we have bower:
My goal is to have only self-written code in the repositories of Winery.
I would try to get all my Java depedencies into Orbit (meaning bundling it as outlined in https://www.eclipse.org/orbit/overview.php). Regarding the JavaScript libraries, I would work on setting up a Eclipse bower registry (https://bugs.eclipse.org/bugs/show_bug.cgi?id=420148).
Does that make sense? How are you dealing with your third party library dependencies?
Cheers,
Oliver
_______________________________________________
soa-pmc mailing list
soa-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/soa-pmc
