|
Taher, I reviewed r1780790 and it's OK with me (not tested yet).
About your proposed patch, it also looks good to me (though not tested). Something though which seems to miss in gradle-svntools-plugin is the svn:externals feature. It would be great if we could not only check plugins out, but also keep them updated later...
Before commenting on Nicolas's comment, I'm not sure I clearly understand the sentence
This task mostly server "Trunk" because it always needs the latest source code of the plugins.
Now if I understand it the same way than Nicolas (ie plugins are always based on trunk) then I agree with Nicolas, and BTW
small incompatibility between a stable branch and the trunk.
is even an euphemism
Nicolas, when you say
With this a user can use a future published version like 16.10.01
I guess you mean 16.10.02? Because 16.10.01 is already released.
If we really are on the same page, I think that rather than using a Java properties file, we should rely on the svn:external svn property.
|
Locked
