On 12/03/2020 13:55, Andreas Sewe wrote:
If the test utilities are simple enough and are somehow specific to foo,
I would put them into foo, under src/main/java, in a package like
com.foo.testing. If they are more general, so that they could be used to
write tests for some other package not rel
Thanks Stephen,
that's very interesting.
Marco.
On 30/10/2012 10:23, Stephen Connolly wrote:
On 30 October 2012 10:14, Zak Mc Kracken wrote:
On 25/10/2012 02:47, Barrie Treloar wrote:
Maven will needless contact all five of your repositories looking for
artifacts that probably aren&#
On 25/10/2012 02:47, Barrie Treloar wrote:
Maven will needless contact all five of your repositories looking for
artifacts that probably aren't even there.
This will require a tcp/ip connection for each one and when you have
large dependencies this can significantly slow down your build.
Which is
Hi Javix,
yes, this is what I mean. You may want to consider what emerged in this
thread about the goodness of this practice.
Cheers,
M.
On 21/09/2012 10:55, Javix wrote:
Finally, I achived (I hope so, tell me if I'm wrong by pointing at some
pitfalls). Here is the updated version of the PO
Hi Roy,
that's a useful addition. Indeed I do something similar with with some
command-line tools. I ship them as a zip which contains: a .jar a
.sh/.bat invoking commands and a default .properties file. For the
latter, I want different defaults depending on the environment where I
deploy fin
OK, I understand that in general it should be considered an
anti-pattern. Despite that, in my organisation we deploy a number of
internal tools on a couple of servers and with different configurations
(dev, test, production). To achieve this we do what it was originally
asked in this thread.
On 24/10/2010 22:29, Arnaud Héritier wrote:
> As some others said, the real solution for you is to use a repository
manager.
> It will bring many advantages to manage binaries coming from outside
and it will give you a transparent access to maven 1 and 2 repositories
On 24/10/2010 22:54, Wayn
es". :-)
/Anders
On Sun, Oct 24, 2010 at 21:22, Anders Hammar wrote:
You need to get a repo manager like Nexus set up, which is able to convert
from Maven 1 to Maven 2 repo format.
/Anders
On Sun, Oct 24, 2010 at 20:35, Zak Mc Kracken wrote:
Hi all,
sorry if the question has already be
Hi all,
sorry if the question has already been asked, I cannot find anything on
the mailing list archive.
Subject should be clear enough, I have a project with many dependencies
on Maven 1 3rd-party repositories that I cannot migrate (e.g.:
java.net). Isn't there a way to continue to use the
Hi all,
Since today "mvn test" does not report the list of failed tests at the
end. I have:
Results :
Failed tests:
Tests run: 74, Failures: 3, Errors: 0, Skipped: 4
[ERROR]
Mojo:
org.apache.maven.plugins:maven-surefire-plugin:2.4.2:test
FAILED for project:
:jar:1.0-
10 matches
Mail list logo
