Attachments

Activity

Are there any error messages in your logs, and if so can you attach any relevant stack trace to this bug report? Does the uploaded file have any non-ANSI characters in the name? Does this occur with all files, or can some be uploaded successfully? I've been busy with other things lately so haven't had a lot of time for JAMWiki development, but it's a long weekend here in the US so hopefully I'll be able to investigate in the next couple of days.

Ryan Holliday
added a comment - 2012-05-26 20:31 Are there any error messages in your logs, and if so can you attach any relevant stack trace to this bug report? Does the uploaded file have any non-ANSI characters in the name? Does this occur with all files, or can some be uploaded successfully? I've been busy with other things lately so haven't had a lot of time for JAMWiki development, but it's a long weekend here in the US so hopefully I'll be able to investigate in the next couple of days.

no, there aren't any error messages in the logs. It seams to be the expected behavior when no file could be uploaded. This occur with all files, regardless of the filename. Let me know if I can help with anything. I tried to build JamWiki myself, but there are some problems with the repositories (doesn't exist any more) of some dependencies.

I hope you enjoyed the long weekend. Here in Germany we also have a long weekend.

Pawel Sawicki
added a comment - 2012-05-28 09:19 Hi Ryan,
no, there aren't any error messages in the logs. It seams to be the expected behavior when no file could be uploaded. This occur with all files, regardless of the filename. Let me know if I can help with anything. I tried to build JamWiki myself, but there are some problems with the repositories (doesn't exist any more) of some dependencies.
I hope you enjoyed the long weekend. Here in Germany we also have a long weekend.
Best regards
Pawel

Alternately, if you'd like to build JAMWiki yourself the trunk and branches/1.2.x branch should now have the Maven problem you mentioned fixed - it looks like someone removed a version of exp4j from the Maven Central repository for some reason, which broke the JAMWiki build.

Ryan Holliday
added a comment - 2012-05-29 21:54 Hi Pawel,
I don't use Glassfish, but is it possible you have multiple versions of commons-fileupload in your classpath? Alternately, since you mentioned you are using 3.1.2, is it possible you are running into the same issue as https://community.jboss.org/thread/196311?_sscc=t (see http://java.net/jira/browse/GLASSFISH-18444 for the Glassfish issue report)?
Alternately, if you'd like to build JAMWiki yourself the trunk and branches/1.2.x branch should now have the Maven problem you mentioned fixed - it looks like someone removed a version of exp4j from the Maven Central repository for some reason, which broke the JAMWiki build.
Ryan

t looks like someone removed a version of exp4j from the Maven Central repository for some reason, which broke the JAMWiki build.
I haven't notice removal of exp4j from maven central and if you do a search you can reach the artifact at: http://search.maven.org/#search%7Cga%7C1%7Cexp4j

But maybe a <repository> element was pointing to the old nexus installation where exp4j was hosted, in which case id recommend removing the <repository> entry from the pom which points at "nexus.congrace.de"

frank
added a comment - 2012-06-04 09:19 Hola Guys,
t looks like someone removed a version of exp4j from the Maven Central repository for some reason, which broke the JAMWiki build.
I haven't notice removal of exp4j from maven central and if you do a search you can reach the artifact at: http://search.maven.org/#search%7Cga%7C1%7Cexp4j
But maybe a <repository> element was pointing to the old nexus installation where exp4j was hosted, in which case id recommend removing the <repository> entry from the pom which points at "nexus.congrace.de"
Hope that helped
Frank

Hi Frank - JAMWiki 1.2 was using exp4j 0.2.8, which no longer seems to be in Maven. I've updated the JAMWiki dependencies (trunk and the 1.2.x branch) to exp4j 0.2.9 to resolve most of the problems, although anyone building off of the 1.2 tag would still see a build failure.

Ryan Holliday
added a comment - 2012-06-04 09:24 Hi Frank - JAMWiki 1.2 was using exp4j 0.2.8, which no longer seems to be in Maven. I've updated the JAMWiki dependencies (trunk and the 1.2.x branch) to exp4j 0.2.9 to resolve most of the problems, although anyone building off of the 1.2 tag would still see a build failure.

Hey Ryan,
Now i'm really confused, 0.2.8 should not have been available on central at all, there was only a 0.2.8 artifact in the sonatype staging repo for a couple of days. 0.2.9 was the first version the sonatype guys let me push to central:https://issues.sonatype.org/browse/OSSRH-2334

could a reference to the staging repo in a pom.xml or settings.xml or even a local artifact have caused this behaviour?

frank
added a comment - 2012-06-04 12:30 Hey Ryan,
Now i'm really confused, 0.2.8 should not have been available on central at all, there was only a 0.2.8 artifact in the sonatype staging repo for a couple of days. 0.2.9 was the first version the sonatype guys let me push to central:
https://issues.sonatype.org/browse/OSSRH-2334
could a reference to the staging repo in a pom.xml or settings.xml or even a local artifact have caused this behaviour?

Marking as won't fix since the problem appears to be a bug in Glassfish - link to a Glassfish patch provided in the bug comments. Note that another user reported the same problem on jamwiki.org, and applying the Glassfish patch was confirmed to resolve the problem.

Ryan Holliday
added a comment - 2012-08-06 20:37 - edited Marking as won't fix since the problem appears to be a bug in Glassfish - link to a Glassfish patch provided in the bug comments. Note that another user reported the same problem on jamwiki.org, and applying the Glassfish patch was confirmed to resolve the problem.