[jira] Created: (SUREFIRE-599) Logs console output multiple times (no. of times log output = the no. of test being run) for JUnit/XMLUnit tests

2010-02-02 Thread Mahender Didwania (JIRA)
Logs console output multiple times (no. of times log output = the no. of test 
being run) for JUnit/XMLUnit tests


 Key: SUREFIRE-599
 URL: http://jira.codehaus.org/browse/SUREFIRE-599
 Project: Maven Surefire
  Issue Type: Bug
  Components: JUnit 3.x support
Affects Versions: 2.5
 Environment: Ubuntu 9.04
Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+)
Java version: 1.6.0_16
OS name: "linux" version: "2.6.31-17-generic" arch: "i386" Family: "unix"
JUnit 3.8.2
Log4j 1.2.14
Reporter: Mahender Didwania


I have a test class (named ATest) written by extending the JUnit TestCase 
class.  This class has a few test methods which all call the same method on a 
class (named A) with different parameters, exactly once each.

Now the class A which is being tested logs to console using Apache log4j's 
ConsoleAppender, at INFO level.

In the first test method, a message is logged once (which is how it should be).
In the second test method, every log message is repeated once (so gets logged 
twice instead of once).
In the third test method, every log message is logged thrice.
...
and so on.  Please note that the method in class A is invoked only once by the 
written source-code in each of the test methods and logs only once.



-- 
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] Closed: (MASSEMBLY-246) The unpack setting, if set to false, results in total exclusion of the dependency .jar file from the assembly

2007-10-10 Thread Mahender Didwania (JIRA)

 [ 
http://jira.codehaus.org/browse/MASSEMBLY-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mahender Didwania closed MASSEMBLY-246.
---

Resolution: Fixed

Duplicate of MASSEMBLY-240

> The unpack setting, if set to false, results in total exclusion of the 
> dependency .jar file from the assembly
> -
>
> Key: MASSEMBLY-246
> URL: http://jira.codehaus.org/browse/MASSEMBLY-246
> Project: Maven 2.x Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 2.2-beta-1
> Environment: Ubuntu 7.04, i386, using the VirtualBox image
>Reporter: Mahender Didwania
>
> 
> zip-me
> 
> zip
> 
> false
> 
> 
> 
> 
> 
> false
> runtime
> 
> 
> 
> 
> target/classes
> 
> 
> 
> 

-- 
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] Created: (MASSEMBLY-246) The unpack setting, if set to false, results in total exclusion of the dependency .jar file from the assembly

2007-10-10 Thread Mahender Didwania (JIRA)
The unpack setting, if set to false, results in total exclusion of the 
dependency .jar file from the assembly
-

 Key: MASSEMBLY-246
 URL: http://jira.codehaus.org/browse/MASSEMBLY-246
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.2-beta-1
 Environment: Ubuntu 7.04, i386, using the VirtualBox image
Reporter: Mahender Didwania



zip-me

zip

false





false
runtime




target/classes





-- 
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] Created: (SUREFIRE-356) Maven 2.x surefire plugin fails with null pointer exception

2007-10-10 Thread Mahender Didwania (JIRA)
Maven 2.x surefire plugin fails with null pointer exception
---

 Key: SUREFIRE-356
 URL: http://jira.codehaus.org/browse/SUREFIRE-356
 Project: Maven Surefire
  Issue Type: Bug
  Components: plugin
Affects Versions: 2.3
 Environment: Ubuntu 7.04, i386, VirtualBox image
Reporter: Mahender Didwania



http://maven.apache.org/POM/4.0.0"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
Test
Test
0.0.1
jar


net.sourceforge.jexcelapi
jxl
2.6






org.apache.maven.plugins
maven-surefire-plugin







-- 
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] Created: (MASSEMBLY-335) 'attached' goal execution is not consistent (and fails for EasyEclipse server java 1.2.2.2 with .m2eclipse plugin on Ubuntu 8.04)

2008-07-03 Thread Mahender Didwania (JIRA)
'attached' goal execution is not consistent (and fails for EasyEclipse server 
java 1.2.2.2 with .m2eclipse plugin on Ubuntu 8.04)
-

 Key: MASSEMBLY-335
 URL: http://jira.codehaus.org/browse/MASSEMBLY-335
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.2-beta-2
 Environment: Ubuntu 8.04 Hardy Heron, Easy Eclipse java server 
distribution with m2eclipse plugin (www.easyeclipse.org), maven 2.0.9
Reporter: Mahender Didwania
 Attachments: pom.xml, src.xml

>From the build output for environment mentioned in Environment:

...
Diagnosis: Internal error in the plugin manager executing goal 
'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error 
adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into plugin 
manager: Cannot add jar resource: 
/home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
 (error discovering new components)
FATAL ERROR: Error executing Maven for a project
[ERROR] reactor-execute : /home/developer/eclipse.workspace/PIDataLoad-PFR_F
Diagnosis: Internal error in the plugin manager executing goal 
'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error 
adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into plugin 
manager: Cannot add jar resource: 
/home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
 (error discovering new components)
FATAL ERROR: Error executing Maven for a project
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Internal error in the plugin manager executing goal 
'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error 
adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into plugin 
manager: Cannot add jar resource: 
/home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
 (error discovering new components)
