[XDoclet-JIRA] Commented: (XDT-1486) xdoclet-jboss-module breaks xdoclet:ejbdoclet maven target

"Stan Kurdziel (JIRA)" <[email protected]>
Newsgroups gmane.comp.java.xdoclet.devel
Message-ID <[email protected]>
    [ http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1486?page=comments#action_17509 ] 

Stan Kurdziel commented on XDT-1486:
------------------------------------

Thanks Felipe!   Awesome work.

For anyone who may be reading, I still took some time to digest everything and get it working, so I figured I'd attach a summary and perhaps help the next person trying to get the jboss.xml to generate.

1. As of 3/9/2006, use version 1.2.3 on everything:
Plugin can be installed with the command
maven -Dmaven.repo.remote=http://xdoclet.sourceforge.net/repository plugin:download -DgroupId=xdoclet -DartifactId=maven-xdoclet-plugin -Dversion=1.2.3

2. Here's the list of dependencies for the project.xml
        <dependency>
            <groupId>xdoclet</groupId>
            <artifactId>xdoclet-jboss-module</artifactId>
            <version>1.2.3</version>
        </dependency>
        <dependency>
            <groupId>xdoclet</groupId>
            <artifactId>xdoclet-jmx-module</artifactId>
            <version>1.2.3</version>
        </dependency>
        <dependency>
            <groupId>xdoclet</groupId>
            <artifactId>xdoclet-web-module</artifactId>
            <version>1.2.3</version>
        </dependency>

3. The project.properties must specify the jboss module to be run.  See attachments for a complete example, but for each EJB you will need this line at minimum:
maven.xdoclet.ejbdoclet.jboss.0=true

4.  You can use the command "maven xdoclet:ejbdoclet" to test artifact generation.   To get to run automatically, use the java:compile pregoal in the maven.xml:
ex:
<project>
    <preGoal name="java:compile">
        <attainGoal name="xdoclet:ejbdoclet"/>
    </preGoal>
</project>


> xdoclet-jboss-module breaks xdoclet:ejbdoclet maven target
> ----------------------------------------------------------
>
>          Key: XDT-1486
>          URL: http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1486
>      Project: XDoclet
>         Type: Bug

>   Components: Maven Plugin, JBoss Module
>     Versions: 1.2.3
>  Environment: JDK 1.5.0 (Windows XP), Maven 1.0.2, XDoclet 1.2.3
>     Reporter: Fredrik Vraalsen
>     Assignee: xdoclet-devel (Use for new issues)
>  Attachments: maven-xdoclet-output-with-jboss-module.txt, maven-xdoclet-output-without-jboss-module.txt, project.properties, project.xml, xdoclet_v1.zip, xdoclet_v2.zip
>
>
> I am unable to get the Maven plugin to generate the jboss.xml file.  As per the instructions on the XDoclet Maven plugin webpage, I tried adding xdoclet-jboss-module-1.2.3.jar to my project dependencies.
> As the xdoclet-jboss-module-1.2.3.jar is not available from the ibiblio maven repository I copied the file manually into my local maven repository.
> However, when I add the jboss module to my dependencies, the xdoclet:ejbdoclet target doesn't work at all.  None of the other files are generated either, it just finishes without any output or error messages whatsoever.
> I'm attaching my project.properties, project.xml as well as the output captured from the command 'maven -o -X xdoclet:ejbdoclet' both with and without the jboss module in my project dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.