lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Building on windows
Date Mon, 14 Mar 2011 15:20:48 GMT
Thanks, I finally got back to this. Turns out that my ant directory
had some jasper jars in it, I have no clue how they got there. Anyway,
I downloaded a new ANT distro and replaced my old one and all is well.

Don't know what/why that would have changed, but "I didn't do nuttin'"
and "I'm sure nothing on my machine changed". And if you accept that I
have a land deal for you.


On Thu, Mar 10, 2011 at 1:41 PM, Steven A Rowe <> wrote:
> Hi Erick,
> I regularly build on Windows, and I've never encountered this problem.
> My environment: I'm on Windows 7 64-bit, using Oracle Java 1.6.0_23 64-bit and Ant 1.7.1.
> My Ant installation directory doesn't have any jasper libs in it ("find . -name '*ja?sp*.jar'"
under cygwin bash shell returns nothing), and the output from "ant -diagnostics", which shows
the ant classpath and boot classpath, doesn't show anything named "*jsp*" or "*jasper*".
> The "jasper" <taskdef> under the "test-jsp" target includes everything (recursively)
under solr/example/lib/ in the classpath for the "JspC" task invocation, so the compiler,
AFAICT, should be coming from somewhere under solr/example/lib/jsp/.
> My guess is that the other jasper jars in your classpath (outside of solr/example/lib/jsp/)
are blocking successful completion of the Solr "test-jsp" target for you.
> Steve
>> -----Original Message-----
>> From: Erick Erickson []
>> Sent: Tuesday, March 08, 2011 12:15 PM
>> To:
>> Subject: Building on windows
>> I've gotta be overlooking the obvious, but I can't seem to run the
>> "dist" or "example" targets on my windows 7 machine on a fresh
>> checkout. The last time I compiled was about three weeks ago, so
>> things are kind of stale. Here's the problem trace:
>> test-jsp:
>>     [mkdir] Created dir: C:\apache-trunk-unmodified\solr\build\jsp-temp
>> 2011-03-08 11:51:59 - ERROR-the file '\admin\action.jsp' generated the
>> following general exception: org.apache.jasper.Ja
>> sperException: /admin/header.jsp(0,0) Page directive: can't have
>> multiple occurrences of contentType
>> C:\apache-trunk-unmodified\solr\build.xml:575:
>> org.apache.jasper.JasperException: Error compiling \admin\action.jsp
>>         at org.apache.jasper.JspC.processFile(
>>         at org.apache.jasper.JspC.execute(
>>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>         at
>> sun.reflect.NativeMethodAccessorImpl.invoke(
>> 39)
>> It looks like Jasper (?) is getting confused about ContentType in
>> included files.... Any off-the-top-of-your-head ideas? I don't want
>> anyone to take time out for this, but did want to mention it in case
>> it's something we should be aware of for the upcoming release. I can
>> get along just fine with artifacts from the nightly build.
>> I can run tests from inside Idea, which isn't too surprising as this
>> error looks related to packaging the web app, so I'm able to make
>> progress, so please don't waste any time on it if it's my problem,
>> stale jars, or any other such nonsense.....
>> I have jasper 4.1.36 in my ant directory, and some unversioned jasper
>> compiler and runtime in my \classtest\tomcat\common\lib directories
>> (probably from a Solr distro?). More unversioned jasper
>> compiler/runtime in the jetBrains directories (for Idea ?).
>> Thanks,
>> Erick
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message