Component descriptor role: 
'org.codehaus.plexus.archiver.manager.ArchiverManager', implementation: 
'org.codehaus.plexus.archiver.manager.DefaultArchiverManager', role hint: 
'default' has a hint, but implementation 
org.codehaus.plexus.archiver.manager.DefaultArchiverManager doesn't
...


Note that if I use Windows XP SP2, maven 2.0.9, the Eclipse distribution 
3.3.1.1 with .m2eclipse plugin installed from 
http://m2eclipse.sonatype.org/update/ , then I get a warning (instead of error) 
during the build, as follows:
...
[WARNING]

DEPRECATED: Binding aggregator mojos to lifecycle phases in the POM is 
considered dangerous.
This feature has been deprecated.  Please adjust your POM files accordingly.

Offending mojo:

org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-1:attached
...
(Since when has this been deprecated, what is the workaround?  Is the error I 
face in any way related to this?)


Note that if I perform the build from the command line using mvn package, the 
build succeeds but all my .jar files in Support/lib end up with the same name 
within the created assembly (.zip), that name is PFR4700.${extension}.  I am 
attaching the pom.xml and src.xml (assembly descriptor).



-- 
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: (MASSEMBLY-335) 'attached' goal execution is not consistent (and fails for EasyEclipse server java 1.2.2.2 with .m2eclipse plugin on Ubuntu 8.04)

2008-07-03 Thread Mahender Didwania (JIRA)

[ 
http://jira.codehaus.org/browse/MASSEMBLY-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140374#action_140374
 ] 

Mahender Didwania commented on MASSEMBLY-335:
-

Update: Build from command line is now atleast consistently succeeding (for 
both the version on Windows and the one on Ubuntu, which apparently use 
different versions of the maven-assembly-plugin though both are maven 2.0.9!!). 
 I had to prefix artifactId with artifact, similarly I had to prefix the 
extension with artifact.extension in src.xml.

So, the only problem now is: version 2.2-beta-2 fails for the attached goal (on 
Ubuntu 8.04) and version 2.2-beta-1 gives a deprecated warning for the same (on 
Windows).

> 'attached' goal execution is not consistent (and fails for EasyEclipse server 
> java 1.2.2.2 with .m2eclipse plugin on Ubuntu 8.04)
> -
>
> Key: MASSEMBLY-335
> URL: http://jira.codehaus.org/browse/MASSEMBLY-335
> Project: Maven 2.x Assembly Plugin
>  Issue Type: Bug
>Affects Versions: 2.2-beta-2
> Environment: Ubuntu 8.04 Hardy Heron, Easy Eclipse java server 
> distribution with m2eclipse plugin (www.easyeclipse.org), maven 2.0.9
>Reporter: Mahender Didwania
> Attachments: pom.xml, src.xml
>
>
> From the build output for environment mentioned in Environment:
> ...
> Diagnosis: Internal error in the plugin manager executing goal 
> 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error 
> adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into 
> plugin manager: Cannot add jar resource: 
> /home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
>  (error discovering new components)
> FATAL ERROR: Error executing Maven for a project
> [ERROR] reactor-execute : /home/developer/eclipse.workspace/PIDataLoad-PFR_F
> Diagnosis: Internal error in the plugin manager executing goal 
> 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error 
> adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into 
> plugin manager: Cannot add jar resource: 
> /home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
>  (error discovering new components)
> FATAL ERROR: Error executing Maven for a project
> [INFO] 
> 
> [ERROR] BUILD ERROR
> [INFO] 
> 
> [INFO] Internal error in the plugin manager executing goal 
> 'org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached': Error 
> adding plugin dependency 'org.codehaus.plexus:plexus-archiver:jar' into 
> plugin manager: Cannot add jar resource: 
> /home/developer/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-10/plexus-archiver-1.0-alpha-10.jar
>  (error discovering new components)
> Component descriptor role: 
> 'org.codehaus.plexus.archiver.manager.ArchiverManager', implementation: 
> 'org.codehaus.plexus.archiver.manager.DefaultArchiverManager', role hint: 
> 'default' has a hint, but implementation 
> org.codehaus.plexus.archiver.manager.DefaultArchiverManager doesn't
> ...
> Note that if I use Windows XP SP2, maven 2.0.9, the Eclipse distribution 
> 3.3.1.1 with .m2eclipse plugin installed from 
> http://m2eclipse.sonatype.org/update/ , then I get a warning (instead of 
> error) during the build, as follows:
> ...
> [WARNING]
> DEPRECATED: Binding aggregator mojos to lifecycle phases in the POM is 
> considered dangerous.
> This feature has been deprecated.  Please adjust your POM files accordingly.
> Offending mojo:
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-1:attached
> ...
> (Since when has this been deprecated, what is the workaround?  Is the error I 
> face in any way related to this?)
> Note that if I perform the build from the command line using mvn package, the 
> build succeeds but all my .jar files in Support/lib end up with the same name 
> within the created assembly (.zip), that name is PFR4700.${extension}.  I am 
> attaching the pom.xml and src.xml (assembly descriptor).

-- 
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