On 17 October 2011 10:41, Jeremy Hughes <[email protected]> wrote: > On 17 October 2011 01:51, David Jencks <[email protected]> wrote: >> IIUC someone really did something very wrong here. Don't change committed >> dependencies (including parent poms) to a non-existent release. >> >> I'd suggest that someone call a release vote on the 0.5 parent pom right >> away, or revert all the claims that such a pom exists. >> >> meanwhile you might be able to resurrect things by building a 0.5 parent >> locally from the (presumably committed, but I didn't check) tag. This is >> kind of a terrible idea because your local maven repo will have something >> that looks released but isn't even under vote yet (the 0.5 parent pom) and >> you'll have to delete it by hand to ever download the official release (when >> it exists). > > Actually what you say has wider implications for our release process. > What we were planning was, at release time, in trunk, to set the > version in the pom to the released version. That would act as an > indicator as to whether anything has changed since the last release. > The first person to change something in the module would change the > version in the pom and add -SNAPSHOT. So if they made a bug fix they > would also increment the micro version, if they made a functional > additive change, they would increment the minor version. If they made > an API breaking change, they would increment the major version. From > what you say, though, even after the releases have been made public, > anyone could check out trunk, make a small change to a module that > hasn't yet had its version changed, and build, and if they hadn't > updated the version in the pom they would get their own build of the > released version in their .m2 local repo. And that would be wrong > because a) they would have local changes included in it b) it wouldn't > be the correctly signed artifacts that were voted on.
OK, so I'm replying to my own email :-) A sticking point is the version in the pom during the staging of releases and after the release. a) we don't want to choose the next version of a module while releasing the current one. b) the version needs to be something-SNAPSHOT to keep maven happy. c) it can't be currentrelease-SNAPSHOT because in maven that has the semantics of being a build leading up to the currentrelease. So, as a suggestion, during the release process, move the trunk to currentrelease-next-SNAPSHOT ... e.g. we're releasing 0.4, so after the staging is complete, trunk will be 0.4-next-SNAPSHOT. I think that solves all three constraints above. > > [1] http://aries.apache.org/development/releasingaries.html > >> >> thanks >> david jencks >> >> On Oct 16, 2011, at 4:38 PM, Alasdair Nottingham wrote: >> >>> I think I sort of know what the problem is. The parent poms are currently >>> versioned at 0.5 in trunk and all the other projects reference it as >>> 0.5-SNAPSHOT. I assume this relates to the release work going on, but is >>> there any chance this can be fixed? >>> >>> Thanks >>> Alasdair >>> >>> On 16 October 2011 19:25, Alasdair Nottingham <[email protected]> wrote: >>> >>>> I'm still not having any luck. I've removed my local m2 repo, rebuild >>>> parent and I'm still getting this problem. I guess I could try to do >>>> another >>>> checkout. >>>> >>>> Alasdair >>>> >>>> >>>> On 14 October 2011 16:23, John W Ross <[email protected]> wrote: >>>> >>>>> I suddenly started hitting a similar issue a few moments ago, although I >>>>> did not do an svn update prior to its appearance. >>>>> >>>>> [ERROR] >>>>> Failed to execute goal on project org.apache.aries.subsystem.core: >>>>> Could not resolve dependencies for project >>>>> >>>>> org.apache.aries.subsystem:org.apache.aries.subsystem.core:bundle:0.1-SNAPSHOT: >>>>> >>>>> Failed to collect dependencies for [ >>>>> >>>>> org.apache.aries.subsystem:org.apache.aries.subsystem.api:jar:0.1-SNAPSHOT >>>>> (compile), >>>>> org.apache.aries:org.apache.aries.util:jar:0.4-SNAPSHOT (compile), >>>>> >>>>> >>>>> >>>>> org.apache.aries.application:org.apache.aries.application.api:jar:0.3.1-SNAPSHOT >>>>> (compile), >>>>> >>>>> >>>>> org.apache.aries.application:org.apache.aries.application.utils:jar:0.3.1-SNAPSHOT >>>>> (compile), >>>>> org.eclipse:osgi:jar:3.8.0-SNAPSHOT (provided), >>>>> org.eclipse.equinox:coordinator:jar:1.0.0.v20110314 (compile), >>>>> org.eclipse.equinox:region:jar:1.0.0.v20110506 (compile), >>>>> org.apache.felix:org.apache.felix.utils:jar:1.1.0 (compile), >>>>> org.apache.felix:org.apache.felix.bundlerepository:jar:1.6.4 >>>>> (compile), >>>>> >>>>> >>>>> org.apache.aries.testsupport:org.apache.aries.testsupport.unit:jar:0.4-SNAPSHOT >>>>> (test), >>>>> org.slf4j:slf4j-simple:jar:1.5.11 (test), >>>>> org.slf4j:slf4j-api:jar:1.5.11 (compile), >>>>> junit:junit:jar:4.8.1 (test)]: >>>>> Failed to read artifact descriptor for >>>>> >>>>> org.apache.aries.testsupport:org.apache.aries.testsupport.unit:jar:0.4-SNAPSHOT: >>>>> >>>>> Failure to find org.apache.aries:java5-parent:pom:0.5 in >>>>> http://repo1.maven.org/maven2 was cached in the local repository, >>>>> resolution will not be reattempted until the update interval of central >>>>> has elapsed or updates are forced -> [Help 1] >>>>> >>>>> The key was apparently "Failure to find >>>>> org.apache.aries:java5-parent:pom:0.5". I noticed I did not have a pom >>>>> file within my local m2 repo under org/apache/aries/java5-parent/0.5. I >>>>> did an svn update followed by an mvn clean install within the aries/parent >>>>> directory, which produced the absent pom file. I am now able to >>>>> successfully execute the goal that was previously failing. >>>>> >>>>> ~ John >>>>> >>>>>> >>>>>> Subject >>>>>> >>>>>> Problem building aries >>>>>> >>>>>> Hi, >>>>>> >>>>>> I've just done an svn up and nothing will build. I get the following >>>>>> exception: >>>>>> >>>>>> [INFO] Scanning for projects... >>>>>> [ERROR] The build could not read 4 projects -> [Help 1] >>>>>> [ERROR] >>>>>> [ERROR] The project >>>>>> >>>>> >>>>> org.apache.aries.application:org.apache.aries.application.api:0.3.1-SNAPSHOT >>>>>> (/Users/nottinga/Documents/apache/aries/trunk/application/ >>>>>> application-api/pom.xml) >>>>>> has 1 error >>>>>> [ERROR] Non-resolvable parent POM: Could not find artifact >>>>>> org.apache.aries:java5-parent:pom:0.5-SNAPSHOT and 'parent.relativePath' >>>>>> points at wrong local POM @ line 21, column 13 -> [Help 2] >>>>>> [ERROR] >>>>>> [ERROR] The project >>>>>> >>>>> >>>>> org.apache.aries.application:org.apache.aries.application.utils:0.3.1-SNAPSHOT >>>>>> (/Users/nottinga/Documents/apache/aries/trunk/application/ >>>>>> application-utils/pom.xml) >>>>>> has 1 error >>>>>> [ERROR] Non-resolvable parent POM: Could not find artifact >>>>>> org.apache.aries:java5-parent:pom:0.5-SNAPSHOT and 'parent.relativePath' >>>>>> points at no local POM @ line 21, column 13 -> [Help 2] >>>>>> [ERROR] >>>>>> [ERROR] The project >>>>>> org.apache.aries.application:org.apache.aries.application.modeller: >>>>>> 0.3.1-SNAPSHOT >>>>>> (/Users/nottinga/Documents/apache/aries/trunk/application/ >>>>>> application-modeller/pom.xml) >>>>>> has 1 error >>>>>> [ERROR] Non-resolvable parent POM: Could not find artifact >>>>>> org.apache.aries:java5-parent:pom:0.5-SNAPSHOT and 'parent.relativePath' >>>>>> points at no local POM @ line 21, column 13 -> [Help 2] >>>>>> [ERROR] >>>>>> [ERROR] The project >>>>>> >>>>> >>>>> org.apache.aries.application:application-modeller-standalone:0.3.1-SNAPSHOT >>>>>> (/Users/nottinga/Documents/apache/aries/trunk/application/ >>>>>> application-modeller-standalone/pom.xml) >>>>>> has 1 error >>>>>> [ERROR] Non-resolvable parent POM: Could not find artifact >>>>>> org.apache.aries:java5-parent:pom:0.5-SNAPSHOT and 'parent.relativePath' >>>>>> points at no local POM @ line 21, column 13 -> [Help 2] >>>>>> [ERROR] >>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the >>>>> -e >>>>>> switch. >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >>>>>> [ERROR] >>>>>> [ERROR] For more information about the errors and possible solutions, >>>>> please >>>>>> read the following articles: >>>>>> [ERROR] [Help 1] >>>>>> >>>>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException >>>>>> [ERROR] [Help 2] >>>>>> >>>>> >>>>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException >>>>> >>>>>> >>>>>> does anyone know what the problem might be? >>>>>> >>>>>> maven -version shows this: >>>>>> >>>>>> Apache Maven 3.0.3 (r1075438; 2011-02-28 17:31:09+0000) >>>>>> Maven home: /usr/share/maven >>>>>> Java version: 1.6.0_26, vendor: Apple Inc. >>>>>> Java home: >>>>> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home >>>>>> Default locale: en_US, platform encoding: MacRoman >>>>>> OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac" >>>>>> >>>>>> -- >>>>>> Alasdair Nottingham >>>>>> [email protected] >>>>> >>>>> >>>> >>>> >>>> -- >>>> Alasdair Nottingham >>>> [email protected] >>>> >>> >>> >>> >>> -- >>> Alasdair Nottingham >>> [email protected] >> >> >
