[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] Problems with headless builds

Without seeing your build.properties is hard to know for sure. Do you have a "top level feature"? If so, does it contain the other feature?  PDE/Build wants to fetch all the features / plug-ins, so from a top level it must be able to reach down to all the requirements.

i.e. if Feature A, contains b, c, and d. But you have a dependency to E, the E must be reachable somewhere (some feature in your structure must include it).

That obviously doesn't explain why things suddenly stopped working though.

cheers,
ian

On Tue, Jan 26, 2010 at 2:04 PM, Kristina Taylor <Kristina.Taylor@xxxxxxx> wrote:

I don't know if this is the right place to ask, so if it's not, please point me to the right place.

 

I'm trying to build a couple of features using the PDE headless build magic, and I feel like I'm beating my head against a wall. I once had this working, but then got pulled into something else, and I came back to it, only to find it horribly broken.  I can't find anything that looks relevant that has changed.  I basically have a parent feature that contains my two other features, which each contain a bunch of plugins/fragments.

 

Here's what I'm running:

 

java -jar C:/software/eclipse-jee-ganymede-win32/plugins/org.eclipse.equinox.launcher_ 1.0.100.v20080509-1800.jar \

                                                                                -application org.eclipse.ant.core.antRunner \

                                                                                -buildfile C:/software/eclipse-jee-ganymede-win32/plugins/org.eclipse.pde.build_3.4.0.v20080604/scripts/build.xml \

                                                                                -Dbase=C:/software \

                                                                                -DbaseLocation=C:/software/eclipse-jee-ganymede-win32 \

                                                                                -DbuildDirectory=${ECLIPSE_DEST_DIR}/temp \

                                                                                -DtopLevelElementType=feature \

                                                                                -DtopLevelElementId=com.mks.integrations.eclipse.super \

                                                                                -Dbuilder=${SOLUTION_INTEGRATIONS_SRC}/products/eclipse/resources/builder \

                                                                                -DjavacSource=1.5 \

                                                                                -DjavacTarget=1.5 \

                                                                                -DjavacDebugInfo=true \

                                                                                -verbose

 

The ${ECLIPSE_DEST_DIR}/temp contains a features and plugins directory with all of my source for each of my features and plugins.  The builder value is pointing to a directory that contains a  build.properties file copied verbatim out of C:/software/eclipse-jee-ganymede-win32/plugins/org.eclipse.pde.build_3.4.0.v20080604/templates/headless-build.  I was led to believe from something I read somewhere that the command line options overrule what's in that file, so figured I'd explicitly set things on the command line, as part of my debugging.

 

I get this:

 

BUILD FAILED

C:\software\eclipse-jee-ganymede-win32\plugins\org.eclipse.pde.build_3.4.0.v20080604\scripts\build.xml:24: The following error occurred while executin

g this line:

C:\software\eclipse-jee-ganymede-win32\plugins\org.eclipse.pde.build_3.4.0.v20080604\scripts\build.xml:64: The following error occurred while executin

g this line:

C:\software\eclipse-jee-ganymede-win32\plugins\org.eclipse.pde.build_3.4.0.v20080604\templates\headless-build\customTargets.xml:12: The following erro

r occurred while executing this line:

C:\software\eclipse-jee-ganymede-win32\plugins\org.eclipse.pde.build_3.4.0.v20080604\templates\headless-build\allElements.xml:16: The following error

occurred while executing this line:

C:\software\eclipse-jee-ganymede-win32\plugins\org.eclipse.pde.build_3.4.0.v20080604\scripts\genericTargets.xml:88: Unable to find feature: com.mks.in

tegrations.eclipse.bundle.

        at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)

        at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)

        at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)

        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)

        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

...

(and a bunch more following, but basically the same gist).

 

com.mksintegrations.eclipse.bundle is one of my two features.  If I switch the command line invocation to build .bundle instead of .super, it complains that it can't find the first plugin in .bundle.  What am I missing?

 

Sorry for the long message.

 

Kristina Taylor
Software Developer

MKS Inc.

410 Albert Street
Waterloo, Ontario
N2L 3V3

 

519-883-3478

www.mks.com

 

When software is critical, build on MKS Integrity™

The information in this e-mail message, including any attachments, is confidential. It is intended only for the named addressee and any use or disclosure by others is strictly prohibited. If you have received this message in error, please accept my apologies, notify me and be so kind as to delete all copies of the message. Thank you.

 


_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev




--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource