On Tue, Jul 22, 2008 at 10:01 PM, simon <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-07-22 at 19:39 +0200, Matthias Wessendorf wrote:
>> Hi,
>>
>> I was running the needed tasks to get the 1.2.7 release of the Apache
>> MyFaces Trinidad Maven 2 Plugins out.
>>
>> The artifacts are deployed to my private Apache account ([1]).
>>
>> Please take a look at the "1.2.7" artifacts and vote.
>>
>> How to test those JARs ?
>>
>> Use the stage repo inside your pom.xml file:
>> ...
>> <pluginRepositories>
>>  <pluginRepository>
>>  <id>apache.stage</id>
>>  <name>Apache Stage Repository</name>
>>  <url>http://people.apache.org/~matzew/127-plugins</url>
>>  <layout>default</layout>
>>  </pluginRepository>
>> </pluginRepositories>
>> ...
>>
>
> The staging dir contains a lot of unneeded *.asc* files, eg
>   maven-faces-plugin-1.2.7-javadoc.jar.asc.asc.md5
> which is AFAIK the md5 checksum of the ascii-armoured signature of the
> ascii-armoured signature of the jar.
>
> I get this too when following the normal release procedure, and just
> manually delete the crap files before uploading. Some day it would be
> nice to fix this properly (probably in the master myfaces pom)....

yeah, I agree

>
> Perhaps you could just delete these from your staging dir manually?

yes, before publishing, ok ?

>
> ===
>
> signatures verify ok (random sample)
> checksums are fine (random sample)
> LICENSE and NOTICE files seem to be present and correct (random sample).
>
> The java .class version format is 48.0, ie it is java1.4-compatible.
> Note that the MANIFEST.MF files states that the code was build with
> java1.5. So there is a minor risk that the code is not actually
> 1.4-compatible. No problem, as long as it's deliberate.
hrm, not sure how to fix that... :(
>
> As noted in another email, there is 1 java file with an old-style
> copyright header, and a couple of pom.xml files with either old or
> missing headers. But it's very few so I don't think this is a
> release-blocker.

will fix that.

>
> So +1 from me.
>
> Regards, Simon
>
>



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org

Reply via email to