| 3.5.0.M04 Cannot determine the artifact identity of the file [message #869913] |
Fri, 04 May 2012 15:05  |
Rich Mayfield Messages: 44 Registered: August 2010 |
Member |
|
|
I'm trying to deploy a very simple (empty even) plan in the pickup directory however this fails every time with the error "Cannot determine the artifact identity of the file ...".
Any ideas what I'm doing wrong here? This is with the Jetty distribution and other plans appear to be fine.
This is on Mac OS X 10.7.3 with Java 1.6.0_31.
The plan is quite simply:
<?xml version="1.0" encoding="UTF-8"?>
<plan name="server.plan" version="1.0.0" scoped="false" atomic="true"
xmlns="http: //www.eclipse.org/virgo/schema/plan"
xmlns:xsi="http: //www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http: //www.eclipse.org/virgo/schema/plan
http: //www.eclipse.org/virgo/schema/plan/eclipse-virgo-plan.xsd">
</plan>
Yields the error:
[2012-05-04 11:55:47.667] fs-watcher <HD0002E> Hot deploy failed for file '.server-1.0.0.plan.swp'. org.eclipse.virgo.kernel.deployer.core.DeploymentException: Cannot determine the artifact identity of the file '/Users/me/Desktop/virgo-jetty-server-3.5.0.M04/pickup/.server-1.0.0.plan.swp': uri='file:/Users/me/Desktop/virgo-jetty-server-3.5.0.M04/pickup/.server-1.0.0.plan.swp': uri='file:/Users/me/Desktop/virgo-jetty-server-3.5.0.M04/pickup/.server-1.0.0.plan.swp'
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:167)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:139)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:252)
at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:163)
at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:67)
at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:245)
at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:166)
at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTask.java:48)
at java.lang.Thread.run(Thread.java:680)
Caused by: org.eclipse.virgo.kernel.deployer.core.DeploymentException: Cannot determine the artifact identity of the file '/Users/me/Desktop/virgo-jetty-server-3.5.0.M04/pickup/.server-1.0.0.plan.swp': uri='file:/Users/me/Desktop/virgo-jetty-server-3.5.0.M04/pickup/.server-1.0.0.plan.swp'
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.determineIdentity(PipelinedApplicationDeployer.java:209)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:159)
... 8 common frames omitted
Caused by: org.eclipse.virgo.kernel.deployer.core.DeploymentException: Cannot determine the artifact identity of the file '/Users/me/Desktop/virgo-jetty-server-3.5.0.M04/pickup/.server-1.0.0.plan.swp'
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.determineIdentity(PipelinedApplicationDeployer.java:348)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.determineIdentity(PipelinedApplicationDeployer.java:207)
... 9 common frames omitted
|
|
|
|
|
| Re: 3.5.0.M04 Cannot determine the artifact identity of the file [message #871243 is a reply to message #869913] |
Fri, 11 May 2012 11:28  |
Rich Mayfield Messages: 44 Registered: August 2010 |
Member |
|
|
Thanks for the replies. I was able to get to the bottom of the problem(s), which I'll summarize.
Note that the ".swp" file was actually created by vi when I edited the plan. In any event, this temporary file and it's name wasn't the problem.
I got this error when:
1) The bundle plan included an artifact with what is apparently an invalid version. For example, "1.0.0.2", which is fine for a Maven artifact versions but not for OSGi artifact versions.
2) The bundle plan was empty - i.e. there were no artifacts whatsoever in the plan. After experiencing "1)" I was just trying to see what it was about my plan, which had 100 artifacts referenced, was incorrect. It baffled me that an empty plan wasn't acceptable.
The error message provided by Virgo, however, is not helpful. In both of the above cases it says that it cannot identify the artifact identity of the plan.
What would be much more useful is if the error cited the artifact within the plan that was causing the problem.
|
|
|
Powered by
FUDForum. Page generated in 0.05706 seconds