On 15 December 2011 17:10, sebb <seb...@gmail.com> wrote:
> On 15 December 2011 16:58, Damjan Jovanovic <damjan....@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.html say
>> 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?
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?
> The new goal is assembly:single
>
>> 3. Running "mvn assembly:assembly" with a manually patched Plexus Archiver
>> (and what a mission it was to figure out which of the 5 versions of Plexus
>> Archiver in my Maven repository is the one used...) does generate those
>> other files, but doesn't sign them.
>
> That's part of the release profile.
>
>> 4. My attempts to manually sign the .jar file, or its md5 or sha1 hash,
>> with gpg, generate different checksums than those generated by Maven. Thus
>> I cannot manually sign the zip/tar files. How is signing supposed to work,
>> what gets signed and how?
>
> No need to sign hashes, nor to provide hashes for sigs.
>
>> 5. "mvn release" is so badly documented that I am scared to use it. When I
>
> You are not the only one ...
>
>> run it with -DdryRun=true, it hangs on [gpg:sign {execution:
>> sign-artifacts}]. The child process launched by "mvn release:prepare" is
>> launched without this parameter, and strace shows it stuck in read() on fd
>> 0 (stdin). Typing the passphrase and pressing enter does nothing.
>> Redirecting stdin from a file with the passphrase also does nothing.
>> Attempts to use -Dgpg.passphrase=... also do nothing, whether passed to
>> directly "mvn" or quoted inside the -Darguments or both, and "ps fax" shows
>> that it isn't passed to the child process.
>>
>> Please help?
>
> I use the manual procedure for creating the SVN tag at:
>
> http://wiki.apache.org/commons/UsingNexus#Create_the_SVN_tags_.28Manual_method.29
>
> Then I use
>
> mvn package deploy -Prelease -Ptest-deploy
>
> to check that the artifacts look OK.
>
> Remove the test-deploy profile to deploy to Nexus (sanselan uses Nexus
> because it is under o.a.commons)
>
> I can try a dry-run here shortly, and you can then do the same.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
