[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wtp-incubator-dev] Build problem
|
David the problem seems to be with when the XSL Source feature is built
during the SDK build process. If this feature isn't already built, it
appears to be trying to grab the old 0.5 source feature and including
this. I have temporarily taken out from the SDK feature, the inclusion
of the source feature. As soon as i did this, the build made it past
the error that Doug was getting.
I've noticed problems with the Include feature option, in that it
appears to look at the target platform, and then only build if it can't
find a feature that is already built. Anyways, it appears the issue
that you ran into on your dev machine, is the same issue that is
happening on the build machine.
We should add the source feature back in after doing some more debugging
with the build machine on when and how the source features actually get
built.
Dave
David M Williams wrote:
I have a partial theory on what's wrong ... but, not sure. Just
thought I'd mention my observations.
Some of the xsl bundles have a "point" pre-req, such as
org.eclipse.jdt.launching;/bundle-version/="3.4.0",
These should be ranges.
They are not the source of the error, though, since the code itself
builds ... it's just having trouble when it starts building the source
jars.
Second, there _is_ some "0.5" versions of XSL in the environment,
since we just pull in the wst zip file, and unzip (in this stand alone
build) so, PDE is somehow getting mixed up and trying to satisfy the
constraints with those lower versions. (not sure why).
My guess is XSL is still building ok in the whole-WTP build, since
there we don't have conflicting/confusing versions.
So ... one solution, for this stand alone build, might be to get a
more exact version of the pre-reqs, so "old" versions are not left
around while the new version is building ... but, a little surprised
that's required, and that PDE build isn't smart enough to figure it
out (it seems smart enough for the code parts).
I had trouble doing a PDE build in my dev. env. for the SDK feature
... if I had the 0.5 versions as part of my dev. environment. Once I
deleted those, things seemed to build better in my environment.
News for now ...
From: David M Williams/Raleigh/IBM@IBMUS
To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date: 08/29/2008 12:56 PM
Subject: Re: [wtp-incubator-dev] Build problem
------------------------------------------------------------------------
Yes, I checked and it is pulling map files from HEAD.
I've studied for an hour or two, and can't see what the problem might be.
If I were to debug it, I'd start by reverting to some simpler cases,
of just the few minimum plugins,
and try adding them back in one by one, so to speak.
From: David Carver <d_a_carver@xxxxxxxxx>
To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Date: 08/29/2008 12:36 PM
Subject: Re: [wtp-incubator-dev] Build problem
------------------------------------------------------------------------
DOUG SATCHWELL wrote:
> The build is still failing...with a similar but slightly different
error: "Unable to find plug-in:
org.eclipse.wst.xsl.core.source_0.5.0.v200808080616."
>
> Not sure what the problem could be, it works via the PDE build?
>
>
David, are we pulling the correct Map files from Head? I know that for
a while you had set it up to pull from a branch.
Dave
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@eclipse.org_
__https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev_
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
------------------------------------------------------------------------
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
