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
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
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.
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
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:
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:
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
