Bug 373861 - Bundle-Classpath directive ignores entries starting with dot
Summary: Bundle-Classpath directive ignores entries starting with dot
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2012-03-10 05:24 EST by Vladimir CLA
Modified: 2021-04-28 16:55 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir CLA 2012-03-10 05:24:16 EST
Build Identifier: 0.14.0

I was trying to test my bundle with embedded 3rd-party jars and tests were failed with NoClassDefFoundError in bundle activator start() method. The same bundle was working quite well in deployed application.

My research narrowed to the problem to the fact, that Tycho cannot understand directive

Bundle-Classpath: ., ./lib/my-lib.jar

as I used to write. It works only with the directive

Bundle-Classpath: ., lib/my-lib.jar

This is a minor issue and a workaround exists, but I wpent a lot of time to debug this.

Reproducible: Always

Steps to Reproduce:
1. Put some jar fine into the Tycho-managed project
2. Add this file or parent folder into bin.includes of the build.properties file
3. Add the jar file to Bundle-Classpath, but use prefix "./"

It should work in the same way as without prefix, but it fails.
Comment 1 Jan Sievers CLA 2012-03-12 04:26:46 EDT
this is because we extract entries from the bundle jar using the path as is.
If non-normalized pahts are supported at rutime, I guess we need to normalize the path before extracting it from the bundle jar.
Comment 2 Mickael Istria CLA 2021-04-08 18:10:44 EDT
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse/tycho/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.