Alex Karasulu wrote:

You called it once again thanks man! I feel like a moron.


Hey - don't feel like a moron. First time this happened to me I spend a day stuffing around with system traces, rebuilding, etc. Based on that process the actual error reporting is rather reliable which is why I was able to spot the issue.


Hopefully this will be resolved in the next imminent release of Maven 11.

Cheers, Steve.


p.s. I'm cross positing to maven dev just so that they are in the loop - and for there benefit - a summary is included below. Fistly - the problem:


http://marc.theaimsgroup.com/?l=avalon-users&m=106370654227153&w=2

and the underlying issue:

Sometimes when you build a artifact using jar:snapshot install, the resulting
artifact SNAPSHOT jar file is not updated. More specifically, a
<artifact-name>-<SNAPSHOT-SIGNATURE>.jar file is older that the most recent
<artifact-name>-SNAPSHOT.jar.


I'm presuming that this is a known problem.

SJM

--

Stephen J. McConnell
mailto:[EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to