You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Alexander Vaysberg <wo...@vaisberg.de> on 2011/01/14 15:08:26 UTC

Problem with properties in Maven.

Hi,

I think, that I a one problem with properties in maven found. The
problem in pom with properties. If any know any other properties, which
worked same. Please say. Thank you.

 The Problem can you reproduce with maven 2.2.1 and maven 3.0.1 in
plug-in surefire. I create the property test:
...
<properties>
      <jmockit-ver>0.998</jmockit-ver>
      <junit-ver>4.8.2</junit-ver>
      <test>bla</test>
  </properties>
...
and if I call mvn clean package test don't worked:
on the version 2.2.1

[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] No tests were executed!  (Set -DfailIfNoTests=false to ignore
this error.)
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch

and 3.0.1

[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.087s
[INFO] Finished at: Fri Jan 14 15:01:48 CET 2011
[INFO] Final Memory: 6M/119M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test)
on project test: No tests were executed!  (Set -DfailIfNoTests=false to
ignore this error.) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

The Output for surefire :

#surefire
#Fri Jan 14 15:00:57 CET 2011
testClassesDirectory=/work/Projekts/test/test/target/test-classes
classPathUrl.3=/work/repo/maven/mockit/jmockit/0.998/jmockit-0.998.jar
classPathUrl.2=/work/repo/maven/junit/junit/4.8.2/junit-4.8.2.jar
useManifestOnlyJar=true
classPathUrl.1=/work/Projekts/test/test/target/classes
reportsDirectory=/work/Projekts/test/test/target/surefire-reports
classPathUrl.0=/work/Projekts/test/test/target/test-classes
dirscanner.0=directoryScannerOptions
providerConfiguration=org.apache.maven.surefire.junitcore.JUnitCoreProvider
testSuiteDefinitionTestSourceDirectory=/work/Projekts/test/test/src/test/java
surefireClassPathUrl.2=/work/repo/maven/org/apache/maven/surefire/surefire-api/2.7.1/surefire-api-2.7.1.jar
requestedTest=bla
surefireClassPathUrl.1=/work/repo/maven/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
surefireClassPathUrl.0=/work/repo/maven/org/apache/maven/surefire/surefire-junit47/2.7.1/surefire-junit47-2.7.1.jar
report.2=org.apache.maven.surefire.report.XMLReporter
useSystemClassLoader=true
report.1=org.apache.maven.surefire.report.BriefFileReporter
report.0=org.apache.maven.surefire.report.ForkingConsoleReporter
isTrimStackTrace=true
dirscanner.0.params=/work/Projekts/test/test/target/test-classes|[**/bla.java]|[]
enableAssertions=true
failIfNoTests=true
dirscanner.0.types=java.io.File|java.util.ArrayList|java.util.ArrayList
includes0=**/bla.java
parallel=false
childDelegation=false



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Problem with properties in Maven.

Posted by Alexander Vaysberg <wo...@vaisberg.de>.
yes, now i know it. But think this part must be on separate scope. Not
globally for alls, or?
If it's globally, than it any must write, which name of the properties
don't be used, or?
Am 14.01.2011 15:52, schrieb Siegmar Alber:
> Hi Alexander,
>
>
> 2011/1/14 Alexander Vaysberg <wo...@vaisberg.de>:
>> I think, that I a one problem with properties in maven found. The
>> problem in pom with properties. If any know any other properties, which
>> worked same. Please say. Thank you.
>>
>> ...
>> <properties>
>>      <jmockit-ver>0.998</jmockit-ver>
>>      <junit-ver>4.8.2</junit-ver>
>>      <test>bla</test>
>>  </properties>
>> ...
> with the "test" property you (accidentally?) set a parameter of the
> surefire-plugin[1]. Remove or rename your property and it should work
> :-)
>
> [1] http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#test
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Problem with properties in Maven.

Posted by Siegmar Alber <si...@gmail.com>.
Hi Alexander,


2011/1/14 Alexander Vaysberg <wo...@vaisberg.de>:
>
> I think, that I a one problem with properties in maven found. The
> problem in pom with properties. If any know any other properties, which
> worked same. Please say. Thank you.
>
> ...
> <properties>
>      <jmockit-ver>0.998</jmockit-ver>
>      <junit-ver>4.8.2</junit-ver>
>      <test>bla</test>
>  </properties>
> ...

with the "test" property you (accidentally?) set a parameter of the
surefire-plugin[1]. Remove or rename your property and it should work
:-)

[1] http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#test

-- 
Have fun,
Siegmar

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Problem with properties in Maven.

Posted by Alexander Vaysberg <wo...@vaisberg.de>.
No Problem, i create the simple maven project with 2 classes and simple
test. You can it's try.

