Re: Availability of Nightly Builds
pt., 1 lut 2019 o 10:32 Eduardo Quintanilla napisał(a): > > Hello all, > > I was reading the "Source Code and Builds[1]" page and in the section > NightlyBuilds says that you can download the latest development build[2] from > Jenkins. > > The link is not working so i went directly to the Jenkins instance and in the > Struts folder[3] explored the tasks but i could not find any stored artifacts. > > Are Nightly Builds not longer supported? > > [1] https://struts.apache.org/builds.html > [2] > https://builds.apache.org/view/S-Z/view/Struts/job/Struts2-JDK6/lastStableBuild/org.apache.struts$struts2-assembly/ > [3] https://builds.apache.org/view/S-Z/view/Struts/ You can find them here https://repository.apache.org/content/repositories/snapshots/org/apache/struts/struts2-assembly/ I will update the link Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Availability of Nightly Builds
Hello all, I was reading the "Source Code and Builds[1]" page and in the section NightlyBuilds says that you can download the latest development build[2] from Jenkins. The link is not working so i went directly to the Jenkins instance and in the Struts folder[3] explored the tasks but i could not find any stored artifacts. Are Nightly Builds not longer supported? [1] https://struts.apache.org/builds.html [2] https://builds.apache.org/view/S-Z/view/Struts/job/Struts2-JDK6/lastStableBuild/org.apache.struts$struts2-assembly/ [3] https://builds.apache.org/view/S-Z/view/Struts/ Best regards, Eduardo Quintanilla - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
Re: [s2] nightly builds
Folks, I've set up a few artifacts to mirror http://people.apache.org/builds/ struts/nightlies/2.0.x/ You can check it out at: http://opensource.bamboo.atlassian.com/browse/STRUTS-MAIN/latest and click on the Artifacts tab. Let me know if it's missing anything or you want me change how it works. It's not all that easy to directly link to artifacts tab directly at the moment (I've raised this at http://jira.atlassian.com/browse/ BAM-1601) Once it's okay I'll roll it out across the other Struts builds. Cheers, Mark C On 15/08/2007, at 2:51 AM, Ted Husted wrote: Sorry, Jim; I'm old and forgetful :) In any event, there something to be said for lettting Bamboo build our JARs on every checkin, and so forth. My suggestion would be to ask Mark to set this up, link to it, and if goes well, we can turn the S2 nightly builds off again. -Ted. On 8/14/07, James Mitchell [EMAIL PROTECTED] wrote: I don't know how many different ways I have to say this to make it stick. -== I am *NOT* running any automated builds on my own machine ==- That covers the terms local machine and personal machine. Everything is done on ASF hardware. The ASF provides us (The Apache Struts Project) with a Solaris Zone [0] that we happen to use to do the automated nightly builds with. Any committer has a right to ask for an account on this box. [0] http://www.apache.org/dev/solaris-zones.html If you guys still feel that you do not need the process that I have in place. Please let me know and I'll stop the cron job. Thanks. -- James Mitchell On Aug 14, 2007, at 8:43 AM, Ted Husted wrote: On 8/14/07, James Mitchell [EMAIL PROTECTED] wrote: You know, there's nothing wrong with what we have now. Besides, you'd have to have an account on the ASF box in order to drop the jars out there and I am -1 on keeping my private key on a box (other than my own personal machine) out there that is not owned and managed by the ASF. That probably breaks some ASF policy anyway. I believe the idea is that we would simply link to the location where Bamboo is keeping the JARs, not unlike the way we link to resource like Biblio and Nabble. From a policy perspective, this solution is preferable since it distances the PMC from the snapshot builds. Under the Apache License, someone building these JARs for us is a perfectly acceptable use, so long as there is not a representation that the JARs are an ASF release. (Which I'm sure there would not be.) Moreover, it means that James M does not need to expose his credentials to an automated process on his local machine. From a technical perspective, this solution is preferable since the JARs would be always up to date. Immediately after committing a patch, the new binaries would be available for volunteers to test. With a nightly build, we might have to wait until the next day for the latest JAR to be available. Moreover, Bamboo is building the JARs anyway, so this solution is more efficient. It also ensures that any interim tests are against the very same JARs that Bamboo is reporting to us as successful or not successful. I'm very +1 on this, since it * relieves us from the busy work of maintaining the latest build JARs, * provides an more effective and efficient technical solution, and * aligns with ASF principles and policies. -Ted. - 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] -- HTH, Ted http://www.husted.com/ted/blog/ - 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: [s2] nightly builds
Folks, If it's any easier, we can setup a nightly build on Bamboo and save any JARs that you want. Or alternately we can *always* save the various JARs as artifacts for all Struts builds on Bamboo so people can download the very latest Struts JAR after any commit. Let me know if you want anything like that (or indeed if you want admin access to the Struts projects on Bamboo) Cheers, Mark C On 13/08/2007, at 11:05 PM, Ted Husted wrote: On 8/13/07, James Holmes [EMAIL PROTECTED] wrote: Awesome. We should place a link on the downloads page of the site... There's a link half-way down the source code page. We're careful to bury the link since these JARs are not authorized distributions of the Apache Struts PMC. There have been discussions on other lists that suggest nightly builds have been overused in the past by some projects, and at times, builds have been used as an alternative to creating an actual release. Substituting builds for releases may undermine the legal protection provided to PMC members by the foundation. We must be clear on the point that the JARs are being provided as a convenience to the *development* community. It is *not* our intention to distribute these JARs to the general public, and PMC members should avoid linking to the builds from posts to the user list. -Ted. - 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: [s2] nightly builds
++1 On Tue Aug 14 8:43 , 'Ted Husted' [EMAIL PROTECTED] sent: On 8/14/07, James Mitchell [EMAIL PROTECTED] wrote: You know, there's nothing wrong with what we have now. Besides, you'd have to have an account on the ASF box in order to drop the jars out there and I am -1 on keeping my private key on a box (other than my own personal machine) out there that is not owned and managed by the ASF. That probably breaks some ASF policy anyway. I believe the idea is that we would simply link to the location where Bamboo is keeping the JARs, not unlike the way we link to resource like Biblio and Nabble. From a policy perspective, this solution is preferable since it distances the PMC from the snapshot builds. Under the Apache License, someone building these JARs for us is a perfectly acceptable use, so long as there is not a representation that the JARs are an ASF release. (Which I'm sure there would not be.) Moreover, it means that James M does not need to expose his credentials to an automated process on his local machine. From a technical perspective, this solution is preferable since the JARs would be always up to date. Immediately after committing a patch, the new binaries would be available for volunteers to test. With a nightly build, we might have to wait until the next day for the latest JAR to be available. Moreover, Bamboo is building the JARs anyway, so this solution is more efficient. It also ensures that any interim tests are against the very same JARs that Bamboo is reporting to us as successful or not successful. I'm very +1 on this, since it * relieves us from the busy work of maintaining the latest build JARs, * provides an more effective and efficient technical solution, and * aligns with ASF principles and policies. -Ted. - 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: [s2] nightly builds
I don't know how many different ways I have to say this to make it stick. -== I am *NOT* running any automated builds on my own machine ==- That covers the terms local machine and personal machine. Everything is done on ASF hardware. The ASF provides us (The Apache Struts Project) with a Solaris Zone [0] that we happen to use to do the automated nightly builds with. Any committer has a right to ask for an account on this box. [0] http://www.apache.org/dev/solaris-zones.html If you guys still feel that you do not need the process that I have in place. Please let me know and I'll stop the cron job. Thanks. -- James Mitchell On Aug 14, 2007, at 8:43 AM, Ted Husted wrote: On 8/14/07, James Mitchell [EMAIL PROTECTED] wrote: You know, there's nothing wrong with what we have now. Besides, you'd have to have an account on the ASF box in order to drop the jars out there and I am -1 on keeping my private key on a box (other than my own personal machine) out there that is not owned and managed by the ASF. That probably breaks some ASF policy anyway. I believe the idea is that we would simply link to the location where Bamboo is keeping the JARs, not unlike the way we link to resource like Biblio and Nabble. From a policy perspective, this solution is preferable since it distances the PMC from the snapshot builds. Under the Apache License, someone building these JARs for us is a perfectly acceptable use, so long as there is not a representation that the JARs are an ASF release. (Which I'm sure there would not be.) Moreover, it means that James M does not need to expose his credentials to an automated process on his local machine. From a technical perspective, this solution is preferable since the JARs would be always up to date. Immediately after committing a patch, the new binaries would be available for volunteers to test. With a nightly build, we might have to wait until the next day for the latest JAR to be available. Moreover, Bamboo is building the JARs anyway, so this solution is more efficient. It also ensures that any interim tests are against the very same JARs that Bamboo is reporting to us as successful or not successful. I'm very +1 on this, since it * relieves us from the busy work of maintaining the latest build JARs, * provides an more effective and efficient technical solution, and * aligns with ASF principles and policies. -Ted. - 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: [s2] nightly builds
Ok, looks like things are rolling again. The one exception was 2.x (trunk), so I added that and it should build and push out the latest on the next run. Let me know if you see any problems. Thanks -- James Mitchell On Aug 12, 2007, at 12:00 PM, James Holmes wrote: Yes, please restart! :) -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, August 12, 2007 12:08 PM To: Struts Developers List Subject: Re: [s2] nightly builds No, actually, we haven't done this on our own machines in quite a while. For a long time we were doing this on our zone account, which is ASF hardware. I stopped this process a few weeks ago while doing some maintenance and never got back to it. I can restart this process if we need to. Let me know. -- James Mitchell On Aug 12, 2007, at 11:15 AM, James Holmes wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [s2] nightly builds
Awesome. We should place a link on the downloads page of the site... -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 6:16 AM To: Struts Developers List Subject: Re: [s2] nightly builds Ok, looks like things are rolling again. The one exception was 2.x (trunk), so I added that and it should build and push out the latest on the next run. Let me know if you see any problems. Thanks -- James Mitchell On Aug 12, 2007, at 12:00 PM, James Holmes wrote: Yes, please restart! :) -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, August 12, 2007 12:08 PM To: Struts Developers List Subject: Re: [s2] nightly builds No, actually, we haven't done this on our own machines in quite a while. For a long time we were doing this on our zone account, which is ASF hardware. I stopped this process a few weeks ago while doing some maintenance and never got back to it. I can restart this process if we need to. Let me know. -- James Mitchell On Aug 12, 2007, at 11:15 AM, James Holmes wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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] - 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: [s2] nightly builds
On 8/13/07, James Holmes [EMAIL PROTECTED] wrote: Awesome. We should place a link on the downloads page of the site... There's a link half-way down the source code page. We're careful to bury the link since these JARs are not authorized distributions of the Apache Struts PMC. There have been discussions on other lists that suggest nightly builds have been overused in the past by some projects, and at times, builds have been used as an alternative to creating an actual release. Substituting builds for releases may undermine the legal protection provided to PMC members by the foundation. We must be clear on the point that the JARs are being provided as a convenience to the *development* community. It is *not* our intention to distribute these JARs to the general public, and PMC members should avoid linking to the builds from posts to the user list. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[s2] nightly builds
We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] nightly builds
Between Bamboo and Maven, I wonder if nightly builds are still worth the trouble. Bamboo alerts us if we do anything that breaks the build, and if someone wants the latest bits, maven install is not so much to ask. -Ted. On 8/12/07, James Holmes [EMAIL PROTECTED] wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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: [s2] nightly builds
Agreed that Bamboo and Maven can approximate a nightly build, but I for one find it much more convenient to simply download an already packaged build. It's much easier to grab this, unzip it, get the latest jars and go. Maven is nice if your project is using Maven, but in my case I'm not and I'm sure there are others in the same boat as me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Husted Sent: Sunday, August 12, 2007 11:49 AM To: Struts Developers List Subject: Re: [s2] nightly builds Between Bamboo and Maven, I wonder if nightly builds are still worth the trouble. Bamboo alerts us if we do anything that breaks the build, and if someone wants the latest bits, maven install is not so much to ask. -Ted. On 8/12/07, James Holmes [EMAIL PROTECTED] wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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: [s2] nightly builds
On 8/12/07, James Holmes [EMAIL PROTECTED] wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? The sticking point is usually permissions to get the files transferred to people.a.o. Infra isn't in favor of 'faceless' accounts, so that part needs to run as someone in particular. There is a shared Continuum instance on vmbuild.apache.org, I'm waiting to see how they solve the where to publish issue. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] nightly builds
No, actually, we haven't done this on our own machines in quite a while. For a long time we were doing this on our zone account, which is ASF hardware. I stopped this process a few weeks ago while doing some maintenance and never got back to it. I can restart this process if we need to. Let me know. -- James Mitchell On Aug 12, 2007, at 11:15 AM, James Holmes wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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: [s2] nightly builds
Yes, please restart! :) -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, August 12, 2007 12:08 PM To: Struts Developers List Subject: Re: [s2] nightly builds No, actually, we haven't done this on our own machines in quite a while. For a long time we were doing this on our zone account, which is ASF hardware. I stopped this process a few weeks ago while doing some maintenance and never got back to it. I can restart this process if we need to. Let me know. -- James Mitchell On Aug 12, 2007, at 11:15 AM, James Holmes wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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: [s2] nightly builds
Ok, I just reenabled the cron job and ran it manually so we don't have to wait to tonight. There may be issues with old jars in the local repo or with the j4 builds, so I'll keep an eye on it. Watch for the artifacts to appear under this directory: http://people.apache.org/builds/struts/nightlies/ Optimally, we would want our Continuum instance (or Bamboo) to build and push the artifacts to the nightly build location. -- James Mitchell On Aug 12, 2007, at 12:00 PM, James Holmes wrote: Yes, please restart! :) -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Sunday, August 12, 2007 12:08 PM To: Struts Developers List Subject: Re: [s2] nightly builds No, actually, we haven't done this on our own machines in quite a while. For a long time we were doing this on our zone account, which is ASF hardware. I stopped this process a few weeks ago while doing some maintenance and never got back to it. I can restart this process if we need to. Let me know. -- James Mitchell On Aug 12, 2007, at 11:15 AM, James Holmes wrote: We need to get a process setup for generating nightly builds for Struts 2. I'm not familiar with all of the infrastructure involved with getting this going, but am willing to help get this in place. I have spoken briefly to James Mitchell about this and I understand that he was doing this for awhile from his own machines. Is there a way we can automate it on the Apache servers? Anyone have info on this? James - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Nightly Builds
We might get around this by enabling wild-carded configPaths. Then scan for struts-plugin-*.xml in addition to what we already do. What do you think? -- James Mitchell 678.910.8017 On Dec 7, 2006, at 11:23 PM, Don Brown wrote: The only way we could do it is if we had a custom maven 2 plugin that combined all the xml, and even then, we'd have to build in conflict resolution capability. No, I think we should get rid of struts-all. Don Wendy Smoak wrote: On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote: So, should we even have a struts-all JAR then? I haven't worked much with plugins, but I don't see how an -all jar can work given that each plugin has a struts-plugin.xml file in the root of the jar. Don? - 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: [s2] Nightly Builds
Yeah, we could adapt the classloader scanning tool we use for the zeroconf stuff to look for xml files at the root. Still, this would involve custom maven 2 work, and even then, the jar wouldn't work in a predictable manner. The problem is that a plugin can tell struts 2 it wants to override certain beans or settings. If you have two plugins that both override, say, objectfactory, the last one loaded wins. Which last one is undefined. Don Mitchell James wrote: We might get around this by enabling wild-carded configPaths. Then scan for struts-plugin-*.xml in addition to what we already do. What do you think? -- James Mitchell 678.910.8017 On Dec 7, 2006, at 11:23 PM, Don Brown wrote: The only way we could do it is if we had a custom maven 2 plugin that combined all the xml, and even then, we'd have to build in conflict resolution capability. No, I think we should get rid of struts-all. Don Wendy Smoak wrote: On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote: So, should we even have a struts-all JAR then? I haven't worked much with plugins, but I don't see how an -all jar can work given that each plugin has a struts-plugin.xml file in the root of the jar. Don? - 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: [s2] Nightly Builds
Is there a way we could just post post the lib.zip distribution as our nightly build, since that contains all the plugins and the various dependencies? If someone isn't building the framework from a source code checkout, but wants to follow the dev discussions, then the lib binaries is all he or she would really need. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Nightly Builds
On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote: So, should we even have a struts-all JAR then? I haven't worked much with plugins, but I don't see how an -all jar can work given that each plugin has a struts-plugin.xml file in the root of the jar. Don? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Nightly Builds
The only way we could do it is if we had a custom maven 2 plugin that combined all the xml, and even then, we'd have to build in conflict resolution capability. No, I think we should get rid of struts-all. Don Wendy Smoak wrote: On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote: So, should we even have a struts-all JAR then? I haven't worked much with plugins, but I don't see how an -all jar can work given that each plugin has a struts-plugin.xml file in the root of the jar. Don? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Nightly Builds
So, should we even have a struts-all JAR then? On 11/27/06, Don Brown [EMAIL PROTECTED] wrote: The only real disadvantage of defaulting to the struts2-all.jar is that you lose the self-configuration aspect of the plugins. For example, by including the Spring plugin jar, it is able to tell Struts 2 to use its ObjectFactory automatically. However, if you included both the Spring and Plexus plugins, the last one loaded would get to set the ObjectFactory, however, determining which one is last is undetermined. The other issue is how the struts-plugin.xml files would be handled. IIRC, the struts2-all.jar simply combines the files into one jar. However, that wouldn't work with plugins because they each define a struts-plugin.xml file in their root directory. Don Ted Husted wrote: Right now, we're posting the api and core JARs for Struts 2 Would it be difficult to switch that to the all JAR, which includes the plugins? (And, now that I say it, I realize that maybe the all JAR is the one we should J4.) Is there a non-technical reason why we are just posting the JARs, and not the source and the rest of it? -Ted. - 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] -- HTH, Ted. * http://www.husted.com/struts/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[s2] Nightly Builds
Right now, we're posting the api and core JARs for Struts 2 Would it be difficult to switch that to the all JAR, which includes the plugins? (And, now that I say it, I realize that maybe the all JAR is the one we should J4.) Is there a non-technical reason why we are just posting the JARs, and not the source and the rest of it? -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Nightly Builds
The only real disadvantage of defaulting to the struts2-all.jar is that you lose the self-configuration aspect of the plugins. For example, by including the Spring plugin jar, it is able to tell Struts 2 to use its ObjectFactory automatically. However, if you included both the Spring and Plexus plugins, the last one loaded would get to set the ObjectFactory, however, determining which one is last is undetermined. The other issue is how the struts-plugin.xml files would be handled. IIRC, the struts2-all.jar simply combines the files into one jar. However, that wouldn't work with plugins because they each define a struts-plugin.xml file in their root directory. Don Ted Husted wrote: Right now, we're posting the api and core JARs for Struts 2 Would it be difficult to switch that to the all JAR, which includes the plugins? (And, now that I say it, I realize that maybe the all JAR is the one we should J4.) Is there a non-technical reason why we are just posting the JARs, and not the source and the rest of it? -Ted. - 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: Location for nightly builds
Sorry, I've been a little slow with keeping up on list traffic these last few weeks, but why are we using this location for anything other than nightly builds? The nightly cron job will clear out anything older than 7 days starting at /www/cvs.apache.org/builds/struts. Should I turn this off? -- James Mitchell On Jul 23, 2006, at 12:09 PM, Ted Husted wrote: Note that I renamed 2.x on people.apache.org/builds/struts to 2.0.x so as to match our conventions for 1.x. -Ted. - 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: Location for nightly builds
Until we have nightly builds again, it's my intent to run these at least every week. Does the cron job clear out everything under 2.0.x, or just the nightly subdirectory? (Has the cron job been updated to use 2.0.x instead of 2.x?) In any event, next time I can just open a 2.0.0 for the weekly snapshots. -Ted. On 7/25/06, James Mitchell [EMAIL PROTECTED] wrote: Sorry, I've been a little slow with keeping up on list traffic these last few weeks, but why are we using this location for anything other than nightly builds? The nightly cron job will clear out anything older than 7 days starting at /www/cvs.apache.org/builds/struts. Should I turn this off? -- James Mitchell On Jul 23, 2006, at 12:09 PM, Ted Husted wrote: Note that I renamed 2.x on people.apache.org/builds/struts to 2.0.x so as to match our conventions for 1.x. -Ted. - 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] -- HTH, Ted. * http://www.husted.com/struts/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
On 7/25/06, James Mitchell [EMAIL PROTECTED] wrote: Sorry, I've been a little slow with keeping up on list traffic these last few weeks, but why are we using this location for anything other than nightly builds? The nightly cron job will clear out anything older than 7 days starting at /www/cvs.apache.org/builds/struts. Should I turn this off? Oops. I forgot about that. Ted, can you put the 1.3.5 distributions back in http://people.apache.org/builds/struts/1.3.5/ ? If not, I have them at home. (reposted from the 'Distribution Directories' thread) Based on the following links, I think it should be under /builds until it becomes a release, then it can be moved to one of the 'dist' directories depending on the quality. * http://www.apache.org/dev/release.html#release-types * http://www.apache.org/dev/release.html#build-directories We could put them somewhere else, such as struts.apache.org/dev/dist. (That was suggested on [EMAIL PROTECTED], and it's what they're using now: http://tomcat.apache.org/dev/dist/ ) Or could we adjust the directory structure and/or the script to avoid deleting the tagged builds? Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
On 7/25/06, Wendy Smoak [EMAIL PROTECTED] wrote: Ted, can you put the 1.3.5 distributions back in http://people.apache.org/builds/struts/1.3.5/ ? Done. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
It clears everything under /www/people.apache.org/builds/struts/ I know I said cvs.apache.org last time, but that's really just a symlink over to the above locationI've had that cron job for a while ;) I have disabled it for now, until we find a better solutions...look for a follow up discussion on this thread. -- James Mitchell On Jul 25, 2006, at 7:04 PM, Ted Husted wrote: Until we have nightly builds again, it's my intent to run these at least every week. Does the cron job clear out everything under 2.0.x, or just the nightly subdirectory? (Has the cron job been updated to use 2.0.x instead of 2.x?) In any event, next time I can just open a 2.0.0 for the weekly snapshots. -Ted. On 7/25/06, James Mitchell [EMAIL PROTECTED] wrote: Sorry, I've been a little slow with keeping up on list traffic these last few weeks, but why are we using this location for anything other than nightly builds? The nightly cron job will clear out anything older than 7 days starting at /www/cvs.apache.org/builds/struts. Should I turn this off? -- James Mitchell On Jul 23, 2006, at 12:09 PM, Ted Husted wrote: Note that I renamed 2.x on people.apache.org/builds/struts to 2.0.x so as to match our conventions for 1.x. -Ted. - 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] -- HTH, Ted. * http://www.husted.com/struts/ - 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: Location for nightly builds
Note that I renamed 2.x on people.apache.org/builds/struts to 2.0.x so as to match our conventions for 1.x. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
Cron is not running on the zone so I was kicking off the builds by hand every day. Then, about 2 weeks ago, Maven just stopped working for me on the zone. Ant works fine and so should Maven. Funny thing is, google does not give me a clue... [EMAIL PROTECTED] # ant Buildfile: build.xml does not exist! expected Build failed [EMAIL PROTECTED] # mvn /usr/local/maven-2.0.4/bin/mvn: test: argument expected wtf? -- James Mitchell On Jul 18, 2006, at 5:07 PM, Ted Husted wrote: So, what is it that we are doing about nightly builds? I though we had them running, but I don't see them now. * http://people.apache.org/builds/struts/ -Ted. - 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: Location for nightly builds
This week I started a new job and so I'm back to having a stable internet connection that I can use to do the builds from this (my personal) machine. I already kicked off the script as I'm typing this so look for them in a few hours. -- James Mitchell On Jul 19, 2006, at 10:14 AM, James Mitchell wrote: Cron is not running on the zone so I was kicking off the builds by hand every day. Then, about 2 weeks ago, Maven just stopped working for me on the zone. Ant works fine and so should Maven. Funny thing is, google does not give me a clue... [EMAIL PROTECTED] # ant Buildfile: build.xml does not exist! expected Build failed [EMAIL PROTECTED] # mvn /usr/local/maven-2.0.4/bin/mvn: test: argument expected wtf? -- James Mitchell On Jul 18, 2006, at 5:07 PM, Ted Husted wrote: So, what is it that we are doing about nightly builds? I though we had them running, but I don't see them now. * http://people.apache.org/builds/struts/ -Ted. - 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: Location for nightly builds
So, what is it that we are doing about nightly builds? I though we had them running, but I don't see them now. * http://people.apache.org/builds/struts/ -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
Ok, so I finally got around to fixing the nightly build for 1.3.x Since crontab is not running on the zone, (and I don't feel like asking why on infr@) I'll be kicking these off from my personal box. This will also allow me to keep a close eye on it. Next stop -- 2.0.x -- James Mitchell On Jun 22, 2006, at 9:13 AM, Ted Husted wrote: AFIAC, you're doing the work, and you can make the decision. :) -Ted. - 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: Location for nightly builds
I've got the script ready to publish the nightlies, but I want to know what everyone wants published (along with any special commands needed to produce it). When I execute mvn package, I see the following that I can publish: ./api/target/struts2-api-2.0-SNAPSHOT.jar ./core/target/struts2-core-2.0-SNAPSHOT.jar ./apps/blank/target/struts2-blank.war ./apps/portlet/target/struts2-portlet.war ./apps/shopping-cart/target/struts2-shopping-cart.war ./apps/showcase/target/struts2-showcase.war ./apps/starter/target/struts2-starter.war Is this all we are offering for nightly downloads? -- James Mitchell On Jul 2, 2006, at 3:22 PM, James Mitchell wrote: Ok, so I finally got around to fixing the nightly build for 1.3.x Since crontab is not running on the zone, (and I don't feel like asking why on infr@) I'll be kicking these off from my personal box. This will also allow me to keep a close eye on it. Next stop -- 2.0.x -- James Mitchell On Jun 22, 2006, at 9:13 AM, Ted Husted wrote: AFIAC, you're doing the work, and you can make the decision. :) -Ted. - 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: Location for nightly builds
On 7/2/06, James Mitchell [EMAIL PROTECTED] wrote: I've got the script ready to publish the nightlies, but I want to know what everyone wants published (along with any special commands needed to produce it). When I execute mvn package, I see the following that I can publish: ... Is this all we are offering for nightly downloads? Try it with -Pextras so it will build the struts2-extras jar. Ideally we would do assemblies for the example apps rather than put the .war files in the snapshot repo, but that's waiting for someone to have time to adapt the work done in Struts 1 Shale to the Struts 2 build. It's fine for now. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
On Jul 2, 2006, at 11:41 PM, Wendy Smoak wrote: On 7/2/06, James Mitchell [EMAIL PROTECTED] wrote: I've got the script ready to publish the nightlies, but I want to know what everyone wants published (along with any special commands needed to produce it). When I execute mvn package, I see the following that I can publish: ... Is this all we are offering for nightly downloads? Try it with -Pextras so it will build the struts2-extras jar. I've added it for tomorrow. Ideally we would do assemblies for the example apps rather than put the .war files in the snapshot repo, Sorry? You mean our nightly location is considered a m2 repo? By who? http://people.apache.org/builds/struts/2.x/ but that's waiting for someone to have time to adapt the work done in Struts 1 Shale to the Struts 2 build. It's fine for now. Ya, I'm still not up to speed on all the assembly stuff we are doing. My schedule should open up here in the next few weeks so I'll be able to spend more time on this and help with releases. -- Wendy -- James Mitchell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
On 7/2/06, James Mitchell [EMAIL PROTECTED] wrote: On Jul 2, 2006, at 11:41 PM, Wendy Smoak wrote: Ideally we would do assemblies for the example apps rather than put the .war files in the snapshot repo, Sorry? You mean our nightly location is considered a m2 repo? By who? http://people.apache.org/builds/struts/2.x/ Sorry, that wasn't directly related to your question about nightly builds. By having the example apps as part of the default build, 'mvn deploy' publishes the .war files as artifacts in the snapshot repo, which I don't want to happen. Nevermind... it will get sorted out eventually. :) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
AFIAC, you're doing the work, and you can make the decision. :) -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
On Jun 20, 2006, at 12:45 PM, Martin Cooper wrote: On 6/20/06, James Mitchell [EMAIL PROTECTED] wrote: Craig and I were discussing a few offline items and one thing that came up was how we currently publish the nightlies. We agree that this is best discussed in public, so here I am :) Currently the nightly build can be found (or will be) on minotaur (people.apache.org) under /builds/struts. For years the builds were done on Craig's personal machine, which would be scp'd up to minotaur and everything moved happily along for a while. Then, as the svn reorg occurred and we sort-of began moving to a Maven 1 based build, I was using my personal machine to build and upload the maven-built artifacts to the same place. The only problem with the using a personal machine approach is that if some dependency changed (with the Ant based build), then, due to the way our build files worked, Craig had to make the manual change on his personal machine. However, with Maven (1 and 2), everything is declarative in the pom.xml, and so unless there's some weird bug in a current plugin or if the POM now needs a later plugin version, there really isn't a need to touch the machine or the local configuration. Later, I moved this process off my personal machine and used my account on the zone to build and scp over to minotaur the same way. This was an improvement in reliability, but we still have the problem that this was *my* account and not just anyone could fix it if there was a problem. Looking back ... in and of itself, the actual location of the build is insignificant with regard to authenticity or security. Anyone with an Apache account can upload anything they like to (almost) wherever they like. And so long as the build requirements or dependencies didn't change, everything went along like clockwork. Fast forward to June 2006, here we are with more or less 4 Maven 2 based projects, each with multiple artifacts. I see our options as: Build using: 1) personal machine 2) zone (personal account) 3) zone (shared account, i.e. mrstruts) Users download from: a) minotaur b) zone Currently we are a mixture of 1a and 3a. Also, 3b isn't really a viable option because someone would have to use their private key for that shared account (so the scp process would work). You mean 3a isn't viable, right? 3b wouldn't require scp at all, would it? Wow, I guess it was later than I thought. Yes, I meant to say we are currently using a mixture of 1a and 2a. And that 3a isn't really a viable option. If b is used/allowed, then it makes the most sense to go with 3b, so everyone can help with fixes and updates. Furthermore, I had always assumed that hosting nightlies from the zone was out of the question. Is that not the case? I don't know. I think it would be worth a ping to infra, since I would think this would be the best option. I'll wait to see how everyone else feels before moving further on this. I am assuming that no news means everyone agrees and has no problems with the current path. Either way, I can see one other approach. 3a with the ability of a few people to su to root, then su to the personal account (e.g. jmitchell) and fix whatever. I suppose, although this would mean we'd have to hand out root more than I'd like. There's also a discussion going on in various places about a machine named vmbuild, which is intended as a build machine for all (?) projects. I haven't been paying close attention, but perhaps we should engage there? Ya, I've seen a few mentions of it on infra, but not completely sure of what the intent is. They do talk about a shared Continuum on it though. Not sure if we'd want to take advantage of it, now that we've got our own :) So, I'm waiting to hear what others think as far as where and how nightlies get published. -- Martin Cooper -- James Mitchell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Location for nightly builds
Craig and I were discussing a few offline items and one thing that came up was how we currently publish the nightlies. We agree that this is best discussed in public, so here I am :) Currently the nightly build can be found (or will be) on minotaur (people.apache.org) under /builds/struts. For years the builds were done on Craig's personal machine, which would be scp'd up to minotaur and everything moved happily along for a while. Then, as the svn reorg occurred and we sort-of began moving to a Maven 1 based build, I was using my personal machine to build and upload the maven-built artifacts to the same place. The only problem with the using a personal machine approach is that if some dependency changed (with the Ant based build), then, due to the way our build files worked, Craig had to make the manual change on his personal machine. However, with Maven (1 and 2), everything is declarative in the pom.xml, and so unless there's some weird bug in a current plugin or if the POM now needs a later plugin version, there really isn't a need to touch the machine or the local configuration. Later, I moved this process off my personal machine and used my account on the zone to build and scp over to minotaur the same way. This was an improvement in reliability, but we still have the problem that this was *my* account and not just anyone could fix it if there was a problem. Looking back ... in and of itself, the actual location of the build is insignificant with regard to authenticity or security. Anyone with an Apache account can upload anything they like to (almost) wherever they like. And so long as the build requirements or dependencies didn't change, everything went along like clockwork. Fast forward to June 2006, here we are with more or less 4 Maven 2 based projects, each with multiple artifacts. I see our options as: Build using: 1) personal machine 2) zone (personal account) 3) zone (shared account, i.e. mrstruts) Users download from: a) minotaur b) zone Currently we are a mixture of 1a and 3a. Also, 3b isn't really a viable option because someone would have to use their private key for that shared account (so the scp process would work). Furthermore, I had always assumed that hosting nightlies from the zone was out of the question. Is that not the case? Either way, I can see one other approach. 3a with the ability of a few people to su to root, then su to the personal account (e.g. jmitchell) and fix whatever. Your thoughts? -- James Mitchell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Struts Nightly builds [was Re: Continnum Is Up]
On 6/19/06, James Mitchell [EMAIL PROTECTED] wrote: My questions would have been about the POM changes that Sean eluded to during our mini hackathon. I could be wrong, but I thought he said there would be an issue with something we needed and it not being published yet and that may or may not have stemmed from a private conversation you may or may not have had over IM. Sorry, the details are still a little cloudy. Forget about it for now, I'm sure if it's a problem we'll know as soon as we begin adding more projects to Continuum. I'm sure it was about changing the struts-parent pom to version 3-SNAPSHOT. I hadn't incremented it after the v2 release, so when Sean made a change to it, there was the potential of someone publishing a different v2 than the one on ibiblio. I commented on the commit message on the list, then caught Sean on IM to make sure he saw it. There is a snapshot available: http://people.apache.org/maven-snapshot-repository/org/apache/struts/struts-parent/3-SNAPSHOT/ The sub-project parent poms can be changed to depend on this version, and we'll need to tag and vote on struts-parent v3 after we add the new committers and make any other necessary changes. If Frank's checkstyle changes are acceptable, we'll also need to release another struts-build.jar. (Depending on the SAF 1.3.5 schedule, it might need to stay on the current released versions.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location for nightly builds
On 6/20/06, James Mitchell [EMAIL PROTECTED] wrote: Craig and I were discussing a few offline items and one thing that came up was how we currently publish the nightlies. We agree that this is best discussed in public, so here I am :) Currently the nightly build can be found (or will be) on minotaur (people.apache.org) under /builds/struts. For years the builds were done on Craig's personal machine, which would be scp'd up to minotaur and everything moved happily along for a while. Then, as the svn reorg occurred and we sort-of began moving to a Maven 1 based build, I was using my personal machine to build and upload the maven-built artifacts to the same place. The only problem with the using a personal machine approach is that if some dependency changed (with the Ant based build), then, due to the way our build files worked, Craig had to make the manual change on his personal machine. However, with Maven (1 and 2), everything is declarative in the pom.xml, and so unless there's some weird bug in a current plugin or if the POM now needs a later plugin version, there really isn't a need to touch the machine or the local configuration. Later, I moved this process off my personal machine and used my account on the zone to build and scp over to minotaur the same way. This was an improvement in reliability, but we still have the problem that this was *my* account and not just anyone could fix it if there was a problem. Looking back ... in and of itself, the actual location of the build is insignificant with regard to authenticity or security. Anyone with an Apache account can upload anything they like to (almost) wherever they like. And so long as the build requirements or dependencies didn't change, everything went along like clockwork. Fast forward to June 2006, here we are with more or less 4 Maven 2 based projects, each with multiple artifacts. I see our options as: Build using: 1) personal machine 2) zone (personal account) 3) zone (shared account, i.e. mrstruts) Users download from: a) minotaur b) zone Currently we are a mixture of 1a and 3a. Also, 3b isn't really a viable option because someone would have to use their private key for that shared account (so the scp process would work). You mean 3a isn't viable, right? 3b wouldn't require scp at all, would it? Furthermore, I had always assumed that hosting nightlies from the zone was out of the question. Is that not the case? I don't know. I think it would be worth a ping to infra, since I would think this would be the best option. Either way, I can see one other approach. 3a with the ability of a few people to su to root, then su to the personal account (e.g. jmitchell) and fix whatever. I suppose, although this would mean we'd have to hand out root more than I'd like. There's also a discussion going on in various places about a machine named vmbuild, which is intended as a build machine for all (?) projects. I haven't been paying close attention, but perhaps we should engage there? -- Martin Cooper Your thoughts? -- James Mitchell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[all] Struts Nightly builds [was Re: Continnum Is Up]
Wonderful timing, I was just about to start a new thread wrt getting the nightlies back online. And so I'll move my thoughts here. So, with the mini hackathon out of the way, and our new buddy MrStruts taking care of the continuous integration for us (ok, he isn't doing much right now, but he is there and ready to roll), I'd like to turn at least some of my attention to getting the nightlies back online. Sorry if this was already discussed/decided on a different thread, I'm behind on every list I am currently subscribed to, except [EMAIL PROTECTED] I plan to have MrStruts do full nightly builds using a similar nightly script to the one I was using for many months with the Maven 1 built nightlies. I'm in the process (as I type this) of creating the necessary build scripts to produce nightly artifacts of Struts Action 1 (1.2.x and 1.3.x), Struts Action 2, and Shale. Currently, we publish the nightlies here: http://people.apache.org/builds/struts/ ...and I see Craig has begun publishing Shale nightlies to this spot: http://people.apache.org/builds/struts/maven2/shale/ So, on that note, I'll begin publishing Action 1 and 2 nightlies in a (almost) similar fashion. Craig, I've already zapped the 'maven' directory, can we: 1. remove the extra directory 'maven2' and just have p.a.o/builds/ struts/shale (requires you to change your scp script)? 2. rm -fr 'nightly' from the same dir? So, (high level) we would have: http://people.apache.org/builds/struts/shale http://people.apache.org/builds/struts/action1/1.2.x/ http://people.apache.org/builds/struts/action1/1.3.x/ http://people.apache.org/builds/struts/action2 http://people.apache.org/builds/struts/tiles (eventually) ...and each directory (Maven 2 built) would have a directory for the particular module, which would have the current jar, war, or zip, and 6 days prior. How does this sound? Wendy wrote: That was a few days ago. :) Yes, I know, I never got back to this. Sorry, it's been a heck of a month this week ;) My questions would have been about the POM changes that Sean eluded to during our mini hackathon. I could be wrong, but I thought he said there would be an issue with something we needed and it not being published yet and that may or may not have stemmed from a private conversation you may or may not have had over IM. Sorry, the details are still a little cloudy. Forget about it for now, I'm sure if it's a problem we'll know as soon as we begin adding more projects to Continuum. -- James Mitchell On Jun 19, 2006, at 9:20 PM, Wendy Smoak wrote: On 6/14/06, James Mitchell [EMAIL PROTECTED] wrote: Yes. There is a wiki page for this as well. http://wiki.apache.org/struts/StrutsContinuum It's a work in progress, and I'm about to head out, but I'd like to ask Wendy a few questions wrt pom, parent-pom, snapshot vs. released, etc, etc. Back in a bit. That was a few days ago. :) Craig, are you ready to get Shale set up on Continuum? I assume you'd like to get out of the nightly builds business, and have them run from the zone. In another thread, I think Sean mentioned it's ready to start adding things. I started to update the Shale site yesterday, but I need to know where the nightly builds/snapshots are going to be so I can link to them. Thanks, -- Wendy - 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: [all] Struts Nightly builds [was Re: Continnum Is Up]
On 6/19/06, James Mitchell [EMAIL PROTECTED] wrote: Craig, I've already zapped the 'maven' directory, can we: 1. remove the extra directory 'maven2' and just have p.a.o/builds/ struts/shale (requires you to change your scp script)? Related: I'm using http://people.apache.org/builds/struts/maven2/shale/site temporarily, staging the site locally wasn't working very well. Let me know if that's a problem, I can change the URLs and deploy it somewhere else. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [all] Struts Nightly builds [was Re: Continnum Is Up]
That brings up another interesting problem. Generated docs. I know we try to keep the latest and greatest docs online (main site) but for branched versions (Action 1.2.x), we would need to provide the docs as well. So it might look like... http://people.apache.org/builds/struts/action1/1.2.x/docs/ -- 1.2 docs here http://people.apache.org/builds/struts/action1/1.2.x/binary/ http://people.apache.org/builds/struts/action1/1.2.x/lib/ http://people.apache.org/builds/struts/action1/1.2.x/src/ ...and if we did the same for others... http://people.apache.org/builds/struts/shale/docs/ http://people.apache.org/builds/struts/shale/shale-blank/ http://people.apache.org/builds/struts/shale/shale-clay-usecases/ http://people.apache.org/builds/struts/shale/shale-framework/ http://people.apache.org/builds/struts/shale/shale-mailreader/ http://people.apache.org/builds/struts/shale/shale-sql-browser/ http://people.apache.org/builds/struts/shale/shale-usecases/ Maybe 1.2.x is a special case or maybe we should just do it anyway so we can see the latest and greatest documentation (build hourly is even possible). -- James Mitchell On Jun 20, 2006, at 12:19 AM, Wendy Smoak wrote: On 6/19/06, James Mitchell [EMAIL PROTECTED] wrote: Craig, I've already zapped the 'maven' directory, can we: 1. remove the extra directory 'maven2' and just have p.a.o/builds/ struts/shale (requires you to change your scp script)? Related: I'm using http://people.apache.org/builds/struts/maven2/shale/site temporarily, staging the site locally wasn't working very well. Let me know if that's a problem, I can change the URLs and deploy it somewhere else. -- Wendy - 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: [all] Struts Nightly builds [was Re: Continnum Is Up]
On 6/19/06, James Mitchell [EMAIL PROTECTED] wrote: Wonderful timing, I was just about to start a new thread wrt getting the nightlies back online. And so I'll move my thoughts here. So, with the mini hackathon out of the way, and our new buddy MrStruts taking care of the continuous integration for us (ok, he isn't doing much right now, but he is there and ready to roll), I'd like to turn at least some of my attention to getting the nightlies back online. Sorry if this was already discussed/decided on a different thread, I'm behind on every list I am currently subscribed to, except [EMAIL PROTECTED] I plan to have MrStruts do full nightly builds using a similar nightly script to the one I was using for many months with the Maven 1 built nightlies. I'm in the process (as I type this) of creating the necessary build scripts to produce nightly artifacts of Struts Action 1 (1.2.x and 1.3.x), Struts Action 2, and Shale. Currently, we publish the nightlies here: http://people.apache.org/builds/struts/ ...and I see Craig has begun publishing Shale nightlies to this spot: http://people.apache.org/builds/struts/maven2/shale/ So, on that note, I'll begin publishing Action 1 and 2 nightlies in a (almost) similar fashion. Craig, I've already zapped the 'maven' directory, can we: 1. remove the extra directory 'maven2' and just have p.a.o/builds/ struts/shale (requires you to change your scp script)? 2. rm -fr 'nightly' from the same dir? Not a problem ... I'll switch for tonight's build. Indeed, I hadn't announced the destination until we had a chance to coordinate across the various builds. I published my shell script from before this change in an earlier response to Wendy's questions ... it's four simple substitutions. So, (high level) we would have: http://people.apache.org/builds/struts/shale http://people.apache.org/builds/struts/action1/1.2.x/ http://people.apache.org/builds/struts/action1/1.3.x/ http://people.apache.org/builds/struts/action2 http://people.apache.org/builds/struts/tiles (eventually) ...and each directory (Maven 2 built) would have a directory for the particular module, which would have the current jar, war, or zip, and 6 days prior. How does this sound? Sounds good, but I've got some additional thoughts that I would like to see us implement consistently. * In addition to publishing artifacts in this directory, I'm also updating the snapshots for all the poms and jars. That way, people who like to live dangerously :-) and have dependencies on the HEAD code effectively get daily updates, without having to manually check out the sources and rebuild them. * I succumbed to my historical habits :-) and produced both .zip and .tar.gz versions of the artifacts. I'd be open to publishing only in zip format since it's pretty universal, and we don't particularly care about file permissions in what we publish (i.e. no executables to worry about). * I'm really happy with the way that the assemblies constructed by the Shale build scripts (both for the framework itself, and for each individual sample app) are themselves buildable if you have Maven2 installed. This kind of thing will encourage others to get on the bandwagon (listen to me, the latecomer :-), even if they don't want to try to download and build the framework itself from Subversion. I'd like to see this approach implemented consistently across our artifacts. * I'm not so happy with the lukewarm support Maven2 currently offers for integration testing. Wendy got inspired by some comments on the user mailling list for Maven, though, and created a nice workaround in the poms for the Shale sample apps. If you do something like: mvn install -Pitest then you can run the system integration tests built into the same project, rather than having to set up a parallel project for those tests. Shale's integration tests happen to be built with HtmlUnit, but it should be equally feasible to use Canoo or whatever else you like. We're also leveraging the Cargo plugin to even start and stop your favorite container for you. Craig Wendy wrote: That was a few days ago. :) Yes, I know, I never got back to this. Sorry, it's been a heck of a month this week ;) My questions would have been about the POM changes that Sean eluded to during our mini hackathon. I could be wrong, but I thought he said there would be an issue with something we needed and it not being published yet and that may or may not have stemmed from a private conversation you may or may not have had over IM. Sorry, the details are still a little cloudy. Forget about it for now, I'm sure if it's a problem we'll know as soon as we begin adding more projects to Continuum. -- James Mitchell On Jun 19, 2006, at 9:20 PM, Wendy Smoak wrote: On 6/14/06, James Mitchell [EMAIL PROTECTED] wrote: Yes. There is a wiki page for this as well. http://wiki.apache.org/struts/StrutsContinuum It's a work in progress, and I'm
Re: [all] Struts Nightly builds [was Re: Continnum Is Up]
Ok, with my latest change, we now have the 1.2.x nightlies back online. http://people.apache.org/builds/struts/action1/1.2.x/ The only hickup was the log file, but that's already resolved and I'm firing off another build in 2 minutes. -- James Mitchell On Jun 20, 2006, at 1:05 AM, James Mitchell wrote: That brings up another interesting problem. Generated docs. I know we try to keep the latest and greatest docs online (main site) but for branched versions (Action 1.2.x), we would need to provide the docs as well. So it might look like... http://people.apache.org/builds/struts/action1/1.2.x/docs/ -- 1.2 docs here http://people.apache.org/builds/struts/action1/1.2.x/binary/ http://people.apache.org/builds/struts/action1/1.2.x/lib/ http://people.apache.org/builds/struts/action1/1.2.x/src/ ...and if we did the same for others... http://people.apache.org/builds/struts/shale/docs/ http://people.apache.org/builds/struts/shale/shale-blank/ http://people.apache.org/builds/struts/shale/shale-clay-usecases/ http://people.apache.org/builds/struts/shale/shale-framework/ http://people.apache.org/builds/struts/shale/shale-mailreader/ http://people.apache.org/builds/struts/shale/shale-sql-browser/ http://people.apache.org/builds/struts/shale/shale-usecases/ Maybe 1.2.x is a special case or maybe we should just do it anyway so we can see the latest and greatest documentation (build hourly is even possible). -- James Mitchell On Jun 20, 2006, at 12:19 AM, Wendy Smoak wrote: On 6/19/06, James Mitchell [EMAIL PROTECTED] wrote: Craig, I've already zapped the 'maven' directory, can we: 1. remove the extra directory 'maven2' and just have p.a.o/builds/ struts/shale (requires you to change your scp script)? Related: I'm using http://people.apache.org/builds/struts/maven2/shale/site temporarily, staging the site locally wasn't working very well. Let me know if that's a problem, I can change the URLs and deploy it somewhere else. -- Wendy - 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: [jira] Created: (WW-1348) Setup Nightly Builds of SAF2
Would you care if we use this ticket for all Struts projects? (Action 1.2.x, 1.3.x, 2.0.x, Shale, and Tiles) Sean and I are meeting today for our mini hackathon and it might be a good idea to keep all of these together. -- James Mitchell On Jun 14, 2006, at 7:29 AM, Ted Husted (JIRA) wrote: Setup Nightly Builds of SAF2 Key: WW-1348 URL: http://issues.apache.org/struts/browse/WW-1348 Project: Struts Action 2 Type: Task Components: Misc Versions: 2.0.0 Reporter: Ted Husted Priority: Critical -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (WW-1348) Setup Nightly Builds of SAF2
I stated to do that, and then realized that might be confusing, since we have a JIRA project for each subproject. Do we want to setup an INFRA or SITE project? -Ted. On 6/14/06, James Mitchell [EMAIL PROTECTED] wrote: Would you care if we use this ticket for all Struts projects? (Action 1.2.x, 1.3.x, 2.0.x, Shale, and Tiles) Sean and I are meeting today for our mini hackathon and it might be a good idea to keep all of these together. -- James Mitchell On Jun 14, 2006, at 7:29 AM, Ted Husted (JIRA) wrote: Setup Nightly Builds of SAF2 Key: WW-1348 URL: http://issues.apache.org/struts/browse/WW-1348 Project: Struts Action 2 Type: Task Components: Misc Versions: 2.0.0 Reporter: Ted Husted Priority: Critical -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted. * http://www.husted.com/struts/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Created: (WW-1348) Setup Nightly Builds of SAF2
I'm fine with combining the tasks as long as they are all resolved in one fell swoop. Considering we generally have little spare time to work on open source projects, I'd like to see tickets at a level of granularity that it only requires a few hours to resolve them, avoiding the basically unresolvable tickets like Struts Action 1 had (Struts fails in too many places, etc). Don James Mitchell wrote: Would you care if we use this ticket for all Struts projects? (Action 1.2.x, 1.3.x, 2.0.x, Shale, and Tiles) Sean and I are meeting today for our mini hackathon and it might be a good idea to keep all of these together. -- James Mitchell On Jun 14, 2006, at 7:29 AM, Ted Husted (JIRA) wrote: Setup Nightly Builds of SAF2 Key: WW-1348 URL: http://issues.apache.org/struts/browse/WW-1348 Project: Struts Action 2 Type: Task Components: Misc Versions: 2.0.0 Reporter: Ted Husted Priority: Critical --This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - 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: [jira] Created: (WW-1348) Setup Nightly Builds of SAF2
I went ahead and setup a SITE project in JIRA where we can log issues with the Site subproject along with the Maven builds, Continuum, et cetera, and added a ticket for Minihachathon James mentioned. * http://issues.apache.org/struts/browse/SITE-1 and made setting up the SAF2 nightly a subtask of that. -Ted. On 6/14/06, Ted Husted [EMAIL PROTECTED] wrote: I stated to do that, and then realized that might be confusing, since we have a JIRA project for each subproject. Do we want to setup an INFRA or SITE project? -Ted. On 6/14/06, James Mitchell [EMAIL PROTECTED] wrote: Would you care if we use this ticket for all Struts projects? (Action 1.2.x, 1.3.x, 2.0.x, Shale, and Tiles) Sean and I are meeting today for our mini hackathon and it might be a good idea to keep all of these together. -- James Mitchell On Jun 14, 2006, at 7:29 AM, Ted Husted (JIRA) wrote: Setup Nightly Builds of SAF2 Key: WW-1348 URL: http://issues.apache.org/struts/browse/WW-1348 Project: Struts Action 2 Type: Task Components: Misc Versions: 2.0.0 Reporter: Ted Husted Priority: Critical -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted. * http://www.husted.com/struts/ -- HTH, Ted. * http://www.husted.com/struts/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Shale] Nightly Builds Resumed
For those of you following Shale, you've probably noticed that there have not been any nightly builds available for the past few weeks. This was due to a combination of circumstances, but the primary reason is we've been focusing on migrating the build environment from Ant-based scripts to use Maven2 instead. When completed, it will be *much* easier to build Shale, or applications based on Shale. However, in the mean time, I'm pleased to announce that creation of nightly builds for Shale have been restored. You can get the 20060612 version from: http://people.apache.org/builds/struts/nightly/struts-shale/ NOTES: * The Shale website currently has a bad link to this page (it points at cvs.apache.org). That will be fixed soon. In the mean time, use the link above. * When the conversion to Maven2 is complete, the organization of the artifacts published as nightly builds (as well as the organization of Shale releases as well) will be changed. Watch here for an announcement of the date that this goes into effect for the nightly builds. Craig McClanahan
Re: [Shale] Nightly Builds Resumed
Craig, James and I are going to attempt to setup the Shale continuum server on Wednesday. Should we try to setup the publishing of Shale nightlies as well? Sean On 6/12/06, Craig McClanahan [EMAIL PROTECTED] wrote: For those of you following Shale, you've probably noticed that there have not been any nightly builds available for the past few weeks. This was due to a combination of circumstances, but the primary reason is we've been focusing on migrating the build environment from Ant-based scripts to use Maven2 instead. When completed, it will be *much* easier to build Shale, or applications based on Shale. However, in the mean time, I'm pleased to announce that creation of nightly builds for Shale have been restored. You can get the 20060612 version from: http://people.apache.org/builds/struts/nightly/struts-shale/ NOTES: * The Shale website currently has a bad link to this page (it points at cvs.apache.org). That will be fixed soon. In the mean time, use the link above. * When the conversion to Maven2 is complete, the organization of the artifacts published as nightly builds (as well as the organization of Shale releases as well) will be changed. Watch here for an announcement of the date that this goes into effect for the nightly builds. Craig McClanahan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Shale] Nightly Builds Resumed
On 6/12/06, Craig McClanahan [EMAIL PROTECTED] wrote: For maximum user benefit, it's nice to ship sample apps ready to run, with all their dependent jars included. But with four apps already, that would mean lots of jar files duplicated -- which would really bloat an all-in-one download. For the Ant based builds, I took the tack of creating several kinds of artifacts: * A zip of the framework itself (library jars, sources, javadocs) * A zip of the dependencies (which Maven will eliminate the need for I think 'jars without dependencies' is possible. Asking for the dependencies, but not the jar they came from, might be more difficult. Could the second one be a library distribution of Shale + dependencies? * A war file for each example (ideally with a buildable source module and javadocs for the application classes included inside). It's usually WEB-INF/src for the sources, but I haven't seen Javadocs in a .war file. WEB-INF/apidocs? (There's an example of copying the sources in Struts Action, probably in apps/pom.xml.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Shale] Nightly Builds Resumed
That would be awesome! But I wouldn't bother setting up the Ant based builds, though; the focus should be on getting the Maven based things to work. A wrinkle is you might have to be a bit adaptable on the assembly stuff, as we're not quite done creating that. And, that actually raises a question about what MyFaces is doing on the topic of sample applications (as well as to solicit advice from other folks here as well). I will try to take a look tomorrow night and see where things stand with the maven build. Even if we don't get things running completely the main thing is to get continuum up and running. Also, it will be good to build the jars at a minimum just to make sure everything is compiling and things are running smoothly. We can add the assembly and publish stuff later. For maximum user benefit, it's nice to ship sample apps ready to run, with all their dependent jars included. But with four apps already, that would mean lots of jar files duplicated -- which would really bloat an all-in-one download. For the Ant based builds, I took the tack of creating several kinds of artifacts: * A zip of the framework itself (library jars, sources, javadocs) Certainly very easy to do with maven. * A zip of the dependencies (which Maven will eliminate the need for * A war file for each example (ideally with a buildable source module and javadocs for the application classes included inside). What do you think of this kind of strategy for Maven based builds as well? Hmmm good idea. This would come in handy with MyFaces now that you mention it. Of course you have to weigh the possible confusion of missing dependencies vs. the bandwith you save. How are existing shale users responding on the user list? (I'm not currently monitoring that one.) Craig Sean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Shale] Nightly Builds Resumed
On 6/12/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 6/12/06, Craig McClanahan [EMAIL PROTECTED] wrote: For maximum user benefit, it's nice to ship sample apps ready to run, with all their dependent jars included. But with four apps already, that would mean lots of jar files duplicated -- which would really bloat an all-in-one download. For the Ant based builds, I took the tack of creating several kinds of artifacts: * A zip of the framework itself (library jars, sources, javadocs) * A zip of the dependencies (which Maven will eliminate the need for I think 'jars without dependencies' is possible. Asking for the dependencies, but not the jar they came from, might be more difficult. Could the second one be a library distribution of Shale + dependencies? Right now we're creating the framework distro with all the Shale jars + the dependencies ... that seems like the most convenient packaging for a non-Maven user, and the size is currently just over 9mb, which shouldn't be any big deal. (Interestingly, the Shale part of that is 400k ... it's nice to not have to implement everything JSF already provides :-). So I don't really see a need for a separate dependencies-only distro. * A war file for each example (ideally with a buildable source module and javadocs for the application classes included inside). It's usually WEB-INF/src for the sources, but I haven't seen Javadocs in a .war file. WEB-INF/apidocs? (There's an example of copying the sources in Struts Action, probably in apps/pom.xml.) The other way we could do this would be build a src/main/assembly directory for each webapp, and package sources/javadocs/war file with the POM in the expected place (top level directory). It's marginally more complicated for someone to have to extract the WAR, but the project would look like an out-of-the-box Maven module. -- Wendy Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (STR-1287) validator needs internet connection (rc1 and latest nightly builds)
[ http://issues.apache.org/struts/browse/STR-1287?page=all ] Don Brown reopened STR-1287: Assign To: (was: Struts Developer Mailing List) validator needs internet connection (rc1 and latest nightly builds) --- Key: STR-1287 URL: http://issues.apache.org/struts/browse/STR-1287 Project: Struts Action 1 Type: Bug Components: Action Versions: 1.1 RC1 Environment: Operating System: All Platform: All Reporter: Patrick Maes It seems the commons-validator in Struts 1.1rc1 needs a working internet connection. When starting the web-app (e.g. the sample apps), I see in the console: INFO: Loading validation rules file from 'WEB-INF/validator-rules.xml' ... SEVERE: Connection timed out: connect ... (same for validation.xml) This startup sequence takes a long time and Validation doesn't work in the app after that. I've tried also the latest nightly builds (20030309) of struts and commons-validator: same problem. When I replace the bundled commons-validator.jar with version 1.0.1, the problem is gone. Removing the headers in validator-rules.xml and in validation.xml also solves it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (STR-1287) validator needs internet connection (rc1 and latest nightly builds)
[ http://issues.apache.org/struts/browse/STR-1287?page=all ] Don Brown closed STR-1287: -- Resolution: Duplicate validator needs internet connection (rc1 and latest nightly builds) --- Key: STR-1287 URL: http://issues.apache.org/struts/browse/STR-1287 Project: Struts Action 1 Type: Bug Components: Action Versions: 1.1 RC1 Environment: Operating System: All Platform: All Reporter: Patrick Maes It seems the commons-validator in Struts 1.1rc1 needs a working internet connection. When starting the web-app (e.g. the sample apps), I see in the console: INFO: Loading validation rules file from 'WEB-INF/validator-rules.xml' ... SEVERE: Connection timed out: connect ... (same for validation.xml) This startup sequence takes a long time and Validation doesn't work in the app after that. I've tried also the latest nightly builds (20030309) of struts and commons-validator: same problem. When I replace the bundled commons-validator.jar with version 1.0.1, the problem is gone. Removing the headers in validator-rules.xml and in validation.xml also solves it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds experiencing some weirdness
On 1/30/06, James Mitchell [EMAIL PROTECTED] wrote: I believe I've fixed the problem and I am manually running the nightly. If you don't hear anything from me then things are running smoothly. Is there an update? If you ran them yesterday, it didn't work-- only the files from the 24th are left. Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds experiencing some weirdness
On 1/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 1/30/06, James Mitchell [EMAIL PROTECTED] wrote: I believe I've fixed the problem and I am manually running the nightly. If you don't hear anything from me then things are running smoothly. Is there an update? If you ran them yesterday, it didn't work-- only the files from the 24th are left. ... in struts-action, etc., that is: http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/ I do see new files under the 1.2 branch, but nothing for 1.3, not even a log file, since the 24th. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds experiencing some weirdness
Right, it's failing in between the builds 1.2 and 1.3. I'm running it again... -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring 678.910.8017 - Original Message - From: Wendy Smoak [EMAIL PROTECTED] Newsgroups: gmane.comp.jakarta.struts.devel Sent: Tuesday, January 31, 2006 7:35 PM Subject: Re: Nightly builds experiencing some weirdness On 1/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 1/30/06, James Mitchell [EMAIL PROTECTED] wrote: I believe I've fixed the problem and I am manually running the nightly. If you don't hear anything from me then things are running smoothly. Is there an update? If you ran them yesterday, it didn't work-- only the files from the 24th are left. ... in struts-action, etc., that is: http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/ I do see new files under the 1.2 branch, but nothing for 1.3, not even a log file, since the 24th. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds experiencing some weirdness
Seems like the last one took, except I'm seeing a build failure due to a failed copy... ... ... [copy] Copying 1 file to /export/home/jmitchell/svn/struts/build/nightly/struts-apps [copy] Copying 1 file to /export/home/jmitchell/svn/struts/build/nightly/struts-apps BUILD FAILED File.. /export/home/jmitchell/svn/struts/build/maven.xml Element... ant:copy Line.. 58 Column 82 Cannot perform operation from directory to file. Total time: 9 minutes 5 seconds Finished at: Wed Feb 01 02:09:56 GMT+00:00 2006 That line is trying to copy strutsel-exercise-taglib.war. Not sure why it's have an issue, and just visually checking the build artifacts, that should have worked. Oh well, everything else seemed to go fine. Unless someone beats me to it, I'll look at it tomorrow. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring 678.910.8017 - Original Message - From: James Mitchell [EMAIL PROTECTED] Newsgroups: gmane.comp.jakarta.struts.devel Sent: Tuesday, January 31, 2006 8:19 PM Subject: Re: Nightly builds experiencing some weirdness Right, it's failing in between the builds 1.2 and 1.3. I'm running it again... -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring 678.910.8017 - Original Message - From: Wendy Smoak [EMAIL PROTECTED] Newsgroups: gmane.comp.jakarta.struts.devel Sent: Tuesday, January 31, 2006 7:35 PM Subject: Re: Nightly builds experiencing some weirdness On 1/31/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 1/30/06, James Mitchell [EMAIL PROTECTED] wrote: I believe I've fixed the problem and I am manually running the nightly. If you don't hear anything from me then things are running smoothly. Is there an update? If you ran them yesterday, it didn't work-- only the files from the 24th are left. ... in struts-action, etc., that is: http://cvs.apache.org/builds/struts/maven/trunk/nightly/struts-action/ I do see new files under the 1.2 branch, but nothing for 1.3, not even a log file, since the 24th. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Speaking of nightly builds...
The nightly builds for Struts Action and friends have gone missing. The last ones are from the 24th. I assume these are (were!) running on the zone. Can someone please check it? Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Nightly builds experiencing some weirdness
Just an FYI -- the nightly builds (performed via a cron job on our zone) suddenly stopped working after 1/24/06. I could be wrong, but this seems to coincide with the recent zone 'down time' or 'maintenance' announcement around that time. The logs [0] indicate that Maven can no longer find JAVA_HOME whereas the process ran untouched for many months without a hitch. I believe I've fixed the problem and I am manually running the nightly. If you don't hear anything from me then things are running smoothly. Thanks. [0] http://svn.apache.org/builds/struts/maven/STRUTS_1_2_BRANCH/nightly/logs/nightly-20060124.log http://svn.apache.org/builds/struts/maven/STRUTS_1_2_BRANCH/nightly/logs/nightly-20060125.log -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring 678.910.8017 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Speaking of nightly builds...
Wow, great minds think alike! I sent the same thing in another thread at the same time. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring 678.910.8017 - Original Message - From: Wendy Smoak [EMAIL PROTECTED] Newsgroups: gmane.comp.jakarta.struts.devel Sent: Monday, January 30, 2006 9:45 PM Subject: Speaking of nightly builds... The nightly builds for Struts Action and friends have gone missing. The last ones are from the 24th. I assume these are (were!) running on the zone. Can someone please check it? Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10294] - bean:define not working in 6/25, 6/26, 6/27 Nightly builds
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=10294. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=10294 [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|--- |1.1 Family -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17812] - validator needs internet connection (rc1 and latest nightly builds)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=17812. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=17812 [EMAIL PROTECTED] changed: What|Removed |Added Component|Validator Framework |Action -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [shale] nightly builds
James, I will have to get some more info on the zones from you. I am VERY behind on my site-dev reading and apparently I have missed a lot. Maybe at some point you could help us set this up for MyFaces as well? There is already an effort to migrate the build to Maven so maybe we could use most of your work on this ... sean On 11/4/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 11/4/05, James Mitchell [EMAIL PROTECTED] wrote: There is still a small chance that infra could yank the zone from us or do something to cause it be (or need to be) wiped clean. And so, knowing this I've kept everything in svn, so that recovery is a matter of: a) finding a different box b) svn co the project c) cp maven-nightly.sh.current nightly.sh d) chmod u+x nightly.sh e) copy my public key to .ssh/authorized_keys on the target box f) setup a crontab And except for that weird issue with automount, it has been running like a champ, totally hands off. Cool. I'm still tweaking what you gave me, so what I'll do is (once my tweaks actually work ;), begin building/scp-ing the nightlies to a different (not over yours) location. This will be a staging area of sorts, until you decide that you are comfortable with the nightly process on the zone. That sounds great. Having it on the zone would mean more people than just me could maintain and fix it, so that would be goodness. I know you are/were building some of the commons nightlies too, we can certainly pick that up for you if you like. (??) That's be great (for the same reasons) ... the only question is whether we should do this in the Struts zone or not :-). I'll send you that script separately ... it's actually simpler because the process for each individual commons package is identical. Craig -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan -- -- - 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] - 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: [shale] nightly builds
I'd be happy to help. Although last I remember, you guys didn't want anything to do with Maven. Has that changed? -- James Mitchell 678.910.8017 On Nov 5, 2005, at 9:10 PM, Sean Schofield wrote: James, I will have to get some more info on the zones from you. I am VERY behind on my site-dev reading and apparently I have missed a lot. Maybe at some point you could help us set this up for MyFaces as well? There is already an effort to migrate the build to Maven so maybe we could use most of your work on this ... sean On 11/4/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 11/4/05, James Mitchell [EMAIL PROTECTED] wrote: There is still a small chance that infra could yank the zone from us or do something to cause it be (or need to be) wiped clean. And so, knowing this I've kept everything in svn, so that recovery is a matter of: a) finding a different box b) svn co the project c) cp maven-nightly.sh.current nightly.sh d) chmod u+x nightly.sh e) copy my public key to .ssh/authorized_keys on the target box f) setup a crontab And except for that weird issue with automount, it has been running like a champ, totally hands off. Cool. I'm still tweaking what you gave me, so what I'll do is (once my tweaks actually work ;), begin building/scp-ing the nightlies to a different (not over yours) location. This will be a staging area of sorts, until you decide that you are comfortable with the nightly process on the zone. That sounds great. Having it on the zone would mean more people than just me could maintain and fix it, so that would be goodness. I know you are/were building some of the commons nightlies too, we can certainly pick that up for you if you like. (??) That's be great (for the same reasons) ... the only question is whether we should do this in the Struts zone or not :-). I'll send you that script separately ... it's actually simpler because the process for each individual commons package is identical. Craig -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan --- --- -- - 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] - 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: [shale] nightly builds
I'd be happy to help. Although last I remember, you guys didn't want anything to do with Maven. Has that changed? Well 'never' might be a little strong. We haven't exactly made it a priority but several of us remain on the persuadable side. Have you made a true believer out of Craig yet? Our user base is growing and we are getting more volunteers to step forward and they are taking a crack at a Maven2 script. If Maven works nicely with the new zone solution then I might be interested in taking another look. sean -- James Mitchell 678.910.8017 On Nov 5, 2005, at 9:10 PM, Sean Schofield wrote: James, I will have to get some more info on the zones from you. I am VERY behind on my site-dev reading and apparently I have missed a lot. Maybe at some point you could help us set this up for MyFaces as well? There is already an effort to migrate the build to Maven so maybe we could use most of your work on this ... sean On 11/4/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 11/4/05, James Mitchell [EMAIL PROTECTED] wrote: There is still a small chance that infra could yank the zone from us or do something to cause it be (or need to be) wiped clean. And so, knowing this I've kept everything in svn, so that recovery is a matter of: a) finding a different box b) svn co the project c) cp maven-nightly.sh.current nightly.sh d) chmod u+x nightly.sh e) copy my public key to .ssh/authorized_keys on the target box f) setup a crontab And except for that weird issue with automount, it has been running like a champ, totally hands off. Cool. I'm still tweaking what you gave me, so what I'll do is (once my tweaks actually work ;), begin building/scp-ing the nightlies to a different (not over yours) location. This will be a staging area of sorts, until you decide that you are comfortable with the nightly process on the zone. That sounds great. Having it on the zone would mean more people than just me could maintain and fix it, so that would be goodness. I know you are/were building some of the commons nightlies too, we can certainly pick that up for you if you like. (??) That's be great (for the same reasons) ... the only question is whether we should do this in the Struts zone or not :-). I'll send you that script separately ... it's actually simpler because the process for each individual commons package is identical. Craig -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan --- --- -- - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: [shale] nightly builds
On 11/5/05, Sean Schofield [EMAIL PROTECTED] wrote: I'd be happy to help. Although last I remember, you guys didn't want anything to do with Maven. Has that changed? Well 'never' might be a little strong. We haven't exactly made it a priority but several of us remain on the persuadable side. Have you made a true believer out of Craig yet? No :-). But it's not as big a deal now that we have several folks willing to do all the hard work :-). Our user base is growing and we are getting more volunteers to step forward and they are taking a crack at a Maven2 script. If Maven works nicely with the new zone solution then I might be interested in taking another look. Maven and zones seem like orthogonal issues??? There are certainly things Maven makes easy, like the site:deploy target, but those all seem possible to do from a standalone desktop as well, using either cron (Unix/Linux systems) or the job scheduler (Windows). Any, it's straightforward to install any software you want on your own zone, so you can have it your way. Basically, zones are a Solaris feature that essentially gives you your own private virtual world (including a root login) on a shared box. Each TLP (such as myfaces or struts) can have one just by asking the infrastructure folks to set it up, as long as the PMC is willing to provide administrative support. One nice advantage is that you can run your own Tomcat instance, for example, so you can have live demos of components or whatever. At the moment, zones are still somewhat experimental and subject to being reinstalled, so keep good backups. But it's a very elegant way for TLPs to take responsibility for some live functionality, without overburdening an already strected infra crew that is doing such a good job of keeping the Apache infrastructure functioning. sean Craig -- James Mitchell 678.910.8017 On Nov 5, 2005, at 9:10 PM, Sean Schofield wrote: James, I will have to get some more info on the zones from you. I am VERY behind on my site-dev reading and apparently I have missed a lot. Maybe at some point you could help us set this up for MyFaces as well? There is already an effort to migrate the build to Maven so maybe we could use most of your work on this ... sean On 11/4/05, Craig McClanahan [EMAIL PROTECTED] wrote: On 11/4/05, James Mitchell [EMAIL PROTECTED] wrote: There is still a small chance that infra could yank the zone from us or do something to cause it be (or need to be) wiped clean. And so, knowing this I've kept everything in svn, so that recovery is a matter of: a) finding a different box b) svn co the project c) cp maven-nightly.sh.current nightly.sh d) chmod u+x nightly.sh e) copy my public key to .ssh/authorized_keys on the target box f) setup a crontab And except for that weird issue with automount, it has been running like a champ, totally hands off. Cool. I'm still tweaking what you gave me, so what I'll do is (once my tweaks actually work ;), begin building/scp-ing the nightlies to a different (not over yours) location. This will be a staging area of sorts, until you decide that you are comfortable with the nightly process on the zone. That sounds great. Having it on the zone would mean more people than just me could maintain and fix it, so that would be goodness. I know you are/were building some of the commons nightlies too, we can certainly pick that up for you if you like. (??) That's be great (for the same reasons) ... the only question is whether we should do this in the Struts zone or not :-). I'll send you that script separately ... it's actually simpler because the process for each individual commons package is identical. Craig -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I
Re: [shale] nightly builds
There is still a small chance that infra could yank the zone from us or do something to cause it be (or need to be) wiped clean. And so, knowing this I've kept everything in svn, so that recovery is a matter of: a) finding a different box b) svn co the project c) cp maven-nightly.sh.current nightly.sh d) chmod u+x nightly.sh e) copy my public key to .ssh/authorized_keys on the target box f) setup a crontab And except for that weird issue with automount, it has been running like a champ, totally hands off. I'm still tweaking what you gave me, so what I'll do is (once my tweaks actually work ;), begin building/scp-ing the nightlies to a different (not over yours) location. This will be a staging area of sorts, until you decide that you are comfortable with the nightly process on the zone. I know you are/were building some of the commons nightlies too, we can certainly pick that up for you if you like. (??) -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan -- -- - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [shale] nightly builds
On 11/4/05, James Mitchell [EMAIL PROTECTED] wrote: There is still a small chance that infra could yank the zone from us or do something to cause it be (or need to be) wiped clean. And so, knowing this I've kept everything in svn, so that recovery is a matter of: a) finding a different box b) svn co the project c) cp maven-nightly.sh.current nightly.sh d) chmod u+x nightly.sh e) copy my public key to .ssh/authorized_keys on the target box f) setup a crontab And except for that weird issue with automount, it has been running like a champ, totally hands off. Cool. I'm still tweaking what you gave me, so what I'll do is (once my tweaks actually work ;), begin building/scp-ing the nightlies to a different (not over yours) location. This will be a staging area of sorts, until you decide that you are comfortable with the nightly process on the zone. That sounds great. Having it on the zone would mean more people than just me could maintain and fix it, so that would be goodness. I know you are/were building some of the commons nightlies too, we can certainly pick that up for you if you like. (??) That's be great (for the same reasons) ... the only question is whether we should do this in the Struts zone or not :-). I'll send you that script separately ... it's actually simpler because the process for each individual commons package is identical. Craig -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:11 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan -- -- - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[shale] nightly builds
I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan
Re: [shale] nightly builds
I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [shale] nightly builds
Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan - 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: [shale] nightly builds
On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan - 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: [shale] nightly builds
So, does that mean you do not want me to add the ant process to the zone builds? -- James Mitchell 678.910.8017 On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan - 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: [shale] nightly builds
On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: So, does that mean you do not want me to add the ant process to the zone builds? I fixed it on my desktop for tonight. Are we confident enough in the zone builds to run nightlies from there instead? If so, I'll just comment it out of my crontab. Also, have you had a chance to mess with the nightly builds for the commons packages also, or is that a separate kettle of fish? -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 1:33 PM, Craig McClanahan wrote: On 11/3/05, James Mitchell [EMAIL PROTECTED] wrote: Um, sorry, the build failed (which I half expected anyway, not having run it on the particular machine yet) so I'll rework a few things and kick it off again. I'll ping the list when they are available. Thanks. Thanks James. I was also able to access my home desktop and figured out what was going wrong (I botched a PATH setup when I reorganized my system a bit), so tonight's nightlies should be produced on schedule. -- James Mitchell 678.910.8017 Craig On Nov 3, 2005, at 12:49 PM, James Mitchell wrote: I have Craig's nightly script and I am running it as I type this. Look for some nightlies in a few minutes. -- James Mitchell 678.910.8017 On Nov 3, 2005, at 10:59 AM, Ryan Wynn wrote: I was hoping to get the latest build of shale, to get the latest clay changes, and I noticed that the latest nightly build is from 10/28. Is there a reason why there is no 11/3 build? Thanks, Ryan - 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: Nightly builds?
It looks like everyone's home directory was deleted on the zone. This is something we knew might happen, and I was willing to take the risk, because recovery was minimal. Thanks for the heads up. I'll restore my nightly process on my home machine. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Oct 30, 2005, at 3:53 PM, Wendy Smoak wrote: Have the nightly builds moved? The most recent one for any of the sub-projects is dated 20051026. http://svn.apache.org/builds/struts/ maven/trunk/nightly/ Thanks, Wendy - 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: Nightly builds?
On 10/31/05, James Mitchell [EMAIL PROTECTED] wrote: It looks like everyone's home directory was deleted on the zone. Ouch. I just sent a request to infra to ask for some advance notice next time. ;-) -- Martin Cooper This is something we knew might happen, and I was willing to take the risk, because recovery was minimal. Thanks for the heads up. I'll restore my nightly process on my home machine. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Oct 30, 2005, at 3:53 PM, Wendy Smoak wrote: Have the nightly builds moved? The most recent one for any of the sub-projects is dated 20051026. http://svn.apache.org/builds/struts/ maven/trunk/nightly/ Thanks, Wendy - 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]
Nightly builds?
Have the nightly builds moved? The most recent one for any of the sub-projects is dated 20051026. http://svn.apache.org/builds/struts/maven/trunk/nightly/ Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Nightly builds for BSF and Flow
James, can you please check the nightly builds for BSF and Flow? 'maven clean dist' works here. Try deleting the 'build' directory under both of them and updating again. Thanks, Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds for BSF and Flow
From: James Mitchell [EMAIL PROTECTED] The nightlies are actually built from a clean checkout of http:// svn.apache.org/repos/asf/struts/current/. So, doing a 'clean' doesn't really apply here. What specifically is the issue? Are we missing nightlies? Yes. http://svn.apache.org/builds/struts/maven/trunk/nightly/struts-bsf/ The last nightly for BSF was the 21st. The log shows CheckStyle complaining that it can't find the license file, which made me think the update wasn't working. But if it's a clean checkout... I have no idea. I recently added the license and notice to BSF (and Flow) after changing the build files so they don't depend on the common build. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds - Status -- READ THIS
Please take a look at this: http://people.apache.org/~jmitchell/docs/ Unless someone says otherwise, I am planning to add to the nightly build a process that zips up the documentation generated by 'maven multiproject:site' in current/site (which are generated to current/ site/target/docs) and deploy it over the current Struts web site. *EVERY NIGHT* And as discussed, I have planned to add additional documentation for older versions of Struts. The only living documentation is in HEAD and STRUTS_1_2_BRANCH. All other docs are static at this point. I am planning to put our documentation under the following: (left nav pane from the main site) Apache Struts Project Welcome Who We Are Announcements Struts 1.2.x-- documentation from STRUTS_1_2_BRANCH Struts 1.2.7-- documentation as was delivered in the 1.2.7 dist Struts 1.2.4-- same as above, but for 1.2.4 Struts 1.1 -- same as above, but for 1.1 Struts 1.0.2-- same as above, but for 1.0.2 Please let me know is we want to add to this or change it in any way. -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Sep 27, 2005, at 6:21 PM, Wendy Smoak wrote: From: James Mitchell [EMAIL PROTECTED] I am planning to deploy the generated site over cvs.apache.org:/ www/ struts.apache.org/ which means our existing web site will never be more than 24 hours old. I don't see a link to the 1.2.7 docs in site/xdocs/navigation.xml. I remember some discussion of what URL to use for the docs for prior versions, and Ted had a suggestion which sounded fine at the time, but I can't find the message in the archives. -- Wendy - 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: Nightly builds - Status -- READ THIS
From: James Mitchell [EMAIL PROTECTED] I am planning to put our documentation under the following: (left nav pane from the main site) Apache Struts Project Welcome Who We Are Announcements Struts 1.2.x-- documentation from STRUTS_1_2_BRANCH Struts 1.2.7-- documentation as was delivered in the 1.2.7 dist Struts 1.2.4-- same as above, but for 1.2.4 Struts 1.1 -- same as above, but for 1.1 Struts 1.0.2-- same as above, but for 1.0.2 I finally found the message I was looking for[0], in which Ted wrote: For consistency, we might want to treat the docs like they were an artifact, which would imply a third form, struts-doc-1.2 :) So we'll have: http://struts.apache.org/struts-doc-1.2/index.html http://struts.apache.org/struts-doc-1.2.7/index.html (and so on...) [0] http://marc.theaimsgroup.com/?l=struts-devm=112567270524054 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds - Status
Ok, I've been monitoring the nightlies for a few days now and it looks to be completely hands off and it all happens on Apache hardware. I also made sure that all configuration for doing the nightlies are included either as files (nightly.sh) or as configuration (cron job config), so in a worse case scenario, we can be back up at a moments notice. Next, I want to bring in the site generation for both 1.2.x and head. I am planning to deploy the generated site over cvs.apache.org:/www/ struts.apache.org/ which means our existing web site will never be more than 24 hours old. If we don't want to do that, I could put together something like a web console hosted on struts.zones.apache.org that we can use to kick off an update.or some kind of hook so that when a commit is made to the documentation, a process is queued to regenerate and deploy a new site after 4 hours. I would also like to build in email notification if the nightly and/ or site generation fails like Gump gives us. The only issue with relying on Gump is that Gump does not build all of what the nightlies build, especially documentation. Your thoughts? -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Sep 24, 2005, at 1:29 AM, James Mitchell wrote: Ok, that's what I needed. I'll see if I can pull it all together. Thanks -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Sep 24, 2005, at 12:09 AM, Wendy Smoak wrote: From: James Mitchell [EMAIL PROTECTED] BTW -- Can you tell me (wiki, mail-archive, etc) where to get the latest instructions to build the web site and documentation and how we want it laid out? I'm getting ready to add that task to the nightly build and I don't want to do it wrong. I haven't been able to get Maven to build a recursive multiproject site. It either loops, or refuses to descend. Here's what I have: echo -- build multiproject site (head) -- cd /cygdrive/e/svn/struts/current/site/ maven multiproject:site /path/to/build.log echo -- build multiproject site (head - Shale) -- cd /cygdrive/e/svn/struts/current/shale/build maven multiproject:site /path/to/build.log cp -r target/docs/* ../../site/target/docs/shale echo -- build multiproject site (head - Sandbox) -- cd /cygdrive/e/svn/struts/current/sandbox/ maven multiproject:site /path/to/build.log cp -r target/docs/* ../site/target/docs/struts-sandbox If you have a multiproject site for Ti, then you'd do the same thing, and copy it up to sandbox/target/docs/struts-ti before you copy the whole of sandbox/target/docs over to 'site'. Or maybe you can get Maven to cooperate. :) HTH, -- Wendy - 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: Nightly builds - Status
From: James Mitchell [EMAIL PROTECTED] I am planning to deploy the generated site over cvs.apache.org:/www/ struts.apache.org/ which means our existing web site will never be more than 24 hours old. I don't see a link to the 1.2.7 docs in site/xdocs/navigation.xml. I remember some discussion of what URL to use for the docs for prior versions, and Ted had a suggestion which sounded fine at the time, but I can't find the message in the archives. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds - Status
From: James Mitchell [EMAIL PROTECTED] I think now would be a good time to discuss the Struts website. I know Wendy and Ted have been making a lot of changes and I honestly haven't been keeping up with it all. I think we've already decided to do everything you mentioned-- go back to publishing the latest and greatest on the website every night, keep docs for prior versions available, etc. Speaking of the prior versions, why do we have the 1.0 and 1.1 API files under site/xdocs/legacy? Can't they be generated from their respective branches if needed? -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds - Status
Yes, that's possible, but not likely to be needed, since it is just extra overhead to generate something that will never change. BTW -- Can you tell me (wiki, mail-archive, etc) where to get the latest instructions to build the web site and documentation and how we want it laid out? I'm getting ready to add that task to the nightly build and I don't want to do it wrong. Your thoughts? -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Sep 23, 2005, at 12:14 PM, Wendy Smoak wrote: From: James Mitchell [EMAIL PROTECTED] I think now would be a good time to discuss the Struts website. I know Wendy and Ted have been making a lot of changes and I honestly haven't been keeping up with it all. I think we've already decided to do everything you mentioned-- go back to publishing the latest and greatest on the website every night, keep docs for prior versions available, etc. Speaking of the prior versions, why do we have the 1.0 and 1.1 API files under site/xdocs/legacy? Can't they be generated from their respective branches if needed? -- Wendy - 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: Nightly builds - Status
From: James Mitchell [EMAIL PROTECTED] BTW -- Can you tell me (wiki, mail-archive, etc) where to get the latest instructions to build the web site and documentation and how we want it laid out? I'm getting ready to add that task to the nightly build and I don't want to do it wrong. I haven't been able to get Maven to build a recursive multiproject site. It either loops, or refuses to descend. Here's what I have: echo -- build multiproject site (head) -- cd /cygdrive/e/svn/struts/current/site/ maven multiproject:site /path/to/build.log echo -- build multiproject site (head - Shale) -- cd /cygdrive/e/svn/struts/current/shale/build maven multiproject:site /path/to/build.log cp -r target/docs/* ../../site/target/docs/shale echo -- build multiproject site (head - Sandbox) -- cd /cygdrive/e/svn/struts/current/sandbox/ maven multiproject:site /path/to/build.log cp -r target/docs/* ../site/target/docs/struts-sandbox If you have a multiproject site for Ti, then you'd do the same thing, and copy it up to sandbox/target/docs/struts-ti before you copy the whole of sandbox/target/docs over to 'site'. Or maybe you can get Maven to cooperate. :) HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds - Status
Ok, that's what I needed. I'll see if I can pull it all together. Thanks -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. http://www.edgetechservices.net/ 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED] Skype: callto://jmitchtx On Sep 24, 2005, at 12:09 AM, Wendy Smoak wrote: From: James Mitchell [EMAIL PROTECTED] BTW -- Can you tell me (wiki, mail-archive, etc) where to get the latest instructions to build the web site and documentation and how we want it laid out? I'm getting ready to add that task to the nightly build and I don't want to do it wrong. I haven't been able to get Maven to build a recursive multiproject site. It either loops, or refuses to descend. Here's what I have: echo -- build multiproject site (head) -- cd /cygdrive/e/svn/struts/current/site/ maven multiproject:site /path/to/build.log echo -- build multiproject site (head - Shale) -- cd /cygdrive/e/svn/struts/current/shale/build maven multiproject:site /path/to/build.log cp -r target/docs/* ../../site/target/docs/shale echo -- build multiproject site (head - Sandbox) -- cd /cygdrive/e/svn/struts/current/sandbox/ maven multiproject:site /path/to/build.log cp -r target/docs/* ../site/target/docs/struts-sandbox If you have a multiproject site for Ti, then you'd do the same thing, and copy it up to sandbox/target/docs/struts-ti before you copy the whole of sandbox/target/docs over to 'site'. Or maybe you can get Maven to cooperate. :) HTH, -- Wendy - 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: Nightly builds - Status
I agree.
I now have the 1.2 branch fully automated and on a cron job. The
only thing that makes this setup not 100% perfect is the fact that it
needs a committer account to push the nightlies over to minotaur.
I just checked in a copy of the nightly script that I am using. And
the job is set up to run tonight at 11:30 PST. If it fails I'll keep
at it till it is hands free.
Now, I'm off to revisit the mailreader application.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 22, 2005, at 12:17 AM, Martin Cooper wrote:
On 9/21/05, James Mitchell [EMAIL PROTECTED] wrote:
My goal is to have the sources for both 1.2.7 branch and HEAD in such
a way that if Infra decides to zap the zones, that I can just flip on
my cron job again and poof (just as quickly) we are back in business.
Right. My point was that we'd have lost a week's worth of
nightlies, so if
there are problems with the latest one, we can't tell people to
pick up one
from a few days ago. But maybe we don't care enough about that to
worry
about it.
--
Martin Cooper
I'm half way there. The 1.2 branch build is complete, and now being
built and uploaded from the zone to minotar (the normal nightly spot)
using my account. It is still not automated (crontab), but it's
there. And let me just say, that machine simply screems! I can do a
full release of the 1.2 branch in about 35 seconds (not counting
download-dependencies). It was at about 3 or 4 minutes on my linux
box.
For HEAD, this means getting the maven build streamlined, which I've
already done some work on, but things could be even faster. I'll
keep plugging away, but be aware that someone is bound to notice the
missing nightlies for 1.3.x.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 21, 2005, at 1:40 PM, Martin Cooper wrote:
On 9/20/05, James Mitchell [EMAIL PROTECTED] wrote:
I have finally gotten around to finishing the setup of my
account on
our zone (http://www.apache.org/dev/solaris-zones.html) and
thanks to
Martin and Google, I'm now able to fully build the nightly (by
hand)
of the entire Struts project.
Woohoo! :-)
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up'
portion of
the script. This basically caused Maven do say oh cool, nothings
changed, let's not build any artifacts, and the rest of the shell
script just happily uploads the same jars from the last build. This
explains the mismatch in date/name of some of the nightly
artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/)http://
struts.zones.apache.org/~jmitchell/nightly/)
http://
struts.zones.apache.org/~jmitchell/nightly/)http://
struts.zones.apache.org/~jmitchell/nightly/)
.
I also updated the
readme on the regular nightly download page to point to this
interim
spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are
configured to
pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to Where will the nightlies live?.
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org http://cvs.apache.org http://cvs.apache.org
b) build via a generic account and scp via a valid account
(committer
account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
As Craig mentioned, the zones are, in theory, still subject to
disappearing
in a puff of bits, so I'd prefer to see the nightlies pushed to
minotaur so
that they're still around if that does ever happen. I think we
should have a
'build' account on the zone that does the actual building; I don't
have any
good ideas on the key to use to push them over when they're done.
That said, with Justin and Leo both stepping back from infra@, and
several
others being, uh, less prominent than they used to be, it's not
clear that
much of anything is going to happen on the zones machine in the
near future
that would disrupt us.
If we do distribute from the zone itself, it would be nice to have
a URL
more
Re: Nightly builds - Status
Oh, I almost forgot.
I think now would be a good time to discuss the Struts website. I
know Wendy and Ted have been making a lot of changes and I honestly
haven't been keeping up with it all.
What is the status of it?
Can we begin pushing this content to the struts.apache.org now? Or
should we wait?
I'd also like to get some feedback on an idea I was thinking about
recently. The content of struts.apache.org has traditionally been
the latest and greatest (including javadocs) even if it took us
months between uploads ;)
Can we add a new section on the main page that provides links to all
previous documents?
I was thinking...like, how we have:
Subprojects
BSF Scripting
JavaServer Faces Integration
Shale Framework
Struts Flow
Documentation
User and Developer Guides
Release Notes
Javadoc
FAQs and Howtos
Community
Mailing Lists
Wiki Pages
Resource Directory
Known Issues (Bugzilla)
We can add a section for old releases:
Historical Documentation
Struts 1.0.2
Struts 1.1
Struts 1.2.2
Struts 1.2.6
Struts 1.2.7
I don't mean just the javadocs either, I mean the entire project site
documentation.
Your thoughts?
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 22, 2005, at 9:11 PM, James Mitchell wrote:
I agree.
I now have the 1.2 branch fully automated and on a cron job. The
only thing that makes this setup not 100% perfect is the fact that
it needs a committer account to push the nightlies over to minotaur.
I just checked in a copy of the nightly script that I am using.
And the job is set up to run tonight at 11:30 PST. If it fails
I'll keep at it till it is hands free.
Now, I'm off to revisit the mailreader application.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 22, 2005, at 12:17 AM, Martin Cooper wrote:
On 9/21/05, James Mitchell [EMAIL PROTECTED] wrote:
My goal is to have the sources for both 1.2.7 branch and HEAD in
such
a way that if Infra decides to zap the zones, that I can just
flip on
my cron job again and poof (just as quickly) we are back in
business.
Right. My point was that we'd have lost a week's worth of
nightlies, so if
there are problems with the latest one, we can't tell people to
pick up one
from a few days ago. But maybe we don't care enough about that to
worry
about it.
--
Martin Cooper
I'm half way there. The 1.2 branch build is complete, and now being
built and uploaded from the zone to minotar (the normal nightly
spot)
using my account. It is still not automated (crontab), but it's
there. And let me just say, that machine simply screems! I can do a
full release of the 1.2 branch in about 35 seconds (not counting
download-dependencies). It was at about 3 or 4 minutes on my
linux box.
For HEAD, this means getting the maven build streamlined, which I've
already done some work on, but things could be even faster. I'll
keep plugging away, but be aware that someone is bound to notice the
missing nightlies for 1.3.x.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 21, 2005, at 1:40 PM, Martin Cooper wrote:
On 9/20/05, James Mitchell [EMAIL PROTECTED] wrote:
I have finally gotten around to finishing the setup of my
account on
our zone (http://www.apache.org/dev/solaris-zones.html) and
thanks to
Martin and Google, I'm now able to fully build the nightly (by
hand)
of the entire Struts project.
Woohoo! :-)
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up'
portion of
the script. This basically caused Maven do say oh cool, nothings
changed, let's not build any artifacts, and the rest of the shell
script just happily uploads the same jars from the last build.
This
explains the mismatch in date/name of some of the nightly
artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/)http://
struts.zones.apache.org/~jmitchell/nightly/)
http://
struts.zones.apache.org/~jmitchell/nightly/)http://
struts.zones.apache.org/~jmitchell/nightly/)
.
I also updated the
readme on the regular nightly download page to point to this
interim
spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right
Re: Nightly builds
I should also mention that I had a few issues to deal with which
required manual intervention (outside of Maven config)
Problem 1
-
BUILD FAILED
...something about Provider
org.apache.xalan.processor.TransformerFactoryImpl not found
Since I'm building with jdk1.5, I kept getting this error during the
current/tiles build. The error is not very intuitive, but if you
google it, you'll find...
http://mail-archives.apache.org/mod_mbox/incubator-jackrabbit-dev/
200502.mbox/[EMAIL PROTECTED]
...which says...
Place xalan.jar in $MAVEN_HOME/lib/endorsed ...
...which fixes the error.
Problem 2
-
...
...
BUILD FAILED
File.. /home/jmitchell/svn/struts/build/maven.xml
Element... maven:reactor
Line.. 61
Column 32
Java heap space
Total time: 10 minutes 11 seconds
Finished at: Wed Sep 21 01:57:43 GMT+00:00 2005
Seems even the zone couldn't handle such a large build.
Solution:
Before rerunning 'maven nightly', I do this...
$export MAVEN_OPTS=-Xmx1024m
(of course, it may not need that much, but whatever the standard
max is, wasn't enough)
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 21, 2005, at 12:10 AM, James Mitchell wrote:
I have finally gotten around to finishing the setup of my account
on our zone (http://www.apache.org/dev/solaris-zones.html) and
thanks to Martin and Google, I'm now able to fully build the
nightly (by hand) of the entire Struts project.
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up' portion
of the script. This basically caused Maven do say oh cool,
nothings changed, let's not build any artifacts, and the rest of
the shell script just happily uploads the same jars from the last
build. This explains the mismatch in date/name of some of the
nightly artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/). I also updated the
readme on the regular nightly download page to point to this
interim spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are configured
to pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to Where will the nightlies live?.
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org
b) build via a generic account and scp via a valid account
(committer account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
Somewhat related - Craig, if you are interested, I'd be happy to
help you move your nightly Ant builds to the new zone.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
-
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: Nightly builds
On 9/20/05, James Mitchell [EMAIL PROTECTED] wrote:
I have finally gotten around to finishing the setup of my account on
our zone (http://www.apache.org/dev/solaris-zones.html) and thanks to
Martin and Google, I'm now able to fully build the nightly (by hand)
of the entire Struts project.
Woohoo! :-)
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up' portion of
the script. This basically caused Maven do say oh cool, nothings
changed, let's not build any artifacts, and the rest of the shell
script just happily uploads the same jars from the last build. This
explains the mismatch in date/name of some of the nightly artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/)http://struts.zones.apache.org/~jmitchell/nightly/).
I also updated the
readme on the regular nightly download page to point to this interim
spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are configured to
pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to Where will the nightlies live?.
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org http://cvs.apache.org
b) build via a generic account and scp via a valid account (committer
account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
As Craig mentioned, the zones are, in theory, still subject to disappearing
in a puff of bits, so I'd prefer to see the nightlies pushed to minotaur so
that they're still around if that does ever happen. I think we should have a
'build' account on the zone that does the actual building; I don't have any
good ideas on the key to use to push them over when they're done.
That said, with Justin and Leo both stepping back from infra@, and several
others being, uh, less prominent than they used to be, it's not clear that
much of anything is going to happen on the zones machine in the near future
that would disrupt us.
If we do distribute from the zone itself, it would be nice to have a URL
more like:
http://struts.zones.apache.org/builds/nightly
rather than actually exposing an account name in the URL. ;-)
--
Martin Cooper
Somewhat related - Craig, if you are interested, I'd be happy to help
you move your nightly Ant builds to the new zone.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Nightly builds
My goal is to have the sources for both 1.2.7 branch and HEAD in such
a way that if Infra decides to zap the zones, that I can just flip on
my cron job again and poof (just as quickly) we are back in business.
I'm half way there. The 1.2 branch build is complete, and now being
built and uploaded from the zone to minotar (the normal nightly spot)
using my account. It is still not automated (crontab), but it's
there. And let me just say, that machine simply screems! I can do a
full release of the 1.2 branch in about 35 seconds (not counting
download-dependencies). It was at about 3 or 4 minutes on my linux box.
For HEAD, this means getting the maven build streamlined, which I've
already done some work on, but things could be even faster. I'll
keep plugging away, but be aware that someone is bound to notice the
missing nightlies for 1.3.x.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 21, 2005, at 1:40 PM, Martin Cooper wrote:
On 9/20/05, James Mitchell [EMAIL PROTECTED] wrote:
I have finally gotten around to finishing the setup of my account on
our zone (http://www.apache.org/dev/solaris-zones.html) and thanks to
Martin and Google, I'm now able to fully build the nightly (by hand)
of the entire Struts project.
Woohoo! :-)
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up' portion of
the script. This basically caused Maven do say oh cool, nothings
changed, let's not build any artifacts, and the rest of the shell
script just happily uploads the same jars from the last build. This
explains the mismatch in date/name of some of the nightly artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/)http://
struts.zones.apache.org/~jmitchell/nightly/).
I also updated the
readme on the regular nightly download page to point to this interim
spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are configured to
pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to Where will the nightlies live?.
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org http://cvs.apache.org
b) build via a generic account and scp via a valid account (committer
account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
As Craig mentioned, the zones are, in theory, still subject to
disappearing
in a puff of bits, so I'd prefer to see the nightlies pushed to
minotaur so
that they're still around if that does ever happen. I think we
should have a
'build' account on the zone that does the actual building; I don't
have any
good ideas on the key to use to push them over when they're done.
That said, with Justin and Leo both stepping back from infra@, and
several
others being, uh, less prominent than they used to be, it's not
clear that
much of anything is going to happen on the zones machine in the
near future
that would disrupt us.
If we do distribute from the zone itself, it would be nice to have
a URL
more like:
http://struts.zones.apache.org/builds/nightly
rather than actually exposing an account name in the URL. ;-)
--
Martin Cooper
Somewhat related - Craig, if you are interested, I'd be happy to help
you move your nightly Ant builds to the new zone.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
-
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: Nightly builds
On 9/21/05, James Mitchell [EMAIL PROTECTED] wrote:
My goal is to have the sources for both 1.2.7 branch and HEAD in such
a way that if Infra decides to zap the zones, that I can just flip on
my cron job again and poof (just as quickly) we are back in business.
Right. My point was that we'd have lost a week's worth of nightlies, so if
there are problems with the latest one, we can't tell people to pick up one
from a few days ago. But maybe we don't care enough about that to worry
about it.
--
Martin Cooper
I'm half way there. The 1.2 branch build is complete, and now being
built and uploaded from the zone to minotar (the normal nightly spot)
using my account. It is still not automated (crontab), but it's
there. And let me just say, that machine simply screems! I can do a
full release of the 1.2 branch in about 35 seconds (not counting
download-dependencies). It was at about 3 or 4 minutes on my linux box.
For HEAD, this means getting the maven build streamlined, which I've
already done some work on, but things could be even faster. I'll
keep plugging away, but be aware that someone is bound to notice the
missing nightlies for 1.3.x.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 21, 2005, at 1:40 PM, Martin Cooper wrote:
On 9/20/05, James Mitchell [EMAIL PROTECTED] wrote:
I have finally gotten around to finishing the setup of my account on
our zone (http://www.apache.org/dev/solaris-zones.html) and thanks to
Martin and Google, I'm now able to fully build the nightly (by hand)
of the entire Struts project.
Woohoo! :-)
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up' portion of
the script. This basically caused Maven do say oh cool, nothings
changed, let's not build any artifacts, and the rest of the shell
script just happily uploads the same jars from the last build. This
explains the mismatch in date/name of some of the nightly artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/)http://struts.zones.apache.org/~jmitchell/nightly/)
http://
struts.zones.apache.org/~jmitchell/nightly/)http://struts.zones.apache.org/~jmitchell/nightly/)
.
I also updated the
readme on the regular nightly download page to point to this interim
spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are configured to
pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to Where will the nightlies live?.
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org http://cvs.apache.org http://cvs.apache.org
b) build via a generic account and scp via a valid account (committer
account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
As Craig mentioned, the zones are, in theory, still subject to
disappearing
in a puff of bits, so I'd prefer to see the nightlies pushed to
minotaur so
that they're still around if that does ever happen. I think we
should have a
'build' account on the zone that does the actual building; I don't
have any
good ideas on the key to use to push them over when they're done.
That said, with Justin and Leo both stepping back from infra@, and
several
others being, uh, less prominent than they used to be, it's not
clear that
much of anything is going to happen on the zones machine in the
near future
that would disrupt us.
If we do distribute from the zone itself, it would be nice to have
a URL
more like:
http://struts.zones.apache.org/builds/nightly
rather than actually exposing an account name in the URL. ;-)
--
Martin Cooper
Somewhat related - Craig, if you are interested, I'd be happy to help
you move your nightly Ant builds to the new zone.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
-
To unsubscribe, e-mail
Nightly builds
I have finally gotten around to finishing the setup of my account on
our zone (http://www.apache.org/dev/solaris-zones.html) and thanks to
Martin and Google, I'm now able to fully build the nightly (by hand)
of the entire Struts project.
For those who haven't been watching, the nightly builds that were
happening on my machine began failing during the 'svn up' portion of
the script. This basically caused Maven do say oh cool, nothings
changed, let's not build any artifacts, and the rest of the shell
script just happily uploads the same jars from the last build. This
explains the mismatch in date/name of some of the nightly artifacts.
So, where are we?
Currently, the latest build (nightly) is available here (http://
struts.zones.apache.org/~jmitchell/nightly/). I also updated the
readme on the regular nightly download page to point to this interim
spot. This is a manual process right now.
Where do we want to be?
Typically, nightlies are hosted from /www/cvs.apache.org/build/
{project}.
Right now, both Craig and my own personal machines are configured to
pull from cvs/svn, run the build, and upload something to that
location. This can only happen as a cron job if we copy the
appropriate ssh keys to the target server (no login prompted).
The question really comes down to Where will the nightlies live?.
If we want to use some generic account on the zone to build the
nightly, the script would need to either:
a) use someone's account (mine?) to build/scp the nightlies over to
cvs.apache.org
b) build via a generic account and scp via a valid account (committer
account on the zone)
Although, we can actually avoid all of this by just hosting the
nightlies from the zone. The url might look like this:
http://struts.zones.apache.org/~nightly/
Somewhat related - Craig, if you are interested, I'd be happy to help
you move your nightly Ant builds to the new zone.
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
