Hi John,
For companies which are this paranoid, perhaps they should not download
artifacts from public repositories at all. Have you considered setting up a
Nexus / Archiva installation which does not connect to any public repos? Then
you can manually deploy any artifacts you wish to this repos
No, there's no need to "fork" for different unit tests. JUnit 4 will run the
old tests just fine, along with the new. All I have done is update my
dependency, like so:
junit
junit
4.8.1
test
Existing tests run, and I can also create and run unit tests using
I have similar experience. I upgraded a couple of projects to JUnit 4.8.1 (from
3.x) in the past few months. Leaving the old tests as-is has worked fine, while
allowing me to write new tests in the new style, just as you propose.
Seems like the best approach to me.
~Daniel Siegmann
-Origin
I want to debug through Maven's code (using Eclipse) when building my
own project. Are there any guides to doing this? I'm sure I can get
Maven checked out from svn myself, I'm just not sure how to run Maven
through Eclipse such that it will be able to build my project.
Specifically I need to dig
<>
Just so you know, VMware Server is free. I have used it to set up
testing environments, seems to work pretty well.
http://www.vmware.com/products/free_virtualization.html
--
Daniel Siegmann
FJA-US, Inc.
512 Seventh Ave., New York, NY 10018
(212) 840-2618 ext. 139
---
