updated path that fixes same exception in unpack mojo and also includes two unit tests.

I was having the same problem as mentioned on the MNGECLIPSE-1027 and saw the recomendation to update the maven-dependency-plugin to version 2.1.

I updated the plugin but still have the same problem.

Any ideas?

I have the same problem too, and the only solution I´ve found was to simply disable workspace resolution. I know that is terrible and with this approach I have to install locally all the time the other dependent projects
Meanwhile, waiting for the fix.

Is it possible to have this patch applied if it works ?

Thanks.

Is there any other workarounds for this one?
Thanks,
Derek

My current workaround for this issue is to use the antrun plug-in. For example,

<plugin>
    <artifactId>maven-antrun-plugin</artifactId>
    <executions>
      <execution>
        <!-- copy just built artifact to some lib dir -->
        <id>copy-to-lib</id>
        <goals>
          <goal>run</goal>
        </goals>
        <phase>package</phase>
        <configuration>
          <tasks>
            <copy
                file="${project.build.directory}/${project.build.finalName}.${project.packaging}"
                tofile="${some.lib.dir}/${project.artifactId}.${project.packaging}" />
          </tasks>
        </configuration>
      </execution>
    </executions>
  </plugin>

This allows "Resolve dependencies from Workspace projects" to work.