Attachment: test.zip.
Am 14.01.2011 15:39, schrieb Wendy Smoak:
> On Fri, Jan 14, 2011 at 9:08 AM, Alexander Vaysberg <wo...@vaisberg.de> wrote:
>> I think, that I a one problem with properties in maven found. The
>> problem in pom with properties. If any know any other properties, which
>> worked same. Please say. Thank you.
>>
>>  The Problem can you reproduce with maven 2.2.1 and maven 3.0.1 in
>> plug-in surefire. I create the property test:
>> ...
>> <properties>
>>      <jmockit-ver>0.998</jmockit-ver>
>>      <junit-ver>4.8.2</junit-ver>
>>      <test>bla</test>
>>  </properties>
> Can you post more of the pom?  Where in the pom are the properties
> defined, and how are you using the properties elsewhere in the pom?
>
> If you can create a simple example project that demonstrates the
> problem, that's probably the quickest way to get someone to take a
> look.
>


Re: Problem with properties in Maven.

Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Jan 14, 2011 at 9:08 AM, Alexander Vaysberg <wo...@vaisberg.de> wrote:
> I think, that I a one problem with properties in maven found. The
> problem in pom with properties. If any know any other properties, which
> worked same. Please say. Thank you.
>
>  The Problem can you reproduce with maven 2.2.1 and maven 3.0.1 in
> plug-in surefire. I create the property test:
> ...
> <properties>
>      <jmockit-ver>0.998</jmockit-ver>
>      <junit-ver>4.8.2</junit-ver>
>      <test>bla</test>
>  </properties>

Can you post more of the pom?  Where in the pom are the properties
defined, and how are you using the properties elsewhere in the pom?

If you can create a simple example project that demonstrates the
problem, that's probably the quickest way to get someone to take a
look.

-- 
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Problem with properties in Maven.

Posted by Justin Edelson <ju...@justinedelson.com>.
How is this a problem? You're telling surefire to execute a test which doesn't exist and this causes a failure. This seems like the expected behavior.

On Jan 14, 2011, at 9:08 AM, Alexander Vaysberg <wo...@vaisberg.de> wrote:

> Hi,
> 
> I think, that I a one problem with properties in maven found. The
> problem in pom with properties. If any know any other properties, which
> worked same. Please say. Thank you.
> 
> The Problem can you reproduce with maven 2.2.1 and maven 3.0.1 in
> plug-in surefire. I create the property test:
> ...
> <properties>
>      <jmockit-ver>0.998</jmockit-ver>
>      <junit-ver>4.8.2</junit-ver>
>      <test>bla</test>
>  </properties>
> ...
> and if I call mvn clean package test don't worked:
> on the version 2.2.1
> 
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] No tests were executed!  (Set -DfailIfNoTests=false to ignore
> this error.)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> 
> and 3.0.1
> 
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1.087s
> [INFO] Finished at: Fri Jan 14 15:01:48 CET 2011
> [INFO] Final Memory: 6M/119M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test)
> on project test: No tests were executed!  (Set -DfailIfNoTests=false to
> ignore this error.) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> 
> The Output for surefire :
> 
> #surefire
> #Fri Jan 14 15:00:57 CET 2011
> testClassesDirectory=/work/Projekts/test/test/target/test-classes
> classPathUrl.3=/work/repo/maven/mockit/jmockit/0.998/jmockit-0.998.jar
> classPathUrl.2=/work/repo/maven/junit/junit/4.8.2/junit-4.8.2.jar
> useManifestOnlyJar=true
> classPathUrl.1=/work/Projekts/test/test/target/classes
> reportsDirectory=/work/Projekts/test/test/target/surefire-reports
> classPathUrl.0=/work/Projekts/test/test/target/test-classes
> dirscanner.0=directoryScannerOptions
> providerConfiguration=org.apache.maven.surefire.junitcore.JUnitCoreProvider
> testSuiteDefinitionTestSourceDirectory=/work/Projekts/test/test/src/test/java
> surefireClassPathUrl.2=/work/repo/maven/org/apache/maven/surefire/surefire-api/2.7.1/surefire-api-2.7.1.jar
> requestedTest=bla
> surefireClassPathUrl.1=/work/repo/maven/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar
> surefireClassPathUrl.0=/work/repo/maven/org/apache/maven/surefire/surefire-junit47/2.7.1/surefire-junit47-2.7.1.jar
> report.2=org.apache.maven.surefire.report.XMLReporter
> useSystemClassLoader=true
> report.1=org.apache.maven.surefire.report.BriefFileReporter
> report.0=org.apache.maven.surefire.report.ForkingConsoleReporter
> isTrimStackTrace=true
> dirscanner.0.params=/work/Projekts/test/test/target/test-classes|[**/bla.java]|[]
> enableAssertions=true
> failIfNoTests=true
> dirscanner.0.types=java.io.File|java.util.ArrayList|java.util.ArrayList
> includes0=**/bla.java
> parallel=false
> childDelegation=false
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org