Re: [Jakarta Standard Taglib] Cactus + Jetty + Maven2
Btw - I got this working. String taglib and Standard taglib now have subprojects using Cactus + Jetty to test through Maven: https://svn.apache.org/repos/asf/jakarta/taglibs/proper/standard/trunk/standard-test https://svn.apache.org/repos/asf/jakarta/taglibs/proper/string/trunk/string-test Hen On Thu, Apr 23, 2009 at 1:44 AM, Henri Yandell wrote: > I'm frustratingly close to having the Cactus Maven2 plugin working > with the Jetty Maven2 plugin for the Jakarta Standard Taglib. > > Here's what you have to do to replicate my current status: > > > svn co > https://svn.apache.org/repos/asf/jakarta/taglibs/proper/taglibs-parent/trunk > taglibs-parent > cd taglibs-parent > mvn install > cd .. > > svn co https://svn.apache.org/repos/asf/jakarta/taglibs/proper/standard/trunk > standard > cd standard > mvn install > cd standard-test > mvn package integration-test > > The cactus tests are in the subdirectory of standard-test. I know it's > a bit hacky having it as the subdirectory, but it's proof of concept > and then I'll rip things apart in the standard directory and do things > properly. > > Current status is: > > Once you have the taglib parent pom and the jstl+impl combo jar > deployed, the war builds happily, it gets cactified, it goes into > jetty as jetty starts up, surefire kicks in and fails the tests due to > JSP webapp setup reasons. Then jetty turns itself off. > > Oddly, some change I made recently has it doing the war stages > multiple times. Not sure why. > > If anyone gets interested, a second pair of eyes on the JSP webapp > setup reasons would be cool; as would any suggestions on how the > pom.xml could be simplified or is doing the wrong thing. > > Thanks, > > Hen > - To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org
Re: [Jakarta Standard Taglib] Cactus + Jetty + Maven2
Problem might be because Jetty embeds a copy of JSTL inside itself. Hen On Thu, Apr 23, 2009 at 1:44 AM, Henri Yandell wrote: > I'm frustratingly close to having the Cactus Maven2 plugin working > with the Jetty Maven2 plugin for the Jakarta Standard Taglib. > > Here's what you have to do to replicate my current status: > > > svn co > https://svn.apache.org/repos/asf/jakarta/taglibs/proper/taglibs-parent/trunk > taglibs-parent > cd taglibs-parent > mvn install > cd .. > > svn co https://svn.apache.org/repos/asf/jakarta/taglibs/proper/standard/trunk > standard > cd standard > mvn install > cd standard-test > mvn package integration-test > > The cactus tests are in the subdirectory of standard-test. I know it's > a bit hacky having it as the subdirectory, but it's proof of concept > and then I'll rip things apart in the standard directory and do things > properly. > > Current status is: > > Once you have the taglib parent pom and the jstl+impl combo jar > deployed, the war builds happily, it gets cactified, it goes into > jetty as jetty starts up, surefire kicks in and fails the tests due to > JSP webapp setup reasons. Then jetty turns itself off. > > Oddly, some change I made recently has it doing the war stages > multiple times. Not sure why. > > If anyone gets interested, a second pair of eyes on the JSP webapp > setup reasons would be cool; as would any suggestions on how the > pom.xml could be simplified or is doing the wrong thing. > > Thanks, > > Hen > - To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org
[Jakarta Standard Taglib] Cactus + Jetty + Maven2
I'm frustratingly close to having the Cactus Maven2 plugin working with the Jetty Maven2 plugin for the Jakarta Standard Taglib. Here's what you have to do to replicate my current status: svn co https://svn.apache.org/repos/asf/jakarta/taglibs/proper/taglibs-parent/trunk taglibs-parent cd taglibs-parent mvn install cd .. svn co https://svn.apache.org/repos/asf/jakarta/taglibs/proper/standard/trunk standard cd standard mvn install cd standard-test mvn package integration-test The cactus tests are in the subdirectory of standard-test. I know it's a bit hacky having it as the subdirectory, but it's proof of concept and then I'll rip things apart in the standard directory and do things properly. Current status is: Once you have the taglib parent pom and the jstl+impl combo jar deployed, the war builds happily, it gets cactified, it goes into jetty as jetty starts up, surefire kicks in and fails the tests due to JSP webapp setup reasons. Then jetty turns itself off. Oddly, some change I made recently has it doing the war stages multiple times. Not sure why. If anyone gets interested, a second pair of eyes on the JSP webapp setup reasons would be cool; as would any suggestions on how the pom.xml could be simplified or is doing the wrong thing. Thanks, Hen - To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org
Re: Maven2 + Cactus
Thanks Petar, Are you installing the cargo-maven2-plugin manually? Hen On Tue, Jan 27, 2009 at 12:04 AM, Petar Tahchiev wrote: > Hi Henry. > > I will update the site tonight. Last night I had some problems with the > internet connection. Meanwhile you can use this URL if you want to get the > latest > Tomcat5 release: > > http://apache.speedbone.de/tomcat/tomcat-5/v5.5.27/bin/apache-tomcat-5.5.27.zip > > We also provide an example using the Jetty embedded container. But the fact > is that you will, eventually need a container (Tomcat, JBoss...) and > normally > it is installed already in some place. You can point to that place by > setting the > [home] parameter in the cargo-maven2-plugin. > > Since different people need to set different [home] parameters and some > people > might not even have a container installed, I thought that it would be much > more > simpler if the container is pulled from the internet. You can also avoid > this if you > want with the [home] parameter I just told you about. > > Cheers, Petar > > 2009/1/27 Henri Yandell > >> 1.8.1 release and I was able to get the m2 plugin! >> >> Next problem is that I can't get the cargo-maven2-plugin as listed on >> the Cactus page :) >> >> The Tomcat url listed doesn't work btw - and wouldn't an example that >> pulls from Maven and not a zip, be it Tomcat or Jetty, be cleaner? >> >> Thanks, >> >> Hen >> >> On Sun, Jan 4, 2009 at 5:17 AM, Petar Tahchiev >> wrote: >> > Hi Henry, >> > >> > good to see you on the Cactus dev list :-). >> > It is also good to see someone is taking care of >> > the Taglibs. I myself once migrated Cactus from Ant >> > to M2 so if you find any problems in the migration >> > you can contact me offline. >> > >> > About the cactus-maven2-plugin. Currently the only possible >> > way to get the 1.8.1-SNAPSHOT maven2 plugin is to >> > checkout cactus from the svn and build it. >> > I was hoping to make a 1.8.1 release by the end of December, but the >> point >> > is cactus depends on Maven-assembly-plugin. I started contributing >> > patches to the assembly-plugin to ease the MASSEMBLY release and now I am >> > currently >> > waiting for the Maven guys to push their release (they already >> > casted a vote on the mailing list). >> > >> > The cactus-maven2 plugin can be used only to cactify your war/ear file. >> The >> > rest of the game is >> > taken care of by the Maven-Assmebly plugin and the Cargo plugin. >> > For the cactifywar goal there is a web-page >> > >> > http://jakarta.apache.org/cactus/integration/maven2/cactifywar.html >> > >> > explaining roughly how to use. I was in the process of writing a >> cactifyear >> > web page and I think it >> > is in the SVN. Cactus comes with several sample applications >> > that you can consult to see how they are working. In the 1.8.0 release >> they >> > used to be built with Ant and Ivy, but in the SVN HEAD they are built >> with >> > maven and the >> > cactus-maven2 plugin. Take a look at them and I am sure you will get the >> > idea. >> > >> > I hope I was able to help. >> > >> > See you in March on the ApacheCON :-). >> > >> > Cheers, Petar. >> > >> > 2009/1/4, Henri Yandell : >> >> >> >> I'm throwing some energy into Jakarta Taglibs - moving it to M2. The >> >> Standard Taglib currently uses Cactus, but it seems to me that all of >> >> them should and it would be a good working example for Cactus to point >> >> to, it being so close project wise etc. >> >> >> >> I had a brief dig into Cactus and M2 - following the instructions on the >> >> site: >> >> >> >> http://jakarta.apache.org/cactus/integration/maven2/index.html >> >> >> >> My current problem is that I can't get the 1.8.1-SNAPSHOT maven2 >> >> plugin. It's not on the snapshot repo, and there's no m2 integration >> >> in the central repo. Later problems that the page doesn't cover will >> >> be: >> >> >> >> * How do I run it? >> >> * Where do I put the jsp files to be picked up etc? >> >> >> >> :) >> >> >> >> Any ideas/thoughts would be greatly appreciated, >> >> >> >> Hen >> >> >> >> ---
Re: Maven2 + Cactus
1.8.1 release and I was able to get the m2 plugin! Next problem is that I can't get the cargo-maven2-plugin as listed on the Cactus page :) The Tomcat url listed doesn't work btw - and wouldn't an example that pulls from Maven and not a zip, be it Tomcat or Jetty, be cleaner? Thanks, Hen On Sun, Jan 4, 2009 at 5:17 AM, Petar Tahchiev wrote: > Hi Henry, > > good to see you on the Cactus dev list :-). > It is also good to see someone is taking care of > the Taglibs. I myself once migrated Cactus from Ant > to M2 so if you find any problems in the migration > you can contact me offline. > > About the cactus-maven2-plugin. Currently the only possible > way to get the 1.8.1-SNAPSHOT maven2 plugin is to > checkout cactus from the svn and build it. > I was hoping to make a 1.8.1 release by the end of December, but the point > is cactus depends on Maven-assembly-plugin. I started contributing > patches to the assembly-plugin to ease the MASSEMBLY release and now I am > currently > waiting for the Maven guys to push their release (they already > casted a vote on the mailing list). > > The cactus-maven2 plugin can be used only to cactify your war/ear file. The > rest of the game is > taken care of by the Maven-Assmebly plugin and the Cargo plugin. > For the cactifywar goal there is a web-page > > http://jakarta.apache.org/cactus/integration/maven2/cactifywar.html > > explaining roughly how to use. I was in the process of writing a cactifyear > web page and I think it > is in the SVN. Cactus comes with several sample applications > that you can consult to see how they are working. In the 1.8.0 release they > used to be built with Ant and Ivy, but in the SVN HEAD they are built with > maven and the > cactus-maven2 plugin. Take a look at them and I am sure you will get the > idea. > > I hope I was able to help. > > See you in March on the ApacheCON :-). > > Cheers, Petar. > > 2009/1/4, Henri Yandell : >> >> I'm throwing some energy into Jakarta Taglibs - moving it to M2. The >> Standard Taglib currently uses Cactus, but it seems to me that all of >> them should and it would be a good working example for Cactus to point >> to, it being so close project wise etc. >> >> I had a brief dig into Cactus and M2 - following the instructions on the >> site: >> >> http://jakarta.apache.org/cactus/integration/maven2/index.html >> >> My current problem is that I can't get the 1.8.1-SNAPSHOT maven2 >> plugin. It's not on the snapshot repo, and there's no m2 integration >> in the central repo. Later problems that the page doesn't cover will >> be: >> >> * How do I run it? >> * Where do I put the jsp files to be picked up etc? >> >> :) >> >> Any ideas/thoughts would be greatly appreciated, >> >> Hen >> >> - >> To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org >> For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org >> >> > > > -- > Regards, Petar! > Karlovo, Bulgaria. > - - - - - - - - > | Author @ Manning Publications. > | Senior Solution Architect @ Unic > | BGJUG-Bulgarian Java User Group Leader. > | 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 > - To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org
Typo in pom
Typo in Project: [INFO] Cactus Uberjars - Parent Projcet Presumably it's in the name in the pom, but figured it's simpler to mention than dig into the source to find it. Hen - To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org
Maven2 + Cactus
I'm throwing some energy into Jakarta Taglibs - moving it to M2. The Standard Taglib currently uses Cactus, but it seems to me that all of them should and it would be a good working example for Cactus to point to, it being so close project wise etc. I had a brief dig into Cactus and M2 - following the instructions on the site: http://jakarta.apache.org/cactus/integration/maven2/index.html My current problem is that I can't get the 1.8.1-SNAPSHOT maven2 plugin. It's not on the snapshot repo, and there's no m2 integration in the central repo. Later problems that the page doesn't cover will be: * How do I run it? * Where do I put the jsp files to be picked up etc? :) Any ideas/thoughts would be greatly appreciated, Hen - To unsubscribe, e-mail: cactus-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: cactus-dev-h...@jakarta.apache.org
Board report
Could a board report be filled out for Cactus this month: http://wiki.apache.org/jakarta/JakartaBoardReport-June2006 See previous quarters for a feel as to what to talk about. Primarily it is the release but any other info is good. http://jakarta.apache.org/site/pmc/board-reports.html Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] Jakarta Cactus/JMeter -> testing.apache.org
I didn't see a vote from Rahul, but did notice he was on the wiki page. Decided that was a good thing - it would have felt pretty bad to have 3 votes moving it to TLP when I know that the active community is larger than that. Hen On Mon, 17 Apr 2006, Felipe Leme wrote: Hi Hen, Didn't Rahul voted as well? I mean, he added his name on the wiki page, I guess he thought that would imply a vote. Anyway, the overall vote was really low, so I'm not sure if it worths pushing it ahead. OTOH, I this move could help renew the projects energies (for instance, there's been some new guys interested to help on the cargo and maven 2 integration for Cactus). -- Felipe Henri Yandell wrote: Closing this vote down as a failed vote; not enough +1s to proceed: +1s Felipe Leme Peter Lin [EMAIL PROTECTED] (non-binding) +0s Sebastian Bazeley Vincent Massol So JMeter/Cactus to stay where they are at the moment. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] Jakarta Cactus/JMeter -> testing.apache.org
Closing this vote down as a failed vote; not enough +1s to proceed: +1s Felipe Leme Peter Lin [EMAIL PROTECTED] (non-binding) +0s Sebastian Bazeley Vincent Massol So JMeter/Cactus to stay where they are at the moment. Hen On 3/24/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > If you vote +1 and want to be a part of the new Testing project, could > you add your name to the proposal please. I've added my name so that I > can help out with any migrational teething troubles, and to be an ASF > member who is paying attention to the project [the board like to see > some ASF members being aware of each project]. > > http://wiki.apache.org/jakarta/TLPCactusAndJMeter > > Felipe Leme has volunteered to be chair, though I'll let him add > himself to the wiki page in place of the mysterious . > > So, > > [ ] +1 > [ ] -1 because... > > > Hen > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Jakarta Cactus/JMeter -> testing.apache.org
If you vote +1 and want to be a part of the new Testing project, could you add your name to the proposal please. I've added my name so that I can help out with any migrational teething troubles, and to be an ASF member who is paying attention to the project [the board like to see some ASF members being aware of each project]. http://wiki.apache.org/jakarta/TLPCactusAndJMeter Felipe Leme has volunteered to be chair, though I'll let him add himself to the wiki page in place of the mysterious . So, [ ] +1 [ ] -1 because... Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What's a chair?
Following on from the last email - the major question would be whether anyone would like to volunteer as a chair? The question was raised on the Hivemind list as to what a chair actually entailed. My reply is below - I'd be happy to join the PMC mailing list (lurk, rather than be on the PMC) to help with any issues that might arise post-promotion. Because testing is a little bit of an umbrella (like logging.apache.org) - the chair role will be a bit more than Hivemind will be; but still not as much a bureacracy as xml/webservices/jakarta. Hen -- Forwarded message -- From: Henri Yandell <[EMAIL PROTECTED]> Date: Mar 17, 2006 11:05 PM Subject: Re: [DICUSS] Move from Jakarta to Tapestry PMC? To: hivemind-dev@jakarta.apache.org Jakarta is a very bad example of the role of a chair - umbrellas create a lot of bureacracy and I make the mistake of letting myself get sucked into it. Ideally the chair role is: 1) Organizing the move to TLP. Howard's going through this one at the moment. It's basically a set of infra requests and tasks. I'm semi-Infra nowadays, so can help move these things along if you nudge me. First off though: Have a vote to move to TLP, have 3 Jakarta PMC members on that vote, inform the PMC. Then write a resolution (copy Tapestry's) that I can submit to the board. 2) Subscribing to [EMAIL PROTECTED] As with any list it goes through ups and downs in terms of noise. Currently it's quite quiet. 3) Sending in a board report every three months (every month for the first three months). In the case of tight TLP, like hivemind.apache.org, this is an easy thing to do (I think). You know what's going on and you don't have to spend weeks chasing up on things, you just sit down and write it, let the PMC see the draft a little bit in advance and send it in. They're often about 6 lines long, not the behemoth that the Jakarta report is. It's really not that big a deal. I'll also be joining the pmc list (unless you'd prefer me not to) and can help out if you hit any issues. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TLP proposal
Anyone mind if I go ahead and organize a TLP resolution (on the wiki) for a testing.apache.org that Cactus/JMeter committers can then sign their names up to as PMC members etc? Reflecting on what the chair role is, there's more organization involved in getting out of Jakarta than there is in anything you've got to do once you're out. Given that I'm the one looking to simplify my role, it seems fair that I should put the effort in instead of giving you guys pain. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE} Cactus 1.7.2 release
Just to confirm - this is now released right? Problem solved? Hen On 3/8/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > +1 > > -Rahul > > > On 3/7/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Sorry for not pushing it ahead before, but I've prepared a new release: > > > > http://people.apache.org/~felipeal/tmp/cactus/ > > > > The current votes are: > > > > 2 binding +1 (PMC members): > > > > - Felipe Leme > > - Vincent Massol > > > > 2 non-binding +1 (committers only): > > > > - Magnus Grimsell > > - Kazuhito SUGURI > > > > I'll wait 'till some other PMC member (*cough* Hen *cough) member vote a > > +1 to send the results to the PMC list; meanwhile, if some of you guys > > could please test those zips, I would appreciate... > > > > []s, > > > > -- Felipe > > > > > > Felipe Leme wrote: > > > Due to the 'legal bug' of Cactus 1.7 and Cactus 1.7.1 had bundled a LGPL > > > jar, I propose we release Cactus 1.7.2 - other than the aforementioned > > > issue, technically speaking the only change was a new property for the > > > Maven plugin (see http://issues.apache.org/jira/browse/CACTUS-231). > > > > > > So, here is the ballot: > > > > > > [ ] +1 - Release Cactus 1.7.2 > > > [ ] -1 - Don't release it (and explain why) > > > > > > -- Felipe > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE} Cactus 1.7.2 release
+1. On 3/7/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > Hi all, > > Sorry for not pushing it ahead before, but I've prepared a new release: > > http://people.apache.org/~felipeal/tmp/cactus/ > > The current votes are: > > 2 binding +1 (PMC members): > > - Felipe Leme > - Vincent Massol > > 2 non-binding +1 (committers only): > > - Magnus Grimsell > - Kazuhito SUGURI > > I'll wait 'till some other PMC member (*cough* Hen *cough) member vote a > +1 to send the results to the PMC list; meanwhile, if some of you guys > could please test those zips, I would appreciate... > > []s, > > -- Felipe > > > Felipe Leme wrote: > > Due to the 'legal bug' of Cactus 1.7 and Cactus 1.7.1 had bundled a LGPL > > jar, I propose we release Cactus 1.7.2 - other than the aforementioned > > issue, technically speaking the only change was a new property for the > > Maven plugin (see http://issues.apache.org/jira/browse/CACTUS-231). > > > > So, here is the ballot: > > > > [ ] +1 - Release Cactus 1.7.2 > > [ ] -1 - Don't release it (and explain why) > > > > -- Felipe > > - > 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]
Reminder to subscribe to general@
We're discussing various ideas and thoughts on restructuring Jakarta on the [EMAIL PROTECTED] mailing list. On the off chance that someone isn't subscribed to the general@jakarta.apache.org mailing list, I thought I'd drop an email to each of the -dev mailing lists so they have a chance to be involved. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Result] Migrate Cactus to another TLP
(I added my vote, so 3 bindings). Need to get a proposal written, then call for a vote on [EMAIL PROTECTED] Here's the Tomcat TLP vote, which includes an example of the proposal. The wording is important, what you're writing is a board resolution to be voted on at the next board meeting [3rd Wednesday of the month from memory]. http://mail-archives.apache.org/mod_mbox/jakarta-general/200504.mbox/[EMAIL PROTECTED] So, Cactus/JMeter subprojects decide informally (vote, whatever you want to do) to goto TLP and draft a proposal (I suggest Cactus drafts the proposal and takes it to jmeter-dev as you guys decided first). Jakarta as a whole (or rather the PMC members on general@) vote on whether they want to send it to the board. Chair takes it to the board, they vote on it. TLP happens. Hen On 1/10/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > The proposal has been approved; here are the results: > > 2 binding committers on PMC votes: > > +1A Felipe Leme > +1A (or +1B) Vincent Massol > > 2 non-binding committer votes: > > +1A Magnus Grimsell > +1A Kenney Westerhof > > 6 non-binding user votes (I've accidentally sent the proposal to the > user list as well): > > +1A Chris Allen > +1A Masibonge Matimba > +1A Oukhemanou Clement > +1A Rostislav Svoboda > +1A Zhong ZHENG > +1A Pedro Nevada > > We didn't get 3 binding votes, but got 4 committer votes, which is > enough (considering we don't have many active committers right now). > > For the PMC's record, the thread is available here: > > http://www.mail-archive.com/cactus-dev%40jakarta.apache.org/msg07820.html > > -- Felipe > > > On 1/4/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > > > > > Hi all, > > > > As we discussed previously in this list, there's been a 'movement' to > > upgrade Jakarta sub-projects to new TLPs (top-level projects) and Henri > > suggested that Cactus should be a TLP on its own or join forces with > > JMeter to create a new Apache Testing TLP (which some of us agreed qould > > be a better option, to bring momentum back to the project) > > So, I'm formalizing these options as a vote: > > > > [ ] -1 leave Cactus on Jakarta > > [ ] +1A move Cactus to a new Apache Testing TLP > > [ ] +1B create the Cactus TLP > > [ ] ?? << other options >> > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate Cactus to another TLP
+1A On 1/4/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > Hi all, > > As we discussed previously in this list, there's been a 'movement' to > upgrade Jakarta sub-projects to new TLPs (top-level projects) and Henri > suggested that Cactus should be a TLP on its own or join forces with > JMeter to create a new Apache Testing TLP (which some of us agreed would > be a better option, to bring momentum back to the project) > So, I'm formalizing these options as a vote: > > [ ] -1 leave Cactus on Jakarta > [ ] +1A move Cactus to a new Apache Testing TLP > [ ] +1B create the Cactus TLP > [ ] ?? << other options >> > > Here is my +1A > > -- Felipe > > PS: I've sent this message originally to the users list - my bad... > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrate Cactus to another TLP
On 1/4/06, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Felipe Leme [mailto:[EMAIL PROTECTED] > > Sent: mercredi 4 janvier 2006 10:25 > > To: Cactus Developers List > > Subject: [VOTE] Migrate Cactus to another TLP > > > > Hi all, > > > > As we discussed previously in this list, there's been a 'movement' to > > upgrade Jakarta sub-projects to new TLPs (top-level projects) and Henri > > suggested that Cactus should be a TLP on its own or join forces with > > JMeter to create a new Apache Testing TLP (which some of us agreed would > > be a better option, to bring momentum back to the project) > > So, I'm formalizing these options as a vote: > > > > [ ] -1 leave Cactus on Jakarta > > [ ] +1A move Cactus to a new Apache Testing TLP > > [ ] +1B create the Cactus TLP > > [ ] ?? << other options >> > > +1 (either A or B. If A can be done relatively easily then I'm +1A). > > Note that once we finish the vote on the cactus list we'll need to send > another vote on the Jakarta PMC list as Cactus is still part of Jakarta. We > may also need to ask on Jakarta General WRT the testing TLP. Just to let you know, JMeter have agreed that testing.apache.org would be best for them. I've told them that I'll ask you guys to drive the drafting of a TLP proposal. Once your vote is complete here (presumably positively), if you could work on a draft to your satisfaction, get the JMeter guys happy and post to [EMAIL PROTECTED]; then we can have a vote on [EMAIL PROTECTED] on the agreed upon proposal. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Legal issue with jboss-j2ee jar
On 1/6/06, Felipe Leme <[EMAIL PROTECTED]> wrote: > Hi Vincent, > > I don't see an issue here - we just need the jars to compile Cactus, we > don't need to redistribute them, right? If so, I think we're fine with > JBoss jars (we just need to change our build to not redistribute them)... I think that would be fine. I'll check with Cliff tomorrow if I can keep it in the front of my mind. Also need to get them out of the old builds etc :) But that's just zip -d if it's not actually needed. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TLP thoughts...
On 12/13/05, Felipe Leme <[EMAIL PROTECTED]> wrote: > On 12/12/05, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > > The other is to jmeter-dev@ in which I raised the question of a > > testing.apache.org (or similar name) that might be a location for > > JMeter and Cactus to live together. This seems quite nice from a point > > > By speaking of a testing TLP, there's been some discussion on the DBUnit > project (which is hosted at SourceForge) about migrating it to ASF, due to > the SF infrastructure issues and to the fact that many DBUnit committers are > ASF committers as well. I could raise the ball again, this time proposing it > to be incubated on this new TLP. > > Why do you think? I'm non-binding, but it all sounds good to me :) Leaderwise, there would need to be one for testing.apache (if that was the way things went) instead of cactus. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
TLP thoughts...
This is a side-effect of another couple of emails: One to general@ in which I mentioned that I wanted to more actively talk about TLP with some of the subprojects, find out what the reasons to stay in Jakarta would be, and ideally end up with a reusable component like Jakarta. The other is to jmeter-dev@ in which I raised the question of a testing.apache.org (or similar name) that might be a location for JMeter and Cactus to live together. This seems quite nice from a point of view of the projects' activity levels, but I suspect I'm inventing things that don't exist. Anyway. What thoughts would Cactus have on TLP, alone, something with JMeter or something else? Just trying to generate some thoughts :) Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn, maven 1 & 2, project restructuration
Okay, done. http://svn.apache.org/repos/asf/jakarta/cactus/ svn co https://svn.apache.org/repos/asf/jakarta/cactus/trunk jakarta-cactus Mail notifications should go happily to [EMAIL PROTECTED] and then to [EMAIL PROTECTED] Authentication is copied over from the CVS side. You should be good to go :) Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn, maven 1 & 2, project restructuration
On 8/22/05, Henri Yandell <[EMAIL PROTECTED]> wrote: > On 8/22/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > > > > -----Original Message- > > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > > Sent: dimanche 21 août 2005 19:02 > > > To: Cactus Developers List > > > Subject: Re: svn, maven 1 & 2, project restructuration > > > > [snip] > > > > > Regardless of the answer on this one, it's probably best for this to > > > be a post-migration discussion. > > > > > > Once you get to Subversion, you can use 'svn move' to rearrange things > > > and keep a history of how it used to be, and how it became. As there's > > > only 1 cvs module involved here, and the split is only from 1 to 2, > > > that would be my advice :) > > > > There has been no scream from the other committers and Nicolas is ok with > > the structure (see his last email) so as everyone has already voted +1 for > > migrating to SVN I think we're all set now. > > > > Henri, could you please make your test SVN the main Cactus SVN? > > > > I think we're now at step 8 of http://apache.org/dev/cvs2svn.html. > > > > Could we now move to step 9? > > Should be doing it sometime in the next 4 hours. Monday mornings are > always a bit unpredictable and if I started now I'd put getting to > work in jeopardy (which would be oh so terrible :) ). Local network was taken down halfway through it. Bit of a surprise for me :( I'm going to back off for an hour and try again after lunch, hoping that the read-only state of CVS isn't a big deal for you. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn, maven 1 & 2, project restructuration
On 8/22/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > -Original Message----- > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > Sent: dimanche 21 août 2005 19:02 > > To: Cactus Developers List > > Subject: Re: svn, maven 1 & 2, project restructuration > > [snip] > > > Regardless of the answer on this one, it's probably best for this to > > be a post-migration discussion. > > > > Once you get to Subversion, you can use 'svn move' to rearrange things > > and keep a history of how it used to be, and how it became. As there's > > only 1 cvs module involved here, and the split is only from 1 to 2, > > that would be my advice :) > > There has been no scream from the other committers and Nicolas is ok with > the structure (see his last email) so as everyone has already voted +1 for > migrating to SVN I think we're all set now. > > Henri, could you please make your test SVN the main Cactus SVN? > > I think we're now at step 8 of http://apache.org/dev/cvs2svn.html. > > Could we now move to step 9? Should be doing it sometime in the next 4 hours. Monday mornings are always a bit unpredictable and if I started now I'd put getting to work in jeopardy (which would be oh so terrible :) ). Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn, maven 1 & 2, project restructuration
On 8/21/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > So far we've always released all the Cactus components together. I guess you > are proposing to release them separately and that's why you're proposing > this organization, is that it? > > I'm not sure that releasing the components separately would require breaking > the project into several SVN modules. You can do that within a single SVN > module. It has the advantage of keeping the whole project cohesive. Also it > makes it simpler for anyone building the sources. Regardless of the answer on this one, it's probably best for this to be a post-migration discussion. Once you get to Subversion, you can use 'svn move' to rearrange things and keep a history of how it used to be, and how it became. As there's only 1 cvs module involved here, and the split is only from 1 to 2, that would be my advice :) Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn, maven 1 & 2, project restructuration
On 8/20/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > - We have to move to SVN anyway as this is an Apache directive and we're > asked to migrate quickly . I don't remember the exact deadline but it's not > in a very long time (a few months). End of the year, though my target is to wrap everything up by the December ApacheCon. > - The cvs2svn script used to migrate to SVN does not loose history AFAIK. Yep, history stays by default. > - See http://apache.org/dev/cvs2svn.html for a migration checklist > > - Henri Yandell will be very happy to help as he's been pushing us to > migrate for some time... I'm cc-ing him even though I'm sure he would catch > this email without the cc... :-) It would have taken a few more days. I browse the dev mail lists for interesting topics in gmail, but takes a while to do a full loop. > - We have already voted for the SVN migration so we just need to do it. I've loaded a snapshot of Cactus into the test repository. http://svn.apache.org/repos/test/jakarta/cactus/ svn co https://svn.apache.org/repos/test/jakarta/cactus/trunk jakarta-cactus Have a look and decide if: * It looks like everything is there (branches etc) and it still works (ignoring the CVS change report) * You're happy with the default structure of branches/tags/trunk. Most of the ASF projects use this, with the difference usually being because they have subprojects of some kind (commons, turbine, taglibs etc). It also gives a everyone a chance to figure out how they want to connect to subversion (IDE, gui, command line, tortoise etc etc) and give it a go. Then we just need to decide when to make the change. It looks like it'll be nice routine easy one. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Welcome to Xuan!
On 7/1/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi Cactus devs, > > Let me introduce Xuan. Xuan has decided to help us by migrating the Cactus > Ant and Maven integrations to use Cargo (http://cargo.codehaus.org). This is > thanks to Google's Summer Of Code initiative. Xuan had chosen to work on the > Cargo codebase itself but since we had 3 persons in total for Cargo we've > decided to reshuffle the assignments and Xuan proposed to work on migrating > Cactus to Cargo. Dumb question time. Is this a part of the Summer of Code initiative, or just a spin-off? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrating to Subversion
On 6/20/05, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Mon, 20 Jun 2005, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > Looks like Stefan's svnchangelog task might take care of the 3 > > issues I list, and should handle excludes as it's based on the Ant > > fileset system. > > It's not mine, it is ours ;-) > > I've modelled the task itself as well as the XML output to match > cvschangelog as closely as possible. Since then I've basically > stopped working on it completely, I'm more than a bit swamped right > now. > > Help is certainly welcome. > > > I'll mail Ant to find out when that's likely to find its way into an > > Ant release. > > The plan is to have antlibs that get released independent of Ant > itself. That's what the sandbox is about. To make that happen, we'll > need more people endorse the sandbox code so that it gets "promoted" > out of the sandbox (very much Jakarta Commons like) and release it. Taking this (along with Stefan's reply on the Ant list that it's unlikely that the svn task will be released in Ant itself), the idea of waiting for Ant to support SVN for the cvschangelog task looks a bit endless. Any thoughts on where to go from here? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrating to Subversion
On 6/7/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > -Original Message----- > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > Sent: mardi 7 juin 2005 15:24 > > To: Vincent Massol > > Cc: Cactus Developers List > > Subject: Re: [VOTE] Migrating to Subversion > > > > Grep and I are unable to find the cvs task being used in the Cactus > > build (at least for the top three directories). > > Are we talking about the cvschangelog task in documentation/build.xml? > > Yes that's the one I had in mind. I posted to the Ant list to see if anyone had solved this before, but sadly not. However, it seems to me that it might be solveable. One of the svn features is that you can get the log in xml format, so an old cvs changelog in xml goes from: 2005-05-08 11:04 downloads.xml 1.17 vmassol 2005-05-08T11:04:00.00Z /full/path/to/downloads.xml Improved download link that goes directly to the Cactus download page on Jakarta. or something much like that. The obvious differences being a lack of CDATA and the fact it'll use the login name and not the user's full name (via /etc/passwd I presume). The first is probably not a problem, I imagine SVN correctly escapes its output, and the second seems to be okay as Cactus doesn't show that data on their changes page (http://jakarta.apache.org/cactus/changes.html). So changing the cvschangelog task to be an exec of 'svn log -v --xml', and modifying the xsl in documentation/docs/skins/jakarta.apache.org/stylesheets/document2html.xsl to handle the different style of input, could do the trick. Still not a piece of cake. Splitting the date, throwing away the unnecessary parts of the path and handling commits that contain more than one file are all issues to be handled, and in a functional language like XSL, they can be oddly painful. Also, there's no obvious way to exclude the 5 excluded files: Looks like Stefan's svnchangelog task might take care of the 3 issues I list, and should handle excludes as it's based on the Ant fileset system. I'll mail Ant to find out when that's likely to find its way into an Ant release. An obvious other suggestion is to comment out the cvs-changelog table for the site between the period of moving to svn and the period of a task existing to easily turn it back on again. Or switch to using the changes.xml style for the site as well and managing it by hand. Neither highly desirable, but thought I'd bring them up. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrating to Subversion
Grep and I are unable to find the cvs task being used in the Cactus build (at least for the top three directories). Are we talking about the cvschangelog task in documentation/build.xml? Could be that you've changed it already too :) Hen On 5/27/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > Hi Henri, > > Actually we have enough positive votes to make it happen. However, I've just > realized that we are using the Ant task in our build and I would be > more comfortable if we had a replacement before going on with the migration. > > I also don't have much time right now to do the migration so I'd suggest > holing off a bit while waiting for the Ant task to be integrated into > Ant (it doesn't seem to be in Ant 1.6.4). I would rather not have builders > have to install an additional jar to get an svn task. > > Would that be fine with everyone? > > If someone wants to perform the migration please stand up! (that involves > having a build solution at least as good as what we currently have). > > Thanks > -Vincent > > > > -Original Message- > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > Sent: jeudi 26 mai 2005 23:52 > > To: Cactus Developers List; [EMAIL PROTECTED] > > Subject: Re: [VOTE] Migrating to Subversion > > > > Is this effectively a go for a subversion migration? I'm unsure how > > much of the active Cactus community these votes represent. > > > > Hen > > > > On 5/9/05, Lesiecki Nicholas <[EMAIL PROTECTED]> wrote: > > > +0 > > > --- Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > Apache is slowly migrating all its projects to Subversion and they're > > > > asking > > > > us if we want to do it for Cactus. I've personally used SVN on several > > > > projects and it's great. The tools are slightly behind compared to CVS > > > > but > > > > they are quite usable (TortoiseSVN for windows, subclipe for Eclipse, > > > > etc). > > > > > > > > Please cast your vote: > > > > > > > > [] +1 Let's do it! > > > > [] 0 I don't mind > > > > [] -1 I have a problem migrating. Please state the reason. > > > > > > > > Here's my +1 > > > > > > > > Thanks > > > > -Vincent > > > > > > > > > > > > > > > > - > > > > 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] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > _ > Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, > photos et vidéos ! > Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Migrating to Subversion
Is this effectively a go for a subversion migration? I'm unsure how much of the active Cactus community these votes represent. Hen On 5/9/05, Lesiecki Nicholas <[EMAIL PROTECTED]> wrote: > +0 > --- Vincent Massol <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Apache is slowly migrating all its projects to Subversion and they're > > asking > > us if we want to do it for Cactus. I've personally used SVN on several > > projects and it's great. The tools are slightly behind compared to CVS > > but > > they are quite usable (TortoiseSVN for windows, subclipe for Eclipse, > > etc). > > > > Please cast your vote: > > > > [] +1 Let's do it! > > [] 0 I don't mind > > [] -1 I have a problem migrating. Please state the reason. > > > > Here's my +1 > > > > Thanks > > -Vincent > > > > > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subversion migration
Pinging this back onto your todo list. 2 is the big one. The easy option is to just: * move jakarta-cactus HEAD to jakarta/cactus/trunk * move all jakarta-cactus branches to jakarta/cactus/branches * move all jakarta-cactus tags to jakarta/cactus/tags Otherwise it'll take thought etc. Looking at the cactus module, it looks like you would probably take the easy option and worry about being clever later on. Hen On 1/4/05, Henri Yandell <[EMAIL PROTECTED]> wrote: > The Infrastructure guys take care of all the server-side stuff; it's > very easy from our point of view: > > 1) Convince community to migrate > 2) Decide on structure > 3) Send request to Infra (template to do this with) > 4) Organise community to test the repo they setup > 5) Announce go-ahead > > Also things like updating the site etc. > > Hen > > On Tue, 4 Jan 2005 08:16:53 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > > > > -Original Message- > > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > > Sent: mardi 4 janvier 2005 04:13 > > > To: Cactus Developers List > > > Subject: Re: Subversion migration > > > > > > Yep, Apache's on the https/http. Quite a nice setup too. > > > > > > For osjava; we have the http as anonymous and the https as secure; but > > > Apache has the https as anonymous too for most modules and it's only > > > when you commit that you have to enter a username/password. > > > > > > Nice part here is that a contributor can be checked out; become a > > > committer and not have to worry about rechecking out. > > > > > > As you've SVN experience, would you be willing to volunteer to manage > > > the migration Vincent? > > > > Why not, but I would need some help as I have never touched the server-side > > part of SVN (only the client part). > > > > Thanks > > -Vincent > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[site] New Jakarta download pages
(Bcc'd to all Jakarta dev lists) Partly an announcement that the Jakarta download pages have been changed somewhat. Rather than one huge page, it's a whole set of pages. So when time comes to do your next release, you modify site/downloads/downloads.xml and run ant. Source, binary and nightly-builds are all part of the same page. More importantly, a suggestion that projects should no longer link to the top download page, but instead link to their particular download page. So POI would link to: http://jakarta.apache.org/site/downloads/downloads_poi.cgi Commons would link to: http://jakarta.apache.org/site/downloads/downloads_commons.html Commons IO would link to: http://jakarta.apache.org/site/downloads/downloads_commons-io.cgi and so on. The new pages should be exact matches to the previous binindex and sourceindex pages. One requested improvement is for filenames to be specified rather than '1.0.zip'. Hopefully we can make that change globally by figuring out the xslt to get the filename from a url. Another improvement is to add the cvs.apache.org/snapshot/velocity, and any other live snapshots as Nightly Builds. Apologies for the cross-list posting, wanted to make sure everybody got the memo about changing the download links if they want. :) Please direct replies back to the general list. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subversion migration
The Infrastructure guys take care of all the server-side stuff; it's very easy from our point of view: *) Convince community to migrate *) Decide on structure *) Send request to Infra (template to do this with) *) Organise community to test the repo they setup *) Announce go-ahead Also things like updating the site etc. Hen On Tue, 4 Jan 2005 08:16:53 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > Sent: mardi 4 janvier 2005 04:13 > > To: Cactus Developers List > > Subject: Re: Subversion migration > > > > Yep, Apache's on the https/http. Quite a nice setup too. > > > > For osjava; we have the http as anonymous and the https as secure; but > > Apache has the https as anonymous too for most modules and it's only > > when you commit that you have to enter a username/password. > > > > Nice part here is that a contributor can be checked out; become a > > committer and not have to worry about rechecking out. > > > > As you've SVN experience, would you be willing to volunteer to manage > > the migration Vincent? > > Why not, but I would need some help as I have never touched the server-side > part of SVN (only the client part). > > Thanks > -Vincent > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subversion migration
Yep, Apache's on the https/http. Quite a nice setup too. For osjava; we have the http as anonymous and the https as secure; but Apache has the https as anonymous too for most modules and it's only when you commit that you have to enter a username/password. Nice part here is that a contributor can be checked out; become a committer and not have to worry about rechecking out. As you've SVN experience, would you be willing to volunteer to manage the migration Vincent? Hen On Mon, 3 Jan 2005 08:05:04 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote: > > > > -Original Message- > > From: Henri Yandell [mailto:[EMAIL PROTECTED] > > Sent: dimanche 2 janvier 2005 23:49 > > To: cactus-dev@jakarta.apache.org > > Subject: Subversion migration > > > > Just wondering if the Cactus community have any thoughts on a > > migration to Subversion? > > I'm personally all for it. I've tried it on Cargo > (http://cargo.codehaus.org) and I like SVN a lot. > > Now it all depends on the other committers. It should not prevent them from > contributing. > > +1 from me > > Note: The only drawback I can think of is if you use the svn+ssh protocol. > In that case, the existing SVN IDE clients do not perform well (TortoiseSVN > is about the only one to work). But I think apache is using http/https so > that's fine. > > [snip] > > Thanks > -Vincent > > > - > 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]
Subversion migration
Just wondering if the Cactus community have any thoughts on a migration to Subversion? I'm aiming to get Jakarta migrated over to Subversion this quarter and this email is intended to nudge the start of the Cactus migration. The process seems pretty easy, though I'm not finished on my first one (jakarta-regexp): http://www.apache.org/dev/cvs2svn.html Alternatively, I'm looking to hear the problems with the idea of a migration to SVN so I can get the Infrastructure guys to deal with them. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
