Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 394292

Summary:	[CBI] run the pom updater
Product:	[Eclipse Project] Platform	Reporter:	Paul Webster <pwebster>
Component:	Releng	Assignee:	Paul Webster <pwebster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.2.1
Target Milestone:	4.2.2
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	372792, 393922

Description Paul Webster

2012-11-14 09:53:05 EST

Just before we run the build, we should run the pom file version updater.

Scenario 1:

1. We auto-tag the build
2. We update the pom versions
3. We send a report to the mailing list so components can update their versions

Scenario 2:

1. we update the pom versions
2. we push the updates to the pom files
3. we auto-tag the build after the update.

Comment 1 Paul Webster

2012-11-16 15:43:00 EST

http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?h=R4_2_maintenance&id=ce52b30997e7bc1e7187cec85078c4e6f456ecab

pom-version-updater.sh will add and commit pom changes in the submodules, and then add any poms and submodule commits in the aggregator

PW

Comment 2 Paul Webster

2012-11-20 19:58:38 EST

I've re-worked the pom updater.  It runs after the build input has been tagged and updates the versions, but doesn't check it in.  Uses:

mvn org.eclipse.tycho:tycho-versions-plugin:update-pom 

I need to generate a report for pom files that need to be updated.

PW

Comment 3 Paul Webster

2012-11-23 15:24:22 EST

generates a report with some patch files in buildDir/pom_updates

PW