[jbosstools-issues] [JBoss JIRA] (JBIDE-20313) Multiple versions of Jetty & objectweb.asm in JBDS

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-20313 at 7/20/15 5:58 PM:
-------------------------------------------------------------

{quote}have you seen any issues beyond validation raising a flag for the duplication ? {quote}
Nope, just trying to make Versionwatch turn blue.

I can split this into two issues if we want, but I suspect the simple answer is "just add more exclusion rules for jetty, and remove the old version of asm", which is fast enough to do that two JIRAs seems overkill. #YMMV

Since we have frequently had a divergent version of Jetty in our TP vs. that in Mars, we end up with 2 versions available at install time. In the past it was 9.2.5 (JBIDE-19497) and 9.2.9 (JBIDE-19585); now it's 9.2.9 and 9.2.10. So, I think the best solution here is to set up exclusion rule filtering such that 9.2.x is acceptable & ignored from versionwatch complaining. See also JBIDE-19065



was (Author: nickboldt):
{quote}have you seen any issues beyond validation raising a flag for the duplication ? {quote}
Nope, just trying to make Versionwatch turn blue.

I can split this into two issues if we want, but I suspect the simple answer is "just add more exclusion rules for jetty, and remove the old version of asm", which is fast enough to do that two JIRAs seems overkill. #YMMV

> Multiple versions of Jetty & objectweb.asm in JBDS
> --------------------------------------------------
>
>                 Key: JBIDE-20313
>                 URL: https://issues.jboss.org/browse/JBIDE-20313
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: arquillian, batch, build, docker, qa, target-platform, updatesite
>    Affects Versions: 4.3.0.Beta1, 4.3.0.Beta2, 4.3.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.CR1
>
>
> Versionwatch reports we have two versions of Jetty IUs in JBDS: 9.2.9 and 9.2.10.
> http://download.jboss.org/jbosstools/mars/snapshots/builds/devstudio.versionwatch_master/2015-07-20_11-32-49_B2490_report_detailed_all.html
> http://download.jboss.org/jbosstools/mars/snapshots/builds/devstudio.versionwatch_master/2015-07-20_11-32-49_B2490_report_summary_all.html
> {code}
> org.eclipse.jetty.io_9.2.9.v20150224 and 9.2.10
> org.eclipse.jetty.continuation_9.2.9.v20150224
> org.eclipse.jetty.servlet_9.2.9.v20150224
> org.eclipse.jetty.util_9.2.9.v20150224
> org.eclipse.jetty.server_9.2.9.v20150224
> org.eclipse.jetty.http_9.2.9.v20150224 
> {code}
> These two versions can be seen here:
> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.0.CR1-SNAPSHOT/REPO/plugins/
> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.0.Beta2/REPO/plugins/
> https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.0.Beta1/REPO/plugins/
> Two versions of *org.objectweb.asm* are also included,
> {code}
> org.objectweb.asm_4.0.0.v201302062210 and 5.0.1
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)