| Re: [buckminster-dev] Plugin dependencies and cspex file [message #22290] |
Mon, 21 July 2008 15:04 |
|
Hi Joseph,
Joseph Campolongo wrote:
> > Exactly what do you mean with "dependency isn't built"?
>
> What I mean is that, when I go to ‘Invoke Action-->bundle.jars’ to
> build the project bundle, only the one bundle is built, not all of its
> dependent bundles. If my dependency is explicit in the manifest.mf,
> then all of those bundles are also built (and placed in my
> <home>/temp/buckminster folder).
>
> So, I’m seeing two different behaviors. If I put a dependency in the
> manifest.mf file and call ‘Invoke Action-->bundle.jars’, my main
> project and its dependency is built and placed in my
> <home>/temp/bunkminster folder. If I put a dependency in the
> buckminster.cspex file (and have it show up under ‘View CSpec’ as a
> dependency, just like if it were part of the manifest.mf), only the
> main project is built, not the dependency (even though in both cases
> the ‘View CSpec’ file looks exactly the same, although I might have
> missed something there).
>
This sounds very odd. You are able to resolve the bundle into your
workspace but it doesn't build? It's surprising because the build system
doesn't care much how the CSPEC comes into existence. Have you tried
running with the Buckminster preference "Console Logger" set to DEBUG?
It will give you some more information about what's built and why.
Regards,
Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.02846 seconds
] 
Search
Help
Register
Login
Home
