Re: [orbit-dev] orbit bundles to maven central

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

honestly, imo orbit ought to produce fully versioned artifacts once
and put them in one place that is durable for all time...and when that
artifact changes, produce a new versioned artifact alongside the other
one...like a maven repository :)

that would be infinitely more usable (from a raw maven perspective)
then producing the equivalent of multiple discrete repositories of
artifacts that you have to surf into to track down a specifically
versioned artifact.  anyway, old argument...

jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Wed, Nov 30, 2011 at 07:21, Gunnar Wagenknecht
<gunnar@xxxxxxxxxxxxxxx> wrote:
> Am 30.11.2011 14:14, schrieb Jesse McConnell:
>> mostly because we have our 'releases' against things that were in
>> early builds of orbit (from the orbit release perspective) and we have
>> had a number of instances where we checked out an old release tag and
>> it wouldn't build because the orbit repo it needed was gone.  so to
>> make our old releases actually build we couldn't rely on orbit repos
>> any longer
>
> That does sound more like a process issue rather then a technical one. I
> think Orbit should produce promoted releases more often if downstream
> consumers need them.
>
> David might have more insights into the process, though.
>
> -Gunnar
>
> --
> Gunnar Wagenknecht
> gunnar@xxxxxxxxxxxxxxx
> http://wagenknecht.org/
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>