problem with sync classes in domain

John Mazzitelli mazz at redhat.com
Tue Aug 9 21:58:11 UTC 2011


There may be a switch or option on the gwt compiler. Anyone know 
anything about the maven gwt plugin? :) We are launching the gwt 
compiler from maven, I assume there can be some option we can configure 
to do this.

On 08/09/2011 05:56 PM, Charles Crouch wrote:
> Can we get the build to fail on these sorts of errors, rather than requiring someones eagle eye?
>
> ----- Original Message -----
>> I noticed the following GWT compilation errors:
>>
>> [INFO] [ERROR] Errors in
>> 'jar:file:/home/mazz/.m2/repository/org/rhq/rhq-core-domain/4.1.0-SNAPSHOT/rhq-core-domain-4.1.0-SNAPSHOT.jar!/org/rhq/core/domain/sync/entity/SystemSettings.java'
>> [INFO] [ERROR] Line 141: No source code is available for type
>> java.util.Properties; did you forget to inherit a required module?
>> [INFO] [ERROR] Errors in
>> 'jar:file:/home/mazz/.m2/repository/org/rhq/rhq-core-domain/4.1.0-SNAPSHOT/rhq-core-domain-4.1.0-SNAPSHOT.jar!/org/rhq/core/domain/sync/ExportWrapper.java'
>> [INFO] [ERROR] Line 38: No source code is available for type
>> java.io.InputStream; did you forget to inherit a required module?
>>
>> We must be very careful when adding classes to the domain module. If
>> you
>> do, you must look at the GWT output and make sure it can compile
>> everything properly.
>>
>> In this case, these two classes in the ..domain.sync package are
>> utilizing Java API that are NOT available in GWT and thus can not be
>> used by the GWT client. Specifically, java.io classes.
>>
>> It may be true that these classes are not going to be used by GWT
>> clients, however, we need to keep stuff out of the GWT compilation if
>> they a) are not to be intended to be used by GWT clients and/or b)
>> they
>> can't be compiled by GWT.
>>
>> We can discuss tomorrow how to fix this. We either a) must move these
>> out of the domain module entirely or b) figure out a good "exclusion"
>> policy for putting things in domain but keeping them out of the GWT
>> compilation unit. We already have one class in domain where we are
>> doing
>> this, we just need to come up with a good naming policy so we can have
>> a
>> place to put domain objects and keep them out of the GWT stuff.
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/rhq-devel
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel


More information about the rhq-devel mailing list