José Morales Martínez wrote:
I will try to solve this problem. This week I am a little busy, but I will try to fix it as soon as possible. Many times to change the name of a field leads to the occurrence of these errors. I think it may be due to this.

I download trunk in r767890  and install, but I get the following error when I 
run mvn install on continuum-webapp-test:

This is for testng-pom.xml and pom.xml.

Anyone happens the same?

yeah, i encountered that Build Error too. what i did was excluding the banned dependency in pom and then build it again. :)

/continuum-webapp-test$ mvn install -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Continuum :: Webapp Tests
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed 
with message:
Found Banned Dependency: commons-logging:commons-logging:jar:1.0.4

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Some Enforcer rules have failed. Look above for specific messages 
explaining why the rule failed.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Some Enforcer rules 
have failed. Look above for specific messages explaining why the rule failed.
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
        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: Some Enforcer rules 
have failed. Look above for specific messages explaining why the rule failed.
        at 
org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:217)
        at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
        at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
        ... 16 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Apr 23 13:29:17 CEST 2009
[INFO] Final Memory: 13M/522M
[INFO] ------------------------------------------------------------------------


________________________________________
De: Marecor Baclay [[email protected]]
Enviado el: jueves, 23 de abril de 2009 2:06
Para: [email protected]
Asunto: Re: Selenium test failures

Wendy Smoak wrote:
I can now run the TestNG webapp tests, but I'm seeing four failures:

Failed tests:
  
testAddMavenTwoProjectFromRemoteSourceToNonDefaultProjectGroup(org.apache.continuum.web.test.MavenTwoProjectTest)
  testAddMavenTwoProject(org.apache.continuum.web.test.MavenTwoProjectTest)
  
testAddMavenToolWithBuildEnvirotment(org.apache.continuum.web.test.InstallationTest)
  
testAddJdkToolWithoutBuildEnvirotment(org.apache.continuum.web.test.InstallationTest)

Tests run: 142, Failures: 4, Errors: 0, Skipped: 49

Are they passing for others?



I got same results as pasted above too.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion.
______________________
This message including any attachments may contain confidential information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.
______________________


Reply via email to