Eclipse Community Forums: Plugin Development Environment (PDE) » Headless build problem with re-exported packages.

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » Headless build problem with re-exported packages.

Show: Today's Messages :: Show Polls :: Message Navigator

Headless build problem with re-exported packages. [message #64350]

Mon, 08 June 2009 21:15

Jean-Marie Damas

Messages: 29
Registered: July 2009

Junior Member

Hello all.

I've got the following problem when trying to headless build my feature:
the compiler fails with this message:

> # Eclipse Java Compiler 0.894_R34x, 3.4.2 release, Copyright IBM Corp 2000, 2008. All rights reserved.
> ----------
> 1. ERROR in C:\Users\FORGES_dev\FORGES\temp\ForgesClientAutomaticBuild\p lugins\com.airbus.forges.client.team\src\com\airbus\forges\c lient\ForgesTeamPlugin.java (at line 16)
> import com.airbus.forges.ws.model.Profile;
> ^^^^^^^^^^^^^^^^^^^^
> The import com.airbus.forges.ws cannot be resolved

My plugin breakdown is as follow :
- the "com.airbus.forges.client.team" plugin requires the
"com.airbus.forges.server.api" plugin and re-exports this dependency,
- the "com.airbus.forges.server.api" plugin exports this 3 packages :
com.airbus.forges.ws.api
com.airbus.forges.ws.model
com.airbus.forges.ws.util

My context is Eclipse 3.4.2 and the PDE build within Eclipse is successfull.

Can you help me in achieving this headless build ?
Thank you.
JM.D

Report message to a moderator

Re: Headless build problem with re-exported packages. [message #64396 is a reply to message #64350]

Tue, 09 June 2009 16:03

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

You can check the classpath being used for the compile by looking in the
generated com.airbus.forges.client.team/build.xml script.

One possibility is that the classpath is correct but
com.airbus.forges.server.api has not been compiled yet.

In 3.4, plugins are compiled according to the feature structure. The
features are visited depth first. The plug-ins within a given feature
are sorted according to dependencies, but this sorting does not cross
the feature boundaries.

This probably works from in the IDE because the classpath generally gets
the com.airbus.forges.server.api/bin folder as well.

You can either re-arrange your feature structure, or upgrade your
builder to 3.5 and define the property "flattenDependencies=true".
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=212467. (You may also
be interested in https://bugs.eclipse.org/bugs/show_bug.cgi?id=238177)

Note it is possible to use a 3.5 builder and still target 3.4.2 for your
release. Just use a baseLocation that is separate from the eclipse
running the build. The Eclipse SDK is currently in final release
candidates for 3.5. RC4 is here:
http://download.eclipse.org/eclipse/downloads/drops/S-3.5RC4 -200906051444/index.php

-Andrew

JM.D wrote:
> Hello all.
>
> I've got the following problem when trying to headless build my feature:
> the compiler fails with this message:
>
>> # Eclipse Java Compiler 0.894_R34x, 3.4.2 release, Copyright IBM Corp
>> 2000, 2008. All rights reserved.
>> ----------
>> 1. ERROR in
>> C:\Users\FORGES_dev\FORGES\temp\ForgesClientAutomaticBuild\p lugins\com.airbus.forges.client.team\src\com\airbus\forges\c lient\ForgesTeamPlugin.java
>> (at line 16)
>> import com.airbus.forges.ws.model.Profile;
>> ^^^^^^^^^^^^^^^^^^^^
>> The import com.airbus.forges.ws cannot be resolved
>
> My plugin breakdown is as follow :
> - the "com.airbus.forges.client.team" plugin requires the
> "com.airbus.forges.server.api" plugin and re-exports this dependency,
> - the "com.airbus.forges.server.api" plugin exports this 3 packages :
> com.airbus.forges.ws.api
> com.airbus.forges.ws.model
> com.airbus.forges.ws.util
>
> My context is Eclipse 3.4.2 and the PDE build within Eclipse is
> successfull.
>
> Can you help me in achieving this headless build ?
> Thank you.
> JM.D

Report message to a moderator

Re: Headless build problem with re-exported packages. [message #64768 is a reply to message #64396]

Fri, 12 June 2009 09:19

Jean-Marie Damas

Messages: 29
Registered: July 2009

Junior Member

Thank you for your help.

After re-arranging the order of my plug-ins in the feature definition, my
headless build worked fine. I can remain with my 3.42 Eclipse release.
My IDE PDE build still works also, that's great !

JM.D

Report message to a moderator

Re: Headless build problem with re-exported packages. [message #598178 is a reply to message #64350]

Tue, 09 June 2009 16:03

Andrew Niefer

Messages: 990
Registered: July 2009

Senior Member

You can check the classpath being used for the compile by looking in the
generated com.airbus.forges.client.team/build.xml script.

One possibility is that the classpath is correct but
com.airbus.forges.server.api has not been compiled yet.

In 3.4, plugins are compiled according to the feature structure. The
features are visited depth first. The plug-ins within a given feature
are sorted according to dependencies, but this sorting does not cross
the feature boundaries.

This probably works from in the IDE because the classpath generally gets
the com.airbus.forges.server.api/bin folder as well.

You can either re-arrange your feature structure, or upgrade your
builder to 3.5 and define the property "flattenDependencies=true".
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=212467 (You may also
be interested in https://bugs.eclipse.org/bugs/show_bug.cgi?id=238177)

Note it is possible to use a 3.5 builder and still target 3.4.2 for your
release. Just use a baseLocation that is separate from the eclipse
running the build. The Eclipse SDK is currently in final release
candidates for 3.5. RC4 is here:
http://download.eclipse.org/eclipse/downloads/drops/S-3.5RC4 -200906051444/index.php

-Andrew

JM.D wrote:
> Hello all.
>
> I've got the following problem when trying to headless build my feature:
> the compiler fails with this message:
>
>> # Eclipse Java Compiler 0.894_R34x, 3.4.2 release, Copyright IBM Corp
>> 2000, 2008. All rights reserved.
>> ----------
>> 1. ERROR in
>> C:\Users\FORGES_dev\FORGES\temp\ForgesClientAutomaticBuild\p lugins\com.airbus.forges.client.team\src\com\airbus\forges\c lient\ForgesTeamPlugin.java
>> (at line 16)
>> import com.airbus.forges.ws.model.Profile;
>> ^^^^^^^^^^^^^^^^^^^^
>> The import com.airbus.forges.ws cannot be resolved
>
> My plugin breakdown is as follow :
> - the "com.airbus.forges.client.team" plugin requires the
> "com.airbus.forges.server.api" plugin and re-exports this dependency,
> - the "com.airbus.forges.server.api" plugin exports this 3 packages :
> com.airbus.forges.ws.api
> com.airbus.forges.ws.model
> com.airbus.forges.ws.util
>
> My context is Eclipse 3.4.2 and the PDE build within Eclipse is
> successfull.
>
> Can you help me in achieving this headless build ?
> Thank you.
> JM.D

Report message to a moderator

Re: Headless build problem with re-exported packages. [message #598290 is a reply to message #64396]

Fri, 12 June 2009 09:19

Jean-Marie Damas

Messages: 29
Registered: July 2009

Junior Member

Report message to a moderator

Previous Topic:	Update Manager issue
Next Topic:	p2-enabled PDE build: features vs. plugins

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 09:34:35 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter