search

NickHeap2 / vscode-ant

Visual Studio Code Ant Task Runner Extension published on the marketplace
MIT License
6 stars 4 forks source link

Scan Workspace and present all Build files #5

Open pyramid-johng opened 5 years ago

pyramid-johng commented 5 years ago

When opened in a workspace, the extension should scan all folders for Ant Build files, and present them in the View. Each discovered Build file should appear as another "node" in the Tree view at the root level. If the file has no name attribute, display the folder it was discovered from.

Each individual folder's build.auto must apply as expected.

dswitzer commented 4 years ago

This is the only thing holding me back from using this extension. We have a very large code base we have various modules that have their own build scripts in their own folders.

pyramid-johng commented 4 years ago

i have found you can mitigate by using a vscode-workspace and putting your "active" build.xml folder as the first entry. other than that, i have been considering implementing workspace awareness, or switching projects over to MVN which works ootb.

TonyGravagno commented 4 years ago

i have found you can mitigate by using a vscode-workspace and putting your "active" build.xml folder as the first entry.

I came to this repo just for to see if anything had brought up this topic. And yes, @pyramid-johng thanks for that tip. Drag a project up to the top position in the workspace and the build.xml being used for Ant changes immediately.

Workspace awareness would be helpful. Thanks.

NickHeap2 commented 4 years ago

Now I've released the import support this is next on the list of things to support. I didn't internally have need for this before but it's just become relevant.

NickHeap2 commented 4 years ago

I've finally released v0.3.0 which will scan workspace folders in turn until it hits one with a build file. Hopefully this will work for people until I get time to do the changes to support multiple folders with multiple build files.