Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » ServerTools (WTP) » Exporting another project when publishing to a server
Exporting another project when publishing to a server [message #203806] Tue, 06 November 2007 20:24 Go to next message
Eclipse UserFriend
Originally posted by: christoph.hodte.de

Hello,

I have a question. Ich have two projects one is a WTP project and the
other is a simple java project. The WTP project depends on the simple java
project. I add the depend project to the buildpath and eclipse find the
classes.

The problem is when I publish the WTP project to a tomcat server the
depended project is not publish to the server or isn't copied to the
classes directory.

Is that a bug? When not how must I configure the projects that both are
published.

I have a Workaround. I export the simple java project to a jar and copy
the jar in the lib dir. But that is not a good solution.

Chris
Re: Exporting another project when publishing to a server [message #203814 is a reply to message #203806] Tue, 06 November 2007 20:49 Go to previous messageGo to next message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1354
Registered: July 2009
Senior Member
Instead of adding the Java project using the Java Build Path page of
project Properties, use the J2EE Module Dependencies page. Checking the
Java project there internally adds it to the build path and WTP will
automatically do during publishing what you are doing manually, i.e.
build a jar from the Java project's Java output and publish it to
WEB-INF/lib.

Cheers,
Larry

Christoph wrote:
> Hello,
>
> I have a question. Ich have two projects one is a WTP project and the
> other is a simple java project. The WTP project depends on the simple
> java project. I add the depend project to the buildpath and eclipse find
> the classes.
>
> The problem is when I publish the WTP project to a tomcat server the
> depended project is not publish to the server or isn't copied to the
> classes directory.
>
> Is that a bug? When not how must I configure the projects that both are
> published.
>
> I have a Workaround. I export the simple java project to a jar and copy
> the jar in the lib dir. But that is not a good solution.
>
> Chris
>
Re: Exporting another project when publishing to a server [message #203860 is a reply to message #203814] Wed, 07 November 2007 07:44 Go to previous messageGo to next message
Christoph is currently offline ChristophFriend
Messages: 1
Registered: July 2009
Junior Member
Thx for the answer. But when I use the J2EE Dependency I must use a J2EE
Application Server but I only need the Tomcat instead Geronimo.

Can I do the same with Tomcat without manuel exporting the project to a
jar?

Christoph
Re: Exporting another project when publishing to a server [message #203884 is a reply to message #203860] Wed, 07 November 2007 11:03 Go to previous message
Eclipse UserFriend
Originally posted by: mauro.molinari.cardinis.com

Christoph ha scritto:
> Thx for the answer. But when I use the J2EE Dependency I must use a J2EE
> Application Server but I only need the Tomcat instead Geronimo.
>
> Can I do the same with Tomcat without manuel exporting the project to a
> jar?
>
> Christoph

AFAIK, you don't need to use a J2EE Application Server to use the J2EE
Module Dependecies page to add inter-project dependencies.

Cheers,
Mauro.
Previous Topic:hierarchical view not showing in Project Explorer
Next Topic:problem in adding Derby plug-ins to Eclipse
Goto Forum:
  


Current Time: Thu Mar 28 11:46:43 GMT 2024

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

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

Back to the top