search

nijogeorgep / smartgwt

Automatically exported from code.google.com/p/smartgwt
0 stars 0 forks source link

org.apache.catalina cannot be resolved #708

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
While building against smartgwt 3.1 I came across this error:

Errors in 
'jar:file:SmartGWT/3.1/smartgwt.jar!/com/smartgwt/client/util/DateUtil.java'
   [ERROR] Line 5: The import org.apache.catalina cannot be resolved

Looking at com.smartgwt.client.util.DateUtil I noticed that there is an import 
to org.apache.catalina.startup.SetDocBaseRule which isn't even used.

Thanks.

Original issue reported on code.google.com by initialZ...@gmail.com on 16 Feb 2013 at 1:55

GoogleCodeExporter commented 8 years ago 
This was fixed long ago in nightly builds, but has now been fixed in SVN as 
well (presumably you did your own build).

Original comment by smartgwt...@gmail.com on 16 Feb 2013 at 6:13

GoogleCodeExporter commented 8 years ago 
Actually, this is in the smartgwt-3.1.zip download from 
https://code.google.com/p/smartgwt/downloads/detail?name=smartgwt-3.1.zip

Original comment by initialZ...@gmail.com on 16 Feb 2013 at 10:11

GoogleCodeExporter commented 8 years ago 
This has already been confirmed fixed by multiple users, so most likely, 
although you have downloaded a new build, you are still running older code due 
to caching, forgetting to run a GWT compile, having multiple .jars in your path 
or a similar problem.

Original comment by smartgwt...@gmail.com on 17 Feb 2013 at 3:31

GoogleCodeExporter commented 8 years ago 
Does this fix get commited to the Maven repository as well?

Original comment by chris.f...@gmail.com on 14 Mar 2013 at 4:03

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I have the same error, jar downloaded from this page, new project started. So 
problem for sure is not solved

Original comment by dereszow...@gmail.com on 23 Mar 2013 at 9:27

GoogleCodeExporter commented 8 years ago 
I used Maven and the SmartClient Maven repository to download the artifact 
named smartgwt-3.1.jar (you can get it yourself at 
http://smartclient.com/maven2/com/smartgwt/smartgwt/3.1/smartgwt-3.1.jar).  You 
will see when you open this jar file that the DateUtil.java contained therein 
features the import in question.

Original comment by ljnelson on 9 Apr 2013 at 11:43

GoogleCodeExporter commented 8 years ago 
Here is a stupid workaround that worked for me (I'm using the gwt-maven-plugin 
for compilation):

1. Create a no-op java file named 
org.apache.catalina.startup.SetDocBaseRule.java.  Locate it in the project 
where GWT compilation takes place.

2. In that project put a GWT module somewhere that references the containing 
package.  In my case, I made a Startup.gwt.xml module in 
mywarproject/src/main/resources/org/apache/catalina whose contents were, in 
total:

<module>
  <inherits name="com.google.gwt.user.User" />
  <source path="startup" />
</module>

3. In your GWT module that contains the entry point, make it inherit this dummy 
module first:

<inherits name="org.apache.catalina.Startup" />

This works around the issue.

Original comment by ljnelson on 9 Apr 2013 at 11:54

GoogleCodeExporter commented 8 years ago 
We don't change releases that have already gone out (that's what is meant by 
"release") so you will not get the fix if you are specifically downloading the 
original 3.1 release and ignoring the patched builds.

If you don't know how to get patched builds through Maven, instructions are 
here:

     http://forums.smartclient.com/showthread.php?t=24921

Original comment by smartgwt...@gmail.com on 9 Apr 2013 at 11:54

GoogleCodeExporter commented 8 years ago 
Ah! I see; I saw that your Maven repository contains some patched builds 
(http://smartclient.com/maven2/com/smartgwt/smartgwt/2.5-patch/), so I simply 
figured that 3.1 didn't have any further patches.  I'll use the 
smartgwt-maven-plugin available from the Sonatype staging repository mentioned 
in the forum thread to bootstrap things I guess.  Thanks.  Is there a reason 
you don't propagate patched builds (or all of them, anyway) to your Maven 
repository? That would be very helpful.

Original comment by ljnelson on 10 Apr 2013 at 12:41

GoogleCodeExporter commented 8 years ago 
We don't propagate them because it would be redundant with the new (Sonatype) 
mechanism and because we don't want to keep older builds.  The system at 
smartclient.com/builds already cleans up stale builds.

Original comment by smartgwt...@gmail.com on 10 Apr 2013 at 12:45