aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts/setup-eclipse.sh
Commit message (Collapse)AuthorAge
* Make local-jdk conform to workspace name rulesGravatar Kristina Chodorow2016-01-27
| | | | | | | | RELNOTES: JDK-related targets are now available via @local_jdk (instead of @local-jdk). -- MOS_MIGRATED_REVID=113067049
* Make setup-eclipse.sh work somewhat again.Gravatar Lukacs Berki2016-01-20
| | | | | | | The generated project is not perfect, but this does unblock Manuel for the time being. -- MOS_MIGRATED_REVID=112571724
* Rationalize copyright headersGravatar Damien Martin-Guillerez2015-09-25
| | | | | | | | | | | 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
* Adds gen jar and manifest proto outputs.Gravatar Alex Humesky2015-07-10
| | | | | | | Adds a jar output to Java and Android rules which contains the class files for source files generated from Java annotation processors. For a java_binary foo, the jar will be foo-gen.jar, and for a java_library foo the jar will be libfoo-gen.jar, and similarly for Android. Also adds a binary serialized proto manifest file output to Java and Android rules which describes the contents of the output class jar of those rules, which is used to create the -gen.jar. See src/main/protobuf/java_compilation.proto. -- MOS_MIGRATED_REVID=97793715
* Make the eclipse set-up more generic and support //external targetsGravatar Damien Martin-Guillerez2015-04-22
| | | | | | | | | | | | | | | | | | | | | 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
* Improved Eclipse support for the Bazel projectGravatar Damien Martin-Guillerez2015-04-20
| | | | | | | | | | | | | 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
* Added script to generate an Eclipse project for BazelGravatar Damien Martin-Guillerez2015-03-16
Now a developer can work on the Java sources by generating an Eclipse project with scripts/eclipse/setup.sh. The xcode tooling are also imported compared to the previously checked-in project resulting in a bunch of errors. -- MOS_MIGRATED_REVID=88548129