Problem with Kobalt plugin after initializing a new project
See original GitHub issueI created a new project in OS X by mkdir “project”, cd “project”
Then did ./kobaltw --init java
This all works.
./kobaltw run
./kobaltw test
all works…
Did ./kobaltw --init idea
and then ran IntelliJ, opened project.
Stack trace follows:
String index out of range: 0
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:658)
at com.intellij.configurationStore.ProjectStateStorageManager.expandMacros(ProjectStateStorageManager.kt:33)
at com.intellij.configurationStore.StateStorageManagerImpl.createStateStorage(StateStorageManagerImpl.kt:194)
at com.intellij.configurationStore.StateStorageManagerImpl.getOrCreateStorage(StateStorageManagerImpl.kt:150)
at com.intellij.configurationStore.StateStorageManagerImpl.getStateStorage(StateStorageManagerImpl.kt:133)
at com.intellij.configurationStore.ComponentStoreImpl.a(ComponentStoreImpl.kt:269)
at com.intellij.configurationStore.ComponentStoreImpl.initComponent(ComponentStoreImpl.kt:90)
at com.intellij.openapi.components.impl.PlatformComponentManagerImpl.initializeComponent(PlatformComponentManagerImpl.java:54)
at com.intellij.openapi.components.impl.ServiceManagerImpl$MyComponentAdapter.getComponentInstance(ServiceManagerImpl.java:237)
at com.intellij.util.pico.DefaultPicoContainer.getLocalInstance(DefaultPicoContainer.java:246)
at com.intellij.util.pico.DefaultPicoContainer.getComponentInstance(DefaultPicoContainer.java:212)
at com.intellij.openapi.components.ServiceManager.doGetService(ServiceManager.java:46)
at com.intellij.openapi.components.ServiceManager.getService(ServiceManager.java:41)
at com.beust.kobalt.intellij.settings.KobaltSettings.getInstance(KobaltSettings.java:34)
at com.beust.kobalt.intellij.manager.KobaltManager$getSettingsProvider$1.fun(KobaltManager.kt:128)
at com.beust.kobalt.intellij.manager.KobaltManager$getSettingsProvider$1.fun(KobaltManager.kt:43)
at com.intellij.openapi.externalSystem.service.settings.AbstractExternalSystemToolWindowCondition.value(AbstractExternalSystemToolWindowCondition.java:48)
at com.intellij.openapi.externalSystem.service.settings.AbstractExternalSystemToolWindowCondition.value(AbstractExternalSystemToolWindowCondition.java:31)
at com.intellij.openapi.wm.impl.ToolWindowManagerImpl$11.computeInReadAction(ToolWindowManagerImpl.java:502)
at com.intellij.openapi.progress.util.ReadTask$1.run(ReadTask.java:52)
at com.intellij.openapi.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:951)
at com.intellij.openapi.progress.util.ReadTask.runBackgroundProcess(ReadTask.java:49)
at com.intellij.openapi.progress.util.ProgressIndicatorUtils$7.run(ProgressIndicatorUtils.java:205)
at com.intellij.openapi.progress.impl.CoreProgressManager$2.run(CoreProgressManager.java:142)
at com.intellij.openapi.progress.impl.CoreProgressManager.a(CoreProgressManager.java:446)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:392)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:54)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:127)
at com.intellij.openapi.progress.util.ProgressIndicatorUtils.a(ProgressIndicatorUtils.java:201)
at com.intellij.openapi.progress.util.ProgressIndicatorUtils.access$000(ProgressIndicatorUtils.java:43)
at com.intellij.openapi.progress.util.ProgressIndicatorUtils$6$2.run(ProgressIndicatorUtils.java:180)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jetbrains.ide.PooledThreadExecutor$1$1.run(PooledThreadExecutor.java:55)
Issue Analytics
- State:
- Created 7 years ago
- Comments:15 (11 by maintainers)
Top Results From Across the Web
Exception in Initializer when running a task · Issue #22 - GitHub
It seems that server always return 500 for kobalt build file. Tested on the latest kobalt-0.761. Note that simple project works well but...
Read more >Kobalt: a modern, versatile build system by Cedric Beust
Templates are invoked with the --init parameter and typically used when you are creating a new project and you want Kobalt to generate...
Read more >Anyone know solution of error in attached Image If i run and
Seems like an issue with accessing gradle distribution files stored in the user profile. Check if "Gradle User Home" is correctly set in...
Read more >Are there any plans to make a better build system for Kotlin ...
31 votes, 58 comments. Gradle has always felt way too bloated and over-engineered to me, it makes project initialization times, ...
Read more >Kotlin: Ready for Production - Realm Academy
Kotlin is a statically-typed language that compiles down to Java, JBM, and JavaScript; No new keyword in Kotlin; No getters and setters, just ......
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
@dmitry-zhuravlev @CaelumF is on the #kobalt Slack channel, feel free to jump in if you want to talk to him directly.
A project that I’ve never ran kobaltw --init in, a pre-existing Kotlin/java project.