|How to define bundle dependency at project level? [message #650138]
||Fri, 21 January 2011 21:47
| Akara Sucharitakul
Registered: January 2011
Working on two (or more) bundle projects - one dependent on the other, I could not find ways to make the dependencies work within the workspace. Let me go into more detail:|
If I work on bundle project A and bundle project B at the same time. I did not yet build project B and put the bundle into the repository, the manifest and parts of A dependent on B will show an error (squiggly underline) saying the type/package/bundle referenced not found or package could not be resolved.
I can work around the type issue by configuring the build path to include project dependencies. But this won't be accurate as the types I see may not be exported/imported by the manifest causing runtime issues. The other workaround is to make sure I bundle project B and place it into the repository. But then, latest API changes for B won't be read by A until I re-publish bundle B. This would be a major inconvenience for large projects.
The question is do we already have a classpath container (or other dependency resolvers) that deals with bundle dependencies at the project level?
I'm using Virgo 2.1 & STS 3.5.1. Thanks.
Powered by FUDForum
. Page generated in 0.01672 seconds