Re: Plugins: skipped obstructing working copy (error message)

Le 15/03/2017 à 16:21, Jacques Le Roux a écrit : Le 15/03/2017 à 15:10, Jacques Le Roux a écrit : In other words, because of the plugins/README.txt file when you create a working copy from the ofbiz-framework/trunk branch you generate a .svn in root folder where there is a "knowledge" of this

Re: Plugins: skipped obstructing working copy (error message)

Le 15/03/2017 à 15:10, Jacques Le Roux a écrit : In other words, because of the plugins/README.txt file when you create a working copy from the ofbiz-framework/trunk branch you generate a .svn in root folder where there is a "knowledge" of this file and the plugins directory. So, we can't

Re: Plugins: skipped obstructing working copy (error message)

Taher, Deepak, I already explained the reason of the problem in the initial thread message. <(plugins folder) and the main .svn gets confused (in root) >> In other words, because of the plugins/README.txt file when you create a working copy from the ofbiz-framework/trunk branch you generate a

Re: Plugins: skipped obstructing working copy (error message)

Hi Deepak, Just to be on the safe side though, do you think that would solve the subversion issue? I mean does subversion complain because of folder deletion and then creation? or does it complain because of move a .svn based repo from one subdirectory to another? Also what about the idea of

Re: Plugins: skipped obstructing working copy (error message)

Thanks Taher, Make sense, I am fine with following approach. > Would that solve the subversion problem? Let me just reiterate the steps: - checkout plugins into /temp - delete everything _inside_ /plugins - move everything (including .svn) from /temp to /plugins - delete /temp Thanks &

Re: Plugins: skipped obstructing working copy (error message)

Hi Deepak, So there are multiple issues with this code that I attempt summarize below: - First, you are directly using the subversion command in an "exec" block. We used the subversion plugin to avoid having gradle depend on anything other than gradle. I think it might be better to try and list

Re: Plugins: skipped obstructing working copy (error message)

Oh, and just for completeness, maybe another solution is to instruct subversion to ignore /plugins completely? or even delete it altogether, but make gradle create the directory if missing? On Wed, Mar 15, 2017 at 10:36 AM, Taher Alkhateeb < slidingfilame...@gmail.com> wrote: > Hi Deepak, > > So

Re: Plugins: skipped obstructing working copy (error message)

Hi Taher, I tried to change it with following bug not able to run sub process. {code} task pullAllPluginsSource(group: ofbizPlugin, description: 'Download and install all plugins from source control.') { def svnOutput = new ByteArrayOutputStream() exec { commandLine

Re: Plugins: skipped obstructing working copy (error message)

From my view, gradle is a simplified maven, is it possible to use version/snapshot way to bring the plugins in? -邮件原件- 发件人: Jacques Le Roux [mailto:jacques.le.r...@les7arts.com] 发送时间: 2017年3月15日 14:13 收件人: dev@ofbiz.apache.org 主题: Re: Plugins: skipped obstructing working copy (error

Re: Plugins: skipped obstructing working copy (error message)

What I fear (still not looked into it) is that Taher did it that way because he (rightly) wanted to have the same structure than before, ie the possibility to commit a change in a plugin from the root of the project. So I fear that another solution will impose to have as much as working copies

Re: Plugins: skipped obstructing working copy (error message)

Sure, let's change the implementation. I'd be glad to help if I receive some suggestions. For now .. the implementation is as follows: - create a temp directory - checkout to that directory - delete /plugins - rename temp to plugins I'm all ears for the best approach. On Wed, Mar 15, 2017 at

Re: Plugins: skipped obstructing working copy (error message)

We need to enhance pullAllPluginsSource task, after running this you will not able to commit or run any svn command on plugins, as it do checkout of plugins/trunk and copy its folder into plugins. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com On Wed, Mar 15, 2017 at 12:18 AM, Jacques

Re: Plugins: skipped obstructing working copy (error message)

That would be better indeed, I did not look a it yet. Jacques Le 14/03/2017 à 19:04, Deepak Dixit a écrit : I think we can improve gradle task and instead of deleting plugins it will its delete sub-folder. I am sure gradle should have ability to delete sub-folder. :) If we delete README.txt

Re: Plugins: skipped obstructing working copy (error message)

I think we can improve gradle task and instead of deleting plugins it will its delete sub-folder. I am sure gradle should have ability to delete sub-folder. :) If we delete README.txt then it will not be available in git as git does not support empty folder. Thanks & Regards -- Deepak Dixit

Re: Plugins: skipped obstructing working copy (error message)

What would you suggest? Jacques Le 14/03/2017 à 14:55, Pierre Smits a écrit : I don't believe replacement of the entire plugin folder (or even deletion, which I noticed in a comment/posting elsewhere) would go down well with developers who also have created their own special purpose

Re: Plugins: skipped obstructing working copy (error message)

I don't believe replacement of the entire plugin folder (or even deletion, which I noticed in a comment/posting elsewhere) would go down well with developers who also have created their own special purpose components. Best regards, Pierre Smits ORRTIZ.COM OFBiz based

Plugins: skipped obstructing working copy (error message)

Hi, I just crossed an issue while updating my ofbiz-framework working copy after having used pullAllPluginsSource. I get an error message "Skipped obstructing working copy". This is because we have already a plugins folder in the ofbiz-framework/trunk branch and when we use