El lun, 30-01-2006 a las 23:22 +0000, Ross Gardler escribió: > David Crossley wrote: > > Ross Gardler wrote: > > > >>Thorsten Scherler wrote: > >> > >>>Hi all, > >>> > >>>I tried to release the dispatcher plugins that they are downloadable to > >>>drop the need for local deploy. > >>> > >>>However: > >>>BUILD FAILED > >>>... > >>>/home/thorsten/src/apache/forrest-trunk/plugins/build.xml:413: srcdir > >>>"/home/thorsten/src/apache/forrest-trunk/plugins/org.apache.forrest.plugin.input.projectInfo/src/java" > >>> does not exist! > >>> > >>>Why does that not exist? > >> > >>It does exist in the plugin template, so the only reason it can't exist > >>in your plugins is that you either deleted it or did not use the template. > >> > >> > >>>Why do I need this anyway? > >> > >>It is used for (you guessed it) java files, but also for DTD catalogs. > > > > > > Actually the DTDs and other schema are in resources/schema > > Yes, you are right, for some reason I was thinking the catalog files > went in the java dir. > > >>The ant script could be modified to allow the build to continue if it is > >>not present. > > > > > > Yep. > > Actually, it already is optional. > > The projectInfo plugin, for example, does not have a java dir. > > The line referenced by Thorsten above is the one that compiles the java > classes and should only be executed if the property "java_exists" has > been set. > > So, Thorsten, it shouldn't fail. I have no suggestions as to why it is > doing so. What are you doing that is "non-standard".
jeje, it is failing of two reasons. 1) forrest site is ATM broken for the dispatcher there is something wrong with the images that I need to track down (that is the reason why e.g. the dispatcher plugin wont deploy). 2) themes.core is not using the "default plugin" structure: http://issues.apache.org/jira/browse/FOR-801 So I guess this is "non-standard". ;-) salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
