[jboss-jira] [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
Carlo de Wolf (JIRA)
jira-events at lists.jboss.org
Thu Dec 23 03:28:18 EST 2010
[ https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572151#comment-12572151 ]
Carlo de Wolf commented on JBAS-8754:
-------------------------------------
Abusing a bug is not regression.
I think the app expects one EjbSynchronizations to be present. The ear must be packaged to reflect that.
JavaEE 6 EE.8.5.2 Bullet 4:
Note that the presence of component-declaring annotations in shared artifacts, such as libraries in the library directory and libraries referenced by more than one module through Class-Path references, can have unintended and undesirable
consequences and is not recommended.
> EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
> -------------------------------------------------------------------------------------------------
>
> Key: JBAS-8754
> URL: https://issues.jboss.org/browse/JBAS-8754
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.0.0.CR1
> Reporter: Max Andersen
> Assignee: Shelly McGowan
> Priority: Blocker
>
> As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss Tools seam tooling because it has an entry in its manifest.mf.
> This is a regression and will mean that seam projects (and possibly other ear projects) created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
> (but it will work on all previous AS versions)
> I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list