Eclipse Community Forums: ServerTools (WTP) » Re: Java EE Module dependencies not showing dependent JARs

Help

Home

Home » Language IDEs » ServerTools (WTP) » Re: Java EE Module dependencies not showing dependent JARs

Show: Today's Messages :: Show Polls :: Message Navigator

Re: Java EE Module dependencies not showing dependent JARs [message #481912]

Mon, 24 August 2009 17:29

Eric Rizzo

Messages: 3070
Registered: July 2009

Senior Member

Copying this to the eclipse.webtools group.

Valdis wrote:
> Hi everybody,
>
> I've a slight problem with my Java EE properties in a project.
>
> I'm using one Utility project that houses all the code and 3rd party
> jars that the project needs and one Dynamic Web project that is
> referencing the Utility project and is deployed in Tomcat 5.5 (in the
> Servers view).
>
> The problem is that in the Utility project the Java EE Module
> Dependencies view is empty - no errors, just an empty table. From what
> I've read in various sites churned out by Google is that this view
> should be populated with a list of the jars referenced in the build path
> if an EAR or Dynamic Web project is referencing this project. For some
> reason it's not happening and when I start up Tomcat it fails miserably
> because it can't see the referenced JARs in the Utility project.
> Obviously I'm missing something, but I can't figure out what exactly.
>
> Eclipse version is: 3.5 (Build id: 20090621-0832)
>
> project file for the Utility project:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <projectDescription>
> <name>XXXXX</name>
> <comment></comment>
> <projects>
> </projects>
> <buildSpec>
> <buildCommand>
> <name>org.eclipse.wst.common.project.facet.core.builder</name >
> <arguments>
> </arguments>
> </buildCommand>
> <buildCommand>
> <name>org.eclipse.jdt.core.javabuilder</name>
> <arguments>
> </arguments>
> </buildCommand>
> <buildCommand>
> <name>org.eclipse.wst.validation.validationbuilder</name>
> <arguments>
> </arguments>
> </buildCommand>
> </buildSpec>
> <natures>
> <nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
> <nature>org.eclipse.jdt.core.javanature</nature>
> <nature>org.eclipse.team.cvs.core.cvsnature</nature>
> <nature>org.eclipse.jem.beaninfo.BeanInfoNature</nature>
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature >
>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature >
> <nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
> </natures>
> </projectDescription>
>
> project contents for the Dynamic Web project:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <projectDescription>
> <name>XXXXX-POC</name>
> <comment></comment>
> <projects>
> <project>XXXXX_3036_2</project>
> </projects>
> <buildSpec>
> </buildSpec>
> <natures>
> <nature>org.eclipse.wst.common.project.facet.core.nature</nature >
> <nature>org.eclipse.jdt.core.javanature</nature>
>
> <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature >
> <nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
> </natures>
> </projectDescription>
>
> Please let me know of any other settings, details you need to know in
> order to help me get this thing sorted out.
>
>
> Regards,
> Valdis

Report message to a moderator

Re: Java EE Module dependencies not showing dependent JARs [message #517815 is a reply to message #481912]

Tue, 02 March 2010 09:17

Messages: 1
Registered: March 2010

Junior Member

Has anyone found solution to this specific issue?
I've had some issues with Java EE Module dependencies as well. It seems that what ever I do the list is empty or says that "Selected module is not referenced by any EAR or Dynamic Web modules". How ever the module is referenced by Dynamic Web module. Am I missing something? has my workspace been corrupted (would not be the first time)? Am I just asking stupid questions?

Regards,
JP

Report message to a moderator

Re: Java EE Module dependencies not showing dependent JARs [message #524518 is a reply to message #481912]

Thu, 01 April 2010 08:51

Niklas

Messages: 1
Registered: April 2010

Junior Member

Hi.

I have a problem related to this. When using maven-eclipse-plugin 2.8 to generate wtp-2.0 config for a multi-module-workspace (webapp depending on projects in the same workspace) I get the project references I want (classpath is updated with a project reference) but Java EE module dependencies for my webapp are not updated and when I start Tomcat 6 some classes cannot be found. Now I wonder if there is any file in eclipse (WTP?) which should have been updated. I can do the update manually and it works fine but I cannot find out how my update changes settings in the eclipse project/workspace. If I know where this setting belongs, I can start searching for a solution in maven-eclipse-plugin but before that, I do not know where to start. Any help would be appreciated.

Regards, Niklas

Report message to a moderator

Re: Java EE Module dependencies not showing dependent JARs [message #641663 is a reply to message #524518]

Fri, 26 November 2010 15:08

Rustam Abdullaev

Messages: 10
Registered: July 2009

Junior Member

For dependent module to be recognized in WTP, you have to enable WTP not only in the WAR module but also in all dependent JAR modules, like this:

	      <plugin>
	        <artifactId>maven-eclipse-plugin</artifactId>
	        <configuration>
	          <wtpversion>1.5</wtpversion>
	        </configuration>
	      </plugin>

Report message to a moderator

Previous Topic:	Somebody Please Come In ASAP And Point Me In The Right Direction
Next Topic:	Eclipse Hangs/Pauses When I Start to Type <elem... in JSPX/XML Editor, Especially with Custom Tag

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 00:00:51 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter