Yeah, since this is our artifact, repo removal should not be an
obstacle.
Ari, I think you need to bootstrap with Mac profile flag from the root
first, before running build-mac.sh:
mvn -P mac install
Andrus
On Aug 6, 2008, at 9:37 AM, Kevin Menard wrote:
You probably need to bootstrap the environment then, as if you were
installing for the first time. I guess this means I just wasted time
deploying snapshots last weekend :-/
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.
--
Kevin
On Wed, Aug 6, 2008 at 9:31 AM, Aristedes Maniatis <[EMAIL PROTECTED]>
wrote:
On 06/08/2008, at 1:00 PM, [EMAIL PROTECTED] wrote:
snapshot repo at people.apache.org just got (partially?) nuked, so
cleaning test snapshot deps
Modified:
cayenne/main/trunk/itests/jpa-chapter5/pom.xml
cayenne/main/trunk/pom.xml
I think there is more to it than just this. When trying to run
assembly/build-mac.sh I get this error:
[INFO] Configured Artifact:
org.apache.cayenne:cayenne-modeler-mac:null:3.0-SNAPSHOT:jar
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
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
I think this explains my frustration with trying to test Andrey's
work and
commit it. Instead of using the local version of the modeler, it was
grabbing bits from the snapshot repository and using some old code.
"mvn -P mac package" is the culprit here, but I can't see what in
the pom
file causes it to go to people.apache.org. There are only two
references to
p.a.o:
docs/quick-start-rop/cayenne-rop-client-tutorial/pom.xml
pom.xml (top level)
I'm thinking we need to get rid of both of these references.
Furthermore, I don't understand how maven caches files when they
aren't
versioned (such as the snapshots). What forces maven to use the
most recent
version of a jar and not something two weeks old?
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
