On 20/03/12 09:24, Andy Seaborne wrote:
On 20/03/12 04:24, Paolo Castagna wrote:
Hi Rob,
this is a problem I sometimes have when I check out stuff from trunk,
mvn package it and then I use the scripts in bin/.
Is this what you were doing?
Somehow, the scripts search for Java binaries in the classes/ directory
instead of target/classes. Only if you fire up Eclipse and compile the
project with Eclipse you'll find out you have stuff in the classes/
directory.
Here is a message where I was having probably exactly your problem:
http://markmail.org/message/yxxofyp6h5cpwmdx
markmail is down but IIRC that was TDB.
And, lo, tdb_path does indeed do existence testing of directories in the
dev setup.
Copied to ARQ.
Andy
My proposal is to:
- CP="$DIRROOT/classes${CP}"
+ CP="$DIRROOT/target/classes${CP}"
See the discussion at the time.
Can we have a solution that does fix one thing by breaking something
else? By your own admission, that will break Eclipse development unless
you do something else as well.
The suggestion at the time was to test for the existence or otherwise of
$DIRROOT/classes. if it exists, add it, else if the maven target dir
exist, add it.
