Hi Dscho,<br><br><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">And sure enough, they don't, because Maven 3 no longer accepts the wagon<br>
extension in its current form.<br></blockquote>
<br>I tested your change on my local system with Maven 3.0.4, but unfortunately it breaks the build:<br><br>[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project pom-ij-base: Failed to deploy artifacts/metadata: No connector available to access repository imagej.snapshots (dav:<a href="http://maven.imagej.net/content/repositories/snapshots">http://maven.imagej.net/content/repositories/snapshots</a>) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1]<br>
<br>However, on my system with the wagon-webdav extension still in place, the deploy works fine. So our experiences are not in line here; Maven 3 + wagon-webdav works for me. Could there be some other cause to the problems you're seeing?<br>
<br><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Since Maven 2.2.1 is the current Maven 2 version and even if I do not know<br>
what version m2e bundles, it seems to compile fine in my m2e<br>
installation, so I assume it is newer than 2.0.9.<br></blockquote>
<br>I agree that we do not need to support Maven 2.0.x. If our builds work with Maven 2.2.x and 3.0.x, then I am happy. (Actually, I am happy even if we require Maven 3, although there are some arguments not to limit ourselves that way.)<br>
<br><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
P.S.: I needed to install Eclipse for all three Operating Systems<br>
supported by Fiji so I can make sure that the changes I intend to make on<br>
SwingOutputWindow do not break existing functionality (as I am on Linux, I<br>
always get these crappy scrollbars, and I verified that the same happens<br>
on Windows, but not on MacOSX, so I guess that some overly specific<br>
dimensioning code is responsible that assumes a bit too much).<br></blockquote>
<br>The crappy scroll bars have been a continuing nuisance. I think it may be a bug in JHotDraw. See also:<br> <a href="https://github.com/imagej/imagej/blob/master/ui/awt-swing/swing/ui-base/src/main/java/imagej/ui/swing/display/JHotDrawImageCanvas.java#L294">https://github.com/imagej/imagej/blob/master/ui/awt-swing/swing/ui-base/src/main/java/imagej/ui/swing/display/JHotDrawImageCanvas.java#L294</a><br>
<br>I certainly agree that this hack of "+5 in both dimensions" is overly specific. If you have a better idea, that's great.<br><br>Regards,<br>Curtis<br><br><br><div class="gmail_quote">On Mon, Feb 27, 2012 at 7:16 PM, Johannes Schindelin <span dir="ltr"><<a href="mailto:Johannes.Schindelin@gmx.de">Johannes.Schindelin@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
unfortunately, I updated the instructions on <a href="http://developer.imagej.net/" target="_blank">http://developer.imagej.net/</a><br>
on how to install Eclipse a bit prematurely: I was so happy that Eclipse<br>
IDE for Java Developers already brought its own Maven plugin that I<br>
edited the text to say that we prefer that version. Without checking that<br>
things actually compile.<br>
<br>
And sure enough, they don't, because Maven 3 no longer accepts the wagon<br>
extension in its current form.<br>
<br>
Now, a little research shows that somebody official _claims_ that starting<br>
with Maven 2.0.9, specifying that wagon extension for WebDAV is not at all<br>
necessary, it should be active by default.<br>
<br>
Since Maven 2.2.1 is the current Maven 2 version and even if I do not know<br>
what version m2e bundles, it seems to compile fine in my m2e<br>
installation, so I assume it is newer than 2.0.9.<br>
<br>
The only thing I am worried about: WebDAV is needed for deploying, too.<br>
And I have no idea how to test that (not without risking the heavens to<br>
break open and the archangels to hunt me down).<br>
<br>
So I'd like your help: could you test this commit?<br>
<br>
<a href="https://github.com/imagej/imagej/commit/2c755b58032c2f74d1a336c80166deedfb86e5e2" target="_blank">https://github.com/imagej/imagej/commit/2c755b58032c2f74d1a336c80166deedfb86e5e2</a><br>
<br>
(I guess that I implictly mean you, Curtis ;-)<br>
<br>
Ciao,<br>
Dscho<br>
<br>
P.S.: I needed to install Eclipse for all three Operating Systems<br>
supported by Fiji so I can make sure that the changes I intend to make on<br>
SwingOutputWindow do not break existing functionality (as I am on Linux, I<br>
always get these crappy scrollbars, and I verified that the same happens<br>
on Windows, but not on MacOSX, so I guess that some overly specific<br>
dimensioning code is responsible that assumes a bit too much).<br>
</blockquote></div><br>