[jboss-jira] [JBoss JIRA] Resolved: (JBAS-6410) JBoss Security (2.0.2.SP3) serialVersionUID breaks interoperability with external tools (e.g. JBoss Tools)

Tue Jan 27 07:26:44 EST 2009

     [ https://jira.jboss.org/jira/browse/JBAS-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dimitris Andreadis resolved JBAS-6410.
--------------------------------------

    Resolution: Done

I suppose we can close this now?

How come those classes end up in jboss-client.jar?

I've searched through the build files and only jboss jboss-client.jar being created in server/build.xml.

> JBoss Security (2.0.2.SP3) serialVersionUID breaks interoperability with external tools (e.g. JBoss Tools)
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6410
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6410
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-5.0.0.GA
>            Reporter: Saverio Trioni
>            Assignee: Anil Saldhana
>             Fix For: JBossAS-5.0.1.GA, JBossAS-5.1.0.Beta1, JBossAS-6.0.0.Alpha1
>
>
> The current version of deployed jbosssx.jar contains a class with the wrong serialVersionUID (set to 1L instead of default value).
> This prevents a server to deploy and communicate with JBossTools in eclipse.
> The code issue is already taken care of:
> https://jira.jboss.org/jira/browse/SECURITY-341
> and the resolution is due in SP4.
> But it's critical to deliver the updated package within the next point release of the app server.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira