Folks,
I think that there may be a problem with building the SCA code from trunk.
I did an svn update on my system yesterday and then did mvn clean.
This FAILED, complaining about not being able to find jars relating to
Saxon 9.0.0.2. I then tried simply mvn, which also failed, this time
due to a failure in one of the itests. Checking the itest failure, it
is caused by not doing mvn clean first.... ;-)
So catch 22. My understanding is that the regular mvn processing fixes
up the Saxon 9.0.0.2 issue - but that can't run properly unless mvn
clean is able to execute fully.
I've not raised a JIRA yet as I'd like to be sure that I've got this
right - so I'd appreciate views from anyone who knows about the Saxon
stuff and why mvn clean fails.
Yours, Mike.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
