[jira] (SUREFIRE-726) Test list preprocessor support for tests to be run

2012-04-16 Thread Daniele Dellafiore (JIRA)

[ 
https://jira.codehaus.org/browse/SUREFIRE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296564#comment-296564
 ] 

Daniele Dellafiore commented on SUREFIRE-726:
-

Hi. I step into this issue lookig for a way to have a sort of global test 
setup, without having to deal with suites. 
The purpose is to have a reset of the whole database and reimport of test data 
at the beginning of the tests, and not pay the reset/reimport on every single 
test case. 
Maybe this is a nice way to address my problem, what do you think>

> Test list preprocessor support for tests to be run
> --
>
> Key: SUREFIRE-726
> URL: https://jira.codehaus.org/browse/SUREFIRE-726
> Project: Maven Surefire
>  Issue Type: New Feature
>Affects Versions: 2.9
>Reporter: Janmejay Singh
> Fix For: 3.0
>
> Attachments: 
> 0001-Adds-test-list-preprocessor-support-which-loads-an-o.patch, 
> 0002-Integration-test-for-preprocessor.-2-modules-one-pro.patch, 
> 0003-exposed-testPreprocessor-configuration-parameter-as-.patch, 
> 0004-exposed-testPreprocessor-for-IntegrationTestMojo-as-.patch
>
>
> This exposes an interface(named TestListPreprocessor, which has a method 
> named preprocessTestClasses) that can be implemented by a user and injected 
> into surefire plugin configuration to have it used for preprocessing list of 
> tests to be run. Given the original test list, user's preprocessing algorithm 
> can choose to prune or reorder the list and return it back from 
> TestListPreprocessor#preprocessTestClasses, which is then used as the list of 
> tests to be executed.
> The patches attached expose a configuration element named "testPreprocessor" 
> the default value of which is "none". User can choose to set it to a value 
> matching the format 
> "[::]" and have 
> the class loaded and called with list of tests to be run. The list of tests 
> returned by the call is then considered for execution.
> Patch description:
> The feature is done in 2 patches. Description follows:
> 0001-Adds-test-list-preprocessor-support-which-loads-an-o.patch
> This patch actually adds the feature and unit tests. It adds the interface, 
> an abstraction that encapsulates aforementioned configuration, booter 
> serialization/deserialization, directory-scanner changes etc. The changes 
> have effect in both forked and in-process execution mode.
> 0002-Integration-test-for-preprocessor.-2-modules-one-pro.patch
> This patch adds an integration test for preprocessor feature. The integration 
> test uses a 2 module setup, where the first module implements the 
> TestListPreprocessor interface which selects only even indexed test classes 
> from the list passed in. The second module(which depends on first) uses the 
> artifact from first and uses the following configuration:
> 
> 
>   
> test.preprocessor.EvenTestOnlyPreprocessor[org.apache.maven.plugins.surefire:preprocessor-impl:1.0-SNAPSHOT]
> 
> 
> The test then asserts that only 2(0th and 2nd) of the 4 test classes the 
> second module has are executed.
> The patches are created on a git-svn clone using format-patch, please use 
> 'patch -p1 < 0001-Adds...'(while in the trunk directory) to apply the patches 
> on svn repository. If using git-svn, git-am can be directly be invoked.
> The patches are done over 
> http://svn.apache.org/repos/asf/maven/surefire/trunk@1091357 (trunk HEAD) so 
> should apply cleanly on any recent enough revision.
> ===
> Context:
> http://stackoverflow.com/questions/5124823/reducing-the-build-time-hudson
> http://code.google.com/p/tlb/issues/detail?id=1
> http://test-load-balancer.github.com

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Created: (MECLIPSE-659) eclipse-plugin does not create .classpath and .project files for projects with packaging pom

2010-06-10 Thread Daniele Dellafiore (JIRA)
eclipse-plugin does not create .classpath and .project files for projects with 
packaging pom


 Key: MECLIPSE-659
 URL: http://jira.codehaus.org/browse/MECLIPSE-659
 Project: Maven 2.x Eclipse Plugin
  Issue Type: Bug
  Components: Core : Multi-projects
Affects Versions: 2.8
 Environment: any
Reporter: Daniele Dellafiore


mvn eclipse:eclipse does not generate eclipse .project and .classpath files 
from any pom.xml file that has packaging set to POM. 


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (MINSTALL-54) [INFO] Error installing artifact's metadata

2009-12-01 Thread Daniele Dellafiore (JIRA)

[ 
http://jira.codehaus.org/browse/MINSTALL-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200152#action_200152
 ] 

Daniele Dellafiore commented on MINSTALL-54:


I received this error as well, not on my machine, just on the machine where 
runs Hudson. 
I manage to make it back to work removing the maven-metadata-local.xml in the 
folder 
/home/boxo-proto/.m2/repository/net/phaedra/phaedra-commons/0.6.2/

Both my machine and CI server run with ubuntu 9.10, sun JDK 6.

here was the output:

[INFO] [jar:jar {execution: default-jar}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/boxo-proto/.hudson/jobs/phaedra/workspace/phaedra/phaedra-commons/target/phaedra-commons-0.6.2.jar
 to 
/home/boxo-proto/.m2/repository/net/phaedra/phaedra-commons/0.6.2/phaedra-commons-0.6.2.jar
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error installing artifact's metadata: Error installing metadata: Error 
updating group repository metadata

input contained no data
[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error installing 
artifact's metadata: Error installing metadata: Error updating group repository 
metadata


Here the complete stack trace:

org.apache.maven.lifecycle.LifecycleExecutionException: Error installing 
artifact's metadata: Error installing metadata: Error updating group repository 
metadata
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.MojoExecutionException: Error installing 
artifact's metadata: Error installing metadata: Error updating group repository 
metadata
at 
org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:143)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: 
Error installing artifact's metadata: Error installing metadata: Error updating 
group repository metadata
at 
org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:123)
at 
org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:105)
... 19 more
Caused by: 
org.apache.maven.artifact.repository.metadata.RepositoryMetadataInstallationException:
 Error installing metadata: Error updating group repository metadata
at 
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.install(DefaultRepositoryMetadataManager.java:462)
at 
org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:111)
... 20 more
Caused by: 
org.apache.maven.artifact.repository.metadata.RepositoryMetadataStoreException: 
Error updating group repository metadata
at 
org.apache.maven.artifact.repository.metadata.AbstractRepositoryMetadata.storeInLocalRepository(AbstractRepositoryMetadata.java:72)
at 
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManag