| [news.eclipse.tools.buckminster] Re: Build fails after headless resolve using p2 |
Scott Hendrickson wrote:
Hi Thomas,
Unfortunately, I am wanting to create a legacy update site. The cspec is what results from directly following the instructions for the "Update sites using the 3.4.x and earlier releases" on the page that you mentioned (without any of the optional features like groups; but, the error occurs when groups are present as well).
I hope that helps :)
Thanks, -- Scott
If you follow the instructions on the page to create a legacy update site, you'll run in to the same error.
-- Scott
Thomas Hallgren wrote:
Hi Scott,the create.site task in the
I looked at your build. Apparently you have handcrafted a cspec that callsbuckminster.pdetasks script. That particular task did undergo significantchanges when we moved to p2 which begs thequestion, what type of update site is it that you want to create? A legacyupdate site or a p2 repository? If it's thelatter, then you can simplify the creation of that update site a great dealby using the "Update sites using the 3.5release" section rather then the "Update sites using the 3.4.x and earlierreleases" on thehttp://wiki.eclipse.org/Building_an_Update_Site_using_Buckminster page.
Regards, Thomas Hallgren
http://tps.ics.uci.edu/svn/projects/infrastructure/trunk/edu.uci.isr.infrastructure.buckminster_build_test/build.xmlOn 08/19/2009 08:20 PM, Scott Hendrickson wrote:Scott Hendrickson wrote:
Thanks Thomas for fixing the second issue. Any ideas on the first?
1) edu.uci.isr.infrastructure.update_site_with_feature/${sp:manifest} doesn't exist (details below: [1])
NOTE: I updated the build script to insert the local path manually for the location using an xstl.
The build script is here:
-- Scott