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.

Sign up for GitHub

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

Jump to bottom

Import workspace using a Project View file to choose packages #5

Closed
plaird opened this issue Nov 21, 2019 · 0 comments
Closed

Import workspace using a Project View file to choose packages #5

plaird opened this issue Nov 21, 2019 · 0 comments
Assignees
@simontoens

Comments

@plaird
Copy link
Contributor

plaird commented Nov 21, 2019 •
edited
Loading

As a BEF user importing a large Bazel workspace
I would like to have a file created by a colleague that lists all the packages most often modified by my team
Such that packages that I don't ever care about are not imported into the Eclipse workspace
Such that I don't have to manually click a long list of checkboxes on import.

Background:
We could use the IJ plugin project view file format to allow team members to share a common set of packages that should be loaded into the IDE at import.

Note that the project view file format has at least 10 possible sections. This ticket would just implement the directories and targets sections.

https://github.com/bazelbuild/intellij/blob/194f34b0690827918356eab5ae84fe85c8f6c50c/base/src/com/google/idea/blaze/base/projectview/section/sections/Sections.java#L27
@plaird plaird mentioned this issue Nov 21, 2019
Closed
@plaird plaird mentioned this issue Dec 20, 2019
Closed
@simontoens simontoens self-assigned this Feb 29, 2020
simontoens added a commit to simontoens/bazel-eclipse that referenced this issue Feb 29, 2020
@simontoens
Some general refactor related to issue salesforce#5 (projectview)
dd8ab44
@simontoens simontoens mentioned this issue Feb 29, 2020
Merged
simontoens added a commit to simontoens/bazel-eclipse that referenced this issue Feb 29, 2020
@simontoens
Some general refactor related to issue salesforce#5 (projectview)
14522bd
simontoens added a commit that referenced this issue Mar 1, 2020
@simontoens
Some general refactor related to issue #5 (projectview) (#61)
aad7207
simontoens added a commit to simontoens/bazel-eclipse that referenced this issue Mar 4, 2020
@simontoens
Replace BazelPackageInfo usage with new Interface during import sales…
ed84dc0 
…force#5

This is to allow different import code paths - the one based on projectview
file changes won't construct BazelPackageInfo instances.
@simontoens simontoens mentioned this issue Mar 4, 2020
Merged
simontoens added a commit that referenced this issue Mar 4, 2020
@simontoens
Replace BazelPackageInfo usage with new Interface during import #5 (#62)
8fb043f 
This is to allow different import code paths - the one based on projectview
file changes won't construct BazelPackageInfo instances.
simontoens added a commit to simontoens/bazel-eclipse that referenced this issue Mar 7, 2020
@simontoens
Initial projectview support - only "directories" support
3edc3d0 
salesforce#5
simontoens added a commit to simontoens/bazel-eclipse that referenced this issue Mar 7, 2020
@simontoens
Initial projectview support - only "directories" support
f71c0d5 
salesforce#5
@simontoens simontoens mentioned this issue Mar 7, 2020
Merged
plaird pushed a commit that referenced this issue Mar 8, 2020
@simontoens
Initial projectview support - only "directories" support (#65)
091b79d 
#5
@simontoens simontoens mentioned this issue Mar 11, 2020
Closed
@simontoens simontoens mentioned this issue Mar 11, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@simontoens simontoens

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@simontoens @plaird