[jira] (MECLIPSE-712) filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin

2013-08-28 Thread Nicolas Ternisien (JIRA) 

[ 
https://jira.codehaus.org/browse/MECLIPSE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332043#comment-332043
 ] 

Nicolas Ternisien commented on MECLIPSE-712:


Any news on this?

Thanks!

 filteredResources in Eclipse .project is not supported and discarded by the 
 Maven 2.x Eclipse Plugin
 

 Key: MECLIPSE-712
 URL: https://jira.codehaus.org/browse/MECLIPSE-712
 Project: Maven Eclipse Plugin
  Issue Type: Bug
  Components: Core : .project
Affects Versions: 2.8
 Environment: Maven 3, Windows 7, Eclipse Indigo Service Release 1
Reporter: René de Bloois
 Attachments: screenshot-1.jpg


 There is a beautiful way to let Eclipse ignore the target folder:
 {code:xml|title=.project}
 ?xml version=1.0 encoding=UTF-8?
 projectDescription
   ...
   filteredResources
   filter
   id1328280594689/id
   name/name
   type10/type
   matcher
   idorg.eclipse.ui.ide.multiFilter/id
   
 arguments1.0-projectRelativePath-matches-true-false-target/arguments
   /matcher
   /filter
   /filteredResources
 /projectDescription
 {code}
 Which in Eclipse means (in the Edit Resource Filter window): Exclude all, 
 Folders, not recursive, Project Relative Path matches target case 
 sensitive.
 This will cause Eclipse to completely ignore this folder and its contents.
 Problem is, after running mvn eclipse:eclipse, this section is removed from 
 the .project file.
 It is also not possible to configure the maven eclipse plugin to add this 
 filteredResources section.
 Maybe it could even be generated by default by the maven eclipse plugin?

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

[jira] (SUREFIRE-1025) TestSetRunListener.testSetCompleted() should write files first before reporting the completion on console.

2013-08-28 Thread Milos Kleint (JIRA) 
Milos Kleint created SUREFIRE-1025:
--

 Summary: TestSetRunListener.testSetCompleted() should write files 
first before reporting the completion on console.
 Key: SUREFIRE-1025
 URL: https://jira.codehaus.org/browse/SUREFIRE-1025
 Project: Maven Surefire
  Issue Type: Bug
  Components: Maven Surefire Plugin
Affects Versions: 2.15
Reporter: Milos Kleint


TestSetRunListener.testSetCompleted() currently prints out the output to the 
console first and only then writes the report xml file. That's causing problems 
in situations when other tools parse the output and want to access the report 
file at the same time.
see issue https://netbeans.org/bugzilla/show_bug.cgi?id=227541

This issue is created to suggest the output to console should be the last thing 
done.

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

[jira] (MDEP-427) Add user property for addParentPoms option

2013-08-28 Thread Devin Reid (JIRA) 
Devin Reid created MDEP-427:
---

 Summary: Add user property for addParentPoms option
 Key: MDEP-427
 URL: https://jira.codehaus.org/browse/MDEP-427
 Project: Maven Dependency Plugin
  Issue Type: New Feature
  Components: copy-dependencies
Affects Versions: 2.8
Reporter: Devin Reid


An boolean option to include parent poms for the copy-dependenices mojo was 
added to 2.8, but did not include a way to set the option from the command 
line. An user property should be added that sets this options. My suggestion is 
mdep.addParentPoms to match the style of the other user options.

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