StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POBundle-Classpath jars not put into dev.properties on PDE launch
primarykey
Id
3874433
data
AcceptedAnswerId
3927037
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-06T15:55:02.980
FavoriteCount
1
LastActivityDate
2010-10-13T18:57:54.490
LastEditDate
LastEditorUserId
0
OwnerUserId
5077
ParentId
0
PostTypeId
1
Score
0
ViewCount
778
LastEditorDisplayName
text
Body
I have an eclipse plugin project that requires a lot of external jar file dependencies. The plugin places these on the Bundle-Classpath and includes them in the plugin when built through build.properties. If you export the plugin and run it through eclipse, everything works fine. When running through the launch configuration (ie: debugging), none of the extra jars are added to the classpath. Only class files from the source of the plugin are put on the classpath. To show this easier, I put together a small dummy application. Contents of Manifest.MF: <pre><code>Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: Test-pde-project Bundle-SymbolicName: test-pde-project Bundle-Version: 1.0.0.qualifier Require-Bundle: org.eclipse.ui, org.eclipse.core.runtime Bundle-ClassPath: plugin-out.jar, lib/dummy.jar </code></pre> Contents of build.properties: <pre><code>source.plugin-out.jar = src/ output.. = bin/ bin.includes = META-INF/,\ plugin-out.jar,\ lib/dummy.jar </code></pre> As you can see, plugin-out.jar contains the class files from my compiled plugin. The dummy.jar is a sample jar file that should be included with this plugin when running it. I would expect to see both of these in dev.properties when the PDE launches eclipse with this plugin. What actually happens though is this dev.properties is the one that is generated: <pre><code># #Wed Oct 06 10:11:09 ADT 2010 test-pde-project=bin @ignoredot@=true </code></pre> Why is lib/dummy.jar not getting added to dev.properties? I did some reading around and my understanding is that it should be there? Can anyone tell me how I can get dummy.jar to be added to the runtime when running through the launch configuration?
Tags
<java><eclipse><eclipse-pde>
Title
Bundle-Classpath jars not put into dev.properties on PDE launch
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USChris Dail
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POBundle-Classpath jars not put into dev.properties on PDE launch
 UserUserId
 USChris Dail
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.