[jboss-jira] [JBoss JIRA] Updated: (JBAS-7500) Synch 6.0.0.M1 changes with trunk

Brian Stansberry (JIRA) jira-events at lists.jboss.org
Thu Dec 10 15:58:29 EST 2009


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

Brian Stansberry updated JBAS-7500:
-----------------------------------

    Attachment: jmx.diff


To check the M1 j2se, jmx and mbeans modules I combined the contents of the src/main folders of those projects into one directory, and then did the same with the contents of all the modules in the externalized JBJMX project. I then did a diff, which is attached as jmx.diff.

Reviewing the diff file, it looks ok. There are a lot of differences, but 95%+ are generics in JBJMX or comments. I only saw only one significant chunk of code in M1 that's not in JBJMX, in the acquire() method of of RepositoryClassLoader. But svn log shows no changes in that file since Branch_5_x was created, so I assume the code was removed in JBJMX, i.e. not a missing addition.

There are some entire file differences; i.e. files in M1 or JBJMX/trunk but not in the other. I will attach a JMX-only-in.txt which lists these. I tend to doubt that Branch_5_x had entire files added/removed w/o doing the same on JBJMX, so I'm not concerned about these; others more familiar are welcome to take a look.

> Synch 6.0.0.M1 changes with trunk
> ---------------------------------
>
>                 Key: JBAS-7500
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7500
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Other
>            Reporter: Dimitris Andreadis
>            Assignee: Brian Stansberry
>            Priority: Blocker
>             Fix For: JBossAS-6.0.0.M2
>
>         Attachments: JMX-only-in.txt, jmx.diff, testsuite.diff.zip, trunk_vs_M1.zip
>
>
> Create a parent task to track work needed to synch changes from the old Branch_5_x (now 6_0_0_M1 tag) to trunk (M2).
> http://www.jboss.org/community/wiki/CodeDifferencesbetweenAStrunkand600M1tag
> Modules Already Reviewed (Please keep alphabetical)
> -------------------------------------
> adminclient - bstansberry (needs to be ported -- JBAS-7540)
> aspects - dmlloyd
> client - bstansberry (reviewed pom and created subtask)
> cluster - bstansberry
> component-matrix - bstansberry (reviewed pom and created subtasks for things needing porting)
> connector - jesper.pedersen
> console - dmlloyd
> deployment - bstansberry
> hibernate-int - bstansberry
> iiop - dimitris
> jboss-as-jmx-remoting - dmlloyd
> jboss-as-remoting - dmlloyd
> jmx-remoting - dmlloyd
> main - dmlloyd
> management - emuckenhuber
> messaging - dmlloyd
> profileservice - emuckenhuber
> security - sguilhen
> server - bstansberry -- reviewed and subtasks created for everything needing porting
> sprint-int - ales confirmed it became the snowdrop project
> system - emuckenhuber (missing changes related to JBAS-7505)
> tomcat - remy & bstansberry
> varia - dandreadis/bstansberry
> webservices - bstansberry
> Modules that need reviewing
> ---------------------------------------
> ejb3 (see JBAS7512)
> system-jmx (alesj - I'll review this one)
> Modules missing
> ------------------------
> j2se
> jmx
> mbeans

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

        



More information about the jboss-jira mailing list