[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] request: test workaround for java 7 bug


On Sun, May 6, 2012 at 9:38 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi Ian,

I thought that if both the .jar and the .jar.pack.gz were present...as is the case in this repo now:

http://download.eclipse.org/rt/ecf/3.5Test/site.p2

that it would not make any difference...because the non-packed jar would be used...i.e. org.jivesoftware.smack...jar

Ah sorry, I didn't test that. I misread the email. I thought we finally found a way to include the unpacked jar inside a bundle. Yes, Pascal's comment still stands.  Maybe somebody else can double check that things actually work now.


...i.e. as per Pascal's comment:   https://bugs.eclipse.org/bugs/show_bug.cgi?id=361628#c32

A little more broadly:  Is there some procedure or workaround...short of restructuring this bundle completely (which isn't an ECF-authored bundle or lib)...that we can use to avoid this problem with pack/unpack in the installation of this bundle and it's internal jars?

If we only list the canonical (unpacked jars) , then this won't be a problem at all. However, users will need to download the un-optimized version  (which sucks).   

The only other option is for us (p2) to include the version of Java that was used to packed the jar, and then use that logic to determine if we should download the optimized (pack.gz) or canonical (unpacked jars).  I'm not sure how invasive a change this is though.

Cheers,
Ian
 

Thanks,

Scott




On 5/6/2012 8:25 PM, Ian Bull wrote:
I'm still seeing the pack.gz inside the bundles (and by me, I mean the jar processor is seeing that).

/var/folders/jm/k2r4m3d960gdxdmtk38t6trm0000gn/T/work6536702224461142051/temp.p2.optimizers.incoming4166018997375651433.jar/jars/xpp.jar.pack.gz

- ian


On Sat, May 5, 2012 at 8:59 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
Hi Markus,

Thanks much.

Those with java 7 (Wim and others)...could you please try installing ECF from

http://download.eclipse.org/rt/ecf/3.5Test/site.p2

and report results on

https://bugs.eclipse.org/bugs/show_bug.cgi?id=376306

Thanks,

Scott



On 5/5/2012 2:52 AM, Markus Alexander Kuppe wrote:
On 05/04/2012 06:16 PM, Scott Lewis wrote:

I see from the bug and consulting the template config that the template
has -Dsite.retain.unpacked=true...which I assume means that the jars (as
well as the .pack.gz files) should both be in the target repo...but when
I consult the build output for a release build...e.g 71

https://build.ecf-project.org/jenkins/job/R-HEAD-sdk.feature/71/artifact/site.p2/plugins/


I don't see the .jars there (there are jars...it's just that they are
only the source jars).

Do you understand why the jars for the bundles themselves are not also
there already?  Is there something else that must be done?
You are looking at an older build. #72
https://build.ecf-project.org/jenkins/job/R-HEAD-sdk.feature/72/artifact/site.p2/plugins/
has .jars

Markus
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev



--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev




--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource