On Mon, Mar 25, 2013 at 1:34 PM, Brian Fox wrote:
> Just to close the loop, this is fixed:
> http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.2/
>
Thanks a lot.
Thomas
Just to close the loop, this is fixed:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1.2/
On Sat, Mar 23, 2013 at 5:54 AM, Brian E. Fox wrote:
> Ok, looking
>
> --Brian (mobile)
>
>
> On Mar 22, 2013, at 8:25 AM, Thomas Neidhart
> wrote:
>
>> On Fri, Mar 22, 2013 at 1:21 PM, B
Ok, looking
--Brian (mobile)
On Mar 22, 2013, at 8:25 AM, Thomas Neidhart wrote:
> On Fri, Mar 22, 2013 at 1:21 PM, Brian Fox wrote:
>
>> I'm here too ;-)
>>
>> Which release exactly? It's possible that we overlooked something when
>> we moved the remaining commons projects over to rao.
>
On Fri, Mar 22, 2013 at 1:21 PM, Brian Fox wrote:
> I'm here too ;-)
>
> Which release exactly? It's possible that we overlooked something when
> we moved the remaining commons projects over to rao.
>
Hi Brian,
It's commons-logging 1.1.2, which was release on 20-03-2013.
btw. groupId is still
I'm here too ;-)
Which release exactly? It's possible that we overlooked something when
we moved the remaining commons projects over to rao.
On Fri, Mar 22, 2013 at 6:42 AM, Simone Tripodi
wrote:
> Hi Thomas,
>
> the best thing to do, in such cases, is dropping an email to our
> repository fello
Hi Thomas,
the best thing to do, in such cases, is dropping an email to our
repository fellows on reposit...@apache.org
It worked for me in the past :P
Best,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.or
Hi,
maven central has not yet picked up the latest release (1.1.2) after
several days.
This is at least unusual compared to other releases lately.
Is this normal or is there maybe something going wrong?
Thanks,
Thomas
