You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Bertrand Delacretaz <bd...@codeconsult.ch> on 2003/02/20 23:56:29 UTC

Re: The new build system (JDK 1.3.1/macosx issues)

Le Jeudi, 20 fév 2003, à 21:44 Europe/Zurich, Stefano Mazzocchi a écrit  
:
> The new build system has landed on CVS.

woooh-hooh-hooh, looks great!

I have a few issues here however, most probably related to my JDK  
(1.3.1 on macosx 10.2.3).

After a build clean + CVS update (no local.* stuff), build.sh works (1  
minute 6 seconds - wow!)

I checked that the target.vm property is correctly set to "1.2" in  
build.xml.

ISSUE 1 - JDBC3 stuff
"build.sh webapp" fails:
src/org/apache/cocoon/components/language/markup/xsp/ 
AbstractEsqlConnection.java:298: cannot resolve symbol
symbol  : class Savepoint
location: package sql
       public java.sql.Savepoint setSavepoint()

Most probably this has to do with the "jdbc3.present" property used by  
./src/blocks/databases/build.xml. I tried to set this property in the  
optional-tests target of the main build.xml but it didn't help.


ISSUE 2 - "build run"
"build.sh run" says "NoClassDefFoundError: org/xml/sax/ContentHandler"  
unless I add this to the classpath of the run target:

   <fileset dir="lib/endorsed">
   	 <include name="*.jar"/>
   </fileset>

Using the <classpath> from the build.old.xml, the "run" target works as  
well (that is, jetty starts but as I have no webapp it doesn't go that  
far).
Also a JDK 1.3.1 issue I think, as this interface is standard in 1.4  
AFAIK but not in 1.3.1.

-Bertrand


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Re: The new build system (JDK 1.3.1/macosx issues)

Posted by Stefano Mazzocchi <st...@apache.org>.
Bertrand Delacretaz wrote:
> Le Jeudi, 20 fév 2003, à 21:44 Europe/Zurich, Stefano Mazzocchi a écrit  :
> 
>> The new build system has landed on CVS.
> 
> 
> woooh-hooh-hooh, looks great!

thank you.

> I have a few issues here however, most probably related to my JDK  
> (1.3.1 on macosx 10.2.3).

ok, I'm working on JDK 1.4.1 on win2k so I was expecting something like 
this.

> After a build clean + CVS update (no local.* stuff), build.sh works (1  
> minute 6 seconds - wow!)

cool

> I checked that the target.vm property is correctly set to "1.2" in  
> build.xml.

great

> ISSUE 1 - JDBC3 stuff
> "build.sh webapp" fails:
> src/org/apache/cocoon/components/language/markup/xsp/ 
> AbstractEsqlConnection.java:298: cannot resolve symbol
> symbol  : class Savepoint
> location: package sql
>       public java.sql.Savepoint setSavepoint()
> 
> Most probably this has to do with the "jdbc3.present" property used by  
> ./src/blocks/databases/build.xml. I tried to set this property in the  
> optional-tests target of the main build.xml but it didn't help.

hmmm, might be a problem with the invocation of the block build. I 
didn't really test that one since it was working for me. I'll try more 
stuff.

> 
> ISSUE 2 - "build run"
> "build.sh run" says "NoClassDefFoundError: org/xml/sax/ContentHandler"  
> unless I add this to the classpath of the run target:
> 
>   <fileset dir="lib/endorsed">
>        <include name="*.jar"/>
>   </fileset>

Oh, damn, you're totally right. Since JDK 1.3.x doesn't have the 
-endorsed command line tag, jetty doesn't find things.

I'm installing JDK 1.3.1 so that I can see these problems myself.

> Using the <classpath> from the build.old.xml, the "run" target works as  
> well (that is, jetty starts but as I have no webapp it doesn't go that  
> far).
> Also a JDK 1.3.1 issue I think, as this interface is standard in 1.4  
> AFAIK but not in 1.3.1.

