Can we remove the special characters  ( -   .  etc. )  from the classifier:

        <envClassifier>hadoop-0.20</envClassifier>
..
        <envClassifier>hadoop-1.0</envClassifier>
..
        <envClassifier>hadoop-0.23</envClassifier>

Instead , make them appear as:

        <envClassifier>hadoop20</envClassifier>
..
        <envClassifier>hadoop100</envClassifier>
..
        <envClassifier>hadoop23</envClassifier>

or something similar , that conveys,

as  I am not sure, if it is a convention/would work with those special
characters in the classifier section of the pom ?





On Thu, Feb 16, 2012 at 5:21 PM, Patrick Hunt <ph...@apache.org> wrote:

> +1 sig/xsum are correct, rat is clean, tests all pass. Looks good to me.
>
> Note: the archive includes a mrunit jar file (the only jar file), did
> you intend to do this? Typically you want to have a src only artifact,
> and one or more artifacts containing "convenience binaries".
>
> Regards,
>
> Patrick
>
> On Wed, Feb 15, 2012 at 7:38 PM, Brock Noland <br...@cloudera.com> wrote:
> > This is an incubator release for Apache MRUnit, version
> > 0.8.1-incubating.
> >
> > It fixes the following issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311292&version=12319881
> >
> > *** Please download, test and vote by [3 working days after sending].
> >
> > Note that we are voting upon the source (tag), binaries are provided
> > for convenience.
> >
> > Source and binary files:
> > http://people.apache.org/~brock/mrunit-0.8.1-incubating-candidate-0/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachemrunit-010/
> >
> > The tag to be voted upon:
> >
> http://svn.apache.org/repos/asf/incubator/mrunit/tags/release-0.8.1-incubating/
> >
> > MRUnit's KEYS file containing PGP keys we use to sign the release:
> > http://svn.apache.org/repos/asf/incubator/mrunit/dist/KEYS
> >
> > Note that the Incubator PMC needs to vote upon the release after a
> > successful PPMC vote before any release can be made official.
>

Reply via email to