incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmuer <>
Subject Re: Invalid jms.jar (was: Build failed in Hudson....)
Date Tue, 15 Dec 2009 22:17:30 GMT
If the jar is only on servers this would be an issue
anyway. I'm wondering if this dependency is really needed or could be
excluded, maybe its just an optional log4j backend or similar that
uses it. if the mulgara storage provider doesn't compile/run with such
an exclusion we could also simply exclude mulgara storage from being a
module in the parent (and move to a special section in the repo). At
least with the current implementation there's no known advantage of
having a mulgara backend over TDB or sesame, in fact it seems to be
very slow.


On Tue, Dec 15, 2009 at 6:07 PM, Bertrand Delacretaz
<> wrote:
> On Tue, Dec 15, 2009 at 5:31 PM, Apache Hudson Server
> <> wrote:
>> ...
>> [INFO] Compilation failure
>> error: error reading /home/hudson/.m2/repository/javax/jms/jms/1.1/jms-1.1.jar; error
in opening zip file...
> I tried mvn depedency:resolve in
> org.apache.clerezza.parent/ on
> my own computer, after deleting the javax/jms part of my local Maven
> repository, and once the build is done I get an HTML file with a
> redirect message instead of a jar file in there, see below.
> Note sure how to fix that, as that jms.jar is a transitive dependency,
> but it's definitely not an issue with the Hudson server.
> -Bertrand
> cat $HOME/.m2/repository/javax/jms/jms/1.1/jms-1.1.jar
> <html><head>
> <title>301 Moved Permanently</title>
> </head><body>
> <h1>Moved Permanently</h1>
> <p>The document has moved <a
> href="">here</a>.</p>
> <hr>
> <address>Apache Server at Port 443</address>
> </body></html>

View raw message