Home » Eclipse Projects » Rich Client Platform (RCP) » Product Build fails unable to parse empty org.eclipse.pde.build.container.feature/feature.xml file
| |
| Re: Product Build fails unable to parse empty org.eclipse.pde.build.container.feature/feature.xml fi [message #452111 is a reply to message #452109] |
Sat, 01 July 2006 10:24   |
 Binil Thomas
Messages: 5
Registered: July 2009 |
Junior Member |
|
|
I edited the productBuild.xml to invoke eclipse.generateFeature task
with verify=false. I am no longer getting the error I was getting, and
the product seems to have built fine.
But I am clueless on the consequences this change has :-) Can someone
please help with some insight, advice etc.
Thanks,
Binil
Binil Thomas wrote:
> The error comes from the following target from productBuild.xml:
>
> <!-- ============================================================ =========
> Generate a container feature based on the product file The plugin or
> feature containing the .product file will need to exist already, use
> preSetup or postSetup to fetch it if necessary
> ============================================================ ========= -->
> <target name="generateFeature">
> <eclipse.generateFeature
> featureId="org.eclipse.pde.build.container.feature"
> buildDirectory="${buildDirectory}"
> baseLocation="${baseLocation}"
> productFile="${product}"
> verify="${verify}"
> pluginPath="${pluginPath}"
> configInfo="${configs}"
> />
> </target>
>
> This target is invoked twice; the first time verify is set to false, the
> second time it is set to true. After the first invocation of
> eclipse.generateFeature,
> ${buildDirectory}/features/org.eclipse.pde.build.container.f eature/feature.xml
> is non-empty and contains the following content:
>
> <feature id="org.eclipse.pde.build.container.feature" version="1.0.0">
> <includes id="my.feature" version="0.0.0"/>
> <includes optional="true"
> id="org.eclipse.platform.launchers" version="0.0.0"/>
> </feature>
>
> By the second invocation of the generateFeature target, the feature.xml
> goes empty and I get the error posted earlier.
>
> Can someone help me fix this error.
>
> Thanks,
> Binil
>
> Binil Thomas wrote:
>> Hi all,
>>
>> I am trying to build an RCP application. My environment is:
>> OS: Win2K
>> Eclipse: 3.2-RC7
>>
>> I am following the instructions in the help entry "Building an RCP
>> application from a product configuration file". My build fails with
>> the message:
>>
>> BUILD FAILED
>> D:\work\twms\eclipse-3.2RC7\plugins\org.eclipse.pde.build_3. 2.0.v20060601\scripts\productBuild\productBuild.xml:21:
>> The following error occurred while executing this line:
>> D:\work\twms\eclipse-3.2RC7\plugins\org.eclipse.pde.build_3. 2.0.v20060601\scripts\productBuild\productBuild.xml:45:
>> Problems parsing the feature
>> file:D:/work/twms/repo/packager/build/product/features/org.e clipse.pde.build.container.feature/feature.xml.
>>
>>
>> I did not put the org.eclipse.pde.build.container.feature in the build
>> directory/features - it was created by the build script. But the file
>> org.eclipse.pde.build.container.feature/feature.xml is empty.
>>
>> A similar issue was mentioned earlier at
>> http://www.eclipsezone.com/eclipse/forums/t74754.html, but I really am
>> not able to understand the "fix" suggested by the original poster.
>>
>> Can someone here guide me towards fixing this?
>>
>> Thanks,
>> Binil
|
|
|
| Re: Product Build fails unable to parse empty org.eclipse.pde.build.container.feature/feature.xml [message #452145 is a reply to message #452111] |
Mon, 03 July 2006 12:45 |
Chris Vines
Messages: 15
Registered: July 2009 |
Junior Member |
|
|
Hi Binil,
I got around this problem by fixing what I think is the problem in
BuildTimeSite.java
After debugging I found that BuildTimeSite#findFeature() tries to get a
feature by loading each feature.xml in turn and checking the feature ID for
a match. For some reason on Linux it can't load the generated feature.xml
for org.eclipse.pde.build.container.feature so it throws an exception. It
might be something to do with the way Linux reads from a file that has been
written to but not closed.
Attached is my temporary patch that I have applied to get the build to work.
Regards
Chris
"Binil Thomas" <binil.thomas@gmail.com> wrote in message
news:e85idc$3kp$1@utils.eclipse.org...
>I edited the productBuild.xml to invoke eclipse.generateFeature task
> with verify=false. I am no longer getting the error I was getting, and
> the product seems to have built fine.
>
> But I am clueless on the consequences this change has :-) Can someone
> please help with some insight, advice etc.
>
> Thanks,
> Binil
>
> Binil Thomas wrote:
>> The error comes from the following target from productBuild.xml:
>>
>> <!--
>> ============================================================ =========
>> Generate a container feature based on the product file The plugin or
>> feature containing the .product file will need to exist already, use
>> preSetup or postSetup to fetch it if necessary
>> ============================================================ ========= -->
>> <target name="generateFeature">
>> <eclipse.generateFeature
>> featureId="org.eclipse.pde.build.container.feature"
>> buildDirectory="${buildDirectory}"
>> baseLocation="${baseLocation}"
>> productFile="${product}"
>> verify="${verify}"
>> pluginPath="${pluginPath}"
>> configInfo="${configs}"
>> />
>> </target>
>>
>> This target is invoked twice; the first time verify is set to false, the
>> second time it is set to true. After the first invocation of
>> eclipse.generateFeature,
>> ${buildDirectory}/features/org.eclipse.pde.build.container.f eature/feature.xml
>> is non-empty and contains the following content:
>>
>> <feature id="org.eclipse.pde.build.container.feature" version="1.0.0">
>> <includes id="my.feature" version="0.0.0"/>
>> <includes optional="true"
>> id="org.eclipse.platform.launchers" version="0.0.0"/>
>> </feature>
>>
>> By the second invocation of the generateFeature target, the feature.xml
>> goes empty and I get the error posted earlier.
>>
>> Can someone help me fix this error.
>>
>> Thanks,
>> Binil
>>
>> Binil Thomas wrote:
>>> Hi all,
>>>
>>> I am trying to build an RCP application. My environment is:
>>> OS: Win2K
>>> Eclipse: 3.2-RC7
>>>
>>> I am following the instructions in the help entry "Building an RCP
>>> application from a product configuration file". My build fails with
>>> the message:
>>>
>>> BUILD FAILED
>>> D:\work\twms\eclipse-3.2RC7\plugins\org.eclipse.pde.build_3. 2.0.v20060601\scripts\productBuild\productBuild.xml:21:
>>> The following error occurred while executing this line:
>>> D:\work\twms\eclipse-3.2RC7\plugins\org.eclipse.pde.build_3. 2.0.v20060601\scripts\productBuild\productBuild.xml:45:
>>> Problems parsing the feature
>>> file:D:/work/twms/repo/packager/build/product/features/org.e clipse.pde.build.container.feature/feature.xml.
>>>
>>>
>>> I did not put the org.eclipse.pde.build.container.feature in the build
>>> directory/features - it was created by the build script. But the file
>>> org.eclipse.pde.build.container.feature/feature.xml is empty.
>>>
>>> A similar issue was mentioned earlier at
>>> http://www.eclipsezone.com/eclipse/forums/t74754.html, but I really am
>>> not able to understand the "fix" suggested by the original poster.
>>>
>>> Can someone here guide me towards fixing this?
>>>
>>> Thanks,
>>> Binil
|
|
| |
| Re: Product Build fails unable to parse empty org.eclipse.pde.build.container.feature/feature.xml fi [message #453072 is a reply to message #452438] |
Fri, 21 July 2006 09:54 |
Aodh O'Lionaird
Messages: 4
Registered: July 2009 |
Junior Member |
|
|
Hello,
I'm experiencing a similar problem. I applied the BuildTimeSite.java patch
and still no go. When I set verify="false" in productBuild.xml as suggested
by Binil Thomas I get dependency related errors.
Plug-in based product build works perfectly but this is inadequate as a
feature based product build will allow test features etc. to be included
easily.
As a work around I will probably have to create a separate product for test
etc. and do two builds.
The exact error is:
BUILD FAILED
C:\Documents and Settings\aolionaird\builder2\ProductBuilder\build.xml:49:
The following error occurred while executing this line:
C:\callisto\eclipse\plugins\org.eclipse.pde.build_3.2.0.v200 60603\scripts\product
Build\productBuild.xml:21: The following error occurred while executing
this
line:C:\calisto\eclipse\plugins\org.eclipse.pde.build_3.2.0. v20060603\scripts\productBuild\productBuild.xml:45:
Problems parsing the feature
file:C:/SSP_Build/features/org.eclipse.pde.build.container.f eature/feature.xml.
Total time: 32 seconds
My platform is: WinXP Pro SP2, x86, Eclipse 3.2.
I hope someone can help..
Thanks,
Aodh.
"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:e8gq98$80a$1@utils.eclipse.org...
> Can someone please raise a bug on pde build with steps to reproduce this.
>
> When verify == true, the following things occur:
> 1. Any plugins being added to the container.feature are verified to exist
> and resolve properly.
> 2. Platform dependent fragments are included only in their correct os,
> ws, & arch configurations.
> 3. Any features being added to the container.feature are verified to
> exist.
>
> These steps are more important when your product is based on a plugin list
> instead of on a feature list.
>
> -Andrew
>
> Chris Vines wrote:
>> Hi Binil,
>>
>> I got around this problem by fixing what I think is the problem in
>> BuildTimeSite.java
>>
>> After debugging I found that BuildTimeSite#findFeature() tries to get a
>> feature by loading each feature.xml in turn and checking the feature ID
>> for a match. For some reason on Linux it can't load the generated
>> feature.xml for org.eclipse.pde.build.container.feature so it throws an
>> exception. It might be something to do with the way Linux reads from a
>> file that has been written to but not closed.
>>
>> Attached is my temporary patch that I have applied to get the build to
>> work.
>>
>> Regards
>> Chris
>>
>>
>>
>>
>>
>>
>>
>>
>> "Binil Thomas" <binil.thomas@gmail.com> wrote in message
>> news:e85idc$3kp$1@utils.eclipse.org...
>>
>>>I edited the productBuild.xml to invoke eclipse.generateFeature task
>>>with verify=false. I am no longer getting the error I was getting, and
>>>the product seems to have built fine.
>>>
>>>But I am clueless on the consequences this change has :-) Can someone
>>>please help with some insight, advice etc.
>>>
>>>Thanks,
>>>Binil
>>>
>>>Binil Thomas wrote:
|
|
|
| Re: Product Build fails unable to parse empty org.eclipse.pde.build.container.feature/feature.xml fi [message #453260 is a reply to message #453072] |
Tue, 25 July 2006 07:34 |
Remo Ferrari
Messages: 3
Registered: July 2009 |
Junior Member |
|
|
Hi there
Same problem here. I am also trying to run the PDE build in headless
mode under Linux for a product that is based on features.
I tried setting the eclipse.generateFeature's verify flag to false and
it worked, but i'm not comfortable with it.
I did not try out the proposed patch for basically the same reason.
What works for me is this:
o in build.properties i set the flags skipMaps and skipFetch to true, so
that my features and plugins are NOT fetched from cvs automatically
based on a map-file.
o in my own customTargets.xml i use the target postSetup to fetch the
needed plugins and features myself and put them into the
buildDirectorys plugins and features directory.
Now i no longer get the error, but frankly, i'm not sure why.
And i probably should mention, that all this is rather new for me and my
workaround should be judged accordingly.
I will happily dump my approach and go back to the more integrated
checkout if this "issue" gets resolved.
Cheers
Remo 8-)
Aodh O'Lionaird wrote:
> Hello,
>
> I'm experiencing a similar problem. I applied the BuildTimeSite.java patch
> and still no go. When I set verify="false" in productBuild.xml as suggested
> by Binil Thomas I get dependency related errors.
>
> Plug-in based product build works perfectly but this is inadequate as a
> feature based product build will allow test features etc. to be included
> easily.
>
> As a work around I will probably have to create a separate product for test
> etc. and do two builds.
>
> The exact error is:
>
> BUILD FAILED
>
> C:\Documents and Settings\aolionaird\builder2\ProductBuilder\build.xml:49:
> The following error occurred while executing this line:
> C:\callisto\eclipse\plugins\org.eclipse.pde.build_3.2.0.v200 60603\scripts\product
>
> Build\productBuild.xml:21: The following error occurred while executing
> this
> line:C:\calisto\eclipse\plugins\org.eclipse.pde.build_3.2.0. v20060603\scripts\productBuild\productBuild.xml:45:
>
>
> Problems parsing the feature
> file:C:/SSP_Build/features/org.eclipse.pde.build.container.f eature/feature.xml.
>
>
> Total time: 32 seconds
>
> My platform is: WinXP Pro SP2, x86, Eclipse 3.2.
>
> I hope someone can help..
>
> Thanks,
>
> Aodh.
>
> "Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
> news:e8gq98$80a$1@utils.eclipse.org...
>> Can someone please raise a bug on pde build with steps to reproduce this.
>>
>> When verify == true, the following things occur:
>> 1. Any plugins being added to the container.feature are verified to
>> exist
>> and resolve properly.
>> 2. Platform dependent fragments are included only in their correct os,
>> ws, & arch configurations.
>> 3. Any features being added to the container.feature are verified to
>> exist.
>>
>> These steps are more important when your product is based on a plugin
>> list
>> instead of on a feature list.
>>
>> -Andrew
>>
>> Chris Vines wrote:
>>> Hi Binil,
>>>
>>> I got around this problem by fixing what I think is the problem in
>>> BuildTimeSite.java
>>>
>>> After debugging I found that BuildTimeSite#findFeature() tries to get a
>>> feature by loading each feature.xml in turn and checking the feature ID
>>> for a match. For some reason on Linux it can't load the generated
>>> feature.xml for org.eclipse.pde.build.container.feature so it throws an
>>> exception. It might be something to do with the way Linux reads from a
>>> file that has been written to but not closed.
>>>
>>> Attached is my temporary patch that I have applied to get the build to
>>> work.
>>>
>>> Regards
>>> Chris
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> "Binil Thomas" <binil.thomas@gmail.com> wrote in message
>>> news:e85idc$3kp$1@utils.eclipse.org...
>>>
>>>> I edited the productBuild.xml to invoke eclipse.generateFeature task
>>>> with verify=false. I am no longer getting the error I was getting, and
>>>> the product seems to have built fine.
>>>>
>>>> But I am clueless on the consequences this change has :-) Can someone
>>>> please help with some insight, advice etc.
>>>>
>>>> Thanks,
>>>> Binil
>>>>
>>>> Binil Thomas wrote:
>
>
>
>
>
|
|
|
Goto Forum:
Current Time: Sat Oct 12 09:46:11 GMT 2024
Powered by FUDForum. Page generated in 0.04396 seconds |
] 
Search
Help
Register
Login
Home
