Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Problem exporting as Deployable Feature
Problem exporting as Deployable Feature [message #31911] Tue, 11 November 2008 10:18 Go to next message
Eclipse UserFriend
Originally posted by: jmordax.terra.es

Hi, I have a Feature Project that includes 6 Plug-ins Projects.
The testings work fine. The Plug-ins Projects build perfectly.
But when I try to export the Feature as a Deployable Feature, there are
tons of errors building (compiling) the Plug-in Projects. It complains
about all imports (for example, SWT classes). It is like the Java Build
Path is lost or something like that when build is fired from the Feature
export process.
BTW, if I export all plug-ins as Plug-in or Fragment it works fine.

This worked fine with Eclipse R3.2 and now it is failing with Eclipse
R3.4.1. Is there any change I am required to do in this new version?

The same problem happens creating a Site Project.

Thanks in advance,

Chemi.
Re: Problem exporting as Deployable Feature [message #31947 is a reply to message #31911] Tue, 11 November 2008 15:21 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: zx.code9.com

Chemi wrote:
> Hi, I have a Feature Project that includes 6 Plug-ins Projects.
> The testings work fine. The Plug-ins Projects build perfectly.
> But when I try to export the Feature as a Deployable Feature, there are
> tons of errors building (compiling) the Plug-in Projects. It complains
> about all imports (for example, SWT classes). It is like the Java Build
> Path is lost or something like that when build is fired from the Feature
> export process.
> BTW, if I export all plug-ins as Plug-in or Fragment it works fine.
>
> This worked fine with Eclipse R3.2 and now it is failing with Eclipse
> R3.4.1. Is there any change I am required to do in this new version?

Can you post your feature.xml?

Also, I assume you have nothing manually added to your build path, and
all dependencies are coming from Require-Bundle/Import-Package and your
Bundle-ClassPath is setup properly?

Cheers,

~ Chris
Re: Problem exporting as Deployable Feature [message #31978 is a reply to message #31947] Tue, 11 November 2008 16:06 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jmordax.terra.es

Chris Aniszczyk wrote:
> Can you post your feature.xml?
>
> Also, I assume you have nothing manually added to your build path, and
> all dependencies are coming from Require-Bundle/Import-Package and
> your Bundle-ClassPath is setup properly?
>
> Cheers,
>
> ~ Chris

Hi Chris.
But I have continued with my investigation during the day and I have
found "the problem" which doesn't make any sense to me.
The problem appears when you have more than one item listed in ws, os,
arch or nl properties.

For example with this content it fails:

<plugin
id="es.org.chemi.games.sokoban"
os="linux,win32"
ws="gtk,motif,win32"
nl="en"
arch="x86"
download-size="0"
install-size="0"
version="3.2.1"
unpack="false"/>

but with this one it works:

<plugin
id="es.org.chemi.games.sokoban"
os="linux"
ws="gtk"
nl="en"
arch="x86"
download-size="0"
install-size="0"
version="3.2.1"
unpack="false"/>

Does it make sense to you? what is the relationship between those
properties and Java compilation problems?
I have seen the same behavior with 3.3.2, 3.4.1 and 3.5M3

Thanks in advance,

Chemi.

I am going to try to create a dummy test case from scratch.
Re: Problem exporting as Deployable Feature [message #32048 is a reply to message #31978] Tue, 11 November 2008 19:13 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
PDE/Build doesn't support lists in the os/ws/arch entries.
I'm surprised this worked in 3.2

-Andrew

Chemi wrote:
> Chris Aniszczyk wrote:
>> Can you post your feature.xml?
>>
>> Also, I assume you have nothing manually added to your build path, and
>> all dependencies are coming from Require-Bundle/Import-Package and
>> your Bundle-ClassPath is setup properly?
>>
>> Cheers,
>>
>> ~ Chris
>
> Hi Chris.
> But I have continued with my investigation during the day and I have
> found "the problem" which doesn't make any sense to me.
> The problem appears when you have more than one item listed in ws, os,
> arch or nl properties.
>
> For example with this content it fails:
>
> <plugin
> id="es.org.chemi.games.sokoban"
> os="linux,win32"
> ws="gtk,motif,win32"
> nl="en"
> arch="x86"
> download-size="0"
> install-size="0"
> version="3.2.1"
> unpack="false"/>
>
> but with this one it works:
>
> <plugin
> id="es.org.chemi.games.sokoban"
> os="linux"
> ws="gtk"
> nl="en"
> arch="x86"
> download-size="0"
> install-size="0"
> version="3.2.1"
> unpack="false"/>
>
> Does it make sense to you? what is the relationship between those
> properties and Java compilation problems?
> I have seen the same behavior with 3.3.2, 3.4.1 and 3.5M3
>
> Thanks in advance,
>
> Chemi.
>
> I am going to try to create a dummy test case from scratch.
Re: Problem exporting as Deployable Feature [message #32119 is a reply to message #32048] Wed, 12 November 2008 07:32 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jmordax.terra.es

Andrew Niefer wrote:
> PDE/Build doesn't support lists in the os/ws/arch entries.
> I'm surprised this worked in 3.2
>
> -Andrew
Hi Andrew. Thanks for your answer.
But let me ask something else, is there any technical reason for this? I
mean, I thought those four properties were just descriptive. For
example, if I have tested my plug-in in Win32 and Motif, I document
there this. Why a Plug-in can't document more than one Window System?
And why this could affect to the compilation?
Finally, why the Feature Editor let me select more than one value if it
is not supported?

Thanks again,

Chemi.
Re: Problem exporting as Deployable Feature [message #32259 is a reply to message #32119] Wed, 12 November 2008 16:38 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
It is really just a feature that never got implemented.

The configs property in the build defines a list of os/ws/arch triplets.
This definitely can not take lists in a given triplet. This is
because the triplets end up being turned into properties set on an OSGi
state that we use to resolve everything and build the classpaths. A
platform specific bundle/fragment that does not match the triplets will
not resolve.

The os/ws/arch settings on the feature entries are used to decide
whether or not the bundle being included matches the set of configs
being built. If it does not match, then it does not get included. This
is more important when you include platforms that you are not building,
so we know we can safely ignore those bundles when they fail to resolve
in the state.

Your problem is likely that the list was never considered to match a
config being built and the bundle was not compiled. I think that
supporting lists would be a matter of improving the algorithm for
matching against the list of configs. Though there may be other things
that I haven't thought of.

-Andrew
Chemi wrote:
> Andrew Niefer wrote:
>> PDE/Build doesn't support lists in the os/ws/arch entries.
>> I'm surprised this worked in 3.2
>>
>> -Andrew
> Hi Andrew. Thanks for your answer.
> But let me ask something else, is there any technical reason for this? I
> mean, I thought those four properties were just descriptive. For
> example, if I have tested my plug-in in Win32 and Motif, I document
> there this. Why a Plug-in can't document more than one Window System?
> And why this could affect to the compilation?
> Finally, why the Feature Editor let me select more than one value if it
> is not supported?
>
> Thanks again,
>
> Chemi.
Re: Problem exporting as Deployable Feature [message #584705 is a reply to message #31911] Tue, 11 November 2008 15:21 Go to previous message
Chris Aniszczyk is currently offline Chris AniszczykFriend
Messages: 674
Registered: July 2009
Senior Member
Chemi wrote:
> Hi, I have a Feature Project that includes 6 Plug-ins Projects.
> The testings work fine. The Plug-ins Projects build perfectly.
> But when I try to export the Feature as a Deployable Feature, there are
> tons of errors building (compiling) the Plug-in Projects. It complains
> about all imports (for example, SWT classes). It is like the Java Build
> Path is lost or something like that when build is fired from the Feature
> export process.
> BTW, if I export all plug-ins as Plug-in or Fragment it works fine.
>
> This worked fine with Eclipse R3.2 and now it is failing with Eclipse
> R3.4.1. Is there any change I am required to do in this new version?

Can you post your feature.xml?

Also, I assume you have nothing manually added to your build path, and
all dependencies are coming from Require-Bundle/Import-Package and your
Bundle-ClassPath is setup properly?

Cheers,

~ Chris
Re: Problem exporting as Deployable Feature [message #584725 is a reply to message #31947] Tue, 11 November 2008 16:06 Go to previous message
Chemi is currently offline ChemiFriend
Messages: 107
Registered: July 2009
Senior Member
Chris Aniszczyk wrote:
> Can you post your feature.xml?
>
> Also, I assume you have nothing manually added to your build path, and
> all dependencies are coming from Require-Bundle/Import-Package and
> your Bundle-ClassPath is setup properly?
>
> Cheers,
>
> ~ Chris

Hi Chris.
But I have continued with my investigation during the day and I have
found "the problem" which doesn't make any sense to me.
The problem appears when you have more than one item listed in ws, os,
arch or nl properties.

For example with this content it fails:

<plugin
id="es.org.chemi.games.sokoban"
os="linux,win32"
ws="gtk,motif,win32"
nl="en"
arch="x86"
download-size="0"
install-size="0"
version="3.2.1"
unpack="false"/>

but with this one it works:

<plugin
id="es.org.chemi.games.sokoban"
os="linux"
ws="gtk"
nl="en"
arch="x86"
download-size="0"
install-size="0"
version="3.2.1"
unpack="false"/>

Does it make sense to you? what is the relationship between those
properties and Java compilation problems?
I have seen the same behavior with 3.3.2, 3.4.1 and 3.5M3

Thanks in advance,

Chemi.

I am going to try to create a dummy test case from scratch.
Re: Problem exporting as Deployable Feature [message #584765 is a reply to message #31978] Tue, 11 November 2008 19:13 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
PDE/Build doesn't support lists in the os/ws/arch entries.
I'm surprised this worked in 3.2

-Andrew

Chemi wrote:
> Chris Aniszczyk wrote:
>> Can you post your feature.xml?
>>
>> Also, I assume you have nothing manually added to your build path, and
>> all dependencies are coming from Require-Bundle/Import-Package and
>> your Bundle-ClassPath is setup properly?
>>
>> Cheers,
>>
>> ~ Chris
>
> Hi Chris.
> But I have continued with my investigation during the day and I have
> found "the problem" which doesn't make any sense to me.
> The problem appears when you have more than one item listed in ws, os,
> arch or nl properties.
>
> For example with this content it fails:
>
> <plugin
> id="es.org.chemi.games.sokoban"
> os="linux,win32"
> ws="gtk,motif,win32"
> nl="en"
> arch="x86"
> download-size="0"
> install-size="0"
> version="3.2.1"
> unpack="false"/>
>
> but with this one it works:
>
> <plugin
> id="es.org.chemi.games.sokoban"
> os="linux"
> ws="gtk"
> nl="en"
> arch="x86"
> download-size="0"
> install-size="0"
> version="3.2.1"
> unpack="false"/>
>
> Does it make sense to you? what is the relationship between those
> properties and Java compilation problems?
> I have seen the same behavior with 3.3.2, 3.4.1 and 3.5M3
>
> Thanks in advance,
>
> Chemi.
>
> I am going to try to create a dummy test case from scratch.
Re: Problem exporting as Deployable Feature [message #584794 is a reply to message #32048] Wed, 12 November 2008 07:32 Go to previous message
Chemi is currently offline ChemiFriend
Messages: 107
Registered: July 2009
Senior Member
Andrew Niefer wrote:
> PDE/Build doesn't support lists in the os/ws/arch entries.
> I'm surprised this worked in 3.2
>
> -Andrew
Hi Andrew. Thanks for your answer.
But let me ask something else, is there any technical reason for this? I
mean, I thought those four properties were just descriptive. For
example, if I have tested my plug-in in Win32 and Motif, I document
there this. Why a Plug-in can't document more than one Window System?
And why this could affect to the compilation?
Finally, why the Feature Editor let me select more than one value if it
is not supported?

Thanks again,

Chemi.
Re: Problem exporting as Deployable Feature [message #584845 is a reply to message #32119] Wed, 12 November 2008 16:38 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
It is really just a feature that never got implemented.

The configs property in the build defines a list of os/ws/arch triplets.
This definitely can not take lists in a given triplet. This is
because the triplets end up being turned into properties set on an OSGi
state that we use to resolve everything and build the classpaths. A
platform specific bundle/fragment that does not match the triplets will
not resolve.

The os/ws/arch settings on the feature entries are used to decide
whether or not the bundle being included matches the set of configs
being built. If it does not match, then it does not get included. This
is more important when you include platforms that you are not building,
so we know we can safely ignore those bundles when they fail to resolve
in the state.

Your problem is likely that the list was never considered to match a
config being built and the bundle was not compiled. I think that
supporting lists would be a matter of improving the algorithm for
matching against the list of configs. Though there may be other things
that I haven't thought of.

-Andrew
Chemi wrote:
> Andrew Niefer wrote:
>> PDE/Build doesn't support lists in the os/ws/arch entries.
>> I'm surprised this worked in 3.2
>>
>> -Andrew
> Hi Andrew. Thanks for your answer.
> But let me ask something else, is there any technical reason for this? I
> mean, I thought those four properties were just descriptive. For
> example, if I have tested my plug-in in Win32 and Motif, I document
> there this. Why a Plug-in can't document more than one Window System?
> And why this could affect to the compilation?
> Finally, why the Feature Editor let me select more than one value if it
> is not supported?
>
> Thanks again,
>
> Chemi.
Previous Topic:Problem using © character
Next Topic:Run/Debug Perspective Preference setting for plugin
Goto Forum:
  


Current Time: Tue Aug 03 05:41:06 GMT 2021

Powered by FUDForum. Page generated in 0.02481 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top