[jbosstools-issues] [JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-22443:
------------------------------------

Max's suggestion and JBDS-3917 are now the same thing. 

And installing the contents of the TP into an Eclipse platform is something we already do as part of the composite install job, which runs on any TP change or any JBT component republish.

For example... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-composite-install_master/1923/consoleFull shows we install the whole TP plus all of JBT. Here's a snippet from that log:  [^composite.install.test.log.txt] 

So... I'm inclined to close this since we do the same sort of verification, albeit a bit AFTER the TP is built.

> Add to TP build a check that produced TP can be installed in target Eclipse version
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-22443
>                 URL: https://issues.jboss.org/browse/JBIDE-22443
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, target-platform
>            Reporter: Mickael Istria
>             Fix For: 4.5.x
>
>         Attachments: composite.install.test.log.txt
>
>
> Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests.
> This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible.
> Technical notes:
> * Trying to install all IUs from the release train site + our TP seems easier to implement
> * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)