On 07/08/2008, at 6:44 AM, Andrus Adamchik wrote:
Yes, this is totally related to my commit and tangentially related to Ari's problem. And in fact I posted a few messages to infra in regards to that last night, as I think it was handled terribly. But I have no time to argue with all the "we did you a great service by breaking your build" types, so I am out of this discussion. Simon is one of the few voices of reason there BTW.
Absolutely agree. I added some notes yesterday to the download page about artifacts disappearing without notice. Is there some way to have maven not search p.a.o to grab artifacts? I see that the repository is defined in the top level pom file since it is needed for publishing, but can it be suppressed so that that isn't used automatically as part of the build cycle if local artifacts are not found?
By the way, even after deleting ~/.m2, running mvn clean, mvn install, mvn -P mac install, and then building the assembly I still get old cayenne-client code built into the result. I stopped working on it at the point when I felt I needed to hurl my laptop at the wall. I'll try again today and take a fresh look at this.
Ari --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
