RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good idea to me, but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to the release repository, ending at iBiblio. Should this be told to the projects that had uploaded snapshots to ibiblio? I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/ Regards. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:08 PM To: Struts Users Mailing List Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote: Hi, Will you deploy it and the struts-el on the apache maven repository? http://www.apache.org/dist/java-repository/struts/jars/ I would argue that it doesn't belong in that location until it is voted a full GA release. Then again, reviewing what seems to be the official word on using the Apache repositories (http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469), it simply says that location is for versioned releases as opposed to nightly builds. For what it's worth, I think that the intention is not that Maven users would have http://www.apache.org/dist/java-repository/ as a repository, but rather than they'd use iBiblio, which is mirrored from that. I don't know if anyone feels strongly about it, but that's how I read the previously cited email. If we don't put Struts 1.2.1 on iBiblio, we should definitely put it at http://cvs.apache.org/builds/java-repository/ I'll do either one, but I'll wait to see if a few opinions roll in before taking action. Joe I have built it from cvs sources with maven and the size is not the same. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Sunday, July 11, 2004 9:11 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [ANN] Struts 1.2.1 (Beta) Released The Struts team announces the release of Struts 1.2.1, currently ranked at Beta quality. This release removes many features deprecated in prior releases (Struts 1.1 and Struts 1.0.2) and also provides several new features. Fixes to known problems have been applied. More detail is available at * http://struts.apache.org/userGuide/release-notes.html The binary, source, and library distributions are available at * http://cvs.apache.org/dist/struts/v1.2.1/ The library distribution contains only the requisite JARs, without the documentation or example applications. We invite your comments on how well this release works with your own applications. Based on feedback from the Struts community, this release may be dubbed ready for prime time and promoted to General Availabilty quality. Please note that Struts now uses Tomcat-style releases. If the feedback on this release were positive, Struts 1.2.1 may be promoted directly to GA, without creating yet-another distribution. If a serious problem were found and fixed, then we will issue Struts 1.2.2 and try again. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM To: Struts DEV Mailing List Cc: Carlos Sanchez Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good idea to me, but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to the release repository, ending at iBiblio. Should this be told to the projects that had uploaded snapshots to ibiblio? I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/ Regards. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:08 PM To: Struts Users Mailing List Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote: Hi, Will you deploy it and the struts-el on the apache maven repository? http://www.apache.org/dist/java-repository/struts/jars/ I would argue that it doesn't belong in that location until it is voted a full GA release. Then again, reviewing what seems to be the official word on using the Apache repositories (http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469), it simply says that location is for versioned releases as opposed to nightly builds. For what it's worth, I think that the intention is not that Maven users would have http://www.apache.org/dist/java-repository/ as a repository, but rather than they'd use iBiblio, which is mirrored from that. I don't know if anyone feels strongly about it, but that's how I read the previously cited email. If we don't put Struts 1.2.1 on iBiblio, we should definitely put it at http://cvs.apache.org/builds/java-repository/ I'll do either one, but I'll wait to see if a few opinions roll in before taking action. Joe I have built it from cvs sources with maven and the size is not the same. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Sunday, July 11, 2004 9:11 PMTo: [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: [ANN] Struts 1.2.1 (Beta) Released The Struts team announces the release of Struts 1.2.1, currently ranked at Beta quality. This release removes many features deprecated in prior releases (Struts 1.1 and Struts 1.0.2) and also provides several new features. Fixes to known problems have been applied. More detail is available at * http://struts.apache.org/userGuide/release-notes.html The binary, source, and library distributions are available at * http://cvs.apache.org
Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
Hey Guys, Yes this is all very good. Definity organize everthing in the /www/cvs.apache.org/repository until you are confident that everything is in its proper place, the biggest issue we encounter is broken symlinks and bad md5 signatures. Once everything is layed out the way you want it and your ready to release, just copy it into /www/www.apache.org/dist/java-repository/... which is rsynced to ibibilio every 4 hours. Make sure premissions are group 'rw' for apcvs and all 'r' once you place it into the official repository location directory. cheers, Mark Carlos Sanchez wrote: Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM To: Struts DEV Mailing List Cc: Carlos Sanchez Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good idea to me, but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to the release repository, ending at iBiblio. Should this be told to the projects that had uploaded snapshots to ibiblio? I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/ Regards. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:08 PM To: Struts Users Mailing List Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote: Hi, Will you deploy it and the struts-el on the apache maven repository? http://www.apache.org/dist/java-repository/struts/jars/ I would argue that it doesn't belong in that location until it is voted a full GA release. Then again, reviewing what seems to be the official word on using the Apache repositories (http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469), it simply says that location is for versioned releases as opposed to nightly builds. For what it's worth, I think that the intention is not that Maven users would have http://www.apache.org/dist/java-repository/ as a repository, but rather than they'd use iBiblio, which is mirrored from that. I don't know if anyone feels strongly about it, but that's how I read the previously cited email. If we don't put Struts 1.2.1 on iBiblio, we should definitely put it at http://cvs.apache.org/builds/java-repository/ I'll do either one, but I'll wait to see if a few opinions roll in before taking action. Joe I have built it from cvs sources with maven and the size is not the same. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Sunday, July 11, 2004 9:11 PMTo: [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: [ANN
RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
You don't need to care about copying or md5 signatures, just use maven! With maven jar:deploy the jar is built and uploaded to the repository in its proper place and with signatures. -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 8:44 PM To: Struts Developers List Subject: Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) Hey Guys, Yes this is all very good. Definity organize everthing in the /www/cvs.apache.org/repository until you are confident that everything is in its proper place, the biggest issue we encounter is broken symlinks and bad md5 signatures. Once everything is layed out the way you want it and your ready to release, just copy it into /www/www.apache.org/dist/java-repository/... which is rsynced to ibibilio every 4 hours. Make sure premissions are group 'rw' for apcvs and all 'r' once you place it into the official repository location directory. cheers, Mark Carlos Sanchez wrote: Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM To: Struts DEV Mailing List Cc: Carlos Sanchez Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good idea to me, but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to the release repository, ending at iBiblio. Should this be told to the projects that had uploaded snapshots to ibiblio? I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/ Regards. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:08 PM To: Struts Users Mailing List Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote: Hi, Will you deploy it and the struts-el on the apache maven repository? http://www.apache.org/dist/java-repository/struts/jars/ I would argue that it doesn't belong in that location until it is voted a full GA release. Then again, reviewing what seems to be the official word on using the Apache repositories (http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469), it simply says that location is for versioned releases as opposed to nightly builds. For what it's worth, I think that the intention is not that Maven users would have http://www.apache.org/dist/java-repository/ as a repository, but rather than they'd use iBiblio, which is mirrored from that. I don't know if anyone feels strongly about it, but that's
Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
On a nice GNU/Linux machine, yea sure. But minotaur is a BSD machine and the md5 command (among others) is named differently, maven failed to produce md5 checksums with minotaur (at least back the last time I tried it which was rc1. With this in mind md5 signing needs to be done manually until the issue is addressed (which may have occured in recent release candidates). As well, the mirror folks managing the dist directory have requested that when placing files into the www.apache.org/dist directory, that they be uploaded to a staging area outside of dist and then copied over into the dist directory. this allows for scripts they have running to check md5 checksums which tend to pickup the file before its been fully uploaded and attempt to generate an md5 off it. -Mark Carlos Sanchez wrote: You don't need to care about copying or md5 signatures, just use maven! With maven jar:deploy the jar is built and uploaded to the repository in its proper place and with signatures. -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 8:44 PM To: Struts Developers List Subject: Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) Hey Guys, Yes this is all very good. Definity organize everthing in the /www/cvs.apache.org/repository until you are confident that everything is in its proper place, the biggest issue we encounter is broken symlinks and bad md5 signatures. Once everything is layed out the way you want it and your ready to release, just copy it into /www/www.apache.org/dist/java-repository/... which is rsynced to ibibilio every 4 hours. Make sure premissions are group 'rw' for apcvs and all 'r' once you place it into the official repository location directory. cheers, Mark Carlos Sanchez wrote: Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM To: Struts DEV Mailing List Cc: Carlos Sanchez Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good idea to me, but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to the release repository, ending at iBiblio. Should this be told to the projects that had uploaded snapshots to ibiblio? I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/ Regards. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:08 PM To: Struts Users Mailing List Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote: Hi, Will you
RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
At 8:15 PM +0200 7/12/04, Carlos Sanchez wrote: Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Carlos: Struts has a beta Maven build process. However, Ant is still the official build tool and I would be reluctant to use maven dist:deploy until we are more confident that we are doing everything in Maven which we have been doing in Ant until now. I have used maven jar:deploy and maven dist:deploy for other projects and agree that they make it pretty easy. If you're interested in helping us to port the build, helping hands are always appreciated. We will be moving the CVS repository from jakarta-struts to struts as part of re-organizing to reflect Struts status as a top-level Apache project. It seems that it would make sense to reorganize to use standard Maven paths (like changing src/share to src/java). There's no schedule for this; it's just waiting for someone with CVS repository access to get started. I'm going to start thinking about this now, but not sure when I'll get to more than thinking... Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place. - Carlos Santana
RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
I'm almost sure that maven doesn't use md5 binary, mostly because I'm using Windows (sorry ;)) and because the deployment has been recently implemented with a pure java ssh. We are moving towards a fully java implementation, without needing external binaries. I'm using 1.0rc4 and 1.0 final will be released soon. -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 9:16 PM To: 'Struts Developers List' Subject: Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) On a nice GNU/Linux machine, yea sure. But minotaur is a BSD machine and the md5 command (among others) is named differently, maven failed to produce md5 checksums with minotaur (at least back the last time I tried it which was rc1. With this in mind md5 signing needs to be done manually until the issue is addressed (which may have occured in recent release candidates). As well, the mirror folks managing the dist directory have requested that when placing files into the www.apache.org/dist directory, that they be uploaded to a staging area outside of dist and then copied over into the dist directory. this allows for scripts they have running to check md5 checksums which tend to pickup the file before its been fully uploaded and attempt to generate an md5 off it. -Mark Carlos Sanchez wrote: You don't need to care about copying or md5 signatures, just use maven! With maven jar:deploy the jar is built and uploaded to the repository in its proper place and with signatures. -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 8:44 PM To: Struts Developers List Subject: Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) Hey Guys, Yes this is all very good. Definity organize everthing in the /www/cvs.apache.org/repository until you are confident that everything is in its proper place, the biggest issue we encounter is broken symlinks and bad md5 signatures. Once everything is layed out the way you want it and your ready to release, just copy it into /www/www.apache.org/dist/java-repository/... which is rsynced to ibibilio every 4 hours. Make sure premissions are group 'rw' for apcvs and all 'r' once you place it into the official repository location directory. cheers, Mark Carlos Sanchez wrote: Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM To: Struts DEV Mailing List Cc: Carlos Sanchez Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good
Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
I went on a code expedition and your correct, it does look like the current cvs head now uses the artifact plugin to deploy jars, this plugin has its own md5 generation. thats good to see. -Mark Carlos Sanchez wrote: I'm almost sure that maven doesn't use md5 binary, mostly because I'm using Windows (sorry ;)) and because the deployment has been recently implemented with a pure java ssh. We are moving towards a fully java implementation, without needing external binaries. I'm using 1.0rc4 and 1.0 final will be released soon. -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 9:16 PM To: 'Struts Developers List' Subject: Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) On a nice GNU/Linux machine, yea sure. But minotaur is a BSD machine and the md5 command (among others) is named differently, maven failed to produce md5 checksums with minotaur (at least back the last time I tried it which was rc1. With this in mind md5 signing needs to be done manually until the issue is addressed (which may have occured in recent release candidates). As well, the mirror folks managing the dist directory have requested that when placing files into the www.apache.org/dist directory, that they be uploaded to a staging area outside of dist and then copied over into the dist directory. this allows for scripts they have running to check md5 checksums which tend to pickup the file before its been fully uploaded and attempt to generate an md5 off it. -Mark Carlos Sanchez wrote: You don't need to care about copying or md5 signatures, just use maven! With maven jar:deploy the jar is built and uploaded to the repository in its proper place and with signatures. -Original Message- From: Mark R. Diggory [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 8:44 PM To: Struts Developers List Subject: Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) Hey Guys, Yes this is all very good. Definity organize everthing in the /www/cvs.apache.org/repository until you are confident that everything is in its proper place, the biggest issue we encounter is broken symlinks and bad md5 signatures. Once everything is layed out the way you want it and your ready to release, just copy it into /www/www.apache.org/dist/java-repository/... which is rsynced to ibibilio every 4 hours. Make sure premissions are group 'rw' for apcvs and all 'r' once you place it into the official repository location directory. cheers, Mark Carlos Sanchez wrote: Hi, The maven process to deploy projects in the repository is very easy, it seems that the maven configuration is a bit outdated. I've attached a small patch setting up the repositories. I suggest you to move the building process to maven, it makes life much easier. If you have any doubt you can contact me directly or send a mail to the maven list. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:25 PM To: Struts DEV Mailing List Cc: Carlos Sanchez Subject: RE: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe At 5:41 PM +0200 7/12
Re: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released)
My thoughts below. Joe Germuska wrote: I'm bringing this thread over to the dev list because it's fairly technical and boring to the average user. I went ahead and set up the nightly builds Maven repository with Struts 1.2.1 -- see http://cvs.apache.org/repository/struts/ I tried to flesh out the directories along the idealized Maven repository, by including 'licenses', 'distributions','poms', and 'tlds' directories as well as 'jars' Not sure if that's right or not, since it doesn't seem to be thoroughly documented; we'll just see. Anyway, so the two pertinent questions are 1) should this go on iBiblio yet? I'm leaning towards no until it reaches GA status. For general reference, the Apache directory /www/www.apache.org/dist/java-repository is mirrored to iBiblio, so that when we decide that a Struts release is GA, we can set up that directory and have the release maven-published automatically. I don't think we should go into /www/www.apache.org/dist/java-repository without a GA build, because that directory also gets mirrorred around the world ... and *that* should only contain GAs. That being said, a private alpha/beta Maven repository on Apache someplace seems reasonable. 2) what version number should struts-el have? 1.2.1 ? I'm not sure we've bothered with formally labelling it with a release in the past, but Maven really likes things to have versions. If we ship it with the standard Struts release, it should have the same version number. If it's shipped separately, then it should have it's own version number series. (That's what I plan to do when struts-faces is ready to be released). On minor administrative issues, I also changed the project.xml file version to 1.2.1 (from 1.2.1-dev) and moved the release tag for that one file so that if someone checks out to the tag, the JAR artifact will have the correct version number. Joe Craig PS: Per my comments last night, we also need to set up our own download page for GA distributions that leverages the mirror network, the way that Ant and Maven etc. do it, rather than continuing to rely on the Jakarta page (which is getting increasingly hard to use because of the number of releases found there. Does anyone have time to work on that? At 5:41 PM +0200 7/12/04, Carlos Sanchez wrote: Hi Joe, I agree that users should use iBiblio, just said apache repository because it's mirrored. About the use of the private repo http://cvs.apache.org/builds/java-repository/ seems a good idea to me, but it hasn't been already created, nobody has upload nothing until now? Many apache projects still upload their snapshots to the release repository, ending at iBiblio. Should this be told to the projects that had uploaded snapshots to ibiblio? I am also sure that 1.2.1 should definitely be put at http://cvs.apache.org/builds/java-repository/ Regards. -Original Message- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, July 12, 2004 4:08 PM To: Struts Users Mailing List Subject: 1.2.1 to which Maven repo? (RE: [ANN] Struts 1.2.1 (Beta) Released) At 11:34 AM +0200 7/12/04, Carlos Sanchez wrote: Hi, Will you deploy it and the struts-el on the apache maven repository? http://www.apache.org/dist/java-repository/struts/jars/ I would argue that it doesn't belong in that location until it is voted a full GA release. Then again, reviewing what seems to be the official word on using the Apache repositories (http://article.gmane.org/gmane.comp.jakarta.commons.devel/39469), it simply says that location is for versioned releases as opposed to nightly builds. For what it's worth, I think that the intention is not that Maven users would have http://www.apache.org/dist/java-repository/ as a repository, but rather than they'd use iBiblio, which is mirrored from that. I don't know if anyone feels strongly about it, but that's how I read the previously cited email. If we don't put Struts 1.2.1 on iBiblio, we should definitely put it at http://cvs.apache.org/builds/java-repository/ I'll do either one, but I'll wait to see if a few opinions roll in before taking action. Joe I have built it from cvs sources with maven and the size is not the same. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Ted Husted [mailto:[EMAIL PROTECTED] Sent: Sunday, July 11, 2004 9:11 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [ANN] Struts 1.2.1 (Beta) Released The Struts team announces the release of Struts 1.2.1, currently ranked at Beta quality. This release removes many features deprecated in prior releases (Struts 1.1 and Struts 1.0.2) and also provides several new features. Fixes to known problems have been applied. More detail is available at * http://struts.apache.org/userGuide/release-notes.html The binary, source, and library distributions are available at * http
