Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assumption of 'proto' subdir is too restrictive #1

Closed
louiscryan opened this issue Apr 14, 2015 · 0 comments · Fixed by #2
Closed

Assumption of 'proto' subdir is too restrictive #1

louiscryan opened this issue Apr 14, 2015 · 0 comments · Fixed by #2

Comments

@louiscryan
Copy link

Plugin assumes proto files are contained in a directory called 'proto' under src/main. This is quite restrictive and other conventions are in active use E.g.

https://github.com/apache/hbase/tree/master/hbase-protocol/src/main/protobuf

This is a clone of
aantono/gradle-plugin-protobuf#24

zhangkun83 added a commit that referenced this issue Apr 21, 2015
Create protoSources convention that can be used to override the default
proto file location, i.e., "src/main/proto" etc.
Create testProjectCustomProtoDir to test it.
zhangkun83 added a commit that referenced this issue Apr 21, 2015
Create protoSources convention that can be used to override the default
proto file location, i.e., "src/main/proto" etc.
Create testProjectCustomProtoDir to test it.
zhangkun83 added a commit that referenced this issue Apr 24, 2015
- Create protoSources convention that can be used to override the default
  proto file location, i.e., "src/main/proto" etc.
- Create testProjectCustomProtoDir to test it.
- Change the required Gradle version to 2.2
zhangkun83 added a commit that referenced this issue Apr 28, 2015
Resolves #4, an alternative solution to #1.

Example:
sourceSets {
  main {
    proto {
      srcDir 'src/main/protobuf'
      include '**/*.protodevel'
    }
  }
}

Removed the protoSources convention that was used to do this.
podarsmarty pushed a commit to podarsmarty/protobuf-gradle-plugin that referenced this issue Jul 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant