After placing the MySql properties into its own profile, the h2 profile worked
(though jmock failed on a couple of data integrity violations) when the
following element was added to the h2 profile:
<dbunit.operation.type>CLEAN_INSERT</dbunit.operation.type>
and when h2 is specified on the command-line, like so:
$ mvn -Ph2 jetty:run-war
However, the h2 profile appears to be non-active when relying on an
<activation/> element containing <activeByDefault>true</activeByDefault>:
$ mvn jetty:run-war
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: com.getpepper.testapp:testapp
POM Location: /home/paul/src/testapp/pom.xml
Validation Messages:
[0] 'dependencies.dependency.artifactId' with value '${jdbc.artifactId}'
does not match a valid id pattern.
[1] 'dependencies.dependency.groupId' with value '${jdbc.groupId}' does not
match a valid id pattern.
Reason: Failed to validate POM for project com.getpepper.testapp:testapp at
/home/paul/src/testapp/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for
project com.getpepper.testapp:testapp at /home/paul/src/testapp/pom.xml
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:376)
...
Any ideas? Have I missed something, or has this bug
(http://jira.codehaus.org/browse/MNG-1586) re-emerged?
$ mvn -v
Maven version: 2.0.8
Java version: 1.6.0_06
OS name: "linux" version: "2.6.24-19-generic" arch: "i386" Family: "unix"
Paul.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
