You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Martin Cooper <ma...@apache.org> on 2004/02/27 06:47:40 UTC
[ANNOUNCE] Struts 1.2.0 Test Build available
The Struts 1.2.0 Test Build is now available here:
http://www.apache.org/~martinc/struts/v1.2.0/
This is the first Struts build being made available following the same
test-and-release process that has been used successfully by the Tomcat
team for some time. It is *not* an official Apache release.
Once feedback has been collected on the stability and general quality of
this build, a determination will be made as to whether it should be
promoted to Alpha status.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: Struts Change Tracking (Re: [ANNOUNCE] Struts 1.2.0 Test Build available)
Posted by Ted Husted <hu...@apache.org>.
Right now, I'm using the Maven changelog as a cut-and-paste guide to the release notes. I think the change plugin could be a replacement for this, especially if we start release more than one product, each of which could have their own change file. (struts-core, struts-opt-taglibs, struts-opt-el, struts-opt-apps, and so forth.)
I do agree that that we need to summarize the changelog to turn data into information, and the changes plugin might be a help with that.
Though, since part of that is "categorizing" the changes, I think we need to divy up the distribution before changing what we now do for release note changes.
Personally, I'd like to prioritize moving the build over to Maven, and dividing the distribution into multiple artifacts with their own release cycles, so that we start taking advantage of features like this.
-Ted.
On Fri, 27 Feb 2004 08:10:53 -0600, Joe Germuska wrote:
> At 9:05 AM +0100 2/27/04, nicolas De Loof wrote:
>> Can you please post a "what's new" about this release to help me
>> make my boss agree to use Struts 1.2.0 for new projects ?
>>
>
> Are committers familiar with the Maven changes.xml file/plugin? If
> it exists, it can be used to generate something that looks like
> this:
>
> http://maven.apache.org/changes-report.html
>
>
> Even though Maven isn't our primary build mechanism, using
> changes.xml might be a good way to track what we're doing. I hope
> I'm not embarassing myself, but there isn't any basic change log
> already is there? If so, I sure haven't been tracking it.
>
> I guess putting every single commit into the changes.xml file isn't
> appropriate, or the thing would get huge. Also, Maven can generate
> a separate report for that (http://maven.apache.org/changelog-
> report.html)
>
> Since changes.xml is structured, we could probably come up with a
> transform to use it in the current Ant-built documentation until we
> are using Maven, and if nothing else, it provides a single place to
> log things.>
> Of course, if people don't think it's worth the energy, I'd rather
> leave it out than have it there but inaccurate.
>
> Joe
>
>
> PS an example of the XML syntax is here:
> http://maven.apache.org/reference/plugins/changes/ It's about as
> much doc as I've ever seen for it.
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Struts Change Tracking (Re: [ANNOUNCE] Struts 1.2.0 Test Build
available)
Posted by Joe Germuska <Jo...@Germuska.com>.
At 9:05 AM +0100 2/27/04, nicolas De Loof wrote:
>Can you please post a "what's new" about this release to help me
>make my boss agree to use Struts 1.2.0 for new projects ?
Are committers familiar with the Maven changes.xml file/plugin? If
it exists, it can be used to generate something that looks like this:
http://maven.apache.org/changes-report.html
Even though Maven isn't our primary build mechanism, using
changes.xml might be a good way to track what we're doing. I hope
I'm not embarassing myself, but there isn't any basic change log
already is there? If so, I sure haven't been tracking it.
I guess putting every single commit into the changes.xml file isn't
appropriate, or the thing would get huge. Also, Maven can generate a
separate report for that
(http://maven.apache.org/changelog-report.html)
Since changes.xml is structured, we could probably come up with a
transform to use it in the current Ant-built documentation until we
are using Maven, and if nothing else, it provides a single place to
log things.
Of course, if people don't think it's worth the energy, I'd rather
leave it out than have it there but inaccurate.
Joe
PS an example of the XML syntax is here:
http://maven.apache.org/reference/plugins/changes/ It's about as
much doc as I've ever seen for it.
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Choosing 1.2.0 (Re: [ANNOUNCE] Struts 1.2.0 Test Build available)
Posted by Joe Germuska <Jo...@Germuska.com>.
At 9:05 AM +0100 2/27/04, nicolas De Loof wrote:
>Can you please post a "what's new" about this release to help me
>make my boss agree to use Struts 1.2.0 for new projects ?
Oh yes, this also reminds me: I think we need to be on guard for a
lot of questions like this. Martin described the release correctly
on struts-user, but many people will be thinking "new struts release,
gotta have it..."
Particularly with the 1.2.0 tree, people need to be conscious that
many deprecated methods and classes were removed, so transitioning to
1.2 from 1.1 may not be a simple drop-in. Also, as Martin noted,
using the Tomcat-style release cycle, the mere existence of a
numbered release of Struts does not necessarily mean the a release
that your boss would be happy with (depending on your boss, of
course).
I've been using Struts nightlies for a while, and I'm confident in
their general stability and reliability -- but that's not sufficient
for everyone.
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by nicolas De Loof <ni...@cgey.com>.
Oops, sory.
I have troubles building the doc using "maven site", so I didn't see
this note. Thanks.
Nico.
Indrajit Raychaudhuri a écrit :
>Download and see the Release Notes :)
>
>----- Original Message -----
>From: "nicolas De Loof" <ni...@cgey.com>
>To: "Struts Developers List" <st...@jakarta.apache.org>
>Sent: Friday, 27 February, 2004 13:35
>Subject: Re: [ANNOUNCE] Struts 1.2.0 Test Build available
>
>
>
>
>>Can you please post a "what's new" about this release to help me make my
>>boss agree to use Struts 1.2.0 for new projects ?
>>
>>Nico.
>>
>>Martin Cooper a écrit :
>>
>>
>>
>>>The Struts 1.2.0 Test Build is now available here:
>>>
>>>http://www.apache.org/~martinc/struts/v1.2.0/
>>>
>>>This is the first Struts build being made available following the same
>>>test-and-release process that has been used successfully by the Tomcat
>>>team for some time. It is *not* an official Apache release.
>>>
>>>Once feedback has been collected on the stability and general quality of
>>>this build, a determination will be made as to whether it should be
>>>promoted to Alpha status.
>>>
>>>--
>>>Martin Cooper
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>>
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Indrajit Raychaudhuri <ir...@indrajit.com>.
Download and see the Release Notes :)
----- Original Message -----
From: "nicolas De Loof" <ni...@cgey.com>
To: "Struts Developers List" <st...@jakarta.apache.org>
Sent: Friday, 27 February, 2004 13:35
Subject: Re: [ANNOUNCE] Struts 1.2.0 Test Build available
> Can you please post a "what's new" about this release to help me make my
> boss agree to use Struts 1.2.0 for new projects ?
>
> Nico.
>
> Martin Cooper a écrit :
>
> >The Struts 1.2.0 Test Build is now available here:
> >
> >http://www.apache.org/~martinc/struts/v1.2.0/
> >
> >This is the first Struts build being made available following the same
> >test-and-release process that has been used successfully by the Tomcat
> >team for some time. It is *not* an official Apache release.
> >
> >Once feedback has been collected on the stability and general quality of
> >this build, a determination will be made as to whether it should be
> >promoted to Alpha status.
> >
> >--
> >Martin Cooper
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by nicolas De Loof <ni...@cgey.com>.
Can you please post a "what's new" about this release to help me make my
boss agree to use Struts 1.2.0 for new projects ?
Nico.
Martin Cooper a écrit :
>The Struts 1.2.0 Test Build is now available here:
>
>http://www.apache.org/~martinc/struts/v1.2.0/
>
>This is the first Struts build being made available following the same
>test-and-release process that has been used successfully by the Tomcat
>team for some time. It is *not* an official Apache release.
>
>Once feedback has been collected on the stability and general quality of
>this build, a determination will be made as to whether it should be
>promoted to Alpha status.
>
>--
>Martin Cooper
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Joe Germuska <Jo...@Germuska.com>.
At 9:34 AM +0100 2/27/04, nicolas De Loof wrote:
>I've built Struts 1.2.0 from the sources package uising maven 1.0RC1
>without trouble.
>
>When I run "maven site", the generated m-target/docs has no
>"index.html" and "faqs", "proposals", "tiles" and "userGuide" are
>empty directory. Is this a known build problem (waiting for update
>for an *official* release) ?
The energy for applying Maven to Struts has been focused on the
build. I think a few people have looked at making it build the docs,
but no one has really focused on it. I've also been pleased to be
able to extend the main project.xml for struts-chain and struts-el to
quickly bring Maven support to those.
Maven is not the official build mechanism for Struts, and there's no
guarantee that it will become such in the 1.x line. On the other
hand, if folks make Maven do everything the current Ant build does,
it might. Of course, the fact that Maven still hasn't seen a full
1.0 release does lend some support with keeping Ant the official way.
For the docs, the main thing would be to eliminate any need to
maintain dual documentation while the Ant build is still the official
build. I think all current efforts have cloned the docs dir, and
I've never tried to get maven:site to work against anything but the
xdocs directory. If anyone knows the trick, patches are always
happily accepted!
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build available)
Posted by Tim Chen <tc...@tampabay.rr.com>.
There's another way to handle these as well.
Following the properties processing rule that Joe had quoted. You will
notice that everything goes through you build.properties
So if you define a version in your build.properties you can access it in
your dependencies.
For example:
//build.properties
java.style.version=2.9.9
// for each project that you use jrefactory/javastyle in simply define
the dependency as:
<!-- pretty task -->
<dependency>
<groupId>jrefactory</groupId>
<artifactId>JavaStyle</artifactId>
<version>${java.style.version}</version>
</dependency>
You can also define an xml file with your dependencies section and
include that with each project using standard xml inclusion.
This is much less typing and very similar to how all your ant files have
that line.. well now all your project.properties file with have a xml
include line.
You can also create a base project.xml with all your dependencies and
their correct versions and use <extend> from your subproject's in order
to bring those dependencies in.
There are more options (including the @FOO_VERSION@ syntax that alot of
people seem to like to use) but I've only used the ones above.
A cool feature being worked on by the maven group is the inclusion of
dependencies from a POM (your project.xml is basically a POM.. when you
upload your artifact to a repository it will create a poms folder with
your project.xml renamed to project.pom). This will allow people to get
all the dependencies of a particular project directly into their project.
Hope that helps,
-Tim :)
Joe Germuska wrote:
>> that lets me define the individual versions of *all* dependencies for
>> *all*
>> projects so that I can say, for example, use *this* version of
>> commons-beanutils and *that* version of commons-digester to build
>> ***all*** of
>> the components that are going in to my overall exectable. I am *so* not
>> interested in dealing with runtime exceptions because different
>> dependent
>> packages were compiled against different versions of the dependent
>> libraries.
>>
>> Can someone please help me understand how to do this with Maven?
>> Without it,
>> I'm not planning to switch any of my personal or internal-to-Sun
>> projects (even
>> if the Struts committers decide to switch Struts development itself).
>
>
> This is actually pretty easy, if I understand you correctly. If you
> define the Maven property "maven.jar.override" to the value "on", then
> when resolving dependencies, Maven will check each against a possibly
> defined override.
>
> For example, the version of Cactus that everyone else in Struts uses
> doesn't work on Mac OS X. The Cactus CVS head has the patch that
> works, so in my Struts/maven environment, I have this defined:
>
> maven.jar.override=on
> # patched version of cactus related to Mac OS X:
> # http://issues.apache.org/bugzilla/show_bug.cgi?id=25266i
> maven.jar.cactus-ant=1.6dev-2003-12-07
> maven.jar.jakarta-cactus-framework=13-1.6dev
>
> You can use full paths to JARs as well as version numbers. This is
> detailed here:
> http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies
>
>
> Properties are defined like so:
> (http://maven.apache.org/reference/user-guide.html#Properties_Processing):
>
>
>> The properties files in Maven are processed in the following order:
>>
>> * ${project.home}/project.properties
>> * ${project.home}/build.properties
>> * ${user.home}/build.properties
>>
>> Where the last definition wins. So, Maven moves through this
>> sequence of properties files overridding any previously defined
>> properties with newer definitions. In this sequence your
>> ${user.home}/build.properties has the final say in the list of
>> properties files processed. We will call the list of properties
>> files that Maven processes the standard properties file set.
>>
>> In addition, System properties are processed after the above chain
>> of properties files are processed. So, a property specified on the
>> CLI using the -Dproperty=value convention will override any previous
>> definition of that property.
>
>
> So if you wanted to have it universally, you'd define this in
> "${user.home}/build.properties" but if it were just for a specific
> project, you'd define it in ${project.home}/build.properties
>
> Did I answer the right question?
>
> Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: [OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build
available)
Posted by Joe Germuska <Jo...@Germuska.com>.
>that lets me define the individual versions of *all* dependencies for *all*
>projects so that I can say, for example, use *this* version of
>commons-beanutils and *that* version of commons-digester to build ***all*** of
>the components that are going in to my overall exectable. I am *so* not
>interested in dealing with runtime exceptions because different dependent
>packages were compiled against different versions of the dependent libraries.
>
>Can someone please help me understand how to do this with Maven? Without it,
>I'm not planning to switch any of my personal or internal-to-Sun
>projects (even
>if the Struts committers decide to switch Struts development itself).
This is actually pretty easy, if I understand you correctly. If you
define the Maven property "maven.jar.override" to the value "on",
then when resolving dependencies, Maven will check each against a
possibly defined override.
For example, the version of Cactus that everyone else in Struts uses
doesn't work on Mac OS X. The Cactus CVS head has the patch that
works, so in my Struts/maven environment, I have this defined:
maven.jar.override=on
# patched version of cactus related to Mac OS X:
# http://issues.apache.org/bugzilla/show_bug.cgi?id=25266i
maven.jar.cactus-ant=1.6dev-2003-12-07
maven.jar.jakarta-cactus-framework=13-1.6dev
You can use full paths to JARs as well as version numbers. This is
detailed here:
http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies
Properties are defined like so:
(http://maven.apache.org/reference/user-guide.html#Properties_Processing):
> The properties files in Maven are processed in the following order:
>
> * ${project.home}/project.properties
> * ${project.home}/build.properties
> * ${user.home}/build.properties
>
> Where the last definition wins. So, Maven moves through this
>sequence of properties files overridding any previously defined
>properties with newer definitions. In this sequence your
>${user.home}/build.properties has the final say in the list of
>properties files processed. We will call the list of properties
>files that Maven processes the standard properties file set.
>
> In addition, System properties are processed after the above chain
>of properties files are processed. So, a property specified on the
>CLI using the -Dproperty=value convention will override any
>previous definition of that property.
So if you wanted to have it universally, you'd define this in
"${user.home}/build.properties" but if it were just for a specific
project, you'd define it in ${project.home}/build.properties
Did I answer the right question?
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
Re: [OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build
available)
Posted by Joe Germuska <Jo...@Germuska.com>.
>that lets me define the individual versions of *all* dependencies for *all*
>projects so that I can say, for example, use *this* version of
>commons-beanutils and *that* version of commons-digester to build ***all*** of
>the components that are going in to my overall exectable. I am *so* not
>interested in dealing with runtime exceptions because different dependent
>packages were compiled against different versions of the dependent libraries.
>
>Can someone please help me understand how to do this with Maven? Without it,
>I'm not planning to switch any of my personal or internal-to-Sun
>projects (even
>if the Struts committers decide to switch Struts development itself).
This is actually pretty easy, if I understand you correctly. If you
define the Maven property "maven.jar.override" to the value "on",
then when resolving dependencies, Maven will check each against a
possibly defined override.
For example, the version of Cactus that everyone else in Struts uses
doesn't work on Mac OS X. The Cactus CVS head has the patch that
works, so in my Struts/maven environment, I have this defined:
maven.jar.override=on
# patched version of cactus related to Mac OS X:
# http://issues.apache.org/bugzilla/show_bug.cgi?id=25266i
maven.jar.cactus-ant=1.6dev-2003-12-07
maven.jar.jakarta-cactus-framework=13-1.6dev
You can use full paths to JARs as well as version numbers. This is
detailed here:
http://maven.apache.org/reference/user-guide.html#Overriding_Stated_Dependencies
Properties are defined like so:
(http://maven.apache.org/reference/user-guide.html#Properties_Processing):
> The properties files in Maven are processed in the following order:
>
> * ${project.home}/project.properties
> * ${project.home}/build.properties
> * ${user.home}/build.properties
>
> Where the last definition wins. So, Maven moves through this
>sequence of properties files overridding any previously defined
>properties with newer definitions. In this sequence your
>${user.home}/build.properties has the final say in the list of
>properties files processed. We will call the list of properties
>files that Maven processes the standard properties file set.
>
> In addition, System properties are processed after the above chain
>of properties files are processed. So, a property specified on the
>CLI using the -Dproperty=value convention will override any
>previous definition of that property.
So if you wanted to have it universally, you'd define this in
"${user.home}/build.properties" but if it were just for a specific
project, you'd define it in ${project.home}/build.properties
Did I answer the right question?
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
Re: [OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build available)
Posted by "Craig R. McClanahan" <cr...@apache.org>.
Quoting Joe Germuska <Jo...@Germuska.com>:
> Oh yeah, also I can't go back from having versioned JAR in my lib
> directories. I suspect that's a matter of taste too, but I'll take
> the overhead of pruning old JARs when new versions are deployed over
> the mystery of knowing which versions your apps depend on any day...
>
Interestingly, this touches on my single biggest frustration with Maven.
Professionally, I live in a world where there are some fairly large projects,
which integrate *lots* of open source projects (a very large number of
jakarta.apache.org and xml.apache.org subprojects are included). Many of these
open source projects have overlapping dependencies on several Jakarta Commons
packages -- not a surprise, those packages were *designed* for reuse. But
Maven (like many other build environments) encourages you to define the
specific version dependencies for each package you build independently. That's
not good enough for enterprise development.
All of the Ant build.xml files I care about include a line like this:
<property file="${user.home}/build.properties"/>
that lets me define the individual versions of *all* dependencies for *all*
projects so that I can say, for example, use *this* version of
commons-beanutils and *that* version of commons-digester to build ***all*** of
the components that are going in to my overall exectable. I am *so* not
interested in dealing with runtime exceptions because different dependent
packages were compiled against different versions of the dependent libraries.
Can someone please help me understand how to do this with Maven? Without it,
I'm not planning to switch any of my personal or internal-to-Sun projects (even
if the Struts committers decide to switch Struts development itself).
> Joe
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build available)
Posted by "Craig R. McClanahan" <cr...@apache.org>.
Quoting Joe Germuska <Jo...@Germuska.com>:
> Oh yeah, also I can't go back from having versioned JAR in my lib
> directories. I suspect that's a matter of taste too, but I'll take
> the overhead of pruning old JARs when new versions are deployed over
> the mystery of knowing which versions your apps depend on any day...
>
Interestingly, this touches on my single biggest frustration with Maven.
Professionally, I live in a world where there are some fairly large projects,
which integrate *lots* of open source projects (a very large number of
jakarta.apache.org and xml.apache.org subprojects are included). Many of these
open source projects have overlapping dependencies on several Jakarta Commons
packages -- not a surprise, those packages were *designed* for reuse. But
Maven (like many other build environments) encourages you to define the
specific version dependencies for each package you build independently. That's
not good enough for enterprise development.
All of the Ant build.xml files I care about include a line like this:
<property file="${user.home}/build.properties"/>
that lets me define the individual versions of *all* dependencies for *all*
projects so that I can say, for example, use *this* version of
commons-beanutils and *that* version of commons-digester to build ***all*** of
the components that are going in to my overall exectable. I am *so* not
interested in dealing with runtime exceptions because different dependent
packages were compiled against different versions of the dependent libraries.
Can someone please help me understand how to do this with Maven? Without it,
I'm not planning to switch any of my personal or internal-to-Sun projects (even
if the Struts committers decide to switch Struts development itself).
> Joe
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org
Re: [OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build
available)
Posted by Joe Germuska <Jo...@Germuska.com>.
At 11:19 AM -0800 2/27/04, Martin Cooper wrote:
>(When it comes to IDEs, though, most of them know about Ant, but don't yet
>know about Maven at all, so there's not so much of a case for Maven there,
>IMHO.)
Since you added the OT to the subject line, I feel ok about dragging
this on... the beauty of Maven and IDEs is that Maven generates the
project for you, for JBuilder, Eclipse, or IDEA. Let's see your Ant
do that! :-)
Just kidding. Ant is great, and actually, I think the fact that
extending Maven is basically like writing Ant is a feature, not a bug.
Oh yeah, also I can't go back from having versioned JAR in my lib
directories. I suspect that's a matter of taste too, but I'll take
the overhead of pruning old JARs when new versions are deployed over
the mystery of knowing which versions your apps depend on any day...
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
[OT] Maven (was Re: [ANNOUNCE] Struts 1.2.0 Test Build available)
Posted by Martin Cooper <ma...@apache.org>.
"Joe Germuska" <Jo...@Germuska.com> wrote in message
news:a06020409bc653226ae85@[192.168.2.81]...
> >Given that Maven still hasn't reached an official 1.0 release in almost 3
> >years of development.....
>
> hey, now... Struts 1.1 took a darn long time! I bet they're in the
> same boat. Plenty of people who don't really track version numbers
> are using it happily, so the urge to actually cut a release is not
> too strong.
I'm not claiming we're angels, but we're doing a lot better than Maven is.
;-) From Struts 1.0.2 Final to Struts 1.1 Final took 1 year, 4 months.
During that time, people still had a Final release to work with. Maven has
been in development for almost *3* years, with *no* Final release to work
with...
>
> >That said, there are some intrepid Maven fans who are working on getting
the
> >Maven build for Struts to the same point as the Ant build system
>
> My enthusiasm for Maven is all about lowering the barrier to entry.
I used to share that enthusiasm. It has faded over time, however, as it
became apparent to me that, once you get past the easy part, writing preGoal
and postGoal scripts isn't much different from writing Ant scripts. Oh, and
Maven changing the way it does things didn't help either. ;-)
> I think long-time Ant/Struts builders forget how tedious it is to set
> up the build.properties file. And that's just to compile; if you use
> an IDE you have another headache getting a Struts project set up.
That is certainly true. One of the things Maven does for you, to ease the
build process, is decide where the dependencies are going to come from. If
we did that in the Ant build files, it would make it almost as simple as
Mave, but then, because they're Ant build files, people would complain that
they were not sufficiently flexible. That makes it hard to win. ;-)
(When it comes to IDEs, though, most of them know about Ant, but don't yet
know about Maven at all, so there's not so much of a case for Maven there,
IMHO.)
--
Martin Cooper
>
> Anyway, no need to proselytize...
>
> Joe
> --
> Joe Germuska
> Joe@Germuska.com
> http://blog.germuska.com
> "Imagine if every Thursday your shoes exploded if you tied them
> the usual way. This happens to us all the time with computers, and
> nobody thinks of complaining."
> -- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Joe Germuska <Jo...@Germuska.com>.
>Given that Maven still hasn't reached an official 1.0 release in almost 3
>years of development.....
hey, now... Struts 1.1 took a darn long time! I bet they're in the
same boat. Plenty of people who don't really track version numbers
are using it happily, so the urge to actually cut a release is not
too strong.
>That said, there are some intrepid Maven fans who are working on getting the
>Maven build for Struts to the same point as the Ant build system
My enthusiasm for Maven is all about lowering the barrier to entry.
I think long-time Ant/Struts builders forget how tedious it is to set
up the build.properties file. And that's just to compile; if you use
an IDE you have another headache getting a Struts project set up.
Anyway, no need to proselytize...
Joe
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"Imagine if every Thursday your shoes exploded if you tied them
the usual way. This happens to us all the time with computers, and
nobody thinks of complaining."
-- Jef Raskin
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Martin Cooper <ma...@apache.org>.
"nicolas De Loof" <ni...@cgey.com> wrote in message
news:403F0101.8080209@capgemini.fr...
> I've built Struts 1.2.0 from the sources package uising maven 1.0RC1
> without trouble.
>
> When I run "maven site", the generated m-target/docs has no "index.html"
> and "faqs", "proposals", "tiles" and "userGuide" are empty directory. Is
> this a known build problem (waiting for update for an *official* release)
?
As Joe has already mentioned, the use of Maven to build various parts of
Struts is an ongoing activity. All of the builds you see distributed from
Jakarta (nightly, release, and this test build) are still built using Ant.
Given that Maven still hasn't reached an official 1.0 release in almost 3
years of development, and given how stable and well-developed the Struts Ant
build system is (it's just as capable as Maven of building the entire
release, including docs, by issuing one command to a shell), I'm personally
in no great rush to switch. ;-)
That said, there are some intrepid Maven fans who are working on getting the
Maven build for Struts to the same point as the Ant build system, so don't
be surprised to see the issues you mention taken to heart and addressed
before an official release of Maven!
--
Martin Cooper
>
> Nico.
>
> Martin Cooper a �crit :
>
> >The Struts 1.2.0 Test Build is now available here:
> >
> >http://www.apache.org/~martinc/struts/v1.2.0/
> >
> >This is the first Struts build being made available following the same
> >test-and-release process that has been used successfully by the Tomcat
> >team for some time. It is *not* an official Apache release.
> >
> >Once feedback has been collected on the stability and general quality of
> >this build, a determination will be made as to whether it should be
> >promoted to Alpha status.
> >
> >--
> >Martin Cooper
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: struts-user-help@jakarta.apache.org
> >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Betty Koon <bk...@adobe.com>.
Hi there,
Is there any news on when the offical 1.2.0 struts will be released or has
it reached Alpha yet? Thanks.
-Betty
-----Original Message-----
From: nicolas De Loof [mailto:nicolas.deloof@cgey.com]
Sent: Friday, February 27, 2004 12:34 AM
To: Struts Users Mailing List
Subject: Re: [ANNOUNCE] Struts 1.2.0 Test Build available
I've built Struts 1.2.0 from the sources package uising maven 1.0RC1
without trouble.
When I run "maven site", the generated m-target/docs has no "index.html"
and "faqs", "proposals", "tiles" and "userGuide" are empty directory. Is
this a known build problem (waiting for update for an *official* release) ?
Nico.
Martin Cooper a écrit :
>The Struts 1.2.0 Test Build is now available here:
>
>http://www.apache.org/~martinc/struts/v1.2.0/
>
>This is the first Struts build being made available following the same
>test-and-release process that has been used successfully by the Tomcat
>team for some time. It is *not* an official Apache release.
>
>Once feedback has been collected on the stability and general quality
>of this build, a determination will be made as to whether it should be
>promoted to Alpha status.
>
>--
>Martin Cooper
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by nicolas De Loof <ni...@cgey.com>.
I've built Struts 1.2.0 from the sources package uising maven 1.0RC1
without trouble.
When I run "maven site", the generated m-target/docs has no "index.html"
and "faqs", "proposals", "tiles" and "userGuide" are empty directory. Is
this a known build problem (waiting for update for an *official* release) ?
Nico.
Martin Cooper a écrit :
>The Struts 1.2.0 Test Build is now available here:
>
>http://www.apache.org/~martinc/struts/v1.2.0/
>
>This is the first Struts build being made available following the same
>test-and-release process that has been used successfully by the Tomcat
>team for some time. It is *not* an official Apache release.
>
>Once feedback has been collected on the stability and general quality of
>this build, a determination will be made as to whether it should be
>promoted to Alpha status.
>
>--
>Martin Cooper
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Martin Cooper <ma...@apache.org>.
"Oswald Campesato" <oc...@yahoo.com> wrote in message
news:20040227055619.79815.qmail@web40504.mail.yahoo.com...
>
>
> Martin Cooper <ma...@apache.org> wrote:
> >The Struts 1.2.0 Test Build is now available here:
> Excellent:)
> >http://www.apache.org/~martinc/struts/v1.2.0/
>
> >This is the first Struts build being made available following the same
> >test-and-release process that has been used successfully by the Tomcat
> >team for some time. It is *not* an official Apache release.
>
> >Once feedback has been collected on the stability and general quality of
> >this build, a determination will be made as to whether it should be
> >promoted to Alpha status.
>
>
> Is there a web page that describes the process by which feedback
> is collected?
Just the usual mechanisms:
* Bug reports: http://jakarta.apache.org/struts/using.html#Bugs
* Feedback on the mailing lists.
The former is preferred if you are sure there is a bug; the latter is where
to speculate and ask questions.
--
Martin Cooper
>
> Thanks,
>
> Oswald
>
>
> --
> Martin Cooper
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Get better spam protection with Yahoo! Mail
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Martin Cooper <ma...@apache.org>.
"Andrew Hill" <an...@gridnode.com> wrote in message
news:LIEOJJJDMLMBMLGHDIGBOEBHHAAA.andrew.david.hill@gridnode.com...
> Ah I see.
> Its just the jars, tlds, dtds necessary for a struts app, sans docs.
Yup, that's it exactly. We've actually been releasing a 'lib' version for a
while now, for people who don't want to have to download the entire binary
version, since the latter is getting a bit big. The description of that does
seem to have fallen off the "Acquiring" page in the docs, though. ;-(
Also, it's worth noting that, due to some great work from Ted, the 1.2.0
binary download is about 25% smaller than the 1.1 equivalent, since several
of the sample web apps have been merged into one, thus demonstrating modules
as well.
--
Martin Cooper
>
> -----Original Message-----
> From: Andrew Hill [mailto:andrew.david.hill@gridnode.com]
> Sent: Friday, 27 February 2004 13:52
> To: Struts Users Mailing List
> Subject: RE: [ANNOUNCE] Struts 1.2.0 Test Build available
>
>
> Cool bananas!
>
> Many thanks to the struts team for all the work they have put into this
> build. :-)
>
> Whats the lib archive for?
>
> -----Original Message-----
> From: Martin Cooper [mailto:martinc@apache.org]
> Sent: Friday, 27 February 2004 13:48
> To: struts-dev@jakarta.apache.org; struts-user@jakarta.apache.org
> Subject: [ANNOUNCE] Struts 1.2.0 Test Build available
>
>
> The Struts 1.2.0 Test Build is now available here:
>
> http://www.apache.org/~martinc/struts/v1.2.0/
>
> This is the first Struts build being made available following the same
> test-and-release process that has been used successfully by the Tomcat
> team for some time. It is *not* an official Apache release.
>
> Once feedback has been collected on the stability and general quality of
> this build, a determination will be made as to whether it should be
> promoted to Alpha status.
>
> --
> Martin Cooper
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Andrew Hill <an...@gridnode.com>.
Ah I see.
Its just the jars, tlds, dtds necessary for a struts app, sans docs.
-----Original Message-----
From: Andrew Hill [mailto:andrew.david.hill@gridnode.com]
Sent: Friday, 27 February 2004 13:52
To: Struts Users Mailing List
Subject: RE: [ANNOUNCE] Struts 1.2.0 Test Build available
Cool bananas!
Many thanks to the struts team for all the work they have put into this
build. :-)
Whats the lib archive for?
-----Original Message-----
From: Martin Cooper [mailto:martinc@apache.org]
Sent: Friday, 27 February 2004 13:48
To: struts-dev@jakarta.apache.org; struts-user@jakarta.apache.org
Subject: [ANNOUNCE] Struts 1.2.0 Test Build available
The Struts 1.2.0 Test Build is now available here:
http://www.apache.org/~martinc/struts/v1.2.0/
This is the first Struts build being made available following the same
test-and-release process that has been used successfully by the Tomcat
team for some time. It is *not* an official Apache release.
Once feedback has been collected on the stability and general quality of
this build, a determination will be made as to whether it should be
promoted to Alpha status.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
RE: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Andrew Hill <an...@gridnode.com>.
Cool bananas!
Many thanks to the struts team for all the work they have put into this
build. :-)
Whats the lib archive for?
-----Original Message-----
From: Martin Cooper [mailto:martinc@apache.org]
Sent: Friday, 27 February 2004 13:48
To: struts-dev@jakarta.apache.org; struts-user@jakarta.apache.org
Subject: [ANNOUNCE] Struts 1.2.0 Test Build available
The Struts 1.2.0 Test Build is now available here:
http://www.apache.org/~martinc/struts/v1.2.0/
This is the first Struts build being made available following the same
test-and-release process that has been used successfully by the Tomcat
team for some time. It is *not* an official Apache release.
Once feedback has been collected on the stability and general quality of
this build, a determination will be made as to whether it should be
promoted to Alpha status.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
Re: [ANNOUNCE] Struts 1.2.0 Test Build available
Posted by Oswald Campesato <oc...@yahoo.com>.
Martin Cooper <ma...@apache.org> wrote:
>The Struts 1.2.0 Test Build is now available here:
Excellent:)
>http://www.apache.org/~martinc/struts/v1.2.0/
>This is the first Struts build being made available following the same
>test-and-release process that has been used successfully by the Tomcat
>team for some time. It is *not* an official Apache release.
>Once feedback has been collected on the stability and general quality of
>this build, a determination will be made as to whether it should be
>promoted to Alpha status.
Is there a web page that describes the process by which feedback
is collected?
Thanks,
Oswald
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-user-help@jakarta.apache.org
---------------------------------
Do you Yahoo!?
Get better spam protection with Yahoo! Mail