OK,
The 2 changes that I would make are simple. 1, use 'co' instead of 'export'
when getting any of the sources out of CVS. 2, Make it more explict which
project.xml is being edited.
Here it is in full.
- get maven. Best, get a snapshot. Install it. Read the FAQ about the beta-9
brokenness. If you're brave, try to get the HEAD to compile.
- prepare the maven-torque-plugin which in its current incarnation is not
able to
build the Turbine peers:
* get the alpha2 snapshot of Torque:
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co -r
TORQUE_3_1_ALPHA2 db-torque
* build the generator:
cd db-torque/src/generator
maven
* install the generator jar to your <user-home on your
machine>/.maven/repository/torque/jars/ subdirectory
* go to <user-home on your
machine>/.maven/plugins/maven-torque-plugins-3.1
* edit your project.xml file:
= look for the "torque-gen" dependency:
<dependency>
<groupId>torque</groupId>
<artifactId>torque-gen</artifactId>
<version>20030327.070220</version>
<properties>
<classloader>root</classloader>
</properties>
</dependency>
change it to
<dependency>
<groupId>torque</groupId>
<artifactId>torque-gen</artifactId>
<version>3.1-alpha2</version>
<properties>
<classloader>root</classloader>
</properties>
</dependency>
= add the following dependency:
<dependency>
<id>commons-logging</id>
<version>1.0.3</version>
<properties>
<classloader>root</classloader>
</properties>
</dependency>
- get the following jars from java.sun.com:
activation.jar put it into
~/.maven/repository/jaf/jars/activation-1.0.2.jar
jndi.jar put it info ~/.maven/repository/jndi/jars/jndi-1.2.1.jar
jdbc.jar put it info ~/.maven/repository/jdbc/jars/jdbc-2.0.jar
mail.jar put it info ~/.maven/repository/javamail/jars/javamail-1.3.jar
- get the current turbine HEAD
cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co -r HEAD
jakarta-turbine-2
- run maven
The following errors might occur:
1) Maven dies with
--- cut ---
The build cannot continue because of the following unsatisfied
dependencies:
activation-1.0.2.jar
javamail-1.3.jar
jdbc-2.0.jar
jndi-1.2.1.jar
--- cut ---
=> You've forgotten to get the java.sun.com jars
2) Maven dies with
--- cut ---
The build cannot continue because of the following unsatisfied
dependencies:
<any other jar>
--- cut ---
=> We're requiring a jar that is not on ibiblio. You can use our
unofficial
Turbine repository by uncommenting the following line in
project.properties
maven.repo.remote=http://www.ibiblio.org/maven/,http://jakarta.apache.org/tu
rbine/repo
Note that this still won't help you with the Sun-provided jars.
3) The Peers are created with strange names and/or wrong packages
=> Your $MAVEN_HOME variable is not set correctly
That is it.
David
-----Original Message-----
From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
Sent: 08 July 2003 13:17
To: [EMAIL PROTECTED]
Subject: Re: Cryptic failure of build for T2.3-dev
"David Wynter" <[EMAIL PROTECTED]> writes:
Good to hear. I was starting to wonder whether we have a problem on the
Win2K platform.
Even if you got it to build: Can you try doing it step by step with the
Howto I posted yesterday and add any necessary windows-specific points.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
