Hi Oliver
At JWT we use Orbit.
Putting dependencies in Orbit requires making a CQ (in order to
get it reviewed by legal people, approved by PMC...).
Here's how we do release builds of JWT using Maven Tycho (and luna
p2 release repository as only repository) :
http://wiki.eclipse.org/JWT_Automatic_Build
Here's how we reuse Orbit dependencies, with some additional
pointers :
http://wiki.eclipse.org/JWT_SVN#Orbit
As said as
http://wiki.eclipse.org/Maven , Eclipse has its own
Nexus at
https://repo.eclipse.org .
Having a look at poms may give you ideas...
Also, in attachment, a related mail from Wayne Beaton, reminding
that all dependencies should indeed be retrieved from Eclipse
servers.
Best Regards
Le 18/12/2013 14:14, Oliver Kopp a écrit :
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