[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:all-tabpanel ]

Nick Boldt updated JBIDE-22443:
-------------------------------
    Attachment: composite.install.test.log.txt


> 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)