Re: Cactus Release Archives
OK, here is the deal.The Cactus framework is, indeed, targeted to the Java 1.4. I changed the dependency to servlet-api, version 1.4. If you want to build the cactus site, then you first execute mvn jxr:jxr mvn javadoc:javadoc (this will place the javadoc and the Xref for the whole project and will place them in cactus-site/src/resource). After that you go to cactus-site and execute: mvn site:site which will generate the Cactus site. I removed the *.dtd because they are not needed any more, since Cactus relies on the Cargo project and the same files are included in the Cargo project. I have also included the Cargo jars with the Cactus distribution and have changed the L N files. On Wed, Apr 2, 2008 at 6:02 AM, sebb [EMAIL PROTECTED] wrote: Just tried mvn site:site on Java 1.4 and it complained that servlet-api-2.5.jar is Java 1.5 rather than 1.4 I thought Cactus was targetted at Java 1.4? I tried with servlet-api-2.4 and it seemed to work OK using Java 1.4. Also, with regard to the DTDs I mentioned before - they don't seem to be present in the binary archive, only the source. I tried a build without them and did not notice any problems, so perhaps they could be removed? This would avoid having to sort out the licenses. == I've been having problems trying to regenerate the binary jar - it does not seem to contain all the required files, probably because I've not created everything. What Maven targets do I need to run apart from assembly:assembly? On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: The only difference is the portlet dependency which I put there by mistake. Now this dependency is removed and the archives are placed on the web-page. I have also added the KEYS file in the Subversion and the archives. Cheers, Petar. On Wed, Apr 2, 2008 at 1:19 AM, sebb [EMAIL PROTECTED] wrote: The copy of pom.xml in the source archive is not the same as the one in SVN - why is this? On 01/04/2008, sebb [EMAIL PROTECTED] wrote: On 01/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi sebb, I changed the assembly-bin and committed it in the trunk. Now the binary archives are built correctly. I checked the source ones - they seem fine. For building the archives I use: mvn assembly:assembly -N at the top level. I still have no idea of the KEYS file. Can you tell me where it is? There's one linked from the downloads page for the previous releases. There should perhaps be a copy in SVN. Thanks. P.S. I have, again, uploaded the archives here: http://people.apache.org/dist/jakarta/cactus/1.8.0/ On Tue, Apr 1, 2008 at 10:37 PM, sebb [EMAIL PROTECTED] wrote: As you may have seen, I have update the LN files to simplify them - there's no need to mention other ASF projects. I think we are getting closer, however there are some DTD files that may need to be replaced and/or credited in the NOTICE file, as they are not ASF licensed. I'll investigate further and report back. As to the updated archives - there is a problem with at least the binary zip file - it contains two copies of the apidocs directory structure. What Maven commands are you using? S On 01/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, I have removed the xref from both the bin and src archives. I have removed the javadoc from the src archives. I have also described the additional licenses in the LICENSE and NOTICE files. The MANIFEST.MF file will stay in the SVN until the assembly plugin could accept manifestEntries (hopefully beta-3). For all the artifacts I produce the Manifest file with maven. I have no idea where the KEYS file is, and when I find it I will place my key there. If the archives seem OK, I will cast a vote on them. How do you find them? On Tue, Apr 1, 2008 at 5:17 AM, sebb [EMAIL PROTECTED] wrote: On 01/04/2008, sebb [EMAIL PROTECTED] wrote: On 31/03/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, sorry for bringing this so long but this is my first time I am making a release and as you see I am not so confident. I have uploaded the new archives here:
Re: Cactus Release Archives
On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, here is the deal.The Cactus framework is, indeed, targeted to the Java 1.4. I changed the dependency to servlet-api, version 1.4. If you want to build the cactus site, then you first execute mvn jxr:jxr mvn javadoc:javadoc (this will place the javadoc and the Xref for the whole project and will place them in cactus-site/src/resource). After that you go to cactus-site and execute: mvn site:site which will generate the Cactus site. I think this needs to be described in a file, as it's non-standard. BTW, the README file refers to http://jakarta.apache.org/cactus/participating/howto_build.html but that is not entirely accurate as some of the dependencies have changed. And the target clean:install should surely be two targets clean install? Also, there's no Ant build file as far as I can tell. This should make the description much simpler, as the dependency details can be removed. But the Maven goals do need to be listed for the tasks of: - building the jars - testing the build - building the site - building the archives I removed the *.dtd because they are not needed any more, since Cactus relies on the Cargo project and the same files are included in the Cargo project. I have also included the Cargo jars with the Cactus distribution and have changed the L N files. I've not seen any updates to the LN files. On Wed, Apr 2, 2008 at 6:02 AM, sebb [EMAIL PROTECTED] wrote: Just tried mvn site:site on Java 1.4 and it complained that servlet-api-2.5.jar is Java 1.5 rather than 1.4 I thought Cactus was targetted at Java 1.4? I tried with servlet-api-2.4 and it seemed to work OK using Java 1.4. Also, with regard to the DTDs I mentioned before - they don't seem to be present in the binary archive, only the source. I tried a build without them and did not notice any problems, so perhaps they could be removed? This would avoid having to sort out the licenses. == I've been having problems trying to regenerate the binary jar - it does not seem to contain all the required files, probably because I've not created everything. What Maven targets do I need to run apart from assembly:assembly? On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: The only difference is the portlet dependency which I put there by mistake. Now this dependency is removed and the archives are placed on the web-page. I have also added the KEYS file in the Subversion and the archives. Cheers, Petar. On Wed, Apr 2, 2008 at 1:19 AM, sebb [EMAIL PROTECTED] wrote: The copy of pom.xml in the source archive is not the same as the one in SVN - why is this? On 01/04/2008, sebb [EMAIL PROTECTED] wrote: On 01/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi sebb, I changed the assembly-bin and committed it in the trunk. Now the binary archives are built correctly. I checked the source ones - they seem fine. For building the archives I use: mvn assembly:assembly -N at the top level. I still have no idea of the KEYS file. Can you tell me where it is? There's one linked from the downloads page for the previous releases. There should perhaps be a copy in SVN. Thanks. P.S. I have, again, uploaded the archives here: http://people.apache.org/dist/jakarta/cactus/1.8.0/ On Tue, Apr 1, 2008 at 10:37 PM, sebb [EMAIL PROTECTED] wrote: As you may have seen, I have update the LN files to simplify them - there's no need to mention other ASF projects. I think we are getting closer, however there are some DTD files that may need to be replaced and/or credited in the NOTICE file, as they are not ASF licensed. I'll investigate further and report back. As to the updated archives - there is a problem with at least the binary zip file - it contains two copies of the apidocs directory structure. What Maven commands are you using? S On 01/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, I have removed the xref from both the bin and src archives. I have removed the javadoc from the src archives. I have also described the additional licenses in the LICENSE and NOTICE files. The MANIFEST.MF file will stay in the SVN until the assembly plugin could
Re: Cactus Release Archives
Tried mvn site from cactus-site, and it complains: Missing: -- 1) org.apache.maven.doxia:doxia-decoration-model:jar:2.4.1 Is there an additional repository that needs to be included in the pom? On 02/04/2008, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, here is the deal.The Cactus framework is, indeed, targeted to the Java 1.4. I changed the dependency to servlet-api, version 1.4. If you want to build the cactus site, then you first execute mvn jxr:jxr mvn javadoc:javadoc (this will place the javadoc and the Xref for the whole project and will place them in cactus-site/src/resource). After that you go to cactus-site and execute: mvn site:site which will generate the Cactus site. I think this needs to be described in a file, as it's non-standard. BTW, the README file refers to http://jakarta.apache.org/cactus/participating/howto_build.html but that is not entirely accurate as some of the dependencies have changed. And the target clean:install should surely be two targets clean install? Also, there's no Ant build file as far as I can tell. This should make the description much simpler, as the dependency details can be removed. But the Maven goals do need to be listed for the tasks of: - building the jars - testing the build - building the site - building the archives I removed the *.dtd because they are not needed any more, since Cactus relies on the Cargo project and the same files are included in the Cargo project. I have also included the Cargo jars with the Cactus distribution and have changed the L N files. I've not seen any updates to the LN files. On Wed, Apr 2, 2008 at 6:02 AM, sebb [EMAIL PROTECTED] wrote: Just tried mvn site:site on Java 1.4 and it complained that servlet-api-2.5.jar is Java 1.5 rather than 1.4 I thought Cactus was targetted at Java 1.4? I tried with servlet-api-2.4 and it seemed to work OK using Java 1.4. Also, with regard to the DTDs I mentioned before - they don't seem to be present in the binary archive, only the source. I tried a build without them and did not notice any problems, so perhaps they could be removed? This would avoid having to sort out the licenses. == I've been having problems trying to regenerate the binary jar - it does not seem to contain all the required files, probably because I've not created everything. What Maven targets do I need to run apart from assembly:assembly? On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: The only difference is the portlet dependency which I put there by mistake. Now this dependency is removed and the archives are placed on the web-page. I have also added the KEYS file in the Subversion and the archives. Cheers, Petar. On Wed, Apr 2, 2008 at 1:19 AM, sebb [EMAIL PROTECTED] wrote: The copy of pom.xml in the source archive is not the same as the one in SVN - why is this? On 01/04/2008, sebb [EMAIL PROTECTED] wrote: On 01/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi sebb, I changed the assembly-bin and committed it in the trunk. Now the binary archives are built correctly. I checked the source ones - they seem fine. For building the archives I use: mvn assembly:assembly -N at the top level. I still have no idea of the KEYS file. Can you tell me where it is? There's one linked from the downloads page for the previous releases. There should perhaps be a copy in SVN. Thanks. P.S. I have, again, uploaded the archives here: http://people.apache.org/dist/jakarta/cactus/1.8.0/ On Tue, Apr 1, 2008 at 10:37 PM, sebb [EMAIL PROTECTED] wrote: As you may have seen, I have update the LN files to simplify them - there's no need to mention other ASF projects. I think we are getting closer, however there are some DTD files that may need to be replaced and/or credited in the NOTICE file, as they are not ASF licensed. I'll investigate further and report back. As to the updated archives - there is a problem with at least the binary zip file - it contains two copies of the apidocs directory structure. What Maven commands are
Cactus Release Archives(2)
I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus Release Archives(2)
OK, about the doxia-problem. It is very strange. I see that too, but I suppose it is a bug in Maven, because the mvn site:site works as a charm. I will have to investigate that further. On Wed, Apr 2, 2008 at 3:47 PM, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9 -- 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus Release Archives(2)
On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. That's not what I meant - the LN files don't need to contain references to other ASF projects, but they should credit external projects even if the license is AL 2.0 I've updated the LN. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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]
Re: Cactus Release Archives(2)
On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, about the doxia-problem. It is very strange. I see that too, but I suppose it is a bug in Maven, because the mvn site:site works as a charm. Yes, for me too. I will have to investigate that further. No need - unless you want to - just update the docs to say one needs site:site. On Wed, Apr 2, 2008 at 3:47 PM, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9 -- 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=getsearch=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]
Re: Cactus Release Archives(2)
On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ The downloads page: http://jakarta.apache.org/cactus/1.8.0/downloads.html says that the core distribution is distributed in separate archives for J2EE1.2 and J2EE1.3 - however that does not seem to be the case. The page http://jakarta.apache.org/cactus/1.8.0/changes-report.html needs to show more recent changes, or it could perhaps be dropped. It would be useful to have some additional reports, e.g. Javadocs Source Xref Clirr? http://jakarta.apache.org/cactus/1.8.0/getting_started.html says that it requires Java 1.2+. This should be 1.4+. The list of jars also looks wrong. I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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]
Re: Cactus Release Archives(2)
On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Actually the cactus provides different implementations for the different JVMs. My purpose is to make available for download only the JVM 1.4 version in the binary archive. If one needs an older version one can get it from the Maven repository, where I will place all of the archetypes. I have committed changes on the downloads page. The changes.xml is a bit old, and I plan to update it. One option is to generate it automatically from the JIRA, but I will decide this later. I want to check that the archives are OK and propose them for a vote and after that I will deal with the site. The site is usually part of the vote. The Xref and Javadoc reports are in the Resources menu: http://jakarta.apache.org/cactus/1.8.0/resources/index.html OK, did not spot them there. Most other Maven sites seem to have them under Reports - perhaps they could be copied/moved there? On Wed, Apr 2, 2008 at 5:00 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ The downloads page: http://jakarta.apache.org/cactus/1.8.0/downloads.html says that the core distribution is distributed in separate archives for J2EE1.2 and J2EE1.3 - however that does not seem to be the case. The page http://jakarta.apache.org/cactus/1.8.0/changes-report.html needs to show more recent changes, or it could perhaps be dropped. It would be useful to have some additional reports, e.g. Javadocs Source Xref Clirr? http://jakarta.apache.org/cactus/1.8.0/getting_started.html says that it requires Java 1.2+. This should be 1.4+. The list of jars also looks wrong. I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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=getsearch=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]
Re: Cactus Release Archives(2)
Actually the cactus provides different implementations for the different JVMs. My purpose is to make available for download only the JVM 1.4 version in the binary archive. If one needs an older version one can get it from the Maven repository, where I will place all of the archetypes. I have committed changes on the downloads page. The changes.xml is a bit old, and I plan to update it. One option is to generate it automatically from the JIRA, but I will decide this later. I want to check that the archives are OK and propose them for a vote and after that I will deal with the site. The Xref and Javadoc reports are in the Resources menu: http://jakarta.apache.org/cactus/1.8.0/resources/index.html On Wed, Apr 2, 2008 at 5:00 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ The downloads page: http://jakarta.apache.org/cactus/1.8.0/downloads.html says that the core distribution is distributed in separate archives for J2EE1.2 and J2EE1.3 - however that does not seem to be the case. The page http://jakarta.apache.org/cactus/1.8.0/changes-report.html needs to show more recent changes, or it could perhaps be dropped. It would be useful to have some additional reports, e.g. Javadocs Source Xref Clirr? http://jakarta.apache.org/cactus/1.8.0/getting_started.html says that it requires Java 1.2+. This should be 1.4+. The list of jars also looks wrong. I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus Release Archives(2)
On Wed, Apr 2, 2008 at 3:29 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Actually the cactus provides different implementations for the different JVMs. My purpose is to make available for download only the JVM 1.4 version in the binary archive. If one needs an older version one can get it from the Maven repository, where I will place all of the archetypes. I have committed changes on the downloads page. The changes.xml is a bit old, and I plan to update it. One option is to generate it automatically from the JIRA, but I will decide this later. I want to check that the archives are OK and propose them for a vote and after that I will deal with the site. The site is usually part of the vote. I disagree, unless its included in the release artifacts - the vote should be only on the release artifacts. Niall The Xref and Javadoc reports are in the Resources menu: http://jakarta.apache.org/cactus/1.8.0/resources/index.html OK, did not spot them there. Most other Maven sites seem to have them under Reports - perhaps they could be copied/moved there? On Wed, Apr 2, 2008 at 5:00 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ The downloads page: http://jakarta.apache.org/cactus/1.8.0/downloads.html says that the core distribution is distributed in separate archives for J2EE1.2 and J2EE1.3 - however that does not seem to be the case. The page http://jakarta.apache.org/cactus/1.8.0/changes-report.html needs to show more recent changes, or it could perhaps be dropped. It would be useful to have some additional reports, e.g. Javadocs Source Xref Clirr? http://jakarta.apache.org/cactus/1.8.0/getting_started.html says that it requires Java 1.2+. This should be 1.4+. The list of jars also looks wrong. I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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=getsearch=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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cactus Release Archives(2)
It is included in the artifacts :-( On Wed, Apr 2, 2008 at 5:33 PM, Niall Pemberton [EMAIL PROTECTED] wrote: On Wed, Apr 2, 2008 at 3:29 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Actually the cactus provides different implementations for the different JVMs. My purpose is to make available for download only the JVM 1.4 version in the binary archive. If one needs an older version one can get it from the Maven repository, where I will place all of the archetypes. I have committed changes on the downloads page. The changes.xml is a bit old, and I plan to update it. One option is to generate it automatically from the JIRA, but I will decide this later. I want to check that the archives are OK and propose them for a vote and after that I will deal with the site. The site is usually part of the vote. I disagree, unless its included in the release artifacts - the vote should be only on the release artifacts. Niall The Xref and Javadoc reports are in the Resources menu: http://jakarta.apache.org/cactus/1.8.0/resources/index.html OK, did not spot them there. Most other Maven sites seem to have them under Reports - perhaps they could be copied/moved there? On Wed, Apr 2, 2008 at 5:00 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ The downloads page: http://jakarta.apache.org/cactus/1.8.0/downloads.html says that the core distribution is distributed in separate archives for J2EE1.2 and J2EE1.3 - however that does not seem to be the case. The page http://jakarta.apache.org/cactus/1.8.0/changes-report.html needs to show more recent changes, or it could perhaps be dropped. It would be useful to have some additional reports, e.g. Javadocs Source Xref Clirr? http://jakarta.apache.org/cactus/1.8.0/getting_started.html says that it requires Java 1.2+. This should be 1.4+. The list of jars also looks wrong. I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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=getsearch=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] - 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus Release Archives(2)
I have just committed the changes plugin to generate the JIRA report, too. On Wed, Apr 2, 2008 at 5:34 PM, Petar Tahchiev [EMAIL PROTECTED] wrote: It is included in the artifacts :-( On Wed, Apr 2, 2008 at 5:33 PM, Niall Pemberton [EMAIL PROTECTED] wrote: On Wed, Apr 2, 2008 at 3:29 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Actually the cactus provides different implementations for the different JVMs. My purpose is to make available for download only the JVM 1.4 version in the binary archive. If one needs an older version one can get it from the Maven repository, where I will place all of the archetypes. I have committed changes on the downloads page. The changes.xml is a bit old, and I plan to update it. One option is to generate it automatically from the JIRA, but I will decide this later. I want to check that the archives are OK and propose them for a vote and after that I will deal with the site. The site is usually part of the vote. I disagree, unless its included in the release artifacts - the vote should be only on the release artifacts. Niall The Xref and Javadoc reports are in the Resources menu: http://jakarta.apache.org/cactus/1.8.0/resources/index.html OK, did not spot them there. Most other Maven sites seem to have them under Reports - perhaps they could be copied/moved there? On Wed, Apr 2, 2008 at 5:00 PM, sebb [EMAIL PROTECTED] wrote: On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I am starting a new thread, because we exceeded the limit from the Mailer-daemon. The building of the web-site is described here: http://wiki.apache.org/jakarta-cactus/DeployingCactusWebSite and I also committed some explanation in the howto_build.xml. I also added a section on how to produce the archives with the assembly plugin. The new web-site is deployed (as a temporary web-site) here: http://jakarta.apache.org/cactus/1.8.0/ The downloads page: http://jakarta.apache.org/cactus/1.8.0/downloads.html says that the core distribution is distributed in separate archives for J2EE1.2 and J2EE1.3 - however that does not seem to be the case. The page http://jakarta.apache.org/cactus/1.8.0/changes-report.html needs to show more recent changes, or it could perhaps be dropped. It would be useful to have some additional reports, e.g. Javadocs Source Xref Clirr? http://jakarta.apache.org/cactus/1.8.0/getting_started.html says that it requires Java 1.2+. This should be 1.4+. The list of jars also looks wrong. I am planning to upload it as an official web-site if the vote for the release succeeds. Actually th LN needed no change, since the Cargo project is licensed under the Apache License and we agreed that the LN files will not contain the Apache licensed dependencies. I have updated the README to contain the Cargo dependency. -- 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=getsearch=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=getsearch=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] - 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9 -- Regards, Petar! Karlovo, Bulgaria. EOOXML objections http://www.grokdoc.net/index.php/EOOXML_objections
Cactus scratchpad tree
Is the scratchpad tree under trunk still needed? If it's intended for experimentation, perhaps it should be moved to a branch instead. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cactus scratchpad tree
When I started my work on Cactus the scratchpad was already there. I think that nobody works in there right now, and almost everything in the scratchpad is done by Vincent Massol. I prefer we move it in a separate branch, too. Cheers, Petar. On Wed, Apr 2, 2008 at 6:03 PM, sebb [EMAIL PROTECTED] wrote: Is the scratchpad tree under trunk still needed? If it's intended for experimentation, perhaps it should be moved to a branch instead. - 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus scratchpad tree
OK, I just moved it as a separate branch. On Wed, Apr 2, 2008 at 6:07 PM, Petar Tahchiev [EMAIL PROTECTED] wrote: When I started my work on Cactus the scratchpad was already there. I think that nobody works in there right now, and almost everything in the scratchpad is done by Vincent Massol. I prefer we move it in a separate branch, too. Cheers, Petar. On Wed, Apr 2, 2008 at 6:03 PM, sebb [EMAIL PROTECTED] wrote: Is the scratchpad tree under trunk still needed? If it's intended for experimentation, perhaps it should be moved to a branch instead. - 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9 -- 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus scratchpad tree
I'm just checking through a few remaining files that contain text, but don't yet have the eol-style set. The file cactus-site/src/site/xdoc/original/Sequence.dfSequence appears to be source - is the line ending important? Another file is: integration/eclipse/org.apache.cactus.eclipse.webapp/src/main/java/org/apache/cactus/eclipse/webapp/internal/ui/WebAppConfigurationBlock.orig It appears to be a copy of the .java file - is it still needed? On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: When I started my work on Cactus the scratchpad was already there. I think that nobody works in there right now, and almost everything in the scratchpad is done by Vincent Massol. I prefer we move it in a separate branch, too. Cheers, Petar. On Wed, Apr 2, 2008 at 6:03 PM, sebb [EMAIL PROTECTED] wrote: Is the scratchpad tree under trunk still needed? If it's intended for experimentation, perhaps it should be moved to a branch instead. - 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=getsearch=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]
Cactus - missing ?xml headers in xml files
There seem to be a few xml files that don't start with the ?xml version=1.0 ...? header line. These are otherwise apparently valid xml files. Is that intentional, or should the missing lines be added? I can add them, but I don't want to mess anything up... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cactus - missing ?xml headers in xml files
I think that all xml files should start with the xml header. Can you add it, please? On Wed, Apr 2, 2008 at 7:53 PM, sebb [EMAIL PROTECTED] wrote: There seem to be a few xml files that don't start with the ?xml version=1.0 ...? header line. These are otherwise apparently valid xml files. Is that intentional, or should the missing lines be added? I can add them, but I don't want to mess anything up... - 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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus RAT report - where to add plugin in pom.xml?
OK, done On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: In my opinion the rat plugin should be specified in the build section. On Wed, Apr 2, 2008 at 7:49 PM, sebb [EMAIL PROTECTED] wrote: The RAT report does not seem to be found if I run mvn rat:check This seems to be because its plugin is under pluginManagement rather than under build, as it works when I moved it there. But I don't know much about Maven, so maybe it needs to be in both? If so, does the config need to be in both? Can anyone advise? Once it's in the correct place(s), there are some exceptions that need to be added, e.g. MANIFEST.MF. I can add those. - 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=getsearch=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]
Re: Cactus - missing ?xml headers in xml files
OK done - apart from two very small jboss-web.xml files. On 02/04/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I think that all xml files should start with the xml header. Can you add it, please? On Wed, Apr 2, 2008 at 7:53 PM, sebb [EMAIL PROTECTED] wrote: There seem to be a few xml files that don't start with the ?xml version=1.0 ...? header line. These are otherwise apparently valid xml files. Is that intentional, or should the missing lines be added? I can add them, but I don't want to mess anything up... - 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=getsearch=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]
Re: Cactus RAT report - where to add plugin in pom.xml?
sebb wrote: The RAT report does not seem to be found if I run mvn rat:check This seems to be because its plugin is under pluginManagement rather than under build, as it works when I moved it there. But I don't know much about Maven, so maybe it needs to be in both? If so, does the config need to be in both? Can anyone advise? http://mojo.codehaus.org/rat-maven-plugin/usage.html Once it's in the correct place(s), there are some exceptions that need to be added, e.g. MANIFEST.MF. I can add those. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cactus RAT report - where to add plugin in pom.xml?
On 02/04/2008, Dennis Lundberg [EMAIL PROTECTED] wrote: sebb wrote: The RAT report does not seem to be found if I run mvn rat:check This seems to be because its plugin is under pluginManagement rather than under build, as it works when I moved it there. But I don't know much about Maven, so maybe it needs to be in both? If so, does the config need to be in both? Can anyone advise? http://mojo.codehaus.org/rat-maven-plugin/usage.html Thanks, already done. Does the plugin also need to be mentioned in dependencyManagement? BTW, why is it rat-maven-plugin and not maven-rat-plugin like most of the others seem to be? [The only other one I've seen with maven-middle-position is jdepend] Once it's in the correct place(s), there are some exceptions that need to be added, e.g. MANIFEST.MF. I can add those. -- Dennis Lundberg - 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]
RE: Cactus RAT report - where to add plugin in pom.xml?
Please unsubscribe me from this list - I have tried twice - still getting emails. Thank you! -Original Message- From: sebb [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 02, 2008 12:49 PM To: Jakarta General List Subject: Cactus RAT report - where to add plugin in pom.xml? The RAT report does not seem to be found if I run mvn rat:check This seems to be because its plugin is under pluginManagement rather than under build, as it works when I moved it there. But I don't know much about Maven, so maybe it needs to be in both? If so, does the config need to be in both? Can anyone advise? Once it's in the correct place(s), there are some exceptions that need to be added, e.g. MANIFEST.MF. I can add those. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
