[
https://issues.apache.org/jira/browse/FELIX-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13264488#comment-13264488
]
Bob Ziuchkovski commented on FELIX-3297:
----------------------------------------
I am running into this problem as well, but during *build* time (using
maven-ipojo-plugin v1.9.0-SNAPSHOT). I passed maven 'export
MAVEN_OPTS="-XX:-UseSplitVerifier"', but the build still fails with:
Execution default of goal
org.apache.felix:maven-ipojo-plugin:1.9.0-SNAPSHOT:ipojo-bundle failed:
java.lang.ClassNotFoundException: <MY CLASS>
`
It's not all that critical, as I was mainly testing what would break if I
switched to JDK7 (several other non-ipojo things as well, unfortunately).
However, I wanted to pass along the heads-up.
> iPOJO Manipulator throws ClassNotFoundException
> -----------------------------------------------
>
> Key: FELIX-3297
> URL: https://issues.apache.org/jira/browse/FELIX-3297
> Project: Felix
> Issue Type: Bug
> Components: iPOJO
> Affects Versions: ipojo-manipulator-1.8.2
> Reporter: Clement Escoffier
> Assignee: Clement Escoffier
> Priority: Critical
> Fix For: ipojo-manipulator-1.8.4
>
>
> The new iPOJO manipulator (1.8.2) asks ASM to compute the bytecode frames.
> However, this may require ASM to load classes (dependencies of the
> manipulated class). If this classloading fails, the maniulatoion is aborted
> with a:
> java.lang.RuntimeException: java.lang.ClassNotFoundException: _THE_CLASS_
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
