commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <damjan....@gmail.com>
Subject Re: [sanselan] how to build a release
Date Fri, 16 Dec 2011 05:13:25 GMT
On Thu, Dec 15, 2011 at 7:33 PM, sebb <sebbaz@gmail.com> wrote:

> On 15 December 2011 17:10, sebb <sebbaz@gmail.com> wrote:
> > On 15 December 2011 16:58, Damjan Jovanovic <damjan.jov@gmail.com>
> wrote:
> >> Hi
> >>
> >> I promised to start the Sanselan release process early this week, but
> I've
> >> been having problem after problem:
> >>
> >> 1. The instructions on http://commons.apache.org/releases/prepare.htmlsay
> >> that you run a variation of "mvn install" to build the release... but
> this
> >> only generates the .jar files, not the src/bin zip/tar.gz/tar.bz2 files.
> >
> > Probably need to run package as well, but it's hard work doing it that
> way.
> >
> >> 2. Running "mvn assembly:assembly" fails because my UTF-8 platform
> locale
> >> causes a multibyte bug in Plexus Archiver when writing a German sounding
> >> filename into the src tar file. I reported this 3 year old bug and
> >> submitted a patch (http://jira.codehaus.org/browse/PLXCOMP-195). How
> did
> >> you build Sanselan without this patch before?
> >
>
> I just tried assembly:assembly (and single) with no issues.
>
> What is your platform locale?
> Java version?
> Maven version?
>
> Can you not use MAVEN_OPTS to override the locale?
>

I am using Linux, Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200),
with locale of en_ZA.UTF-8.

You're probably on Windows, which uses a different locale, which doesn't
generate any multi-byte characters, so everything's fine.

Alternatively, perhaps the oddly-named files should be renamed to omit
> the accents etc.
> They may well cause unnecessary grief for others...
>
> Are the actual names an essential part of the test suite, or is it
> just the contents that matter?
>
>
Just the contents, and I can rename it for now, but somebody should really
fix Plexus Archiver and make Maven use the new version, otherwise this will
just happen again in a different project.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message