.1-j5-v4.jar, xjavadoc-1.1-j5.zip,
> xjavadoc-jdk15-patch.diff, xjavadoc-src-1.1-j5-v4.zip
>
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generate
; xjavadoc-jdk15-patch.diff, xjavadoc-src-1.1-j5-v4.zip
>
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generated by JIRA.
For
c-1.1-j5.zip,
> xjavadoc-jdk15-patch.diff, xjavadoc-src-1.1-j5-v4.zip
>
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generated by JIRA.
For
tags when I'm in the
of Class2?
It would be good if there is a function in the Field handler like
and a
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.co
My question is how can I generate a hbm that refers to
http://www.hibernate.org/dtd/ in the dtd instead of
htttp://hibernate.sourceforge.net.
regards
Shirin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
/j2se/1.5.0/docs/api/java/lang/SuppressWarnings.html
--
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/Administ
ine 14, column 36.
> Encountered: @'
> I am however using method level annotations successfully.
> Any help would be appreciated,
> thanks in advance
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
htt
ile = new
File("src/com/acme/tests/XDocletInnerClassProblemTest.java");
SourceSet sc = new FileSourceSet(file);
xjavadoc.addSourceSet(sc);
xjavadoc.getSourceClasses();
}
}
--
This message is automatically generated by JIRA.
-
If you think it was sent incor
d help.
> for tests i have some websphere 6.1 here
--
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
-
rated 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
d help.
> for tests i have some websphere 6.1 here
--
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
-
27;t
> get reconfigured.
> Having a flag in SubTask doesn't solve this - the subtaskmap should
> be reset, so all fields are properly reconfigured, or after execute
> is finished, the fields should be set to null.
> I know there are some related issues that are
.
Firstly , i 'm asking if it is possible or not to run XDoclet to generate Java
Classes while my Web Application is runnig.
Then , how can i make sure that the XDoclet jars are been read.
Finally , if someone have an idea of how to resolve this exception i will be
grathefull for him if he h
1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
; Attachments: xjavadoc-1.1-j5-src.zip, xjavadoc-1.1-j5-v2.jar,
> xjavadoc-1.1-j5-v3.jar, xjavadoc-1.1-j5-v4.jar, xjavadoc-1.1-j5.zip,
> xjavadoc-jdk15-patch.diff, xjavadoc-src-1.1-j5-v4.zip
>
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> Is
analysis compare http://issues.apache.org/jira/browse/GERONIMO-2307
I am currently packaging xdoclet for Debian/Ubuntu. We cannot distribute
proprietary sources in main/universe. Therefore we plan to replace proprietary
DTD/XSD with free versions (where available).
Here's the relevant part
xdoclet it refreshes the weblogic-jar.xml and Jndi information from the
weblogic-jar.xml gets deleted. This is only happening for MDB creation. Could
you please help me out. This is very urgent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of
XDoclet not planning to support Weblogic 9 and 10 folks with EJB2?
--
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/Administrat
t.execute(UnknownElement.java:275)
> [webdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
> [webdoclet] at org.apache.tools.ant.Target.execute(Target.java:341)
> [webdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:369)
> [webdoclet] at
> org.ap
rg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
> [webdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
> [webdoclet] at org.apache.tools.ant.Target.execute(Target.java:341)
> [webdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:369)
&
as in:
for( Object[] obj : list )
--
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.atlassia
question is how to assign for the "street"
attribute a desired column in the person-table
--
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/se
This attribute is no longer
> used. Ignoring.
> It seems that OpenJPA does not support persistence-capable-superclass,
> despite in the JDO 2.0 standard it still exists in the DTD definition.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of
ribute is no longer
> used. Ignoring.
> It seems that OpenJPA does not support persistence-capable-superclass,
> despite in the JDO 2.0 standard it still exists in the DTD definition.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact on
ohdatenMeldungX" declares the
"persistence-capable-superclass" attribute. This attribute is no longer used.
Ignoring.
It seems that OpenJPA does not support persistence-capable-superclass, despite
in the JDO 2.0 standard it still exists in the DTD definition.
--
This message is a
g.apache.tools.ant.Task.perform(Task.java:341)
--
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
on Windows, but on Linux(IC server) java 1.5 grammar
> (annotation, ... ) is not recognize.
--
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.jsp
611 & ant-1.6.5
> Windows
> Linux
>Reporter: Olivier DUGAST
>Assignee: xdoclet-devel (Use for new issues)
>
> Hi all
> It's works perfectly on Windows, but on Linux(IC server) java 1.5 grammar
> (annotation, ... ) is not recognize.
--
This
nnotation, ... ) is not recognize.
--
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
DocletMain.java:46)
> at xdoclet.DocletTask.start(DocletTask.java:457)
> at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:96)
> at org.apache.tools.ant.Task.perform(Task.java:341)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectl
at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:96)
> at org.apache.tools.ant.Task.perform(Task.java:341)
--
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
would be appreciated,
thanks in advance
--
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.atlassi
>
>
> ..
>
> notice that the webservices tag is missplaced, it should be out of
> enterprise-beans tag.
> This can be easily fixed by changing the jboss_xml.xdt files in the jboss
> module
--
This message is
ssage 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/softw
in advance
--
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.atlassi
ossible to generate deployment descriptors using
> current version of ejbdoclet weblogic subtask.
--
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.js
ea Module
>Affects Versions: 1.2.3
>Reporter: Michael Bronshteyn
>Assignee: xdoclet-devel (Use for new issues)
>
> With weblogic 9.1 it is not possible to generate deployment descriptors using
> current version of ejbdoclet weblogic subtask.
--
This message is automat
sues)
> Attachments: ibm-ejb-jar-bnd_xmi.xdt, WebSphereSubTask.java
>
>
> Currently the IBM module does not support to specify a mergeDir and assemble
> the IBM specific deployment descriptor by using the merge snippets.
> See the BEA Weblogic module for how this is done
done!
--
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 informatio
deployment descriptor by using the merge snippets.
See the BEA Weblogic module for how this is done!
--
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
gt;Affects Versions: 1.2.3
>Reporter: Michael Bronshteyn
>Assignee: xdoclet-devel (Use for new issues)
>
> With weblogic 9.1 it is not possible to generate deployment descriptors using
> current version of ejbdoclet weblogic subtask.
--
This message is automatically
eblogic 9.1 it is not possible to generate deployment descriptors using
> current version of ejbdoclet weblogic subtask.
--
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/secu
t; [webdoclet] at org.apache.tools.ant.Task.perform(Task.java:364)
> [webdoclet] at org.apache.tools.ant.Target.execute(Target.java:341)
> [webdoclet] at org.apache.tools.ant.Target.performTasks(Target.java:369)
> [webdoclet] at
> org.apache.tools.ant.Project.executeSortedTarget
j5.zip,
> xjavadoc-jdk15-patch.diff, xjavadoc-src-1.1-j5-v4.zip
>
> Time Spent: 1 hour, 30 minutes
> Remaining Estimate: 0 minutes
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generated by JIRA.
-
If you think i
30 minutes
> Remaining Estimate: 0 minutes
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administr
t; invalid jbosscmp-jdbc entity-entry like:
>
>
>
>
>
>
>
>
>
>
> It must be:
>
>
>
>
>
>
>
>
>
> This tag has therefor to be specified on method-level on methods which
> specifi
has therefor to be specified on method-level on methods which specifiy
jboss.query, jboss.dynamic-query and so on.
--
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
://xdoclet.sourceforge.net/xdoclet/tags/jboss-tags.html
--
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
it's release date.
> Please, build up a release of the core library and all the modules you can:
> we strongly need it!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects
ease is quite stale at over 1 year old, and
> Hibernatedoclet (at least) has lots of patches that need to be released.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/x
f the core library and all the modules you can: we
strongly need it!
--
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
eep in core, where the superceded class in
> question is revisited.
> I made a small patch to stop this revisit in my project, but unfortunatelty
> i'm unable to provide a full patch againt your CVS version.
> The patch is in unified diff format.
--
This message is automatically
cally 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.
-
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
heir sorting in the JavaDoc is out of order also.
Can the tags in the TLD's be sorted alphabetically ?
--
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/Admin
somewhere in the generator code, something is looking
for a method starting with "findByPrimaryKey" if it finds one then it doesn't
generate the method.
I've reported this because I guess some else is going to run into the same
problem.
--
This message is automatically generat
> http://opensource.atlassian.com/projects/xdoclet/browse/XJD-77
> Project: XJavaDoc
> Issue Type: Bug
>Reporter: bracha
>Assignee: xdoclet-devel (Use for new issues)
> Attachments: error building xsd.txt
>
>
--
This messag
Reporter: bracha
Assignee: xdoclet-devel (Use for new issues)
--
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
eep in core, where the superceded class in
> question is revisited.
> I made a small patch to stop this revisit in my project, but unfortunatelty
> i'm unable to provide a full patch againt your CVS version.
> The patch is in unified diff format.
--
This message is automatically g
eep in core, where the superceded class in
> question is revisited.
> I made a small patch to stop this revisit in my project, but unfortunatelty
> i'm unable to provide a full patch againt your CVS version.
> The patch is in unified diff format.
--
This message is automatically g
eep in core, where the superceded class in
> question is revisited.
> I made a small patch to stop this revisit in my project, but unfortunatelty
> i'm unable to provide a full patch againt your CVS version.
> The patch is in unified diff format.
--
This message is automatically g
K into
> "ejbinterfaces" packages (copy "interfaces" to "ejbinterfaces", delete
> "interfaces", replace all references to "com.abc.main.interfaces" with
> "com.abc.main.ejbinterfaces" within generated class files.
> Lo
faces", replace all references to "com.abc.main.interfaces" with
"com.abc.main.ejbinterfaces" within generated class files.
Looks like the packageSubstitution task SHOULD be able to handle the situation
where packages and substituteWith start with the same tex
java:67)
> [ejbdoclet] Error parsing File
> /usr/local/home/ssutton/projects/efms_72/nextjet/enterprise/src/java/com/fedex/cc/eauth/domain/config/EauthPackageConfig.java:Parse
> error at line 156, column 71. Encountered: :
> [ejbdoclet] (XDocletMain.start
[
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1679?page=comments#action_17772
]
Andrew Stevens commented on XDT-1679:
-
Fair enough; in that case it sounds like a bug in the parser grammar. I'm
moving this issue to the XJD JIRA pr
; Is there any Converting tool for weblogic-ejb-jar.xml to Jboss.xml using
> Xdoclet?
--
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
. the language has to be
> read from some other configuration file at runtime when the build process is
> run.
> please let me know any possible approach to achieve my goal of setting
> language value at runtime.
> thanks in advance
> hari
--
This message is automatic
--
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 informa
alue at runtime.
thanks in advance
hari
--
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://ww
believe the xdoclet is not able to parse properly the annotation which takes
a string array with only empty brackets (empty array). This should to be
fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
.3.jar"/>
>location="${env.XDOCLET}/lib/xjavadoc-1.1.jar"/>
>location="${env.XDOCLET}/lib/commons-collections-2.0.jar"/>
>location="${env.XDOCLET}/lib/commons-logging.jar&quo
-devel (Use for new issues)
POrting WEblogic to JBoss:
Is there any Converting tool for weblogic-ejb-jar.xml to Jboss.xml using
Xdoclet?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
uno Braga
> Assignee: xdoclet-devel (Use for new issues)
> Priority: Critical
> Fix For: 1.5
>
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatically generated by JIRA.
-
If you think it was sent inc
gt; Components: Parser
> Versions: 1.0.2
> Reporter: Bruno Braga
> Assignee: xdoclet-devel (Use for new issues)
> Priority: Critical
> Fix For: 1.5
>
>
> Is there any plan to upgrade the parser to support Java 1.5 syntax?
--
This message is automatical
c
> Type: Task
> Versions: 1.0
> Environment: jdk1.4 and j2ee1.4
> Reporter: priyanka rani
> Assignee: xdoclet-devel (Use for new issues)
>
>
> is xjavadoc1.0.jar is compatible with j2ee1.4 and jdk1.4?
> please do reply by earliest.
--
This message is a
anything. I also searched the mailing lists, but only found people
> finding the same problem but no solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.
at is missing from the XDoclet command is the abiilty to add the
> jndi-name capability other than doing so manually.
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.
tton/projects/efms_72/nextjet/enterprise/src/java/com/fedex/cc/eauth/domain/config/EauthPackageConfig.java:Parse
> error at line 156, column 71. Encountered: :
> [ejbdoclet] (XDocletMain.start 47 ) Running
> [ejbdoclet] Generating weblogic-ejb-jar.xml.
&g
newer 1.5 syntax constructs, including
attributes. There is a patched version of xjavadoc in JIRA issue XJD-41 that
allows the processing of files that use 1.5-specific syntax.
> Xdoclet generation for Junit4.2 version
> ---
>
>
from JIRA issue XJD-41? I suspect the
former, in which case it's not so much the "final" that it objects to, but the
":" as that form of the for statement was introduced in Java 1.5 and the older
parser jar doesn't support the newer 1.5-specific syntax.
> XDoc
subtask. Falling back to 2.0
[ejbdoclet] Generating weblogic-cmp-rdbms-jar.xml.
// END STACK TRACE
--
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
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
lled), they don't
> get reconfigured.
> Having a flag in SubTask doesn't solve this - the subtaskmap should
> be reset, so all fields are properly reconfigured, or after execute
> is finished, the fields should be set to null.
> I know there are some related issues that are
distributable="${session.replication}" />
>
>file="${secondDir}/web.xml" type="file" />
>
> web.xml not generated in the ${secondDir}.
>
>
> The worka
uot; />
>
>file="${secondDir}/web.xml" type="file" />
>
> web.xml not generated in the ${secondDir}.
>
>
> The workaround is set destDir attribute on the subtask depl
is detected as End of Comment by
> the Java Compiler and/or JavaDoc parser. The Java Language Specification does
> not specify any escaping in Java Comments.
> I browsed any Documentation for XDoclet if it provides any Escaping, but did
> not find anything. I also searched the mailing lis
is detected as End of Comment by
> the Java Compiler and/or JavaDoc parser. The Java Language Specification does
> not specify any escaping in Java Comments.
> I browsed any Documentation for XDoclet if it provides any Escaping, but did
> not find anything. I also searched the mailing lis
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
the second webdoclet task. But one have to specify "destDir" on the
parent task also since it is required.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projec
not be set to the calculated session
> class name.
--
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/Administ
t be set to the calculated session
> class name.
--
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/secur
less" * transaction-type="Container"
> *
> * **
> if i do this deployment descriptor gets created.
> But the eclipse JST is failing at some where else. It is expecting @ejb.bean
> to be the first tag.
> Lachu
--
This message is
quot;equipmentDao"
> class="com.xxx.dao.spring.hibernate.EquipmentDaoHibernateImpl"
> >
>
>
>
>
> id="baseDao"
> class="com.xxx.dao.spring.hibernate.EquipmentDaoHibernateImpl"
> >
>
>
-file, whether a session
> class should or should not be generated for the bean class. At the true
> value, the session class should not be generated and the deployment
> descriptor bean class attribute should not be set to the calculated session
> class name.
--
This message is
uld govern file-by-file, whether a session
> class should or should not be generated for the bean class. At the true
> value, the session class should not be generated and the deployment
> descriptor bean class attribute should not be set to the calculated session
> class name.
--
,
the session class should not be generated and the deployment descriptor bean
class attribute should not be set to the calculated session class name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http
in
> your project.properties or just strips off "Bean"
leaving you with org.springframework.ejb.support.AbstractStatelessSession
which also does not exist. I've scoured the earth looking for any
documentation, blog, or anything that will tell me how to get around this. I
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/xdo
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/proje
doclet
> xdoclet-jboss-module
> 1.2.3
>
>
> xdoclet
> xdoclet-jmx-module
> 1.2.3
>
>
> xdoclet
> xdoclet-web-module
> 1.2.3
>
1 - 100 of 568 matches
Mail list logo