[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

[Max Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572157#comment-12572157 ] 

Max Andersen commented on JBAS-8754:
------------------------------------

Carlo,

You need to be a bit more informative please since your comment is as confusing as the exception being thrown ;)

Which part of the EAR is causing the problem ?

Is that we put a jar in the manifest classpath the problem ? Why is that a problem - its just a jar.

How is that ever related to what synchronization annotations that are expected on classes ? Causing failure at this point is rather uninformative nor very userfriendly.

Again, if this is what AS 6 will be released with it will not be able to deploy EAR's that have been working fine on AS 5, AS 5.1 (I think even back to AS 4) and if we "fix" this
by removing the classpath entry in the manifest.mf Eclipse "looses" its ability to see what classes to compile against.

I would love to fix that problem too but that is unfortunately not our codebase nor something we could fix within the AS 6 release time.

Thus I would like to understand why we have "regressed" or "become more strict" (depending on your POV) and what we can do about it for AS 6 release time ?





> 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