Jeremy Hughes wrote:
When releasing a module (B) that depends on a module (A), A has to be
available in a repo (local or remote). So either you could install the
artifacts from the staging repo into your local repo or you could
configure maven to look in the staging repo. But this is slightly
dangerous because if we were to respin and create a new release
candidate then we would be replacing the artifacts in the staging repo
and I don't think the maven client would pick this up.
An alternatives to this in the future would be to create a branch
prior to releasing, so others can continue to develop on the trunk
which the release is being finalized. However, with this there were
quite a lot of structural changes going on and this is usually tricky
to merge back in afterwards.
Moving the release candidate over to a branch and moving the trunk up
to 0.2-incubating-SNAPSHOT would be a pain right now. Is there any way
you can cope until the vote has ended?
Valentin's suggestion works, so the answer is yes. I do however feel
slightly uncomfortable that any visitor to the Aries site who decides to
check out and build the code will not be able to for some indeterminate
period. I think I'll put a note on the Website in the 'Building Aries'
section, I can take it down again after things go back to normal.
Thanks,
Jeremy
On 12 April 2010 11:48, Jeremy Hughes <[email protected]> wrote:
Hmm, I'll look into this. I had expected the maven-release-plugin to
bump *everything* up to 0.2-incubating-SNAPSHOT
On 11 April 2010 12:46, zoe slattery <[email protected]> wrote:
Hi Valentin
I see, is it perhaps little incentive to vote +1 because the build
will be broken till we do? :-)
Thanks - that helps a lot. In case it's useful these are the commands
I used to modify all the poms.
find . -name "pom.xml" | xargs sed -i {}
"s/0.1-incubating-SNAPSHOT/0.2-incubating-SNAPSHOT/g"
find . -name "pom.xml" | xargs sed -i {}
"s/0.1-incubating/0.2-incubating-SNAPSHOT/g"
Zoe
On 11 April 2010 12:01, Valentin Mahrwald <[email protected]> wrote:
Hi Zoe,
as far as I understand it the build is in a bit of an unholy state due to
upcoming release (so there is 0.1-incubating, 0.1-incubating-SNAPSHOT and
0.2-incubating-SNAPSHOT freely intermixed). I assume this is going to go
away once the 0.1-incubating binaries are in an external maven repository
(maybe they already are, but I could not find them).
As an interim measure I would suggest you do the following locally:
Replace all in project: "0.1-incubating-SNAPSHOT" ->
"0.2-incubating-SNAPSHOT"
Replace all in project: "0.1-incubating" -> "0.2-incubating-SNAPSHOT"
This will give you consistently version "0.2-incubating-SNAPSHOT" and stuff
starts building again.
Hope this helps,
Valentin
On 11 Apr 2010, at 11:17, zoe slattery wrote:
Hi - I'm not able to build Aries at the moment. I'm not sure is this
is some problem with the slightly unusual network set up at Knockree
(I'm at the Apache retreat), or the instructions being out of date...
although it looks to me as though Hudson is having similar issues. Any
ideas?
My build fails when I try to build the eba-maven-plugin, like this:
Downloading:
http://repo1.maven.org/maven2/org/apache/aries/java5-parent/0.1-incubating/java5-parent-0.1-incubating.pom
[INFO] Unable to find resource
'org.apache.aries:java5-parent:pom:0.1-incubating' in repository
central (http://repo1.maven.org/maven2)
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: null:eba-maven-plugin:maven-plugin:0.2-incubating-SNAPSHOT
Reason: Cannot find parent: org.apache.aries:java5-parent for project:
null:eba-maven-plugin:maven-plugin:0.2-incubating-SNAPSHOT for project
null:eba-maven-plugin:maven-plugin:0.2-incubating-SNAPSHOT
--
Zoe Slattery
IBM
--
Zoe Slattery
IBM
