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.
Andrus
On Aug 6, 2008, at 4:37 PM, Mike Kienenberger wrote:
Maybe this is somehow related? Maybe not -- maven is a black box to
me and I haven't been following that closely. [Note that the final
conclusion is that all files will be purged after 30 days -- search
for the thread if you want to know the details]
---------- Forwarded message ----------
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Aug 6, 2008 5:23 AM
Subject: disappearing apache snapshots (was Re: [myfaces site] skin)
To: MyFaces Development <[EMAIL PROTECTED]>
Grant Smith schrieb:
I was idling in #asfinfra on freenode yesterday and looking at the
logs now I see they did clean out that repository...
Just to let people know, there is currently some discussion going on
at the infrastructure list about this.
It was indeed the infra team who deleted all files older than 30
days, as people.apache.org was running short of disk space.
The current opinion of the infra admins seems to be that they reserve
the right to delete stuff from the snapshot repo at any time, and that
any reliance on files staying in the snapshot repo for more than a
couple of days is wrong. In particular, some people are concerned that
allowing non-apache people access to the snapshot repo for any purpose
other than testing of artifacts is equivalent to bypassing the release
process, ie any use of this repo except for internal apache
development purposes is wrong (my phrasing).
A couple of contrary opinions have been expressed; I'll let you know
what the final conclusion is.
Regards,
Simon
On 8/6/08, Aristedes Maniatis <[EMAIL PROTECTED]> wrote:
On 06/08/2008, at 11:59 PM, Andrus Adamchik wrote:
Ari, I think you need to bootstrap with Mac profile flag from the
root
first, before running build-mac.sh:
mvn -P mac install
Ah, that worked, thanks. I was bootstrapping but just with 'mvn
install'. I
see now that p.a.o was being used just as a fallback since the
local file
system didn't have the needed jar.
On 06/08/2008, at 11:37 PM, Kevin Menard wrote:
As for versioning, the snapshot artifacts have timestamps attached
to
them. Maven uses though when determining which version to use. You
can pin to a given version of a snapshot this way as well.
OK, but how does it know that to build the modeler it needs to use
the
cayenne-client jar from the same svn checkout (that is, the one
created 10
minutes ago is fine, but not the one from yesterday)?
In this case, the failed download was
Downloading:
http://people.apache.org/repo/m2-snapshot-repository//org/apache/cayenne/cayenne-modeler-mac/3.0-SNAPSHOT/cayenne-modeler-mac-3.0-SNAPSHOT.jar
nothing in that path that gives us a timestamp. Seems rather
dangerous
since (like I have been for four days now) you can easily build the
wrong
bits into the assembly. Even with any number of 'mvn clean's, I was
creating
modelers with new modeler code and old cayenne-client code. I now
know that
to build and run the modeler on OSX and be sure of getting current
code I
should:
# mvn -P mac install
# cd assembly
# ./build-mac.sh
open dmg and run
That all takes quite some time. About 15 minutes on my laptop.
Anyhow, I'm not going to fight with maven. I've got a set of magic
steps
now.
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
