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

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

currently the glassfish jsp reference implementation with a couple of
patches on them that have been opened with the project but either
haven't been applied or don't meet our release schedule

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Tue, Nov 29, 2011 at 16:20, Igor Fedorenko <ifedorenko@xxxxxxxxxxxx> wrote:
> What dependencies you need to deploy to central? Wouldn't the duplicate
> artifacts that are already there?
>
> --
> Regards,
> Igor
>
> On 11-11-29 4:32 PM, Jesse McConnell wrote:
>>
>> Since we (jetty) have been putting more efforts into getting the jsp
>> reference implementation into orbit in a generally usable fashion (its
>> sadly had a few glassfish specific things creep in we have had to
>> patch and take up with them) we have tried to align our usage with the
>> bundles in orbit.
>>
>> however since can't rely on orbit being durable at all, the artifacts
>> inside can change their versions, or the link to the actual orbit
>> repositories change on a whim we long ago stopped trying to consume
>> directory out of orbit for our maven builds, opting instead to put the
>> limited number of objects we require into a special directory on
>> downloads.eclipse.org under out jetty project and reference those
>> directly for building out distributions.....
>>
>> Which leads me to the issue we now face, of getting the jsp bundles we
>> produced in orbit as a maven dependency for our jetty-maven-plugin
>> which is hosted out of our codehaus git repository.  It _needs_ be to
>> able to address this jsp bundle with maven coordinates so I am going
>> to start putting our orbit bundles into maven central for jetty.  This
>> is a flat out requirement for us now...our prior solution isn't
>> acceptable any longer now that we have our maven plugin needing to
>> reference this bundle.
>>
>> my intent at this point is to stuff our orbit bundles under
>> org.mortbay.jetty.jsp.orbit, or perhaps
>> org.eclipse.jetty.orbit:artifactId.  Ehile it would be nicer if I put
>> them under org.eclipse.orbit....I suspect there might be some
>> heartburn if I went and tried that :)
>>
>> So, does anyone have any plans they want to share on how they handle
>> this situation?  I know there have been countless discussions on this
>> topic on countless bugs in bugzilla, I have participated in a few of
>> them...but at this point we just can't wait anymore and are going to
>> put in a patchwork solution for the time being.
>>
>> So its clear, even if orbit were to produce both p2 and maven
>> repositories of their content (which I believe people have said is
>> doable) we would still require that those maven repositories be synced
>> to maven central.
>>
>> cheers,
>> jesse
>>
>> --
>> jesse mcconnell
>> jesse.mcconnell@xxxxxxxxx
>> _______________________________________________
>> 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
>