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

Follow Maven convention for putting source files in "src/main/java" #359

Closed
wonderfly opened this issue Jan 10, 2015 · 2 comments
Closed
Assignees
Labels
imported type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@wonderfly
Copy link
Contributor

From rmis...@google.com on November 04, 2011 08:43:27

Filed internally by yanivi:

I can't think of anything negatively impacted by this, but currently we are generating the source files like this:

com/google/api/services/buzz/Buzz.java

which implies the root source directory is ".".

However, the standard convention is to put source under src/main/java.

Note also that the in the pom.xml should match what we are using. Currently it is:

com/google/api/services/{{ api.name }}

Which is actually incorrect since it should be .. If instead we change it to the Maven default of "src/main/java", then we can remove sourceDirectory completely.

Original issue: http://code.google.com/p/google-api-java-client/issues/detail?id=344

@wonderfly wonderfly added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. imported 1 star labels Jan 10, 2015
@wonderfly
Copy link
Contributor Author

From rmis...@google.com on November 04, 2011 08:43:45

Status: Fixed

@wonderfly wonderfly self-assigned this Jan 10, 2015
@wonderfly
Copy link
Contributor Author

From yan...@google.com on November 07, 2011 09:37:16

Labels: -Priority-Medium Priority-Low

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
imported type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

1 participant