not sure why is was broke but i've committed some fixes and i think it now works for me. i'm think that your approach was right (hopefully someone will jump in here and correct me if i'm wrong) and everything should work now.
- robert On Wed, 2005-05-18 at 22:26 +1200, Simon Kitching wrote: > Hi, > > I've figured out how to update the jakarta site pages. It's mostly > documented here, though some parts need updating: > http://jakarta.apache.org/commons/releases/release.html > Basically, it involves committing .xml and .html files into svn, then > doing a svn update on people.apache.org. > > > And updating the project-specific pages is simple with maven: > * maven site:generate > * maven site:deploy > (at least that's how I think it works; haven't done this yet). > > > But how are the generic commons pages updated? The "releases" link above > just doesn't seem right at all; it refers to a "jakarta-commons" > directory in subversion but I can't see any such thing. And it still > refers to "cvs" which must be wrong. It looks like the pages that need > to be edited are under commons-build in subversion, but I can't see how > to generate the html versions or push them out. > > > Running "maven site:generate" in commons-build/trunk just results in > maven errors (maven 1.0.2): > > ASTIdentifier : java.lang.reflect.InvocationTargetException > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.apache.commons.jexl.util.introspection.UberspectImpl > $VelMethodImpl.invoke(UberspectImpl.java:304) > at > org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:56) > at > org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:106) > at > org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:88) > at > org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:123) > at > org.apache.commons.jelly.expression.jexl.JexlExpression.evaluate(JexlExpression.java:115) > at org.apache.maven.jelly.MavenExpressionFactory > $1.evaluate(MavenExpressionFactory.java:76) > at > org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:106) > at > org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsString(ExpressionSupport.java:91) > at > org.apache.commons.jelly.expression.CompositeExpression.evaluateAsString(CompositeExpression.java:354) > at > org.apache.maven.jelly.JellyUtils.decomposeExpression(JellyUtils.java:246) > at > org.apache.maven.MavenUtils.getInterpolatedPOM(MavenUtils.java:384) > > > > > What I would like to do is just push some changes that I have made to > http://jakarta.apache.org/commons/patches.html > which replaces obsolete CVS info with new SVN info. I've committed > changes to subversion file > commons/proper/commons-build/trunk/xdocs/patches.xml > but can't figure out how to build and deploy the site. > > I guess once I figure all this deployment stuff out, I should also > update the "releases" page in commons that is supposed to document all > this :-). > > > I also see that there is a subversion directory > http://svn.apache.org/repos/asf/jakarta/commons/proper/docs/ > which I presume is left over from the old days where the commons site > was deployed by checking in .html files to CVS, then having someone run > "cvs update" on people.apache.org to pull the latest files out. If this > is the case, then can we delete this directory? > > > > > > Cheers, > > Simon > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
