Maven + NetBeans 6.7.1 (Wagon plugin)

[Cush1978]

I'm still having an issue I posted about before regarding a Maven project that works under NetBeans 6.5.1 and does not in NetBeans 6.7.1.

I'm using the latest Maven 2.2.1.

The project BUILDS fine under both versions of the NetBeans IDE. The project loads as a "Badly Formed Maven Project" in 6.7.1 and thus will not give me access to the project's source code.

I've tried wiping my entire Maven repository and that didn't change anything.

The issue is the wagon/webdav plugin as indicated by NetBeans:

The Extension or Plugin with Extensions with coordinates org.apache.maven.wagon:wagon-webdav:unknown was not found in the following remote repositories...

The wagon plugin is not distributed through a repository; it's part of the "uber" JAR packaged with Maven.

I don't know if it's matters, but the wagon plugin is not directly referenced by my project. All of our projects inherit from a hierarchy of parent projects that contain information common to all projects. The wagon plugin is referenced in one of them.

I've been stuck on 6.5.1 for months now because 6.7.1 is unusable for these projects.

[mkleint]

feel free to file a bug report. a sample project demonstrating the
problem is essential. it's a problem in maven embedder we ship with
netbeans. (3rd party code)
I don't quite follow your comment on uber jar. maven itself doesn't ship
with webdav wagon. and the message shown suggests you don't define
explicit version of the webdav wagon, while that might not be a problem
for command line maven, the embedder requires it (additionally it will
be faster (no repeated network pings) if you do declare the version

Milos


Cush1978 wrote:

[Cush1978]

OK, well I went up the POM hierarchy and sure enough, wagon-webdav is specified higher up, but does not have a version associated with it.

Does the Maven embedder require this to be specified at the highest level? Here's what I did:

- Added the plugin in my project (theoretically overriding the parent):

<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>
</extensions>
</build>

Unfortunately, I'm getting the exact same error message, which leads me to my question. For the purposes of the embedder does the version have to be specified at the highest level? i.e., is it bombing out in the parent before it even looks at my project to see that I have specified a version?

It's hard to build a good test case because I'm not an expert on Maven and I have to wade through all the parent POMs written by someone other than me. We have a "parent" POM, then a "core" POM, then a multi-project "super" POM, and finally my project which is one of the modules under the "super" project.

I've tried adding the webdav "version" at both the "super" POM and the "module" POM level without success. I'd like to confirm that it's needed higher than that before I go mucking with POMs I don't exactly own.

I saw a "wagon" package in the "uber" JAR, so I assumed that's where the webdav stuff was coming from. I was wrong about that; I guess it does exist in remote repositories.

Anyway, if a bug report needs to be filed, I'd like to narrow down exactly what's wrong before I do so. If you say the version *must* be specified, I'm thinking it might also have to be specified at the highest level of a given hierarchy. I think the embedder might work top-down and report an error before it sees the version specified later, but that's entirely a guess.

[Cush1978]

[mkleint]

Cush1978 wrote:

[Roti]

So we are waiting for hte 3.0 release of maven?

We have the same issue with 6.9.1:

The Extension or Plugin with Extensions with coordinates org.apache.maven.plugins:maven-dependency-plugin:2.2-SNAPSHOT was not found in the following remote repositories:
...
central (http://repo1.maven.org/maven2)
...

Unable to complete the construction of the Maven Project instance. Please fix your project. Possible causes of the problem and solutions are described on a Wiki page, click the Open Wiki Page button to view the page.

With no version in the root pom.