[jira] Issue Comment Edited: (MNG-4471) Profile activation fails if contains variables

2009-11-27 Thread J C (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199813#action_199813
 ] 

J C edited comment on MNG-4471 at 11/27/09 6:12 PM:


I can't seem to attach the file, so here's testcase2.xml:

{noformat} 


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
  testcase2
  testcase2
  1.0
  
  
.
  
  
  

  testcase2
  

  ${test.prop}/testcase2.xml

  


  absolute path
  

  ./testcase2.xml

  

  

{noformat} 

  was (Author: j4zzcat):
I can't seem to attach the file, so here's testcase2.xml:



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
  testcase2
  testcase2
  1.0
  
  
.
  
  
  

  testcase2
  

  ${test.prop}/testcase2.xml

  


  absolute path
  

  ./testcase2.xml

  

  


  
> Profile activation fails if  contains variables 
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
>  Issue Type: Bug
>  Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when  has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn

-- 
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: (MNG-4471) Profile activation fails if contains variables

2009-11-27 Thread J C (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199813#action_199813
 ] 

J C commented on MNG-4471:
--

I can't seem to attach the file, so here's testcase2.xml:



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
  testcase2
  testcase2
  1.0
  
  
.
  
  
  

  testcase2
  

  ${test.prop}/testcase2.xml

  


  absolute path
  

  ./testcase2.xml

  

  



> Profile activation fails if  contains variables 
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
>  Issue Type: Bug
>  Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when  has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn

-- 
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] Updated: (MNG-4471) Profile activation fails if contains variables

2009-11-27 Thread J C (JIRA)

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

J C updated MNG-4471:
-

Attachment: testcase2.xml

> Profile activation fails if  contains variables 
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
>  Issue Type: Bug
>  Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when  has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn

-- 
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] Updated: (MNG-4471) Profile activation fails if contains variables

2009-11-27 Thread J C (JIRA)

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

J C updated MNG-4471:
-

Attachment: testcase2.xml

To reproduce:
1. Run "mvn -f testcase2.xml help:active-profiles"
2. Expected result: both profiles should have been activated;
   Observed result: only one profile is activated, 
   the "testcase2" profile is not activated. 


> Profile activation fails if  contains variables 
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
>  Issue Type: Bug
>  Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml, testcase2.xml
>
>
> See the attached testcase.
> The profile is not activated when  has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn

-- 
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] Reopened: (MNG-4471) Profile activation fails if contains variables

2009-11-27 Thread J C (JIRA)

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

J C reopened MNG-4471:
--


I'm attaching a better testcase that shows the issue.

> Profile activation fails if  contains variables 
> --
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
>  Issue Type: Bug
>  Components: Profiles
>Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
>Reporter: J C
>Assignee: Benjamin Bentmann
> Attachments: pom.xml, testcase.xml
>
>
> See the attached testcase.
> The profile is not activated when  has variables in it:
> ${env.M2_HOME}/bin/mvn
> But when the path is absolute, it works:
> /my/maven/home/bin/mvn

-- 
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: (MNG-4471) Profile activation fails if contains variables

2009-11-27 Thread J C (JIRA)
Profile activation fails if  contains variables 
--

 Key: MNG-4471
 URL: http://jira.codehaus.org/browse/MNG-4471
 Project: Maven 2
  Issue Type: Bug
  Components: Profiles
Affects Versions: 3.0-alpha-5
 Environment: Mac OS X 10.6.2
Reporter: J C
 Attachments: testcase.xml

See the attached testcase.

The profile is not activated when  has variables in it:
${env.M2_HOME}/bin/mvn

But when the path is absolute, it works:
/my/maven/home/bin/mvn


-- 
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: (MSUREFIREREP-22) Aggragated surefire report from modules

2006-11-02 Thread J-C (JIRA)
[ 
http://jira.codehaus.org/browse/MSUREFIREREP-22?page=comments#action_79087 ] 

J-C commented on MSUREFIREREP-22:
-

Structure of my demo is :

Sample(packaging pom)
---> sample 1 (jar with some failure in testcase)
>sample 2 (jar with some failure in testcase)
>sample 3 (packaging pom)
  >sample 4 (jar with some failure in 
testcase)


It is a project with several level of modules

> Aggragated surefire report from modules
> ---
>
> Key: MSUREFIREREP-22
> URL: http://jira.codehaus.org/browse/MSUREFIREREP-22
> Project: Maven 2.x Surefire report Plugin
>  Issue Type: New Feature
>Affects Versions: 2.0
> Environment: all
>Reporter: Bugittaa Pahasti
> Attachments: patch.patch, report.JPG
>
>
> Aggregated surefire report from child modules. I think this has been 
> discussed in the mailing lists, but seemed not to be on Jira yet.

-- 
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] Updated: (MSUREFIREREP-22) Aggragated surefire report from modules

2006-11-02 Thread J-C (JIRA)
 [ http://jira.codehaus.org/browse/MSUREFIREREP-22?page=all ]

J-C updated MSUREFIREREP-22:


Attachment: patch.patch
report.JPG

I patch surefire-reporting 2.0 to include an report for pom packaging. 

In 2.0, report is done only if language is java. In my patch it is also apply 
on pom packaging file. 

When packaging is pom, it checked for modules and create a report page that 
contains the total number of test executed, failed, ...

If there is some failure, test in failure are listed ordered by module. It 
supports several level of modules. A hyperlink on the module title allow to 
navigate to the reporting page of the module

I tried it on a sample project:

Sample(packaging pom)
  |---> sample 1 (jar with some failure in testcase)
  |>sample 2 (jar with some failure in testcase)
  |>sample 3 (packaging pom)
   |>sample 4 (jar with some failure in testcase)

Aggregated report looks like report.jpg

Problem is that before running the plugin tests must have been executed. 

It might be a nice feature to include that patch in surefire-reporting ...

> Aggragated surefire report from modules
> ---
>
> Key: MSUREFIREREP-22
> URL: http://jira.codehaus.org/browse/MSUREFIREREP-22
> Project: Maven 2.x Surefire report Plugin
>  Issue Type: New Feature
>Affects Versions: 2.0
> Environment: all
>Reporter: Bugittaa Pahasti
> Attachments: patch.patch, report.JPG
>
>
> Aggregated surefire report from child modules. I think this has been 
> discussed in the mailing lists, but seemed not to be on Jira yet.

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