On Jul 16, 2009, at 9:19 AM, Jeanfrancois Arcand wrote:
> Salut,
>
> Igor Minar wrote:
>> hi there,
>> by an unfortunate accident I included in my app grizzly-http-
>> webserver instead of grizzly-http as a maven dependency and by
>> doing that I ran into some issues with grizzly-sendfile. When I
>> finally got to the root of the problem, I realized that grizzly-
>> http-webserver contains outdated classes (I know that they are
>> outdated because they don't contain fix that JFA put in for me in
>> 1.9.15).
>> I don't know how this could have happened since the classes are
>> being included as a part of the maven build, but look at this:
>> $ jar -xf ./lib/grizzly-http-webserver-1.9.15.jar com/sun/grizzly/
>> http/SelectorThreadKeyHandler.class
>> $ mv com/sun/grizzly/http/SelectorThreadKeyHandler.class
>> SelectorThreadKeyHandler.class-webserver
>> $ jar -xf ./lib/grizzly-http-1.9.15.jar com/sun/grizzly/http/
>> SelectorThreadKeyHandler.class
>> $ mv com/sun/grizzly/http/SelectorThreadKeyHandler.class
>> SelectorThreadKeyHandler.class-http
>> $ md5 SelectorThreadKeyHandler.class-*
>> MD5 (SelectorThreadKeyHandler.class-http) =
>> 36823ec9a47eea16e410fd89fec31ce9
>> MD5 (SelectorThreadKeyHandler.class-webserver) =
>> cfe76039740cbb0b71fe11a4a60d8fdb
>> $ ls -l SelectorThreadKeyHandler.class-*
>> -rw-r--r-- 1 me3x staff 3580 May 4 16:52
>> SelectorThreadKeyHandler.class-http
>> -rw-r--r-- 1 me3x staff 3419 May 4 14:35
>> SelectorThreadKeyHandler.class-webserver
>> The classes have different length, content and even timestamp.
>> Strange, isn't it?
>
> GRRRRRR This is again a failure related to Hudson/SVN/Java.net
> issue. Will repromote it.
redeploying the poms won't help, because the artifacts are already
cached all over the place, so I wouldn't even bother.
I just wonder how this could have happened. Supposing that the
artifacts were build only after 1.9.15 was cut, it should not be
possible to end up with a build like this. Unless somehow mvn clean
was not ran before the final build or something, but if you use mvn
release plugin, it runs clean automatically.
What is the current release process?
/i
>
>> Somehow the build got corrupted and an old class was bundled with
>> the grizzly-http-webserver module.
>
> Thanks!!
>
> -- Jeanfrancois
>
>> /i
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>