[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target

2015-10-05 Thread ar...@arendvr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arend v. Reinersdorff commented on  JENKINS-29093 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POM location is deleted when changing Maven top-level target  
 
 
 
 
 
 
 
 
 
 
POM location is no longer deleted with version 1.44. Thanks a lot  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target

2015-09-25 Thread mdono...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mdonohue resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in the 1.44 version of configurationslicing 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29093 
 
 
 
  POM location is deleted when changing Maven top-level target  
 
 
 
 
 
 
 
 
 

Change By:
 
 mdonohue 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target

2015-09-17 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29093 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: POM location is deleted when changing Maven top-level target  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Michael Donohue Path: .project pom.xml src/main/java/configurationslicing/executeshell/MavenTargetsSlicer.java http://jenkins-ci.org/commit/configurationslicing-plugin/120e5ee47bfdb1551755fbcd831a979159cc9071 Log: Copy all existing maven config values to newly created builder 
JENKINS-29093 The Maven top-level target slicer was trying to be careful about the maven installation version used, but this ends up breaking other maven settings when the default maven installation is used. 
The fix is to copy the config values if we have an old maven builder, regardless of whether it has a maven installation version set. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target

2015-07-21 Thread als...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Java updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29093 
 
 
 
  POM location is deleted when changing Maven top-level target  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexey Java 
 
 
 

Priority:
 
 Minor Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target

2015-07-21 Thread als...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Java commented on  JENKINS-29093 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: POM location is deleted when changing Maven top-level target  
 
 
 
 
 
 
 
 
 
 
I think all data corruption bugs should have critical priority. it's one thing when data is not updated / ignored, but it's much worse when plugin can erase/damage existing data. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target

2015-06-26 Thread ar...@arendvr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Arend v. Reinersdorff created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29093 
 
 
 
  POM location is deleted when changing Maven top-level target  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 mdonohue 
 
 
 

Components:
 

 configurationslicing-plugin 
 
 
 

Created:
 

 26/Jun/15 8:32 AM 
 
 
 

Environment:
 

 Jenkins 1.6.10  Configuration Slicing Plugin 1.40 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Arend v. Reinersdorff 
 
 
 
 
 
 
 
 
 
 
I noticed that setting the Maven top-level target for a job deletes the job's POM location setting. 
I can reproduce this as follows: 
 

There's a freestyle project with a Maven Build step. The Goals are clean verify, the POM location is myproject-parent/pom.xml.
 

Change the Maven goal with the Configuration Slicing Plugin to clean package
 
 
Result: The POM location is empty.