Phil Steitz wrote:
On 12/4/05, Steve Cohen <[EMAIL PROTECTED]> wrote:
Phil Steitz wrote:
On 12/4/05, Steve Cohen <[EMAIL PROTECTED]> wrote:
Martin Cooper wrote:
On 12/4/05, Steve Cohen <[EMAIL PROTECTED]> wrote:
Phil Steitz wrote:
On 12/4/05, Steve Cohen <[EMAIL PROTECTED]> wrote:
This is another inaccuracy in the instructions. Step 14 says the
dependencies are listed in STATUS.html. Net, at least doesn't have a
STATUS.html. These seem to be generated from project.xml.
Good point. Patch / update welcome. It would be great if you could
bundle up any other issues that you ran into into a patch or direct
update for the building/releasing docs.
Phil
I will, Phil. But is the non-existence of STATUS.html common to all of
commons? If so, I will make the revisions myself. Incidentally, these
items are all handled now prior to cutting the release, not as post
release items.
The STATUS files are a hold-over from the pre-Maven days. They were required
because there was no POM / project.xml file in which the committer list
could be maintained. Now that all of the components are using Maven, the
STATUS files are pretty much obsolete.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks, Martin. I'll be happy to update the files myself, but where are
they? I see some files that look like old versions of the site in
commons-build's xdocs but they don't match what's on the site now.
I've glanced all over the repository and haven't found the right place yet.
The relevant files are in
http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk/xdocs/releases/
maven site from /commons-build should generate the site locally for
you, then maven site:sshdeploy to publish (assuming you have key set
up)
Make sure to check changes in before updating the site.
Thanks!
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Alas and alack.
More maven problems.
Couldn't run maven site on commons-build
Downloaded maven 1.0.2
Reinstalled the maven xdoc plugin 1.9.2
get this:
xdoc:jelly-transform:
[echo] en
[echo] The current Locale is the default one
[echo] Scanning '/home/scohen/commons-build/target/generated-xdocs'...
[echo] Generating
/home/scohen/commons-build/target/docs/license.html from
/home/scohen/commons-build/target/generated-xdocs/license.xml
BUILD FAILED
File...... /home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin.jelly
Element... j:include
Line...... 479
Column.... 58
file:/home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:33:17:
<jsl:stylesheet>
file:/home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:156:57:
<jsl:applyTemplates>
file:/home/scohen/.maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:240:105:
<maven:property> You must define an attribute called 'defaultValue' for
this tag.
Total time: 10 seconds
Finished at: Sun Dec 04 22:09:51 CST 2005
:-(
Are you sure you are executing maven from the the right directory -
i.e., not above trunk?
Also, you need the top-level directory to be named "commons-build"
The second requirement can probably be removed by changing
maven.xdoc.jsl=../commons-build/commons-site.jsl
to
maven.xdoc.jsl=commons-site.jsl
In project.properties.
Phil
Thanks for all your help. These last suggestions worked.
I built the site, tested my changes, then pushed the site.
I DON'T have my key set up. where do I do this, it's a pain to keep
typing in my password, but doable.
Also, fyi, in my pushing of the site, I saw gobs of
[exec] chmod: some/file: Operation not permitted
Is this something not set up properly in my account or an expected
glitch? In any case somebody might want to check the chmod settings of
the site now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
