ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-11337) replace pullPluginFromSvn with a git equivalent
Date Sun, 01 Mar 2020 12:45:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-11337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048553#comment-17048553

Pierre Smits commented on OFBIZ-11337:

I wonder whether the project should keep these functions in the codebase. People working with
repositories know how to put them in the right place to do both development (and safeguarding
their changes) and implementation for production use.

> replace pullPluginFromSvn with a git equivalent
> -----------------------------------------------
>                 Key: OFBIZ-11337
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11337
>             Project: OFBiz
>          Issue Type: Sub-task
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Priority: Major
>              Labels: contributing, git
>         Attachments: Screen Shot 2020-02-03 at 10.43.17.png
> Currently we have a 'pullPluginFromSvn' task defined in *build.gradle*. The drawback
with this is that the pulled plugin is defined as an SVN style repository (having a .svn folder).
> With current migration from svn to git we should have it in such a way that the cloned
plugin is a git style repository.  The standard way to clone from a publicly available git
repository (e.g. Github) is:
> {code:java}
> git clone https://github.com/<githubUserId>/<repoName>.git
> {code}
> This would allow a developer not only to work on his local changes, but also commit the
changes and share these with the community via the public Github fork and eventually via Pull
Requests included into the project's repository.

This message was sent by Atlassian Jira

View raw message