Add the build-helper-maven-plugin to your project's POM. This may look
something like this:
65
66 org.codehaus.mojo
67 build-helper-maven-plugin
68 1.1
69
70
71 add-so
Sounds like this might help you:
- Create a Maven plugin which is executed in any phase >>bevore<< test,
e.g. 'generate-test-resources'. This will make it possible to set up the
database. This plugin might help for starting the database (only if you're
using HSQL):
http://gforge.openehealth.or
We had the same problem with, I guess, a Fornax repository a few months
ago and it was terrible. Question to Maven developers: Wouldn't it be
possible to treat a 301 (redirect) error the same way as a 40x error? This
would prevent the POMs from beeing corrupted.
Bernd
Andy Jefferson wrote o
Søren Krogh Neigaard wrote on
05.02.2010 07:45:51:
> We are already using
> the sql-maven-plugin to bootstrap the database, but it only gets run
> once before all junit tests are run, and that is not what I need, I
> need it to run for every test to ensure a clean database.
>
> I can easily m
According to Maven's documentation here
http://maven.apache.org/pom.html#Properties, this should work (I didn't
try it):
settings.xml:
true
oracle.jdbc.driver.OracleDriver
jdbc:oracle:thin:@myhome:1521:orcl
pom.xml:
oracle.jdbc.OracleDr
Of course:
27 /**
28 * @parameter expression="${session}"
29 */
30 private MavenSession mavenSession;
Bernd
meier.krist...@gmail.com wrote on 05.03.2010 06:28:53:
> [image removed]
>
> Re: offline mode with in plugin
>
> kristian
>
> to:
>
> Maven Users List
>
>
Hi all!
When switching from 3.0.4 to 3.1.0 I encountered that obviously the classes
* org.apache.maven.repository.internal.MavenRepositorySystemSession
* org.apache.maven.repository.internal.MavenServiceLocator
are no longer there. Seems, the last version with these classes was 3.0.5.
However,
t-wip-us.apache.org/repos/asf?p=maven.git;a=tree;h=5a0e6574404b4964522d90c3438e25574a95466c;hb=893ca28a1da9d5f51ac03827af98bb730128f9f2
The tag you saw in svn is probably the leftover of an aborted release before
the move to git.
On 19 Sep 2013, at 22:36, Bernd Adamowicz wrote:
Hi all!
When swit
Hi all,
When switching from Maven 3.0.x to 3.1.x some of our projects where not able to
execute anymore due to a problem with MavenEmbedder. Both projects are command
line based, no Maven plugin around it.
I think the most important part of the stack trace is this:
37) No implementation for
j
No answer so far. Should I file a bug? Any opinion?
Bernd Adamowicz
-Original Message-
From: Bernd Adamowicz [mailto:bernd.adamow...@esailors.de]
Sent: Montag, 18. November 2013 16:12
To: users@maven.apache.org
Subject: MavenEmbedder problem with 3.1.x
Hi all,
When switching from
Amazing! This works!
I tried so many permutations of dependency version, but obviously never got the
right one. Thanks a lot Stuart!
--
Bernd Adamowicz
-Original Message-
From: Stuart McCulloch [mailto:mccu...@gmail.com]
Sent: Mittwoch, 20. November 2013 16:04
To: Maven Users List
11 matches
Mail list logo
