[
https://issues.apache.org/jira/browse/VELOCITY-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928689#action_12928689
]
Tamas Cserveny edited comment on VELOCITY-694 at 11/5/10 1:26 PM:
------------------------------------------------------------------
I think some of the imports should be marked as optional.
";resolution:=optional"
Currently they are all needed even if no XML support and using eg. JDK14
logging.
com.werken.xpath
org.apache.commons.logging
org.apache.log
org.apache.log.format
org.apache.log.output.io
org.apache.log4j,
org.apache.oro.text.perl
org.apache.tools.ant
org.apache.tools.ant.taskdefs
org.jdom
org.jdom.input
org.jdom.output
org.xml.sax
I would suggest using maven-bundle-plugin(bnd) version 1.4.3 to generate the
manifest, which can run with JDK14.
was (Author: smil):
I think some of the imports should be marked as optional.
";resolution:=optional"
Currently they are all needed even if no XML support and using eg. JDK14
logging.
com.werken.xpath
org.apache.commons.logging
org.apache.log
org.apache.log.format
org.apache.log.output.io
org.apache.log4j,
org.apache.oro.text.perl
org.apache.tools.ant
org.apache.tools.ant.taskdefs
org.jdom
org.jdom.input
org.jdom.output
org.xml.sax
I would suggest using maven-bundle-plugin(bnd) which can run with JDK14 as far
as I know.
> Make Velocity OSGi-ready
> ------------------------
>
> Key: VELOCITY-694
> URL: https://issues.apache.org/jira/browse/VELOCITY-694
> Project: Velocity
> Issue Type: Wish
> Affects Versions: 1.6.1
> Reporter: Stevo Slavic
> Fix For: 1.7, 2.0
>
> Attachments: velocity-dep.jar
>
>
> Velocity jar should be OSGi-ready with all necessary headers in MANIFEST.MF
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
