Building from trunk

[Apoptosis]

I have been trying to build the code from the repository trunk and
have hit a few snags...

I am not sure if your still using eclipse but I have to make some
modifications to get it to compile:

.classpath
-------------------------------------------------------------------------------------------
1) Add: <classpathentry kind="lib" path="lib/spring-2.5.6.jar"/>
2) Alter: <classpathentry kind="output" path="build/bin"/> (To match
ant bin.dir, so that AntEnhanceTask is found)

After I do that I still have trouble compiling:

com.avaje.ebean.server.lib.sql.ExtendedPreparedStatement
com.avaje.ebean.server.lib.sql.PooledConnection

Because they don't fully implement their interfaces. I first assumed
it was because I was using jdk 1.6, however I looked all the way back
to jdk 1.4 and many of the unimplemented methods were in 1.4.

I can imagine your compiling just fine... Which interfaces are you
compiling against?

Jacob

[Rob Bygrave]

>> 1) Add:  <classpathentry kind="lib" path="lib/spring-2.5.6.jar"/>
2) Alter: <classpathentry kind="output" path="build/bin"/> (To match
ant bin.dir, so that AntEnhanceTask is found)

Yes, I think we may want to add a "ide.bin.dir" to use just for the enhancement task... as the "bin.dir" is used elsewhere in the build.

>> After I do that I still have trouble compiling:

com.avaje.ebean.server.lib.

sql.ExtendedPreparedStatement
com.avaje.ebean.server.lib.sql.PooledConnection

 

You need to compile using JDK 1.5 (not JDK 1.6 due to changes in java.sql API).

Check both of these settings:
  eclipse - project - properties - java build path - libraries - JRE System Library [JDK1.5]
  eclipse - project - properties - java compiler - JDK compliance [JDK1.5]

That should do the trick.

Cheers, Rob.

[Hielke Hoeve]

On 6 jul, 04:55, Rob Bygrave <robin.bygr...@gmail.com> wrote:
> *>> 1) Add:  <classpathentry kind="lib" path="lib/spring-2.5.6.jar"/>

> 2) Alter: <classpathentry kind="output" path="build/bin"/> (To match
> ant bin.dir, so that AntEnhanceTask is found)

> *

> Yes, I think we may want to add a "ide.bin.dir" to use just for the
> enhancement task... as the "bin.dir" is used elsewhere in the build.

Is there any reason why you are using maven and ant together? Maven
can build the projects in any fashion you wish...

I am trying to setup a java webapp (Wicket) as demo linked to the
ebean source but when using maven I can't seem to link all the
dependencies just right. I have to do major changes in the provided
poms, but that might also be because of my demands :-)
Also the sample application is still referring to ebean 1.1 (still
works with 1.2 though).

Hielke

BTW: Great job! This looks promising!

[edge]

The current poms are not actually being used to build Ebean.
We intend to move to maven after our next major release 2.0 which is
coming up soon and we're actually working on refactoring the API to
make it easier to build with maven.
So, short term you'll have to use ant

Eddie