Downloading 100%
Disconnected from the target VM, address: '127.0.0.1:59343', transport: 'socket'
13:28:50.502 ERROR - Failed to move module
java.nio.file.InvalidPathException: Illegal char <:> at index 55: C:\path\to\my\project\src\main\groovy\mods\maven:io.vertx:lang-groovy:1.0.0-SNAPSHOT
at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182) ~[na:1.8.0-ea]
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153) ~[na:1.8.0-ea]
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77) ~[na:1.8.0-ea]
at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94) ~[na:1.8.0-ea]
at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255) ~[na:1.8.0-ea]
at java.nio.file.Paths.get(Paths.java:84) ~[na:1.8.0-ea]
at org.vertx.java.core.file.impl.DefaultFileSystem.moveInternal(DefaultFileSystem.java:349) ~[vertx-core-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.core.file.impl.DefaultFileSystem.moveSync(DefaultFileSystem.java:75) ~[vertx-core-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager.unzipModule(DefaultPlatformManager.java:913) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager.doInstallMod(DefaultPlatformManager.java:814) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager.loadIncludedModules(DefaultPlatformManager.java:690) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager.doDeploy(DefaultPlatformManager.java:1059) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager.doDeployVerticle(DefaultPlatformManager.java:470) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager.access$600(DefaultPlatformManager.java:53) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager$7.action(DefaultPlatformManager.java:319) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.platform.impl.DefaultPlatformManager$7.action(DefaultPlatformManager.java:316) [vertx-platform-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.core.impl.BlockingAction$1.run(BlockingAction.java:51) [vertx-core-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.core.impl.Context$1.run(Context.java:126) [vertx-core-2.0.0-SNAPSHOT.jar:na]
at org.vertx.java.core.impl.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:90) [vertx-core-2.0.0-SNAPSHOT.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.8.0-ea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.8.0-ea]
at java.lang.Thread.run(Thread.java:722) [na:1.8.0-ea]
13:28:50.503 ERROR - Failed to load module: maven:io.vertx:lang-groovy:1.0.0-SNAPSHOT
# Language run-times
# <runtime_name>=[implementing module name:]<FQCN of verticle factory>
groovy=maven:io.vertx:lang-groovy:1.0.0-SNAPSHOT:org.vertx.groovy.platform.impl.GroovyVerticleFactory
# Mapping of file extension to language runtime
# If the main is specified without a runtime prefix the file extension will be used to determine
# which runtime to use
# If a prefix is used e.g. 'groovy:org.foo.MyMainClass' then the prefix will be used to determine the
# runtime instead
.groovy=groovy
.class=java
.java=java
# The default runtime - if no prefix is specified and the main does not match any of the file extensions above
# then the default will be used
.=groovy
You are right Tim. Sorry. I ment show-stopper for me to goon with the lang-module (and things which depend on it). Thanks that is in your list.
On Wednesday, March 6, 2013 8:31:01 AM UTC+1, Tim Fox wrote:Well, it shouldn't be a show stopper since no-one one's "show" should be relying on a development branch which is very much WIP :)
This is on my list of things to look at. I'll probably get around to it today.
On Wednesday, 6 March 2013 06:42:46 UTC, Christian Essl wrote:That is indeed a showstopper. Should I go ahead and try to fix it, because I can not work on otherwise witht that? I'll try to replace all colons with File#pathSeparator for the module's file-name (not the module name) in DefaultPlatformManager. Hopefully this fixes it.
On Tuesday, March 5, 2013 9:24:41 PM UTC+1, Mihai Cazacu wrote:Any help would be most welcome.
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Tim,
Thanks for fixing that so fast.
The new module naming is
owner#modname#version, e.g.
com.mycompany#my-mod#1.0.0
the "type" prefix has now disappeared (i.e. the maven: or bintray or old:)
With a maven repo owner maps to groupid, modname maps to artifactid and version to version.
The new module naming is
owner#modname#version, e.g.
com.mycompany#my-mod#1.0.0
the "type" prefix has now disappeared (i.e. the maven: or bintray or old:)
With a maven repo owner maps to groupid, modname maps to artifactid and version to version.
Thanks for this info.How are "local-modules" - those which are in the same mods dir but not in any repo - named?
Or you can ping Charlie Nutter to fix it in JRuby :-)
How about using something that is certainly supported like underscore (_). Than just vertx-modules may not contain _ in any part of their name. IMO this wouldn't be a big problem.
And why not treat it as a repository (maven or otherwise) and just create directory structure instead of actually saving it with the same name that we provide to resolve it?
However, I am edging towards $ as my favourite now...