What is the failure you get? The wagon should continue to work with
2.0.9.
Also, it is a common misconception that you need to use this wagon for
repository managers - most actually work without it (just drop dav:
from the front of your URL). It is only required on an actual DAV
server which won't create parent directories automatically.
- Brett
On 21/10/2008, at 7:50 PM, Julien Stern wrote:
Hi list,
I'm sure that many people have encountered the same issue, but I did
not find a way to solve it...
In our master pom, we define the wagon extension:
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>
This works fine with 2.0.7 and 2.0.8, but fails with 2.0.9.
Apparently, this is because wagon is now included with 2.0.9.
OK. Fine, but if I remove the extension, it fails with 2.0.7 and
2.0.8.
So, I tried to use profiles, activated based on the Maven version,
but profiles do not allow to define extensions.
So, how can I ensure that my projects will work both with 2.0.8 and
2.0.9 ? Currently, I have to choose either one or the other, but not
both.
Thanks,
--
Julien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
