Re: [orbit-dev] Contribution to Orbit of code from existing Eclipse Proj

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

see! the people want a single unified central repository of artifacts!
 they want to make it easier to allow others to consume their work...

now if we could just find one that works well and serves out millions
of artifacts a day

hmmmm :)

*removes tongue from cheek*

jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Tue, Jan 31, 2012 at 17:35, David M Williams
<david_williams@xxxxxxxxxx> wrote:
>
>> It is a third party library - in that it is
>> a library we depend on to run that is potentially used by other
>> parties that do
>> not use our project's code.
>
> I can sympathize, since it has "javax" in the package name ... but I don't
> think that is related to it being third party or not.
>
> There are (or, must be, or could be) many ways EclipseLink can make this
> available for others to use, that do not otherwise use EclipseLink. But, an
> Orbit repo is not one of them.
>
> A similar case is the JDT compiler ... others (e.g. apache tomcat (I
> think)) use it, but they still "get" it from JDT. Similar for an xpath
> processor used by xerces ... they get it from the XSL project in WTP. In
> those cases, the "packages" can be used as jars, or as OSGi bundles, and
> the consumers are not interested in any other part of the parent project.
>
> Not sure what would be different about this case with 'javax.persistence'.
> If it is "appearances" that you are trying to change (to make it clear that
> javax.persistence is "independent" of EclipseLink) then ... well, ... a)
> not sure it is completely since same people work on both :) but more
> important, b) "moving it to Orbit" to change appearances does not seem like
> a completely honest move (since Orbit is well known to be the home of
> non-Eclipse bundles). Perhaps there are other options?
>
> I'm sure I could easily be misunderstanding something, but my take is that
> this is not in the scope of Orbit.
>
> Hope these comments are constructive and get you thinking of other
> solutions ... or ways to educate me on what I am missing :)
>
>
>
>
>
>
> From:   Tom Ware <tom.ware@xxxxxxxxxx>
> To:     orbit-dev@xxxxxxxxxxx,
> Date:   01/31/2012 04:09 PM
> Subject:        Re: [orbit-dev] Contribution to Orbit of code from existing
>            Eclipse Project
> Sent by:        orbit-dev-bounces@xxxxxxxxxxx
>
>
>
> The reason we are considering Orbit is that the code we are spinning off is
> in a
> javax package (javax.persistence).  It is a third party library - in that
> it is
> a library we depend on to run that is potentially used by other parties
> that do
> not use our project's code.  The unusual part about it is that we are both
> the
> main contributers to the Eclipse project that uses it and the "3rd party"
> the
> provides the library.
>
> -Tom
>
> On 31/01/2012 3:55 PM, David M Williams wrote:
>>
>>  From a quick read, if I am understanding this suggestion, this does not
>> seem appropriate.
>>
>> Orbit is all about "third party" code (i.e. code not at Eclipse).
>>
>> If your goal is to make your project's code "more readily accessible to
>> other projects" then there are better ways to do that. Such has have your
>> own p2 repository on 'downloads' server.
>>
>> Make sense?
>>
>>
>>
>>
>>
>> From:          Tom Ware<tom.ware@xxxxxxxxxx>
>> To:            Orbit Developer discussion<orbit-dev@xxxxxxxxxxx>,
>> Date:          01/31/2012 03:50 PM
>> Subject:               [orbit-dev] Contribution to Orbit of code from existing
> Eclipse
>>              Project
>> Sent by:               orbit-dev-bounces@xxxxxxxxxxx
>>
>>
>>
>> Hi All,
>>
>>     I am not sure if there is precedent for this, but I am hoping to spin
>> off a
>> part of an Existing Eclipse project into Orbit to make it more readily
>> accessible to other projects.  All the code is EPL/EDL and was checked-in
>> following the Eclipse IP process.
>>
>>     I am already an Orbit committer and hoping to add this code.
>>
>>     I have entered a CQ for the contribution to Orbit referencing the SVN
>> location of the existing code.
>>
>>     Is there anything additional I should do outside of the normal Orbit
>> process?
>>
>> Thanks in advance,
>> Tom
>> _______________________________________________
>> orbit-dev mailing list
>> orbit-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>>
>>
>>
>> _______________________________________________
>> orbit-dev mailing list
>> orbit-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/orbit-dev
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
>
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev