This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 177788 - [68cat]Maven Wagon-WebDav is not working as expected.
Summary: [68cat]Maven Wagon-WebDav is not working as expected.
Status: RESOLVED DUPLICATE of bug 188871
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: PC Other
: P2 normal (vote)
Assignee: David Simonek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-28 15:44 UTC by fmonsalvo
Modified: 2010-07-22 15:55 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Unsuccessful attempt to reproduce in a dev build (3.70 KB, application/zip)
2010-07-22 15:55 UTC, Jesse Glick 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description fmonsalvo 2009-11-28 15:44:02 UTC 
I'm experiencing a bug that seems to be present on NB 6.7.1 and hasn't
yet been fixed.
The bug I'm talking about is that any maven project containing maven
wagon-webdav plugin with no defined version is not correctly open in
the IDE and showing the "Badly Formed Maven Project" message.
If I even add a version for that project I still have problems with
the child modules, the only way I found to fix this on some modules is
to redefine the wagon-webdav declaration on every pom, but still
couldn't fix every project in the hierarchy.
Here's an old forum post about this issue:
http://forums.netbeans.org/ntopic13920.html
Comment 1 Milos Kleint 2009-11-30 00:29:40 UTC 
eventually to be fixed by upgrading to maven3 embedder. However the no-version declared scenario will not work either. m3 is not going to support the RELEASE and LATEST metaversions..
Comment 2 fmonsalvo 2009-11-30 10:06:51 UTC 
But it should be working now, since that configuration is accepted by Maven 2.
Comment 3 Milos Kleint 2009-11-30 23:36:31 UTC 
well, the released 2.x maven binaries cannot be embedded, so we currently using an svn trunk snapshot from Jun 2008. So it can be a bug in that codebase or something that was at that time considered a feature. In any case we will only see what works and wat not after we actually upgrade to latests alphas/betas of 3.0
Comment 4 Antonin Nebuzelsky 2010-03-01 03:02:08 UTC 
Milos, what's your plan with this issue in 6.9?
Comment 5 Milos Kleint 2010-03-01 03:19:37 UTC 
there is no plan for 6.9. That's why the target milestone is set to next. IMHO only fixable by upgrading to maven3.
Comment 6 Jesse Glick 2010-07-22 15:54:21 UTC 
Maybe fixed by M3 embedder. I did not manage to reproduce your problem using the current embedder; no sample project ZIP was provided to test against.

*** This bug has been marked as a duplicate of bug 188871 ***
Comment 7 Jesse Glick 2010-07-22 15:55:36 UTC 
Created attachment 100988 [details]
Unsuccessful attempt to reproduce in a dev build

If unpacked, the two projects can be opened and built without apparent error in a dev build. Perhaps I am missing some crucial detail of project setup. If so, attach your test case and reopen for reevaluation.