Well, yee-haw then. :P
On Feb 4, 2010, at 10:36 AM, Jon Schneider wrote:
Please do. I think it would be advantageous to build the final
IvyDE 2.1.0
with this fix as well.
Jon
On Thu, Feb 4, 2010 at 10:24 AM, Matt Benson
wrote:
Okay, all the silly questions notwithstanding, I was act
Please do. I think it would be advantageous to build the final IvyDE 2.1.0
with this fix as well.
Jon
On Thu, Feb 4, 2010 at 10:24 AM, Matt Benson wrote:
> Okay, all the silly questions notwithstanding, I was actually able to
> muddle through this. ;) As it turns out, the Pulse-managed Eclip
Okay, all the silly questions notwithstanding, I was actually able to
muddle through this. ;) As it turns out, the Pulse-managed Eclipse
installations I've been using, even after adding Eclipse plugin
development plugins, are apparently not suitable as baseLocations for
the updatesite's b
Matt,
Just dump the contents of the dist directory into a folder (e.g. updatesite)
in any http server of your choice. That's it.
Jon
On Wed, Feb 3, 2010 at 3:07 PM, Matt Benson wrote:
> Hi, Jon. I realize from the text below that the problem here is a bug with
> this other tool, and believe
Hi, Jon. I realize from the text below that the problem here is a
bug with this other tool, and believe me, I have reported it. But
rank hath its privileges, and being in a position to affect the IvyDE
updatesite Hudson build I am inclined to selfishly do so. If it is
that big a deal I c
>From the Eclipse documentation concerning the pack200="true" attribute we
have on our updatesite:
"This lets the Update Manager know that the site contains packed jars, and
it will look for a .jar.pack.gz file beside the .jar file that it would
normally download. If the .jar.pack.gz file is found
My original email seems to have been lost; please see below:
On Feb 3, 2010, at 1:16 PM, Matt Benson wrote:
For fun I'll include the text of my patch file between --- and --- :
[SNIP]
---
On Feb 3, 2010, at 12:55 PM, Matt Benson wrote:
Apparently some tools (in particular I'm back to deali
For fun I'll include the text of my patch file between --- and --- :
---
Index: build.xml
===
--- build.xml (revision 906164)
+++ build.xml (working copy)
@@ -405,6 +405,7 @@
+
