[
https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-26283:
------------------------------------
{quote}can we get the file in the JAR were the diff has been detected ?{quote}
I gave you an example of a jar that fails the comparison test here:
https://issues.jboss.org/browse/JBIDE-26283?focusedCommentId=13614123&...
And the explanation is ... the manifest.mf differ because the Eclipse-SourceReferences is
different, as the baseline was build BEFORE we moved to parent pom 4.9.0.AM1, and the
latest builds are built AFTER that change. So the single line in the manifest differs. See
the screenshots above.
Baseline and reactor have same fully qualified version, but with
different content in jbosstools-base plugins/features
----------------------------------------------------------------------------------------------------------------------
Key: JBIDE-26283
URL:
https://issues.jboss.org/browse/JBIDE-26283
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.9.0.AM1
Reporter: Josef Kopriva
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.9.0.AM2
Attachments: diff-baseline-with-local-build-commented-timestamps.png,
diff-baseline-with-local-build-sourcereferences-cause-problem.png
Job
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
is red for one week.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)