commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <damjan....@gmail.com>
Subject Maven bugs when building Sanselan
Date Wed, 29 Feb 2012 18:00:54 GMT
Hi

As we near the 1.0 release of Sanselan / Apache Commons Imaging, I am
having showstopper problems with Maven.

The first problem, now fixed, was that "mvn assembly:assembly" failed
due to the Maven Assembly plugin failing to add a non-ASCII filename
to a tar file (https://jira.codehaus.org/browse/MASSEMBLY-515),
because Plexus Archiver had a bug that wrongly assumed number of chars
= number of bytes, an assumption that quickly fails on UTF-8 locales
(http://jira.codehaus.org/browse/PLXCOMP-195). I sent a patch to
Plexus Archiver, they quickly included that patch in the next release,
and Maven Assembly then made a 2.3 release which unknowingly pulled in
that new release of Plexus Archiver. So by increasing the needed
version of Maven Assembly to 2.3, I got that working now :). I see
someone recently patched the Commons parent POM with the same version
change - even better.

The second is that "mvn site" fails because Clirr can't compare some
inner classes properly, and the Maven Clirr plugin doesn't properly
count and delete classes that can't be compared, leading to
ArrayIndexOutOfBoundsException
(http://jira.codehaus.org/browse/MCLIRR-36 and probably
http://jira.codehaus.org/browse/MCLIRR-25 and
http://jira.codehaus.org/browse/MCLIRR-37). I made and attached a
working patch to that bug, but there's been no response yet and the
project seems dead :(.

Otherwise, what is the procedure for renaming the project to Apache
Commons Imaging?

Thank you
Damjan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message