You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jeff MAURY <je...@jeffmaury.com> on 2012/05/08 23:01:13 UTC

Re: resolver-status.properties read/write warnings

On Thu, Apr 19, 2012 at 7:08 AM, Jason van Zyl <ja...@tesla.io> wrote:

> Separate repos work. If you absolutely needed a concurrent safe local repo
> there's one here:
>
> https://github.com/etesla/tesla-concurrent-localrepo
>

Link is not valid anymore

Jeff


> On Apr 18, 2012, at 10:03 PM, Bracewell, Robert wrote:
>
> > I wasn't aware that a shared local repo wasn't supported. I just switched
> > over all nodes to a local repo throughout the build farm and the warnings
> > did indeed disappear.
> > Version of Java used on this particular OSX node is
> > java version "1.6.0_31"
> > Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-11M3635)
> > Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
> >
> >
> > Thanks,
> > Robert
> >
> > On 4/18/12 6:44 PM, "Wayne Fay" <wa...@gmail.com> wrote:
> >
> >>>> farm. The Maven repo is hosted on a net app box that is visible to all
> >>>> my
> >>>> Redhat, Windows and now OSX build nodes via an NFS mount. The build
> >> ...
> >>> It seems you are using a shared local repository which is not supported
> >>
> >> Agreed on this point. You must use a local repo cache on each machine.
> >> And you should ensure that you only have 1 Maven instance access
> >> eaching local repo cache at once as well. If you're using
> >> Jenkins/Hudson, this is simple to configure.
> >>
> >>>> When running any mvn command (tried 3.0.3 and 3.0.4) on OSX Lion I see
> >>
> >> What version of Java are you running?
> >>
> >>>> java.io.IOException: Operation not supported
> >>>>       at sun.nio.ch.FileChannelImpl.lock0(Native Method)
> >>>>       at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:832)
> >>>>       at
> >>>>
> >>>>
> org.sonatype.aether.impl.internal.TrackingFileManager.lock(TrackingFileM
> >>>> anager.java:209)
> >>
> >> This stacktrace suggests to me that your OS does not support file
> >> locking over NFS? Look at sun.nio.ch.FileChannelImpl for more info.
> >>
> >> Wayne
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
> We know what we are, but know not what we may be.
>
>  -- Shakespeare
>
>
>
>
>


-- 
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually
working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury

Re: resolver-status.properties read/write warnings

Posted by Jason van Zyl <ja...@tesla.io>.
I will come back Monday with a website.

On May 8, 2012, at 4:01 PM, Jeff MAURY wrote:

> On Thu, Apr 19, 2012 at 7:08 AM, Jason van Zyl <ja...@tesla.io> wrote:
> 
>> Separate repos work. If you absolutely needed a concurrent safe local repo
>> there's one here:
>> 
>> https://github.com/etesla/tesla-concurrent-localrepo
>> 
> 
> Link is not valid anymore
> 
> Jeff
> 
> 
>> On Apr 18, 2012, at 10:03 PM, Bracewell, Robert wrote:
>> 
>>> I wasn't aware that a shared local repo wasn't supported. I just switched
>>> over all nodes to a local repo throughout the build farm and the warnings
>>> did indeed disappear.
>>> Version of Java used on this particular OSX node is
>>> java version "1.6.0_31"
>>> Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-11M3635)
>>> Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
>>> 
>>> 
>>> Thanks,
>>> Robert
>>> 
>>> On 4/18/12 6:44 PM, "Wayne Fay" <wa...@gmail.com> wrote:
>>> 
>>>>>> farm. The Maven repo is hosted on a net app box that is visible to all
>>>>>> my
>>>>>> Redhat, Windows and now OSX build nodes via an NFS mount. The build
>>>> ...
>>>>> It seems you are using a shared local repository which is not supported
>>>> 
>>>> Agreed on this point. You must use a local repo cache on each machine.
>>>> And you should ensure that you only have 1 Maven instance access
>>>> eaching local repo cache at once as well. If you're using
>>>> Jenkins/Hudson, this is simple to configure.
>>>> 
>>>>>> When running any mvn command (tried 3.0.3 and 3.0.4) on OSX Lion I see
>>>> 
>>>> What version of Java are you running?
>>>> 
>>>>>> java.io.IOException: Operation not supported
>>>>>>      at sun.nio.ch.FileChannelImpl.lock0(Native Method)
>>>>>>      at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:832)
>>>>>>      at
>>>>>> 
>>>>>> 
>> org.sonatype.aether.impl.internal.TrackingFileManager.lock(TrackingFileM
>>>>>> anager.java:209)
>>>> 
>>>> This stacktrace suggests to me that your OS does not support file
>>>> locking over NFS? Look at sun.nio.ch.FileChannelImpl for more info.
>>>> 
>>>> Wayne
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>> 
>> 
>> Thanks,
>> 
>> Jason
>> 
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder,  Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>> 
>> We know what we are, but know not what we may be.
>> 
>> -- Shakespeare
>> 
>> 
>> 
>> 
>> 
> 
> 
> -- 
> Jeff MAURY
> 
> 
> "Legacy code" often differs from its suggested alternative by actually
> working and scaling.
> - Bjarne Stroustrup
> 
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
> http://www.twitter.com/jeffmaury

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------

There's no sense in being precise when you don't even know what you're talking about.

 -- John von Neumann