[
https://jira.jboss.org/jira/browse/JBIDE-5713?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5713:
------------------------------------
What's shown in the image doesn't match *at all* what's being shown in the
xml file. If it was just hte ejb reference that was missing I'd be torn.
Right now, all I can say by looking at this screenshot is that the user may have added
references to the wizard and not clicked "apply" yet to save them, which means
the page was out of sync with the xml file.
Without a project to test it with, I have no idea what's going on here. It does not
seem to make sense at all and aside from free-testing, theres virtually nothing I can do.
Incoherent module assembly structure
------------------------------------
Key: JBIDE-5713
URL:
https://jira.jboss.org/jira/browse/JBIDE-5713
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR1
Environment: Vista, JBT 3.1.CR1
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: incoherent_module_assembly_structure.jpg
I was a bit puzzled -and kinda worried- after opening the module assembly page of an EJB
project.
As you can see on the following screenshot (incoherent_module_assembly_structure.jpg),
the page indicates EJB dependencies of my testEJB2 project should be exported in the
resulting jar. Fortunately, they aren't (hence the minor priority), but it's
pretty disturbing.
My understanding of the module assembly page is that :
- it's just a GUI over ./settings/org.eclipse.wst.common.component
- it should reflect the content of the produced assembly. i.e everything in this page
should be present in the resulting .jar/.ear/.sar, whatever.
well, it's also probable I misunderstood a lot :-)
regards,
Fred Bricon
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira