[
https://issues.apache.org/jira/browse/OFBIZ-9262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927634#comment-15927634 ]
Deepak Dixit commented on OFBIZ-9262:
-------------------------------------
I think we can proceed with this change, without ignore,
In case of ignore svn will not include plugins directory, like if we have some custom changes or custom component in plugins directory then svn will ignore them while committing code in ofbiz-framework. like build or runtime/uploads etc.
> Error message when svn updating due to pullAllPluginsSource
> -----------------------------------------------------------
>
> Key: OFBIZ-9262
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9262> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Critical
> Fix For: Upcoming Release
>
> Attachments: OFBIZ-9262.patch
>
>
> When try to update a ofbiz-framework working copy after having used pullAllPluginsSource, you 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 pullAllPluginsSource we replace it by a new one (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 .svn in root folder where there is a "knowledge" of this file and the plugins directory.
> So, we can't delete the whole plugins directory and replace it by another different plugins directory with the plugins sub-folders inside.
> Morevoer you can't make a chekout (which pullAllPluginsSource currently does) in a non empty folder.
> And If you temporarily move the plugins/README.txt file to get an empty directory you get this error message
> > svn-checkout failed for
https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/trunk> svn: E155000: 'C:\projectsASF\ofbiz-framework\plugins' is already a working copy for a different URL; perform update to complete it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Locked
