Hi, 1) The parent site is not going to be deployed. The web-site is contained in cactus-site. 2) I added the assembly descriptors and after updating the project, you can look at the assemblies via: mvn assembly:assembly
3) I don't think that the manifests are lacking of information. As to the license there is a license header of every source file. 4) The scratchpad folder stays in the SVN repository, but is excluded from the assemblies, being produced. Please notice that my first goal is to move the source from the branch specified to the trunk, and after that making a release candidate. On Feb 1, 2008 2:41 PM, sebb <[EMAIL PROTECTED]> wrote: > mvn install - seems to work OK now > mvn site:site - seems to work OK now > > The parent pom needs some work if the parent site is to be deployed - > a lot of the sections are empty, e.g. no license or description. > > I could not work out how to create the distribution artefacts, so it > is impossible to say if they would be OK, but I did notice that the > jars that are created don't contain NOTICE or LICENSE files. For jars > that contain code, it would be helpful if the Manifests contained java > source and target versions. > > The Manifests are generally a bit lacking in information. It would be > useful to have: > > Built-By: User > Implementation-Version: 1.xx > X-Compile-Source-JDK: 1.4 (e.g.) > X-Compile-Target-JDK: 1.4 (e.g.) > Extension-Name: JMeter > Specification-Title: Apache Jakarta Cactus > Specification-Vendor: Apache Software Foundation > Implementation-Vendor: Apache Software Foundation > Implementation-Vendor-Id: org.apache > > Is the scratchpad directory tree necessary? It does not seem to be > used in the build. > > Also, the image files in > > documentation/dist/doc/images > > seem to be corrupt. > > Not sure what the purpose of the documentation tree is. > > S/// > On 01/02/2008, Petar Tahchiev <[EMAIL PROTECTED]> wrote: > > OK, > > > > if anybody tried it, can you post your recommendations and impressions? > > > > If not, I guess that it is OK, for a RC and I will continue with > improving > > the documentation. > > > > Cheers, Petar. > > > > On Jan 31, 2008 10:40 PM, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > > > On Jan 31, 2008 7:34 AM, Niall Pemberton <[EMAIL PROTECTED]> > > > wrote: > > > > On Jan 31, 2008 3:26 PM, Magnus Grimsell < > [EMAIL PROTECTED]> > > > wrote: > > > > > > Well, the version of Cargo integrated is: 0.9 > > > > > > > > > > Ok, I've done some fixes for Cactus to work with Cargo > 1.0-SNAPSHOT. > > > > > Once cargo releases 1.0 I'll be able to commit them. > > > > > > > > > > > One other quick question. My PGP key is signed only by Roy > > > > > > Fielding(I missed > > > > > > the > > > > > > key-signing party in Atlanta :-)) so will I be able to make a > > > release? > > > > > > > > > > I have never been involved in releasing Cactus. Maybe someone else > can > > > share some light on this? > > > > > > > > AFAIK you can (I've done several ASF releases and my key is signed > by > > > > nobody) - its nice to have but not required and the release signing > > > > FAQ doesn't say its required: > > > > http://www.apache.org/dev/release-signing.html#web-of-trust > > > > > > Same view here. Key-signing's not a blocker. > > > > > > Hen > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Regards, Petar! > > Karlovo, Bulgaria. > > > > EOOXML objections > > http://www.grokdoc.net/index.php/EOOXML_objections > > > > Public PGP Key at: > > http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9 > > Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Regards, Petar! Karlovo, Bulgaria. EOOXML objections http://www.grokdoc.net/index.php/EOOXML_objections Public PGP Key at: http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
