-
Bug
-
Resolution: Unresolved
-
Major
-
None
1. When I rename Maven installation - all dependent projects break down.
This happens because in project's config.xml you store that name as an identifier.
But from UI this is not so obvious that simple display name influences so much.
You should either edit this name in all projects or use some integer identifer.
Or at least - warn a user when he renames an installation that all dependent projects are going to break down.
2. The same cause but other consequence - if I created second Maven installation, used it somewhere but then removed it I get unresolvable problem.
Jobs that used removed installation cannot be revived without manual editing config.xml - in configuration I even cannot setup maven installation.
[JENKINS-19632] Using maven installation as an identifer causes data integrity errors
Description |
Original:
When I rename Maven installation - all projects break down. This happens because in config.xml you store that name as an identifier. But from UI this is not so obvious that simple display name influences so much. You should either edit this name in all projects or use some integer identifer. Or at least - warn a user when he renames an installation that all dependent projects are going to break down. |
New:
When I rename Maven installation - all projects break down. This happens because in project's config.xml you store that name as an identifier. But from UI this is not so obvious that simple display name influences so much. You should either edit this name in all projects or use some integer identifer. Or at least - warn a user when he renames an installation that all dependent projects are going to break down. |
Description |
Original:
When I rename Maven installation - all projects break down. This happens because in project's config.xml you store that name as an identifier. But from UI this is not so obvious that simple display name influences so much. You should either edit this name in all projects or use some integer identifer. Or at least - warn a user when he renames an installation that all dependent projects are going to break down. |
New:
1. When I rename Maven installation - all dependent projects break down. This happens because in project's config.xml you store that name as an identifier. But from UI this is not so obvious that simple display name influences so much. You should either edit this name in all projects or use some integer identifer. Or at least - warn a user when he renames an installation that all dependent projects are going to break down. 2. The same cause but other consequence - if I created second Maven installation, used it somewhere but then removed it I get unresolvable problem. Jobs that used removed installation cannot be revived without manual editing config.xml - in configuration I even cannot setup maven installation. |
Summary | Original: Renaming Maven installation causes all dependent projects to forget about it | New: Using maven installation as an identifer causes errors |
Summary | Original: Using maven installation as an identifer causes errors | New: Using maven installation as an identifer causes data integrity errors |
Workflow | Original: JNJira [ 151149 ] | New: JNJira + In-Review [ 177866 ] |