| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
| |
|
|
|
|
|
|
| |
This is not really a problem anymore because of latest change but
it is error prone to leave it that way.
--
MOS_MIGRATED_REVID=91782569
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, other people might just copy the setup-eclipse.sh
and get_project_path.sh scripts and adapt it to their workspace
(change the variables at the top of the setup-eclipse.sh script) to
generate an eclipse project.
I tested it by replacing guava dependency in Bazel by a maven_jar and
importing the project in Eclipse on OS X.
It is incomplete because it actually filters out bind dependencies for
generated java source but there might be some java generation in them
if importing an other actual workspace. Let say that you have your
project and you want to import targets from the Bazel workspace, the
java library from generated sources won't be imported in the Eclipse
classpath and the sources will be imported as source in the Eclipse
classpath.
--
MOS_MIGRATED_REVID=91696217
|
|
|
Now the paths are 100% determined using Bazel query. To adapt to
another project, change the variables at the top of the
setup-eclipse.sh file. It also handles correctly java_plugins now.
Because we must do queries on the full workspace, it is not easy to
embed in a bazel build. I made a prototype for it but it is really
impractical.
--
MOS_MIGRATED_REVID=91580472
|
Damien Martin-Guillerez