Le 13/02/2017 à 10:56, Jacques Le Roux a écrit :
So updting a plugin by hand with svn, or even several plugins at a time with an IDE or a Svn GUI , is not be a problem, nor to commit changes, etc.
So we don't need Gradle tasks for that, all is still possible.
To summarize, so far I seed no disadvantages with Taher solution, but in
Builbot for plugins.
Something I forgot to talk about and, though related to rare cases, is worth to mention for committers. Each time we use pullPluginSource Gradle task,
we create an embedded working copy for the imported component. With the to come pullAllPluginsSource Gradle task we can't checkout the whole plugins
folder in an embedded working copy. It would be in conflict with what pullPluginSource Gradle task creates. So we have to create as much as embedded
working copies as components in the plugins folder. So in rare cases were a lot of components are modified we will need to do as much as commits as
component are changed.
Jacques
