; 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
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
++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
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
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
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
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
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
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
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
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
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.
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
:[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
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
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
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
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
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
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
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
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
22 matches
Mail list logo
