Yep, "struts-1.2.7.jar" vs "struts-core-1.2.7.jar".
^^^^^
http://www.ibiblio.org/maven/struts/jars/
--
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 13, 2005, at 3:24 PM, James Mitchell wrote:
Then it must be a naming thing......checking....
--
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 13, 2005, at 3:21 PM, Don Brown wrote:
Ideally, sub projects are ones that are independent from the core
in that they have to deal with older version of Struts.
Previously, Struts Flow was set to depend on Struts 1.1 and
apparently things were working fine. Some of the changes Joe made
in 1.2 I want to use, so I switched it to 1.2.7. I certainly
wouldn't exect the build to build 1.2.7 from scratch every time,
but treat Struts as yet another third-party dependency.
FWIW, the Ant build works fine, and even retrieves 1.2.7 remotely :)
Don
James Mitchell wrote:
I just fixed a bug in my nightly script and re-ran it manually...
struts:~/svn/struts/flow jmitchell$ svn up
Fetching external item into 'build'
External at revision 320772.
At revision 320772.
struts:~/svn/struts/flow jmitchell$ maven dist
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download struts-core-1.2.7.jar.
WARNING: Failed to download struts-core-1.2.7.jar.
Attempting to download commons-validator-SNAPSHOT.jar.
The build cannot continue because of the following unsatisfied
dependency:
struts-core-1.2.7.jar (try downloading from http://
struts.apache.org/)
Total time: 7 seconds
Finished at: Thu Oct 13 14:02:30 GMT+00:00 2005
----
It seems that struts-flow depends on struts-core-1.2.7.jar,
which doesn't exist locally (on my boxes) or remotely (our zone
on apache). The nightly for 1.2.x is run with ant, which
creates a 'struts.jar', not 'struts-core-1.2.7.jar', and does
not put it under the local Maven repository anyway, like the
1.3.x nightly Maven build does. Still, running 'maven jar' from
the 1.2.x branch yields struts-1.2.7.jar (perhaps just a typo in
project.xml)
The nightly shell script (as of about 2 hours ago), does a mv
struts - > struts-$TODAY (struts-20051013) and then does a clean
checkout of the entire source from head. I then reran the
nightly script on the nightly box (zone) and while it completed
ok, I see this in the log file...
[from http://svn.apache.org/builds/struts/maven/trunk/nightly/
logs/ nightly-20051013.log]
...
...
+----------------------------------------
| Building nightlies Struts Flow
| Memory: 231M/318M
+----------------------------------------
Attempting to download struts-core-1.2.7.jar.
WARNING: Failed to download struts-core-1.2.7.jar.
...
...
I'm not sure what to say. What's the solution here?
a) build 1.2.7 with Maven, instead of Ant
b) stick a struts-core-1.2.7.jar as a "one time deal" in the
nightly build's .maven/repository
c) stick a struts-core-1.2.7.jar in a temporary repository on
people.apache.org/~mrdon, and reference an additional repo
I don't think any of them are a "safe" long term solution. With
(a), I'm pretty sure the 1.2.x branch is not fully mavenized
(i.e. core, taglib, tiles, sample apps, contrib, etc). For (b),
we would have to update that jar any time something changed in
core. Which brings me to (c), which makes things easier for me,
but still requires someone to keep that jar up to date.
Are we specifying the 1.2.7 dependency because flow is
incompatible with 1.3.x?
With (b), I can't see us running both Ant and Maven on the 1.2.x
branch nightly "just in case" there was a change to 1.2.7 that
flow needed, but I suppose we could do that as an interim solution.
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 Oct 13, 2005, at 12:32 AM, Wendy Smoak wrote:
From: "Don Brown" <[EMAIL PROTECTED]>
Thanks, I'll look at it tonite.
I just looked at it and I think this is another case where we
need to
decouple a sub-project from the common build. You're picking up
a couple of
dependencies that you don't need (antlr and fileupload) and I'm
having
trouble getting Maven to pick up additional files (**/*.conf)
from the
src/test directory. The test is failing because it can't find
sqlmap.conf.
So... for now I'm just going to add a project.properties file
to make Maven
skip the tests for Struts Flow, and (unless you want to work on
the Maven
build) I'll get back to it eventually and give it a separate
build file.
And maybe even get the example webapp into the nightly
build. :) Right now
I just need the website build to work.
James, can you check the nightly builds? They should be failing
as well,
but they're not. The project.xml in the 20051013 Struts Flow
nightly build
does not have Don's changes from 10/8.
--
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]
---------------------------------------------------------------------
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]
