| M8 to M9 upgrade gives duplicate class files [message #149615] |
Mon, 28 November 2005 20:58  |
Eclipse User |
|
|
|
I've just finished upgrading a number of WTP 1.0M8 projects to WTP 1.0M9.
I have edited the .settings/.component files* and .classpath file as
needed to rearrange project components as needed. When these files are
compared with the control files for a new "Dynamic Web Project", generated
using the GUI wizard - the syntax is identical. When exporting the "old"
projects to a WAR file, I have duplicate class files. For example,
"WEB-INF/classes/mypackage.MyClass" will also be included as
"mypackage.MyClass". Any ideas?
* virtually identical to the .wtpmodules files in earlier versions of the
WTP
|
|
|
|
| Re: M8 to M9 upgrade gives duplicate class files [message #149647 is a reply to message #149631] |
Tue, 29 November 2005 01:59  |
| Eclipse User |
|
|
|
David Lewis wrote:
> Is this my problem?:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=117956
>
I dont think so.
I believe bug 117956 related to J2EE Dependant projects being published
under the Server tab. The internal class files in those J2EE Utility
projects are being returned unexpectedly. The error the user sees is
explained in bug report:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=116964
Try this one instead:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=116253
This report relates to duplicate classes in WAR files and the fact the
project is outside the default workspace location $HOME/workspace seems
to affect it.
If this problem affects you too, show your interest, maybe it will help
move it up the priority list.
These issues (and a few more) are show stoppers for me and it concerns
me greatly what we are fast approaching WTP 1.0 release yet there is no
smoke test for what I believe to be the bread-and-butter WTP usage of
the masses.
This would cover creating a DWP project, creating a J2EE Utility
project, running XDoclet over DWP, adding the J2EE Utility project to
the DWP as a J2EE Dependancy, creating server runtime, deploying DWP to
server runtime, testing a servlet runs / debugs ok, then exporting to
WAR for production use. For me this basic path has to be usable.
When the _WORKING_ feature set of 0.7.1 and M9 are compare side-by-side
0.7.1 wins, there is still a good 2 weeks left of coding effort and I
know how fast the WTP team are able to respond so I still remain very
optimistic.
Its great to have all the other fancy stuff but if I can't use the
platform to develop a more simplstic project based on static content and
a few servlets, how can I move on to something a little more complex
with confidence.
Darryl
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.08989 seconds
Home