On 02/06/2012 03:28 AM, Franklin, Matthew B. wrote:
Temporarily changing trunk back to 0.4-incubating until master is released.
Ah, that is for a part my mistake, at least of not having made the
0.8-incubating-SNAPSHOT master-pom available from the SNAPSHOT repositories. I
did bump the master-pom version (to 0.8-incubating-SNAPSHOT) but forgot to also
deploy it.
What we can do though to fix this is add a rave-master-pom/tags/0.8-incubating
job to Hudson (but *without* the deploy on success). That should push this
version into the Hudson local repository making it available for the
rave-project 0.9-incubating-SNAPSHOT (trunk) job, only locally.
No matter what though, this is the one annoying thing about dual releasing both
master pom and project pom at the same time.
There are two ways to solve or improve on this:
a) Move the master-pom (back) in the project, making it a separate module of its
own. This is used by several other projects as well, but the one downside of
this is: you will and can only have one release cycle. If another 'standalone'
module (e.g. addons, extensions, archetypes, whatnot) come into live which can
(and should) have their own release cycle, you'd have to duplicate the
master-pom configuration. As I expect we will/should get such additional
'standalone' modules, I'd not be in favor of this option
b) Release master-pom separately, e.g. independent of project.
Actually that really is its whole point and purpose IMO :)
While within the incubator, the 'overhead' of at least 2x72h waiting time
though, and depending on at least +3 IPMC votes makes this a bit inconvenient
right now, but once Rave graduates it should become a much more trivial thing.
So, unless the PMC has a different opinion on this, I advise to stay with the
current setup.
Ate
On 2/5/12 9:24 PM, "Apache Jenkins Server"<[email protected]>
wrote:
See<https://builds.apache.org/job/rave-project-trunk/412/changes>
Changes:
[mfranklin] [maven-release-plugin] prepare for next development iteration
[mfranklin] [maven-release-plugin] prepare release 0.8-incubating
[mfranklin] Updated CHANGELOG for 0.8-incubating release
------------------------------------------
Started by an SCM change
Started by upstream project "rave-master-pom-trunk" build number 19
Building remotely on ubuntu3
Updating http://svn.apache.org/repos/asf/incubator/rave/trunk
U rave-components/rave-core/pom.xml
U rave-components/rave-commons/pom.xml
U rave-components/rave-web/pom.xml
U rave-components/pom.xml
U rave-portal-dependencies/pom.xml
U rave-shindig/pom.xml
U rave-portal-resources/pom.xml
U CHANGELOG
U rave-providers/rave-opensocial-provider/pom.xml
U rave-providers/rave-w3c-provider/pom.xml
U rave-providers/pom.xml
U pom.xml
U rave-demo-gadgets/pom.xml
U rave-portal/pom.xml
At revision 1240879
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Parsing POMs
Failed to transfer Could not find artifact
org.apache.rave:rave-master:pom:0.8-incubating in spring-milestone
(http://maven.springframework.org/milestone)
Failed to transfer Could not find artifact
org.apache.rave:rave-master:pom:0.8-incubating in central
(http://repo1.maven.org/maven2)
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed:
<https://builds.apache.org/job/rave-project-trunk/ws/trunk> at
hudson.remoting.Channel@3bf2e5c0:ubuntu3
at hudson.FilePath.act(FilePath.java:780)
at hudson.FilePath.act(FilePath.java:766)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.
java:913)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java
:658)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Caused by: hudson.remoting.ProxyException:
hudson.maven.MavenModuleSetBuild$MavenExecutionException:
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact
org.apache.rave:rave-master:pom:0.8-incubating in spring-milestone
(http://maven.springframework.org/milestone) and 'parent.relativePath'
points at wrong local POM @ line 26, column 13
at
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java
:1271)
at
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java
:1048)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2045)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.
java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: hudson.remoting.ProxyException:
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact
org.apache.rave:rave-master:pom:0.8-incubating in spring-milestone
(http://maven.springframework.org/milestone) and 'parent.relativePath'
points at wrong local POM @ line 26, column 13
at
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder
.java:339)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
at
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java
:1221)
... 11 more
Skipping Cobertura coverage report as build was not UNSTABLE or better ...
