Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351601 - Tooling should include Bundle-ClassPath during new project setup
Summary: Tooling should include Bundle-ClassPath during new project setup
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 368782
  Show dependency tree
 
Reported: 2011-07-08 14:08 EDT by rshelley CLA
Modified: 2012-01-16 18:41 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rshelley CLA 2011-07-08 14:08:56 EDT 
Build Identifier: 201107041000

Due to the backwards incompatible change in M06 for WABs, Web Bundles created through the tooling should offer the project creator to enter a Bundle-ClassPath during setup.  If the Bundle-ClassPath is not explicitly set for WABs, it's likely the bundle will fail to start.

Release notes documenting backward incompatible changes:
http://www.eclipse.org/virgo/download/release-notes/3.0.0.M06.php

Reproducible: Always

Steps to Reproduce:
1. File > New > Other > EclipseRT > Bundle Project
2. Enter project name, click Next
3. Check "Web Application Bundle", click Next

Should add "Bundle-ClassPath" as optional header here (maybe with default to WEB-INF/classes,WEB-INF/lib?)