commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Colebourne" <scolebou...@btopenworld.com>
Subject Re: [all] Shared build causes issues in releases
Date Tue, 06 Apr 2004 21:45:46 GMT
Thanks for sorting the problem with current builds.

My point is more long term. I am proposing that a release of a single
commons component should be complete (and tagged) internally, without
reference to an external commons-build folder.

To achieve this, a release must
a) copy and rename commons-build/project.xml to project/project-common.xml
b) edit project/project.xml to change the reference from the central source
to the local one

ATM release managers will have to remember to do this manually.

(BTW, I needed the maven to work not to create a jar, but to fetch the
dependencies of validator. Running 'maven clean' seemed like the quickest
solution.)

Stephen

From: "Mark R. Diggory" <mdiggory@latte.harvard.edu>
> I've now added build and report sections that were missing to the
> subproject project.xml files, please verify they contain what you want
> for your project and adjust them to your liking if they do not.
>
> Maybe someone can review and do the same for the sandbox?
>
> On Tue, 2004-04-06 at 13:24, David Graham wrote:
> > Well both the old and new versions cause problems for some set of
projects
> > so going back isn't really going to help.  The common project.xml should
> > not define a <build> section because each component is different.  For
> > example, Validator has src/share instead of src/java.  It should be up
to
> > each project to define how they build and what reports they want
> > generated.
> >
> > Note that the sandbox-build's project.xml suffers from the same
definition
> > as commons-build used to and also needs to be changed.
> >
> > David
> >
> > --- Gary Gregory <ggregory@seagullsw.com> wrote:
> > > Why can't we go /back/ to the version of commons-build that did not
blow
> > > up and /discuss/ it from there. Then we can change all projects in
step.
> > >
> > > ?
> > >
> > > Thank you,
> > > Gary
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Small Business $15K Web Design Giveaway
> > http://promotions.yahoo.com/design_giveaway/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> --
> Mark R. Diggory
> Software Developer - VDC Project
> Harvard MIT Data Center
> http://www.hmdc.harvard.edu
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message