[
http://jira.jboss.com/jira/browse/JBIDE-1862?page=comments#action_12402634 ]
Rob Stryker commented on JBIDE-1862:
------------------------------------
private boolean canExportClasspathComponentDependencies(IVirtualComponent component) {
final IProject project = component.getProject();
// check for valid project type
if (J2EEProjectUtilities.isEJBProject(project)
|| J2EEProjectUtilities.isDynamicWebProject(project)
|| J2EEProjectUtilities.isJCAProject(project)
|| J2EEProjectUtilities.isUtilityProject(project)) {
return true;
}
return false;
}
In the new JEEFlexProjDeployable, EAR projects are specifically ignored. They cannot
export their component dependencies.
Ear/jar packaging behaving weird on Eclipse 3.2.2
-------------------------------------------------
Key: JBIDE-1862
URL:
http://jira.jboss.com/jira/browse/JBIDE-1862
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, Seam
Affects Versions: 2.0.0.GA
Environment:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135187#...
Reporter: Max Andersen
Assigned To: Rob Stryker
Fix For: 2.1
Something weird is happing with jboss-seam.jar in ear packaging. See the forum for
details.
Apparently fixing application.xml apparently fixes it but why?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira