0 Replies Latest reply on Nov 24, 2008 9:49 AM by Tom Baeyens

    xsddoc

    Tom Baeyens Master

      can someone on linux fiddle around with the xsddoc task ?

      in jbpm 4, in api, there is this snippet commented:

      <!--
       <plugin>
       <artifactId>maven-antrun-plugin</artifactId>
       <executions>
       <execution>
       <id>generate-jpdlxsd-doc</id>
       <phase>package</phase>
       <goals>
       <goal>run</goal>
       </goals>
       <configuration>
       <tasks>
       <echo message="basedir: ${basedir}" />
       <taskdef name="xsddoc" classname="net.sf.xframe.xsddoc.Task" classpathref="maven.plugin.classpath" />
       <mkdir dir="target/doc/schemadoc" />
       <xsddoc out="${basedir}/target/doc/schemadoc" title="jBPM 4 Schema's" verbose="false">
       <fileset dir="src/main/resources" />
       </xsddoc>
       </tasks>
       </configuration>
       </execution>
       </executions>
       <dependencies>
       <dependency>
       <groupId>xsddoc</groupId>
       <artifactId>xsddoc</artifactId>
       <version>1.0</version>
       </dependency>
       <dependency>
       <groupId>xalan</groupId>
       <artifactId>xalan</artifactId>
       <version>2.7.0</version>
       </dependency>
       </dependencies>
       </plugin>
       -->


      If you uncomment it, it works on my windows, but not on linux with java5 for some reason.

      It has to do with how maven passes the basedir property to the ant task, i believe.

      It's in this hudson run that i got a problem:

      http://jbpm.dyndns.org:8180/hudson/job/jBPM4-JDK1.5/9/console

      for some reason or another, the basedir seems to be duplicated:

      and without the basedir, it doesn't work when this build is being called from the parent project.

      it seems a pitty that we can't use this as it works well on windows and i couldn't get this xsddoc to work in any other way. also not the maven integration...