You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Werner Punz (JIRA)" <de...@myfaces.apache.org> on 2010/03/01 20:26:05 UTC
[jira] Created: (EXTSCRIPT-75) Add asm package relocation
Add asm package relocation
--------------------------
Key: EXTSCRIPT-75
URL: https://issues.apache.org/jira/browse/EXTSCRIPT-75
Project: MyFaces Extensions Scripting
Issue Type: Improvement
Reporter: Werner Punz
Assignee: Werner Punz
We use ASM, we cannot get rid of it since our dependency scan relies on it, to get rid of packaging conflicts probably introduced by other parts of the system we have to relocate asm in the build process via the maven shade plugin: http://maven.apache.org/plugins/maven-shade-plugin/ or via jarjar http://code.google.com/p/jarjar/
One way or the other the com.objectweb.asm hierarchy has to be mapped into org.apache.myfaces.scripting.com.objectweb.asm package, to avoid any namespace collisions with other projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTSCRIPT-75) Add asm package relocation
Posted by "Werner Punz (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/EXTSCRIPT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Werner Punz resolved EXTSCRIPT-75.
----------------------------------
Resolution: Fixed
> Add asm package relocation
> --------------------------
>
> Key: EXTSCRIPT-75
> URL: https://issues.apache.org/jira/browse/EXTSCRIPT-75
> Project: MyFaces Extensions Scripting
> Issue Type: Improvement
> Reporter: Werner Punz
> Assignee: Werner Punz
>
> We use ASM, we cannot get rid of it since our dependency scan relies on it, to get rid of packaging conflicts probably introduced by other parts of the system we have to relocate asm in the build process via the maven shade plugin: http://maven.apache.org/plugins/maven-shade-plugin/ or via jarjar http://code.google.com/p/jarjar/
> One way or the other the com.objectweb.asm hierarchy has to be mapped into org.apache.myfaces.scripting.com.objectweb.asm package, to avoid any namespace collisions with other projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (EXTSCRIPT-75) Add asm package relocation
Posted by "Werner Punz (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/EXTSCRIPT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840089#action_12840089 ]
Werner Punz commented on EXTSCRIPT-75:
--------------------------------------
Done, the maven shader plugin is a joy to work with, does all out of the box what I needed to get asm into a repackaged namespace.
ASM now is in its own packaging hierarchy in the final binaries.
> Add asm package relocation
> --------------------------
>
> Key: EXTSCRIPT-75
> URL: https://issues.apache.org/jira/browse/EXTSCRIPT-75
> Project: MyFaces Extensions Scripting
> Issue Type: Improvement
> Reporter: Werner Punz
> Assignee: Werner Punz
>
> We use ASM, we cannot get rid of it since our dependency scan relies on it, to get rid of packaging conflicts probably introduced by other parts of the system we have to relocate asm in the build process via the maven shade plugin: http://maven.apache.org/plugins/maven-shade-plugin/ or via jarjar http://code.google.com/p/jarjar/
> One way or the other the com.objectweb.asm hierarchy has to be mapped into org.apache.myfaces.scripting.com.objectweb.asm package, to avoid any namespace collisions with other projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.