[jbosstools-issues] [JBoss JIRA] (JBTIS-15) set up automated install tests to verify JBTIS 4 can be installed against the latest JBT 4.0.x and the latest Eclipse 4.2.x

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12753761#comment-12753761 ] 

Nick Boldt commented on JBTIS-15:
---------------------------------

Looks like installation of JBTIS 4 onto JBDS 6 *WILL FAIL* due to missing org.jboss.tools.birt.feature, because BIRT is not included in JBDS:

{code}
  [p2.dir] Command-line arguments:  -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product -application org.eclipse.equinox.p2.director -clean -consoleLog -flavor tooling -profile epp.package.jee -destination /mnt/hudson_workspace/workspace/jtis-4.0_stable_branch.director-install-tests.eclipse42x.jbt40x.matrix/JBTIS_Site/download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate/all/repo/JBT_Site/www.qa.jboss.com/binaries/RHDS/updates/stable/6.0.0.GA.core/eclipseBundleVersion/juno.R/label/RHEL/eclipse -bundlepool /mnt/hudson_workspace/workspace/jtis-4.0_stable_branch.director-install-tests.eclipse42x.jbt40x.matrix/JBTIS_Site/download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate/all/repo/JBT_Site/www.qa.jboss.com/binaries/RHDS/updates/stable/6.0.0.GA.core/eclipseBundleVersion/juno.R/label/RHEL/eclipse -installIU org.jboss.ide.eclipse.archives.feature.feature.group,org.jboss.ide.eclipse.as.feature.feature.group,org.jboss.ide.eclipse.freemarker.feature.feature.group,org.jboss.tools.birt.feature.feature.group,org.jboss.tools.cdi.deltaspike.feature.feature.group,org.jboss.tools.cdi.feature.feature.group,org.jboss.tools.cdi.seam.feature.feature.group,org.jboss.tools.central.feature.feature.group,org.jboss.tools.central.themes.feature.feature.group,org.jboss.tools.common.core.feature.feature.group,org.jboss.tools.common.feature.feature.group,org.jboss.tools.common.jdt.feature.feature.group,org.jboss.tools.common.mylyn.feature.feature.group,org.jboss.tools.common.text.ext.feature.feature.group,org.jboss.tools.common.ui.feature.feature.group,org.jboss.tools.common.verification.feature.feature.group,org.jboss.tools.community.central.feature.feature.group,org.jboss.tools.community.project.examples.feature.feature.group,org.jboss.tools.forge.feature.feature.group,org.jboss.tools.gwt.feature.feature.group,org.jboss.tools.jmx.feature.feature.group,org.jboss.tools.jsf.feature.feature.group,org.jboss.tools.jst.feature.feature.group,org.jboss.tools.maven.cdi.feature.feature.group,org.jboss.tools.maven.feature.feature.group,org.jboss.tools.maven.gwt.feature.feature.group,org.jboss.tools.maven.hibernate.feature.feature.group,org.jboss.tools.maven.jaxrs.feature.feature.group,org.jboss.tools.maven.jbosspackaging.feature.feature.group,org.jboss.tools.maven.jdt.feature.feature.group,org.jboss.tools.maven.jpa.feature.feature.group,org.jboss.tools.maven.jsf.feature.feature.group,org.jboss.tools.maven.portlet.feature.feature.group,org.jboss.tools.maven.profiles.feature.feature.group,org.jboss.tools.maven.project.examples.feature.feature.group,org.jboss.tools.maven.seam.feature.feature.group,org.jboss.tools.maven.sourcelookup.feature.feature.group,org.jboss.tools.openshift.egit.integration.feature.feature.group,org.jboss.tools.openshift.express.feature.feature.group,org.jboss.tools.portlet.feature.feature.group,org.jboss.tools.project.examples.feature.feature.group,org.jboss.tools.richfaces.feature.feature.group,org.jboss.tools.runtime.core.feature.feature.group,org.jboss.tools.runtime.seam.detector.feature.feature.group,org.jboss.tools.seam.feature.feature.group,org.jboss.tools.struts.feature.feature.group,org.jboss.tools.usage.feature.feature.group,org.jboss.tools.vpe.browsersim.feature.feature.group,org.jboss.tools.vpe.feature.feature.group,org.jboss.tools.ws.feature.feature.group,org.jboss.tools.ws.jaxrs.feature.feature.group,org.jboss.tools.xulrunner.feature.feature.group,org.hibernate.eclipse.feature.feature.group,org.mozilla.xulrunner.feature.feature.group -metadataRepository http://www.qa.jboss.com/binaries/RHDS/updates/stable/6.0.0.GA.core/,http://download.jboss.org/jbosstools/updates/juno/ -artifactRepository http://www.qa.jboss.com/binaries/RHDS/updates/stable/6.0.0.GA.core/,http://download.jboss.org/jbosstools/updates/juno/,file:/mnt/hudson_workspace/workspace/jtis-4.0_stable_branch.director-install-tests.eclipse42x.jbt40x.matrix/JBTIS_Site/download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate/all/repo/JBT_Site/www.qa.jboss.com/binaries/RHDS/updates/stable/6.0.0.GA.core/eclipseBundleVersion/juno.R/label/RHEL/eclipse -profileProperties org.eclipse.update.install.features=true
   [p2.dir] 
   [p2.dir] The installable unit org.jboss.tools.birt.feature.feature.group has not been found.
   [p2.dir] Application failed
{code}

Does anything in JBTIS actually depend on BIRT?
                
> set up automated install tests to verify JBTIS 4 can be installed against the latest JBT 4.0.x and the latest Eclipse 4.2.x
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-15
>                 URL: https://issues.jboss.org/browse/JBTIS-15
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: distribution, releng, target-platform
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> Job must perform the following install steps:
> a) unpack eclipse
> b) install JBT (specific version)
> c) install JBTIS (specific version)
> That will ensure that:
> * JBTIS can be installed against a specific older version of JBT AND
> * JBTIS can also magically update the version of JBT installed to the latest at the same time.
> Need a matrix job to handle a few (12) permutations:
> {code}
> Eclipse {4.2.0,4.2.1,4.2.2} x JBT {4.0.0,4.0.1} x JBTIS {4.0.0}
> Eclipse {4.2.0,4.2.1,4.2.2} x JBDS {6.0.0,6.0.1} x JBTIS {4.0.0}
> {code}

--
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: http://www.atlassian.com/software/jira