> > Most likely you do not need it, because you can implement a standalone > ToolInstaller. But such switch is a good option for generic installers as > well. >
Aha, so making a standalone ToolInstaller should work then? What needs to be done in a standalone in order for this to work? Should I copy the behavior of FilePath's installIfNecessary(...) into my performInstallation(...) regarding connections and so on? Will this ultimately end up like a copy of FilePath of some sort? Here is a link <https://github.com/Preyfix/HMS-Examensarbete> to my Github repository with my current RAR extractor if you want to see. It uses String file paths to point where the RAR file is and where to extract the content on the local computer. How should the extractor know where to extract a file in this standalone installer? Using strings won't work, will it? So many questions, haha. Thanks again for helping me. Sincerely, Martin Hjelmqvist -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9bafbc5e-7bce-4566-809a-99244329fc23%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
