]
Paul Leacu resolved JBTIS-113.
------------------------------
Resolution: Out of Date
Consider - the Integration Stack is designed to use a fixed target platform and a fixed
JBT core. Components like Teiid can add to the "collective" and update the
target dependencies if need be. The component leads are then free to bump the JBTIS
version. The IS build establishes compatibility at a package level. There's really
no need for a "nightly" of the IS. The Jenkins jobs are clear and allow for
some variability (other variables like target dependency must be done in the JBTIS target
platform).
See
Improve ability to configure dependent hudson jobs and provide
accessable documentation
---------------------------------------------------------------------------------------
Key: JBTIS-113
URL:
https://issues.jboss.org/browse/JBTIS-113
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Barry LaFond
Assignee: Paul Leacu
SOA decoupling has elevated the need to have more configurable control over upstream and
downstream dependencies.
Notes from Nick:
* a number of jobs are now set to build only when triggered by upstream, but SOA stuff is
not as well handled
* ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should
use Parameterized Trigger to cause downstream to fire
* you can also ensure that you're building against a stable aggregate using an
override like the one I've set up for SOA Tooling aggregate...
* in your maven invocation, under Properties, you can do this: # use latest upstream
nightly Core update site instead of "wild components" in the composite staging
site
jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
* that way you pull from the aggregate (updates weekly) instead of the composite (updates
every time a component respins)
* means if you depended on something like
tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry
about getting incompatible pieces
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: