[ 
https://issues.apache.org/jira/browse/GEODE-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123638#comment-16123638
 ] 

ASF GitHub Bot commented on GEODE-3165:
---------------------------------------

GitHub user pivotal-jbarrett opened a pull request:

    https://github.com/apache/geode-native/pull/115

    GEODE-3165: Reogranized sources relative to the root for better CMake

    … IDE integration.
    
    - Moved src/docs to docs/api.
    - Moved src/* to root.
    - Fixup paths in CMake files.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pivotal-jbarrett/geode-native 
feature/GEODE-3165

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/geode-native/pull/115.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #115
    
----
commit 6cbd424fe39bc907025460c555768552430c0c5d
Author: Jacob Barrett <jbarr...@pivotal.io>
Date:   2017-08-11T15:30:49Z

    GEODE-3165: Reogranized sources relative to the root for better CMake IDE 
integration.
    
    - Moved src/docs to docs/api.
    - Moved src/* to root.
    - Fixup paths in CMake files.

----


> Re-organize sources to make integration with IDE that support CMake easier.
> ---------------------------------------------------------------------------
>
>                 Key: GEODE-3165
>                 URL: https://issues.apache.org/jira/browse/GEODE-3165
>             Project: Geode
>          Issue Type: Task
>          Components: docs, native client
>            Reporter: Jacob S. Barrett
>            Assignee: Jacob S. Barrett
>
> Many of the IDE's that support CMake expect that CMakeList.txt be in the root 
> of the project. I propose moving the contents of src/ to the root, which was 
> the intent after cleaning out all the legacy cruft in root.
> /src/docs -> /docs/api
> /src/* -> /root/*
> Since this a pretty straight forward move there should not be issues with 
> merging changes between older branches and develop after this move.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to