Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released
Good work Haroon, Thanks for the information. In my case I'm getting the error on the command line. My project has numerous subprojects and the error only occurs several projects into the build so it will take some time to create a minimal test case. Donnchadh On 07/02/2008, Haroon Rafique [EMAIL PROTECTED] wrote: On Today at 3:30pm, DD=Donnchadh Ó Donnabháin [EMAIL PROTECTED] wrote: DD Hi Dan, DD DD When I switch from surefire 2.4 to 2.4.1 I get the error below. DD /tmp/surefirebooter22682.jar doesn't seem to even exist. Any idea what DD might be causing this? DD Not knowing much about surefirebooter, I can at least tell you (paraphrasing here) that the /tmp/surefirebooter*.jar files are created at runtime and then deleted when the test is over. If you run with mvn -X, the /tmp/surefirebooter*.jar will be left in tact to aid in the debugging process. For me when the error about Failed to load Main-Class manifest attribute from /tmp/surefirebooter???.jar appeared, I re-ran the tests with mvn -X and then opened up the /tmp/surefirebooter???.jar file. It is a .jar file with only one entry META-INF/MANIFEST.MF. Inside the MANIFEST.MF there are 2 entries. Class-Path and Main-Class. Sure enough, the file was in tact, yet surefirebooter would say it can't find the Main-Class. You can even try the actual java -jar /tmp/surebooter???.jar . command and it still failed. Looking a little bit more, I was able to extract the MANIFEST.MF file and change its format from dos to unix in vim and repackaged it back into a jar and sure enough the java -jar /tmp/surefirebooter???.jar . command was able to run. This is as far as I've gotten so far. Two other data points: 1) Problems are fixed when dropping jdk to 1.5.0_14 2) Problem only appears running inside cruisecontrol (not on the command line) I would be tempted to file a jira but my project is pretty big and I'm finding it absolutely difficult to localize the issue so that I can present a minimal test case. So, with the information that I have provided to you so far, hopefully you can provide a minimal test case :-) (or at least, I can wish). Regards, -- Haroon Rafique [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven Surefire Plugin 2.4.1 for Maven 2 Released
Hi Dan, When I switch from surefire 2.4 to 2.4.1 I get the error below. /tmp/surefirebooter22682.jar doesn't seem to even exist. Any idea what might be causing this? Thanks Donnchadh [INFO] Surefire report directory: /home/donnchadh/projects/ ... /target/surefire-reports Failed to load Main-Class manifest attribute from /tmp/surefirebooter22682.jar [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /home/donnchadh/projects/ ... /target/surefire-reports for the individual test results. [INFO] [INFO] Trace org.apache.maven.BuildFailureException: There are test failures. Please refer to /home/donnchadh/projects/ ... /target/surefire-reports for the individual test results. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: There are test failures. Please refer to /home/donnchadh/projects/ ... /target/surefire-reports for the individual test results. at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:530) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 16 more [EMAIL PROTECTED] myproject]$ mvn -version Maven version: 2.0.8 Java version: 1.6.0_04 OS name: linux version: 2.6.23.14-107.fc8 arch: i386 Family: unix On 06/02/2008, Dan Fabulich [EMAIL PROTECTED] wrote: The Maven team is pleased to announce the release of the Maven Surefire Plugin, version 2.4.1 http://maven.apache.org/plugins/maven-surefire-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId version2.4.1/version /plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
overlaid war files and timestamps
In Better Builds with Maven, it says: If you add a dependency on a WAR, then the WAR you generate will be overlaid with the content of that dependent WAR, allowing the aggregation of multiple WAR files. However, only files not in the existing Web application will be added, and files such as web.xml won't be merged. I have a property fole in my webapp and from the above paragraph I would not expect it to be overwritten. However, it is. If I update the timestamp of the file in my webapp (using 'touch') the property file is not overwritten. This behaviour isn't mentioned in http://maven.apache.org/plugins/maven-war-plugin/examples/war-overlay.html either. Of course, I can use dependentWarExcludes to exclude that property file, but the documentation is missleading when it suggests that only file not in the existing application will be added. Donnchadh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven 2.0.6 Released
On 4/1/07, Jason van Zyl [EMAIL PROTECTED] wrote: The Apache Maven team would like to announce the availability of Maven 2.0.6. We have closed out 22 issues for this release and the upgrade from 2.0.5 should be pain free. We corrected a major flaw in the artifact resolution mechanism and we cannot find any problems but information about the change can be found here: Just gave this a try and got the following error: [INFO] Building wumpus Web Application [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:164) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:334) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:75) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:284) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1238) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:397) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven 2.0.6 Released
OK, I'll try to create a simplified pom which exposes this bug. It seems to occur on this line: resetArtifact.selectVersion( resetArtifact.getVersionRange().matchVersion(resetArtifact.getAvailableVersions() ).toString() ); Maybe it's related to the following bug (same piece of code) http://jira.codehaus.org/browse/MNG-2861 Donnchadh On 4/2/07, Jason van Zyl [EMAIL PROTECTED] wrote: Provide a test project with your setup so I can track it down. I've run hundreds of projects with that snapshot so you have something in your POM that's causing the problem. Jason. On 2 Apr 07, at 7:05 AM 2 Apr 07, Donnchadh Ó Donnabháin wrote: On 4/1/07, Jason van Zyl [EMAIL PROTECTED] wrote: The Apache Maven team would like to announce the availability of Maven 2.0.6. We have closed out 22 issues for this release and the upgrade from 2.0.5 should be pain free. We corrected a major flaw in the artifact resolution mechanism and we cannot find any problems but information about the change can be found here: Just gave this a try and got the following error: [INFO] Building wumpus Web Application [INFO]task-segment: [install] [INFO] -- -- [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] -- -- [ERROR] FATAL ERROR [INFO] -- -- [INFO] null [INFO] -- -- [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse (DefaultArtifactCollector.java:164) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse (DefaultArtifactCollector.java:334) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse (DefaultArtifactCollector.java:334) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect (DefaultArtifactCollector.java:75) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTran sitively(DefaultArtifactResolver.java:284) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTran sitively(DefaultArtifactResolver.java:272) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependen cies(DefaultPluginManager.java:1238) at org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginManager.java:397) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif ecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand leFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced (Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode (Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] -- -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Download Sources
Running mvn dependency:sources results in the following error for me [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: dependency:sources Donnchadh On 2/15/07, Tomislav Stojcevich [EMAIL PROTECTED] wrote: You shouldn't need to configure anything in the pom, just do mvn dependency:sources - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse target directory
Here's a quick and dirty Eclipse Monkey (http://www.eclipse.org/dash/)
script to make all target folders derived. Update site for Eclipse
Monkey is http://download.eclipse.org/technology/dash/update/
--- Came wiffling through the eclipsey wood ---
/*
* Menu: Maven Make Maven Targets Derived
* Kudos: Donnchadh Ó Donnabháin
* License: EPL 1.0
* DOM: http://download.eclipse.org/technology/dash/update/org.eclipse.dash.doms
*/
function main() {
var files = resources.filesMatching(.*/pom\\.xml);
var targetFolder;
for each( file in files ) {
if (targetFolder = file.eclipseObject.parent.findMember(target)) {
targetFolder.setDerived(true);
}
}
}
--- And burbled as it ran! ---
Once you've installed eclipse monkey, copy the contents of this
message and select 'Monkey Paste Script'. You will now have a new
menu item 'Monkey Maven Make Maven Targets Derived'
As I said it's quick and dirty so feel free to improve on it.
Donnchadh
On 10/17/06, Daniel Serodio [EMAIL PROTECTED] wrote:
Douglas Ferguson wrote:
Awesome! Thanks.
The only problem is that this breaks when the target folder is
re-created (for example, if you run mvn clean, because this
information (is derived) is stored in the folder's metadata.
I've requested the ``ability to remember that a resource is derived
when said resource is deleted´´
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=154089), but it seems
like it's not going to happen (see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=150578).
HTH,
Daniel Serodio
Where does it store this value? I can't find it in any of the config files
for the project.
Could this be added to eclipse:eclipse?
-Original Message-
From: Donnchadh Ó Donnabháin [mailto:[EMAIL PROTECTED]
Sent: Friday, September 08, 2006 8:48 AM
To: Maven Users List
Subject: Re: Eclipse target directory
In eclipse right-click on the target folder and select 'Properties...'
Then, in the Info page, check the 'derived' check box. This should
exlude it from searches and resource lookups. Probably error reporting
too but I haven't verified that
Donnchadh
On 9/5/06, Douglas Ferguson [EMAIL PROTECTED] wrote:
When using eclipse on war projects, the target directory will start to
collect copies of jsp files, from war:war commands, etc.
Is there a way to have eclipse ignore the files when searching and
reporting errors?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Progress indicators for project management
I tried it quicly and came across a few issues (most of which are
easily dealt with).
I took the example configuration on the maven2 QALab plugin page
( http://qalab.sourceforge.net/maven2/faq.html )
and simplified it to just working with PMD. I came across the following issues:
* By default PMD doesn't seem to produce an XML report
* When the PMD plugin is instructed to produce an XML report it puts
it in target and the QALab example QALab expects it to be in
target/pmd.
* By Default, the PMD plugin seems to run in the report phase and the
example runs in the verify phase
I got it working in the end with the following configuration
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
executions
execution
idpmd/id
phaseverify/phase
goals
goalpmd/goal
/goals
/execution
/executions
configuration
linkXreftrue/linkXref
targetJdk1.5/targetJdk
formatxml/format
/configuration
/plugin
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
executions
execution
idpmd-merge/id
phaseverify/phase
goals
goalmerge/goal
/goals
configuration
handlernet.objectlab.qalab.parser.PMDStatMerge/handler
inputFile
${project.build.directory}/pmd.xml
/inputFile
/configuration
/execution
execution
idqalab-movers/id
phaseverify/phase
goals
goalmovers/goal
/goals
configuration
startTimeHoursOffset480/startTimeHoursOffset
/configuration
/execution
execution
idqalab-chart/id
phaseverify/phase
goals
goalchart/goal
/goals
configuration
summaryOnlyfalse/summaryOnly
/configuration
/execution
/executions
configuration
typespmd/types
/configuration
/plugin
/plugins
/build
reporting
plugins
plugin
groupIdnet.objectlab/groupId
artifactIdmaven-qalab-plugin/artifactId
version2.1/version
reportSets
reportSet
reports
reportreport/report
reportmovers-report/report
/reports
/reportSet
/reportSets
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-pmd-plugin/artifactId
configuration
linkXreftrue/linkXref
targetJdk1.5/targetJdk
formatxml/format
/configuration
/plugin
/plugins
/reporting
It seems a little verbose. I wonder if a more concise configuration is possible?
Also, I would like to set it up in my root pom and inherit the
confiuration in the modules, but that doesn't seem very
straightforward.
Is it possible to configure it in the root pom and bind it to a
lifecycle phase in the child pom (this is a general maven 2 question)?
A bigger issue is that the history is stored within an xml file in the
project. I imagine that qalab would be run within a continuous
integration context in general and the history would be lost.
Is it possible to override the location of this and store it somewhere
outside the project so that when the continuous integration system
(luntbuild in our case) does a clean build, this history is not lost?
Donnchadh
On 9/21/06, Christophe Deneux [EMAIL PROTECTED] wrote:
Thanks Doug,
I will try QALab. It seems that no Maven2 plugin exists for XRadar.
Christophe
-- Initial Header ---
From : Doug Douglass [EMAIL PROTECTED]
To : Maven Users List users@maven.apache.org
Cc :
Date : Thu, 21 Sep 2006 08:00:37 -0600
Subject : Re: Progress indicators for project management
Checkout qalab[1], there's a maven plugin around for it, though I haven't
used it. Perhaps search the [EMAIL PROTECTED] list archives, I think there
was a
thread over there in the last few weeks regarding the maven reporting API.
Many people are very, very interested in this type of capability.
XRadar[2] was another tool name that come to mind.
Cheers,
Doug
[1] http://qalab.sourceforge.net/
[2] http://xradar.sourceforge.net/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Database deployment
At first I used the maven exec plugin to run a shell script, but now I'm switching to the sql-maven-plugin, both from the codehaus mojo project. sql-maven-plugin seems to be exactly what I was looking for. other options would have been dbunit for data and using hibernate (maybe via the maven exec plugin) to generate generate the schema. Once we have a released version we also plan on running migration scripts. Donnchadh On 9/12/06, Christophe DENEUX [EMAIL PROTECTED] wrote: We plan to use the ant task exec, and its attribute os to manage the difference between operating system. Our projects use an Oracle database, so the exec task will execute sqlplus with a sql script file. We plan to follow this way during the life of our project: a) for the first release (V1), we will use the exec ant task to drop and create the V1 database schema, b) when the V1 will be released, we will export the schema (data and DDL) in a dump file c) for the next release (V2), according to the possible project installation (from scratch, or over the previous version), we will use: c1) for from scratch case: exec ant task to drop and create the V2 database schema, c2) for over the previous release case: exec ant task to drop, import V1 dump file and migrate from V1 to V2 with the database patch script, Our projects that are planned to use this way, have an manual installation procedure (helped by scripts) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Database deployment
Yes, ours is a continuous integration context too. What ant task do you use? At it's simplest we could execute the mysql command with the DDL script. I guess what I'm looking for is, what is the standard way of doing this? I would imagine that a large proportion of of projects using maven are database-backed, (presumably the majority of web applications that use maven) so there must be a standard way of deploying a database schema from a maven build. Alternatives to getting the build to deploy the schema is to package the DDL script into the webapp and get it to run it on startup if necessary. Donnchadh On 9/1/06, Christophe DENEUX [EMAIL PROTECTED] wrote: We are thinking to a solution on a similar problem, but in a contionuous integration context. Our solution should be the following: - on the pre-integration-tests phase, execute the following tasks through the maven-antrun-plugin: 1 - drop all tables in your database 2 - import a database corresponding to the previous version of your webapp 3 - run sql scripts to update the database schema. - on the integration-test phase, execute your jWebUnit tests I think that to use the setup methods of the test-cases to initialize the database schema is not a good idea because you will probably update your testcases in the next release of your webapp. We use profiles to deploy on different QA environments. Christophe DENEUX / Capgemini Sud / Méditerranée Technical Leader Tel: + 33 4 93 72 43 74 / www.capgemini.com Fax: + 33 4 93 21 02 95 Porte de l'Arénas - Entrée B / 455 Promenade des Anglais / 06200 Nice Join the Collaborative Business Experience Donnchadh Ó Donnabháin a écrit : Hi everyone, I'm using the cargo plugin to deploy a webapp to tomcat. This webapp depends on a database and I would like run a SQL script to deploy the updated schema before deploying the webapp. What is the best approach to this? Is there a plugin to facilitate this? Once I have this working I would like to perform integration tests (probably using jWebUnit and htmlunit) and if they succeed, deploy the webapp to another context to provide feedback to the client Donnchadh - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Integration testing - tests are being run during both 'test' and 'integration-test' phases
I've added the following to buildplugins: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution phaseintegration-test/phase goals goaltest/goal /goals /execution /executions /plugin This results in my tests being executed during the integration-test phase, which is great. The problem is that they are still being run during the test phase (before the database schema has been deployed) How do I prevent my integration tests being run during the test phase? Thanks Donnchadh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integration testing - tests are being run during both 'test' and 'integration-test' phases
That's perfect Thanks Donnchadh On 9/12/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 9/12/06, Donnchadh Ó Donnabháin [EMAIL PROTECTED] wrote: I've added the following to buildplugins: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId executions execution phaseintegration-test/phase goals goaltest/goal /goals /execution /executions /plugin This results in my tests being executed during the integration-test phase, which is great. The problem is that they are still being run during the test phase (before the database schema has been deployed) How do I prevent my integration tests being run during the test phase? The standard advice is to move the integration tests to a separate module with a packaging type of 'pom'. Then nothing run except the plugin executions that you bind to various lifecycle phases. Or, this wiki page might help: http://docs.codehaus.org/pages/viewpage.action?pageId=62120 !-- skip unit test run, tests to be executed during integration-test -- plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration skiptrue/skip /configuration executions execution idsurefire-it/id phaseintegration-test/phase goals goaltest/goal /goals configuration skipfalse/skip /configuration /execution /executions /plugin -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse target directory
In eclipse right-click on the target folder and select 'Properties...' Then, in the Info page, check the 'derived' check box. This should exlude it from searches and resource lookups. Probably error reporting too but I haven't verified that Donnchadh On 9/5/06, Douglas Ferguson [EMAIL PROTECTED] wrote: When using eclipse on war projects, the target directory will start to collect copies of jsp files, from war:war commands, etc. Is there a way to have eclipse ignore the files when searching and reporting errors? D- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse target directory
It seems to be stored in a binary file in the workspace (making it difficult for eclipse:eclipse to do much about ir) but there is an API method for setting it so maybe the m2eclipse eclipse plugin could do that Donnchadh On 9/8/06, Douglas Ferguson [EMAIL PROTECTED] wrote: Awesome! Thanks. Where does it store this value? I can't find it in any of the config files for the project. Could this be added to eclipse:eclipse? -Original Message- From: Donnchadh Ó Donnabháin [mailto:[EMAIL PROTECTED] Sent: Friday, September 08, 2006 8:48 AM To: Maven Users List Subject: Re: Eclipse target directory In eclipse right-click on the target folder and select 'Properties...' Then, in the Info page, check the 'derived' check box. This should exlude it from searches and resource lookups. Probably error reporting too but I haven't verified that Donnchadh On 9/5/06, Douglas Ferguson [EMAIL PROTECTED] wrote: When using eclipse on war projects, the target directory will start to collect copies of jsp files, from war:war commands, etc. Is there a way to have eclipse ignore the files when searching and reporting errors? D- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Module dependecy graph
Hi everyone, Does anyone know of a tool (preferrably a maven2 plugin) to generate a graph of dependices between modules within a maven2 project? I'm thinking of something that you could point at the root pom.xml and would go through all the modules - possibly something like springs beandoc (BTW is there a beandoc plugin for maven2?). I'm not interested in the external dependencies of the project, just inter-module dependencies. Thanks Donnchadh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Database deployment
Hi everyone, I'm using the cargo plugin to deploy a webapp to tomcat. This webapp depends on a database and I would like run a SQL script to deploy the updated schema before deploying the webapp. What is the best approach to this? Is there a plugin to facilitate this? Once I have this working I would like to perform integration tests (probably using jWebUnit and htmlunit) and if they succeed, deploy the webapp to another context to provide feedback to the client Donnchadh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Module dependecy graph
Yeah, that's probably 90% of what I want. I'm thinking of something that draws a visual graph and only shows inter-module dependencies On 9/1/06, Vinod Panicker [EMAIL PROTECTED] wrote: I asked this question today. Basically to get the dependency graph, you can run the site goal. If you have a multi-module project, you will have to run the site goal within each module directory since the plugin currently does not collate all the dependency information. HTH, Vinod. On 9/1/06, Donnchadh Ó Donnabháin [EMAIL PROTECTED] wrote: Hi everyone, Does anyone know of a tool (preferrably a maven2 plugin) to generate a graph of dependices between modules within a maven2 project? I'm thinking of something that you could point at the root pom.xml and would go through all the modules - possibly something like springs beandoc (BTW is there a beandoc plugin for maven2?). I'm not interested in the external dependencies of the project, just inter-module dependencies. Thanks Donnchadh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
