velocity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Glass-Husain (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (VELOCITY-390) add MANIFEST.MF to build
Date Wed, 04 Jan 2006 06:15:00 GMT
     [ http://issues.apache.org/jira/browse/VELOCITY-390?page=all ]
     
Will Glass-Husain resolved VELOCITY-390:
----------------------------------------

    Resolution: Fixed

Added "org.apache" as "Implementation-Vendor-Id".


> 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


Mime
View raw message