navigate to the
target/checkout directory.... Run "mvn install" once, to
have it produce dependencies. Then you'd be able to actually perform the
release.
That worked for me. Something is fishy here. The mvn:prepare goal
formerly ran the install goal for each module and installed it locally
for the tagged version, so something has changed to require explicitly
building and installing the tagged version.
In any case the build completed and I've staged the artifacts in OSS
such that they should appear in Maven Central shortly. I'll send a
release announcement to the usual channels as soon as I confirm they're
available. I don't plan to push up distribution bundles to
jasig/downloads unless someone things they're useful. I would imagine
most early adopters and testers are pulling artifacts from Maven Central.
I've created a Jira issue to track improvements to the build system that
I would argue are required before we cut another release:
https://issues.jasig.org/browse/CAS-1322
Developers may lose hair, sanity, or both when dealing with the current
process.
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
