On Thu 11 Jan 2018 at 18:47, Plamen Totev wrote:
> Hi,
>
> On 12/28/2017 10:16 PM, Karl Heinz Marbaise wrote:
> > Hi,
> >
> > On 28/12/17 20:46, Stephen Connolly wrote:
> >> But shouldn’t we be copying the last modified time stamp always anyway
> >
> > I'm the same opinion...but that means in con
Hi,
On 12/28/2017 10:16 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> On 28/12/17 20:46, Stephen Connolly wrote:
>> But shouldn’t we be copying the last modified time stamp always anyway
>
> I'm the same opinion...but that means in consequence that the test in
> plexus-archiver is not correct...cause i
Hi,
On 28/12/17 20:46, Stephen Connolly wrote:
But shouldn’t we be copying the last modified time stamp always anyway
I'm the same opinion...but that means in consequence that the test in
plexus-archiver is not correct...cause it's waiting for a change in the
last-modified time ...
Hm...
But shouldn’t we be copying the last modified time stamp always anyway
On Thu 28 Dec 2017 at 14:52, Karl Heinz Marbaise wrote:
> Hi,
>
> after diving more into this..
>
> I found that if I upgrade plexus-utils to 3.1.0 in plexus-archiver the
> tests in plexus-archiver stuck completely...as I alr
Hi,
after diving more into this..
I found that if I upgrade plexus-utils to 3.1.0 in plexus-archiver the
tests in plexus-archiver stuck completely...as I already observed (which
I though was another cause)...
https://travis-ci.org/codehaus-plexus/plexus-archiver/jobs/321821294
So more divin