On 02/09/2012 08:16 AM, Herbert.Neureiter@xxxxxxxxxxx wrote:
1) Libraries that were approved for reuse as is, be it via a PB or regular CQ (examples would be https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5318 or https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5503 ). In this case I would see two options:
The best option is to add them to Orbit. The second best option is
to pull them in from where they exist today (tools.tm) may have them
in a form that you can consume. Third, you can just put a copy of
the library in your own project's source code repository and pull it
from there.
I might actually change the order of two and three. Providing this
library for other projects to consume isn't tools.tm's role; forming
any kind of dependency along those lines is inadvisable. In fact,
let's just take that off the table.
I'm pretty sure that Maven will let you get away with #3 while we're
(you're) putting #1 in place...
I'm not sure exactly what form maven.eclipse.org will wind up
taking, but I'm pretty sure that everything that will be in there
will be owned by one project or another, which means that the three
options I've outlined will still apply, but with a different
delivery mechanism.
2) Libraries that are approved for reuse with modifications (subset). An example would be https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5561 . In this case I am not entirely sure what the process and distribution of responsibilities would be to get the modified binaries made available via maven.eclipse.org. Would the standard process be via an Orbit contribution or are there other ways to address this?
It depends :-)
Modified/subset libraries might fit in Orbit if they are generally
useful. The specific case should be discussed with Orbit team. If
the modifications are only useful to your project, then they
probably belong in your project.
Ultimately, projects will be able to populate maven.eclipse.org
themselves and you can put the libraries in there.
Is any of this helpful?
Wayne
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
 
|