I need to clear and initialize a database prior to running our
integration tests, so I can have a reliable dataset during the test
cases.
Are there any suggestions as to plugins or best practices for managing
the cleaning and initialization of database contents prior to
integration testing?
I didn't implement DBunit in each test case because I wanted to avoid:
1.) changing each of the database related test cases to extend from a
dbunit base class (reducing my test's coupling to the framework)
-and-
2.) I only want to insert the test data once, before a run of
integration tests -- I
Isn't this what the updatePolicy element in the snapshotRepository
element is all about? I don't have any documentation of it at hand, can
anyone else shed any light?
-jason
-Original Message-
From: jim stafford [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 11:23 PM
To:
Try ${project.build.directory}.
-jason
-Original Message-
From: David J. M. Karlsen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 26, 2006 11:37 AM
To: Maven Users List
Subject: [m2] variable for ${basedir}/target ?
Hi!
Does any variable exist for ${basedir}/target - or is this the
Andy:
Sadly, if the author doesn't put the API version in the jar's manifest
file or it's not built into the name of the jar itself you're not going
to have a good chance at discerning the version. Your mileage may vary;
however, these are generally the only two ways of which I'm aware.
Right, I didn't think of that. That would assuredly work, but I don't
know if it's automated.
-jason
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 9:42 AM
To: users@maven.apache.org
Subject: RE: Identifying versions of jar files
I
Greetings:
Continuum 1.0.3, running on FC-4.
I've had a great experience running Continuum for our newer Maven 2
builds; however, I've been integrating our existing ant builds into
Continuum with some difficulty.
The root cause of the difficulty is somewhat outside the scope of this
list
Greetings:
Maven 2.0.4, Ant 1.6.5, Windows XP (also occurs on RH FC-4)
I've integrated a number of our existing Ant builds with the maven
dependency resolution mechanism. They are drawing their dependencies
from our proxy repository without difficulty.
I'm having trouble with the deployment
Thanks for the quick reply. Running a build all didn't get rid of the
old in progress status builds, but that may simply be because I
bounced continuum since the in progress build hung. I suppose it's
not really a problem, just an aesthetic issue with having a messy build
history.
-jason
Maven v2.0.4, JDK 1.5 on Windows XP. I'm trying to integrate an
existing ant build with our maven repository. I've enabled the maven
tasks for ant, and am using maven-artifact-ant-2.0.4-dep.jar.
My configuration looks like:
target name=deployJar description=Deploy a jar to the maven repo
Sorry for the repost, but is there anyone out there that knows anything
about this error?
-jason
-Original Message-
From: Yankus, Jason
Sent: Thursday, July 13, 2006 10:24 AM
To: users@maven.apache.org
Subject: Error deploying artifact: Did receive proper ACK: '1'
Maven v2.0.4, JDK
I believe I've answered my own question. The problem here was that the
permission structure on the repository was missing the appropriate group
write bit for the projects I was trying to deploy. The reason the other
developer could perform this is because his user was the explicit owner
of the
Proximity. Works well as an internal mirror of central. Also provides
the capability to house your own deployed artifacts. The method by
which you deploy your own artifacts is somewhat variable based on the
decisions you make about the installation of the mirror, but generally
using the
13 matches
Mail list logo
