[jbosstools-issues] [JBoss JIRA] (JBIDE-17025) Patching EAP 6.2 breaks classpath jar files

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-17025 at 4/11/14 11:41 AM:
--------------------------------------------------------------

My understanding from the discussion on the PM call yesterday was that the solution was:

a) instead of breaking /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP2-redhat-1.jar and installing new file /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP3-redhat-1.jar, you would instead:

{code}
# rename new SP3 jar to old SP2 jar's name, replacing old SP2 jar
mv -f /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP3-redhat-1.jar \
      /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP2-redhat-1.jar
{code}
                
      was (Author: nickboldt):
    My understanding from the discussion on the PM call yesterday was that the solution was:

a) instead of breaking /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP2-redhat-1.jar and installing new file /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP3-redhat-1.jar, you would instead:

{code}
# rename new SP3 jar to old SP2 jar's name, replacing old SP2 jar
mv -f /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP3-redhat-1.jar \
         /home/mmusaji/JBoss/jboss-eap-6.2.1/modules/system/layers/base/org/picketbox/main/picketbox-4.0.19.SP2-redhat-1.jar
{code}
                  
> Patching EAP 6.2 breaks classpath jar files
> -------------------------------------------
>
>                 Key: JBIDE-17025
>                 URL: https://issues.jboss.org/browse/JBIDE-17025
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.1.2.Final
>         Environment: Windows 7, Kepler SR2
>            Reporter: Jesper Skov
>            Priority: Blocker
>             Fix For: 4.2.0.Beta2
>
>
> Using the JBoss CLI command 'patch apply .../eap-6.2.2.zip' breaks some of the module jars (the files become invalid ZIP-archives).
> This is apparently done as a way to mark the modules off-limits for the container, while still allowing roll-back if necessary.
> See https://access.redhat.com/site/discussions/726623
> Unfortunately, Eclipse includes these jars in the JBossTools-defined classpath. When scanned, these will be found corrupt, and the project classpath marked as broken.
> On my installation, the first few files to trigger this problem are: 
> * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar
> * modules/system/layers/base/javax/el/api/main/jboss-el-api_2.2_spec-1.0.2.Final-redhat-1.jar
> I guess it might be possible to adjust the server definition's Default Classpath Entries in Eclipse preferences. But I decided to just copy the original EAP 6.2 files on top of the runtime and get on with work...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira