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

Bug 418285

Summary:	define global URL for tycho-eclipserun-plugin
Product:	[Eclipse Project] Platform	Reporter:	David Williams <david_williams>
Component:	Doc	Assignee:	David Williams <david_williams>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, markus.kell.r
Version:	4.3
Target Milestone:	4.3.2
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:	411500
Bug Blocks:

Description David Williams

2013-09-29 19:57:38 EDT

+++ This bug was initially created as a clone of Bug #411500 +++

tycho-eclipserun-plugin
is used in a profile in main parent pom for "API descriptions" 

It is also used for all the "generate JavaDoc" builds in 'common' repository. 

It seems ideally all "tycho-eclipserun-plugin" (in our build) could use the same repo from which to instantiate "eclipse". 

Even if not, likely better to define these URLs in "global" properties, so easier to find and change when required.

Comment 1 David Williams

2013-09-29 20:00:06 EDT

Assuming all goes well in the Luna stream, and there are no objections, I think we should strive for this same consistency and hygiene in the maintenance stream as well. 

We are currently using the "Juno repository" (4.2) to build Java Doc, but using Kepler SR1 to build the api descriptions for Kepler SR2.

Comment 2 Dani Megert

2014-01-07 03:03:30 EST

Next week is RC1, so, if still planned, it's a good time to fix this now.

Comment 3 David Williams

2014-01-14 01:09:39 EST

This is the commit to move the doc bundle from "juno" to use the variable defined in parent pom (which was defined some time ago). 

http://git.eclipse.org/c/platform/eclipse.platform.common.git/commit/?h=R4_3_maintenance&id=721c0e9759399216af84506f5d39844f4c3b846d

And, I also update the parent pom's variable to point to "4.3.1", instead of "4.3". 

http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?h=R4_3_maintenance&id=7ffa7a5b195f2029382d855b50a964545a4f072d

Now my only question is what we used for "api generation" in the 4.3 stream ... I'll have to look around ...

Comment 4 David Williams

2014-01-14 01:18:12 EST

Ok, found it ... 

http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse-platform-parent/pom.xml?h=R4_3_maintenance#n589

We'd already made the change there. 

So, now for SR2 we will use "SR1" to generate the API Descriptions, instead of Kepler SR0 (4.3.1 vs 4.3, respectively) ... as far as I know, this will make no difference ... but, hopefully those that know how to check, will confirm with our Wednesday M build that all it still well.