JBTIS is where fully resolvable dependencies are - can't it just use the jbtis public url ? otherwise you would just need to create your own site which is a composite of the teiid component site and with p2 references to the JBTIS target platform. /max On Tue, Aug 06, 2013 at 01:35:30PM +0100, Paul Richardson wrote: > Hi, > > With testing the latest Teiid Designer nightlies, we have come across the following constaint on the > installation: > > Missing requirement: Designer Datatools Plug-in 8.2.0.Nightly-v20130730-1414-B2372 > (org.teiid.designer.datatools 8.2.0.Nightly-v20130730-1414-B2372) requires 'bundle > org.codehaus.jackson.core [1.6.0,2.0.0)' but it could not be found > > Now I removed jackson.core from Designer's codebase and had it added to JBT-IS, since it is > available in JBT's Eclipse Orbit. Thus, jenkins builds the nightlies successfully. > > However, installing a TD-nightly is only possible with adding the Eclipse Orbit site to available > update sites. When we release Designer 8.2 in a couple of weeks, I would like to avoid this becoming > an issue for users so is there something that can be done? I am not sure what ... > > Cheers > > PGR > > -- > Paul Richardson > > * p.g.richardson(a)redhat.com > * pgrichardson(a)linux.com > * mob: +44 (0)9780 869490 > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

> Hey Max, > > This is where my confusion lies ... > > I included both [1], [2] and [3] in my eclipse update sites and the error > still occurs. It seems > these only offer the SOA tooling features and plugins and not those > dependency plugins used in the > integration-stack-base.target [4], which was used to build JBT-IS. > > I kinda would have expected the JBT-IS to offer its dependency plugins as > well in a composite so it > served as a single-stop-shop for installing any of the SOA tools it offers. This is correct. If those dependencies are not resolving, we need to correct the JBTIS update site. > > Am I missing something? Certainly not sure we want to be created another > component site, do we? > > PGR > > [1] > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > [2] > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > [3] > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > [4] > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

JBTIS is where fully resolvable dependencies are - can't it just use the jbtis public url ? otherwise you would just need to create your own site which is a composite of the teiid component site and with p2 references to the JBTIS target platform.

/max On Tue, Aug 06, 2013 at 01:35:30PM +0100, Paul Richardson wrote: >Hi, > >With testing the latest Teiid Designer nightlies, we have come across the >following constaint on the >installation: > >Missing requirement: Designer Datatools Plug-in >8.2.0.Nightly-v20130730-1414-B2372 >(org.teiid.designer.datatools 8.2.0.Nightly-v20130730-1414-B2372) requires >'bundle >org.codehaus.jackson.core [1.6.0,2.0.0)' but it could not be found > >Now I removed jackson.core from Designer's codebase and had it added to >JBT-IS, since it is >available in JBT's Eclipse Orbit. Thus, jenkins builds the nightlies >successfully. > >However, installing a TD-nightly is only possible with adding the Eclipse >Orbit site to available >update sites. When we release Designer 8.2 in a couple of weeks, I would >like to avoid this becoming >an issue for users so is there something that can be done? I am not sure >what ... > >Cheers > >PGR > >-- >Paul Richardson > > * p.g.richardson(a)redhat.com > * pgrichardson(a)linux.com > * mob: +44 (0)9780 869490 > >_______________________________________________ >jbosstools-dev mailing list >jbosstools-dev(a)lists.jboss.org >https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

>Generally, users of specific components (e.g. TEIID), should install the >latest "release" using the JBTIS site. If those same users want to stay up >to date with the latest nightly or development version of that component, >they should also add the update site for that specific component. This >should work for all cases except where the nightly or dev version changes >its dependencies in such a way that they cannot be fulfilled by JBTIS. Yeah, I would prefer to avoid creating too many separate individual sites cross-referencing each other causing a nice mess of p2 sites for users.

For bleeding edge users its fine, but for our "normal" users which tend to use more than just *one* of our plugins having actual release of JBTIS is crucial since it allow us to hand out an actual stable url that has a much less likelyhood of problems. p.s. one could argue that bleeding edge users should be okey adding <teiid-component-site> + JBTIS-TP site for their bleeding edge testing.

Paul, can't that "skinny" tp you did for jbdsIs be applied here ?

/max (sent from my phone) On 08/08/2013, at 21.26, Rob Cernich <rcernich(a)redhat.com&gt; wrote: >>> Generally, users of specific components (e.g. TEIID), should install the >>> latest "release" using the JBTIS site. If those same users want to stay >>> up >>> to date with the latest nightly or development version of that component, >>> they should also add the update site for that specific component. This >>> should work for all cases except where the nightly or dev version changes >>> its dependencies in such a way that they cannot be fulfilled by JBTIS. >> >> Yeah, I would prefer to avoid creating too many separate individual sites >> cross-referencing each other causing a nice mess of p2 sites for users. > > Paul, given that, can we update JBTIS to create a p2 site for the target > platform that can be published and referenced by the aggregate? > Referencing the target platform site would take the place of most of the > associate sites listed in the site pom. I suspect you would publish it up > to something like .../integration-stack/target-platform/4.1.1. We would > need to ensure the target platform is tagged, published and promoted in > the same way the aggregate is. Keep in mind, we only need to publish the > target platform site when the integration-stack-base.target file changes. > (Ping me on IRC if you want to discuss in more detail.) > >> >> For bleeding edge users its fine, but for our "normal" users which tend to >> use more than just *one* of our plugins having actual release of JBTIS is >> crucial since it allow us to hand out an actual stable url that has a much >> less likelyhood of problems. >> >> p.s. one could argue that bleeding edge users should be okey adding >> <teiid-component-site> + JBTIS-TP site for their bleeding edge testing. > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev