Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Invalid
-
None
-
None
-
None
-
None
Description
If you stupidly tell two different @Components to use the same configurationPid, one of them will just get stuck, and neither bundle:services nor any of the scr commands will reveal what the problem is. It sure would be nice to have a log message, or some detail from one of the commands.