[
http://jira.codehaus.org/browse/MOJO-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144635#action_144635
]
Henri Tremblay commented on MOJO-767:
-------------------------------------
You mean vafer was fixed and so the bug doesn't occur anymore? I can't tell if
that's the case on my project since I've quit using minijar but if you say so,
it's ok for me to close the issue.
> minijar:ueberjar RuntimeWrapper are invalid
> -------------------------------------------
>
> Key: MOJO-767
> URL: http://jira.codehaus.org/browse/MOJO-767
> Project: Mojo
> Issue Type: Bug
> Components: minijar
> Reporter: Henri Tremblay
> Priority: Blocker
> Attachments: dependency-fixRuntimeWrapperClassName.txt,
> RuntimeMapper.class
>
>
> The jar created jar by ueber doesn't work at all. At runtime, the
> RuntimeMapper classes are causing ClassFormatError. This is probably coming
> from vafer.dependency.
> The created class is in attachment. From a quick look, one problem seems to
> be the class name. They end with the suffix ".class".
> From there I have a question. Can't we have an option to create a flat having
> everything in the root instead of in subdirectories? That will remove the
> need of any runtime wrapper and would work nicely.
> Out of subject, I also notice that the final jar has no manifest (the initial
> jar has).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
