RTC representation of "svn:externals"
Joef Huang (46●11●4)
| asked May 06 '11, 5:41 p.m.
edited Oct 13 '17, 3:11 p.m. by David Lafreniere (4.8k●7) Hello,
|
4 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered May 07 '11, 5:10 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I've submitted work item 164956 for this.
There were two existing work items for two possible implementations for this (work item 148034 and work item 44004), both referenced by the new work item. Cheers, Geoff On 5/6/2011 5:53 PM, joefh wrote: Hello, Comments I've submitted work item 164956 for this.
|
Is there a reason you want to do this in source control rather than a dependency manager such as maven or ivy?
|
Geoff,
I have the exact same use case. Update your plugin/build.properties as follows: source.. = src/ output.. = bin/ bin.includes = META-INF/,\ .,\ ProjectA.jar,\ ProjectB.jar,\ other_dependencies_if_you_have_them.jar jars.compile.order = ProjectA.jar,\ ProjectB.jar,\ . source.ProjectA.jar = ../ProjectA/src/ output.ProjectA.jar = bin/ source.ProjectB.jar = ../ProjectB/src/ output.ProjectB.jar = bin/ Do NOT forget the "." line under jars.compile.order ... this is what compiles your original plugin code. This update says "compile project A, then project B, then my local plugin code to build this plugin" Your MANIFEST.MF needs only reference these jars locally: Bundle-ClassPath: ProjectA.jar, ProjectB.jar, ., Make the appropriate updates if you want to put the jar files in a lib/ or other subfolder ... this trick puts the jars in your project root. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.