[
https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-26283:
----------------------------------------
An error like this should not be worked around nor skipped and pushed back to GA imo.
Doing this adds a serious amount of technical debt and the errors given by the comparator
can result in major bugs if not taken care of properly.
The comparator here tells clearly which bundles something changed, it's necessary to
find out what it is and what changed.
For example, comment from [~jeffmaury] about a nested jar changing in size while keeping
same name and version should be investigated as it's a suspicious behavior. If this is
acceptable, then version of the bundle should be bumped to reflect that it's indeed
different content as before.
About the Eclipse-SourceReference being different, it's a bit strange that this
changed and nothing else. It could be a non-payload file that was modified. In such case,
I think Tycho offers the control to declare such non-payload file to the generation of
Eclipse-SourceReferences so it would allow to stick to the exact same bundle.
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.
More info:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)