As long as they are called through the service engine or some other
means of late-binding (ie so they won't break the compilation of
other things) then we can just exclude the various Java files
involved from the build script(s) and then call it good. In the UI if
someone tries to use them and it results in a service call there will
be an error that the class isn't found, and they'll just have to drop
in the UNO jars, comment out the class build exclusion in the
build.xml file(s) and then build and run.
-David
On Jan 29, 2006, at 1:23 AM, Al Byers wrote:
> Would it make sense to move the OpenOffice services to a specialized
> webapp just so they will not cause the compile to break by their
> absence? They are currently in org.ofbiz.content.openoffice.
>
> -Al
>
> _______________________________________________
> Dev mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/dev_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
Locked
