|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I just noticed this today when upgrading from Jenkins ver. 1.466 to 1.554.1. Where did my nice /slave1/tools/JDK/... directory go?
I agree with the localization comment. I might have suggested a specific dirname property to say, "Java JDK's get installed to the JDK folder".
However, in considering this issue more, using the id and thus the full class name is genius. Consider if you have two plugins, each managing a Foo. FooPlugin1 and FooPlugin2 want to create a tools/foo directory. Not a problem, unless BOTH are installed. In this case you have two plugins using the same tools/foo directory. Bad.
Using the classname creates tools/foo.vendor1.com and tools/foo.vendor2.org. Collision prevented.
This, of course, assumes there is no whitespace in the ID, else Windows throws up.