Can not invoke Task if source is che
See original GitHub issueIf I have a task defined on tasks.json
with source
defined as che
, it can not be started from Command palette. I can see a message printed on JS Console as ERROR Can't get task launch configuration for label: echo me
If I remove the source property from the following example task I can start the task without issues.
{
"label": "echo me",
"source": "che",
"type": "process",
"command": "echo test",
"target": {
"machineName": "theia-idemh5"
}
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Run my task before a plugin's task? - gradle
I need a task I've written to run sometime after clean but sometime before war . Preferably without modifying the plugin.
Read more >Invoking Builds: Deployment and Project Task Patterns
We've been using Fabric to manage deployments for a while and lately Invoke for adding similar functionality where SSH based deployment isn't required....
Read more >Command-Line Interface
When executed with --continue , Gradle executes every task in the build if all of the dependencies for that task completed without failure....
Read more >Common Resource Functionality - Chef Documentation
All resources (including custom resources) share a set of common actions, properties, conditional executions, notifications, and relative ...
Read more >Custom Tasks - Gradle Recipes for Android [Book]
The dependency on assembleDebug means all the debug APKs will be generated before the copy task runs. You can use assemble instead if...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since the PR https://github.com/eclipse/che-theia/pull/295 was merged we consider
che
tasks asconfigured
, not asdetected
. User doesn’t need to useConfigure task
action forche
tasks: we convert che commands from devfile to theia tasks format and copy them to tasks.json file.So I’m closing the issue.
@RomanNikitenko could you please check if it’s already fixed and whether we can close that issue