Eclipse Community Forums: Virgo » Installation and Using of Virgo Maven Plugin

Home » Eclipse Projects » Virgo » Installation and Using of Virgo Maven Plugin(Installation and Using of Virgo Maven Plugin)

Installation and Using of Virgo Maven Plugin [message #1005250]

Thu, 24 January 2013 13:07

Eclipse User

Hi Everyone,

I'm quite new to Maven and Virgo. I have some OSGi/Virgo projects working well and would like to start using Maven with these. I've read about the Virgo Maven Plugin and tried to use it. Following are the steps:

Downloaded the Virgo Maven Plugin ZIP from github
Extracted the ZIP
Went to the dir: "virgo-maven-plugin-master/virgo-maven-plugin" (where there is the pom.xml file)
Executed mvn clean install
Then went to where my OSGi project is (the pom.xml) and executed mvn virgo:deploy

Following is what was displayed.

C:\exp\test2>mvn virgo:start
[INFO] Scanning for projects...
[WARNING] The POM for net.flybyte.virgo:virgo-maven-plugin:jar:1.0.0 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for net.flybyte.virgo:virgo-maven-plugin:1.0.0: Plugin net.flybyte.virgo:virgo-maven-plugin:1.0.0 or one of its d
ependencies could not be resolved: Failed to read artifact descriptor for net.flybyte.virgo:virgo-maven-plugin:jar:1.0.0
Downloading: maven-metadata.xml
Downloading: maven-metadata.xml
Downloaded: maven-metadata.xml (11 KB at 30.5 KB/sec)
Downloaded: maven-metadata.xml (22 KB at 41.8 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.604s
[INFO] Finished at: Thu Jan 24 18:37:05 CET 2013
[INFO] Final Memory: 9M/184M
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'virgo' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\maven\.m2\repository), central (maven2)] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] NoPluginFoundForPrefixException

Note that the links had to be removed as otherwise it would not allow me to submit the post.

Can someone please tell me how to get this working?

Re: Installation and Using of Virgo Maven Plugin [message #1005271 is a reply to message #1005250]

Thu, 24 January 2013 13:52

Eclipse User

Hi,

Found the first problem. It was the version. In the examples it shows version 1.0.0 while the virgo-maven-plugin has a version of 1.0.1-SNAPSHOT.

Now I have a new error.

C:\exp\test2>mvn virgo:deploy
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building test2 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- virgo-maven-plugin:1.0.1-SNAPSHOT:deploy (default-cli) @test2 ---
[info] Start deploying the artefact to Eclipse Virgo
[info] Create new service URL: service:jmx:rmi://localhost:9875/jndi/rmi://localhost:9875/jmxrmi
[info] Create a new JMX connector (user = 'admin')
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.983s
[INFO] Finished at: Thu Jan 24 19:49:59 CET 2013
[INFO] Final Memory: 7M/184M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.flybyte.virgo:virgo-maven-plugin:1.0.1-SNAPSHOT:deploy (default-cli) on project test2: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
[ERROR] java.net.ConnectException: Connection refused: connect]
[ERROR] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:357)
[ERROR] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
[ERROR] at net.flybyte.virgo.maven.BaseMojo.getConnection(BaseMojo.java:200)
[ERROR] at net.flybyte.virgo.maven.deployer.Deploy.execute(Deploy.java:29)
[ERROR] at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[ERROR] at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
[ERROR] at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[ERROR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
[ERROR] at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
[ERROR] Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
[ERROR] java.net.ConnectException: Connection refused: connect]
[ERROR] at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:118)
[ERROR] at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:203)
[ERROR] at javax.naming.InitialContext.lookup(InitialContext.java:411)
[ERROR] at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1924)
[ERROR] at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1891)
[ERROR] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:274)
[ERROR] ... 24 more
[ERROR] Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
[ERROR] java.net.ConnectException: Connection refused: connect
[ERROR] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
[ERROR] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
[ERROR] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
[ERROR] at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:340)
[ERROR] at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
[ERROR] at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:114)
[ERROR] ... 29 more
[ERROR] Caused by: java.net.ConnectException: Connection refused: connect
[ERROR] at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
[ERROR] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
[ERROR] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
[ERROR] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
[ERROR] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157)
[ERROR] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
[ERROR] at java.net.Socket.connect(Socket.java:579)
[ERROR] at java.net.Socket.connect(Socket.java:528)
[ERROR] at java.net.Socket.<init>(Socket.java:425)
[ERROR] at java.net.Socket.<init>(Socket.java:208)
[ERROR] at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
[ERROR] at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:146)
[ERROR] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
[ERROR] ... 34 more
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] MojoFailureException

[Updated on: Thu, 24 January 2013 13:55] by Moderator

Re: Installation and Using of Virgo Maven Plugin [message #1005288 is a reply to message #1005271]

Thu, 24 January 2013 14:30

Eclipse User

A simple reboot fixed the problem.

The real issues was the plugin version. While the examples read version: 1.0.0, in reality this was: 1.0.1-SNAPSHOT

Hope this helps someone.

Previous Topic:	Doubts regarding ManagedServiceFactory
Next Topic:	Per-application log doesn't capture bundle startup message

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 18:41:18 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter