Community
Participate
Working Groups
When testing our M7 API artefacts I've noticed that we should also contribute the source-feature for the Client API core.
Should be fixed with http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=0d0a784bffebecc47b0500fc694c5ddf2175675d
This has been tested by SSt for JUB-1234
The latest repository reports indicate that: 1. the contributed source feature JAR is unsigned - see [1] 2. a couple of source bundles are missing the corresponding legal (about.html) file inclusion - see [2] We should address both of these issues until Mars RC3 this week. [1] https://hudson.eclipse.org/simrel/job/simrel.mars.runaggregator.CLEAN_BUILD/lastSuccessfulBuild/artifact/aggregation/final/buildInfo/reporeports/reports/verifydiroutput/unsigned8.txt [2] https://hudson.eclipse.org/simrel/job/simrel.mars.runaggregator.CLEAN_BUILD/lastSuccessfulBuild/artifact/aggregation/final/buildInfo/reporeports/reports/layoutCheck.txt
The resolving of these issues has also been recommended on cross-project-issues dev mailing list.
Missing about.html file inclusion has been fixed on master: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=cec8201c3f3409865eb63a15936cf03ba192a582 and on mars: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?h=mars&id=fd7f6a95309cfbd628ffb92a24e280ae8484510e
We've discovered that this feature isn't currently being signed. We are using a combination of different tycho plugins to generate the feature - and the signing doesn't seem to work for this transiently created source feature jar. Markus, our release engineer, is looking into this in the hope that we can fix it for RC3. In case that doesn't work, what would you recommend as the next steps? Would it be possible to get an exception for it? We'd prefer to leave it in if possible.
I've found a pretty good hint on cbi-dev - see [1] - and will give it a try. [1] http://dev.eclipse.org/mhonarc/lists/cbi-dev/msg00867.html
I doubt this was intended to be assigned to me, was it? Perhaps add me to CC? It is not currently showing up as unsigned ... is that because you removed it? (Would be best to be present, and would be best to be signed ... so ... hope your releng can fix it). Let me know if you had a more specific question for me.
Thanks for the update David! @DW: No, we haven't done anything so far (even not removed our artefact - see [1]) addressing this signing problems (for mars) and though: it's not listed there [anymore] (though I can confirm that the artefact we're contributing not signed). Maybe there is a problem with the report at the moment? As bug 396445 also points out the (same) solution I'm currently giving it a try on master: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=cd7fca84136fc22448e9cf0e8673ea47c3e58f8e And it's already part of Jubula nightly build #2455 - I'm pretty sure this will resolve it. As soon as I can confirm that I'll also apply it to our mars branch. [1] http://download.eclipse.org/jubula/milestones/mars-rc2/features/org.eclipse.jubula.feature.api.core.source_3.1.0.201505270711.jar
I've also cherry-picked this to mars: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?h=mars&id=10e661cfc063ceb195dcf3e9361a4aade7ac638d
What's the exact name of the source feature that is (was) unsigned? I just want to investigate why latest reports do not report it.
@DW: Thanks for investigating this! It's the artefact referenced as [1] in comment 9 and currently listed at position 663. in the "Feature names report" - see [a]: org.eclipse.jubula.feature.api.core.source.feature.group 3.1.0.201505270711 Jubula Functional Testing - API Core Developer Resources [a] https://hudson.eclipse.org/simrel/job/simrel.mars.runaggregator.CLEAN_BUILD/lastSuccessfulBuild/artifact/aggregation/final/buildInfo/reporeports/reports/featureNames.html
I can confirm that the jar is now signed.
