[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [buckminster-dev] Plugin dependencies and cspex file
|
Hi Joseph,
I think that what you see is all due to actions and their prerequisites.
You build some action that has prerequisites on other actions in other
bundles. If you examine those prerequisites more carefully, you will see
that the bundle where you add the cspex automatically adds them when you
add the dependency to the manifest.mf.
If you just add the dependency manually without adding any prerequisites
to an action that you execute, well, then it's required that the
component exists (i.e. resolution will work) but there's no reason for
it to be built. The actions that you execute have no action prerequisite
chain that ever reaches the bundle in question.
You can add this of course, by altering some of the groups or actions
that exists in the generated cspec.
I think the best way to really understand what's going on is to take a
look at the generated XML of a bundle cspec and pay specific attention
to the prerequisites and groups.
Regards,
Thomas Hallgren
Joseph Campolongo wrote:
Just to re-iterate, the ‘View CSpec’ action give me a cspec file that
has the following block in it:
<cs:dependencies>
<cs:dependency name="OSGi_Dependency"
componentType="osgi.bundle" versionDesignator="1.0.0" versionType="OSGi"/>
</cs:dependencies>
Then, running the project with debug turned on, I don’t see anything
having to do with dependencies at all. It is all very strange. Note
also that if I keep the buckminster.cspex file and add the dependency to
the manifest.mf, I still don’t get the dependency being built. Only if
I have the dependency in the manifest file and the buckminster.cspex
file doesn’t exist does it get built.
I’m guessing that I’m doing something wrong somewhere, but it is opaque
enough to stymie me.
Actions to perform (in order)
com.cra.project:osgi.bundle$1.0.1#OSGi#target.fragments
com.cra.project:osgi.bundle$1.0.1#OSGi#eclipse.build
com.cra.project:osgi.bundle$1.0.1#OSGi#bundle.jar
[start com.cra.project:osgi.bundle$1.0.1#OSGi#eclipse.build]
target.arch=x86
PROJECT_Runtime=c:\Project_metronome
buckminster.component=com.cra.project
workspace.root=C:/Documents and Settings/jcampolongo/workspace
buckminster.temp=C:/DOCUME~1/JCAMPO~1/LOCALS~1/Temp/buckminster/com.cra.project_1.0.1-osgi.bundle/temp
buckminster.home=C:\dev\Project\trunk\Metronome-Project\
buckminster.output=C:/DOCUME~1/JCAMPO~1/LOCALS~1/Temp/buckminster/com.cra.project_1.0.1-osgi.bundle/build
localhost=jcampolongo-dt1
buckminster.component.type=osgi.bundle
buckminster.version.type=OSGi
buckminster.version=1.0.1
target.nl=en_US
target.ws=win32
eclipse.home=C:\eclipse
target.os=win32
target.location=C:\dev\Project\trunk\target_platform
[end com.cra.project:osgi.bundle$1.0.1#OSGi#eclipse.build]
Action com.cra.project:osgi.bundle$1.0.1#OSGi#bundle.jar using 'up to
date' policy COUNT: Rebuild needed: File count(0) < expected(1)
[start com.cra.project:osgi.bundle$1.0.1#OSGi#bundle.jar]
Product alias = action.output
Product base = ${buckminster.output}\jar\
target.arch=x86
PROJECT_Runtime=c:\Project_metronome
buckminster.component=com.cra.project
workspace.root=C:/Documents and Settings/jcampolongo/workspace
buckminster.temp=C:/DOCUME~1/JCAMPO~1/LOCALS~1/Temp/buckminster/com.cra.project_1.0.1-osgi.bundle/temp
buckminster.home=C:\dev\Project\trunk\Metronome-Project\
buckminster.output=C:/DOCUME~1/JCAMPO~1/LOCALS~1/Temp/buckminster/com.cra.project_1.0.1-osgi.bundle/build
localhost=jcampolongo-dt1
buckminster.component.type=osgi.bundle
buckminster.version.type=OSGi
buckminster.version=1.0.1
target.nl=en_US
target.ws=win32
eclipse.home=C:\eclipse
target.os=win32
target.location=C:\dev\Project\trunk\target_platform
[end com.cra.project:osgi.bundle$1.0.1#OSGi#bundle.jar]
Joseph Campolongo
Charles River Analytics, Inc.
THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS
ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the
intended recipient, your use of this message for any purpose is strictly
prohibited. If you have received this communication in error, please
delete the message and notify the sender so that we may correct our
records.