Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] Fixing our TERRIBLE eclipse oriented build


sorry for the late response.

I agree that the lack or reproducibility is a huge problem.  Also our
dependency traceability is really badly damaged by the current system
(as evidenced by the cut and past of orbit versions between
jetty-distribution and jetty-osgi/test-jetty-osgi

My suggestion is that we create a separate project called
jetty-orbit-dependencies, whose entire function would be to pull down
orbit jars and publish them to maven central repository in group id
like: org.eclipse.jetty.orbit.javax.sevlet

This project itself would not have a reproducible build (as it would
fail once the orbit URLs had changed yet again), but at least it's
artefacts would be durable in maven central and thus jetty releases
would also be durable.


On 7 August 2010 01:25, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:
> This is just flat out ridiculous how our build has degraded to this point.
> IMO we can not release AT ALL based on eclipse repositories in our
> build to obtain artifacts.  They are far far too transitory with their
> retention policy and it absolutely devastates our build
> reproducibility...less then a week or two after one of our releases we
> can't build the tag without making adjustments to the ant download
> portions of the build.
> I am open to suggestions on ways to deal with this...and ideally
> eclipse will someday grow up and have a proper artifact repository
> that is durable but until then I propose we do the following.
> * pull every artifact that we rely upon out of orbit and put it into
> our site
> we still need to use this ant goop to build since we can't release
> with external maven repositories but this way we will at least have
> reproducible builds for longer then a week based on a tag
> I'll hold off on making this change to solicit feedback...for a little while...
> jesse
> --
> jesse mcconnell
> jesse.mcconnell@xxxxxxxxx
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx

Back to the top