ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 47446] Manifest.MF when generated programmatically, generates un-usable Class-Path attribute.
Date Mon, 29 Jun 2009 09:49:13 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=47446


Stefan Bodewig <bodewig@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Stefan Bodewig <bodewig@apache.org>  2009-06-29 02:49:12 PST ---
Garima, 

you've already been told that the classpath entry inside the MANIFEST.MF is
correct on the mailing list - this is what the specification of the manifest
format says: no lines longer than 72 chars (including newline) with
continuation lines starting with a space.

If you classpath doesn't work it is *not* because of the formatting of the
classpath entry - unless the code reading the manifest was in violation of the
spec, that is.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message