[jboss-jira] [JBoss JIRA] Commented: (JBAS-7512) Review "ejb3" module diffs and apply ports as necessary
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Mon Dec 7 10:29:29 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12498621#action_12498621 ]
jaikiran pai commented on JBAS-7512:
------------------------------------
As per our (internal EJB3 team) policy, when we did updated something in Branch_5_x (from which 6.0.0.M1 was released), we also updated the same in AS trunk. So ideally, there shouldn't be porting necessary. However, i did a quick JIRA search for fix version 6.0.0.M1 and component=EJB3 https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&&fixfor=12313214&pid=10030&component=12310663&sorter/field=issuekey&sorter/order=DESC
>From the commit history in those JIRAs, the only ones that probably need porting is JBAS-6327 and JBAS-5464 (this one doesn't have JIRA commit log).
P.S: This again may not be a complete set.
> Review "ejb3" module diffs and apply ports as necessary
> -------------------------------------------------------
>
> Key: JBAS-7512
> URL: https://jira.jboss.org/jira/browse/JBAS-7512
> Project: JBoss Application Server
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: EJB3
> Reporter: Andrew Lee Rubinger
> Assignee: Andrew Lee Rubinger
> Fix For: JBossAS-6.0.0.M2
>
> Attachments: ejb3diffs.patch
>
>
> Ensure trunk is staying in line with 6.0.0.M1
--
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