[
https://issues.apache.org/jira/browse/VELOCITY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen closed VELOCITY-390.
-------------------------------------------
> add MANIFEST.MF to build
> ------------------------
>
> Key: VELOCITY-390
> URL: https://issues.apache.org/jira/browse/VELOCITY-390
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.5
> Environment: Operating System: other
> Platform: Other
> Reporter: Will Glass-Husain
> Fix For: 1.5
>
> Attachments: build.patch
>
>
> From [EMAIL PROTECTED]:
> build.xml changes:
> manifest.mf file: It is like windows
> secondaryClick/Version tabsheet information where we
> can see version info etc.
> See my webpage zipfile, where you should find
> src/META-INF/MANIFEST.MF file. I believe diff did not
> include it (just realized).
> So to summarize:
> * meaninfull src/META-INF/MANIFEST.MF file added (take
> from zip)
> * updated build.xml to include manifest file when
> jarring a project
> Go ahead and test it in your working copy. Then open
> Velocity-xxx.jar file to Winzip or something and see
> manifest.mf file. I really hope Velocity started to
> use a meaninfull manifest.mf file.
--
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]
