 Java EE referenced classpaths broken in Helios? [message #543106] |
Mon, 28 June 2010 08:25  |
 Jason Levine
Messages: 12
Registered: July 2009 |
Junior Member |
|
|
In Helios, I've been struggling to understand how the old Java EE Module Dependencies functionality has been replaced by the Deployment Assembly property pane; I'm now experiencing what's either a misunderstanding about how referenced classpaths work within Deployment Assembly, or a legitimate bug. In essence, when you set which referenced classpaths should be included in an individual project's deployment, that setting applies to all projects in your workspace, not just the one you applied them to -- and thus, all projects with different settings then break.
I filed a bug report about it here over the weekend, including the full way to reproduce what I'm seeing (so that someone else can help me understand if this is just me misunderstanding the functionality vs. a real bug). Here's what I said there:
| Quote: | If I add "Referenced Projects Classpath Entries" to a Dynamic Web Project and then make selections of which entries to pull into the project, those changes are mirrored across *all* Dynamic Web Projects in my workspace, breaking the deployment of any but the project that has been most-recently set up.
|
I'd love if anyone else could take a look and see; for now, this is a big-enough headache that there's really no way I can use Helios for development, since it breaks every single one of my Dynamic Web Projects.
[Updated on: Mon, 28 June 2010 08:28] Report message to a moderator |
|
|
] 
Search
Help
Register
Login
Home
