Any chance to see a vote for 2.2.1 release to solve this ?
Nico.
2007/1/16, Henri Yandell [EMAIL PROTECTED]:
If no one else is able to, I'll be looking at this next week along
with the IO and Lang releases (if no one moves them on). This week is
too busy/lacking my personal laptop/too snowy
Can anyone make a release to solve this ?
2007/1/5, nicolas de loof [EMAIL PROTECTED]:
The manifest.mf in SVN contain a Created-By: Apache Maven but I never
got maven include such Extension-List in my manifest. The one generated by
the maven build don't include them. It seems the
If no one else is able to, I'll be looking at this next week along
with the IO and Lang releases (if no one moves them on). This week is
too busy/lacking my personal laptop/too snowy (hurts cable for some
reason).
Hen
On 1/16/07, nicolas de loof [EMAIL PROTECTED] wrote:
Can anyone make a
The manifest.mf in SVN contain a Created-By: Apache Maven but I never got
maven include such Extension-List in my manifest. The one generated by the
maven build don't include them. It seems the
maven.jar.manifest.extensions.add option creates those entries in manifest.
Maybe this property was
On 1/3/07, nicolas de loof [EMAIL PROTECTED] wrote:
Hello,
I'm using commons-attributes with Spring on a Java 1.4 application.
I've included commons-attributes-api 2.2 (from maven repo)
I get this Tomcat exception on startup :
LifecycleException: Missing optional package Extension[ant,
According to SVN log, the manifest has been added by bayard. The maven
generated manifest is not used (why ?)
I also notice maven.compiler.target has been set to 1.4 during 2.2 (rev
410143 by leosutic) that will break backward compatibility : I'm using
commons-attributes on other projects on JRE
On 1/4/07, nicolas de loof [EMAIL PROTECTED] wrote:
According to SVN log, the manifest has been added by bayard. The maven
generated manifest is not used (why ?)
These are for the Ant build - they're the ones that Maven generated
for me. Seem to recall that attributes didn't like building on
Hello,
I'm using commons-attributes with Spring on a Java 1.4 application.
I've included commons-attributes-api 2.2 (from maven repo)
I get this Tomcat exception on startup :
LifecycleException: Missing optional package Extension[ant,
implementationURL=
