Wasn't 3.0.3 simply staged and dropped?

Op Sun, 07 Feb 2016 12:26:41 +0100 schreef Hervé BOUTEMY <[email protected]>:

even if 3.0.3 has a bug, it should be on central, isn't it?
or is it a deliberate choice not to publish it to central?

Regards,

Hervé

Le samedi 6 février 2016 12:03:32 Karl Heinz Marbaise a écrit :
Hi Hervé,

Kristian wrote to me that he has found an regression and he will try to
understand it...but unfortunately i haven't heard more about it......

Yes I'm waiting for plexus-archiver etc...

plexus-archiver 3.0.2 seemed to be never on central...in contradiction
to the plexus page there is a release 3.0.2 tagged (git)...

So...yes migration sounds like a very good approach...


Kind regards
Karl Heinz

On 2/6/16 11:43 AM, Hervé BOUTEMY wrote:
> what happened to plexus-archiver 3.0.2 and 3.0.3? [1]
>
> is someone working on it?
>
> do we finally need to really work on Plexus Components migration to ASF?
> [2]
>
> Regards,
>
> Hervé
>
> [1]
> http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/
>
> [2] https://cwiki.apache.org/confluence/display/MAVEN/Plexus+dependencies
>
> Le vendredi 5 février 2016 23:54:18 Apache Jenkins Server a écrit :
>> See
>> <https://builds.apache.org/job/maven-plugins/org.apache.maven.plugins$mav
>> en
>> -source-plugin/5050/>
>>
>> ------------------------------------------
>> [INFO]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Apache Maven Source Plugin 3.0.0-SNAPSHOT
>> [INFO]
>> ------------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to