[jbosstools-issues] [JBoss JIRA] (JBIDE-20674) Write automated tests to check consistency of Jetty between JBT & Eclipse

[Konstantin Marmalyukov (JIRA)]

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

Konstantin Marmalyukov commented on JBIDE-20674:
------------------------------------------------

We don't need a test for target platform content - we already do actually the same for cordovasim - we check jetty bundles availability and compare version with the one we use. I miss this tests failure because I was not subscribe to aerogear builds. Now I fix it and will be on pulse. Cc [~xcoulon]

Regarding tests for Eclipse Help compatibility - the problem is that API for help only provide me an option to open Help window - I can't at least detect which port is used by jetty server which help uses. This issue needs deeper investigation and become not critical since it looks like we have to follow Eclipse with jetty versions.

> Write automated tests to check consistency of Jetty between JBT & Eclipse
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-20674
>                 URL: https://issues.jboss.org/browse/JBIDE-20674
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: browsersim, livereload, target-platform
>            Reporter: Mickael Istria
>            Assignee: Konstantin Marmalyukov
>             Fix For: 4.4.0.Alpha1
>
>
> Since it appears Jetty is somehow a "weak" component (ie APIs are often broken and versions are not well managed), we often have to enforce a specific version of Jetty for our JBoss Tools bundles. However, it happens that the version used by JBoss Tools component isn't the same as the one shipped by some other Eclipse components.
> We need to make sure that enforcing a version of Jetty doesn't break those Eclipse components. The best way to achieve that is to write a test trying to validate the correct work of any Eclipse component we're aware it's using Jetty, as part of the same test plugin that validates the JBoss Tools components.
> The list of identified Eclipse component using Jetty so far:
> * Equinox (but I don't know how it uses Jetty, so neither how to make sure it's working well)
> * Eclipse Help (test coulod load the help and make sure it shows content and not a 302 or 500 HTTP error)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)