Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » Java EE referenced classpaths broken in Helios?
icon5.gif  Java EE referenced classpaths broken in Helios? [message #543106] Mon, 28 June 2010 12:25 Go to next message
Jason Levine is currently offline Jason LevineFriend
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 12:28]

Report message to a moderator

Re: Java EE referenced classpaths broken in Helios? [message #543143 is a reply to message #543106] Mon, 28 June 2010 14:22 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1313
Registered: July 2009
Senior Member
On 6/28/2010 8:25 AM, Jason Levine wrote:
> 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
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=318068 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). 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.

I believe this aspect of Deployment Assembly is still a work in
progress. However, it is important to note that the issue is strictly
in the UI and what you end up with is no different than with Galileo.
The problem is that when you are selecting which jars in utility
projects you want included in WEB-INF/lib, you may see the jars for more
projects than your current dynamic web project currently references
(which will occur in step 9 of your bug). You can change the inclusion
or exclusion of those jars in the "extra" projects and it will only
affect dynamic web projects that reference those projects. It won't
affect the current dynamic web project since it doesn't currently
reference any of the "extra" projects. Thus, in step 9 of your bug,
there is no need to uncheck the jar in Test1. The state of that jar
doesn't affect TestWeb2 because it doesn't reference the Test1 project.

Note that the "Pull in classpath elements from referenced project" item
that appears in the table is somewhat misleading because it doesn't
actually pull in anything. It is just a means to controlling the
attribute which marks a jar on the Java Build Path for inclusion in
WEB-INF/lib. HTH.

Cheers,
Larry
Re: Java EE referenced classpaths broken in Helios? [message #543146 is a reply to message #543143] Mon, 28 June 2010 14:54 Go to previous messageGo to next message
Jason Levine is currently offline Jason LevineFriend
Messages: 12
Registered: July 2009
Junior Member
Ah -- interesting. So by my read of that, then, I assume there's no way to have two projects in the same workspace which reference the same project and would pull different referenced parts of that project in?

In other words, if I have two dynamic web projects, Web1 and Web2, both of which reference generic Java project Java1, is there any way for Web1 and Web2 to reference different sets of classpath entries from Java1?
Re: Java EE referenced classpaths broken in Helios? [message #543177 is a reply to message #543146] Mon, 28 June 2010 15:13 Go to previous message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1313
Registered: July 2009
Senior Member
On 6/28/2010 10:54 AM, Jason Levine wrote:
> Ah -- interesting. So by my read of that, then, I assume there's no way
> to have two projects in the same workspace which reference the same
> project and would pull different referenced parts of that project in?
>
> In other words, if I have two dynamic web projects, Web1 and Web2, both
> of which reference generic Java project Java1, is there any way for Web1
> and Web2 to reference different sets of classpath entries from Java1?

As you note, you can't do this with the "Referenced Projects Classpath
Entries" reference type because the attribute it adds goes in the
referenced Java project and affects all referencing web projects the
same. For the use case you cite, you have to go with one of the other
reference types, such as Archive, and have Web1 and Web2 reference the
desired jars directly. You would only use of the "Referenced Projects
Classpath Entries" type to ensure the jars being "managed" are unchecked.

Cheers,
Larry
Previous Topic:Problem with Eclipse BPEL plugin and org.eclipse.jface
Next Topic:Helios JSDT validation bug?
Goto Forum:
  


Current Time: Sat Dec 20 14:34:15 GMT 2014

Powered by FUDForum. Page generated in 0.10665 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software