commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Cohen <sco...@javactivity.org>
Subject Re: [net] working on 1.2.0 release
Date Wed, 21 Apr 2004 03:15:54 GMT
On Tuesday 20 April 2004 9:59 pm, Jeffrey D. Brekke wrote:
...
>
> I just gen'd the site ( didn't deploy ) with rc-2.

By "the site" do you mean commons-build or commons-net?
I can't generate commons-build or commons-net.  Very annoying.  Maven seems to 
have millions of options and no good documentation on how to use/debug it.  
Was so much easier with ant, and even maven, earlier, wasn't this bad.

BUILD FAILED
File...... file:/home/scohen/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly
Element... attainGoal
Line...... 639
Column.... 48
No goal [maven-license-plugin:register]
Total time: 6 seconds
Finished at: Tue Apr 20 21:23:36 CDT 2004

Bah.  The last was trying to gen commons-build.


>
> >>>>> On Tue, 20 Apr 2004 20:49:25 -0500, Steve Cohen
> >>>>> <scohen@javactivity.org> said:
> >
> > And the same happens with maven 1.0-rc2
> >
> > On Tuesday 20 April 2004 8:16 pm, Steve Cohen wrote:
> >> maven site ended after about 5 minutes with the following error
> >> message.  Any idea what this may have been caused by?  Do I need a
> >> new version of maven? I'm running 1.0-rc1-SNAPSHOT.
> >>
> >>
> >>
> >> xdoc:jelly-transform: [echo] Generating
> >> /home/scohen/workspace/jakarta-commons-net/target/docs/javadoc.html
> >> from
> >> /home/scohen/workspace/jakarta-commons-net/target/generated-xdocs/javado
> >>c.x ml
> >>
> >> BUILD FAILED
> >> File...... file:/home/scohen/.maven/plugins/maven-xdoc-plugin-1.4/
> >> Element... x:parse Line...... 325 Column.... 49
> >> /home/scohen/workspace/commons-build/menus/menus.dtd (No such file
> >> or directory) Nested exception:
> >> /home/scohen/workspace/commons-build/menus/menus.dtd (No such file
> >> or directory) Total time: 4 minutes 50 seconds Finished at: Tue Apr
> >> 20 20:02:47 CDT 2004
> >>
> >> On Tuesday 20 April 2004 3:43 pm, Jeffrey D. Brekke wrote:
> >> > >>>>> On Tue, 20 Apr 2004 07:52:20 -0500, Steve Cohen >
>>>>>
> >>
> >> <scohen@javactivity.org> said:
> >> > > Thanks Jeff.  Looks like maven dist will take care of the
> >>
> >> binary and > > source distros.
> >>
> >> > > What command "pushes the site out"?
> >> >
> >> > maven site:deploy
> >> >
> >> > This will generate all the docs and reports, and then attempt to
> >>
> >> ssh > the site out.  If the user you are logged in as is a
> >> different > username than your apache one, you need to have
> >> maven.username set to > your apache account that has access to
> >> where the sites are.  You can > do this in your ~/build.properties
> >>
> >> or on the command-line:
> >> > maven -Dmaven.username=brekke site:deploy
> >> >
> >> > > Then there are the checksumming and gpg signing mentioned here:
> >> > > http://jakarta.apache.org/commons/releases/release.html
> >> >
> >> > I did this by hand on the last release.
> >> >
> >> > > Are these supported by maven?  Are they necessary for a release
> >> > > candidate as opposed to a full-up release?  I'm planning to do
> >>
> >> a > > release candidate, then a vote, then cut the actual release,
> >>
> >> > > assuming it passes.
> >> >
> >> > I don't think they are necessary for rc's but can't hurt.
> >> >
> >> > > Steve
> >> > >
> >> > > On Monday 19 April 2004 10:04 pm, Jeffrey D. Brekke wrote:
> >> > >> Not that I know of.  The last release I did I used maven to
> >>
> >> build > >> the source and binary dist's along with pushing the site
> >> out as > >> usual.
> >>
> >> > >> If you walk through it, keep some notes and maybe we can
> >>
> >> ammend the > >> current steps with maven alternatives.
> >>
> >> > >> >>>>> On Mon, 19 Apr 2004 20:42:06 -0500, Steve
Cohen >>>>>
> >> > >>
> >> > >> <scohen@javactivity.org> said: > >> > Most of
the release docs
> >>
> >> under Apache appear to be pre-maven.  Is > >> > there a doc on
> >> preparing a release with maven?
> >>
> >>
> >> ---------------------------------------------------------------------
> >>
> >> > >> > 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
> >>
> >> ---------------------------------------------------------------------
> >> 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


---------------------------------------------------------------------
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