Matt Raible wrote:
On 1/31/07, *Dale Newfield* wrote:
Matt Raible wrote:
> I had problems with Struts 2 and File Upload in AppFuse 2. Upgrading
> to commons-fileupload 1.1.1 and commons-io 1.1 fixed the problem.
My commons-fileupload was 1.1, so an upgrade to 1.1.1 seems in order.
commons-io, on the other hand, was already at 1.2...did you mean the
current 1.3?
I only saw 1.1 in the Maven repo - wasn't aware that 1.3 existed.
AppFuse 1.9.4 included commons-io 1.2, which is what confused me. Guess
I'll upgrade to 1.3 :-)
For that matter, I guess it makes sense to look at each of the jakarta
commons jars in lib/jakarta-commons/. In the MANIFEST.MF file in each
there is listed an "Implementation-Version". Looking on the jakarta
website reveals what is currently available. Turns out that 2/3 of the
1.9.4 jars are not current:
component in 1.9.4 current
------------------------ ------------------------- ----------
commons-beanutils.jar: 1.6 1.7
commons-chain-1.1.jar: 1.1 up to date
commons-collections.jar: 3.1 3.2
commons-dbcp.jar: 1.2.1 up to date
commons-digester.jar: "1.6" 1.8
commons-fileupload.jar: 1.1 1.1.1
commons-io.jar: 1.2 1.3
commons-lang.jar: 2.1 2.2
commons-logging-1.1.jar: 1.1 up to date
commons-pool.jar: 1.2 up to date
commons-validator.jar: 1.3.0 1.3.1
jakarta-oro.jar: 2.0.7 2003-01-25 09:27:58 2.0.8
I recognize that the whole point of maven is to have this all magically
happen for you, but for those of us still developing 1.9.4 apps, can
anyone describe any reason not to upgrade any of these?
I'll probably also modify so that the version number is in the .jar file
name.
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
