| Problem with deployment of dependent projects [message #139370] |
Sun, 18 September 2005 19:27  |
Eclipse User |
|
|
|
Originally posted by: l.dokov.enless-soft.coom
I saw the previous posts on this issue but I still have a problem. When I
deploy my Dynamic Web project, it copies only its own source folders but not
the dependent projects. In the Properties window of the Web Project I have
selected dependent project and jars in the Java Build Path section. In the
"Java JAR Dependencies" section the checkbox is disabled and the list is
empty. Any ideas? I tried with a previous build of WTP - M20050819 because I
read that it is working in some previous post. The same results as with the
newest. I still am not sure is this a bug or am I doing something wrong.
Possibly a bug. I was previously using MyEclipse(a commercial plug-in) and
it has the option to deploy dependent projects and/or jars. Unfortunately
it's JSP editor is very slow.
Server: Apache Tomcat 5.0.28
JDK: 1.5.0_02
|
|
|
| Re: Problem with deployment of dependent projects [message #139554 is a reply to message #139370] |
Mon, 19 September 2005 23:54  |
| Eclipse User |
|
|
|
Originally posted by: laurentd75___no.sp_am.yahoo.fr
"Liubomir Dokov" wrote:
> I saw the previous posts on this issue but I still have a problem. When I
> deploy my Dynamic Web project, it copies only its own source folders but
not
> the dependent projects. In the Properties window of the Web Project I have
> selected dependent project and jars in the Java Build Path section. In the
> "Java JAR Dependencies" section the checkbox is disabled and the list is
> empty. Any ideas? I tried with a previous build of WTP - M20050819 because
I
> read that it is working in some previous post. The same results as with
the
> newest. I still am not sure is this a bug or am I doing something wrong.
> Server: Apache Tomcat 5.0.28
> JDK: 1.5.0_02
>
Hi there Liubomir,
I'm the one who reported on this issue in a previous post (see "WTP0.7 - JAR
Dependency handling: Regression from 1.0M5 ??"
<news:ac40ea4ee3c93355bf3e80d45ae1f88a$1@www.eclipse.org>).
Just to correct a small mistake, the M20050819 maintenance release actually
came *after* release 0.7, so it's a "newer" release, not a "previous one"...
Or, maybe you are actually saying that you tried an even more recent
maintenance release at first, and that you experienced problems with it ??
In any case, I'm surprised to hear you are experiencing a problem with
M20050819, and that the project list in your "Java JAR dependencies"
property page comes up empty (as to the checkbox, I think it's OK if it's
disabled).
Have you tried to follow the example I described in my post ?
The only difference is I'm using JDK 1.4, not 1.5, but I wouldn't think it
would make a difference.
Regards,
Laurent
|
|
|
| Re: Problem with deployment of dependent projects [message #139793 is a reply to message #139554] |
Tue, 20 September 2005 19:25 |
| Eclipse User |
|
|
|
Originally posted by: l.dokov.enless-soft.coom
Hi again, Laurent, and thank you vary much for your consideration.
I tried to use the workaround you mentioned but it wasn't working. Nothing
seemed to have changed. After restarting the Tomcat server many times (and a
night rest), rebuilding and cleaning all the projects with the added
classpathentry in the .classpath file, now it appears to be working fine. It
copied my utility project compiled files to the classes folder in
WEB-INF(not as a .jar in the lib folder but that's not a problem). After
that I added a second project to be deployed and it is not working. Only the
first dependent project is copied. Looks very strange to me. I will try to
work it out but I hope there will be a fix for this problem soon. Dealing
with .classpath is not something VERY hard but it's time taking.
Thanks again for the help.
Liubomir
|
|
|
Powered by
FUDForum. Page generated in 0.04960 seconds
] 
Search
Help
Register
Login
Home
