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]
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]
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]
