2007/10/17, Ted Husted <[EMAIL PROTECTED]>: > > I should mention that right now the Maven builds are not creating the > -docs artifact or doing the J4 backports. I don't know if the release > plugin is setup to do those too now.
Thanks for the mention :-) The release plugin won't do it automatically, so I need to configure it in some ways (an assembly descriptor for -docs, a new profile for J4). (Do we even want to keep running the J4 backport for 2.1? If so, we > might want to change the distribution artifact from -j4 to -backport, > to match the repository.) The classifier will be "backport" instead of "j4", right? BTW, the retrotranslator plugin for Maven 2 seems to be ok (I tried with Tiles 2), is there a reason not to using it? Another "sticky wicket" is that the current version number is embedded > in the home page for the Struts 2 area: > > * http://struts.apache.org/2.0.9/index.html > > We've been editing the docs/index.html file locally to change download > label to version 2.0.# (<small>version 2.0.#</small>). Otherwise, when > we archive the page, it cites the prior version rather than (what will > be) the current version.The index page actually in the repository > (rather than confluence), so we could also edit it before and after > the tagging. Or, we could stop citing the version number :) Sorry, I cannot understand, the "index.xml" is already in the repository, so we could edit, commit, and then release. Do you mean that the generated " index.html" is replaced by the one with the same name under Confluence? Ted, at this point I have a question: there are some issues to be fixed before the release plugin could be used. Do you want me to fix them, and then try to release the 2.1.0 version (but it will take a while), or do you want to release 2.1.0 ASAP and fix these issues later? In the latter case, I think I will pass, and let Rainer do the release :-D Thanks Antonio
