Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 351601

Summary:	Tooling should include Bundle-ClassPath during new project setup
Product:	[RT] Virgo	Reporter:	rshelley <ryan.shelley>
Component:	tooling	Assignee:	Project Inbox <virgo-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse, mlippert
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:
Bug Blocks:	368782

Description rshelley

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?)