![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
mdonohue
|
|
Components:
|
configurationslicing |
|
Created:
|
22/Jun/13 11:22 PM
|
|
Description:
|
From 1.36 to 1.37 something changed so we now see all modules of all our maven projects as separately configurable in configuration slicing.
Due to the number of projects and the huge number of modules within each of them, configuration slicing lost much of its usability.
Maybe the noted change "add support for folders" brought this change.
Would be nice to have a global config switch to set configuration slicing to default to the old behaviour no longer showing every single maven module in config slicing lists when not explicitely chosen to do so.
Reverting to 1.36 from 1.37 brought back the old behaviour for us so we can see again our projects without every single maven module listed besides them.
|
|
Environment:
|
Debian 7.0 amd64 , Oracle JRE 7.0u17 x64 , Tomcat 7.0.40 , Jenkins 1.509.1 , de_DE.UTF-8
|
|
Project:
|
Jenkins
|
|
Labels:
|
configuration
plugin
lts-candidate
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Tim-Christian Bloss
|
|
|
|
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
|
--
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/groups/opt_out.
