Hi All,
In the IoT Server, this is the script[1]
<https://github.com/wso2-incubator/product-iot-server/blob/master/modules/samples/installer/device-deployer.xml>
uses to install sample device types into IOT Server. Sometimes, it behaves
in an annoying manner. Because I could able to install sample device type
in the local machine successfully. But when I try to install the same
application on a remote server I am getting this error.
[INFO] --- carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) @
devicetype-feature-installation ---
[ERROR] No such file or directory
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createTempFile(File.java:2001)
at java.io.File.createTempFile(File.java:2047)
at
org.wso2.maven.p2.RepositoryGenMojo.createAndSetupPaths(RepositoryGenMojo.java:377)
at
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:199)
at
org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[INFO]
------------------------------------------------------------------------
Full stacktrace[2]
<https://gist.github.com/GPrathap/3265c496f85c0f916b25#file-installation-process-of-sample-device-type>
According to this[1], when generating p2 feature it should be generated a
folder called p2-repo. It seems to be p2-repo folder isn't generated when
it is on the remote server. That is why getting above error while creating
a custom distribution for that.
Tested Environment
Local Machine
Remote Server
Java Version/Java VM: JDK1.7.0_95 Java
Version/Java VM: JDK1.7.0_79
Maven Version: 3.0.5
Maven Version: 3.0.4
*Is there is any specific reason not to generate p2-repo folder?*
1.
https://github.com/wso2-incubator/product-iot-server/blob/master/modules/samples/installer/device-deployer.xml
2.
https://gist.github.com/GPrathap/3265c496f85c0f916b25#file-installation-process-of-sample-device-type
Thank you,
Geesara
--
Geesara Prathap Kulathunga
Software Engineer
WSO2 Inc; http://wso2.com
Mobile : +940772684174
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
