Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Clarification of repo requirements for projects participating in Helios


Yes, it helps a little.

The thing to look at, for this issue, is your "plugins" folder in your repo (we try to call them repo's these days ... not update sites :)
It should contain both *.jar file, and a corresponding one that has same name, but ends with .pack.gz

For example, from ~/downloads/webtools/milestones
you'd see one example of

-rw-rw-r-- 1 david_williams webtoolsadmin    70772 2010-03-16 02:57 org.eclipse.wst.xsd.core_1.1.501.v200912170622.jar
-rw-rw-r-- 1 david_williams webtoolsadmin    24695 2010-03-16 02:57 org.eclipse.wst.xsd.core_1.1.501.v200912170622.jar.pack.gz

I looked in
~/downloads/jetty/integrations/7.0.2-SNAPSHOT/update/org.eclipse.jetty.osgi.site-7.0.2-SNAPSHOT/site

And saw only jars ... but, not every project "packs" every build, so not sure if that site is representative for your project.

And, I'll be quick to add, the need to have "optimized" (packed) jars files isn't new.
This thread is all about _leaving_ the jar files in your repo once you have the pack.gz files.
So you got the jar part down already :)

From a shell on build.eclipse.org, two good examples to look at are ~/downloads/webtools/milestones
or my favorite, ~/downloads/eclipse/updates/3.6milestones

Keep asking questions ...




From: Jesse McConnell <jesse.mcconnell@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 04/02/2010 04:34 PM
Subject: Re: [cross-project-issues-dev] Clarification of repo requirements for        projects participating in Helios
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx





I have the lionshare of all that stuff worked out, it would just be really nice if I had a directory listing of a 'perfect example' of a what the p2 repo needs to look like, specifically to address whatever is actually being added as a requirement based on this thread, so I could compare the output of my jetty build with the others to make sure I am not in violation..

I have it so that I can crack open a clean install of eclipse 3.6 and install jetty from my update site, all signed and packed...but it sounds like there are other things I need to make sure are included in the update site now that wouldn't necessarily tell me something is wrong based on my casual litmus test..

does that help explain what I need? 

--
jesse mcconnell

jesse.mcconnell@xxxxxxxxx


On Fri, Apr 2, 2010 at 14:20, David M Williams <david_williams@xxxxxxxxxx> wrote:

Backing up some ... are you looking for the general requirements for the Simultaneously Release?


Those are at

http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php

And it contains some explanations and links to other pages.


See also the general category on the wiki,


http://wiki.eclipse.org/Category:Helios

and the documents and other sites it points to.


Maybe some of those are what you are looking for?


Thanks,



From: Jesse McConnell <jesse.mcconnell@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 04/02/2010 03:37 PM
Subject: Re: [cross-project-issues-dev] Clarification of repo requirements for        projects participating in Helios
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx







I'm getting the impression that as Eclipse gets larger and more diverse, some things have to be better specified, to keep consistent, instead of just assuming "everyone knows", since that's increasingly not the case, as this example illustrates.



If I am not the poster boy for that statement I don't know who is :)

As near as i can tell I'll have to alter the maven plugin I have that prepares the jetty update site but I am still not 100% what changes I need to make based on this thread.

cheers,

jesse _______________________________________________

cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top