[ 
https://issues.apache.org/jira/browse/JSPWIKI-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451662#comment-13451662
 ] 

Juan Pablo Santos Rodríguez commented on JSPWIKI-746:
-----------------------------------------------------

Oh, didn't see the Java 6 requirement for Jetty 8, so Jetty 7 should be fine. I 
also ended up with a bunch of Jetty jars, so seems to me that the aggregate jar 
should be a better option.

Regarding selenium and webtests, I've been digging into it. [#1] is the only 
thread I've regarding selenium and [#2] seems to point that the Selenium server 
we're using supports only Firefox 1.4.1 to 2.0.0.*. Probably the same happens 
with IE or Safari. 

So I wouldn't bet that anyone is using them, at least nowadays. As the tests 
can be readed/executed with latest Selenium IDE, I was thinking in going into 
latest Selenium Server (perhaps translating the tests into JUnit). 

Also regarding the tests, they date back from a long time ago, so there's a 
chance that the front-end has evolved while the tests haven't, and there could 
be incompatibilities between them. If that's the case I would drop the tests, 
but not the Selenium support, we could add Selenium tests later on...


rgrds,
jp

[#1]: http://markmail.org/message/ywtaml3kftagqkdt
[#2]: http://www.qaautomation.net/?p=245

                
> Different versions of dependencies available at Central repo
> ------------------------------------------------------------
>
>                 Key: JSPWIKI-746
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-746
>             Project: JSPWiki
>          Issue Type: Sub-task
>    Affects Versions: Graduating, 2.9
>            Reporter: Juan Pablo Santos Rodríguez
>
> some libraries are present at Central, but with different versions: 
> - jrcs-diff-0.2.jar -> The closest match I was able to find is JMeld, a LGPL 
> app which includes the exact classes from jrcs-diff (among many others). 
> There's also a newer version of the library at Central, at [#3] but it 
> includes a package rename. Other than, it seems fine, but this might be the 
> most delicate jar to upgrade.
> - jasper-*-5.5.25.jar [2 files] -> downgrade to 5.5.23? We use them to 
> precompile JSPs, downgrading shouldn't affect us and we could use the version 
> from Central.
> - jetty-* [3 files] -> upgrade to 7.0.0.pre5 (5.1.14 11MB zip downloadable at 
> http://dist.codehaus.org/jetty/jetty-5.1.x/jetty-5.1.14.tgz). Have to locate 
> the use of these jars to see the possible consequences of upgrading (there 
> are earlier versions on Central of jetty-*, except for the case of jetty-jmx, 
> so it seems safer to upgrade all three of them to 7.0.0.pre5)
> - selenium-*-1.0-beta-1 [2 files] -> upgrade them to 1.0-beta-2. Not very 
> sure if this could be done w/o changing code. If that's the case, we could 
> try to upgrade to 1.0.2.

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

Reply via email to