Cedric Beust

1. Not sure I follow, can you elaborate? Do you mean that templates should belong to a group (like tasks) and have a version number? 2. This can't always be...

Generating these in the project allows that project to have its own independent Kobalt version. I think this scheme (which Gradle uses) works well. What kind of dependency hell are...

The one discrepancy between what Kobalt does when it updates itself and how the IDEA plug-in updates is that the IDEA plug-in probably doesn't update `wrapperVersion.txt`, so we should fix...

Actually, the only reason for the wrapper is that without it, it's much harder to update. For example, if you invoke the following code: ``` java -jar foo.jar foo.Main ```...

Amending my post above. Actually, the main value is more that you can switch the version number by editing a text file (`kobalt-wrapper.properties`). I think this is desirable. Can we...

That's my impression too, I can't think of another way to do this without a wrapper but just checking to make sure I'm not missing an obvious alternative.

But if you have `kobaltw`, you already have the wrapper, don't you?

Confirmed, I get the exact same stack trace.

`LauncherActivity` is in the .dex and since the stack trace contains a `NoClassDefFoundException`, I think it's a dependency of that class that can't be instantiated. Bit of a misleading stack...

Wanted to add a vote for this feature.