[
https://issues.apache.org/jira/browse/VELOCITY-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852598#action_12852598
]
Nathan Bubna commented on VELOCITY-694:
---------------------------------------
Shame on me. Didn't actually test release task, for which we still require
JDK1.4, while Bundlor requires 1.5. Here's the options i see:
- Build non-OSGi-ready release for 1.7 and leave people to build their own
manifests.
- Bump the target JDK to 1.5 (No, building with 1.5 target 1.4 is not an option
due to StringBuffer.append mess)
- "Manually" build an OSGi-ready manifest with the jar tasks manifest sub-task.
This means sticking a massive property like the one above into
build.properties. But that would only be for 1.7. In 2.0, we'll be back to
the Bundlor manifest.
I'm inclined to go with option 3.
> 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]
