[VOTE] Release Cactus 1.8.1 (Third attempt)
Hi guys, here is another attempt to release Cactus 1.8.1 As promised I made a new tag: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc3/ and the artifacts: http://people.apache.org/~ptahchiev/1.8.1-rc3/ Please cast you vote. Here is mine: +1 The vote is open 72 hrs. Thanks -- 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: [VOTE] Release Jakarta Cactus 1.8.1
Hi guys, can you tell me how to reproduce this behaviour - I am really clueless. I have no idea what triggeres it and I cannot see it locally on my machine. This way I cannot work on fixing it. Thanks, Petar. On Wed, Jan 21, 2009 at 8:41 AM, Henri Yandell bay...@generationjava.comwrote: Yep - turning off my local JIRA got me passed that problem and now I get the same set of errors as Seb. Hen On Tue, Jan 20, 2009 at 2:11 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Actually Hentry's problem was that he had something alreadty running on port 8080. But you are right. We check if the property is set :-( Ok, I will try to investigate further. On Wed, Jan 21, 2009 at 12:06 AM, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi guys, I think I found the problem, but since I cannot reproduce this behaviour I am clueless if this will work. I think the problem is here: http://jira.codehaus.org/browse/SUREFIRE-98 The issue relates to not finding a property - however the code already does a separate check to see if the property has been retrieved OK, so I don't think it applies here. I changed the version of the Surefire plugin we use to the latest one. I have commited it. Anything else before I make the RC-3 and cast the vote? Probably best if Henri could provide more info on the failure he saw, which I think was different from mine. I'm also intending to try a test on Unix. I suggest waiting a bit. Thanks again, Petar. On Tue, Jan 20, 2009 at 10:51 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi Sebb, I removed the CDDL license and described the servlet-api as an Apache 2.0 licensed. I also added the Apache license headers. I also changed the version of AspectJ we are using. About the test failures that you mention I think they are different from what Henry is getting. Anyways I am unable to reproduce them :-( What should I do? Do I need to make a RC-3 and call the vote on it? Thanks for the tips guys. On Tue, Jan 20, 2009 at 9:42 PM, sebb seb...@gmail.com wrote: On 20/01/2009, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi all, maybe I am too impatient, but has anybody tried the artifacts? 1 minor problem - the .asc files should be detached ascii signatures, not signed archives. No need to recreate the RC, just recreate the .asc files. We don't normally provide binary .sig files - they can be deleted. I'm still looking at other aspects of the RC. The servlet-api-2.4.jar file is an Apache version, as Henri already mentioned. The cddl licence should be deleted, and the README updated. Like Henri, I also get test failures: [surefire] Tests run: 5, Failures: 3, Errors: 0, Time elapsed: 0.25 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWarArchive [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXml [surefire] Tests run: 54, Failures: 0, Errors: 0, Time elapsed: 2.359 sec [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXmlVersion [surefire] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.093 sec [surefire] Running org.apache.cactus.integration.ant.TestCactifyEarTask [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactifyWarTask [surefire] Tests run: 21, Failures: 21, Errors: 0, Time elapsed: 0.281 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.078 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTestTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.094 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestRunServerTestsTask [surefire] Tests run: 6, Failures: 6, Errors: 0, Time elapsed: 0.078 sec FAILURE !! I ran mvn test, which failed when it could not find the cactus jars. It would be better if this worked without needing to do mvn install first. I then ran mvn install and got the errors shown above. It looks like these are all caused by junit.framework.AssertionFailedError: The system property 'testinput.dir' must point to an existing directory at junit.framework.Assert.fail
Re: [VOTE] Release Jakarta Cactus 1.8.1
Hi Henry,
I followed your instructions and luckily was able to reproduce the
behaviour.
What I did was:
unzip rc-1
mvn clean install - Did not fail;
change the localrepostiry to~/.m2/repository1
rm -rf rc1
unzip rc-1
mvn clean install - FAILED
Next steps:
exactly the same, but against the trunk. In the trunk we print the
testinput.dir property.
I was not amazed that the testinput.dir was printed to be.src/test-input.
What amazed me was the value of testInputDir.getAbsolutePath()
It was
/home/peter/bin/workspace/cactus-1.8.1-rc1-src/src/test-input
The problem was that my test-input should reside in
/home/peter/bin/workspace/cactus-1.8.1-rc1-src/integration/ant/src/test-input
You see somehow Maven misinterpretes the ${basedir} and
suggests it to be the root of the project, instead of /root/integration/ant/
I thought that this might be connected with the issue I told sebb about:
http://jira.codehaus.org/browse/SUREFIRE-98
and since this issue is resolved I updated to the latest version of the
surefire plugin
and tested again. This time it all worked for me.
So now I think that it is all fine.
In trunk I have committed to use the latest version of
surefire plugin.
Can you retest the trunk and let me know the result.
Thanks, Petar.
On Wed, Jan 21, 2009 at 7:41 PM, Henri Yandell bay...@generationjava.comwrote:
On Wed, Jan 21, 2009 at 3:41 AM, sebb seb...@gmail.com wrote:
On 21/01/2009, Henri Yandell bay...@generationjava.com wrote:
Yep - turning off my local JIRA got me passed that problem and now I
get the same set of errors as Seb.
Does this always happen for you?
If so, what is the path it is trying to find?
This would require testing against trunk...
Tried this morning - but against the rc1 (sorry). Will try against
trunk later (vacation right now and various parenting tasks I have to
do).
mvn clean install at top level: Failed
mvn clean install in integration/ant: Passed
mvn clean install in integration: Passed
mvn clean install at top level: Passed
rm -fr cactus-src
unzip
mvn clean install at top level: Passed
mv m2 repo to bckp
mvn clean install at top level: Failed
mvn clean install at top level: Passed
Error in integration/ant failure:
junit.framework.AssertionFailedError: The system property
'testinput.dir' must point to an existing directory
Hen
-
To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
--
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: [VOTE] Release Jakarta Cactus 1.8.1
OK I will now prepare a RC3
On Thu, Jan 22, 2009 at 12:33 AM, Henri Yandell
bay...@generationjava.comwrote:
That worked for me - trunk is happy :)
Thanks,
Hen
On Wed, Jan 21, 2009 at 1:24 PM, Petar Tahchiev
paranoiabla.li...@gmail.com wrote:
Hi Henry,
I followed your instructions and luckily was able to reproduce the
behaviour.
What I did was:
unzip rc-1
mvn clean install - Did not fail;
change the localrepostiry to~/.m2/repository1
rm -rf rc1
unzip rc-1
mvn clean install - FAILED
Next steps:
exactly the same, but against the trunk. In the trunk we print the
testinput.dir property.
I was not amazed that the testinput.dir was printed to be.src/test-input.
What amazed me was the value of testInputDir.getAbsolutePath()
It was
/home/peter/bin/workspace/cactus-1.8.1-rc1-src/src/test-input
The problem was that my test-input should reside in
/home/peter/bin/workspace/cactus-1.8.1-rc1-src/integration/ant/src/test-input
You see somehow Maven misinterpretes the ${basedir} and
suggests it to be the root of the project, instead of
/root/integration/ant/
I thought that this might be connected with the issue I told sebb about:
http://jira.codehaus.org/browse/SUREFIRE-98
and since this issue is resolved I updated to the latest version of the
surefire plugin
and tested again. This time it all worked for me.
So now I think that it is all fine.
In trunk I have committed to use the latest version of
surefire plugin.
Can you retest the trunk and let me know the result.
Thanks, Petar.
On Wed, Jan 21, 2009 at 7:41 PM, Henri Yandell
bay...@generationjava.comwrote:
On Wed, Jan 21, 2009 at 3:41 AM, sebb seb...@gmail.com wrote:
On 21/01/2009, Henri Yandell bay...@generationjava.com wrote:
Yep - turning off my local JIRA got me passed that problem and now I
get the same set of errors as Seb.
Does this always happen for you?
If so, what is the path it is trying to find?
This would require testing against trunk...
Tried this morning - but against the rc1 (sorry). Will try against
trunk later (vacation right now and various parenting tasks I have to
do).
mvn clean install at top level: Failed
mvn clean install in integration/ant: Passed
mvn clean install in integration: Passed
mvn clean install at top level: Passed
rm -fr cactus-src
unzip
mvn clean install at top level: Passed
mv m2 repo to bckp
mvn clean install at top level: Failed
mvn clean install at top level: Passed
Error in integration/ant failure:
junit.framework.AssertionFailedError: The system property
'testinput.dir' must point to an existing directory
Hen
-
To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
--
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: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
--
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: [VOTE] Release Jakarta Cactus 1.8.1
They need to be there for the maven1 plugin.
On Thu, Jan 22, 2009 at 12:46 AM, sebb seb...@gmail.com wrote:
What about the other comments I made?
i.e. maven.xml and project.xml files? Are these useful or obsolete?
On 21/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote:
OK I will now prepare a RC3
On Thu, Jan 22, 2009 at 12:33 AM, Henri Yandell
bay...@generationjava.comwrote:
That worked for me - trunk is happy :)
Thanks,
Hen
On Wed, Jan 21, 2009 at 1:24 PM, Petar Tahchiev
paranoiabla.li...@gmail.com wrote:
Hi Henry,
I followed your instructions and luckily was able to reproduce the
behaviour.
What I did was:
unzip rc-1
mvn clean install - Did not fail;
change the localrepostiry to~/.m2/repository1
rm -rf rc1
unzip rc-1
mvn clean install - FAILED
Next steps:
exactly the same, but against the trunk. In the trunk we print the
testinput.dir property.
I was not amazed that the testinput.dir was printed to
be.src/test-input.
What amazed me was the value of testInputDir.getAbsolutePath()
It was
/home/peter/bin/workspace/cactus-1.8.1-rc1-src/src/test-input
The problem was that my test-input should reside in
/home/peter/bin/workspace/cactus-1.8.1-rc1-src/integration/ant/src/test-input
You see somehow Maven misinterpretes the ${basedir} and
suggests it to be the root of the project, instead of
/root/integration/ant/
I thought that this might be connected with the issue I told sebb
about:
http://jira.codehaus.org/browse/SUREFIRE-98
and since this issue is resolved I updated to the latest version of
the
surefire plugin
and tested again. This time it all worked for me.
So now I think that it is all fine.
In trunk I have committed to use the latest version of
surefire plugin.
Can you retest the trunk and let me know the result.
Thanks, Petar.
On Wed, Jan 21, 2009 at 7:41 PM, Henri Yandell
bay...@generationjava.comwrote:
On Wed, Jan 21, 2009 at 3:41 AM, sebb seb...@gmail.com wrote:
On 21/01/2009, Henri Yandell bay...@generationjava.com wrote:
Yep - turning off my local JIRA got me passed that problem and
now I
get the same set of errors as Seb.
Does this always happen for you?
If so, what is the path it is trying to find?
This would require testing against trunk...
Tried this morning - but against the rc1 (sorry). Will try against
trunk later (vacation right now and various parenting tasks I have
to
do).
mvn clean install at top level: Failed
mvn clean install in integration/ant: Passed
mvn clean install in integration: Passed
mvn clean install at top level: Passed
rm -fr cactus-src
unzip
mvn clean install at top level: Passed
mv m2 repo to bckp
mvn clean install at top level: Failed
mvn clean install at top level: Passed
Error in integration/ant failure:
junit.framework.AssertionFailedError: The system property
'testinput.dir' must point to an existing directory
Hen
-
To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
--
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: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
--
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: general-unsubscr...@jakarta.apache.org
For additional commands, e-mail: general-h...@jakarta.apache.org
--
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: [VOTE] Release 1.8.1 of Cactus
Hi Henry, unfortunately I am unable to reproduce this behaviour. :-( I run mvn clean install in the source unpacked directory and everything goes smooth. Can you tell me what is the error in the test-logs? Or maybe try to run it again? Or even try the rc2, which is here: http://people.apache.org/~ptahchiev/1.8.1-rc2/http://people.apache.org/%7Eptahchiev/1.8.1-rc2/ Thanks, Petar On Tue, Jan 20, 2009 at 2:58 AM, Henri Yandell bay...@generationjava.comwrote: I ran 'mvn clean install' in the source unpacked directory: --- T E S T S --- Running org.apache.cactus.extension.jetty.TestJettyTestSetup log4j:WARN No appenders could be found for logger (org.apache.cactus.internal.util.ClassLoaderUtils). log4j:WARN Please initialize the log4j system properly. Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 5.05 sec FAILURE! Running org.apache.cactus.TestAll Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Results : Tests in error: testSetUpWhenServerNotAlreadyStarted(org.apache.cactus.extension.jetty.TestJettyTestSetup) testSetUpWhenServerIsAlreadyStarted(org.apache.cactus.extension.jetty.TestJettyTestSetup) Hen On Sun, Jan 18, 2009 at 1:05 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hello guys, It's been more than 10 months since I released Cactus version 1.8.0, and not I am trying to push the 1.8.1 release. I have closed some issues in the JIRA, added a maven2 plugin for Cactus and included a sample EJB3 application, as a reference how to test EJB3. Here is the tag code-base: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc1/ And here are the archives: http://people.apache.org/~ptahchiev/1.8.1-rc1/http://people.apache.org/%7Eptahchiev/1.8.1-rc1/ http://people.apache.org/%7Eptahchiev/1.8.1-rc1/ Please test and cast your vote. [+1]Go man, go! 0] I don't care. [-1] I am against it, because ... Here is mine: +1 Thanks, Petar. -- 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: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org -- 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: [VOTE] Release Jakarta Cactus 1.8.1
Hi all, maybe I am too impatient, but has anybody tried the artifacts? What is your opinion expressed by any of the three numbers :-). On Mon, Jan 19, 2009 at 10:33 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi guys, here comes the second attempt for releasing cactus-1.8.1. The artifacts, hashes and signatures are here: http://people.apache.org/~ptahchiev/1.8.1-rc2/http://people.apache.org/%7Eptahchiev/1.8.1-rc2/ The tagged code-base is here: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc2/ I think it is OK this time. Here is my +1 Please vote. Thanks. -- 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: [VOTE] Release Jakarta Cactus 1.8.1
Hi Sebb, I have uploaded the signatures as detached files. Cheers, Petar. On Tue, Jan 20, 2009 at 6:49 PM, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi all, maybe I am too impatient, but has anybody tried the artifacts? 1 minor problem - the .asc files should be detached ascii signatures, not signed archives. No need to recreate the RC, just recreate the .asc files. We don't normally provide binary .sig files - they can be deleted. I'm still looking at other aspects of the RC. What is your opinion expressed by any of the three numbers :-). On Mon, Jan 19, 2009 at 10:33 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi guys, here comes the second attempt for releasing cactus-1.8.1. The artifacts, hashes and signatures are here: http://people.apache.org/~ptahchiev/1.8.1-rc2/http://people.apache.org/%7Eptahchiev/1.8.1-rc2/ http://people.apache.org/%7Eptahchiev/1.8.1-rc2/ The tagged code-base is here: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc2/ I think it is OK this time. Here is my +1 Please vote. Thanks. -- 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: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org -- 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: [VOTE] Release Jakarta Cactus 1.8.1
Hi Sebb, I removed the CDDL license and described the servlet-api as an Apache 2.0 licensed. I also added the Apache license headers. I also changed the version of AspectJ we are using. About the test failures that you mention I think they are different from what Henry is getting. Anyways I am unable to reproduce them :-( What should I do? Do I need to make a RC-3 and call the vote on it? Thanks for the tips guys. On Tue, Jan 20, 2009 at 9:42 PM, sebb seb...@gmail.com wrote: On 20/01/2009, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi all, maybe I am too impatient, but has anybody tried the artifacts? 1 minor problem - the .asc files should be detached ascii signatures, not signed archives. No need to recreate the RC, just recreate the .asc files. We don't normally provide binary .sig files - they can be deleted. I'm still looking at other aspects of the RC. The servlet-api-2.4.jar file is an Apache version, as Henri already mentioned. The cddl licence should be deleted, and the README updated. Like Henri, I also get test failures: [surefire] Tests run: 5, Failures: 3, Errors: 0, Time elapsed: 0.25 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWarArchive [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXml [surefire] Tests run: 54, Failures: 0, Errors: 0, Time elapsed: 2.359 sec [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXmlVersion [surefire] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.093 sec [surefire] Running org.apache.cactus.integration.ant.TestCactifyEarTask [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactifyWarTask [surefire] Tests run: 21, Failures: 21, Errors: 0, Time elapsed: 0.281 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.078 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTestTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.094 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestRunServerTestsTask [surefire] Tests run: 6, Failures: 6, Errors: 0, Time elapsed: 0.078 sec FAILURE !! I ran mvn test, which failed when it could not find the cactus jars. It would be better if this worked without needing to do mvn install first. I then ran mvn install and got the errors shown above. It looks like these are all caused by junit.framework.AssertionFailedError: The system property 'testinput.dir' must point to an existing directory at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.cactus.integration.ant.AntTestCase.getBuildFile(AntTestCase.java:370) This is a bit odd, as the directory appears to be there. The assert() message ought to quote the directory name it is looking for. [I'll update SVN trunk.] Even odder, the problem does not occur when I reran the test. I've tried several times to recreate the error, but it only happened once. == There are various jetty files under samples/jetty/src which don't have AL headers. Are these Jetty sources? If so, then the source archive really needs to include the relevant license. If the samples were generated under the ASF, then they need the AL headers. There seem to be some oddities in the main pom.xml: dependencies dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.5.3/version /dependency specifies version 1.5.3, whereas dependencyManagement dependencies ... dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.2.1/version /dependency specifies version 1.2.1 - I would have expected the two to be the same? == There are several maven.xml and project.xml files in the directory tree - are these still current? What is your opinion expressed by any of the three numbers :-). On Mon, Jan 19, 2009 at 10:33 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi guys, here comes the second attempt for releasing cactus-1.8.1. The artifacts, hashes and signatures are here: http://people.apache.org/~ptahchiev/1.8.1-rc2/http://people.apache.org/%7Eptahchiev/1.8.1-rc2/ http://people.apache.org/%7Eptahchiev/1.8.1-rc2/ The tagged code
Re: [VOTE] Release Jakarta Cactus 1.8.1
Hi guys, I think I found the problem, but since I cannot reproduce this behaviour I am clueless if this will work. I think the problem is here: http://jira.codehaus.org/browse/SUREFIRE-98 I changed the version of the Surefire plugin we use to the latest one. I have commited it. Anything else before I make the RC-3 and cast the vote? Thanks again, Petar. On Tue, Jan 20, 2009 at 10:51 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi Sebb, I removed the CDDL license and described the servlet-api as an Apache 2.0 licensed. I also added the Apache license headers. I also changed the version of AspectJ we are using. About the test failures that you mention I think they are different from what Henry is getting. Anyways I am unable to reproduce them :-( What should I do? Do I need to make a RC-3 and call the vote on it? Thanks for the tips guys. On Tue, Jan 20, 2009 at 9:42 PM, sebb seb...@gmail.com wrote: On 20/01/2009, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi all, maybe I am too impatient, but has anybody tried the artifacts? 1 minor problem - the .asc files should be detached ascii signatures, not signed archives. No need to recreate the RC, just recreate the .asc files. We don't normally provide binary .sig files - they can be deleted. I'm still looking at other aspects of the RC. The servlet-api-2.4.jar file is an Apache version, as Henri already mentioned. The cddl licence should be deleted, and the README updated. Like Henri, I also get test failures: [surefire] Tests run: 5, Failures: 3, Errors: 0, Time elapsed: 0.25 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWarArchive [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXml [surefire] Tests run: 54, Failures: 0, Errors: 0, Time elapsed: 2.359 sec [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXmlVersion [surefire] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.093 sec [surefire] Running org.apache.cactus.integration.ant.TestCactifyEarTask [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactifyWarTask [surefire] Tests run: 21, Failures: 21, Errors: 0, Time elapsed: 0.281 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.078 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTestTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.094 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestRunServerTestsTask [surefire] Tests run: 6, Failures: 6, Errors: 0, Time elapsed: 0.078 sec FAILURE !! I ran mvn test, which failed when it could not find the cactus jars. It would be better if this worked without needing to do mvn install first. I then ran mvn install and got the errors shown above. It looks like these are all caused by junit.framework.AssertionFailedError: The system property 'testinput.dir' must point to an existing directory at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.cactus.integration.ant.AntTestCase.getBuildFile(AntTestCase.java:370) This is a bit odd, as the directory appears to be there. The assert() message ought to quote the directory name it is looking for. [I'll update SVN trunk.] Even odder, the problem does not occur when I reran the test. I've tried several times to recreate the error, but it only happened once. == There are various jetty files under samples/jetty/src which don't have AL headers. Are these Jetty sources? If so, then the source archive really needs to include the relevant license. If the samples were generated under the ASF, then they need the AL headers. There seem to be some oddities in the main pom.xml: dependencies dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.5.3/version /dependency specifies version 1.5.3, whereas dependencyManagement dependencies ... dependency groupIdaspectj/groupId artifactIdaspectjrt/artifactId version1.2.1/version /dependency specifies version 1.2.1 - I would have expected the two to be the same? == There are several maven.xml and project.xml files in the directory tree - are these still current? What is your opinion expressed by any
Re: [VOTE] Release Jakarta Cactus 1.8.1
Actually Hentry's problem was that he had something alreadty running on port 8080. But you are right. We check if the property is set :-( Ok, I will try to investigate further. On Wed, Jan 21, 2009 at 12:06 AM, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi guys, I think I found the problem, but since I cannot reproduce this behaviour I am clueless if this will work. I think the problem is here: http://jira.codehaus.org/browse/SUREFIRE-98 The issue relates to not finding a property - however the code already does a separate check to see if the property has been retrieved OK, so I don't think it applies here. I changed the version of the Surefire plugin we use to the latest one. I have commited it. Anything else before I make the RC-3 and cast the vote? Probably best if Henri could provide more info on the failure he saw, which I think was different from mine. I'm also intending to try a test on Unix. I suggest waiting a bit. Thanks again, Petar. On Tue, Jan 20, 2009 at 10:51 PM, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi Sebb, I removed the CDDL license and described the servlet-api as an Apache 2.0 licensed. I also added the Apache license headers. I also changed the version of AspectJ we are using. About the test failures that you mention I think they are different from what Henry is getting. Anyways I am unable to reproduce them :-( What should I do? Do I need to make a RC-3 and call the vote on it? Thanks for the tips guys. On Tue, Jan 20, 2009 at 9:42 PM, sebb seb...@gmail.com wrote: On 20/01/2009, sebb seb...@gmail.com wrote: On 20/01/2009, Petar Tahchiev paranoiabla.li...@gmail.com wrote: Hi all, maybe I am too impatient, but has anybody tried the artifacts? 1 minor problem - the .asc files should be detached ascii signatures, not signed archives. No need to recreate the RC, just recreate the .asc files. We don't normally provide binary .sig files - they can be deleted. I'm still looking at other aspects of the RC. The servlet-api-2.4.jar file is an Apache version, as Henri already mentioned. The cddl licence should be deleted, and the README updated. Like Henri, I also get test failures: [surefire] Tests run: 5, Failures: 3, Errors: 0, Time elapsed: 0.25 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWarArchive [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXml [surefire] Tests run: 54, Failures: 0, Errors: 0, Time elapsed: 2.359 sec [surefire] Running org.apache.cactus.integration.ant.deployment.webapp.TestWebXmlVersion [surefire] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.093 sec [surefire] Running org.apache.cactus.integration.ant.TestCactifyEarTask [surefire] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 0.031 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactifyWarTask [surefire] Tests run: 21, Failures: 21, Errors: 0, Time elapsed: 0.281 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.078 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestCactusTestTask [surefire] Tests run: 7, Failures: 7, Errors: 0, Time elapsed: 0.094 sec FAILURE !! [surefire] Running org.apache.cactus.integration.ant.TestRunServerTestsTask [surefire] Tests run: 6, Failures: 6, Errors: 0, Time elapsed: 0.078 sec FAILURE !! I ran mvn test, which failed when it could not find the cactus jars. It would be better if this worked without needing to do mvn install first. I then ran mvn install and got the errors shown above. It looks like these are all caused by junit.framework.AssertionFailedError: The system property 'testinput.dir' must point to an existing directory at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.cactus.integration.ant.AntTestCase.getBuildFile(AntTestCase.java:370) This is a bit odd, as the directory appears to be there. The assert() message ought to quote the directory name it is looking for. [I'll update SVN trunk.] Even odder, the problem does not occur when I reran the test. I've tried several times to recreate the error, but it only happened once. == There are various jetty files under samples/jetty/src which don't have AL headers. Are these Jetty sources
[VOTE] Release Jakarta Cactus 1.8.1
Hi guys, here comes the second attempt for releasing cactus-1.8.1. The artifacts, hashes and signatures are here: http://people.apache.org/~ptahchiev/1.8.1-rc2/ The tagged code-base is here: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc2/ I think it is OK this time. Here is my +1 Please vote. Thanks. -- 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: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
[VOTE] Release 1.8.1 of Cactus
Hello guys, It's been more than 10 months since I released Cactus version 1.8.0, and not I am trying to push the 1.8.1 release. I have closed some issues in the JIRA, added a maven2 plugin for Cactus and included a sample EJB3 application, as a reference how to test EJB3. Here is the tag code-base: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc1/ And here are the archives: http://people.apache.org/~ptahchiev/1.8.1-rc1/http://people.apache.org/%7Eptahchiev/1.8.1-rc1/ Please test and cast your vote. [+1]Go man, go! 0] I don't care. [-1] I am against it, because ... Here is mine: +1 Thanks, Petar. -- 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
[VOTE] Release Cactus 1.8.1
Hello guys, It's been more than 10 months since I released Cactus version 1.8.0, and not I am trying to push the 1.8.1 release. I have closed some issues in the JIRA, added a maven2 plugin for Cactus and included a sample EJB3 application, as a reference how to test EJB3. Here is the tag code-base: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.1-rc1/ And here are the archives: http://people.apache.org/~ptahchiev/1.8.1-rc1/http://people.apache.org/%7Eptahchiev/1.8.1-rc1/ Please test and cast your vote. [+1]Go man, go! 0] I don't care. [-1] I am against it, because ... Here is mine: +1 Thanks, Petar. -- Regards, Petar! Karlovo, Bulgaria. - - - - - - - - | Author @ Manning Publications. | Senior Solution Architect @ Unic | BGJUG-Bulgarian Java User Group Leader. | Apache Maven Developer. | Apache Jakarta PMC member. | Jakarta Cactus Lead Developer. | Blogger: http://weblogs.java.net/blog/paranoiabla/ - - - - - - - - Public PGP Key at: https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611 Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: [VOTE] JMeter 2.3.2RC1
Hi guys, I checked out the tag and tried to build it with ant and all went well. Then I tried to execute: ant test and I got a coonection exception batchtest: [echo] Starting BatchTestLocal using -Rlocalhost [java] Created the tree successfully using testfiles/BatchTestLocal.jmx [java] Configuring remote engine for localhost [java] Failure connecting to remote hostjava.rmi.ConnectException: Connection refused to host: localhost; nested exception is: [java] java.net.ConnectException: Connection refused [java] Java Result: 1 [echo] BatchTestLocal output files compared OK [concat] 2008/05/22 12:46:31 FATAL - jmeter.JMeter: Failure connecting to remote host java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: [concat] java.net.ConnectException: Connection refused [concat] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601) [concat] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198) [concat] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184) [concat] at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322) [concat] at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source) [concat] at java.rmi.Naming.lookup(Naming.java:84) [concat] at org.apache.jmeter.engine.ClientJMeterEngine.getEngine(ClientJMeterEngine.java:52) [concat] at org.apache.jmeter.engine.ClientJMeterEngine.init(ClientJMeterEngine.java:56) [concat] at org.apache.jmeter.JMeter.doRemoteInit(JMeter.java:857) [concat] at org.apache.jmeter.JMeter.run(JMeter.java:769) [concat] at org.apache.jmeter.JMeter.startNonGui(JMeter.java:703) [concat] at org.apache.jmeter.JMeter.start(JMeter.java:360) [concat] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [concat] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [concat] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [concat] at java.lang.reflect.Method.invoke(Method.java:597) [concat] at org.apache.jmeter.NewDriver.main(NewDriver.java:210) [concat] Caused by: java.net.ConnectException: Connection refused [concat] at java.net.PlainSocketImpl.socketConnect(Native Method) [concat] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [concat] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) [concat] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) [concat] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) [concat] at java.net.Socket.connect(Socket.java:518) [concat] at java.net.Socket.connect(Socket.java:468) [concat] at java.net.Socket.init(Socket.java:365) [concat] at java.net.Socket.init(Socket.java:179) [concat] at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22) [concat] at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128) [concat] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595) [concat] ... 16 more HTH, Petar. On Tue, May 20, 2008 at 11:46 PM, Oleg Kalnichevski [EMAIL PROTECTED] wrote: On Tue, 2008-05-20 at 21:03 +0100, sebb wrote: On 20/05/2008, Oleg Kalnichevski [EMAIL PROTECTED] wrote: On Tue, 2008-05-20 at 01:23 +0100, sebb wrote: It's about time (indeed overdue) for another JMeter release, so I've created JMeter 2.3.1 RC1 in the directory: http://people.apache.org/~sebb/jmeter-2.3.2/disthttp://people.apache.org/%7Esebb/jmeter-2.3.2/dist Site/Docs are here: http://people.apache.org/~sebb/jmeter-2.3.2/docshttp://people.apache.org/%7Esebb/jmeter-2.3.2/docs Tag: http://svn.apache.org/repos/asf/jakarta/jmeter/tags/v2_3_2RC1 Keys are here: http://svn.apache.org/repos/asf/jakarta/jmeter/trunk/KEYS.txt also http://www.apache.org/dist/jakarta/jmeter/KEYS All feedback (and votes!) welcome. [ ]+1 - the release candidate is OK [ ]-1 - there is a problem (please indicate what it is) The vote will remain open for at least 72 hours. Note: If the vote passes, the intention is to release the archive files and create the release tag from the RC1 tag. Hi Sebastian Thanks for trying it out. JMeter compiles and builds just fine. All tests pass for me, but the 'ant test' terminates with a build failure. BUILD FAILED /home/oleg/temp/jakarta-jmeter-2.3.2/build.xml:1552: Files are not identical. Any idea what may be wrong? One of the tests uses two
Re: [VOTE] Jakarta Cactus 1.8.0
I am closing this vote after more than 72 hours. On Tue, Apr 8, 2008 at 11:33 AM, Stefan Bodewig [EMAIL PROTECTED] wrote: On Mon, 7 Apr 2008, Petar Tahchiev [EMAIL PROTECTED] wrote: I found a small error in the trunk and after consulting with sebb I decided to make another archives and a tag: Please cast your vote as you feel it :-). +1 Stefan - 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
[VOTE Results] Jakarta Cactus 1.8.0
[VOTE][RESULT] Jakarta Cactus 1.8.0 release The vote to release Jakarta Cactus has passed with the following results +1 (3 binding votes in total) Petar Tahchiev [EMAIL PROTECTED]* sebb [EMAIL PROTECTED]* (Sorry sebb, I never knew your real name) Stefan Bodewig [EMAIL PROTECTED]* * binding votes Original voting thread: http://www.nabble.com/-VOTE--Jakarta-Cactus-1.8.0-td16546018.html -- 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
[VOTE] Jakarta Cactus 1.8.0
Hi guys, I found a small error in the trunk and after consulting with sebb I decided to make another archives and a tag: Here is the tag: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.0-RC3/ and here are the archives: http://people.apache.org/dist/jakarta/cactus/1.8.0-RC3/ Please cast your vote as you feel it :-). Her is mine: +1 Thanks. -- 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
[VOTE] Cactus 1.8.0
Hi guys, you know what they say: Third time is a charm :-). I have changed a bit the documentation, also excluded the .project and .classpath files from the archives. Also made small modifications on the samples project. Now the archives are called 1.8.0, so that if the vote passes they will be used as official. The tag is here: http://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.0-RC2/ and the archives here: http://people.apache.org/dist/jakarta/cactus/1.8.0-RC2/ Please, cast your vote if you think that the archives are OK. Here is mine: +1 -- 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: [VOTE] Jakarta Cactus 1.8.0 Release Candidate (Second attempt)
OK, as I spoke with sebb in private I will open another discussion. On Fri, Apr 4, 2008 at 2:43 AM, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi guys, I have uploaded the archives here: http://people.apache.org/dist/jakarta/cactus/1.8.0-RC/ and the tag here: https://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.0-rc/ Please review and vote as you feel it. My vote is here: +1 (binding) Cheers, Petar. -- 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)
If there are no objections any more, I will propose the archives for a release-vote. Is there something else to be fixed? On Wed, Apr 2, 2008 at 6:02 PM, Petar Tahchiev [EMAIL PROTECTED] wrote: 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
[VOTE] Jakarta Cactus 1.8.0 Release Candidate
Hi everybody I would like to cast a vote on releasing Jakarta Cactus 1.8.0. The RC archives are here: http://people.apache.org/dist/jakarta/cactus/1.8.0-RC/ and the tag that the archives were made of is here: http://svn.apache.org/repos/asf/jakarta/cactus/tags/cactus-1.8.0-rc/ My vote is below (binding): yes [ x ] (+1) no [ ] (-1) Thanks, Petar. -- 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
[VOTE] Jakarta Cactus 1.8.0 Release Candidate (Second attempt)
Hi guys, I have uploaded the archives here: http://people.apache.org/dist/jakarta/cactus/1.8.0-RC/ and the tag here: https://svn.apache.org/repos/asf/jakarta/cactus/tags/1.8.0-rc/ Please review and vote as you feel it. My vote is here: +1 (binding) Cheers, Petar. -- 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
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: http://people.apache.org/dist
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)
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)
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
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 - 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 Release Archives
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: http://people.apache.org/dist/jakarta/cactus/1.8.0/ Just noticed that both the source and binary archives contain the apidocs and xref. It does not make sense to have them in both jars - no wonder the source jar has doubled in size... Javadocs are more useful in the binary archive. Xref can just go on the web-site - no need for it in either archive. You'll need to add your key to the KEYS file. Also, it would be better if you included your ASF e-mail in the key details. with the following changes: 0) Now everything is built with JDK 1.4 1) The LN files are included. The LICENSE file needs to include or point to the 3rd party licenses. The NOTICE file needs to note that the product includes contributions from these 3rd party sources: http://www.apache.org/legal/src-headers.html and http://www.apache.org/licenses/example-NOTICE.txt [but note that the header in === should not be included!] 2) The MANIFEST.MF is proper (according to me). There seem to be some manifest files in SVN, which do look fine. However, they contain the Java versions. These should be created by the build to reflect the actual settings used to create the jars. Any manifest files in SVN should be used as templates or boiler-plate only. But it's probably easier to use Maven to create the entire file. 3) I have removed the duplicate maven-release-plugin declaration, which used to bring the line
Re: Cactus Release Archives
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: http://people.apache.org/dist/jakarta/cactus/1.8.0/ with the following changes: 0) Now everything is built with JDK 1.4 1) The LN files are included. 2) The MANIFEST.MF is proper (according to me). 3) I have removed the duplicate maven-release-plugin declaration, which used to bring the line: tagBasefile:home/peter/tags//tagBase I have made the archives from the trunk. I have no RC tag. If the archives are OK, I will cast a vote upon them and if the vote succeeds I will copy the trunk in a tag. The only issue I see now is that we have the DEPENDENCIES file in the META-INF, but since it is not a blocking issue I will leave as it is. (Actually I couldn't find anywhere in the web how to remove this file). Please can you have a look over the artifacts and in case there are any problems, I will be glad to work on fixing them. Thanks a lot. P.S I have the following in my ~/.subversion/config file: *.java = svn:eol-style=native but I don't seem to set the eol-style correctly. Can you tell me where am I wrong? Also I have added the RAT plugin in the master pom so that we can execute the rat plugin. I exclude the scratchpad/, descriptors/ and ANNOUNCEMENT.txt and I don't see any other file with a missing header On Mon, Mar 31, 2008 at 11:49 PM, sebb [EMAIL PROTECTED] wrote: On 30/03/2008, sebb [EMAIL PROTECTED] wrote: On 29/03/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi Sebb, thanks for the feedback. I prefer to keep the bz2 archives. I have improved the licenses according to the lib folder. There are still several jars in the lib directory which are not mentioned in the licenses/README.txt. README.txt says: Apache ServletAPI - Apache 2.0 However, the MANIFEST in servlet-api-2.5.jar suggests that the owner is Sun, not Apache, and the license may not be AL 2.0. Also I have made the MANIFEST.MF to include the data you pointed. But the compiler versions are not in cactus.core.framework.uberjar.javaEE.14-1.8.0.jar. Also, the version says source and target = 1.4, yet the code was built (and presumably tested) with Java 1.6. The code should be built and tested with Java 1.4. I just tried mvn install with Java 1.4, and a lot of tests failed. The ones I checked failed with: java.lang.NoClassDefFoundError: org/w3c/dom/ranges/DocumentRange Also the META-INF folder to include the LICENSE and NOTICE files. However, these files need to relate to the contents of the jar or archive - for example, the ones in the cactus jars should only mention Apache, as all the code therein is Apache, as far as I can tell. The N L files for the archives need to mention the external software that is included. I have also included the 'source' and 'target' versions in the parent pom.xml and also the inceptionYear attribute. The inceptionYear should agree with the first Copyright year. The pom includes the lines: urlscp://[EMAIL PROTECTED] :/www/jakarta.apache.org/cactus/1.8.0//url tagBasefile:home/peter/tags//tagBase which are unlikely to work for other users. Now I think that everything is OK. You can see the new files here: http://people.apache.org/dist/jakarta/cactus/1.8.0/ Where is the RC tag for the source? There should be an RC tag and a build that is made from the tag. If the vote succeeds, the tag can be copied to the release tag. If not, then a new tag can be made once all the fixes have been applied, and the process repeated. It looks like the final release tag has already been created. If the vote fails, this will have to be deleted and recreated once the fixes have been made. That's not ideal for release tags. Tomorrow morning I will cast a release-vote for these archives. Sorry, but I don't think they are ready. Just ran RAT on cactus-trunk - there are a lot of files that don't have the proper AL header. Cheers, Petar. On Sat, Mar 29, 2008 at 3:43 AM, sebb [EMAIL PROTECTED] wrote: On 29/03/2008, sebb [EMAIL PROTECTED] wrote: On 25/03/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi everybody, I am following this tutorial: http://wiki.apache.org/HttpComponents/HttpComponentsCoreReleaseProcess and making it for Cactus. So I want to invite you all to test the archives I have uploaded here: http://people.apache.org/dist/jakarta/cactus/ and report problems if you find some. Not sure it's useful to include the bz2 archives; although they are slightly smaller, the user-base is much smaller
Re: Cactus Release Archives
Hi Sebb, thanks for the feedback. I prefer to keep the bz2 archives. I have improved the licenses according to the lib folder. Also I have made the MANIFEST.MF to include the data you pointed. Also the META-INF folder to include the LICENSE and NOTICE files. I have also included the 'source' and 'target' versions in the parent pom.xml and also the inceptionYear attribute. Now I think that everything is OK. You can see the new files here: http://people.apache.org/dist/jakarta/cactus/1.8.0/ Tomorrow morning I will cast a release-vote for these archives. Cheers, Petar. On Sat, Mar 29, 2008 at 3:43 AM, sebb [EMAIL PROTECTED] wrote: On 29/03/2008, sebb [EMAIL PROTECTED] wrote: On 25/03/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi everybody, I am following this tutorial: http://wiki.apache.org/HttpComponents/HttpComponentsCoreReleaseProcess and making it for Cactus. So I want to invite you all to test the archives I have uploaded here: http://people.apache.org/dist/jakarta/cactus/ and report problems if you find some. Not sure it's useful to include the bz2 archives; although they are slightly smaller, the user-base is much smaller... The licenses/README.txt file does not seem to agree with the jars in the lib directory. Also, several of the jars in the lib directory are quite old versions; if possible, they should be updated. The generated cactus jars must contain NOTICE and LICENSE files (e.g. in the META-INF directory) It would be useful if the cactus jar manifests included the following attributes: Built-By: x Implementation-Title: Jakarta Cactus Implementation-Vendor: The Apache Software Foundation Implementation-Vendor-Id: org.apache Implementation-Version: 1.8-SNAPSHOT Specification-Title: Jakarta Cactus Specification-Vendor: The Apache Software Foundation Specification-Version: 1.8-SNAPSHOT Build-Jdk: 1.5.0_12 (e.g.) X-Compile-Source-JDK: 1.3 (e.g.) X-Compile-Target-JDK: 1.3 (e.g.) There seem to be some problems with SVN file properties; I've fixed most of them in trunk. Did you create the archives from trunk? There are some discrepancies between that and the source archive. Just noticed that the pom.xml does not specify the source and target java versions. It should also have inceptionYear Might be an idea to use a property for the version so the individual poms don't have to be updated. The eclipse .classpath file looks a bit odd - it seems to have lots of entries that don't seem to be required. If no problems occur, I will continue with the next steps of the tutorial and make official release archives and cast a vote upon them. Thank you all. P.S. You can also have a look at the new Cactus web-site I have uploaded here: http://jakarta.apache.org/cactus/1.8.0/ I am currently doing final test upon it and then I will upload it as official Cactus site. -- 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
Cactus Release Archives
Hi everybody, I am following this tutorial: http://wiki.apache.org/HttpComponents/HttpComponentsCoreReleaseProcess and making it for Cactus. So I want to invite you all to test the archives I have uploaded here: http://people.apache.org/dist/jakarta/cactus/ and report problems if you find some. If no problems occur, I will continue with the next steps of the tutorial and make official release archives and cast a vote upon them. Thank you all. P.S. You can also have a look at the new Cactus web-site I have uploaded here: http://jakarta.apache.org/cactus/1.8.0/ I am currently doing final test upon it and then I will upload it as official Cactus site. -- 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 Development For a RC
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=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 Development For a RC
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=getsearch=0x1A15B53B761500F9 Key Fingerprint: AA16 8004 AADD 9C76 EF5B 4210 1A15 B53B 7615 00F9
Re: Cactus Development For a RC
Hi Magnus, sorry I didn't see your email, while I was typing mine :-). Well, the version of Cargo integrated is: 0.9 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? Cheers, Petar. On Jan 31, 2008 4:41 PM, Petar Tahchiev [EMAIL PROTECTED] wrote: OK, so far: 1) I removed all of the .cvsignore files. 2) Improved lots of the documentation. 3) Removed the samples module from the initial build. If you just run mvn install then the samples modules will not be build. When specifying a with-samples profile, like: mvn clean install -P with-samples then the same build will pass + the samples modules. Now for the samples to be executed correctly you will need a servlet container/ejb container. Hopefully Cargo gives us the opportunity to get the containers from internet. This will, however, slow down the build process, but as far as you have patience, it's OK. :-) Any other comments? On Jan 30, 2008 7:44 PM, sebb [EMAIL PROTECTED] wrote: Trying mvn site:site complains that it cannot find: org.apache.cactus:cactus.maven.skin:jar:2.0.0 mvn install fails because it cannot find: [C:/apache/tomcat/apache-tomcat-6.0.14] On 30/01/2008, sebb [EMAIL PROTECTED] wrote: A brief look shows that: The README file has the line: To build Cactus from CVS, please refer to the following tuturial which should probably be To build Cactus from SVN, please refer to the following tutorial There need to be LICENSE and NOTICE files. The .cvsignore files should be deleted. === Not everyone will want to build the code and documentation just in order to review the proposed release, so may I suggest that you create the distribution artefacts and web-site from the branch and upload them to your personal directory on people.apache.org? Once any issues are sorted, a formal vote can be started. Sebastian On 30/01/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi guys, my name is Petar Tahchiev, and I see I am currently the only active committer for the Cactus project. For the last year I have been working in a separate branch here: http://svn.apache.org/repos/asf/jakarta/cactus/branches/CACTUS_TRUNK_MAMOUTH/ and I think that I am ready to try and make a release candidate (RC). Because of the status of Cactus I guess I will have to initiate a vote for this release to be done, and also to fix if you find something to be broken. The current changes include: 1) new Maven2 based build system 2) integration between Cargo Cactus 3) new Ant tasks (see the sample projects). 4) the New Cactus web-site (look in cactus-site and execute mvn site:site) 5) Cactus-eclipse plugin refactored to support Eclipse 3.2 Well, currently the only thing that is left is to describe everything in a nice documentation, but I prefer to do this once I see that you guys say everything is OK. So that's what I do now. I hope that you guys checkout the project from the repository and give it a try. Waiting for your comments. Cheers, Petar. -- 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 -- 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 Development For a RC
OK, so far: 1) I removed all of the .cvsignore files. 2) Improved lots of the documentation. 3) Removed the samples module from the initial build. If you just run mvn install then the samples modules will not be build. When specifying a with-samples profile, like: mvn clean install -P with-samples then the same build will pass + the samples modules. Now for the samples to be executed correctly you will need a servlet container/ejb container. Hopefully Cargo gives us the opportunity to get the containers from internet. This will, however, slow down the build process, but as far as you have patience, it's OK. :-) Any other comments? On Jan 30, 2008 7:44 PM, sebb [EMAIL PROTECTED] wrote: Trying mvn site:site complains that it cannot find: org.apache.cactus:cactus.maven.skin:jar:2.0.0 mvn install fails because it cannot find: [C:/apache/tomcat/apache-tomcat-6.0.14] On 30/01/2008, sebb [EMAIL PROTECTED] wrote: A brief look shows that: The README file has the line: To build Cactus from CVS, please refer to the following tuturial which should probably be To build Cactus from SVN, please refer to the following tutorial There need to be LICENSE and NOTICE files. The .cvsignore files should be deleted. === Not everyone will want to build the code and documentation just in order to review the proposed release, so may I suggest that you create the distribution artefacts and web-site from the branch and upload them to your personal directory on people.apache.org? Once any issues are sorted, a formal vote can be started. Sebastian On 30/01/2008, Petar Tahchiev [EMAIL PROTECTED] wrote: Hi guys, my name is Petar Tahchiev, and I see I am currently the only active committer for the Cactus project. For the last year I have been working in a separate branch here: http://svn.apache.org/repos/asf/jakarta/cactus/branches/CACTUS_TRUNK_MAMOUTH/ and I think that I am ready to try and make a release candidate (RC). Because of the status of Cactus I guess I will have to initiate a vote for this release to be done, and also to fix if you find something to be broken. The current changes include: 1) new Maven2 based build system 2) integration between Cargo Cactus 3) new Ant tasks (see the sample projects). 4) the New Cactus web-site (look in cactus-site and execute mvn site:site) 5) Cactus-eclipse plugin refactored to support Eclipse 3.2 Well, currently the only thing that is left is to describe everything in a nice documentation, but I prefer to do this once I see that you guys say everything is OK. So that's what I do now. I hope that you guys checkout the project from the repository and give it a try. Waiting for your comments. Cheers, Petar. -- 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
Cactus Development For a RC
Hi guys, my name is Petar Tahchiev, and I see I am currently the only active committer for the Cactus project. For the last year I have been working in a separate branch here: http://svn.apache.org/repos/asf/jakarta/cactus/branches/CACTUS_TRUNK_MAMOUTH/ and I think that I am ready to try and make a release candidate (RC). Because of the status of Cactus I guess I will have to initiate a vote for this release to be done, and also to fix if you find something to be broken. The current changes include: 1) new Maven2 based build system 2) integration between Cargo Cactus 3) new Ant tasks (see the sample projects). 4) the New Cactus web-site (look in cactus-site and execute mvn site:site) 5) Cactus-eclipse plugin refactored to support Eclipse 3.2 Well, currently the only thing that is left is to describe everything in a nice documentation, but I prefer to do this once I see that you guys say everything is OK. So that's what I do now. I hope that you guys checkout the project from the repository and give it a try. Waiting for your comments. Cheers, Petar. -- 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
BGJUG loads with Apache Software
Hi guys, I started the Bulgarian Java User Group and last week was our first meeting. I have blogged my impressions [1], but I wanted to share with you something else. As I am a jakarta commiter, I tried to make the site, using only Apache tools, whenever that was possible. So here is what happened.Our site is powered by these technologies: --- Apache FTP Server, Apache James Server, --- Apache HTTPD Server Apache mod_jk Apache Tomcat Apache Struts, Apache Log4J, Apache ANT, Apache Jakarta Commons-* -- In addition to I also use these technologies: Spring, Hibernate(for ORM), SVN, PostgreSQL, and Sun Solaris for the OS. In future we plan to use also Apache Roller for blogging system. As a conclusion I want to say that the whole system is purely Java implemented (except for the Postgre). Congratulations ApacheJakarta - you are amazing!!! :-) [1]* *http://weblogs.java.net/blog/paranoiabla/ -- 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
[VOTE] JMeter + Cactus + ... - Testing TLP
Hi guys, it's Petar. I wanted to talk to you about an idea I found in the mailing list archives lately[1]. I spoke with Felipe Leme and he told me that once, he tried to move all the testing related apache projects to a new TLP project under the domain: http://testing.apache.org/ This structure would contain the two major testing-related projects in the ASF: Jakarta Cactus and Jakarta JMeter. This structure would also be a host for all other testing related projects that would come from the incubator and fulfill the testing.apache.org policies. This TLP project would serve as umbrella, like the Jakarta, DB, XML, Commons, WS (especially), etc ... There are also lots of other test-related projects, or sub-projects that come to my mind, and that would like to come under the the t.a.o project: - Apache HttpTest Project ( http://httpd.apache.org/test/ ) - Shale Test Framework (http://shale.apache.org/shale-test/index.html ) - Apache Harmony build-test framework (http://harmony.apache.org/subcomponents/buildtest/index.html ) The main reason why the initial idea was rejected was that we might have ended with a dormant TLP project, which I agree is really bad. But I don't think that will ever happen: first I have been active on the Cactus project and I will make a presentation on this year's ApacheCON USA with the latest changes I have made. We also plan a release of Cactus by the end of the year. JMeter, on the other hand has a stable community of 13 developers,and lots of other contributors. Another reason for considering moving those projects as a TLP, would be that: with a central place for all the testing related ASF software more people will get involved in the idea, and let's face it - that's very good for Cactus, as it is somewhat dormant. Finally I want to to redirect you for additional information to Felipe's posts, and to the wiki of Jakarta: [1]http://marc.info/?l=jakarta-generalm=115047715227445w=2 [2]http://wiki.apache.org/jakarta/TLPCactusAndJMeter/Notes Waiting for your votes and/or questions, mine is here: [+1] -- 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: [PROPOSAL] The future of Jakarta
On 5/15/07, Danny Angus [EMAIL PROTECTED] wrote: Hi, Ok, I've followed the commons TLP vote thread with some interest because it seems to impact directly on the end-game for Jakarta. I believe that we have to make some pretty fundamental decisions about that future before we can fully resolve the commons TLP issues. 0/ Do we agree that the end-game is dissolution of the Jakarta PMC and closure of the project? Pro - Draws a line under the reorg effort which has gone on for 3 or 4 *years*. Con - Removes the remaining tangible historic links between former Jakarta sub-projects. 1/ If so do we wish to preserve the Jakarta brand? (the website and possibly general@) Pro - As Ted H. says We should stop thinking of Jakarta only as an entity, and go back to thinking of it as to the ASF synonym for Java, as originally intended. With this thought in mind around 10% of the referrals to james.apache come from jakarta.apache. Con - Others consider that the effort of maintaining the resources would be unacceptable to anyone. 2/ If we believe that the brand should be preserved should the commons TLP take ownership of the brand (if/when Jakarta PMC is dissolved) Pro - Commons is an active community which continues to fulfil the jakarta==java remit. Con - Commons is not necessarily interested in the brand or maintenance of its resources. (would people from other projects step up) 3/ If we believe that a commons TLP should not own the brand are any of the alternative options acceptable? - Retain the Jakarta PMC solely to maintain the brand - Move ownership of the brand to the prc (should they agree to have it) - Move ownership of the brand to projects.apache maintainers x/ Should we consult more widely the Members and/or the Board? My own (2c) opinion is that: 0/ Yes dissolve the jakarta pmc 1/ Yes preserve the brand 2/ If commons PMC would be comfortable with this it would be my preferred choice, *and* it would resolve the naming issue because the project could be Jakarta Commons which is a minor change from the sub-project name Jakarta/Commons 3/ If commons PMC would be against this then I think we should approach the prc. x/ Don't know In essence are we in favour of a revolutionary end or an evolutionary one? WDYT? d. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hello to everybody, my personal opinion differes slightly. I still believe that we have to preserve Jakarta as a project summoning the Java projects in the foundation. If you ask me directly Do we need another Jakartas like for .NET for instance? - I would say yes. Those new Jakarta, or Nairobi or whatever we decide to call it has to be a TLP, and has to have a commons project, and has to have a PMC and everything else. Then,part of our current .NET projects could be transfered to the .NET-commons one. Actually I have been following the mail lists for more than three years by now, although I am part of the Jakarta project for less than three months, so you don't need to consider my thoughts seriosly. I am curious to hear what Martin van den Bemt has to say, as I know he is going to lead a presentation on the ApacheCON USA with the exact same name. Have a nice day. -- Regards, Petar! Karlovo, Bulgaria. 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: [VOTE] Commons moving to TLP
On 5/9/07, Jörg Schaible [EMAIL PROTECTED] wrote: +1 Henri Yandell wrote on Tuesday, May 08, 2007 7:20 PM: Sadly a bit too late to make the next board meeting I suspect. However, here's a vote for Commons to officially request that it move to TLP. http://wiki.apache.org/jakarta-commons/TLPResolution Please add your name if you're a Commons developer and haven't added your name yet. [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... Voting will close in one week. Hen - 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] Hi, I am not a Jakarta commiter, and also vote is not binding, but I want to ask something. What are the benefits for commons of moving to a TLP? Also as I read the official commons intro, it states that commons is a project focused on all aspects of reusable Java components. So as we all know Jakarta is a devision of Apache, that deals with the Java open-source projects in the foundation, therefore, as I see it, it would be better for commons to stay in the Jakarta. So, maybe I am wrong, but I don't see any direct benefit for commons to move to a TLP. That's why, I have to vote: -1 and ask you to prove me wrong. Thank you all. -- Regards, Petar! Karlovo, Bulgaria. 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: [VOTE] Commons moving to TLP
On 5/10/07, Martin van den Bemt [EMAIL PROTECTED] wrote: I am not a Jakarta commiter, and also vote is not binding, but I want to ask something. What are the benefits for commons of moving to a You are a Jakarta committer :) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sorry about that :-( I meant to say I am not a Jakarta Commons comitter. -- Regards, Petar! Karlovo, Bulgaria. 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: [VOTE] Move POI to TLP
On 5/4/07, Henning Schmiedehausen [EMAIL PROTECTED] wrote: +1 Nick Burch schrieb: Hi All After lots of discussion within POI, and Jakarta in general, we think POI is ready to graduate to its own TLP. Thanks to the magic of ApacheCon, lots of people have been on-hand to help finalise the proposal for this, which is attached below. So, now is the time to vote on the proposal: [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] My vote is not binding, but anyway I also think that POI is mature enough for a TLP: +1 -- Regards, Petar! Karlovo, Bulgaria. 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
Notification of acceptance vote in the cactus lists
Hi, I just raised an acceptance vote in the cactus dev-list, for accepting the maven build system I have implemented [1]. Anyone interested can cast their vote there. [1] http://mamouth.svn.sourceforge.net/svnroot/mamouth/Cactus -- Regards, Petar! Karlovo, Bulgaria. 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: An Official Request For Moving Cactus In The Incubator
On 3/7/07, Martin van den Bemt [EMAIL PROTECTED] wrote: will come back to this on friday.. Mvgr, Martin Petar Tahchiev wrote: Hello guys, first of all let me introduce myself. My name is Petar Tahchiev and I am from Bulgaria. I wanted to enroll in the last-years Google Summer Of Code where I applied with the project of migrating the Cactus build system to Maven. Unfortunatelly me and Felipe Leme (my mentor), who I would like to thank once again for the encouragement and the help he provided me, weren't qualified. Later I had a few personal issues to solve, but the point is that I continued to work on my own and sooner I managed to migrate the Cactus project to be built with Maven. When everything was done I started submitting patches in the cactus jira, for some known bugs. The problem with the patch of the build system was that it turned out to be very large so I couldn't apply it in the jira. Then me and Felipe agreed that it would be better to move the cactus to a separate repository and test the build system there (you understand that the new build structure was absolutely different from the old one and merging was a kind of a tough task). So I got my work and imported it in my own repository at the sourceforge.netwhere we began testing. The point is that when we wanted to apply the changes in the cactus trunk in the Apache repository we were adviced by Martin van den Bemt that we have to ask that the project be moved in the incubator first and then when the code is appropriate for the cactus's trunk move it in the trunk. Now the process of moving Cactus in the incubator is stalled, as well as our work on it, because I want to move it in the incubator, before I continue making additional changes and implementing new features. So my request to you guys is this: if anyone can help us move the code in the incubator, he is more than wellcome. Thank you very much. P.S. You may find additional information of the whole process here: [1] http://www.mail-archive.com/cactus-dev@jakarta.apache.org/msg08579.html [2] http://www.nabble.com/Question-About-the-Current-State-Of -Cactus-In-the-Incubator-t361.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, no problem. I know that you are busy, but I have another idea that came to me reading the Matt Benson's post. In fact the guys are dealing with a project that seems to be inspired the jakarta commons Convert project and so it would be possible to accept the code without passing through the incubator. So why isnt' this situation possible for Cactus (I mean I have refactored existing code and added the maven xml files - it is not a new project). I also agree that passing through the incubator is the best solution in the great majority of cases, but in my opinion there are still some cases (like Cactus for instance) that are threatened of stalling even more. P.S. Personaly for me, I am happy with both of the solutions - with or without the incubator. My desire is to start working on the project as soon as possible because we are planning of implementing some new features and then releasing a RC. Looking forward to your reply. -- Regards, Petar! Karlovo, Bulgaria. 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: An Official Request For Moving Cactus In The Incubator
On 3/9/07, Martin van den Bemt [EMAIL PROTECTED] wrote: Hence the reason I wanted to wait for a response till I had more time (still busy).. My approach for you would have been : get a software grant, ccla and icla on file and start a vote on you being a committer for cactus, I just failed horribly to send out that mail (btw sending in those documents is what legal incubation is about). I will send you some links for this, if you didn't figure it out earlier or someone else beats me to it.. Since there is still enough interest in Cactus I think that new activity will be enough to get more people aboard and get the ball rolling again :) Mvgr, Martin Petar Tahchiev wrote: On 3/7/07, Martin van den Bemt [EMAIL PROTECTED] wrote: will come back to this on friday.. Mvgr, Martin Petar Tahchiev wrote: Hello guys, first of all let me introduce myself. My name is Petar Tahchiev and I am from Bulgaria. I wanted to enroll in the last-years Google Summer Of Code where I applied with the project of migrating the Cactus build system to Maven. Unfortunatelly me and Felipe Leme (my mentor), who I would like to thank once again for the encouragement and the help he provided me, weren't qualified. Later I had a few personal issues to solve, but the point is that I continued to work on my own and sooner I managed to migrate the Cactus project to be built with Maven. When everything was done I started submitting patches in the cactus jira, for some known bugs. The problem with the patch of the build system was that it turned out to be very large so I couldn't apply it in the jira. Then me and Felipe agreed that it would be better to move the cactus to a separate repository and test the build system there (you understand that the new build structure was absolutely different from the old one and merging was a kind of a tough task). So I got my work and imported it in my own repository at the sourceforge.netwhere we began testing. The point is that when we wanted to apply the changes in the cactus trunk in the Apache repository we were adviced by Martin van den Bemt that we have to ask that the project be moved in the incubator first and then when the code is appropriate for the cactus's trunk move it in the trunk. Now the process of moving Cactus in the incubator is stalled, as well as our work on it, because I want to move it in the incubator, before I continue making additional changes and implementing new features. So my request to you guys is this: if anyone can help us move the code in the incubator, he is more than wellcome. Thank you very much. P.S. You may find additional information of the whole process here: [1] http://www.mail-archive.com/cactus-dev@jakarta.apache.org/msg08579.html [2] http://www.nabble.com/Question-About-the-Current-State-Of -Cactus-In-the-Incubator-t361.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, no problem. I know that you are busy, but I have another idea that came to me reading the Matt Benson's post. In fact the guys are dealing with a project that seems to be inspired the jakarta commons Convert project and so it would be possible to accept the code without passing through the incubator. So why isnt' this situation possible for Cactus (I mean I have refactored existing code and added the maven xml files - it is not a new project). I also agree that passing through the incubator is the best solution in the great majority of cases, but in my opinion there are still some cases (like Cactus for instance) that are threatened of stalling even more. P.S. Personaly for me, I am happy with both of the solutions - with or without the incubator. My desire is to start working on the project as soon as possible because we are planning of implementing some new features and then releasing a RC. Looking forward to your reply. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] It would be better you send me those links, since I have no idea what a software grant, ccla and icla is :-). Ok waiting for the links. Greetings. -- Regards, Petar! Karlovo, Bulgaria. 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: An Official Request For Moving Cactus In The Incubator
On 3/9/07, Martin van den Bemt [EMAIL PROTECTED] wrote: I know that you are busy, but I have another idea that came to me reading the Matt Benson's post. In fact the guys are dealing with a project that seems to be inspired the jakarta commons Convert project and so it would be possible to accept the code without passing through the incubator. So why isnt' this situation possible for Cactus (I mean I have refactored existing code and added the maven xml files - it is not a new project). I also agree that passing through the incubator is the best solution in the great majority of cases, but in my opinion there are still some cases (like Cactus for instance) that are threatened of stalling even more. Martin or others may answer this better - but AIUI one of the two primary goals of the incubator is building community around code bases. This is not just a nice thing at Apache - its an absolute necessity. As an example under Apache rules without 3 votes from the PMC (project management committee) responsible for a project you can't release anything. Once a project falls below that critical level of involved people its basically dead in the water as far as releasing any software goes. In the case of a project like Cactus the main reason for going back to the incubator would be to re-create a viable community. From what I understood from current people that have cactus on their radar and have sufficient power to vote, Cactus will be able to get a release out the door. An another note : After incubation it could still be that you cannot get a release out the door if you end up at Jakarta, depending on the fact if you actually make it on the Jakarta PMC. This is also one of the reasons an Incubator project should have 3 mentors, so they can actually release, without depending on the time of people not directly involved. Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] All right, I get it now. Thank you Martin. Yes, It sounds now more reasonable to move in the incubator. On more thing: when we move to incubator, who is going to be the incubation champion and the projecty mentors? Thank you Niall for the link. I read the licenses that are listed there. Sorry my negligence about this stuff. :-) Waiting for the further annotation on the status of setting the project in the incubator. P.S. If there is anything I can help, please feel free to let me know. -- Regards, Petar! Karlovo, Bulgaria. 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
An Official Request For Moving Cactus In The Incubator
Hello guys, first of all let me introduce myself. My name is Petar Tahchiev and I am from Bulgaria. I wanted to enroll in the last-years Google Summer Of Code where I applied with the project of migrating the Cactus build system to Maven. Unfortunatelly me and Felipe Leme (my mentor), who I would like to thank once again for the encouragement and the help he provided me, weren't qualified. Later I had a few personal issues to solve, but the point is that I continued to work on my own and sooner I managed to migrate the Cactus project to be built with Maven. When everything was done I started submitting patches in the cactus jira, for some known bugs. The problem with the patch of the build system was that it turned out to be very large so I couldn't apply it in the jira. Then me and Felipe agreed that it would be better to move the cactus to a separate repository and test the build system there (you understand that the new build structure was absolutely different from the old one and merging was a kind of a tough task). So I got my work and imported it in my own repository at the sourceforge.netwhere we began testing. The point is that when we wanted to apply the changes in the cactus trunk in the Apache repository we were adviced by Martin van den Bemt that we have to ask that the project be moved in the incubator first and then when the code is appropriate for the cactus's trunk move it in the trunk. Now the process of moving Cactus in the incubator is stalled, as well as our work on it, because I want to move it in the incubator, before I continue making additional changes and implementing new features. So my request to you guys is this: if anyone can help us move the code in the incubator, he is more than wellcome. Thank you very much. P.S. You may find additional information of the whole process here: [1] http://www.mail-archive.com/cactus-dev@jakarta.apache.org/msg08579.html [2] http://www.nabble.com/Question-About-the-Current-State-Of -Cactus-In-the-Incubator-t361.html -- Regards, Petar! Karlovo, Bulgaria. 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
