commons-fileupload does not build

[matt@…]

Today I am trying to install Tomcat6 on a 2010 standard Mac mini running 10.6.6 and I am unable to get it to install because I am receiving an error caused by the inability to install commons-fileupload. I also experienced this with a Core2Duo 27" iMac with 10.6.6. The files are being pulled from the Facebook Apache mirror ​http://mirror.facebook.net/apache/commons/fileupload/ .

---

[matt@…]

_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_commons-fileupload

[ryandesign (Ryan Carsten Schmidt)]

The relevant error seems to be:

      [get] Error opening connection java.io.IOException: Server returned HTTP response code: 502 for URL: http://repo1.maven.org/maven/commons-io/jars/commons-io-1.3.2.jar

See also #27776.

[matt@…]

Replying to ryandesign@…:

The relevant error seems to be:

      [get] Error opening connection java.io.IOException: Server returned HTTP response code: 502 for URL: http://repo1.maven.org/maven/commons-io/jars/commons-io-1.3.2.jar

See also #27776.

Is there an available fix?

[ryandesign (Ryan Carsten Schmidt)]

On second thought, that may not be the relevant error after all. It appears in my log too, but commons-fileupload still builds.

[matt@…]

Replying to ryandesign@…:

On second thought, that may not be the relevant error after all. It appears in my log too, but commons-fileupload still builds.

What version of OS X are you running and are you running the most recent java update 4 or the last one (3)?

Quite frankly I believe this is the error...

[javac] /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_commons-fileupload/work/commons-fileupload-1.2.1-src/build.xml:80: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds

[matt@…]

Because this is not a 502 error issue can this be changed to an appropriate ticket name?

[matt@…]

Thank you for changing the name. I am continuing to try to resolve this issue and have noticed that all the response are replying with bad gateways (502) and am now trying to set the build files to reference additional sources. It does not appear that the files have changed at in some time and I was able to build this, as recently as two weeks ago. I appreciate the help to get this resolved.

[kamil@…]

(sorry if this is stating the obvious)

It looks like the commons-fileupload port is going out to the maven repositories:

​http://repo1.maven.org/maven or ​http://people.apache.org/repo/m1-snapshot-repository

and trying to get: ​http://repo1.maven.org/maven/commons-io/jars/commons-io-1.3.2.jar But looking at: ​http://repo1.maven.org/maven/ returns a 502.

Then trying from the alternate: ​http://people.apache.org/repo/m1-snapshot-repository/commons-io/jars/ one finds that commons-io-1.3.2.jar does not (at time of writing) exist. And that part of the build returns: Error opening connection java.io.FileNotFoundException

[matt@…]

Thanks for the response Kamil, but I already posted the appropriate fix to the build.xml file. Hopefully this will help rectify this problem for the future. This build file that originated with this package work as recently as a few weeks ago so I assume there was some recent changes. Considering all the get/build systems out there, this is a testament for the need of a better and centralized notification system for projects to post changes to.

[kamil@…]

Hey Matt, using your build file, I get:

:info:build
:info:build BUILD FAILED
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_java_commons-fileupload/work/commons-fileupload-1.2.1-src/build.xml:2: Unexpected element "{http://www.w3.org/1999/xhtml}html" {antlib:org.apache.tools.ant}html
:info:build
:info:build Total time: 2 minutes 3 seconds

[matt@…]

How did you download it? That was most likely added by your browser or by the this server because that is a header element. Just click the link and copy that contents of the document into a plain text document and save it as build.xml. Then it will work.

[kamil@…]

Replying to matt@…:

How did you download it? That was most likely added by your browser or by the this server because that is a header element. Just click the link and copy that contents of the document into a plain text document and save it as build.xml. Then it will work.\

ok thanks. I got it.

[ryandesign (Ryan Carsten Schmidt)]

To all the people on this ticket: I've updated commons-fileupload to 1.2.2; has that helped?

[jmroot (Joshua Root)]

I can't reproduce this and neither can the buildbot: ​http://build.macports.org/builders/buildports-snowleopard-x86_64/builds/5274