| p2-enabled PDE build fails when p2.category.definition is set (seemingly valid categories.xml file) [message #539204] |
Wed, 09 June 2010 23:21  |
 Troy Nichols
Messages: 28
Registered: July 2009 |
Junior Member |
|
|
I'd like to echo an unanswered question from a while back (9/30/2009 -
James Peltzer, see here:
http://www.eclipse.org/forums/index.php?t=msg&goto=48911 0&).
That problem is exactly the same one I'm having. Building with
p2.gathering turned on works fine, unless p2.category.definition is also
turned on. And like James, it does appear to be finding my
categories.xml file, but it fails with the bizarre error message of
"missing dependencies," for plugins which are part of my project, and
are indeed present and accounted for.
Here are the contents of my categories.xml
<?xml version="1.0" encoding="UTF-8"?>
<site>
<feature
url="features/com.intervoice.gtf.feature_2.0.0.qualifier.jar "
id="com.intervoice.gtf.feature" version="2.0.0.qualifier">
<category name="ToolingFeatures"/>
</feature>
<feature
url=" features/com.intervoice.doc.tooling.feature_2.0.0.qualifier. jar "
id="com.intervoice.doc.tooling.feature" version="2.0.0.qualifier">
<category name="DocFeatures"/>
</feature>
<category-def name="ToolingFeatures" label="Tooling Features">
<description>
Interaction Composer tooling features, including IC Diagram
Editors and SCXML Exporter.
</description>
</category-def>
<category-def name="DocFeatures" label="Documentation">
<description>
Interaction Composer Documentation Features. This includes IC
help files and user guide.
</description>
</category-def>
</site>
This file is sitting in the ${buildDirectory} dir, which I gather is the
right place for it (right?).
Thanks,
Troy Nichols
Dallas, TX, USA.
|
|
|
| Re: p2-enabled PDE build fails when p2.category.definition is set (seemingly valid categories.xml fi [message #539681 is a reply to message #539204] |
Fri, 11 June 2010 20:17  |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
The location of the category.xml (or site.xml) doesn't really matter
provided the property points to the correct location.
I'm not sure how adding the category stuff would break things like this.
Unless there is some sort of exception that is screwing things up.
If you can create a little example that reproduces the problem it would be
worth raising a bug on pde/build.
-Andrew
Troy Nichols wrote:
> I'd like to echo an unanswered question from a while back (9/30/2009 -
> James Peltzer, see here:
> http://www.eclipse.org/forums/index.php?t=msg&goto=48911 0&).
>
> That problem is exactly the same one I'm having. Building with
> p2.gathering turned on works fine, unless p2.category.definition is also
> turned on. And like James, it does appear to be finding my
> categories.xml file, but it fails with the bizarre error message of
> "missing dependencies," for plugins which are part of my project, and
> are indeed present and accounted for.
>
> Here are the contents of my categories.xml
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <site>
> <feature
> url="features/com.intervoice.gtf.feature_2.0.0.qualifier.jar "
> id="com.intervoice.gtf.feature" version="2.0.0.qualifier">
> <category name="ToolingFeatures"/>
> </feature>
> <feature
> url=" features/com.intervoice.doc.tooling.feature_2.0.0.qualifier. jar "
> id="com.intervoice.doc.tooling.feature" version="2.0.0.qualifier">
> <category name="DocFeatures"/>
> </feature>
> <category-def name="ToolingFeatures" label="Tooling Features">
> <description>
> Interaction Composer tooling features, including IC Diagram
> Editors and SCXML Exporter.
> </description>
> </category-def>
> <category-def name="DocFeatures" label="Documentation">
> <description>
> Interaction Composer Documentation Features. This includes IC
> help files and user guide.
> </description>
> </category-def>
> </site>
>
> This file is sitting in the ${buildDirectory} dir, which I gather is the
> right place for it (right?).
>
>
> Thanks,
> Troy Nichols
> Dallas, TX, USA.
|
|
|
| Re: p2-enabled PDE build fails when p2.category.definition is set (seemingly valid categories.xml fi [message #606002 is a reply to message #539204] |
Fri, 11 June 2010 20:17 |
Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
The location of the category.xml (or site.xml) doesn't really matter
provided the property points to the correct location.
I'm not sure how adding the category stuff would break things like this.
Unless there is some sort of exception that is screwing things up.
If you can create a little example that reproduces the problem it would be
worth raising a bug on pde/build.
-Andrew
Troy Nichols wrote:
> I'd like to echo an unanswered question from a while back (9/30/2009 -
> James Peltzer, see here:
> http://www.eclipse.org/forums/index.php?t=msg&goto=48911 0&).
>
> That problem is exactly the same one I'm having. Building with
> p2.gathering turned on works fine, unless p2.category.definition is also
> turned on. And like James, it does appear to be finding my
> categories.xml file, but it fails with the bizarre error message of
> "missing dependencies," for plugins which are part of my project, and
> are indeed present and accounted for.
>
> Here are the contents of my categories.xml
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <site>
> <feature
> url="features/com.intervoice.gtf.feature_2.0.0.qualifier.jar "
> id="com.intervoice.gtf.feature" version="2.0.0.qualifier">
> <category name="ToolingFeatures"/>
> </feature>
> <feature
> url=" features/com.intervoice.doc.tooling.feature_2.0.0.qualifier. jar "
> id="com.intervoice.doc.tooling.feature" version="2.0.0.qualifier">
> <category name="DocFeatures"/>
> </feature>
> <category-def name="ToolingFeatures" label="Tooling Features">
> <description>
> Interaction Composer tooling features, including IC Diagram
> Editors and SCXML Exporter.
> </description>
> </category-def>
> <category-def name="DocFeatures" label="Documentation">
> <description>
> Interaction Composer Documentation Features. This includes IC
> help files and user guide.
> </description>
> </category-def>
> </site>
>
> This file is sitting in the ${buildDirectory} dir, which I gather is the
> right place for it (right?).
>
>
> Thanks,
> Troy Nichols
> Dallas, TX, USA.
|
|
|
Powered by
FUDForum. Page generated in 0.03638 seconds
] 
Search
Help
Register
Login
Home
