Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #439154 +++ Bug 439154 reminded me we need to update the "product versions" in R4_4_maintenance branch to 4.4.1. This is important in two places, for each "product" in "org.eclipse.platform.releng.tychoeclipsebuilder": 1. Is the product definition itself. Pretty obvious. 2. And for reasons I do not quite recall, this is one of the few places where the "artifact id" in the POM file needs to be updated also to 4.4.1. Related to some thing about the way Tycho computes "version number" for Mac's plist.info or something kind of obscure like that. I bet Thanh remembers (he's the one who told me in Kepler stream).
This is the commit covering all "products" in eclipsetychobuilder, both product definitions, and pom artifact IDs. http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?h=R4_4_maintenance&id=e7465adb24bea1967fa61ea347eaacf52615bdba Thanh, if you could recall the reason why we needed to update the artifact id, or recall enough to search for original bug :) ... that'd be great to document here. But, another question for you. While doing this change, I noticed we do not have a "version number" for the "eclipse-junit-tests" (thought, we did in the distant past, and at some point it was removed). I'm wonder if you recall why? I'm guessing it's related to it being of "type" eclipse-repository instead of a typical "artifact" in the Maven sense? And, wondering if you recall if if was harmful to have one ... or, just not needed? I'm partially asking out of curiosity, but also because our "main" repository does have a version, and am wonder if that can/should be removed too? See http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.tychoeclipsebuilder/eclipse.platform.repository/pom.xml#n22 Thanks,
I made one typo, and corrected it here http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?h=R4_4_maintenance&id=84a5542a5a9921642218e0efa609c4e2b93cb55e And it was a very lucky typo, since that is the place where I documented why we need to update the artifact ID, and documented the original bug 423677 which "explains everything" ... well, at least the questions I asked above. (It has to do with the "metadata" that is written to content.jar or artifacts.jar, so only "shows up" in some circumstances of "update" or "install" ... such as if only Platform was installed, that product version would initially appear correct, but after installing Eclipse SDK on top of it, the product id would then show up as "4.4.0" in some places (but not others). In any case, I think we're set for our first M-build Wednesday morning.
