...adding to my previous comment about the old way of building with Ant.
Building Struts via the Ant build script has always been an issue with
respect to dependencies. Before Mavenization, every single person who
wanted to build Struts from source had to:
a) download all the dependencies by hand
b) configure your own local copy of build.properties to point to the right
JARs
...we do this so that Struts could use the required dependent libraries
without having to resort to the time-proven _bad practice_ of keeping JARs
in the repository.
I had a couple of issues with our particular Ant build setup because I had
several other projects that conflicted with the way we were naming the keys
that pointed to some of the JARs.
One of the major benefits of using Maven is that all of this confusion is
completely removed. However, there is an intermediate step. You can
configure an Ant build script to download dependent JARs the same way Maven
does without requiring Maven.
A few months ago, it became apparent that there was interest in maintaining
nightlies for the "STRUTS_1_2_BRANCH", so I modified the build.xml file to
be able download the dependencies as part of the build.
See this page for details:
https://svn.apache.org/repos/asf/struts/core/tags/STRUTS_1_2_7/build.xml
...scroll down to the "download-dependencies" target.
With that new target, I have been producing 1.2.x nightlies for several
months now.
https://svn.apache.org/repos/asf/struts/core/branches/STRUTS_1_2_BRANCH/.
(* see note below)
* As part of preparing this email, I noticed the distribution dirs (src,
bin, lib) were empty due to a version change to the build.xml. When the
version was changed from 1.2.7-dev, to 1.2.7 a few weeks back, that broke
the nightly build. I just fixed my local shell script and reran the nightly
for 1.2.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]
----- Original Message -----
From: "James Mitchell" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[email protected]>
Cc: "Struts Developers List" <[email protected]>
Sent: Monday, May 30, 2005 9:46 PM
Subject: Re: Struts-1.2.7
That would be a mistake on our part. Probably due to the (old) way we
used to build Struts.
At this point it may be safe to assume that the release notes/wiki will be
changed to match the distribution. But that has yet to be discussed.
I'd like to add a few more comments about this, but I'll do it over on the
Struts Developers List.
Thanks for pointing this out.
--
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]
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, May 30, 2005 10:47 AM
Subject: Struts-1.2.7
Hi,
I'm upgrading my project to the latest version of struts 1.2.7.
In the Wiki under the Dependency section
(http://wiki.apache.org/struts/StrutsRelease127) it mentions that the
Common BeanUtils version 1.7.0 is required.
When I look at the Manifest.mf file found in the struts-1.2.7\lib
directory this is what I get.
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: 1.4.1_01-b01 (Sun Microsystems Inc.)
Extension-Name: org.apache.commons.beanutils
Specification-Title: Jakarta Commons Beanutils
Specification-Vendor: Apache Software Foundation
Specification-Version: 1.6
Implementation-Title: org.apache.commons.beanutils
Implementation-Vendor: Apache Software Foundation
Implementation-Version: 1.6
I have also noted a discrepency between the manifest for antlr.jar and
the
Wiki.
Am I missing something here or is there just a typo in the Wiki?
- Glenn
---------------------------------------------------------------------
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]