Yes, it's trivial to fix, but I'll install JDK 1.3.1 so that I can do 
stuff myself.

Thanks and keep up reporting the problems.

-- 
Stefano Mazzocchi                               <st...@apache.org>
    Pluralitas non est ponenda sine necessitate [William of Ockham]
--------------------------------------------------------------------



Re: The new build system (JDK 1.3.1/macosx issues)

Posted by Pier Fumagalli <pi...@betaversion.org>.
"Christian Haul" <ha...@dvs1.informatik.tu-darmstadt.de> wrote:

> ISSUE 3: mocks 4 blocks
> It appears that building mocks does not work currently. IOW all blocks
> that have mocks don't build :-(

Whopsie? I went through the compilation of all blocks (except databases)
fine, but now it's reporting:

prepare-webapp-samples:
Copying 1 file to 
/Users/pier/Desktop/cocoon/build/cocoon-2.1-dev/webapp/WEB-INF/lib
Reading: 
/Users/pier/Desktop/cocoon/build/cocoon-2.1-dev/webapp/samples/sitemap.xmap

BUILD FAILED
file:///Users/pier/Desktop/cocoon/build.xml:669: IOException:
java.io.FileNotFoundException:
/Users/pier/Desktop/cocoon/build/cocoon-2.1-dev/webapp/samples/sitemap.xmap
(No such file or directory)

Still some ironing out to do...

    Pier


Re: The new build system (JDK 1.3.1/macosx issues)

Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
ISSUE 3: mocks 4 blocks 
It appears that building mocks does not work currently. IOW all blocks
that have mocks don't build :-(

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

Re: The new build system (JDK 1.3.1/macosx issues)

Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
ISSUE 3: mocks4blocks

It appears that no blocks with mock classes can be build because the
mock classes are not compiled (or even copied).

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

Re: The new build system (JDK 1.3.1/macosx issues)

Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Thursday, February 20, 2003, at 10:56 PM, Bertrand Delacretaz wrote:

> Le Jeudi, 20 fév 2003, à 21:44 Europe/Zurich, Stefano Mazzocchi a  
> écrit :
>> The new build system has landed on CVS.
>
> woooh-hooh-hooh, looks great!
>
> I have a few issues here however, most probably related to my JDK  
> (1.3.1 on macosx 10.2.3).
>

I am sorry to report problems too.

MacOSX 10.2.4, JVM 1.3.1.

/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:53: package  
oracle.jdbc does not exist
import oracle.jdbc.OracleResultSet;
                    ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:54: package  
oracle.sql does not exist
import oracle.sql.BLOB;
                   ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:55: package  
oracle.sql does not exist
import oracle.sql.CLOB;
                   ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:187: cannot  
resolve symbol
symbol  : class OracleResultSet
location: class org.apache.cocoon.acting.OraAddAction
                 OracleResultSet set = (OracleResultSet)  
LOBstatement.executeQuery();
                 ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:187: cannot  
resolve symbol
symbol  : class OracleResultSet
location: class org.apache.cocoon.acting.OraAddAction
                 OracleResultSet set = (OracleResultSet)  
LOBstatement.executeQuery();
                                        ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:204: cannot  
resolve symbol
symbol  : class CLOB
location: class org.apache.cocoon.acting.OraAddAction
                                 CLOB ascii = set.getCLOB(index);
                                 ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/acting/OraAddAction.java:217: cannot  
resolve symbol
symbol  : class BLOB
location: class org.apache.cocoon.acting.OraAddAction
                                 BLOB binary = set.getBLOB(index);
                                 ^
/Users/jermq/Checkouts/Secure/xml-cocoon2/build/cocoon-2.1-dev/blocks/ 
databases/src/org/apache/cocoon/components/modules/database/ 
IfxSerialAutoIncrementModule.java:78: package com.informix.jdbc does  
not exist
         return new Integer(((com.informix.jdbc.IfxStatement)  
stmt).getSerial());


not sure where to go with this ....

any suggestions?

many thanks

regards Jeremy