Re: Commons-Attributes 2.2 Corrupted Manifest
I already asked for a 2.2.1 release to remove those -Extension in manifest, as they break running my app under tomcat 4. Those libs are only required by the compiler jar, not the api (runtime) jar, tho they can be removed from the manifest. This manifest is hand-writen and is included during the ant build. Building with maven doesn't include it. @see http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg88665.html Nico. 2007/3/6, Jörg Schaible [EMAIL PROTECTED]: Henri Yandell wrote on Monday, March 05, 2007 9:45 PM: On 3/5/07, Leo Sutic [EMAIL PROTECTED] wrote: On 3/5/07, Jörg Schaible [EMAIL PROTECTED] wrote: Leo Sutic wrote: Hi all, the Commons-Attributes 2.2 jars have corrupted manifest.mf files. This is apparently causing a bit of problems for users. The issue is in the extension properties: ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant-1.5. jar qdox-Extension-Name: qdox qdox-Implementation-Version: 1.5 qdox-Implementation-URL: http://www.ibiblio.org/maven/qdox/jars/qdox-1 .5.jar As you can see, there are spaces and cr/lfs in the URLs. This causes maven 2 etc. to fail. AFAICS the manifest is OK according the spec (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Name-V alue%20pairs%20and%20Sections) by respecting the line length of 72 bytes. Longer lines violate the manifest ... Heh. Thanks - I had no idea. Well, that explains where those line breaks came from. I guess the ball is in the other court then. I'm aiming to make a 2.2.1 release at some point for this - but low energy towards it currently. The above is good to know, said manifest was generated by a Sun JDK (1.4 I presume) on a Linux box, so nothing out of the ordinary. Is there an issue raised with Maven for this? Don't think so. What exactly is the reported problem? - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Commons-Attributes 2.2 Corrupted Manifest
Hi Nico, nicolas de loof wrote on Tuesday, March 06, 2007 10:00 AM: I already asked for a 2.2.1 release to remove those -Extension in manifest, as they break running my app under tomcat 4. Those libs are only required by the compiler jar, not the api (runtime) jar, tho they can be removed from the manifest. This manifest is hand-writen and is included during the ant build. Building with maven doesn't include it. @see http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg 88665.html OK, so the entries itself are OK regarding manifest spec, but they cause the java runtime to start further actions that fail. According the spec these entries are used to define the dependencies for applets ... so I wonder also why they are present in this manifest at all. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Commons-Attributes 2.2 Corrupted Manifest
On 3/6/07, nicolas de loof [EMAIL PROTECTED] wrote: I already asked for a 2.2.1 release to remove those -Extension in manifest, as they break running my app under tomcat 4. Those libs are only required by the compiler jar, not the api (runtime) jar, tho they can be removed from the manifest. This manifest is hand-written and is included during the ant build. Building with maven doesn't include it. It isn't hand-written btw. It came from the Maven build and was put in SVN for the Ant build to use. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Commons-Attributes 2.2 Corrupted Manifest
You're right, sorry for this mistake. The maven generated manifest was using a maven option to declare dependencies as extensions-list. this option is not set in the project properties, so it may has been set on the computer used to generate the manifest. According to maven doc This can cause some applications to break, so it has been disabled by default. The project also is configured to use target=1.4. I'm using commons-attributes on java 1.3 and have compiled the 2.2 version on java 1.3without any issue. I did not searched the cvs log to know why it has been set. 2007/3/6, Henri Yandell [EMAIL PROTECTED]: On 3/6/07, nicolas de loof [EMAIL PROTECTED] wrote: I already asked for a 2.2.1 release to remove those -Extension in manifest, as they break running my app under tomcat 4. Those libs are only required by the compiler jar, not the api (runtime) jar, tho they can be removed from the manifest. This manifest is hand-written and is included during the ant build. Building with maven doesn't include it. It isn't hand-written btw. It came from the Maven build and was put in SVN for the Ant build to use. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Commons-Attributes 2.2 Corrupted Manifest
Leo Sutic wrote: Hi all, the Commons-Attributes 2.2 jars have corrupted manifest.mf files. This is apparently causing a bit of problems for users. The issue is in the extension properties: ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant-1.5. jar qdox-Extension-Name: qdox qdox-Implementation-Version: 1.5 qdox-Implementation-URL: http://www.ibiblio.org/maven/qdox/jars/qdox-1 .5.jar As you can see, there are spaces and cr/lfs in the URLs. This causes maven 2 etc. to fail. AFAICS the manifest is OK according the spec (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Name-Value%20pairs%20and%20Sections) by respecting the line length of 72 bytes. Longer lines violate the manifest ... Frankly, I have no desire nor time to get a new release out. What I wonder, however, is if we can treat this as a corrupted file issue and I can just fix the jars in the distribution directory by replacing or deleting the manifest.mf file in them. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Commons-Attributes 2.2 Corrupted Manifest
On 3/5/07, Leo Sutic [EMAIL PROTECTED] wrote: On 3/5/07, Jörg Schaible [EMAIL PROTECTED] wrote: Leo Sutic wrote: Hi all, the Commons-Attributes 2.2 jars have corrupted manifest.mf files. This is apparently causing a bit of problems for users. The issue is in the extension properties: ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant-1.5. jar qdox-Extension-Name: qdox qdox-Implementation-Version: 1.5 qdox-Implementation-URL: http://www.ibiblio.org/maven/qdox/jars/qdox-1 .5.jar As you can see, there are spaces and cr/lfs in the URLs. This causes maven 2 etc. to fail. AFAICS the manifest is OK according the spec (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Name-Value%20pairs%20and%20Sections) by respecting the line length of 72 bytes. Longer lines violate the manifest ... Heh. Thanks - I had no idea. Well, that explains where those line breaks came from. I guess the ball is in the other court then. I'm aiming to make a 2.2.1 release at some point for this - but low energy towards it currently. The above is good to know, said manifest was generated by a Sun JDK (1.4 I presume) on a Linux box, so nothing out of the ordinary. Is there an issue raised with Maven for this? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Commons-Attributes 2.2 Corrupted Manifest
Henri Yandell wrote on Monday, March 05, 2007 9:45 PM: On 3/5/07, Leo Sutic [EMAIL PROTECTED] wrote: On 3/5/07, Jörg Schaible [EMAIL PROTECTED] wrote: Leo Sutic wrote: Hi all, the Commons-Attributes 2.2 jars have corrupted manifest.mf files. This is apparently causing a bit of problems for users. The issue is in the extension properties: ant-Implementation-URL: http://www.ibiblio.org/maven/ant/jars/ant-1.5. jar qdox-Extension-Name: qdox qdox-Implementation-Version: 1.5 qdox-Implementation-URL: http://www.ibiblio.org/maven/qdox/jars/qdox-1 .5.jar As you can see, there are spaces and cr/lfs in the URLs. This causes maven 2 etc. to fail. AFAICS the manifest is OK according the spec (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Name-V alue%20pairs%20and%20Sections) by respecting the line length of 72 bytes. Longer lines violate the manifest ... Heh. Thanks - I had no idea. Well, that explains where those line breaks came from. I guess the ball is in the other court then. I'm aiming to make a 2.2.1 release at some point for this - but low energy towards it currently. The above is good to know, said manifest was generated by a Sun JDK (1.4 I presume) on a Linux box, so nothing out of the ordinary. Is there an issue raised with Maven for this? Don't think so. What exactly is the reported problem? - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
