5 PM
To: Maven Users List
Subject: RE: Ordering of compilation
Hi Nick,
I have switched to your approach and do as follows:
Module 1: build first java package
Module 2: translate SQLJ and build second java package (with module 1
listed as a dependency within the pom)
However, whatever I seem to d
2008 12:22
To: Maven Users List
Subject: RE: Ordering of compilation
As an afterthought, I would still recommend two modules:
module 1: compile and process-classes (which is a phase, to bind your
sqlj plugin to) module 2: dependency on module 1 and compile
This is much easier to understand for
Stolwijk
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wed 1/9/2008 1:17 PM
To: Maven Users List
Subject: RE: Ordering of compilation
The target/classes directory is in the classpath (check with mvn -X clean
compile). Did you generate classes or java files? If
http://mojo.codehaus.org/build-helper-maven-plugin/index.html
-Original Message-
From: Matthew Tordoff [mailto:[EMAIL PROTECTED]
Sent: Wed 1/9/2008 12:30 PM
To: Maven Users List
Subject: RE: Ordering of compilation
Hi Nick,
Thanks for your response. I actually decided to follow your second
o
PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 09 January 2008 10:15
To: Maven Users List
Subject: RE: Ordering of compilation
> I am looking at building the initial java code in a separate module,
> then importing it and unpacking it as a dependency and then continuing
> with the build as
> I am looking at building the initial java code in a separate module,
> then importing it and unpacking it as a dependency and then continuing
> with the build as previously designed, packing everything up in a single
> JAR at the end.
I would go for this way. Even not unpacking the dependency, b
