You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Matt Benson <gu...@gmail.com> on 2010/02/03 20:16:07 UTC
Re: IvyDE updatesite packing again
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 @@
<fileset dir="${updatesite.dir}">
<include name="plugins/org.apache.ivy_*.jar" />
<include name="plugins/org.apache.ivy.eclipse*.jar" />
+ <include name="features/org.apache.ivy.*jar" />
</fileset>
</copy>
</target>
@@ -415,23 +416,34 @@
<copy todir="${work.dir}/updatesite">
<fileset dir="${updatesite.dir}">
<include name="plugins/org.apache.ivyde.*.jar" />
+ <include name="features/org.apache.ivyde.*.jar" />
</fileset>
</copy>
</target>
+ <macrodef name="siteOptimizerJarPack">
+ <attribute name="directory" />
+ <sequential>
+ <java classpath="${eclipse.classpath}"
classname="org.eclipse.core.launcher.Main"
+ fork="true" failonerror="true">
+ <arg value="-consolelog" />
+ <arg line="-application
org.eclipse.update.core.siteOptimizer" />
+ <arg line="-jarProcessor -verbose -processAll -pack" />
+ <arg line="-outputDir @{directory}" />
+ <arg line="@{directory}" />
+ </java>
+ </sequential>
+ </macrodef>
+
<target name="do-pack-jars" depends="eclipse-classpath">
<!-- launch the packing -->
- <java classpath="${eclipse.classpath}"
classname="org.eclipse.core.launcher.Main" fork="true"
failonerror="true">
- <arg value="-consolelog" />
- <arg line="-application
org.eclipse.update.core.siteOptimizer" />
- <arg line="-jarProcessor -verbose -processAll -pack" />
- <arg line="-outputDir ${work.dir}/updatesite/plugins" />
- <arg line="${work.dir}/updatesite/plugins" />
- </java>
+ <siteOptimizerJarPack directory="${work.dir}/updatesite/
plugins" />
+ <siteOptimizerJarPack directory="${work.dir}/updatesite/
features" />
<!-- put the packs back to the updatesite -->
<copy todir="${updatesite.dir}">
<fileset dir="${work.dir}/updatesite">
<include name="plugins/*.jar.pack.gz" />
+ <include name="features/*.jar.pack.gz" />
</fileset>
</copy>
</target>
@@ -479,6 +491,7 @@
<include name="plugins/org.apache.ivy*.jar" />
<include name="plugins/org.apache.ivy*.jar.pack.gz" />
<include name="features/org.apache.ivy*.jar" />
+ <include name="features/org.apache.ivy*.jar.pack.gz" />
<include name="digest.zip" />
</fileset>
</checksum>
@@ -487,6 +500,7 @@
<include name="plugins/org.apache.ivy*.jar" />
<include name="plugins/org.apache.ivy*.jar.pack.gz" />
<include name="features/org.apache.ivy*.jar" />
+ <include name="features/org.apache.ivy*.jar.pack.gz" />
<include name="digest.zip" />
</fileset>
</checksum>
@@ -498,6 +512,7 @@
<include name="plugins/org.apache.ivy*.jar" />
<include name="plugins/org.apache.ivy*.jar.pack.gz" />
<include name="features/org.apache.ivy*.jar" />
+ <include name="features/org.apache.ivy*.jar.pack.gz" />
<include name="digest.zip" />
</fileset>
</checksum>
@@ -512,6 +527,7 @@
<include name="plugins/org.apache.ivy*.jar" />
<include name="plugins/org.apache.ivy*.jar.pack.gz" />
<include name="features/org.apache.ivy*.jar" />
+ <include name="features/org.apache.ivy*.jar.pack.gz" />
<include name="digest.zip" />
</fileset>
</checksum>
---
On Feb 3, 2010, at 12:55 PM, Matt Benson wrote:
> Apparently some tools (in particular I'm back to dealing with
> Genuitec Pulse) want not only plugins but features jars to be
> packed. I can pretty well see how to add this to the updatesite
> build, but I don't have a whole lot of idea what is required for me
> to test my changes locally. Can either of you guys, Nicolas/Jon,
> help me with that? I'm hoping to do it all on Mac OSX Tiger w/
> Java 1.5....
>
> Thanks,
> Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE updatesite packing again
Posted by Matt Benson <gu...@gmail.com>.
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 <gu...@gmail.com>
> wrote:
>
>> 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
>> buildfile. After downloading a plugin-development-target Eclipse
>> installation and using that I was able to to create the optimized
>> artifacts,
>> and was able to use a filesystem-based updatesite from there to
>> verify that
>> the Pulse tool is now able to recognize the packed features jars.
>> So does
>> anyone oppose my committing my changes on trunk so that the Hudson
>> builds
>> will also pack these jars?
>>
>> Thanks,
>> Matt
>>
>>
>>
>> On Feb 3, 2010, at 3:15 PM, Jon Schneider wrote:
>>
>> 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
>>> <gu...@gmail.com> wrote:
>>>
>>> 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 could
>>>> use a locally staged updatesite to begin with, but this still
>>>> brings to a
>>>> head the problem I have which actually prompted my original
>>>> mail: I am
>>>> not
>>>> clear on how to set up my own local updatesite. ;)
>>>>
>>>> Thanks,
>>>> Matt
>>>>
>>>>
>>>> On Feb 3, 2010, at 2:58 PM, Jon Schneider wrote:
>>>>
>>>> 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, it will be
>>>>> downloaded
>>>>> and unpacked, otherwise the .jar file is downloaded as normal."
>>>>>
>>>>> This indicates to me that a reasonable local test would be to
>>>>> delete all
>>>>> but
>>>>> the packed jars from a locally staged update site and verify
>>>>> that the
>>>>> Update
>>>>> Manager will pick up the feature jar correctly.
>>>>>
>>>>> Jon
>>>>>
>>>>> On Wed, Feb 3, 2010 at 2:25 PM, Matt Benson <gu...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> 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 dealing with
>>>>>>> Genuitec
>>>>>>>
>>>>>>> Pulse) want not only plugins but features jars to be
>>>>>>> packed. I can
>>>>>>>> pretty
>>>>>>>> well see how to add this to the updatesite build, but I
>>>>>>>> don't have a
>>>>>>>> whole
>>>>>>>> lot of idea what is required for me to test my changes
>>>>>>>> locally. Can
>>>>>>>> either
>>>>>>>> of you guys, Nicolas/Jon, help me with that? I'm hoping to
>>>>>>>> do it all
>>>>>>>> on Mac
>>>>>>>> OSX Tiger w/ Java 1.5....
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Matt
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> -----
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE updatesite packing again
Posted by Jon Schneider <jk...@gmail.com>.
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 <gu...@gmail.com> wrote:
> 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
> buildfile. After downloading a plugin-development-target Eclipse
> installation and using that I was able to to create the optimized artifacts,
> and was able to use a filesystem-based updatesite from there to verify that
> the Pulse tool is now able to recognize the packed features jars. So does
> anyone oppose my committing my changes on trunk so that the Hudson builds
> will also pack these jars?
>
> Thanks,
> Matt
>
>
>
> On Feb 3, 2010, at 3:15 PM, Jon Schneider wrote:
>
> 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 <gu...@gmail.com> wrote:
>>
>> 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 could
>>> use a locally staged updatesite to begin with, but this still brings to a
>>> head the problem I have which actually prompted my original mail: I am
>>> not
>>> clear on how to set up my own local updatesite. ;)
>>>
>>> Thanks,
>>> Matt
>>>
>>>
>>> On Feb 3, 2010, at 2:58 PM, Jon Schneider wrote:
>>>
>>> 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, it will be
>>>> downloaded
>>>> and unpacked, otherwise the .jar file is downloaded as normal."
>>>>
>>>> This indicates to me that a reasonable local test would be to delete all
>>>> but
>>>> the packed jars from a locally staged update site and verify that the
>>>> Update
>>>> Manager will pick up the feature jar correctly.
>>>>
>>>> Jon
>>>>
>>>> On Wed, Feb 3, 2010 at 2:25 PM, Matt Benson <gu...@gmail.com>
>>>> wrote:
>>>>
>>>> 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 dealing with
>>>>>> Genuitec
>>>>>>
>>>>>> Pulse) want not only plugins but features jars to be packed. I can
>>>>>>> pretty
>>>>>>> well see how to add this to the updatesite build, but I don't have a
>>>>>>> whole
>>>>>>> lot of idea what is required for me to test my changes locally. Can
>>>>>>> either
>>>>>>> of you guys, Nicolas/Jon, help me with that? I'm hoping to do it all
>>>>>>> on Mac
>>>>>>> OSX Tiger w/ Java 1.5....
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Matt
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: IvyDE updatesite packing again
Posted by Matt Benson <gu...@gmail.com>.
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 buildfile. After downloading a plugin-development-
target Eclipse installation and using that I was able to to create
the optimized artifacts, and was able to use a filesystem-based
updatesite from there to verify that the Pulse tool is now able to
recognize the packed features jars. So does anyone oppose my
committing my changes on trunk so that the Hudson builds will also
pack these jars?
Thanks,
Matt
On Feb 3, 2010, at 3:15 PM, Jon Schneider wrote:
> 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 <gu...@gmail.com>
> wrote:
>
>> 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 could
>> use a locally staged updatesite to begin with, but this still
>> brings to a
>> head the problem I have which actually prompted my original mail:
>> I am not
>> clear on how to set up my own local updatesite. ;)
>>
>> Thanks,
>> Matt
>>
>>
>> On Feb 3, 2010, at 2:58 PM, Jon Schneider wrote:
>>
>> 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, it will be
>>> downloaded
>>> and unpacked, otherwise the .jar file is downloaded as normal."
>>>
>>> This indicates to me that a reasonable local test would be to
>>> delete all
>>> but
>>> the packed jars from a locally staged update site and verify that
>>> the
>>> Update
>>> Manager will pick up the feature jar correctly.
>>>
>>> Jon
>>>
>>> On Wed, Feb 3, 2010 at 2:25 PM, Matt Benson
>>> <gu...@gmail.com> wrote:
>>>
>>> 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 dealing with
>>>>> Genuitec
>>>>>
>>>>>> Pulse) want not only plugins but features jars to be packed.
>>>>>> I can
>>>>>> pretty
>>>>>> well see how to add this to the updatesite build, but I don't
>>>>>> have a
>>>>>> whole
>>>>>> lot of idea what is required for me to test my changes
>>>>>> locally. Can
>>>>>> either
>>>>>> of you guys, Nicolas/Jon, help me with that? I'm hoping to do
>>>>>> it all
>>>>>> on Mac
>>>>>> OSX Tiger w/ Java 1.5....
>>>>>>
>>>>>> Thanks,
>>>>>> Matt
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>> -------------------------------------------------------------------
>>>> --
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE updatesite packing again
Posted by Jon Schneider <jk...@gmail.com>.
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 <gu...@gmail.com> wrote:
> 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 could
> use a locally staged updatesite to begin with, but this still brings to a
> head the problem I have which actually prompted my original mail: I am not
> clear on how to set up my own local updatesite. ;)
>
> Thanks,
> Matt
>
>
> On Feb 3, 2010, at 2:58 PM, Jon Schneider wrote:
>
> 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, it will be
>> downloaded
>> and unpacked, otherwise the .jar file is downloaded as normal."
>>
>> This indicates to me that a reasonable local test would be to delete all
>> but
>> the packed jars from a locally staged update site and verify that the
>> Update
>> Manager will pick up the feature jar correctly.
>>
>> Jon
>>
>> On Wed, Feb 3, 2010 at 2:25 PM, Matt Benson <gu...@gmail.com> wrote:
>>
>> 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 dealing with Genuitec
>>>>
>>>>> Pulse) want not only plugins but features jars to be packed. I can
>>>>> pretty
>>>>> well see how to add this to the updatesite build, but I don't have a
>>>>> whole
>>>>> lot of idea what is required for me to test my changes locally. Can
>>>>> either
>>>>> of you guys, Nicolas/Jon, help me with that? I'm hoping to do it all
>>>>> on Mac
>>>>> OSX Tiger w/ Java 1.5....
>>>>>
>>>>> Thanks,
>>>>> Matt
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: IvyDE updatesite packing again
Posted by Matt Benson <gu...@gmail.com>.
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 could use a locally staged updatesite to begin
with, but this still brings to a head the problem I have which
actually prompted my original mail: I am not clear on how to set up
my own local updatesite. ;)
Thanks,
Matt
On Feb 3, 2010, at 2:58 PM, Jon Schneider wrote:
> 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, it will be
> downloaded
> and unpacked, otherwise the .jar file is downloaded as normal."
>
> This indicates to me that a reasonable local test would be to
> delete all but
> the packed jars from a locally staged update site and verify that
> the Update
> Manager will pick up the feature jar correctly.
>
> Jon
>
> On Wed, Feb 3, 2010 at 2:25 PM, Matt Benson <gu...@gmail.com>
> wrote:
>
>> 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 dealing with
>>> Genuitec
>>>> Pulse) want not only plugins but features jars to be packed. I
>>>> can pretty
>>>> well see how to add this to the updatesite build, but I don't
>>>> have a whole
>>>> lot of idea what is required for me to test my changes locally.
>>>> Can either
>>>> of you guys, Nicolas/Jon, help me with that? I'm hoping to do
>>>> it all on Mac
>>>> OSX Tiger w/ Java 1.5....
>>>>
>>>> Thanks,
>>>> Matt
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: IvyDE updatesite packing again
Posted by Jon Schneider <jk...@gmail.com>.
>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, it will be downloaded
and unpacked, otherwise the .jar file is downloaded as normal."
This indicates to me that a reasonable local test would be to delete all but
the packed jars from a locally staged update site and verify that the Update
Manager will pick up the feature jar correctly.
Jon
On Wed, Feb 3, 2010 at 2:25 PM, Matt Benson <gu...@gmail.com> wrote:
> 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 dealing with Genuitec
>>> Pulse) want not only plugins but features jars to be packed. I can pretty
>>> well see how to add this to the updatesite build, but I don't have a whole
>>> lot of idea what is required for me to test my changes locally. Can either
>>> of you guys, Nicolas/Jon, help me with that? I'm hoping to do it all on Mac
>>> OSX Tiger w/ Java 1.5....
>>>
>>> Thanks,
>>> Matt
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
Re: IvyDE updatesite packing again
Posted by Matt Benson <gu...@gmail.com>.
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 dealing with
>> Genuitec Pulse) want not only plugins but features jars to be
>> packed. I can pretty well see how to add this to the updatesite
>> build, but I don't have a whole lot of idea what is required for
>> me to test my changes locally. Can either of you guys, Nicolas/
>> Jon, help me with that? I'm hoping to do it all on Mac OSX Tiger
>> w/ Java 1.5....
>>
>> Thanks,
>> Matt
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org