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:
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,
When running any mvn command (tried 3.0.3 and 3.0.4) on OSX Lion I see numerous
lines of output similar to below. I added a mac box to my build 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 doesn't
It seems you are using a shared local repository which is not supported
Jeff
Le 18 avr. 2012 23:56, Bracewell, Robert rbrac...@qualcomm.com a écrit :
When running any mvn command (tried 3.0.3 and 3.0.4) on OSX Lion I see
numerous lines of output similar to below. I added a mac box to my build
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
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
Separate repos work. If you absolutely needed a concurrent safe local repo
there's one here:
https://github.com/etesla/tesla-concurrent-localrepo
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
