[jbosstools-issues] [JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features
[
https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-26283:
------------------------------------
Agree that skipping/hiding is bad behaviour.
Re: declaring a bundle as non-payload... How do you do that? Some config in the
plugin's pom or an Eclipse-SomethingSomething in the manifest.mf?
Maybe we just add `lib/*.jar` to
https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml..., so
binaries are ignored from the comparison? Wait, no, that sounds like a bad idea.
We could set
`<sourceReferences><generate>false</generate></sourceReferences>`
[0] for some plugins which are just upstream runtime wrapper plugins, like aesh.runtime
[1]. Does that sound like a reasonable approach?
[0] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
[1]
https://github.com/jbosstools/jbosstools-forge/tree/master/plugins/org.jb...
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)