On Sat, Dec 28, 2013 at 8:11 AM, <[email protected]> wrote: > I had a quick lock at the Copier class and it should be > fairly easy to add a Copier that uses hard links if the source files are on > the same machine (using the Java 7 nio.Files API).
Would make sense, yes. > What would be the best way to add a new Copier? Create a new plugin with > only the Copier class in it? Or extend the existing Copy Artifact plugin? Probably just an addition to the Copy Artifact plugin would be best. > How do I make sure that the new Copier is used instead of the standard > implementation? Maybe the UI needs an option to select a copier instance? Yes, I think so. > How do I deal with the Java 7 dependency? First, make sure the option cleanly degrades to a simple copy (or perhaps symlink?) when the slave is actually using Java 6. Then keep the Java 7 dependencies in a self-contained method and use @IgnoreJRERequirement to mark this method as not needing to be compatible with Java 6. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
