You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Pascal Grange (JIRA)" <ji...@apache.org> on 2005/12/14 18:02:46 UTC
[jira] Reopened: (VELOCITY-390) add MANIFEST.MF to build
[ http://issues.apache.org/jira/browse/VELOCITY-390?page=all ]
Pascal Grange reopened VELOCITY-390:
------------------------------------
An entry "Implementation-Vendor-Id" is also missing in the manifest file and should be added.
> add MANIFEST.MF to build
> ------------------------
>
> Key: VELOCITY-390
> URL: http://issues.apache.org/jira/browse/VELOCITY-390
> Project: Velocity
> Type: Bug
> Components: Build
> Versions: 1.5
> Environment: Operating System: other
> Platform: Other
> Reporter: Will Glass-Husain
> Fix For: 1.5
> Attachments: build.patch
>
> From mailmur@yahoo.com:
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org