Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ecf-dev] Re: platform integration build not producing jars

On 05/21/2010 07:02 PM, Scott Lewis wrote:
> Hi Markus and Ted,
> 
> The p2 folks identified a bug/enhancement in ECF that I've fixed:
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=313519
> 
> Now, I'm trying to do a build for the platform usage, and so as usual I
> did this build:
> 
> https://ecf2.osuosl.org/hudson/job/I-HEAD-platform.feature/39/
> 
> It succeeded just fine...and on dev.eclipse.org there is this also this
> directory (as expected):
> 
> /home/data/users/slewis/downloads/rt/ecf/integration/platform/v2010-05-21_07-28-37
> 
> aka
> /home/data/httpd/download.eclipse.org/rt/ecf/integration/platform/v2010-05-21_07-28-37
> 
> 
> All this is as expect.  The difficulty, however, is that when I look in
> the plugins directory, however, I don't see any jar files (except source
> jars).  There are the pack.gz.jar files, but that's not what's needed to
> provide to the p2 consume bug (i.e.
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=219499
> 
> Is there some way to change this I build to produce the individual
> plugin jars rather than the pack.gz?  It used to do this
> automatically...I don't know what if anything changed.
> 
> Thanks for any info.
> 
> Scott

Hi,

the fact that Hucky only produces pack.gz is a result of bug #302243 and
a subsequent (offline) discussion among David Williams and the two of us.

If ECF has to produce plain jars for the platform feature, we will have
to make site.pack200 configurable in the Template-Build by adding one
more environment var. All the builds then need to set this environment
variable (no "inheritance" of env vars yet). But what I don't get is,
why p2 cannot consume a valid p2 repo?

Btw. please comment on bug #312395 [1]. It relates to this issue.

Markus

[0] https://bugs.eclipse.org/bugs/show_bug.cgi?id=302243
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=312395

P.S.: I took the liberty of posting to ecf-dev instead so it gets
archived for future reference.


Back to the top