Re: xdoclet plugin for maven - custom tag handlers

[Brian Topping]

If you aren't getting a stack trace with the error, run 'mvn -X install' to get 
one.  There will be a lot more information to wade through, but it will be in 
there.

Once you find it, download the sources for the version of XDoclet you are using 
and take a look at where it's getting caught up.  If you want to debug into 
XDoclet, there is a version of Maven that is installed called mvndebug (i.e. 
mvndebug install which will allow you to set breakpoints in XDoclet and debug 
it.

I'm sure you know this already, but it's been several years since XDoclet has 
been actively developed or supported, and you'd really be better off moving to 
JSR-175 annotations. 

Brian


On Oct 11, 2012, at 11:52 AM, Abitfarago Cini ciniabitfar...@gmail.com wrote:

 Hi,
 
 I try to port an old Ant based build to Maven. It contains multiple xdoclet
 generations, of them (for XML files) uses home brewed tag handlers. These
 handlers are built separately and the artifact is installed in my local
 repository.
 
 When I run the *mvn install* it complains saying:
 
 [ERROR] Failed to execute goal
 org.codehaus.mojo:xdoclet-maven-plugin:1.0:xdoclet (default) on project
 pcm-services-model: Error executing ant tasks: Unexpected error: XDoclet
 failed. xdoclet.template.TemplateException: Could not find tag handler for
 prefix: 'xdclDum' - [Help 1]
 
 What I am missing?
 
 Abitfarago


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: XDoclet plugin failed: Failed to set property restrictedpath

[jembo]

Did anybody solved this problem and can help me, because i have the same
problem. I tried a lot but without any effect 

Thanks a lot...
Jembo


rexhuang936 wrote:
 
 Hi all.
 I tried to build magnolia trunk, everything seems ok, but
 magnolia-taglib-cms isn't. I got this message, and I don't know how to fix
 it. Anybody can help me ?
 
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building CMS Tag Library
 [INFO]task-segment: [clean, install]
 [INFO]
 
 [INFO] [clean:clean]
 [INFO] [enforcer:enforce {execution: enforce}]
 [WARNING] Attempting to build MavenProject instance for Artifact
 (org.codehaus.xdoclet:maven2-xdoclet2-plugin:2.0.7-20090427.164453-14) of
 type: maven-plugin; constructing POM arti
 [INFO] [2-xdoclet2:xdoclet {execution: xdoclet-tld}]
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] XDoclet plugin failed: Failed to set property restrictedpath to
 file://C:\Users\Phan Le Thanh Chuong\.m2\repository: null
 
 The filename, directory name, or volume label syntax is incorrect
 [INFO]
 
 [INFO] Trace
 org.apache.maven.lifecycle.LifecycleExecutionException: XDoclet plugin
 failed: Failed to set property restrictedpath to file://C:\Users\Phan Le
 Thanh Chuong\.m2\repository: null
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
 
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
 
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
 
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
 
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
 
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
 
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 
 at java.lang.reflect.Method.invoke(Method.java:585)
 at
 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Caused by: org.apache.maven.plugin.MojoExecutionException: XDoclet plugin
 failed: Failed to set property restrictedpath to file://C:\Users\Phan Le
 Thanh Chuong\.m2\repository: null
 at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:260)
 at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
 
 at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
 
 ... 16 more
 Caused by: org.picocontainer.PicoInitializationException: Failed to set
 property restrictedpath to file://C:\Users\Phan Le Thanh
 Chuong\.m2\repository: null
 at
 org.picocontainer.defaults.BeanPropertyComponentAdapter.getComponentInstance(BeanPropertyComponentAdapter.java:79)
 
 at
 org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfType(DefaultPicoContainer.java:274)
 
 at
 org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfTypeWithContainerAdaptersLast(DefaultPicoContainer.java:377)
 
 at
 org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:347)
 
 at
 org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(LifecycleContainerBuilder.java:52)
 
 at
 org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(LifecycleContainerBuilder.java:45)
 
 at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:251)
 ... 18 more
 Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25

XDoclet plugin failed: Failed to set property restrictedpath

[Rex Huang]

Hi all.
I tried to build magnolia trunk, everything seems ok, but
magnolia-taglib-cms isn't. I got this message, and I don't know how to fix
it. Anybody can help me ?

[INFO] Scanning for projects...
[INFO]

[INFO] Building CMS Tag Library
[INFO]task-segment: [clean, install]
[INFO]

[INFO] [clean:clean]
[INFO] [enforcer:enforce {execution: enforce}]
[WARNING] Attempting to build MavenProject instance for Artifact
(org.codehaus.xdoclet:maven2-xdoclet2-plugin:2.0.7-20090427.164453-14) of
type: maven-plugin; constructing POM arti
[INFO] [2-xdoclet2:xdoclet {execution: xdoclet-tld}]
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] XDoclet plugin failed: Failed to set property restrictedpath to
file://C:\Users\Phan Le Thanh Chuong\.m2\repository: null

The filename, directory name, or volume label syntax is incorrect
[INFO]

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: XDoclet plugin
failed: Failed to set property restrictedpath to file://C:\Users\Phan Le
Thanh Chuong\.m2\repository: null
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: XDoclet plugin
failed: Failed to set property restrictedpath to file://C:\Users\Phan Le
Thanh Chuong\.m2\repository: null
at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:260)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)

... 16 more
Caused by: org.picocontainer.PicoInitializationException: Failed to set
property restrictedpath to file://C:\Users\Phan Le Thanh
Chuong\.m2\repository: null
at
org.picocontainer.defaults.BeanPropertyComponentAdapter.getComponentInstance(BeanPropertyComponentAdapter.java:79)

at
org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfType(DefaultPicoContainer.java:274)

at
org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfTypeWithContainerAdaptersLast(DefaultPicoContainer.java:377)

at
org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:347)

at
org.nanocontainer.integrationkit.LifecycleContainerBuilder.autoStart(LifecycleContainerBuilder.java:52)

at
org.nanocontainer.integrationkit.LifecycleContainerBuilder.buildContainer(LifecycleContainerBuilder.java:45)

at org.codehaus.xdoclet.XDocletMojo.execute(XDocletMojo.java:251)
... 18 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)
at
org.picocontainer.defaults.BeanPropertyComponentAdapter.getComponentInstance(BeanPropertyComponentAdapter.java:77)

... 24 more
Caused by: java.io.IOException: The filename, directory name, or volume
label syntax is incorrect

maven 2 + xdoclet plugin out of memory

[ppppppp]

I know xdoclet is old crusty last century technology, but we use it and are
really frustrated with using it with maven. The plugin itself is seems
faulty, we can't get the task to run using 'mvn xdoclet:xdoclet' and the
codebase has not been touched in about two years leaving it in in an alpha
state.

Today, after years of relative quiet, we ran into a problem with the xdoclet
plugin failing with outofmemory exceptions on one of our developer's
machines. We found that using 2.0.5 but not older or newer versions worked.
I'd be happy to blame this problem on xdoclet (xjavadoc to be specific, see
below) except for this. Yes, we're using a hacked xjavadoc.jar to work with
generics.

This kind of stuff drives us nuts. Has anybody else seen this? Any ideas
what would cause it? Something in our own code that drives xdoclet wild in a
maven 2.0.{x!=5} way?

pre
SEVERE: Invoking method failed:
xdoclet.tagshandler.ClassTagsHandler.forAllClasses, line=106 of template
file: jar:file:
/C:/java/.m2/repository/xdoclet/xdoclet-spring-module/1.2.3/xdoclet-spring-module-1.2.3.jar!/xdoclet/modules/spring/reso
urces/spring_xml.xdt
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at xdoclet.template.TemplateEngine.invoke(TemplateEngine.java:641)
at
xdoclet.template.TemplateEngine.invokeMethod(TemplateEngine.java:567)
at
xdoclet.template.TemplateEngine.invokeBlockMethod(TemplateEngine.java:965)
at
xdoclet.template.TemplateEngine.handleBlockTag(TemplateEngine.java:932)
at
xdoclet.template.TemplateEngine.handleTag(TemplateEngine.java:472)
at xdoclet.template.TemplateEngine.generate(TemplateEngine.java:348)
at xdoclet.template.TemplateEngine.start(TemplateEngine.java:415)
at xdoclet.TemplateSubTask.startEngine(TemplateSubTask.java:562)
at
xdoclet.TemplateSubTask.startProcessForAll(TemplateSubTask.java:618)
at xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:599)
at xdoclet.XmlSubTask.startProcess(XmlSubTask.java:227)
at
xdoclet.modules.spring.SpringXmlSubTask.execute(SpringXmlSubTask.java:111)
at xdoclet.XDocletMain.start(XDocletMain.java:48)
at xdoclet.DocletTask.start(DocletTask.java:468)
at xjavadoc.ant.XJavadocTask.execute(XJavadocTask.java:105)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:99)
at
org.codehaus.mojo.xdoclet.XDocletMojo.execute(XDocletMojo.java:102)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:48
0)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.OutOfMemoryError: Java heap space
at xjavadoc.JavaCharStream.GetImage(JavaCharStream.java:469)
at
xjavadoc.SimpleParserTokenManager.jjFillToken(SimpleParserTokenManager.java:1885)
at
xjavadoc.SimpleParserTokenManager.getNextToken(SimpleParserTokenManager.java:1972)
at xjavadoc.SimpleParser.jj_scan_token(SimpleParser.java:6681

Re: Is there an XDoclet Plugin which uses XJavadoc 1.5 (Generics) ?

[Mac-Systems]

Hello,

we already patched the XDoclet Plugin with the new XJavaDoc Plugin, 
Works for us.
I'd like to update the maven repository, so anyone can tell me who is 
responsible

for maven xdoclet plugin ?

regards,
jens


Hi,

We are also interested by using Xdoclet with JDK 1.5.

What I understood is we need a specific version of the xjavadoc library :
xjavadoc-1.5-050611.jar

An issue was opened in order to upload this library : MAVENUPLOAD-1399 (cf.
http://jira.codehaus.org/browse/MAVENUPLOAD-1399).
The status is Closed and the resolution Incomplete.
I am not sure to understand why. Perhaps Carlos can explain ?
But this library is unfortunately not available is the maven 2 repository.

An other issue is open in order to take into account this new library by the
maven xdoclet plugin : MOJO-665 (cf.
http://jira.codehaus.org/browse/MOJO-665).
The status is still open and is Unassigned.

I don't really know what to do except from upload it in my maven 2 proxy
repository.
But I think it's better if these issues can be resolved by the maven 2
community.

I don't know if a commiter can help for that.

Rémy

  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Is there an XDoclet Plugin which uses XJavadoc 1.5 (Generics) ?

[Rémy Sanlaville]

Hi,

We are also interested by using Xdoclet with JDK 1.5.

What I understood is we need a specific version of the xjavadoc library :
xjavadoc-1.5-050611.jar

An issue was opened in order to upload this library : MAVENUPLOAD-1399 (cf.
http://jira.codehaus.org/browse/MAVENUPLOAD-1399).
The status is Closed and the resolution Incomplete.
I am not sure to understand why. Perhaps Carlos can explain ?
But this library is unfortunately not available is the maven 2 repository.

An other issue is open in order to take into account this new library by the
maven xdoclet plugin : MOJO-665 (cf.
http://jira.codehaus.org/browse/MOJO-665).
The status is still open and is Unassigned.

I don't really know what to do except from upload it in my maven 2 proxy
repository.
But I think it's better if these issues can be resolved by the maven 2
community.

I don't know if a commiter can help for that.

Rémy

Is there an XDoclet Plugin which uses XJavadoc 1.5 (Generics) ?

[Mac-Systems]

Anyone can point to to a Version which allows to use Generics with XDoclet ?


regards,
Jens



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven2 Xdoclet Plugin - Project Source Dir

[Brian Ashburn]

Has anyone been able to work through or dealt with using a different project
source directory than src/main/java?  I'm trying to get Maven2 building a
legacy system.  I don't have the luxury of changing the source directory.  I
set it in the project.build.sourceDirectory, but the xdoclet plugin doesn't
pick it up.  Any help would be greatly appreciated.

-BA

RE: Maven2 Xdoclet Plugin - Project Source Dir

[Mark Eramo]

Hi Brian,
   I do this for one of my projects, although I am just using the jar-plugin 
but this should work for any plugin.
In your pom.xml you sould have a build tag. At the start of the build tag, 
add the following:
 
sourceDirectoryyour src path/sourceDirectory
 
Regards,
Mark



From: Brian Ashburn [mailto:[EMAIL PROTECTED]
Sent: Mon 12/3/2007 10:47 AM
To: users@maven.apache.org
Subject: Maven2 Xdoclet Plugin - Project Source Dir



Has anyone been able to work through or dealt with using a different project
source directory than src/main/java?  I'm trying to get Maven2 building a
legacy system.  I don't have the luxury of changing the source directory.  I
set it in the project.build.sourceDirectory, but the xdoclet plugin doesn't
pick it up.  Any help would be greatly appreciated.

-BA

RE: Xdoclet plugin for generating EJB sources of ejbdoclet project

[COPPENS, Fabien]

 
Hi.
You are right it xdoclet 1.2.3.
I have already tried what you suggest, but I get this kind of error :

[INFO] Internal error in the plugin manager executing goal 
'org.codehaus.mojo:xdoclet-maven-plugin:1.0-alpha-2:xdoclet': Unable to find 
the mojo 'org.codehaus.mojo:x
doclet-maven-plugin:1.0-alpha-2:xdoclet' in the plugin 
'org.codehaus.mojo:xdoclet-maven-plugin'
org/apache/tools/ant/PropertyHelper


-Message d'origine-
De : Bob Allison [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 6 septembre 2007 01:32
À : Maven Users List
Objet : Re: Xdoclet plugin for generating EJB sources of ejbdoclet project

Are you sure that you are using XDoclet 1.3.2 and not 1.2.3?  I do not see a 
version 1.3.x on the XDoclet home page.

In my projects that use XDoclet, I specify:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
  execution
phasegenerate-sources/phase
goals
  goalxdoclet/goal
/goals
configuration
  tasks
ejbdoclet ... 
..
..
..
/ejbdoclet
  /tasks
/configuration
  /execution
/executions
  /plugin

Using this downloads all of the correct bits and pieces from the repository for 
XDoclet 1.2.3

HTH

- Original Message -
From: COPPENS, Fabien [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Wednesday, September 05, 2007 10:36 AM
Subject: Xdoclet plugin for generating EJB sources of ejbdoclet project



I am trying to automate the build of an EJB project that was generated
in Eclipse 3.2.2
using the Web Tools Platform (WTP 1.5.4) wizard for ejbdoclet projects.
This WTP service is based on xdoclet 1.3.2 (I see that in the project
facets).
I get a failure when trying to use the plugin xdoclet-maven-plugin
because it is apparently
expecting xdoclet v2.
When I look at repo1.maven.org/maven2/xdoclet-plugins, I see that there
are many different xdoclet plugins, including one called
xdoclet-plugin-ejb.

Can someone point me to a xdoclet plugin that will be compatible with
xdoclet 1.3.2 so that I can automate
my EJB project build ?

Fabien


This message contains information that may be privileged or confidential and 
is the property of the Capgemini Group. It is intended only for the person 
to whom it is addressed. If you are not the intended recipient,  you are not 
authorized to read, print, retain, copy, disseminate,  distribute, or use 
this message or any part thereof. If you receive this  message in error, 
please notify the sender immediately and delete all  copies of this message.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Xdoclet plugin for generating EJB sources of ejbdoclet project

[COPPENS, Fabien]

Ok, I found the solution to the problem here :
http://www.nabble.com/Re:-maven-2.0.6-and-xdoclet-maven-plugin-p9839377s177.html

I needed to add a dependency to ant :

dependencies
dependency
groupIdant/groupId
artifactIdant/artifactId
version1.6.5/version
/dependency
/dependencies 


-Message d'origine-
De : COPPENS, Fabien [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 6 septembre 2007 11:51
À : Maven Users List
Objet : RE: Xdoclet plugin for generating EJB sources of ejbdoclet project


 
Hi.
You are right it xdoclet 1.2.3.
I have already tried what you suggest, but I get this kind of error :

[INFO] Internal error in the plugin manager executing goal 
'org.codehaus.mojo:xdoclet-maven-plugin:1.0-alpha-2:xdoclet': Unable to find 
the mojo 'org.codehaus.mojo:x doclet-maven-plugin:1.0-alpha-2:xdoclet' in the 
plugin 'org.codehaus.mojo:xdoclet-maven-plugin'
org/apache/tools/ant/PropertyHelper


-Message d'origine-
De : Bob Allison [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 6 septembre 2007 01:32
À : Maven Users List
Objet : Re: Xdoclet plugin for generating EJB sources of ejbdoclet project

Are you sure that you are using XDoclet 1.3.2 and not 1.2.3?  I do not see a 
version 1.3.x on the XDoclet home page.

In my projects that use XDoclet, I specify:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdxdoclet-maven-plugin/artifactId
executions
  execution
phasegenerate-sources/phase
goals
  goalxdoclet/goal
/goals
configuration
  tasks
ejbdoclet ... 
...
...
...
/ejbdoclet
  /tasks
/configuration
  /execution
/executions
  /plugin

Using this downloads all of the correct bits and pieces from the repository for 
XDoclet 1.2.3

HTH

- Original Message -
From: COPPENS, Fabien [EMAIL PROTECTED]
To: users@maven.apache.org
Sent: Wednesday, September 05, 2007 10:36 AM
Subject: Xdoclet plugin for generating EJB sources of ejbdoclet project



I am trying to automate the build of an EJB project that was generated in 
Eclipse 3.2.2 using the Web Tools Platform (WTP 1.5.4) wizard for ejbdoclet 
projects.
This WTP service is based on xdoclet 1.3.2 (I see that in the project facets).
I get a failure when trying to use the plugin xdoclet-maven-plugin because it 
is apparently expecting xdoclet v2.
When I look at repo1.maven.org/maven2/xdoclet-plugins, I see that there are 
many different xdoclet plugins, including one called xdoclet-plugin-ejb.

Can someone point me to a xdoclet plugin that will be compatible with xdoclet 
1.3.2 so that I can automate my EJB project build ?

Fabien


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Xdoclet plugin for generating EJB sources of ejbdoclet project

[COPPENS, Fabien]

I am trying to automate the build of an EJB project that was generated
in Eclipse 3.2.2
using the Web Tools Platform (WTP 1.5.4) wizard for ejbdoclet projects.
This WTP service is based on xdoclet 1.3.2 (I see that in the project
facets).
I get a failure when trying to use the plugin xdoclet-maven-plugin
because it is apparently
expecting xdoclet v2.
When I look at repo1.maven.org/maven2/xdoclet-plugins, I see that there
are many different xdoclet plugins, including one called
xdoclet-plugin-ejb.
 
Can someone point me to a xdoclet plugin that will be compatible with
xdoclet 1.3.2 so that I can automate
my EJB project build ?
 
Fabien


This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.

Re: Xdoclet plugin for generating EJB sources of ejbdoclet project

[Bob Allison]

Are you sure that you are using XDoclet 1.3.2 and not 1.2.3?  I do not see a 
version 1.3.x on the XDoclet home page.


In my projects that use XDoclet, I specify:
plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdxdoclet-maven-plugin/artifactId
   executions
 execution
   phasegenerate-sources/phase
   goals
 goalxdoclet/goal
   /goals
   configuration
 tasks
   ejbdoclet ... 
.
.
.
   /ejbdoclet
 /tasks
   /configuration
 /execution
   /executions
 /plugin

Using this downloads all of the correct bits and pieces from the repository 
for XDoclet 1.2.3


HTH

- Original Message - 
From: COPPENS, Fabien [EMAIL PROTECTED]

To: users@maven.apache.org
Sent: Wednesday, September 05, 2007 10:36 AM
Subject: Xdoclet plugin for generating EJB sources of ejbdoclet project



I am trying to automate the build of an EJB project that was generated
in Eclipse 3.2.2
using the Web Tools Platform (WTP 1.5.4) wizard for ejbdoclet projects.
This WTP service is based on xdoclet 1.3.2 (I see that in the project
facets).
I get a failure when trying to use the plugin xdoclet-maven-plugin
because it is apparently
expecting xdoclet v2.
When I look at repo1.maven.org/maven2/xdoclet-plugins, I see that there
are many different xdoclet plugins, including one called
xdoclet-plugin-ejb.

Can someone point me to a xdoclet plugin that will be compatible with
xdoclet 1.3.2 so that I can automate
my EJB project build ?

Fabien


This message contains information that may be privileged or confidential and 
is the property of the Capgemini Group. It is intended only for the person 
to whom it is addressed. If you are not the intended recipient,  you are not 
authorized to read, print, retain, copy, disseminate,  distribute, or use 
this message or any part thereof. If you receive this  message in error, 
please notify the sender immediately and delete all  copies of this message.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: xdoclet plugin and weblogic-ejb-jar.xml descriptor

[Brian Smith]

I'm using Weblogic 9.2.  I think you're correct in that the weblogic plugin
only works for versions 8.x and earlier.   I haven't found any great
solutions for this hurdle yet.

On 8/31/07, Scott Ryan [EMAIL PROTECTED] wrote:

 What version of Weblogic are you using?  You can use the weblogic tag
 to generate the XML files  but as far as I know xdoclet can only
 generate xml files for 8.x and prior.  9.x and 10.x are not supported
 but then maybe you should be using JPA, EJB 3.0 or Hibernate by then.

 Scott Ryan
 CTO Soaring Eagle L.L.C.
 Denver, Co. 80129
 www.soaringeagleco.com
 www.theryansplace.com
 (303) 263-3044
 [EMAIL PROTECTED]


 On Aug 31, 2007, at 9:34 AM, Brian Smith wrote:

  I'm working on a simple HelloWorldEJB stateless session bean that I
  want to
  run in Weblogic.  I'm using the xdoclet plugin and xdoclet is able to
  generate the home/remote classes.  Should xdoclet be able to
  generate the
  weblogic-ejb-jar.xml descriptor?  If so, how do I do this?  Is there a
  special tag in the EJB source code or is there something in the pom
  I need
  to specify?
 
  I'm guessing this a task of xdoclet instead of maven but I'm not
  sure.  Any
  input would be appreciated.
 
  Thanks,
  Brian

Re: xdoclet plugin and weblogic-ejb-jar.xml descriptor

[Scott Ryan]

You could always try ejbgen.  I was going to build that into the  
Weblogic plugin but most people have gone to JPA instead so there was  
not much demand.


Scott Ryan
CTO Soaring Eagle L.L.C.
Denver, Co. 80129
www.soaringeagleco.com
www.theryansplace.com
(303) 263-3044
[EMAIL PROTECTED]


On Sep 4, 2007, at 9:30 AM, Brian Smith wrote:

I'm using Weblogic 9.2.  I think you're correct in that the  
weblogic plugin

only works for versions 8.x and earlier.   I haven't found any great
solutions for this hurdle yet.

On 8/31/07, Scott Ryan [EMAIL PROTECTED] wrote:


What version of Weblogic are you using?  You can use the weblogic tag
to generate the XML files  but as far as I know xdoclet can only
generate xml files for 8.x and prior.  9.x and 10.x are not supported
but then maybe you should be using JPA, EJB 3.0 or Hibernate by then.

Scott Ryan
CTO Soaring Eagle L.L.C.
Denver, Co. 80129
www.soaringeagleco.com
www.theryansplace.com
(303) 263-3044
[EMAIL PROTECTED]


On Aug 31, 2007, at 9:34 AM, Brian Smith wrote:


I'm working on a simple HelloWorldEJB stateless session bean that I
want to
run in Weblogic.  I'm using the xdoclet plugin and xdoclet is  
able to

generate the home/remote classes.  Should xdoclet be able to
generate the
weblogic-ejb-jar.xml descriptor?  If so, how do I do this?  Is  
there a

special tag in the EJB source code or is there something in the pom
I need
to specify?

I'm guessing this a task of xdoclet instead of maven but I'm not
sure.  Any
input would be appreciated.

Thanks,
Brian

xdoclet plugin and weblogic-ejb-jar.xml descriptor

[Brian Smith]

I'm working on a simple HelloWorldEJB stateless session bean that I want to
run in Weblogic.  I'm using the xdoclet plugin and xdoclet is able to
generate the home/remote classes.  Should xdoclet be able to generate the
weblogic-ejb-jar.xml descriptor?  If so, how do I do this?  Is there a
special tag in the EJB source code or is there something in the pom I need
to specify?

I'm guessing this a task of xdoclet instead of maven but I'm not sure.  Any
input would be appreciated.

Thanks,
Brian

Re: xdoclet plugin and weblogic-ejb-jar.xml descriptor

[Scott Ryan]

What version of Weblogic are you using?  You can use the weblogic tag  
to generate the XML files  but as far as I know xdoclet can only  
generate xml files for 8.x and prior.  9.x and 10.x are not supported  
but then maybe you should be using JPA, EJB 3.0 or Hibernate by then.


Scott Ryan
CTO Soaring Eagle L.L.C.
Denver, Co. 80129
www.soaringeagleco.com
www.theryansplace.com
(303) 263-3044
[EMAIL PROTECTED]


On Aug 31, 2007, at 9:34 AM, Brian Smith wrote:

I'm working on a simple HelloWorldEJB stateless session bean that I  
want to

run in Weblogic.  I'm using the xdoclet plugin and xdoclet is able to
generate the home/remote classes.  Should xdoclet be able to  
generate the

weblogic-ejb-jar.xml descriptor?  If so, how do I do this?  Is there a
special tag in the EJB source code or is there something in the pom  
I need

to specify?

I'm guessing this a task of xdoclet instead of maven but I'm not  
sure.  Any

input would be appreciated.

Thanks,
Brian

m2: How to include jars in classpath of xdoclet plugin definition?

[Joaquim Oliveira]

Hi all,

I cannot generate xdoclet from my EJB classes because my classes extend 
one class from an external jar, that needs to be in classpath when the 
ejbdoclet task is defined. How do I do this in the m2 xdoclet plugin 
configuration?


Here is my actual plugin configuration:

   plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdxdoclet-maven-plugin/artifactId
   executions
 execution
   phasegenerate-sources/phase
   goals
 goalxdoclet/goal
   /goals
   configuration
 tasks
   ejbdoclet 
destDir=${project.build.directory}/generated-sources/xdoclet 
ejbSpec=2.1 verbose=true force=true
 fileset dir=${basedir}/src/java

   include name=**/*Bean.java/include

 /fileset
 homeinterface/
 remoteinterface/
 localhomeinterface/
 localinterface/
 deploymentdescriptor 
destDir=${project.build.outputDirectory}/META-INF/

   /ejbdoclet
 /tasks
   /configuration
 /execution
   /executions
   /plugin

Thanks for your help,
--
--


   Joaquim Oliveira, MSc


 Analista de Sistemas



Fone: +55 (85) 3216.7971
Fax: +55 (85) 3216.7864
Skype: joaquim.oliveira


   ISO 9001 : 2000 - CMMI3




   www.atlantico.com.br http://www.atlantico.com.br


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Xdoclet plugin and multi module projects

[Eric Helfrich]

I realize the suggestion was meant to be helpful -- I think it has to do
with properties being immutable in ant and xdoclet1 being dependent on ant.
I am working with a substantial base of code and to attempt to reorg it
efficiently at this point would be difficult.  XD2 doesn't rely on ant --
but I haven't been successful in getting it set up.  I may put a bit more
effort into it now.  In the meantime another solution would be to call out
to an ant task using ant run and have that task run in its own process.
That is my fallback if xd2 isn't ready yet.





On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:


The suggestion was not as what is best, but rather what is possible right
now as I have also encountered the same issue you where facing. Maybe XD2
fixes this?



On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:

 I don't think that putting everything that gets xdocleted in a common
jar
 is
 an ideal solution --  one of the reasons for breaking you code up into
 projects is to separate functionality -- and one of the reasons to use
 Maven
 is to support that flexibility -- not limit it.  Thanks for the
suggestion
 though.

 On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
 
  Why, the ejbs will be in the common-jar and they can be added the same
  way.
 
  On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
  
   Yes it would work -- and is probably better from a resource point of
  view
   anyway.  On the other hand, that won't work for the ejbdoclet
issues.
  
   On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
   
Just add a common jar as the 1st module, and add that jar to your
  legacy
code. Would that work?
   
   
   
On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:

 that would work -- except I am pulling in a legacy build system
 here
 and would rather not have to start moving code around at that
 level


 On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
  I use hibernate doclet, and it acts the same for me.
  I just have my 1st module is my common-jar that gets added to
 all
  my
 modules
  anyways. Works fine even though it is strange...
 
 
  On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
  
   Has anyone been able to get this to work
correctly?  Hibernate
doclet
   and ejbdoclet do not work correctly -- ejb doclet generates
 all
files
   in the generated sources directory of the first project it
 runs.
   Hibernate doclet does not seem to find the source files at
all
   when
   run from a parent project which defines the plugin - -but
 works
   fine
   if generate-sources is run on the sub project.  Any ideas?
  
  
   
 -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  ---
  Thanks,
  Mick Knutson
 
  http://www.baselogic.com
  http://www.blincmagazine.com
  http://www.djmick.com
  http://www. . /djmick_dot_com
  http://www.thumpradio.com
  ---
 


  -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   
   
--
---
Thanks,
Mick Knutson
   
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www. . /djmick_dot_com
http://www.thumpradio.com
---
   
  
 
 
 
  --
  ---
  Thanks,
  Mick Knutson
 
  http://www.baselogic.com
  http://www.blincmagazine.com
  http://www.djmick.com
  http://www. . /djmick_dot_com
  http://www.thumpradio.com
  ---
 




--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www. . /djmick_dot_com
http://www.thumpradio.com
---

Xdoclet plugin and multi module projects

[Eric Helfrich]

Has anyone been able to get this to work correctly?  Hibernate doclet
and ejbdoclet do not work correctly -- ejb doclet generates all files
in the generated sources directory of the first project it runs.
Hibernate doclet does not seem to find the source files at all when
run from a parent project which defines the plugin - -but works fine
if generate-sources is run on the sub project.  Any ideas?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Xdoclet plugin and multi module projects

[Mick Knutson]

I use hibernate doclet, and it acts the same for me.
I just have my 1st module is my common-jar that gets added to all my modules
anyways. Works fine even though it is strange...


On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:


Has anyone been able to get this to work correctly?  Hibernate doclet
and ejbdoclet do not work correctly -- ejb doclet generates all files
in the generated sources directory of the first project it runs.
Hibernate doclet does not seem to find the source files at all when
run from a parent project which defines the plugin - -but works fine
if generate-sources is run on the sub project.  Any ideas?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---

Re: Xdoclet plugin and multi module projects

[Eric Helfrich]

that would work -- except I am pulling in a legacy build system here
and would rather not have to start moving code around at that level


On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:

I use hibernate doclet, and it acts the same for me.
I just have my 1st module is my common-jar that gets added to all my modules
anyways. Works fine even though it is strange...


On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:

 Has anyone been able to get this to work correctly?  Hibernate doclet
 and ejbdoclet do not work correctly -- ejb doclet generates all files
 in the generated sources directory of the first project it runs.
 Hibernate doclet does not seem to find the source files at all when
 run from a parent project which defines the plugin - -but works fine
 if generate-sources is run on the sub project.  Any ideas?

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Xdoclet plugin and multi module projects

[Mick Knutson]

Just add a common jar as the 1st module, and add that jar to your legacy
code. Would that work?



On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:


that would work -- except I am pulling in a legacy build system here
and would rather not have to start moving code around at that level


On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
 I use hibernate doclet, and it acts the same for me.
 I just have my 1st module is my common-jar that gets added to all my
modules
 anyways. Works fine even though it is strange...


 On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
 
  Has anyone been able to get this to work correctly?  Hibernate doclet
  and ejbdoclet do not work correctly -- ejb doclet generates all files
  in the generated sources directory of the first project it runs.
  Hibernate doclet does not seem to find the source files at all when
  run from a parent project which defines the plugin - -but works fine
  if generate-sources is run on the sub project.  Any ideas?
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 ---
 Thanks,
 Mick Knutson

 http://www.baselogic.com
 http://www.blincmagazine.com
 http://www.djmick.com
 http://www.myspace.com/djmick_dot_com
 http://www.thumpradio.com
 ---


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---

Re: Xdoclet plugin and multi module projects

[Eric Helfrich]

Yes it would work -- and is probably better from a resource point of view
anyway.  On the other hand, that won't work for the ejbdoclet issues.

On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:


Just add a common jar as the 1st module, and add that jar to your legacy
code. Would that work?



On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:

 that would work -- except I am pulling in a legacy build system here
 and would rather not have to start moving code around at that level


 On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
  I use hibernate doclet, and it acts the same for me.
  I just have my 1st module is my common-jar that gets added to all my
 modules
  anyways. Works fine even though it is strange...
 
 
  On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
  
   Has anyone been able to get this to work correctly?  Hibernate
doclet
   and ejbdoclet do not work correctly -- ejb doclet generates all
files
   in the generated sources directory of the first project it runs.
   Hibernate doclet does not seem to find the source files at all when
   run from a parent project which defines the plugin - -but works fine
   if generate-sources is run on the sub project.  Any ideas?
  
  
-
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  ---
  Thanks,
  Mick Knutson
 
  http://www.baselogic.com
  http://www.blincmagazine.com
  http://www.djmick.com
  http://www.myspace.com/djmick_dot_com
  http://www.thumpradio.com
  ---
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---

Re: Xdoclet plugin and multi module projects

[Mick Knutson]

Why, the ejbs will be in the common-jar and they can be added the same way.

On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:


Yes it would work -- and is probably better from a resource point of view
anyway.  On the other hand, that won't work for the ejbdoclet issues.

On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:

 Just add a common jar as the 1st module, and add that jar to your legacy
 code. Would that work?



 On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
 
  that would work -- except I am pulling in a legacy build system here
  and would rather not have to start moving code around at that level
 
 
  On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
   I use hibernate doclet, and it acts the same for me.
   I just have my 1st module is my common-jar that gets added to all my
  modules
   anyways. Works fine even though it is strange...
  
  
   On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
   
Has anyone been able to get this to work correctly?  Hibernate
 doclet
and ejbdoclet do not work correctly -- ejb doclet generates all
 files
in the generated sources directory of the first project it runs.
Hibernate doclet does not seem to find the source files at all
when
run from a parent project which defines the plugin - -but works
fine
if generate-sources is run on the sub project.  Any ideas?
   
   
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
   --
   ---
   Thanks,
   Mick Knutson
  
   http://www.baselogic.com
   http://www.blincmagazine.com
   http://www.djmick.com
   http://www.myspace.com/djmick_dot_com
   http://www.thumpradio.com
   ---
  
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 ---
 Thanks,
 Mick Knutson

 http://www.baselogic.com
 http://www.blincmagazine.com
 http://www.djmick.com
 http://www.myspace.com/djmick_dot_com
 http://www.thumpradio.com
 ---






--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---

Re: Xdoclet plugin and multi module projects

[Eric Helfrich]

I don't think that putting everything that gets xdocleted in a common jar is
an ideal solution --  one of the reasons for breaking you code up into
projects is to separate functionality -- and one of the reasons to use Maven
is to support that flexibility -- not limit it.  Thanks for the suggestion
though.

On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:


Why, the ejbs will be in the common-jar and they can be added the same
way.

On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:

 Yes it would work -- and is probably better from a resource point of
view
 anyway.  On the other hand, that won't work for the ejbdoclet issues.

 On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
 
  Just add a common jar as the 1st module, and add that jar to your
legacy
  code. Would that work?
 
 
 
  On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
  
   that would work -- except I am pulling in a legacy build system here
   and would rather not have to start moving code around at that level
  
  
   On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
I use hibernate doclet, and it acts the same for me.
I just have my 1st module is my common-jar that gets added to all
my
   modules
anyways. Works fine even though it is strange...
   
   
On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:

 Has anyone been able to get this to work correctly?  Hibernate
  doclet
 and ejbdoclet do not work correctly -- ejb doclet generates all
  files
 in the generated sources directory of the first project it runs.
 Hibernate doclet does not seem to find the source files at all
 when
 run from a parent project which defines the plugin - -but works
 fine
 if generate-sources is run on the sub project.  Any ideas?


  -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


   
   
--
---
Thanks,
Mick Knutson
   
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---
   
  
  
-
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 
 
  --
  ---
  Thanks,
  Mick Knutson
 
  http://www.baselogic.com
  http://www.blincmagazine.com
  http://www.djmick.com
  http://www.myspace.com/djmick_dot_com
  http://www.thumpradio.com
  ---
 




--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---

Re: Xdoclet plugin and multi module projects

[Mick Knutson]

The suggestion was not as what is best, but rather what is possible right
now as I have also encountered the same issue you where facing. Maybe XD2
fixes this?



On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:


I don't think that putting everything that gets xdocleted in a common jar
is
an ideal solution --  one of the reasons for breaking you code up into
projects is to separate functionality -- and one of the reasons to use
Maven
is to support that flexibility -- not limit it.  Thanks for the suggestion
though.

On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:

 Why, the ejbs will be in the common-jar and they can be added the same
 way.

 On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
 
  Yes it would work -- and is probably better from a resource point of
 view
  anyway.  On the other hand, that won't work for the ejbdoclet issues.
 
  On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
  
   Just add a common jar as the 1st module, and add that jar to your
 legacy
   code. Would that work?
  
  
  
   On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
   
that would work -- except I am pulling in a legacy build system
here
and would rather not have to start moving code around at that
level
   
   
On 2/16/07, Mick Knutson [EMAIL PROTECTED] wrote:
 I use hibernate doclet, and it acts the same for me.
 I just have my 1st module is my common-jar that gets added to
all
 my
modules
 anyways. Works fine even though it is strange...


 On 2/16/07, Eric Helfrich [EMAIL PROTECTED] wrote:
 
  Has anyone been able to get this to work correctly?  Hibernate
   doclet
  and ejbdoclet do not work correctly -- ejb doclet generates
all
   files
  in the generated sources directory of the first project it
runs.
  Hibernate doclet does not seem to find the source files at all
  when
  run from a parent project which defines the plugin - -but
works
  fine
  if generate-sources is run on the sub project.  Any ideas?
 
 
  
-
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 ---
 Thanks,
 Mick Knutson

 http://www.baselogic.com
 http://www.blincmagazine.com
 http://www.djmick.com
 http://www.myspace.com/djmick_dot_com
 http://www.thumpradio.com
 ---

   
   
 -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   
   
  
  
   --
   ---
   Thanks,
   Mick Knutson
  
   http://www.baselogic.com
   http://www.blincmagazine.com
   http://www.djmick.com
   http://www.myspace.com/djmick_dot_com
   http://www.thumpradio.com
   ---
  
 



 --
 ---
 Thanks,
 Mick Knutson

 http://www.baselogic.com
 http://www.blincmagazine.com
 http://www.djmick.com
 http://www.myspace.com/djmick_dot_com
 http://www.thumpradio.com
 ---






--
---
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/djmick_dot_com
http://www.thumpradio.com
---

xdoclet plugin makes eclipse:eclipse fail

[nicolas de loof]

Hello,

I'm using the xdoclet plugin in maven2 for jspdoclets.
My webapp depends on another module (persistence).

When the xdoclet plugin is commented, maven eclipse:eclipse works fine.
When the xdoclet plugin used, maven eclipse:eclipse requires the
persistence.jar to be in repository.

A new  developer on the project has to build the persitence artifact before
beeing able to configure eclipse. As there may be bugs in the current CVS,
he cannot get the project in eclipse and solve any issue !

Is this a known limitation ?

new configuration phase ? (was: xdoclet plugin makes eclipse:eclipse fail)

[nicolas de loof]

I solved this by setting xdoclet to run under process-resources phase and
not generate-resource, as the eclispe:eclispe goal is attached to it.

Is there some plan to add native support in maven for environment
configuration, without any requirement for a build phase ?
Why should the eclispe plugin handle generation (or copy from a POM CDATA)
of the .checkstyle ? Cannot the checkstyle plugin generate it from maven
configuration ?

What about a configure phase for configuring the developer environment ?
Every maven plugin could handle the target environment if it also has
support as a IDE plugin.

example :

profille
  ideclipse/id
  plugins
 plugin
 artifactIdmaven-eclipse-plugin/artifactId
 execution
phaseconfigure/phase
goaleclipsegoal
 /execution
 /plugin
 plugin
 artifactIdmaven-checkstyle-plugin/artifactId
 execution
phaseconfigure/phase
goaleclipsegoal
 /execution
 /plugin
  /plugins
profille





2007/1/26, nicolas de loof [EMAIL PROTECTED]:


Hello,

I'm using the xdoclet plugin in maven2 for jspdoclets.
My webapp depends on another module (persistence).

When the xdoclet plugin is commented, maven eclipse:eclipse works fine.
When the xdoclet plugin used, maven eclipse:eclipse requires the
persistence.jar to be in repository.

A new  developer on the project has to build the persitence artifact
before beeing able to configure eclipse. As there may be bugs in the current
CVS, he cannot get the project in eclipse and solve any issue !

Is this a known limitation ?

Xdoclet Plugin

[Yves Van Steen]

Hey,

 

Little help needed with xdoclet plugin.

  

1)hibernatecf doesn’t add the mappingsfiles to the configuration file.

The mappings files are in the resource folder. Why?

2)The schemaexport tag doesn’t seem to work. Normal ?

3)How can I execute the generated sql file on my database?

  

configuration

  tasks

mkdir
dir=${project.build.directory}/generated-sources/hibernate/cfg /

  

hibernatedoclet 

 
destDir=${project.build.directory}/generated-sources/hibernate/cfg

  fileset dir=src/main/resources includes=**/*.hbm.xml
/

  hibernatecfg

version=3.0

dialect=org.hibernate.dialect.MySQLDialect

driver=com.mysql.jdbc.Driver

jdbcUrl=${db.url}

username=${db.username}

password=${db.password}



  /hibernatecfg

  schemaexport

  quiet=yes text=true drop=false delimiter=;

 
output=${project.build.directory}/generated-sources/installation.sql

  fileset dir=src/main/resources
includes=**/*.hbm.xml/

/schemaexport

/hibernatedoclet

  /tasks

/configuration


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.408 / Virus Database: 268.13.5/483 - Release Date: 18/10/2006
 

Null Pointer Exception when compiling with the maven-xdoclet-plugin

[Jeffrey R. Phillips]

I am using Maven 2.0.4.

This is my POM file and below that is the output from running mvn
install

 

Any help would be greatly appreciated.

 

?xml version=1.0 encoding=UTF-8?

 

 

project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;

xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;

modelVersion4.0.0/modelVersion

groupIdgestalt-search/groupId

artifactIdgestalt-search-web/artifactId

packagingwar/packaging

version1.0.5-SNAPSHOT/version

nameGestalt Search WebApp/name

urlhttp://www.gestalt-llc.com/url

scm

 
connectionscm:svn:https://www.giglite.org/svn/gestalt-search-web/conn
ection

 
developerConnectionscm:svn:https://www.giglite.org/svn/gestalt-search-
web/developerConnection

/scm

dependencies

dependency

groupIdgestalt-search/groupId

artifactIdgestalt-search-lib/artifactId

version1.0.5-SNAPSHOT/version

scopecompile/scope

/dependency

dependency

groupIdlucene/groupId

artifactIdlucene/artifactId

version1.4.3/version

scopecompile/scope

/dependency

dependency

groupIdrome/groupId

artifactIdrome/artifactId

version0.8/version

scopecompile/scope

/dependency

dependency

groupIdjdom/groupId

artifactIdjdom/artifactId

version1.0/version

scopecompile/scope

/dependency

dependency

groupIdcommons-logging/groupId

artifactIdcommons-logging/artifactId

version1.0.4/version

scopecompile/scope

/dependency

dependency

groupIdlog4j/groupId

artifactIdlog4j/artifactId

version1.2.13/version

scopecompile/scope

/dependency

dependency

groupIdservletapi/groupId

artifactIdservletapi/artifactId

version2.3/version

/dependency

 

!-- XDoclet dependencies --

dependency

groupIdxdoclet/groupId

artifactIdxdoclet/artifactId

version1.2/version

/dependency

dependency

groupIdxdoclet/groupId

artifactIdxdoclet-web-module/artifactId

version1.2/version

/dependency

dependency

groupIdxdoclet/groupId

artifactIdxjavadoc/artifactId

version1.0.2/version

/dependency

dependency

groupIdxdoclet/groupId

artifactIdmaven-xdoclet-plugin/artifactId

version1.2/version

typeplugin/type

/dependency

/dependencies

!-- Repository Conventions --

repositories

repository

idMaven Snapshots/id

nameMojo Sandbox/name

urlhttp://snapshots.maven.codehaus.org/maven2//url

snapshots

enabledtrue/enabled

/snapshots

releases

enabledfalse/enabled

/releases

/repository

repository

idIbiblio-Maven2-Repository/id

nameIbiblio Maven2 Repository/name

urlhttp://www.ibiblio.org/maven2/url

/repository

/repositories



!-- Plugin Repository Conventions --

pluginRepositories

pluginRepository

idMaven Snapshots/id

urlhttp://snapshots.maven.codehaus.org/maven2//url

snapshots

enabledtrue/enabled

/snapshots

releases

enabledfalse/enabled

/releases

/pluginRepository

pluginRepository

idibiblio/id

urlhttp://www.ibiblio.org/maven2/url

/pluginRepository

/pluginRepositories



build

sourceDirectory./src/java/sourceDirectory

plugins

plugin

groupIdorg.codehaus.mojo/groupId

artifactIdtomcat-maven-plugin/artifactId

version1.0-SNAPSHOT/version

/plugin

   plugin

groupIdxdoclet/groupId

artifactIdmaven-xdoclet-plugin/artifactId

version1.2/version

/plugin

/plugins

/build

/project

 

 

Below is the output of running mvn install.  I keep getting a null
pointer exception.  Does anyone know how to get rid of that exception?

 

[INFO] Scanning for projects...

[INFO]



[INFO] Building Gestalt Search WebApp

[INFO]task-segment: [install]

[INFO]



[INFO] artifact org.apache.maven.plugins:maven-resources-plugin

XDoclet problem using the Maven2 xdoclet plugin

[Morgovsky, Alexander \(US - Glen Mills\)]

Hi.  I try to generate the XDoclet artifacts using the following
definition.  However, nothing gets produced in the target in
generated-souces/xdoclet.  In fact, no artificats anywhere are produced
when I call mvn generate-sources.  May someone please assist me in this,
as I have searched this forum and unfortunately I could not solve this
problem?  Please help if you may.  Thank you in advance.

plugin
  artifactIdxdoclet-maven-plugin/artifactId
  groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-2/version
  executions
execution
  phasegenerate-sources/phase
  goals
goalxdoclet/goal
  /goals
  configuration
tasks
ejbdoclet
destdir=${project.build.directory}/generated-sources/xdoclet
deploymentdescriptor
destDir=${project.build.outputDirectory}/META-INF/
fileset dir=${basedir}/src/java
includes=**/ejb/**/*.java /
weblogic
version=8.1
createtables=Disabled
validateXML=true
destDir=${project.build.outputDirectory}/META-INF/
  /ejbdoclet
/tasks
  /configuration
/execution
  /executions
/plugin 


This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited. [v.E.1]

Re: XDoclet problem using the Maven2 xdoclet plugin

[Rémy Sanlaville]

It seems that the XDoclet plugin does not work very welll.
One solution is to use the antrun plugin with an ejbdoclet task

See
http://www.nabble.com/-M2--Struts-and-XDoclet-tf1775233.html#a4832525
http://www.nabble.com/maven2---xdoclet-plugin-and-strutsconfigxml-tf2270128.html#a6363580
http://www.nabble.com/-M2--maven.plugin.classpath-tf2292286.html#a6366996

Rémy

2006/10/7, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED]:


Hi.  I try to generate the XDoclet artifacts using the following
definition.  However, nothing gets produced in the target in
generated-souces/xdoclet.  In fact, no artificats anywhere are produced
when I call mvn generate-sources.  May someone please assist me in this,
as I have searched this forum and unfortunately I could not solve this
problem?  Please help if you may.  Thank you in advance.

plugin
  artifactIdxdoclet-maven-plugin/artifactId
  groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-2/version
  executions
execution
  phasegenerate-sources/phase
  goals
goalxdoclet/goal
  /goals
  configuration
tasks
ejbdoclet
destdir=${project.build.directory}/generated-sources/xdoclet
deploymentdescriptor
destDir=${project.build.outputDirectory}/META-INF/
fileset dir=${basedir}/src/java
includes=**/ejb/**/*.java /
weblogic
version=8.1
createtables=Disabled
validateXML=true
destDir=${project.build.outputDirectory}/META-INF/
  /ejbdoclet
/tasks
  /configuration
/execution
  /executions
/plugin


This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  If
you are not the intended recipient, you should delete this message.


Any disclosure, copying, or distribution of this message, or the taking of
any action based on it, is strictly prohibited. [v.E.1]

Re: maven2 / xdoclet plugin and strutsconfigxml

[Rémy Sanlaville]

Hi Marco,

I don't know why, but It seems that the xdoclet plugin does not work very
well
for struts. I send a post on 2006-06-12 19:06 related to xdoclet and struts
http://www.nabble.com/-M2--Struts-and-XDoclet-tf1775233.html#a4832525

You will find my pom in the post.
It still found any solution for my problem. If you have an idea...

Hope this helps,

Rémy

Re: maven2 / xdoclet plugin and strutsconfigxml

[Marco Mistroni]

Hello Remy,
 yes i actually managed to find a workaround
instead of using xdoclet plugin, i just created an ant task and invoked it
from maven .
here's my pom, should sort out also your problem  :)

first off, here are dependencies you need

dependency
   artifactIdxdoclet-ejb-module/artifactId
   groupIdxdoclet/groupId
   version1.2.3/version
   typejar/type
   /dependency
   dependency
   artifactIdxdoclet-apache-module/artifactId
   groupIdxdoclet/groupId
   version1.2.3/version
   typejar/type
   /dependency
   dependency
   artifactIdxdoclet-jboss-module/artifactId
   groupIdxdoclet/groupId
   version1.2.3/version
   typejar/type
   /dependency
   dependency
   artifactIdxdoclet-jmx-module/artifactId
   groupIdxdoclet/groupId
   version1.2.3/version
   typejar/type
   /dependency
   dependency
   artifactIdxdoclet-web-module/artifactId
   groupIdxdoclet/groupId
   version1.2.3/version
   typejar/type
   /dependency
   dependency
   artifactIdxdoclet-xdoclet-module/artifactId
   groupIdxdoclet/groupId
   version1.2.3/version
   typejar/type
   /dependency
   dependency
   groupIdxdoclet/groupId
   artifactIdxjavadoc/artifactId
   version1.1/version
   typejar/type
   /dependency

and then the plugin part
plugins
  plugin
artifactIdmaven-antrun-plugin/artifactId
version1.0/version
executions
   execution
 phasepackage/phase
 goals
   goalrun/goal
  /goals
  configuration
tasks
  taskdef name=webdoclet classname=
xdoclet.modules.web.WebDocletTask
   classpath refid=maven.dependency.classpath/
   classpath
 fileset dir=${jboss.libdir}\client
 include name=jbossall-client.jar/
 /fileset
   /classpath
  /taskdef
  webdoclet destdir=xdoclet mergedir=merge verbose=true

fileset dir=JavaSource /
deploymentdescriptor
 destDir=${project.build.outputDirectory}/META-INF
useIDs=true/
strutsconfigxml validatexml=true version=1.1/
webspherewebxml/
jbosswebxml/
  /webdoclet
/tasks
  /configuration
  /execution
/executions
  /plugin


hth, pls let me know if this still does not solve your problem

regards
marco

Re: maven2 / xdoclet plugin and strutsconfigxml

[Rémy Sanlaville]

Hello Marco,

You help me a lot, it works now, many thanks !

But I still have some questions :

(1) I tried also to use the antrun plugin without success.
I used this classpath (that works with ant).

path id =xdoclet.classpath
 fileset dir=C:/Tools/XDoclet/v1.2.3/lib
 include name=*.jar/
 /fileset
/path

taskdef
   name= webdoclet
   classname= xdoclet.modules.web.WebDocletTask
   classpathref= xdoclet.classpath
/

But if I use the maven.dependency.classpath as you, it works well !
Strange no ?!

taskdef
   name= webdoclet
   classname= xdoclet.modules.web.WebDocletTask
   classpathref= maven.dependency.classpath
/

(2) In order to don't put the xdoclet dependencies in the WEB-INF/lib, I
wanted
to use the maven.plugin.classpath (see [1]), but it seems that it does not
exist any more
   Embedded error: Reference maven.plugin.classpath not found.
It is normal ?

It is not possible also to use the scope provided because the
maven.dependency.classpath
don't take into account this scope.

(3) Why are you the packaging phase insteed of the generate-sources phase ?
execution
   phasepackage/phase

Thanks again,
Rémy

[1] http://maven.apache.org/plugins/maven-antrun-plugin/classpaths.html

Re: maven2 / xdoclet plugin and strutsconfigxml

[Marco Mistroni]

hello remy,
i'll try to answer ur questions, but i feel i m not the best guy to explain
that classpath behaviour

On 9/18/06, Rémy Sanlaville [EMAIL PROTECTED] wrote:


Hello Marco,

You help me a lot, it works now, many thanks !

But I still have some questions :

(1) I tried also to use the antrun plugin without success.
I used this classpath (that works with ant).

path id =xdoclet.classpath
  fileset dir=C:/Tools/XDoclet/v1.2.3/lib
  include name=*.jar/
  /fileset
/path

taskdef
name= webdoclet
classname= xdoclet.modules.web.WebDocletTask
classpathref= xdoclet.classpath
/

But if I use the maven.dependency.classpath as you, it works well !
Strange no ?!



Well, it would not surprise me if in your fileset
dir=C:/Tools/XDoclet/v1.2.3


/lib you are missing some jars.. cos theoretically if  in that lib
dir you have



all jars needed by xdoclet, it should have worked just fine





taskdef

name= webdoclet
classname= xdoclet.modules.web.WebDocletTask
classpathref= maven.dependency.classpath
/



this i m sure it works becaue in my dependencies there is all that xdoclet
need to run the task.
If in your lib directory you h ave all xdoclet-xxx-module.jar as well as
xjavadoc, i see no reason of why your code above hsould not work
again,, any maven expert here can condraddict and give feedback, i m no
guru...i have just learned things from trying them out (and failing :) )


(2) In order to don't put the xdoclet dependencies in the WEB-INF/lib, I

wanted
to use the maven.plugin.classpath (see [1]), but it seems that it does not
exist any more
Embedded error: Reference maven.plugin.classpath not found.
It is normal ?

It is not possible also to use the scope provided because the
maven.dependency.classpath
don't take into account this scope.



mmm, this scopes confuse me too... in your dependencies, try to put
scopeprovided/scope
this assumes that at runtime those libraries are alredy present (if i m
correct), and thus maven won't include them in yoru war (it worked for me
while building an .ear..)



(3) Why are you the packaging phase insteed of the generate-sources phase ?

execution
phasepackage/phase



ah! ignore it...i had problems wtih dependencies but it might have been
due to the fact that i had incorrect classpath
it should work also with phasegenerate-sources/phase
but i haven't triedhave no time unfortunately.  i m not using maven
at work, so i have to use it in my spare time and nowadays i have very
little spare time
you might want to try and see if you have classpath problem

hth
marco

Thanks again,

Rémy

[1] http://maven.apache.org/plugins/maven-antrun-plugin/classpaths.html

Re: maven2 / xdoclet plugin and strutsconfigxml

[Rémy Sanlaville]

Hello Marco,


(1) I tried also to use the antrun plugin without success.
 I used this classpath (that works with ant).

 path id =xdoclet.classpath
   fileset dir=C:/Tools/XDoclet/v1.2.3/lib
   include name=*.jar/
   /fileset
 /path

 taskdef
 name= webdoclet
 classname= xdoclet.modules.web.WebDocletTask
 classpathref= xdoclet.classpath
 /

 But if I use the maven.dependency.classpath as you, it works well !
 Strange no ?!


Well, it would not surprise me if in your fileset
dir=C:/Tools/XDoclet/v1.2.3

 /lib you are missing some jars.. cos theoretically if  in that lib
 dir you have

all jars needed by xdoclet, it should have worked just fine


taskdef
 name= webdoclet
 classname= xdoclet.modules.web.WebDocletTask
 classpathref= maven.dependency.classpath
 /


this i m sure it works becaue in my dependencies there is all that xdoclet
need to run the task.
If in your lib directory you h ave all xdoclet-xxx-module.jar as well as
xjavadoc, i see no reason of why your code above hsould not work
again,, any maven expert here can condraddict and give feedback, i m no
guru...i have just learned things from trying them out (and failing :) )



I think that it's not this problem because as I indicated it works with ant
so
it's why I don't understand what happen. Anyway your solution is better...


(2) In order to don't put the xdoclet dependencies in the WEB-INF/lib, I

 wanted
 to use the maven.plugin.classpath (see [1]), but it seems that it does
not
 exist any more
 Embedded error: Reference maven.plugin.classpath not found.
 It is normal ?

 It is not possible also to use the scope provided because the
 maven.dependency.classpath
 don't take into account this scope.


mmm, this scopes confuse me too... in your dependencies, try to put
scopeprovided/scope
this assumes that at runtime those libraries are alredy present (if i m
correct), and thus maven won't include them in yoru war (it worked for me
while building an .ear..)



I tried it before to wrote :

It is not possible also to use the scope provided because the
maven.dependency.classpath don't take into account this scope.

I will post a new question for this on the mailing list..

(3) Why are you the packaging phase insteed of the generate-sources phase ?

 execution
 phasepackage/phase


ah! ignore it...i had problems wtih dependencies but it might have
been
due to the fact that i had incorrect classpath
it should work also with phasegenerate-sources/phase
but i haven't triedhave no time unfortunately.  i m not using
maven
at work, so i have to use it in my spare time and nowadays i have very
little spare time
you might want to try and see if you have classpath problem



For me it works well with the generate-sources.It's why I asked you this
question
to be sure that it's what you really want to do because I think it's better
to use the
generate-sources phase.

Thanks,

Remy

Re: maven2 / xdoclet plugin and strutsconfigxml

[Marco Mistroni]

Hello Remy,
for some reasons, if i use  generated-sources as a phase, the xdoclet task
doe snot generate me anything at all!!
i think it has to do with classpath i think (any maven guru pls correct
me if i m wrong), maven.dependency.classpath works for 'package' phase but
not for 'generated-sources'...
i'll try to sort things out and post here my results

thanks again and regards
marco




On 9/18/06, Rémy Sanlaville [EMAIL PROTECTED] wrote:


Hello Marco,

 (1) I tried also to use the antrun plugin without success.
  I used this classpath (that works with ant).
 
  path id =xdoclet.classpath
fileset dir=C:/Tools/XDoclet/v1.2.3/lib
include name=*.jar/
/fileset
  /path
 
  taskdef
  name= webdoclet
  classname= xdoclet.modules.web.WebDocletTask
  classpathref= xdoclet.classpath
  /
 
  But if I use the maven.dependency.classpath as you, it works well !
  Strange no ?!


 Well, it would not surprise me if in your fileset
 dir=C:/Tools/XDoclet/v1.2.3
 
  /lib you are missing some jars.. cos theoretically if  in that
lib
  dir you have

 all jars needed by xdoclet, it should have worked just fine


 taskdef
  name= webdoclet
  classname= xdoclet.modules.web.WebDocletTask
  classpathref= maven.dependency.classpath
  /


 this i m sure it works becaue in my dependencies there is all that
xdoclet
 need to run the task.
 If in your lib directory you h ave all xdoclet-xxx-module.jar as well as
 xjavadoc, i see no reason of why your code above hsould not work
 again,, any maven expert here can condraddict and give feedback, i m no
 guru...i have just learned things from trying them out (and failing :) )


I think that it's not this problem because as I indicated it works with
ant
so
it's why I don't understand what happen. Anyway your solution is better...


(2) In order to don't put the xdoclet dependencies in the WEB-INF/lib, I
  wanted
  to use the maven.plugin.classpath (see [1]), but it seems that it does
 not
  exist any more
  Embedded error: Reference maven.plugin.classpath not found.
  It is normal ?
 
  It is not possible also to use the scope provided because the
  maven.dependency.classpath
  don't take into account this scope.


 mmm, this scopes confuse me too... in your dependencies, try to put
 scopeprovided/scope
 this assumes that at runtime those libraries are alredy present (if i m
 correct), and thus maven won't include them in yoru war (it worked for
me
 while building an .ear..)


I tried it before to wrote :
 It is not possible also to use the scope provided because the
 maven.dependency.classpath don't take into account this scope.
I will post a new question for this on the mailing list..

(3) Why are you the packaging phase insteed of the generate-sources phase
?
  execution
  phasepackage/phase


 ah! ignore it...i had problems wtih dependencies but it might have
 been
 due to the fact that i had incorrect classpath
 it should work also with phasegenerate-sources/phase
 but i haven't triedhave no time unfortunately.  i m not using
 maven
 at work, so i have to use it in my spare time and nowadays i have very
 little spare time
 you might want to try and see if you have classpath problem


For me it works well with the generate-sources.It's why I asked you this
question
to be sure that it's what you really want to do because I think it's
better
to use the
generate-sources phase.

Thanks,

Remy

Re: maven2 / xdoclet plugin and strutsconfigxml

[Rémy Sanlaville]

Hello Marco,

for some reasons, if i use  generated-sources as a phase, the xdoclet task

doe snot generate me anything at all!!
i think it has to do with classpath i think (any maven guru pls
correct
me if i m wrong), maven.dependency.classpath works for 'package' phase but
not for 'generated-sources'...
i'll try to sort things out and post here my results



For me it works well : mvn clean compile
Don't you generate a part of your code source ?

Regards,

Remy

Re: maven2 / xdoclet plugin and strutsconfigxml

[Marco Mistroni]

hello remy,
ok i'll give it another try tomorrow and see... for my uses, it's really
not important the phase as long as the files get generated ..
will let you know

thanx for ur help
regards
marco

On 9/18/06, Rémy Sanlaville [EMAIL PROTECTED] wrote:


Hello Marco,

for some reasons, if i use  generated-sources as a phase, the xdoclet task
 doe snot generate me anything at all!!
 i think it has to do with classpath i think (any maven guru pls
 correct
 me if i m wrong), maven.dependency.classpath works for 'package' phase
but
 not for 'generated-sources'...
 i'll try to sort things out and post here my results


For me it works well : mvn clean compile
Don't you generate a part of your code source ?

Regards,

Remy

maven2 / xdoclet plugin and strutsconfigxml

[Marco Mistroni]

hi all,
 i have a webapp where i want to generete the struts-config.xml

i am currently using maven2,  my action class is as follows

/**
* @struts.action name=contactForm path=/editPerson scope=request
*  validate=false input=mainMenu
*
* @struts.action-forward
*name=success
*path=viewContacts.jsp
*
* @jboss.ejb-ref-jndi
* jndi-name=ejb/ContactMaintenanceLocalHome
* ref-name=ContactMaintenance
*
*/

my pom.xml is as follows

build
sourceDirectory${basedir}\JavaSource/sourceDirectory

plugins
  plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdxdoclet-maven-plugin/artifactId
   executions
 execution
   idgenerateSources/id
   phasegenerate-sources/phase
   goals
 goalxdoclet/goal
   /goals
   configuration
 tasks
   webdoclet
   destDir=${project.build.directory}/generated-sources/xdoclet
   excludedTags=@author,@version
   fileset
   dir=${basedir}/JavaSource
   includes=**/*.java /
   strutsconfigxml validatexml=true version=1.1/
   strutsvalidationxml/
   deploymentdescriptor
   destDir=${project.build.outputDirectory}/META-INF
   useIDs=true/
   jbosswebxml/

   /webdoclet
 /tasks
/configuration
  /execution
/executions
 /plugin

i got the jbosswebxml generated successfully.. i have tagged even my forms
with @struts.form tags and struts config
get properly generated
the only problem is that i see no action-mappings for my action class...
i did a google search, was not able to find anything that could help.. is it
a bug in the struts plugin?

thanks in advance and regards
marco

Re: [Xdoclet-user] XDoclet plugin.... problem generating wsdl for ejbwebservice

[David J. M. Karlsen]

Marco Mistroni wrote:

hello all,
 i am trying to expose an EJB as a webservice in my app that is using 
Maven2


what i am trying to do is to generate sources with xdoclet, and then 
use wseedoclet to generate wsdl file

and mappings

At runtime, generation of sources works fine...
generation of ejb jar works partially fine (my ejb tobe exposed as 
webservice does not have correct endpoint)..

and wseedoclet doesnot run at all giving this error

here's my pom.xml (only relevant part)

Embedded error: Ambiguous subtask definition for logical name 
deploymentdescript
or: xdoclet.modules.ejb.dd.EjbDotXmlSubTask and 
xdoclet.modules.wsee.WebServices

XmlSubTask

see http://jira.codehaus.org/browse/MOJO-223 and vote :-)

--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: XDoclet plugin.... problem generating wsdl for ejb webservice

[David J. M. Karlsen]

Marco Mistroni wrote:

hello all,
i am trying to expose an EJB as a webservice in my app that is using 
Maven2


what i am trying to do is to generate sources with xdoclet, and then use
wseedoclet to generate wsdl file
and mappings

At runtime, generation of sources works fine...
generation of ejb jar works partially fine (my ejb tobe exposed as
webservice does not have correct endpoint)..
and wseedoclet doesnot run at all giving this error

here's my pom.xml (only relevant part)

Embedded error: Ambiguous subtask definition for logical name
deploymentdescript
or: xdoclet.modules.ejb.dd.EjbDotXmlSubTask and
xdoclet.modules.wsee.WebServices
XmlSubTask


Known bugs in xdoclet-plugin and/or xdoclet,
see http://jira.codehaus.org/browse/MOJO-223
and vote :-)


--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

XDoclet plugin.... problem generating wsdl for ejb webservice

[Marco Mistroni]

hello all,
i am trying to expose an EJB as a webservice in my app that is using Maven2

what i am trying to do is to generate sources with xdoclet, and then use
wseedoclet to generate wsdl file
and mappings

At runtime, generation of sources works fine...
generation of ejb jar works partially fine (my ejb tobe exposed as
webservice does not have correct endpoint)..
and wseedoclet doesnot run at all giving this error

here's my pom.xml (only relevant part)

Embedded error: Ambiguous subtask definition for logical name
deploymentdescript
or: xdoclet.modules.ejb.dd.EjbDotXmlSubTask and
xdoclet.modules.wsee.WebServices
XmlSubTask


plugins
 plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdxdoclet-maven-plugin/artifactId
   executions
 execution
   idgenerateSources/id
   phasegenerate-sources/phase
   goals
 goalxdoclet/goal
   /goals
   configuration
 tasks
   ejbdoclet
   destDir=${project.build.directory}/generated-sources/xdoclet
   excludedTags=@author,@version
   fileset
   dir=src/main/java
   includes=**/*Bean.java /
   service-endpoint /
   entitycmp
destDir=${project.build.directory}/generated-sources/xdoclet
/
   homeinterface destDir=${project.build.directory
}/generated-sources/xdoclet
   !-- packagesubstitution packages=session
 substituteWith=interfaces useFirst=  true/
--
   /homeinterface
   localinterface destDir=${project.build.directory
}/generated-sources/xdoclet/
   localhomeinterface destDir=${project.build.directory
}/generated-sources/xdoclet/
   remoteinterface destDir=${project.build.directory
}/generated-sources/xdoclet/
   deploymentdescriptor
   destDir=${project.build.outputDirectory
}/META-INF/
   jboss version=4.0
   destDir=${project.build.outputDirectory}/META-INF
   dataSource=java:/DefaultDS
   datasourceMapping=Hypersonic SQL
   createTable=true
   removeTable=true/
   /ejbdoclet
 /tasks
/configuration
  /execution
  execution
 idgenerateWsdl/id
 phaseprocess-classes/phase
 goals
goalxdoclet/goal
 /goals
 configuration
 tasks
   wseedoclet jaxrpcMappingFile=mappings.xml
wsdlFile=wsdl/service.wsdl
destDir=target/META-INF force=true
verbose=true
fileset dir=src includes=**/*Bean.java /
fileset dir=target includes=**/*IF.*java /
  !-- deploymentdescriptor
   configParam name=Name value=TestService /
   /deploymentdescriptor--
  jaxrpc-mapping/
  wsdl/
   /wseedoclet
  /tasks
  /configuration
  /execution

/executions
 /plugin


and here's part of my annotated ejb

/**
* @ejb.bean
*name=TranslationServiceSession
*view-type=service-endpoint
*local-jndi-name=ngen/mw/ejb/TranslationServiceSessionLocalHome
*
* @wsee.port-component name=TranslationServiceIFPort
*
* @ejb.interface service-endpoint-class=
com.waersystems.mw.webservices.TranslationServiceIF
..


the TranslationServiceIF interface gets generated properly, but the
deployment descriptor is still wrong

session 
description![CDATA[]]/description
ejb-nameTranslationServiceSession/ejb-name
ejb-classcom.mmistroni.mw.ejb.TranslationServiceSessionBean
/ejb-class
session-typeStateless/session-type
transaction-typeContainer/transaction-type

can anyone help me out?

thanx and regards
marco

New release of XDoclet plugin?

[Jörg Schaible]

Hi folks,

is there any chance of a new release of the XDocelt plugin with actualized 
versions? Especially the dep to the antrun plugin 1.0 does major grief, since 
it breaks any multi-module builds that usilize both plugins.

- Jörg

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

examples on maven xdoclet plugin

[Jagan Padmanabha Pillai -X \(jpadmana - Insight Solutions, Inc. at Cisco\)]

 
Hi 
 
Can anyone please send me some examples on using maven2-xdoclet2-plugin
for annotated beans.
 
Thanks
-Jagan
 
 

Re: examples on maven xdoclet plugin

[Wayne Fay]

This was just discussed in the last 2 days on the [mojo-dev] list.
Check the archives for the dev@mojo.codehaus.org email list -- Kostis
provided some sample code and configuration...

Wayne

On 4/14/06, Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions,
Inc. at Cisco) [EMAIL PROTECTED] wrote:

 Hi

 Can anyone please send me some examples on using maven2-xdoclet2-plugin
 for annotated beans.

 Thanks
 -Jagan

RE: examples on maven xdoclet plugin

[Jagan Padmanabha Pillai -X \(jpadmana - Insight Solutions, Inc. at Cisco\)]

Hi Wayne,

I couldn't find anything in the dev archives at,
http://archive.mojo.codehaus.org/dev/

Could you please give me more info.

Thanks
-Jagan

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 14, 2006 10:40 AM
To: Maven Users List
Subject: Re: examples on maven xdoclet plugin

This was just discussed in the last 2 days on the [mojo-dev] list.
Check the archives for the dev@mojo.codehaus.org email list -- Kostis
provided some sample code and configuration...

Wayne

On 4/14/06, Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions,
Inc. at Cisco) [EMAIL PROTECTED] wrote:

 Hi

 Can anyone please send me some examples on using 
 maven2-xdoclet2-plugin for annotated beans.

 Thanks
 -Jagan





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: examples on maven xdoclet plugin

[Wayne Fay]

Check here:
http://www.nabble.com/mojo---dev-f11981.html

Wayne


On 4/14/06, Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions,
Inc. at Cisco) [EMAIL PROTECTED] wrote:

 Hi Wayne,

 I couldn't find anything in the dev archives at,
 http://archive.mojo.codehaus.org/dev/

 Could you please give me more info.

 Thanks
 -Jagan

 -Original Message-
 From: Wayne Fay [mailto:[EMAIL PROTECTED]
 Sent: Friday, April 14, 2006 10:40 AM
 To: Maven Users List
 Subject: Re: examples on maven xdoclet plugin

 This was just discussed in the last 2 days on the [mojo-dev] list.
 Check the archives for the dev@mojo.codehaus.org email list -- Kostis
 provided some sample code and configuration...

 Wayne

 On 4/14/06, Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions,
 Inc. at Cisco) [EMAIL PROTECTED] wrote:
 
  Hi
 
  Can anyone please send me some examples on using
  maven2-xdoclet2-plugin for annotated beans.
 
  Thanks
  -Jagan
 
 
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

[M2] Xdoclet plugin and hibernate task

[Srepfler Srgjan]

Hi,
I've been trying the xdoclet plugin 1.0-alpha-2 from org.codehaus.mojo ; 
I've tried to compile some standard hibernate annotated classes from the 
appfuse project and I'm getting this error:
Below is the pom.xml, any ideas why am I getting this error message? 
Thanks in advance, keep up the good work with maven2 and does anyone 
know will there be soon a plugin for xdoclet2?


[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'xdoclet'.
[INFO] 


[INFO] Building jspArt EJB Module
[INFO]task-segment: [xdoclet:xdoclet]
[INFO] 


[WARNING]
 This artifact has been relocated to javax.sql:jdbc-stdext:2.0.

[INFO] [xdoclet:xdoclet]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
(XDocletMain.start   47  ) Running hibernate/
INFO:Some classes refer to other classes that were not found among 
the sources or on the classpath.
(Perhaps the referred class doesn't exist? Hasn't been 
generated yet?)
The referring classes do not import any fully qualified classes 
matching these classes.
However, since no packages are imported, xjavadoc has assumed 
that the referred classes

belong to the same package as the referring class. The classes are:
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Address.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Role.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\User.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\UserCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Address.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Role.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\User.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\UserCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject

[INFO] Executed tasks
[INFO] 


[INFO] BUILD SUCCESSFUL
[INFO] 


[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Nov 18 17:37:15 CET 2005
[INFO] Final Memory: 3M/7M
[INFO] 





here is my project's pom.xml:

project xmlns=http://maven.apache.org/POM/4.0.0;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;

 modelVersion4.0.0/modelVersion
 groupIdit.sigmalab.jspart/groupId
 artifactIdjspArtEjb/artifactId
 packagingejb/packaging
 version1.0-SNAPSHOT/version
 namejspArt EJB Module/name
 urlhttp://www.sigmalab.net/jspart/url
 build
   pluginManagement
 plugins
   plugin
 artifactIdxdoclet-maven-plugin/artifactId
 groupIdorg.codehaus.mojo/groupId
 version1.0-alpha-2/version
 executions
   execution
 goals
   goalxdoclet/goal
 /goals
   /execution
 /executions
 configuration
   tasks
 hibernatedoclet destdir=${basedir}/src
   !-- fileset 
dir=${basedir}/src/main/java/net/sigmalab/jspart/model 
includes=**/*.java/  --
   fileset 
dir=${basedir}/src/main/java/org/appfuse/model includes=**/*.java/

   hibernate version=3.0/
 /hibernatedoclet
   /tasks
 /configuration
   /plugin
   !-- plugin
 artifactIdmaven-antrun-plugin/artifactId
 executions
   execution
 phasegenerate-sources/phase
 configuration
   tasks
 echobu/echo
   /tasks
 /configuration
 goals
   goalrun/goal
 /goals
   /execution
 /executions
   /plugin --
   plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-compiler-plugin/artifactId
  configuration
  source1.5/source
  target1.5/target

RE: [M2] Xdoclet plugin and hibernate task

[Allison, Bob]

A couple questions:

Where does BaseObject come from?  According to the error message, it
is not in the source tree and not on the class path.  If should be in
the source tree, there is something wrong with that source file.  If it
comes from Hibernate, you need to import the class (NOT the package) for
XDoclet to work correctly.

Do these four classes compile correctly if you skip running XDoclet?  To
do this, comment out the XDoclet stuff from your pom.xml and try mvn
compile again.  If they do not compile for reasons other than missing
classes that XDoclet would be providing, you need to fix these errors
before XDoclet will work without problems.  There are a number of
compile problems that XDoclet won't mind but there are some (like
unknown classes) which prevent XDoclet from being able to work properly.

-Original Message-
From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 11:42
To: Maven Users List
Subject: [M2] Xdoclet plugin and hibernate task


Hi,
I've been trying the xdoclet plugin 1.0-alpha-2 from org.codehaus.mojo ;

I've tried to compile some standard hibernate annotated classes from the

appfuse project and I'm getting this error:
Below is the pom.xml, any ideas why am I getting this error message? 
Thanks in advance, keep up the good work with maven2 and does anyone 
know will there be soon a plugin for xdoclet2?

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'xdoclet'.
[INFO] 


[INFO] Building jspArt EJB Module
[INFO]task-segment: [xdoclet:xdoclet]
[INFO] 


[WARNING]
  This artifact has been relocated to javax.sql:jdbc-stdext:2.0.

[INFO] [xdoclet:xdoclet]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
(XDocletMain.start   47  ) Running hibernate/
INFO:Some classes refer to other classes that were not found among 
the sources or on the classpath.
 (Perhaps the referred class doesn't exist? Hasn't been 
generated yet?)
 The referring classes do not import any fully qualified classes

matching these classes.
 However, since no packages are imported, xjavadoc has assumed 
that the referred classes
 belong to the same package as the referring class. The classes
are:
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Add
ress.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Rol
e.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
r.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
rCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Add
ress.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Rol
e.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
r.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
rCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
[INFO] Executed tasks
[INFO] 


[INFO] BUILD SUCCESSFUL
[INFO] 


[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Nov 18 17:37:15 CET 2005
[INFO] Final Memory: 3M/7M
[INFO] 





here is my project's pom.xml:

project xmlns=http://maven.apache.org/POM/4.0.0;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;
  modelVersion4.0.0/modelVersion
  groupIdit.sigmalab.jspart/groupId
  artifactIdjspArtEjb/artifactId
  packagingejb/packaging
  version1.0-SNAPSHOT/version
  namejspArt EJB Module/name
  urlhttp://www.sigmalab.net/jspart/url
  build
pluginManagement
  plugins
plugin
  artifactIdxdoclet-maven-plugin/artifactId
  groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-2/version
  executions
execution
  goals
goalxdoclet/goal
  /goals
/execution

Re: [M2] Xdoclet plugin and hibernate task

[Srepfler Srgjan]

BaseObject is in the same folter as the model objects.

Allison, Bob wrote:


A couple questions:

Where does BaseObject come from?  According to the error message, it
is not in the source tree and not on the class path.  If should be in
the source tree, there is something wrong with that source file.  If it
comes from Hibernate, you need to import the class (NOT the package) for
XDoclet to work correctly.

Do these four classes compile correctly if you skip running XDoclet?  To
do this, comment out the XDoclet stuff from your pom.xml and try mvn
compile again.  If they do not compile for reasons other than missing
classes that XDoclet would be providing, you need to fix these errors
before XDoclet will work without problems.  There are a number of
compile problems that XDoclet won't mind but there are some (like
unknown classes) which prevent XDoclet from being able to work properly.

-Original Message-
From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 11:42

To: Maven Users List
Subject: [M2] Xdoclet plugin and hibernate task


Hi,
I've been trying the xdoclet plugin 1.0-alpha-2 from org.codehaus.mojo ;

I've tried to compile some standard hibernate annotated classes from the

appfuse project and I'm getting this error:
Below is the pom.xml, any ideas why am I getting this error message? 
Thanks in advance, keep up the good work with maven2 and does anyone 
know will there be soon a plugin for xdoclet2?


[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'xdoclet'.
[INFO] 



[INFO] Building jspArt EJB Module
[INFO]task-segment: [xdoclet:xdoclet]
[INFO] 



[WARNING]
 This artifact has been relocated to javax.sql:jdbc-stdext:2.0.

[INFO] [xdoclet:xdoclet]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
(XDocletMain.start   47  ) Running hibernate/
INFO:Some classes refer to other classes that were not found among 
the sources or on the classpath.
(Perhaps the referred class doesn't exist? Hasn't been 
generated yet?)

The referring classes do not import any fully qualified classes

matching these classes.
However, since no packages are imported, xjavadoc has assumed 
that the referred classes

belong to the same package as the referring class. The classes
are:
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Add
ress.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Rol
e.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
r.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
rCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Add
ress.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Rol
e.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
r.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Use
rCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject

[INFO] Executed tasks
[INFO] 



[INFO] BUILD SUCCESSFUL
[INFO] 



[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Nov 18 17:37:15 CET 2005
[INFO] Final Memory: 3M/7M
[INFO] 






here is my project's pom.xml:

project xmlns=http://maven.apache.org/POM/4.0.0;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;

 modelVersion4.0.0/modelVersion
 groupIdit.sigmalab.jspart/groupId
 artifactIdjspArtEjb/artifactId
 packagingejb/packaging
 version1.0-SNAPSHOT/version
 namejspArt EJB Module/name
 urlhttp://www.sigmalab.net/jspart/url
 build
   pluginManagement
 plugins
   plugin
 artifactIdxdoclet-maven-plugin/artifactId
 groupIdorg.codehaus.mojo/groupId
 version1.0-alpha-2/version
 executions
   execution
 goals

Re: [M2] Xdoclet plugin and hibernate task

[Srepfler Srgjan]

The classes compile just fine, here's a a class and the baseobject;

User.java:

package org.appfuse.model;

import java.io.Serializable;
import java.util.HashSet;
import java.util.Set;

import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;
import org.apache.commons.lang.builder.ToStringBuilder;
import org.apache.commons.lang.builder.ToStringStyle;

/**
* User class
*
* This class is used to generate the Struts Validator Form as well as the
* Hibernate mapping file.
*
* pa href=User.java.htmliView Source/i/a/p
*
* @author a href=mailto:[EMAIL PROTECTED]Matt Raible/a
* Updated by Dan Kibler ([EMAIL PROTECTED])
*
* @struts.form include-all=true extends=BaseForm
* @hibernate.class table=app_user
*/
public class User extends BaseObject implements Serializable {
   private static final long serialVersionUID = 3832626162173359411L;
   protected String username;
   protected String password;
   protected String confirmPassword;
   protected String firstName;
   protected String lastName;
   protected Address address = new Address();
   protected String phoneNumber;
   protected String email;
   protected String website;
   protected String passwordHint;
   protected Integer version;
   protected Set roles = new HashSet();
   protected Boolean enabled;

   /**
* Returns the username.
*
* @return String
*
* @struts.validator type=required
* @hibernate.id column=username length=20 
generator-class=assigned

*   unsaved-value=version
*/
   public String getUsername() {
   return username;
   }

   /**
* Returns the password.
* @return String
*
* @struts.validator type=required
* @struts.validator type=twofields msgkey=errors.twofields
* @struts.validator-args arg1resource=userForm.password
* @struts.validator-args arg1resource=userForm.confirmPassword
* @struts.validator-var name=secondProperty value=confirmPassword
* @hibernate.property column=password not-null=true
*/
   public String getPassword() {
   return password;
   }

   /**
* Returns the confirmedPassword.
* @return String
*
* @struts.validator type=required
*/
   public String getConfirmPassword() {
   return confirmPassword;
   }

   /**
* Returns the firstName.
* @return String
*
* @struts.validator type=required
* @hibernate.property column=first_name not-null=true length=50
*/
   public String getFirstName() {
   return firstName;
   }

   /**
* Returns the lastName.
* @return String
*
* @struts.validator type=required
* @hibernate.property column=last_name not-null=true length=50
*/
   public String getLastName() {
   return lastName;
   }

   public String getFullName() {
   return firstName + ' ' + lastName;
   }

   /**
* Returns the address.
*
* @return Address
*
* @hibernate.component
*/
   public Address getAddress() {
   return address;
   }

   /**
* Returns the email.  This is an optional field for specifying a
* different e-mail than the username.
*
* @return String
*
* @struts.validator type=required
* @struts.validator type=email
* @hibernate.property name=email not-null=true unique=true
*/
   public String getEmail() {
   return email;
   }

   /**
* Returns the phoneNumber.
*
* @return String
*
* @struts.validator type=mask msgkey=errors.phone
* @struts.validator-var name=mask value=${phone}
* @hibernate.property column=phone_number not-null=false
*/
   public String getPhoneNumber() {
   return phoneNumber;
   }

   /**
* Returns the website.
*
* @return String
*
* @struts.validator type=required
* @hibernate.property column=website not-null=false
*/
   public String getWebsite() {
   return website;
   }

   /**
* Returns the passwordHint.
*
* @return String
*
* @struts.validator type=required
* @hibernate.property column=password_hint not-null=false
*/
   public String getPasswordHint() {
   return passwordHint;
   }

   /**
* Returns the user's roles.
*
* @return Set
*
* @hibernate.set table=user_role cascade=save-update lazy=false
* @hibernate.collection-key column=username
* @hibernate.collection-many-to-many class=org.appfuse.model.Role
*column=role_name
*/
   public Set getRoles() {
   return roles;
   }

   /**
* Adds a role for the user
*
* @param rolename
*/
   public void addRole(Role role) {
   getRoles().add(role);
   }

   /**
* Sets the username.
* @param username The username to set
*/
   public void setUsername(String username) {
   this.username = username;
   }

   /**
* Sets the password.
* @param password The password to set
*/
   public void setPassword(String password) {
   

RE: [M2] Xdoclet plugin and hibernate task

[Allison, Bob]

So do all five classes compile without using XDoclet?

-Original Message-
From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 12:00
To: Maven Users List
Subject: Re: [M2] Xdoclet plugin and hibernate task


BaseObject is in the same folter as the model objects.

Allison, Bob wrote:

A couple questions:

Where does BaseObject come from?  According to the error message, it
is not in the source tree and not on the class path.  If should be in
the source tree, there is something wrong with that source file.  If it
comes from Hibernate, you need to import the class (NOT the package)
for
XDoclet to work correctly.

Do these four classes compile correctly if you skip running XDoclet?
To
do this, comment out the XDoclet stuff from your pom.xml and try mvn
compile again.  If they do not compile for reasons other than missing
classes that XDoclet would be providing, you need to fix these errors
before XDoclet will work without problems.  There are a number of
compile problems that XDoclet won't mind but there are some (like
unknown classes) which prevent XDoclet from being able to work
properly.

-Original Message-
From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 11:42
To: Maven Users List
Subject: [M2] Xdoclet plugin and hibernate task


Hi,
I've been trying the xdoclet plugin 1.0-alpha-2 from org.codehaus.mojo
;

I've tried to compile some standard hibernate annotated classes from
the

appfuse project and I'm getting this error:
Below is the pom.xml, any ideas why am I getting this error message? 
Thanks in advance, keep up the good work with maven2 and does anyone 
know will there be soon a plugin for xdoclet2?

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'xdoclet'.
[INFO] 
---
-

[INFO] Building jspArt EJB Module
[INFO]task-segment: [xdoclet:xdoclet]
[INFO] 
---
-

[WARNING]
  This artifact has been relocated to javax.sql:jdbc-stdext:2.0.

[INFO] [xdoclet:xdoclet]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
(XDocletMain.start   47  ) Running hibernate/
INFO:Some classes refer to other classes that were not found among 
the sources or on the classpath.
 (Perhaps the referred class doesn't exist? Hasn't been 
generated yet?)
 The referring classes do not import any fully qualified
classes

matching these classes.
 However, since no packages are imported, xjavadoc has assumed 
that the referred classes
 belong to the same package as the referring class. The classes
are:
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ad
d
ress.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ro
l
e.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us
e
r.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us
e
rCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ad
d
ress.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Ro
l
e.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us
e
r.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
C:\Documents and Settings\User 
Name\maven-projects\jspArt\jspArtEjb\src\main\java\org\appfuse\model\Us
e
rCookie.java 
-- BaseObject qualified to org.appfuse.model.BaseObject
[INFO] Executed tasks
[INFO] 
---
-

[INFO] BUILD SUCCESSFUL
[INFO] 
---
-

[INFO] Total time: 4 seconds
[INFO] Finished at: Fri Nov 18 17:37:15 CET 2005
[INFO] Final Memory: 3M/7M
[INFO] 
---
-




here is my project's pom.xml:

project xmlns=http://maven.apache.org/POM/4.0.0;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;
  modelVersion4.0.0/modelVersion
  groupIdit.sigmalab.jspart/groupId
  artifactIdjspArtEjb/artifactId
  packagingejb/packaging
  version1.0-SNAPSHOT/version
  namejspArt EJB Module/name
  urlhttp://www.sigmalab.net/jspart/url
  build

Re: [M2] Xdoclet plugin and hibernate task

[Srepfler Srgjan]

Allison, Bob wrote:


So do all five classes compile without using XDoclet?

 

Yes, they all compile, furthermore they are the same classes from the 
well established framework appfuse, meaning the annotations are correct 
(although I'm not shure if he uses hibernate 2.0 or 3.0 as a version).


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [M2] Xdoclet plugin and hibernate task

[Allison, Bob]

I'm not really sure why the messages from XDoclet, since the classes
look fine.  My guess is that XDoclet is ignoring abstract classes in
deciding if it can find the class.  I think this is something you need
to take to the XDoclet list, since I don't think it is a maven problem.

-Original Message-
From: Srepfler Srgjan [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 12:03
To: Maven Users List
Subject: Re: [M2] Xdoclet plugin and hibernate task


The classes compile just fine, here's a a class and the baseobject;

User.java:

package org.appfuse.model;

import java.io.Serializable;
import java.util.HashSet;
import java.util.Set;

import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;
import org.apache.commons.lang.builder.ToStringBuilder;
import org.apache.commons.lang.builder.ToStringStyle;

/**
 * User class
 *
 * This class is used to generate the Struts Validator Form as well as
the
 * Hibernate mapping file.
 *
 * pa href=User.java.htmliView Source/i/a/p
 *
 * @author a href=mailto:[EMAIL PROTECTED]Matt Raible/a
 * Updated by Dan Kibler ([EMAIL PROTECTED])
 *
 * @struts.form include-all=true extends=BaseForm
 * @hibernate.class table=app_user
 */
public class User extends BaseObject implements Serializable {
private static final long serialVersionUID = 3832626162173359411L;
protected String username;
protected String password;
protected String confirmPassword;
protected String firstName;
protected String lastName;
protected Address address = new Address();
protected String phoneNumber;
protected String email;
protected String website;
protected String passwordHint;
protected Integer version;
protected Set roles = new HashSet();
protected Boolean enabled;

/**
 * Returns the username.
 *
 * @return String
 *
 * @struts.validator type=required
 * @hibernate.id column=username length=20 
generator-class=assigned
 *   unsaved-value=version
 */
public String getUsername() {
return username;
}

/**
 * Returns the password.
 * @return String
 *
 * @struts.validator type=required
 * @struts.validator type=twofields msgkey=errors.twofields
 * @struts.validator-args arg1resource=userForm.password
 * @struts.validator-args arg1resource=userForm.confirmPassword
 * @struts.validator-var name=secondProperty
value=confirmPassword
 * @hibernate.property column=password not-null=true
 */
public String getPassword() {
return password;
}

/**
 * Returns the confirmedPassword.
 * @return String
 *
 * @struts.validator type=required
 */
public String getConfirmPassword() {
return confirmPassword;
}

/**
 * Returns the firstName.
 * @return String
 *
 * @struts.validator type=required
 * @hibernate.property column=first_name not-null=true
length=50
 */
public String getFirstName() {
return firstName;
}

/**
 * Returns the lastName.
 * @return String
 *
 * @struts.validator type=required
 * @hibernate.property column=last_name not-null=true
length=50
 */
public String getLastName() {
return lastName;
}

public String getFullName() {
return firstName + ' ' + lastName;
}

/**
 * Returns the address.
 *
 * @return Address
 *
 * @hibernate.component
 */
public Address getAddress() {
return address;
}

/**
 * Returns the email.  This is an optional field for specifying a
 * different e-mail than the username.
 *
 * @return String
 *
 * @struts.validator type=required
 * @struts.validator type=email
 * @hibernate.property name=email not-null=true unique=true
 */
public String getEmail() {
return email;
}

/**
 * Returns the phoneNumber.
 *
 * @return String
 *
 * @struts.validator type=mask msgkey=errors.phone
 * @struts.validator-var name=mask value=${phone}
 * @hibernate.property column=phone_number not-null=false
 */
public String getPhoneNumber() {
return phoneNumber;
}

/**
 * Returns the website.
 *
 * @return String
 *
 * @struts.validator type=required
 * @hibernate.property column=website not-null=false
 */
public String getWebsite() {
return website;
}

/**
 * Returns the passwordHint.
 *
 * @return String
 *
 * @struts.validator type=required
 * @hibernate.property column=password_hint not-null=false
 */
public String getPasswordHint() {
return passwordHint;
}

/**
 * Returns the user's roles.
 *
 * @return Set
 *
 * @hibernate.set table=user_role cascade=save-update
lazy=false
 * @hibernate.collection-key column=username

Re: [M2] Xdoclet plugin and hibernate task

[Srepfler Srgjan]

Could it be that I should modify my pom.xml? Perhaps I used variables 
that put the files in a wrong position so that it can't find it in the 
classpath?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: M2 : Major Bug in xdoclet plugin ?

[Peschier J. (Jeroen)]

I ran into this myself too. It's a known bug in XDoclet itself. See
http://opensource2.atlassian.com/projects/xdoclet/browse/XDT-1505

The problem is the old definition of destDir is used which results in
the class being generated in a place you don't want or even expect them.
As a workaround you can set the destDir attribute on any subtask of the
ejbdoclet, e.g.:

ejbdoclet ejbSpec=2.1 destDir=${basedir}/src
  fileset dir=${basedir}/src includes=**/*Bean.java/
  homeinterface destDir=${basedir}/src/
  remoteinterface destDir=${basedir}/src/
  localinterface destDir=${basedir}/src/
  localhomeinterface destDir=${basedir}/src/
/ejbdoclet  

---Oorspronkelijk bericht-
Van: Pete [mailto:[EMAIL PROTECTED] 
Verzonden: zondag 13 november 2005 17:26
Aan: Maven Users List
Onderwerp: Re: M2 : Major Bug in xdoclet plugin ?

Anyone help ?

On 12/11/05, Pete [EMAIL PROTECTED] wrote:
 If I use the xdoclet plugin to generate ejb classes all works fine and
 as expected - providing I running one ejb project at a time.

 e.g.
 mvn clean generate-sources

 from the pom.xml for the EJB project(s)  all is ok.

 BUT if I run from the parent project pom :-

 - the reactor correctly finds the order
 - runs generate-sources   on my 2 ejb projects

 but at the end the target\generated-sources\xdoclet  directory
 for the 1st EJB project contains BOTH ejbs generated sources

 The 2nd EJB project is missing the target\generated-sources\xdoclet
directory

 The -X debug looks fine for both EJB projects.
 If I swap the dependencies around then the exact reverse happens.
 If I remove one EJB child module from the parent poms module list,
 all works fine.

 Here is what I have in each of the ejb poms

 1st EJB pom (the one that ends up with both generated-sources)
 build
finalNameebars_dmz_srv_ExampleService/finalName
plugins
plugin

artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
executions
execution

phasegenerate-sources/phase
goals

goalxdoclet/goal
/goals
configuration
tasks

ejbdoclet
 destdir=${project.build.directory}/generated-sources/xdoclet

fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

entitycmp destDir=${project.build.outputDirectory}/

!-- session/  --

remoteinterface pattern={0}Remote/

localinterface pattern={0}Local/

homeinterface pattern={0}RemoteHome/

localhomeinterface pattern={0}LocalHome/

deploymentdescriptor
 destDir=${project.build.outputDirectory}/META-INF/

!--orion
 destdir=${project.build.outputDirectory}/META-INF/   --

/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin

/build


 2nd EJB pom (ends up with no generated-sources)

 build
finalNameebars_dmz_bus_ExampleManager/finalName
plugins
!-- needed to override to add manifest
class-path in ejb jar --

plugin

artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-2/version

executions
execution

phasegenerate-sources/phase
goals

goalxdoclet/goal
/goals
configuration
tasks

ejbdoclet
 destdir=${project.build.directory}/generated-sources/xdoclet

fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

entitycmp destDir=${project.build.outputDirectory}/

!-- session/  --

remoteinterface pattern={0}Remote/

localinterface pattern={0}Local/

homeinterface pattern={0}RemoteHome/

localhomeinterface pattern={0}LocalHome/

deploymentdescriptor
 destDir=${project.build.outputDirectory}/META-INF/

!--orion
 destdir=${project.build.outputDirectory}/META-INF/   --

/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin
/plugins
/build

 I have also tried both :-
  version1.0-alpha-1/version
  version1.0-alpha-2/version

 of the plugin.

 Finally here's the -X output

Re: M2 : Major Bug in xdoclet plugin ?

[Pete]

Yes thanks very much for that.

I only realised this myself yesterday, I had re-posted the same
problem under a different title yesterday hoping to get more response,
but then (as always) noticed the bug myself !

On 17/11/05, Peschier J. (Jeroen) [EMAIL PROTECTED] wrote:

 I ran into this myself too. It's a known bug in XDoclet itself. See
 http://opensource2.atlassian.com/projects/xdoclet/browse/XDT-1505

 The problem is the old definition of destDir is used which results in
 the class being generated in a place you don't want or even expect them.
 As a workaround you can set the destDir attribute on any subtask of the
 ejbdoclet, e.g.:

 ejbdoclet ejbSpec=2.1 destDir=${basedir}/src
  fileset dir=${basedir}/src includes=**/*Bean.java/
  homeinterface destDir=${basedir}/src/
  remoteinterface destDir=${basedir}/src/
  localinterface destDir=${basedir}/src/
  localhomeinterface destDir=${basedir}/src/
 /ejbdoclet

 ---Oorspronkelijk bericht-
 Van: Pete [mailto:[EMAIL PROTECTED]
 Verzonden: zondag 13 november 2005 17:26
 Aan: Maven Users List
 Onderwerp: Re: M2 : Major Bug in xdoclet plugin ?

 Anyone help ?

 On 12/11/05, Pete [EMAIL PROTECTED] wrote:
  If I use the xdoclet plugin to generate ejb classes all works fine and
  as expected - providing I running one ejb project at a time.
 
  e.g.
  mvn clean generate-sources
 
  from the pom.xml for the EJB project(s)  all is ok.
 
  BUT if I run from the parent project pom :-
 
  - the reactor correctly finds the order
  - runs generate-sources   on my 2 ejb projects
 
  but at the end the target\generated-sources\xdoclet  directory
  for the 1st EJB project contains BOTH ejbs generated sources
 
  The 2nd EJB project is missing the target\generated-sources\xdoclet
 directory
 
  The -X debug looks fine for both EJB projects.
  If I swap the dependencies around then the exact reverse happens.
  If I remove one EJB child module from the parent poms module list,
  all works fine.
 
  Here is what I have in each of the ejb poms
 
  1st EJB pom (the one that ends up with both generated-sources)
  build
 finalNameebars_dmz_srv_ExampleService/finalName
 plugins
 plugin
 
 artifactIdxdoclet-maven-plugin/artifactId
 groupIdorg.codehaus.mojo/groupId
 version1.0-alpha-2/version
 executions
 execution
 
 phasegenerate-sources/phase
 goals
 
 goalxdoclet/goal
 /goals
 configuration
 tasks
 
 ejbdoclet
  destdir=${project.build.directory}/generated-sources/xdoclet
 
 fileset dir=${basedir}/src/main/java includes=**/*Bean.java/
 
 entitycmp destDir=${project.build.outputDirectory}/
 
 !-- session/  --
 
 remoteinterface pattern={0}Remote/
 
 localinterface pattern={0}Local/
 
 homeinterface pattern={0}RemoteHome/
 
 localhomeinterface pattern={0}LocalHome/
 
 deploymentdescriptor
  destDir=${project.build.outputDirectory}/META-INF/
 
 !--orion
  destdir=${project.build.outputDirectory}/META-INF/   --
 
 /ejbdoclet
 /tasks
 /configuration
 /execution
 /executions
 /plugin
 
 /build
 
 
  2nd EJB pom (ends up with no generated-sources)
 
  build
 finalNameebars_dmz_bus_ExampleManager/finalName
 plugins
 !-- needed to override to add manifest
 class-path in ejb jar --
 
 plugin
 
 artifactIdxdoclet-maven-plugin/artifactId
 groupIdorg.codehaus.mojo/groupId
   version1.0-alpha-2/version
 
 executions
 execution
 
 phasegenerate-sources/phase
 goals
 
 goalxdoclet/goal
 /goals
 configuration
 tasks
 
 ejbdoclet
  destdir=${project.build.directory}/generated-sources/xdoclet
 
 fileset dir=${basedir}/src/main/java includes=**/*Bean.java/
 
 entitycmp destDir=${project.build.outputDirectory}/
 
 !-- session/  --
 
 remoteinterface pattern={0}Remote/
 
 localinterface pattern={0}Local/
 
 homeinterface pattern={0}RemoteHome/
 
 localhomeinterface pattern={0}LocalHome/
 
 deploymentdescriptor
  destDir=${project.build.outputDirectory}/META-INF/
 
 !--orion
  destdir=${project.build.outputDirectory}/META-INF/   --
 
 /ejbdoclet

XDoclet plugin : What was wrong - Solutions

[Jerarckill - ANS]

The problem related to the XDoclet plugin that was producing a nasty  
exception when launched was due to the fact that the alpha-1.0 version was  
just not working.


This version is the one referenced as example on Codehaus website and is  
NOT WORKING for ejbDoclet task (I don't know for other ones).


Anyway, an Alpha-2.0 version has also been released and just changing this  
makes the ejbDoclet plugin work.


Also, if you have problems using this plugin with Java 1.5, know that the  
XJavadoc version used in this plugin (1.1) doesn't work with Java 1.5  
syntax.  You will have to change this dependency to XJavadoc 1.5 in order  
to have XDoclet work with this specific syntax.


Hope it will help somebody else,

Jérôme

P.S: Thank you all for the reply sent to me while searching for a solution


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m2] new xdoclet plugin + framework - feedback?

[Ashley Williams]

Hi

Just testing the waters here with regards to a new plugin framework  
that I've started, to see if there is any demand.
It's not specific to xdoclet but because I rely on xdoclet  
functionality a lot, it's become my prototype project.


First of all the link: https://svn.codehaus.org/mojo/trunk/mojo/mojo- 
sandbox/xjc-maven-plugin/earlyaccess/
There are 2 plugins under there called ejbdoclet and webdoclet (build  
mant first though).


There is also a sample ear project so that you can see how to invoke  
them.


Description


The motivation for this is that I would like to avoid reinventing the  
wheel when there is already an ant task out there.
Kenneys antrun plugin (that I believe the existing xdoclet delegates  
to) is a good solution to this.


For me the final piece of the jigsaw is a way of automatically  
specifying ant attributes that I feel maven should already
know about on my behalf. To take an example instead of specifying the  
following:



  task![CDATA[
ejbdoclet ejbspec=2.1
  fileset includes=**/*Bean.java/
  deploymentdescriptor/
  remoteinterface/
  homeinterface/
  localinterface/
  localhomeinterface/
  session/
  entitycmp/
  entitypk/
  jboss version=4.0/
/ejbdoclet
  ]]/task

So as you can see there are no attributes such as  
destDir=target/

That's it really.

Implementation
-
If anyone is interested it's quite easy to knock out plugins as it  
basically just defines a map. For example here is the webdoclet plugin:


   public void execute()
throws MojoExecutionException, MojoFailureException
{
String[] mappings = new String[] {
@destDir,  MantGoal.JAVA_GEN,
deploymentdescriptor/@destDir, MantGoal.META_INF_GEN,
fileset/@dir,  MantGoal.JAVA,
jboss/@destDir,MantGoal.META_INF_GEN
};
MantGoal goal = new MantGoal(this, project,  
xdoclet.modules.ejb.EjbDocletTask, task, mappings);

goal.execute(xdoclet.class.path);
}

As you can see all I do is map an xpath location of the ant tag to a  
maven constant - eg JAVA_GEN is a generated-sources dir

under target. To give another example this is from xjc:

public void execute()
throws MojoExecutionException, MojoFailureException
{
String[] mappings = new String[] { @target,  
MantGoal.JAVA_GEN };
MantGoal goal = new MantGoal(this, project,  
org.apache.ws.jaxme.generator.XJCTask, task, mappings);

goal.execute();
}

and that's it.

Considerations

I suppose speed is the main thing - the fact that I have to maintain  
an additional layer to prop up ant can't be doing
me any favors. Not done any tests but this may be a problem for large  
builds. However to take the xjc plugin as
an example (I happen to be the maintainer) it would save me lots of  
time and unit tests to know I can just delegate

to ant.

Is this idea a non starter? Maybe there is howler of a design flaw  
that means this won't work long term - just tell

me before I spend too much time on it ;)

All opinions welcome.

Thanks
- Ashley



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Cannot make XDoclet plugin work

[Pete]

If you search for your error on the Mailing list you'll see a
workaround has been posted a couple of times recently.

On 14/11/05, Dennis Lundberg [EMAIL PROTECTED] wrote:
 There is an issue for this in Jira:
   http://jira.codehaus.org/browse/MEV-191

 Dennis Lundberg wrote:
  Hello
 
  The problem is with either xdoclet or the xdoclet-maven-plugin. One of
  them has a dependency on commons-logging-1.1-dev, which is not yet
  released. That dependency is therefor not available at ibiblio.
 
  Jerarckill - ANS wrote:
  Hello,
 
  I am trying to make the XDoclet plugin work on one of my project.
  Since the task needed is ejbDoclet, i just copy-pasted the code given
  from
  http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
 
  This copy-pasted code is the following:
  //
  
 
  plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-1/version
executions
  execution
phasegenerate-sources/phase
goals
  goalxdoclet/goal
/goals
configuration
  tasks
 
!-- example : --
 
ejbdoclet destdir=${project.build.outputDirectory}
  fileset dir=${basedir}/src/main/java
  includes=**/*Bean.java/
  entitycmp destDir=${project.build.outputDirectory}/
  deploymentdescriptor
destDir=${project.build.outputDirectory}/META-INF
  /
/ejbdoclet
 
  /tasks
/configuration
  /goal
/goals
  /plugin
 
  //
  
 
  When launching the mvn compile goal, I receive this output, which is,
  as you can see, totally unclear.
 
  //
  
 
  C:\development\projects\workflows\users-modelcmd /k mvn compile
  [INFO] Scanning for projects...
  [INFO]
  
 
  [INFO] Building Theseos default Model project
  [INFO]task-segment: [compile]
  [INFO]
  
 
  Downloading:
  http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.pom
 
  8K downloaded
  Downloading:
  http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.jar
 
  6K downloaded
  [WARNING]
This artifact has been relocated to javax.transaction:jta:1.0.1B.
 
 
  Downloading:
  http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1-dev/commons-logging-1.1-dev.pom
 
  [WARNING] Unable to get resource from repository central
  (http://repo1.maven.org/maven2)
  [WARNING]
This artifact has been relocated to javax.servlet:servlet-api:2.3.
 
 
  [INFO]
  
 
  [ERROR] FATAL ERROR
  [INFO]
  
 
  [INFO] null
  [INFO]
  
 
  [INFO] Trace
  java.lang.AbstractMethodError
  at
  org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
 
  at
  org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
 
  at
  org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
 
  at
  org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1038)
 
  at
  org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:563)
 
  at
  org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:377)
 
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
 
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
 
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
 
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301)
 
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268)
 
  at
  org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137)
 
  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java

Re: Cannot make XDoclet plugin work

[Pete]

Just to clarify I'm talking about the 2nd error the exception :-
java.lang.AbstractMethodError
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)

not the missing dependant JAR warning

On 16/11/05, Pete [EMAIL PROTECTED] wrote:
 If you search for your error on the Mailing list you'll see a
 workaround has been posted a couple of times recently.

 On 14/11/05, Dennis Lundberg [EMAIL PROTECTED] wrote:
  There is an issue for this in Jira:
http://jira.codehaus.org/browse/MEV-191
 
  Dennis Lundberg wrote:
   Hello
  
   The problem is with either xdoclet or the xdoclet-maven-plugin. One of
   them has a dependency on commons-logging-1.1-dev, which is not yet
   released. That dependency is therefor not available at ibiblio.
  
   Jerarckill - ANS wrote:
   Hello,
  
   I am trying to make the XDoclet plugin work on one of my project.
   Since the task needed is ejbDoclet, i just copy-pasted the code given
   from
   http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html
  
   This copy-pasted code is the following:
   //
   
  
   plugin
 artifactIdxdoclet-maven-plugin/artifactId
 groupIdorg.codehaus.mojo/groupId
 version1.0-alpha-1/version
 executions
   execution
 phasegenerate-sources/phase
 goals
   goalxdoclet/goal
 /goals
 configuration
   tasks
  
 !-- example : --
  
 ejbdoclet destdir=${project.build.outputDirectory}
   fileset dir=${basedir}/src/main/java
   includes=**/*Bean.java/
   entitycmp destDir=${project.build.outputDirectory}/
   deploymentdescriptor
 destDir=${project.build.outputDirectory}/META-INF
   /
 /ejbdoclet
  
   /tasks
 /configuration
   /goal
 /goals
   /plugin
  
   //
   
  
   When launching the mvn compile goal, I receive this output, which is,
   as you can see, totally unclear.
  
   //
   
  
   C:\development\projects\workflows\users-modelcmd /k mvn compile
   [INFO] Scanning for projects...
   [INFO]
   
  
   [INFO] Building Theseos default Model project
   [INFO]task-segment: [compile]
   [INFO]
   
  
   Downloading:
   http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.pom
  
   8K downloaded
   Downloading:
   http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.jar
  
   6K downloaded
   [WARNING]
 This artifact has been relocated to javax.transaction:jta:1.0.1B.
  
  
   Downloading:
   http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1-dev/commons-logging-1.1-dev.pom
  
   [WARNING] Unable to get resource from repository central
   (http://repo1.maven.org/maven2)
   [WARNING]
 This artifact has been relocated to javax.servlet:servlet-api:2.3.
  
  
   [INFO]
   
  
   [ERROR] FATAL ERROR
   [INFO]
   
  
   [INFO] null
   [INFO]
   
  
   [INFO] Trace
   java.lang.AbstractMethodError
   at
   org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
  
   at
   org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
  
   at
   org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
  
   at
   org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1038)
  
   at
   org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:563)
  
   at
   org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:377)
  
   at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519)
  
   at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469)
  
   at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448)
  
   at
   org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301

Re: Cannot make XDoclet plugin work

[Dennis Lundberg]

Hello

The problem is with either xdoclet or the xdoclet-maven-plugin. One of 
them has a dependency on commons-logging-1.1-dev, which is not yet 
released. That dependency is therefor not available at ibiblio.


Jerarckill - ANS wrote:

Hello,

I am trying to make the XDoclet plugin work on one of my project.
Since the task needed is ejbDoclet, i just copy-pasted the code given from
http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html

This copy-pasted code is the following:
// 

plugin
  artifactIdxdoclet-maven-plugin/artifactId
  groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-1/version
  executions
execution
  phasegenerate-sources/phase
  goals
goalxdoclet/goal
  /goals
  configuration
tasks

  !-- example : --

  ejbdoclet destdir=${project.build.outputDirectory}
fileset dir=${basedir}/src/main/java 
includes=**/*Bean.java/

entitycmp destDir=${project.build.outputDirectory}/
deploymentdescriptor
  destDir=${project.build.outputDirectory}/META-INF
/
  /ejbdoclet

/tasks
  /configuration
/goal
  /goals
/plugin

// 

When launching the mvn compile goal, I receive this output, which is, as 
you can see, totally unclear.


// 

C:\development\projects\workflows\users-modelcmd /k mvn compile
[INFO] Scanning for projects...
[INFO]
 


[INFO] Building Theseos default Model project
[INFO]task-segment: [compile]
[INFO]
 


Downloading:
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.pom 


8K downloaded
Downloading:
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.jar 


6K downloaded
[WARNING]
  This artifact has been relocated to javax.transaction:jta:1.0.1B.


Downloading:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1-dev/commons-logging-1.1-dev.pom 


[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
  This artifact has been relocated to javax.servlet:servlet-api:2.3.


[INFO]
 


[ERROR] FATAL ERROR
[INFO]
 


[INFO] null
[INFO]
 


[INFO] Trace
java.lang.AbstractMethodError
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247) 


at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) 


at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56) 


at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1038) 


at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:563) 


at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:377) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) 


at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 


at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 


at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java

Re: Cannot make XDoclet plugin work

[Dennis Lundberg]

There is an issue for this in Jira:
  http://jira.codehaus.org/browse/MEV-191

Dennis Lundberg wrote:

Hello

The problem is with either xdoclet or the xdoclet-maven-plugin. One of 
them has a dependency on commons-logging-1.1-dev, which is not yet 
released. That dependency is therefor not available at ibiblio.


Jerarckill - ANS wrote:

Hello,

I am trying to make the XDoclet plugin work on one of my project.
Since the task needed is ejbDoclet, i just copy-pasted the code given 
from

http://mojo.codehaus.org/xdoclet-maven-plugin/usage.html

This copy-pasted code is the following:
// 



plugin
  artifactIdxdoclet-maven-plugin/artifactId
  groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-1/version
  executions
execution
  phasegenerate-sources/phase
  goals
goalxdoclet/goal
  /goals
  configuration
tasks

  !-- example : --

  ejbdoclet destdir=${project.build.outputDirectory}
fileset dir=${basedir}/src/main/java 
includes=**/*Bean.java/

entitycmp destDir=${project.build.outputDirectory}/
deploymentdescriptor
  destDir=${project.build.outputDirectory}/META-INF
/
  /ejbdoclet

/tasks
  /configuration
/goal
  /goals
/plugin

// 



When launching the mvn compile goal, I receive this output, which is, 
as you can see, totally unclear.


// 



C:\development\projects\workflows\users-modelcmd /k mvn compile
[INFO] Scanning for projects...
[INFO]
 


[INFO] Building Theseos default Model project
[INFO]task-segment: [compile]
[INFO]
 


Downloading:
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.pom 


8K downloaded
Downloading:
http://repo1.maven.org/maven2/org/codehaus/mojo/xdoclet-maven-plugin/1.0-alpha-1/xdoclet-maven-plugin-1.0-alpha-1.jar 


6K downloaded
[WARNING]
  This artifact has been relocated to javax.transaction:jta:1.0.1B.


Downloading:
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.1-dev/commons-logging-1.1-dev.pom 


[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[WARNING]
  This artifact has been relocated to javax.servlet:servlet-api:2.3.


[INFO]
 


[ERROR] FATAL ERROR
[INFO]
 


[INFO] null
[INFO]
 


[INFO] Trace
java.lang.AbstractMethodError
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247) 


at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) 


at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56) 


at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1038) 


at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:563) 


at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:377) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) 


at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 


at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 


at java.lang.reflect.Method.invoke(Method.java:585

Re: M2 : Major Bug in xdoclet plugin ?

[Pete]

Anyone help ?

On 12/11/05, Pete [EMAIL PROTECTED] wrote:
 If I use the xdoclet plugin to generate ejb classes all works fine and
 as expected - providing I running one ejb project at a time.

 e.g.
 mvn clean generate-sources

 from the pom.xml for the EJB project(s)  all is ok.

 BUT if I run from the parent project pom :-

 - the reactor correctly finds the order
 - runs generate-sources   on my 2 ejb projects

 but at the end the target\generated-sources\xdoclet  directory
 for the 1st EJB project contains BOTH ejbs generated sources

 The 2nd EJB project is missing the target\generated-sources\xdoclet  directory

 The -X debug looks fine for both EJB projects.
 If I swap the dependencies around then the exact reverse happens.
 If I remove one EJB child module from the parent poms module list,
 all works fine.

 Here is what I have in each of the ejb poms

 1st EJB pom (the one that ends up with both generated-sources)
 build
finalNameebars_dmz_srv_ExampleService/finalName
plugins
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
   
  ejbdoclet
 destdir=${project.build.directory}/generated-sources/xdoclet

 fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

 entitycmp destDir=${project.build.outputDirectory}/
!-- 
 session/  --

 remoteinterface pattern={0}Remote/

 localinterface pattern={0}Local/

 homeinterface pattern={0}RemoteHome/

 localhomeinterface pattern={0}LocalHome/

 deploymentdescriptor
 destDir=${project.build.outputDirectory}/META-INF/
!--   
  orion
 destdir=${project.build.outputDirectory}/META-INF/   --
/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin

/build


 2nd EJB pom (ends up with no generated-sources)

 build
finalNameebars_dmz_bus_ExampleManager/finalName
plugins
!-- needed to override to add manifest  
 class-path in ejb jar --

plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-2/version

executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks
   
  ejbdoclet
 destdir=${project.build.directory}/generated-sources/xdoclet

 fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

 entitycmp destDir=${project.build.outputDirectory}/
!-- 
 session/  --

 remoteinterface pattern={0}Remote

M2 : Major Bug in xdoclet plugin ?

[Pete]

If I use the xdoclet plugin to generate ejb classes all works fine and
as expected - providing I running one ejb project at a time.

e.g.
mvn clean generate-sources

from the pom.xml for the EJB project(s)  all is ok.

BUT if I run from the parent project pom :-

- the reactor correctly finds the order
- runs generate-sources   on my 2 ejb projects

but at the end the target\generated-sources\xdoclet  directory
for the 1st EJB project contains BOTH ejbs generated sources

The 2nd EJB project is missing the target\generated-sources\xdoclet  directory

The -X debug looks fine for both EJB projects.
If I swap the dependencies around then the exact reverse happens.
If I remove one EJB child module from the parent poms module list,
all works fine.

Here is what I have in each of the ejb poms

1st EJB pom (the one that ends up with both generated-sources)
build
finalNameebars_dmz_srv_ExampleService/finalName
plugins
plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
version1.0-alpha-2/version
executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks

ejbdoclet
destdir=${project.build.directory}/generated-sources/xdoclet

fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

entitycmp destDir=${project.build.outputDirectory}/
!-- 
session/  --

remoteinterface pattern={0}Remote/

localinterface pattern={0}Local/

homeinterface pattern={0}RemoteHome/

localhomeinterface pattern={0}LocalHome/

deploymentdescriptor
destDir=${project.build.outputDirectory}/META-INF/
!--
orion
destdir=${project.build.outputDirectory}/META-INF/   --
/ejbdoclet
/tasks
/configuration
/execution
/executions
/plugin

/build


2nd EJB pom (ends up with no generated-sources)

build
finalNameebars_dmz_bus_ExampleManager/finalName
plugins
!-- needed to override to add manifest  class-path 
in ejb jar --

plugin
artifactIdxdoclet-maven-plugin/artifactId
groupIdorg.codehaus.mojo/groupId
  version1.0-alpha-2/version

executions
execution
phasegenerate-sources/phase
goals
goalxdoclet/goal
/goals
configuration
tasks

ejbdoclet
destdir=${project.build.directory}/generated-sources/xdoclet

fileset dir=${basedir}/src/main/java includes=**/*Bean.java/

entitycmp destDir=${project.build.outputDirectory}/
!-- 
session/  --

remoteinterface pattern={0}Remote/

localinterface pattern={0

[m2] xdoclet plugin

[Miguel Griffa]

Is there any xdoclet plugin ready for m2?
I haven't found a reference in m2 site, any idea?

--
Miguel Griffa
Skype: miguel.griffa
Y!: m_griffa
MSN: [EMAIL PROTECTED]
Cell: 54-911-62519355

RE: [m2] xdoclet plugin

[Yann Le Du]

Hi Miguel,

You got one at mojo.codehaus.org :
http://mojo.codehaus.org/xdoclet-maven-plugin/

Regards,
Yann


--- Miguel Griffa [EMAIL PROTECTED] a écrit :

 Is there any xdoclet plugin ready for m2?
 I haven't found a reference in m2 site, any idea?
 
 --
 Miguel Griffa
 Skype: miguel.griffa
 Y!: m_griffa
 MSN: [EMAIL PROTECTED]
 Cell: 54-911-62519355
 







___ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] xdoclet plugin

[Miguel Griffa]

great!
thanks
I'll try it asap

On 11/2/05, Yann Le Du [EMAIL PROTECTED] wrote:

 Hi Miguel,

 You got one at mojo.codehaus.org http://mojo.codehaus.org :
 http://mojo.codehaus.org/xdoclet-maven-plugin/

 Regards,
 Yann


 --- Miguel Griffa [EMAIL PROTECTED] a écrit :

  Is there any xdoclet plugin ready for m2?
  I haven't found a reference in m2 site, any idea?
 
  --
  Miguel Griffa
  Skype: miguel.griffa
  Y!: m_griffa
  MSN: [EMAIL PROTECTED]
  Cell: 54-911-62519355
 








 ___
 Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
 Téléchargez cette version sur http://fr.messenger.yahoo.com

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
Miguel Griffa
Skype: miguel.griffa
Y!: m_griffa
MSN: [EMAIL PROTECTED]
Cell: 54-911-62519355

Re: maven2 xdoclet plugin

[Konstantin Priblouda]

--- Arto Pastinen [EMAIL PROTECTED] wrote:

 Hi!
 
 XDoclet 1, unless what is the situation of the
 XDoclet 2?!?
 If the hibernatedoclet works it is also fine for
 me..


hibernate plugin is mot active part of XD2.  I recall
that one of your developers ( Anatol Pomozov ) was
active
in M2 lists...

You may repeat the question in dedicated lits for XD2
plugins. 
( see http://xdoclet.codehaus.org ) 

regards,

[ Konstantin Pribluda http://www.pribluda.de ]
Still using XDoclet 1.x?  XDoclet 2 is released and of production quality.
check it out: http://xdoclet.codehaus.org




Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

maven2 xdoclet plugin

[Arto Pastinen]

Hi!

Does anyone know how to get xdoclet plugins to work in maven2?!?

- Artsi

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven2 xdoclet plugin

[Konstantin Priblouda]

--- Arto Pastinen [EMAIL PROTECTED] wrote:

 Hi!
 
 Does anyone know how to get xdoclet plugins to work
 in maven2?!?

You mean XD 1.2.x or XD2 ? 

regards,

[ Konstantin Pribluda http://www.pribluda.de ]
Still using XDoclet 1.x?  XDoclet 2 is released and of production quality.
check it out: http://xdoclet.codehaus.org

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

XDoclet plugin for maven 2

[Loïc Lefèvre]

Hi,
do you know if the maven xdoclet plugin has been / is being ported to maven 2?

Thanks for your comments,
Loïc

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with strutsconfigxml piece of webdoclet piece of xdoclet plugin for maven

[AAKhopkar]

Hi,

I am using xdoclet1.2.3

I have the apache module setup as a dependency.  However, when I run
webdoclet, no struts-config file is generated.  I do have the apache module
as a dependency.  Here's a snippet:

dependency
  idxdoclet/id
  version1.2.3/version
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-web-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-apache-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

When I run maven xdoclet:webdoclet here's my project.properties file:

maven.xdoclet.webdoclet.strutsconfigxml.0.destinationFile=struts-config-generated.xml

maven.xdoclet.webdoclet.strutsconfigxml.0.destDir=${basedir}/src/webapp/WEB-INF

maven.xdoclet.webdoclet.strutsconfigxml.0.mergeDir=${basedir}/xdocletmerge
maven.xdoclet.webdoclet.strutsconfigxml.0=true
maven.xdoclet.webdoclet.fileset.0.include=**/*.java

maven.xdoclet.webdoclet.strutsconfigxml.0.validateXML=false
maven.xdoclet.webdoclet.strutsconfigxml.0.Version=1.2.4

maven.xdoclet.webdoclet.deploymentdescriptor.0=false
maven.xdoclet.webdoclet.jsptaglib.0=false

When I run with the -X option, here's the output  (As you can see from the
output, the apache module does get loaded):

Please let me know what I'm missing here


 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Initializing Plugins!
Set plugin source directory to C:\apps\maven\plugins
Set unpacked plugin directory to C:\Documents and
Settings\NOUT198\.maven\cache
Set user plugin directory to C:\Documents and
Settings\NOUT198\.maven\plugins
Loading plugin cache
Now mapping cached plugins
Loading plugin 'maven-cruisecontrol-plugin-1.6'
Loading plugin 'maven-multichanges-plugin-1.1'
Loading plugin 'maven-checkstyle-plugin-2.5'
Loading plugin 'maven-file-activity-plugin-1.5.1'
Loading plugin 'maven-jellydoc-plugin-1.3.1'
Loading plugin 'maven-ear-plugin-1.6'
Loading plugin 'maven-jdepend-plugin-1.5'
Loading plugin 'maven-pom-plugin-1.4.1'
Loading plugin 'maven-jira-plugin-1.1.2'
Loading plugin 'maven-overnite-xmlbeans-plugin-1.0'
Loading plugin 'maven-jar-plugin-1.6.1'
Loading plugin 'maven-developer-activity-plugin-1.5.1'
Loading plugin 'maven-jboss-plugin-1.5'
Loading plugin 'maven-faq-plugin-1.4'
Loading plugin 'maven-dist-plugin-1.6.1'
Loading plugin 'maven-javadoc-plugin-1.7'
Loading plugin 'maven-linkcheck-plugin-1.3.4'
Loading plugin 'maven-tasklist-plugin-2.3'
Loading plugin 'maven-idea-plugin-1.5'
Loading plugin 'maven-jcoverage-plugin-1.0.9'
Loading plugin 'maven-junit-report-plugin-1.5'
Loading plugin 'maven-plugin-plugin-1.5.2'
Loading plugin 'maven-jxr-plugin-1.4.2'
Loading plugin 'maven-ashkelon-plugin-1.2'
Loading plugin 'maven-announcement-plugin-1.3'
Loading plugin 'maven-xdoc-plugin-1.8'
Loading plugin 'maven-eclipse-plugin-1.9'
Loading plugin 'maven-shell-plugin-1.1'
Loading plugin 'maven-rar-plugin-1.0'
Loading plugin 'maven-dashboard-plugin-1.6'
Loading plugin 'maven-scm-plugin-1.4.1'
Loading plugin 'maven-clover-plugin-1.6'
Loading plugin 'maven-uberjar-plugin-1.2'
Loading plugin 'maven-war-plugin-1.6.1'
Loading plugin 'maven-simian-plugin-1.4'
Loading plugin 'maven-ant-plugin-1.8.1'
Loading plugin 'maven-ejb-plugin-1.5'
Loading plugin 'maven-tjdo-plugin-1.0.0'
Loading plugin 'maven-changes-plugin-1.5.1'
Loading plugin 'maven-j2ee-plugin-1.5.1'
Loading plugin 'maven-release-plugin-1.4.1'
Loading plugin 'maven-abbot-plugin-1.1'
Loading plugin 'maven-multiproject-plugin-1.3.1'
Loading plugin 'maven-nsis-plugin-1.1'
Loading plugin 'maven-license-plugin-1.2'
Loading plugin 'maven-jdiff-plugin-1.4'
Loading plugin 'maven-pmd-plugin-1.6'
Loading plugin 'maven-repository-plugin-1.2'
Loading plugin 'maven-xdoclet-plugin-1.2.3'
Loading plugin 'andromda-cartridge-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-jbuilder-plugin-1.5'
Loading plugin 'maven-console-plugin-1.1'
Loading plugin 'maven-webserver-plugin-2.0'
Loading plugin 'maven-axis-plugin-0.7'
Loading plugin 'maven-aspectwerkz-plugin-1.2'
Loading plugin 'maven-test-plugin-1.6.2'
Loading plugin 'maven-jetty-plugin-1.1'
Loading plugin 'maven-andromdapp-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'andromda-translation-library-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-docbook-plugin-1.2'
Loading plugin 'maven-latka-plugin-1.4.1'
Loading plugin 'maven-aspectj-plugin-3.2'
Loading plugin 'maven-hibernate-plugin-1.2'
Loading plugin 'maven-native-plugin-1.1'
Loading plugin 'maven-site-plugin-1.5.2'
Loading plugin 'maven-gump-plugin-1.4'
Loading plugin 'maven-appserver-plugin-2.0'
Loading plugin 'maven-java-plugin-1.5'
Loading plugin 'maven-pdf-plugin-2.2.1'
Loading plugin 'maven-html2xdoc-plugin-1.3.1'
Loading plugin 'maven-jdee-plugin-1.1'
Loading plugin 'maven-jalopy-plugin-1.3.1'
Loading plugin 'maven-andromda-plugin-3.0-RC2-SNAPSHOT

Problem with strutsconfigxml piece of webdoclet piece of xdoclet plugin for maven

[AAKhopkar]

Hi,

I am using xdoclet1.2.3

I have the apache module setup as a dependency.  However, when I run
webdoclet, no struts-config file is generated.  I do have the apache module
as a dependency.  Here's a snippet:

dependency
  idxdoclet/id
  version1.2.3/version
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-web-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-apache-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

When I run maven xdoclet:webdoclet here's my project.properties file:

maven.xdoclet.webdoclet.strutsconfigxml.0.destinationFile=struts-config-generated.xml

maven.xdoclet.webdoclet.strutsconfigxml.0.destDir=${basedir}/src/webapp/WEB-INF

maven.xdoclet.webdoclet.strutsconfigxml.0.mergeDir=${basedir}/xdocletmerge
maven.xdoclet.webdoclet.strutsconfigxml.0=true
maven.xdoclet.webdoclet.fileset.0.include=**/*.java

maven.xdoclet.webdoclet.strutsconfigxml.0.validateXML=false
maven.xdoclet.webdoclet.strutsconfigxml.0.Version=1.2.4

maven.xdoclet.webdoclet.deploymentdescriptor.0=false
maven.xdoclet.webdoclet.jsptaglib.0=false

When I run with the -X option, here's the output  (As you can see from the
output, the apache module does get loaded):

Please let me know what I'm missing here


 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Initializing Plugins!
Set plugin source directory to C:\apps\maven\plugins
Set unpacked plugin directory to C:\Documents and
Settings\NOUT198\.maven\cache
Set user plugin directory to C:\Documents and
Settings\NOUT198\.maven\plugins
Loading plugin cache
Now mapping cached plugins
Loading plugin 'maven-cruisecontrol-plugin-1.6'
Loading plugin 'maven-multichanges-plugin-1.1'
Loading plugin 'maven-checkstyle-plugin-2.5'
Loading plugin 'maven-file-activity-plugin-1.5.1'
Loading plugin 'maven-jellydoc-plugin-1.3.1'
Loading plugin 'maven-ear-plugin-1.6'
Loading plugin 'maven-jdepend-plugin-1.5'
Loading plugin 'maven-pom-plugin-1.4.1'
Loading plugin 'maven-jira-plugin-1.1.2'
Loading plugin 'maven-overnite-xmlbeans-plugin-1.0'
Loading plugin 'maven-jar-plugin-1.6.1'
Loading plugin 'maven-developer-activity-plugin-1.5.1'
Loading plugin 'maven-jboss-plugin-1.5'
Loading plugin 'maven-faq-plugin-1.4'
Loading plugin 'maven-dist-plugin-1.6.1'
Loading plugin 'maven-javadoc-plugin-1.7'
Loading plugin 'maven-linkcheck-plugin-1.3.4'
Loading plugin 'maven-tasklist-plugin-2.3'
Loading plugin 'maven-idea-plugin-1.5'
Loading plugin 'maven-jcoverage-plugin-1.0.9'
Loading plugin 'maven-junit-report-plugin-1.5'
Loading plugin 'maven-plugin-plugin-1.5.2'
Loading plugin 'maven-jxr-plugin-1.4.2'
Loading plugin 'maven-ashkelon-plugin-1.2'
Loading plugin 'maven-announcement-plugin-1.3'
Loading plugin 'maven-xdoc-plugin-1.8'
Loading plugin 'maven-eclipse-plugin-1.9'
Loading plugin 'maven-shell-plugin-1.1'
Loading plugin 'maven-rar-plugin-1.0'
Loading plugin 'maven-dashboard-plugin-1.6'
Loading plugin 'maven-scm-plugin-1.4.1'
Loading plugin 'maven-clover-plugin-1.6'
Loading plugin 'maven-uberjar-plugin-1.2'
Loading plugin 'maven-war-plugin-1.6.1'
Loading plugin 'maven-simian-plugin-1.4'
Loading plugin 'maven-ant-plugin-1.8.1'
Loading plugin 'maven-ejb-plugin-1.5'
Loading plugin 'maven-tjdo-plugin-1.0.0'
Loading plugin 'maven-changes-plugin-1.5.1'
Loading plugin 'maven-j2ee-plugin-1.5.1'
Loading plugin 'maven-release-plugin-1.4.1'
Loading plugin 'maven-abbot-plugin-1.1'
Loading plugin 'maven-multiproject-plugin-1.3.1'
Loading plugin 'maven-nsis-plugin-1.1'
Loading plugin 'maven-license-plugin-1.2'
Loading plugin 'maven-jdiff-plugin-1.4'
Loading plugin 'maven-pmd-plugin-1.6'
Loading plugin 'maven-repository-plugin-1.2'
Loading plugin 'maven-xdoclet-plugin-1.2.3'
Loading plugin 'andromda-cartridge-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-jbuilder-plugin-1.5'
Loading plugin 'maven-console-plugin-1.1'
Loading plugin 'maven-webserver-plugin-2.0'
Loading plugin 'maven-axis-plugin-0.7'
Loading plugin 'maven-aspectwerkz-plugin-1.2'
Loading plugin 'maven-test-plugin-1.6.2'
Loading plugin 'maven-jetty-plugin-1.1'
Loading plugin 'maven-andromdapp-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'andromda-translation-library-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-docbook-plugin-1.2'
Loading plugin 'maven-latka-plugin-1.4.1'
Loading plugin 'maven-aspectj-plugin-3.2'
Loading plugin 'maven-hibernate-plugin-1.2'
Loading plugin 'maven-native-plugin-1.1'
Loading plugin 'maven-site-plugin-1.5.2'
Loading plugin 'maven-gump-plugin-1.4'
Loading plugin 'maven-appserver-plugin-2.0'
Loading plugin 'maven-java-plugin-1.5'
Loading plugin 'maven-pdf-plugin-2.2.1'
Loading plugin 'maven-html2xdoc-plugin-1.3.1'
Loading plugin 'maven-jdee-plugin-1.1'
Loading plugin 'maven-jalopy-plugin-1.3.1'
Loading plugin 'maven-andromda-plugin-3.0-RC2-SNAPSHOT

Problem with strutsconfigxml part of webdoclet piece of xdoclet plugin for maven

[AAKhopkar]

Hi,

I am using xdoclet1.2.3

I have the apache module setup as a dependency.  However, when I run
webdoclet, no struts-config file is generated.  I do have the apache module
as a dependency.  Here's a snippet:

dependency
  idxdoclet/id
  version1.2.3/version
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-web-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-apache-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

When I run maven xdoclet:webdoclet here's my project.properties file:

maven.xdoclet.webdoclet.strutsconfigxml.0.destinationFile=struts-config-generated.xml

maven.xdoclet.webdoclet.strutsconfigxml.0.destDir=${basedir}/src/webapp/WEB-INF

maven.xdoclet.webdoclet.strutsconfigxml.0.mergeDir=${basedir}/xdocletmerge
maven.xdoclet.webdoclet.strutsconfigxml.0=true
maven.xdoclet.webdoclet.fileset.0.include=**/*.java

maven.xdoclet.webdoclet.strutsconfigxml.0.validateXML=false
maven.xdoclet.webdoclet.strutsconfigxml.0.Version=1.2.4

maven.xdoclet.webdoclet.deploymentdescriptor.0=false
maven.xdoclet.webdoclet.jsptaglib.0=false

When I run with the -X option, here's the output  (As you can see from the
output, the apache module does get loaded):

Please let me know what I'm missing here


 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Initializing Plugins!
Set plugin source directory to C:\apps\maven\plugins
Set unpacked plugin directory to C:\Documents and
Settings\NOUT198\.maven\cache
Set user plugin directory to C:\Documents and
Settings\NOUT198\.maven\plugins
Loading plugin cache
Now mapping cached plugins
Loading plugin 'maven-cruisecontrol-plugin-1.6'
Loading plugin 'maven-multichanges-plugin-1.1'
Loading plugin 'maven-checkstyle-plugin-2.5'
Loading plugin 'maven-file-activity-plugin-1.5.1'
Loading plugin 'maven-jellydoc-plugin-1.3.1'
Loading plugin 'maven-ear-plugin-1.6'
Loading plugin 'maven-jdepend-plugin-1.5'
Loading plugin 'maven-pom-plugin-1.4.1'
Loading plugin 'maven-jira-plugin-1.1.2'
Loading plugin 'maven-overnite-xmlbeans-plugin-1.0'
Loading plugin 'maven-jar-plugin-1.6.1'
Loading plugin 'maven-developer-activity-plugin-1.5.1'
Loading plugin 'maven-jboss-plugin-1.5'
Loading plugin 'maven-faq-plugin-1.4'
Loading plugin 'maven-dist-plugin-1.6.1'
Loading plugin 'maven-javadoc-plugin-1.7'
Loading plugin 'maven-linkcheck-plugin-1.3.4'
Loading plugin 'maven-tasklist-plugin-2.3'
Loading plugin 'maven-idea-plugin-1.5'
Loading plugin 'maven-jcoverage-plugin-1.0.9'
Loading plugin 'maven-junit-report-plugin-1.5'
Loading plugin 'maven-plugin-plugin-1.5.2'
Loading plugin 'maven-jxr-plugin-1.4.2'
Loading plugin 'maven-ashkelon-plugin-1.2'
Loading plugin 'maven-announcement-plugin-1.3'
Loading plugin 'maven-xdoc-plugin-1.8'
Loading plugin 'maven-eclipse-plugin-1.9'
Loading plugin 'maven-shell-plugin-1.1'
Loading plugin 'maven-rar-plugin-1.0'
Loading plugin 'maven-dashboard-plugin-1.6'
Loading plugin 'maven-scm-plugin-1.4.1'
Loading plugin 'maven-clover-plugin-1.6'
Loading plugin 'maven-uberjar-plugin-1.2'
Loading plugin 'maven-war-plugin-1.6.1'
Loading plugin 'maven-simian-plugin-1.4'
Loading plugin 'maven-ant-plugin-1.8.1'
Loading plugin 'maven-ejb-plugin-1.5'
Loading plugin 'maven-tjdo-plugin-1.0.0'
Loading plugin 'maven-changes-plugin-1.5.1'
Loading plugin 'maven-j2ee-plugin-1.5.1'
Loading plugin 'maven-release-plugin-1.4.1'
Loading plugin 'maven-abbot-plugin-1.1'
Loading plugin 'maven-multiproject-plugin-1.3.1'
Loading plugin 'maven-nsis-plugin-1.1'
Loading plugin 'maven-license-plugin-1.2'
Loading plugin 'maven-jdiff-plugin-1.4'
Loading plugin 'maven-pmd-plugin-1.6'
Loading plugin 'maven-repository-plugin-1.2'
Loading plugin 'maven-xdoclet-plugin-1.2.3'
Loading plugin 'andromda-cartridge-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-jbuilder-plugin-1.5'
Loading plugin 'maven-console-plugin-1.1'
Loading plugin 'maven-webserver-plugin-2.0'
Loading plugin 'maven-axis-plugin-0.7'
Loading plugin 'maven-aspectwerkz-plugin-1.2'
Loading plugin 'maven-test-plugin-1.6.2'
Loading plugin 'maven-jetty-plugin-1.1'
Loading plugin 'maven-andromdapp-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'andromda-translation-library-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-docbook-plugin-1.2'
Loading plugin 'maven-latka-plugin-1.4.1'
Loading plugin 'maven-aspectj-plugin-3.2'
Loading plugin 'maven-hibernate-plugin-1.2'
Loading plugin 'maven-native-plugin-1.1'
Loading plugin 'maven-site-plugin-1.5.2'
Loading plugin 'maven-gump-plugin-1.4'
Loading plugin 'maven-appserver-plugin-2.0'
Loading plugin 'maven-java-plugin-1.5'
Loading plugin 'maven-pdf-plugin-2.2.1'
Loading plugin 'maven-html2xdoc-plugin-1.3.1'
Loading plugin 'maven-jdee-plugin-1.1'
Loading plugin 'maven-jalopy-plugin-1.3.1'
Loading plugin 'maven-andromda-plugin-3.0-RC2-SNAPSHOT

Re: Problem with strutsconfigxml part of webdoclet piece of xdoclet plugin for maven

[Felipe Leme]

Changing the subject a little bit, is XDoclet 1.2.3 already in a public
maven repository?

I'm asking because I have to use that version and had to setup it
locally in my machine (I didn't want to open a MAVENUPLOAD REQUEST for
it, as there are dozens of jars to be bundled and I was too lazy to pack
them :-).

-- Felipe


On Fri, 2005-05-20 at 15:10 -0400, [EMAIL PROTECTED] wrote:

 I am using xdoclet1.2.3



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Problem with strutsconfigxml piece of webdoclet piece of xdoclet plugin for maven

[AAKhopkar]

Hi,

I am using xdoclet1.2.3

I have the apache module setup as a dependency.  However, when I run
webdoclet, no struts-config file is generated.  I do have the apache module
as a dependency.  Here's a snippet:

dependency
  idxdoclet/id
  version1.2.3/version
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-web-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

dependency
  groupIdxdoclet/groupId
  artifactIdxdoclet-apache-module/artifactId
  version1.2.3/version
  urlhttp://xdoclet.sf.net//url
/dependency

When I run maven xdoclet:webdoclet here's my project.properties file:

maven.xdoclet.webdoclet.strutsconfigxml.0.destinationFile=struts-config-generated.xml
maven.xdoclet.webdoclet.strutsconfigxml.0.destDir=${basedir}/src/webapp/WEB-INF
maven.xdoclet.webdoclet.strutsconfigxml.0.mergeDir=${basedir}/xdocletmerge
maven.xdoclet.webdoclet.strutsconfigxml.0=true
maven.xdoclet.webdoclet.fileset.0.include=**/*.java

maven.xdoclet.webdoclet.strutsconfigxml.0.validateXML=false
maven.xdoclet.webdoclet.strutsconfigxml.0.Version=1.2.4

maven.xdoclet.webdoclet.deploymentdescriptor.0=false
maven.xdoclet.webdoclet.jsptaglib.0=false

When I run with the -X option, here's the output  (As you can see from the
output, the apache module does get loaded):

Please let me know what I'm missing here


 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Initializing Plugins!
Set plugin source directory to C:\apps\maven\plugins
Set unpacked plugin directory to C:\Documents and
Settings\NOUT198\.maven\cache
Set user plugin directory to C:\Documents and
Settings\NOUT198\.maven\plugins
Loading plugin cache
Now mapping cached plugins
Loading plugin 'maven-cruisecontrol-plugin-1.6'
Loading plugin 'maven-multichanges-plugin-1.1'
Loading plugin 'maven-checkstyle-plugin-2.5'
Loading plugin 'maven-file-activity-plugin-1.5.1'
Loading plugin 'maven-jellydoc-plugin-1.3.1'
Loading plugin 'maven-ear-plugin-1.6'
Loading plugin 'maven-jdepend-plugin-1.5'
Loading plugin 'maven-pom-plugin-1.4.1'
Loading plugin 'maven-jira-plugin-1.1.2'
Loading plugin 'maven-overnite-xmlbeans-plugin-1.0'
Loading plugin 'maven-jar-plugin-1.6.1'
Loading plugin 'maven-developer-activity-plugin-1.5.1'
Loading plugin 'maven-jboss-plugin-1.5'
Loading plugin 'maven-faq-plugin-1.4'
Loading plugin 'maven-dist-plugin-1.6.1'
Loading plugin 'maven-javadoc-plugin-1.7'
Loading plugin 'maven-linkcheck-plugin-1.3.4'
Loading plugin 'maven-tasklist-plugin-2.3'
Loading plugin 'maven-idea-plugin-1.5'
Loading plugin 'maven-jcoverage-plugin-1.0.9'
Loading plugin 'maven-junit-report-plugin-1.5'
Loading plugin 'maven-plugin-plugin-1.5.2'
Loading plugin 'maven-jxr-plugin-1.4.2'
Loading plugin 'maven-ashkelon-plugin-1.2'
Loading plugin 'maven-announcement-plugin-1.3'
Loading plugin 'maven-xdoc-plugin-1.8'
Loading plugin 'maven-eclipse-plugin-1.9'
Loading plugin 'maven-shell-plugin-1.1'
Loading plugin 'maven-rar-plugin-1.0'
Loading plugin 'maven-dashboard-plugin-1.6'
Loading plugin 'maven-scm-plugin-1.4.1'
Loading plugin 'maven-clover-plugin-1.6'
Loading plugin 'maven-uberjar-plugin-1.2'
Loading plugin 'maven-war-plugin-1.6.1'
Loading plugin 'maven-simian-plugin-1.4'
Loading plugin 'maven-ant-plugin-1.8.1'
Loading plugin 'maven-ejb-plugin-1.5'
Loading plugin 'maven-tjdo-plugin-1.0.0'
Loading plugin 'maven-changes-plugin-1.5.1'
Loading plugin 'maven-j2ee-plugin-1.5.1'
Loading plugin 'maven-release-plugin-1.4.1'
Loading plugin 'maven-abbot-plugin-1.1'
Loading plugin 'maven-multiproject-plugin-1.3.1'
Loading plugin 'maven-nsis-plugin-1.1'
Loading plugin 'maven-license-plugin-1.2'
Loading plugin 'maven-jdiff-plugin-1.4'
Loading plugin 'maven-pmd-plugin-1.6'
Loading plugin 'maven-repository-plugin-1.2'
Loading plugin 'maven-xdoclet-plugin-1.2.3'
Loading plugin 'andromda-cartridge-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-jbuilder-plugin-1.5'
Loading plugin 'maven-console-plugin-1.1'
Loading plugin 'maven-webserver-plugin-2.0'
Loading plugin 'maven-axis-plugin-0.7'
Loading plugin 'maven-aspectwerkz-plugin-1.2'
Loading plugin 'maven-test-plugin-1.6.2'
Loading plugin 'maven-jetty-plugin-1.1'
Loading plugin 'maven-andromdapp-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'andromda-translation-library-plugin-3.0-RC2-SNAPSHOT'
Loading plugin 'maven-docbook-plugin-1.2'
Loading plugin 'maven-latka-plugin-1.4.1'
Loading plugin 'maven-aspectj-plugin-3.2'
Loading plugin 'maven-hibernate-plugin-1.2'
Loading plugin 'maven-native-plugin-1.1'
Loading plugin 'maven-site-plugin-1.5.2'
Loading plugin 'maven-gump-plugin-1.4'
Loading plugin 'maven-appserver-plugin-2.0'
Loading plugin 'maven-java-plugin-1.5'
Loading plugin 'maven-pdf-plugin-2.2.1'
Loading plugin 'maven-html2xdoc-plugin-1.3.1'
Loading plugin 'maven-jdee-plugin-1.1'
Loading plugin 'maven-jalopy-plugin-1.3.1'
Loading plugin 'maven-andromda-plugin-3.0-RC2-SNAPSHOT

Newbie: maven and xdoclet without the xdoclet-plugin - No results

[Louis Burroughs]

I was running the xdoclet plugin for maven and was having trouble with 
error messages telling me that I had files in more than one fileset.  So I 
decided to scale back and take a working ant script and incorporate it 
into my maven.xml.  The script runs to completion and tells me that the 
build passed, but nothing is created.  I pasted the verbose output from 
maven below and you can see where Ant is loading classes and appears to be 
ready to execute the task, it then terminates without generating the files 
or giving an error.  Anybody point me in the right direction?  Thanks!

PS - I have also posted this to the xdoclet user list.


goal name=webdoclet_goal
description=Generate deployment descriptors

echo
 +---+
/echo
echo|-|/echo
echo| R U N N I N G W E B D O C L E T |/echo
echo|_|/echo
echo
 +---+
/echo
echoTaskdef./echo
taskdef name=webdoclet_a
classname=xdoclet.modules.web.WebDocletTask
classpath
path refid=maven.dependency.classpath /
pathelement

path=${pom.getDependencyPath('xdoclet:xdoclet-web-module')} /
pathelement

path=${pom.getDependencyPath('xdoclet:xdoclet-ibm-module')} /
pathelement

path=${pom.getDependencyPath('xdoclet:xdoclet')} /
pathelement

path=${pom.getDependencyPath('xjavadoc:xjavadoc')} /
pathelement

path=${pom.getDependencyPath('xdoclet:xdoclet-xdoclet-module')} /
pathelement

path=${pom.getDependencyPath('commons-collections:commons-collections')} /
pathelement

path=${pom.getDependencyPath('commons-logging:commons-logging')} /
pathelement

path=${pom.getDependencyPath('log4j:log4j')} /
/classpath
/taskdef

tstamp
echoTimestamp.../echo
format property=TODAY pattern=d-MM-yy /
/tstamp
webdoclet_a destdir=${maven.xdoclet.webdoclet.destDir}
mergedir=${maven.xdoclet.webdoclet.mergedir}
excludedtags=@version,@author,@todo
addedtags=@xdoclet-generated at ${TODAY},@copyright 
The XDoclet Team,@author 
XDoclet
force=false verbose=true
echoWebdoclet../echo
fileset dir=${basedir}/JavaSource
echoFileset../echo
include name=**/*.java /
/fileset
echoDeployment Descriptor/echo
deploymentdescriptor servletspec=2.3
sessiontimeout=65 
destdir=${maven.xdoclet.webdoclet.destDir}
displayname=PSO_TEST /
echoXMI files../echo
webspherewebxml virtualHostName=pso_host
destdir=${maven.xdoclet.webdoclet.destDir}
fileServingEnabled=false validateXml=false
directoryBrowsingEnabled=false
serveServletsByClassnameEnabled=false 
preCompileJSPs=false /
echoExit webdoclet./echo
/webdoclet_a
/goal



webdoclet_goal:
[echo] 
 +---+
 
[echo] |-|
[echo] | R U N N I N G W E B D O C L E T |
[echo] |_|
[echo] 
 +---+
 
[taskdef] [DEBUG] Finding class xdoclet.modules.web.WebDocletTask
[taskdef] [DEBUG] Finding class xdoclet.DocletTask
[taskdef] [DEBUG] Finding class xjavadoc.ant.XJavadocTask
[taskdef] [DEBUG] Class org.apache.tools.ant.Task loaded from parent 
loader
[taskdef] [DEBUG] Class xjavadoc.ant.XJavadocTask loaded from ant 
loader
[taskdef] [DEBUG] Class org.apache.tools.ant.DynamicConfigurator 
loaded from parent loader
[taskdef] [DEBUG] Class xdoclet.DocletTask loaded from ant loader
[taskdef] [DEBUG] Class

Maven Xdoclet plugin question

[Poppe, Troy]

I have an ant script with the following ejbdoclet task being executed, and I'd
like to convert this to Maven.  I'm working on editing my project.properties, and
setting up the appropriate maven.xdoclet.ejbdoclet properties.  I'm a little
stumped at how I would do the packageSubstitution that I am currently doing.

You'll notice that there is a packageSubstitution for each subtask of ejbdoclet.
The intention is to get all the interfaces into one package, and the VOs into
another, with CMP, BMP, and Session implementations in their own packages.

I cannot for the life of me figure out what the properties would be to get each
subtask to use a different packageSubstitution.  I think at least part of my
confusion is the whole index thing with the property names.

Any help would be greatly appreciated!

Thanks.

Troy


[-- snip --]



 ejbdoclet
destdir=${ejbsrc.dir}
mergedir=${ejb.dd.dir}
excludedtags=@version,@author,@todo
addedtags=@lomboz generated
ejbspec=2.0
force=${xdoclet.force}
verbose=true 


   fileset dir=../src defaultexcludes=yes
 patternset include=**/*Bean.java /
   /fileset

 valueobject
 packageSubstitution packages=pms substituteWith=pms.vo/
 /valueobject
 utilobject cacheHomes=true includeGUID=true
 /utilobject
 remoteinterface
 packageSubstitution packages=pms
substituteWith=pms.interfaces/
 /remoteinterface
 localinterface
 packageSubstitution packages=pms
substituteWith=pms.interfaces/
 /localinterface
 homeinterface
 packageSubstitution packages=pms
substituteWith=pms.interfaces/
 /homeinterface
 localhomeinterface
 packageSubstitution packages=pms
substituteWith=pms.interfaces/
 /localhomeinterface
 
 entitypk/
 entitycmp
 packageSubstitution packages=pms substituteWith=pms.cmp/
 /entitycmp
 entitybmp
 packageSubstitution packages=pms substituteWith=pms.bmp/
 /entitybmp
 session
 packageSubstitution packages=pms
substituteWith=pms.session/
 /session

 deploymentdescriptor 
destdir=${ejb.dd.dir} 
validatexml=false
mergedir=${ejb.dd.dir} /

  jboss
 version=3.0
 unauthenticatedPrincipal=nobody
 xmlencoding=UTF-8
 destdir=${ejb.dd.dir}
 validatexml=false
 datasource=java:/jdbc/PMSDS
 datasourcemapping=Oracle9i
 preferredrelationmapping=relation-table
 createTable = false
 removeTable = false/

  orion 
 destdir=${ejb.dd.dir}/
  /ejbdoclet


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven Xdoclet plugin question

[Eric Pugh]

Have you looked at the Xdoclet maven plugin? It does some pretty funky
setting of properties.  I ended up cribbing from it to do what I needed it
to do.

Eric

 -Original Message-
 From: Poppe, Troy [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, August 11, 2004 11:02 PM
 To: Maven Users List
 Subject: Maven Xdoclet plugin question



 I have an ant script with the following ejbdoclet task being
 executed, and I'd
 like to convert this to Maven.  I'm working on editing my
 project.properties, and
 setting up the appropriate maven.xdoclet.ejbdoclet properties.
 I'm a little
 stumped at how I would do the packageSubstitution that I am
 currently doing.

 You'll notice that there is a packageSubstitution for each
 subtask of ejbdoclet.
 The intention is to get all the interfaces into one package, and
 the VOs into
 another, with CMP, BMP, and Session implementations in their own packages.

 I cannot for the life of me figure out what the properties would
 be to get each
 subtask to use a different packageSubstitution.  I think at least
 part of my
 confusion is the whole index thing with the property names.

 Any help would be greatly appreciated!

 Thanks.

 Troy


 [-- snip --]



  ejbdoclet
 destdir=${ejbsrc.dir}
 mergedir=${ejb.dd.dir}
 excludedtags=@version,@author,@todo
 addedtags=@lomboz generated
 ejbspec=2.0
 force=${xdoclet.force}
 verbose=true 


  fileset dir=../src defaultexcludes=yes
patternset include=**/*Bean.java /
  /fileset

  valueobject
packageSubstitution packages=pms
 substituteWith=pms.vo/
  /valueobject
  utilobject cacheHomes=true includeGUID=true
  /utilobject
  remoteinterface
packageSubstitution packages=pms
 substituteWith=pms.interfaces/
  /remoteinterface
  localinterface
packageSubstitution packages=pms
 substituteWith=pms.interfaces/
/localinterface
  homeinterface
packageSubstitution packages=pms
 substituteWith=pms.interfaces/
/homeinterface
  localhomeinterface
packageSubstitution packages=pms
 substituteWith=pms.interfaces/
/localhomeinterface

  entitypk/
  entitycmp
packageSubstitution packages=pms
 substituteWith=pms.cmp/
  /entitycmp
  entitybmp
packageSubstitution packages=pms
 substituteWith=pms.bmp/
  /entitybmp
  session
packageSubstitution packages=pms
 substituteWith=pms.session/
  /session

  deploymentdescriptor
 destdir=${ejb.dd.dir}
 validatexml=false
 mergedir=${ejb.dd.dir} /

 jboss
  version=3.0
  unauthenticatedPrincipal=nobody
  xmlencoding=UTF-8
  destdir=${ejb.dd.dir}
  validatexml=false
  datasource=java:/jdbc/PMSDS
  datasourcemapping=Oracle9i
  preferredrelationmapping=relation-table
  createTable = false
  removeTable = false/

   orion
  destdir=${ejb.dd.dir}/
   /ejbdoclet


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven Xdoclet plugin question

[M.-Leander Reimer]

Jey Troy,
here is are a few examples of my ejbdoclet properties adapted to your 
packages:

maven.xdoclet.ejbdoclet.utilobject.0   
= true
maven.xdoclet.ejbdoclet.utilobject.0.Kind
   = physical
maven.xdoclet.ejbdoclet.utilobject.0.cacheHomes
   = true
maven.xdoclet.ejbdoclet.utilobject.0.includeGUID
   = true

maven.xdoclet.ejbdoclet.valueobject.0
   = true
maven.xdoclet.ejbdoclet.valueobject.0.PackageSubstitution.0
= true
maven.xdoclet.ejbdoclet.valueobject.0.PackageSubstitution.0.packages
 = pms
maven.xdoclet.ejbdoclet.valueobject.0.PackageSubstitution.0.substituteWith
  = pms.vo

maven.xdoclet.ejbdoclet.remoteinterface.0  
= true
maven.xdoclet.ejbdoclet.remoteinterface.0.PackageSubstitution.0  
 = true
maven.xdoclet.ejbdoclet.remoteinterface.0.PackageSubstitution.0.packages 
   = pms
maven.xdoclet.ejbdoclet.remoteinterface.0.PackageSubstitution.0.substituteWith  
   = pms.interfaces

If you need multiple package substitutions for a subtask you have to 
increment the PackageSubstition index, e.g.

maven.xdoclet.ejbdoclet.remoteinterface.0.PackageSubstitution.1  
 = true
maven.xdoclet.ejbdoclet.remoteinterface.0.PackageSubstitution.1.packages 
   = pms.other
maven.xdoclet.ejbdoclet.remoteinterface.0.PackageSubstitution.1.substituteWith  
   = pms.other.interfaces

You have to be a bit careful, sometimes I found that the actual maven 
plugin property names differ from the ant task attributes, so if 
something doesn't work you better look into the xdoclet plugin's jelly 
script. But I think with the 1.2.1 version things are pretty consistent now.

Hope that helps.
Leander
Poppe, Troy schrieb:
I have an ant script with the following ejbdoclet task being executed, and I'd
like to convert this to Maven.  I'm working on editing my project.properties, and
setting up the appropriate maven.xdoclet.ejbdoclet properties.  I'm a little
stumped at how I would do the packageSubstitution that I am currently doing.
You'll notice that there is a packageSubstitution for each subtask of ejbdoclet.
The intention is to get all the interfaces into one package, and the VOs into
another, with CMP, BMP, and Session implementations in their own packages.
I cannot for the life of me figure out what the properties would be to get each
subtask to use a different packageSubstitution.  I think at least part of my
confusion is the whole index thing with the property names.
Any help would be greatly appreciated!
Thanks.
Troy
[-- snip --]

ejbdoclet
   destdir=${ejbsrc.dir}
   mergedir=${ejb.dd.dir}
   excludedtags=@version,@author,@todo
   addedtags=@lomboz generated
   ejbspec=2.0
   force=${xdoclet.force}
   verbose=true 
   fileset dir=../src defaultexcludes=yes
 patternset include=**/*Bean.java /
   /fileset
valueobject
	 packageSubstitution packages=pms substituteWith=pms.vo/
/valueobject
utilobject cacheHomes=true includeGUID=true
/utilobject
remoteinterface
	 packageSubstitution packages=pms
substituteWith=pms.interfaces/
/remoteinterface
localinterface
	 packageSubstitution packages=pms
substituteWith=pms.interfaces/
	 /localinterface
homeinterface
	 packageSubstitution packages=pms
substituteWith=pms.interfaces/
	 /homeinterface
localhomeinterface
  	 packageSubstitution packages=pms
substituteWith=pms.interfaces/
  	 /localhomeinterface

entitypk/
entitycmp
  	 packageSubstitution packages=pms substituteWith=pms.cmp/
/entitycmp
entitybmp
  	 packageSubstitution packages=pms substituteWith=pms.bmp/
/entitybmp
session
	 packageSubstitution packages=pms
substituteWith=pms.session/
/session

deploymentdescriptor 
   destdir=${ejb.dd.dir} 
   validatexml=false
   mergedir=${ejb.dd.dir} /

  jboss
version=3.0
unauthenticatedPrincipal=nobody
xmlencoding=UTF-8
destdir=${ejb.dd.dir}
validatexml=false
datasource=java:/jdbc/PMSDS
datasourcemapping=Oracle9i
preferredrelationmapping=relation-table
createTable = false
removeTable = false/
 orion 
destdir=${ejb.dd.dir}/
 /ejbdoclet

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

Maven-Xdoclet-plugin to generate struts-config.xml ????

[Eric Chow]

Hello,


I want to use SSLExt for Struts.

In my struts-config.xml, I have to add something in the action-mapping/ as
following:

action-mappings type=org.apache.struts.config.SecureActionConfig
action path=/call
 type=com.echows.ejcourse.portal.action.RedirectAction
 scope=request
  
 set-property property=secure value=false/
  /action
/action-mappings


I will set the type of action-mappings as
org.apache.struts.config.SecureActionConfig.


How can I define this

Eric

==
If you know what you are doing,
it is not called RESEARCH!
==


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

xdoclet plugin problem

[Nathan Coast]

Hi,
I've just started trying to use ejbdoclet task from the xdoclet plugin 
with maven rc3 and I'm getting the following error:

taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
If I output the classpath passed to the taskdef command, I get the 
following:
D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-ejb-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-jboss-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-jmx-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\jboss\jars\jboss-j2ee-3.2.3.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-xdoclet-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\commons-collections\jars\commons-collections-2.1.jar;D:\apache\Maven-1.0-rc3\repository\commons-logging\jars\commons-logging-1.1-dev.jar;D:\apache\Maven-1.0-rc3\repository\log4j\jars\log4j-1.2.6.jar

xdoclet.modules.ejb.EjbDocletTask is within the jar:
D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-ejb-module-1.2.jar
any ideas?
is anyone successfully using the xdoclet plugin with maven rc3?
cheers
Nathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: xdoclet plugin problem

[Nathan Coast]

well I fixed (workaround) the problem by using the deprecated
properties
  classloaderroot/classloader
/properties
for the plugin's dependencies .
I checked the FAQ http://maven.apache.org/faq.html#classloader-property 
as instructed by the deprecation warning.  Does this mean the xdoclet 
team need to update their plugin?

cheers
Nathan
Nathan Coast wrote:
Hi,
I've just started trying to use ejbdoclet task from the xdoclet plugin 
with maven rc3 and I'm getting the following error:

taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
If I output the classpath passed to the taskdef command, I get the 
following:
D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-ejb-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-jboss-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-jmx-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\jboss\jars\jboss-j2ee-3.2.3.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-xdoclet-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\commons-collections\jars\commons-collections-2.1.jar;D:\apache\Maven-1.0-rc3\repository\commons-logging\jars\commons-logging-1.1-dev.jar;D:\apache\Maven-1.0-rc3\repository\log4j\jars\log4j-1.2.6.jar 

xdoclet.modules.ejb.EjbDocletTask is within the jar:
D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-ejb-module-1.2.jar
any ideas?
is anyone successfully using the xdoclet plugin with maven rc3?
cheers
Nathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: xdoclet plugin problem

[Nathan Coast]

I just modified the xdoclet plugin in accordance with the docs and I get 
back to the original problem of:

taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
any suggestions as to how to fix the problem without the root 
classloader workaround?

Nathan Coast wrote:
well I fixed (workaround) the problem by using the deprecated
properties
  classloaderroot/classloader
/properties
for the plugin's dependencies .
I checked the FAQ http://maven.apache.org/faq.html#classloader-property 
as instructed by the deprecation warning.  Does this mean the xdoclet 
team need to update their plugin?

cheers
Nathan
Nathan Coast wrote:
Hi,
I've just started trying to use ejbdoclet task from the xdoclet plugin 
with maven rc3 and I'm getting the following error:

taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
If I output the classpath passed to the taskdef command, I get the 
following:
D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-ejb-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-jboss-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-jmx-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\jboss\jars\jboss-j2ee-3.2.3.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-1.2.jar;D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-xdoclet-module-1.2.jar;D:\apache\Maven-1.0-rc3\repository\commons-collections\jars\commons-collections-2.1.jar;D:\apache\Maven-1.0-rc3\repository\commons-logging\jars\commons-logging-1.1-dev.jar;D:\apache\Maven-1.0-rc3\repository\log4j\jars\log4j-1.2.6.jar 

xdoclet.modules.ejb.EjbDocletTask is within the jar:
D:\apache\Maven-1.0-rc3\repository\xdoclet\jars\xdoclet-ejb-module-1.2.jar 

any ideas?
is anyone successfully using the xdoclet plugin with maven rc3?
cheers
Nathan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven XDoclet Plugin and the maven.xdoclet.ejbdoclet.fileset property

[Konstantin Priblouda]

--- Webb Morris [EMAIL PROTECTED] wrote:
 I've been thinking about what Konstantin said below:
 
 And you always have option to use ant invokation for
 xdoclet tasks un your maven.xml  - this is prefererd
 way for xdoclet 2 ( at least there is no maven
 plugin
 planned, because everything got easier ) 
 
 It seems to me, that no matter how much easier
 things got with the new XDoclet 2 way of doing
 things, that wrapping up that functionality in a
 plugin would still be preferable.  That way, you
 wouldn't have to keep writing the same snippet of
 maven.xml over and over again for each project
 that used XDoclet. Perhaps my ignorance of how easy
 things in XDoclet 2 are going to be is at
 fault here, but there are plugins available for
 lot's of easy tasks (JAR for instance) that make
 life much simpler.

That's my invocation of xdoclet 2 in maven:
---%---
  goal name=xdoclet-all
path id=xdoclet.task.classpath
pathelement location=${basedir}/src/main/merge/
pathelement location=${basedir}/src/test//
path refid=maven.dependency.classpath/
/path

taskdef
name=xdoclet
classname=org.xdoclet.ant.XDocletTask
classpathref=xdoclet.task.classpath
/
   xdoclet
fileset
dir=${pom.build.sourceDirectory}
include name=**/*.java/
/fileset

 component
 
classname=org.xdoclet.plugin.hibernate.HibernateMappingPlugin
 
destdir=${basedir}/target/xdoclet/hibernatedoclet
  / 
  component
 
classname=org.xdoclet.plugin.webwork.ViewsPropertiesPlugin
 
destdir=${basedir}/target/xdoclet/webdoclet
  /
  component
 
classname=org.xdoclet.plugin.externalizer.MessageBundlePlugin
 
destdir=${basedir}/target/xdoclet/xdoclet
  /
  component
 
classname=org.xdoclet.plugin.externalizer.PropertiesTranslatorPlugin
 
destdir=${basedir}/target/xdoclet/xdoclet
  / 
/xdoclet

path id=xdoclet.java.compile.src.set
location=${basedir}/target/xdoclet/xdoclet/
maven:addPath id=maven.compile.src.set
refid=xdoclet.java.compile.src.set/
  /goal
---%

As you may see ( or not :) ) ant task for xdoclet-2
is basically a picocontainer, where you just drop
components you deem appropriate. 

( and you may as well use several instances of same
task ) 

Yes, it's possible to wrap in plugin, but it would 
require a lot of properties to set up

I prefer this way. Though taskdef part could be
factored out. 


regards,



=
[ Konstantin Pribluda ( ko5tik ) ]
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung. 
Arbeitsort: Mainz 
Skills:  Programieren, Kentnisse in OpenSource-Bereich
[ http://www.pribluda.de ]




__
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25¢
http://photos.yahoo.com/ph/print_splash

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Maven XDoclet Plugin and the maven.xdoclet.ejbdoclet.fileset property

[Konstantin Priblouda]

--- Webb Morris [EMAIL PROTECTED] wrote:
 Everyone,
 
 In the XDoclet Plugin, when you specify the filesets
 for the ejbdoclet task, the task always
 assumes the files will be in
 pom.build.sourceDirectory.  I think this is rather
 short-sighted
 (mainly because I have some filesets that are not in
 that directory ;) ).  Anyway, this would be
 simple enough to fix by adding the additional
 maven.xdoclet.ejbdoclet.fileset.0.directory
 attribute for all specified filesets.  My real
 question is who do I approach about this fix?  How
 can I ensure that it makes it into the next plugin
 release?  Sorry for the newbee-ish questions,
 but I couldn't find a good jumping off point at the
 XDoclet site that deals specifically with
 plugin patches.

plugin.jelly for xdoclet plugin is generated
automatically ( surprisingly by xdoclet itself )  - so

the pathces shall be done to the respective template
( AFAIR ) in  the xdoclet-xdoclet module. 

And you always have option to use ant invokation for
xdoclet tasks un your maven.xml  - this is prefererd
way for xdoclet 2 ( at least there is no maven plugin
planned, because everything got easier ) 

regards,

=
[ Konstantin Pribluda ( ko5tik ) ]
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung. 
Arbeitsort: Mainz 
Skills:  Programieren, Kentnisse in OpenSource-Bereich
[ http://www.pribluda.de ]




__
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven XDoclet Plugin and the maven.xdoclet.ejbdoclet.fileset property

[Webb Morris]

Everyone,

In the XDoclet Plugin, when you specify the filesets for the ejbdoclet task, the task 
always
assumes the files will be in pom.build.sourceDirectory.  I think this is rather 
short-sighted
(mainly because I have some filesets that are not in that directory ;) ).  Anyway, 
this would be
simple enough to fix by adding the additional 
maven.xdoclet.ejbdoclet.fileset.0.directory
attribute for all specified filesets.  My real question is who do I approach about 
this fix?  How
can I ensure that it makes it into the next plugin release?  Sorry for the newbee-ish 
questions,
but I couldn't find a good jumping off point at the XDoclet site that deals 
specifically with
plugin patches.

WM




__
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: What does the XDoclet plugin expects?

[Konstantin Priblouda]

--- Marco Tedone [EMAIL PROTECTED] wrote:
 I've defined your same properties, defined ejbdoclet
 as pregoal and I'm
 obtaining the following error:
 
 ant:javac srcdir

D:\Projects\jemos-xmlop-1.0\src\target\xdoclet\ejbdoclet
 does not exist!
 
 The ejbdoclet goal is looking for a
 src/target/xdoclet/ejbdoclet folder that
 doesn't exists. Shall I create it?

It's not xdoclet that barfed, it's javac which had
missed directory where xdoclet generated sources shall
be. xdoclet pljugin registered it for javac.

 I've got the following package:
 
 /src
   |
   java (src folder)
 |
 org (package begins)
   |
   --jemos
   |
   --xmlop
   |
  
 OneNormalClass.java
  
 SecondNormalClass.java
   FirstEJB.java 
(Entity)
  
 FirstBeanSession.java  (Session)
 
 In the following property I declared  the following:
 

maven.xdoclet.xdoclet.fileset.0.include=**/*EJB.java,
 **/*Bean.java

Shall be  maven.xdoclet.ejbdoclet.fileset - we are
calling ejbdoclet.
( respectively webdoclet, ejbdoclet, hibernatedoclet
etc )  

 Is it ok? (I mean the use of the comma).

Yes. And you did not forgot to say:
maven.xdoclet.ejbdoclet.fileset.0=true ?


 Is there a standard directory structure I could
 follow when creating EJBs
 with Maven?

Also check that you got proper dependencies specified
- 
xdoclet-ejbdoclet module, jar containing javax.ejb.* 
etc.


regards,

=
[ Konstantin Pribluda ( ko5tik ) ]
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung. 
Arbeitsort: Mainz 
Skills:  Programieren, Kentnisse in OpenSource-Bereich
[ http://www.pribluda.de ]

__
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: What does the XDoclet plugin expects?

[Marco Tedone]

I've defined your same properties, defined ejbdoclet as pregoal and I'm
obtaining the following error:

ant:javac srcdir
D:\Projects\jemos-xmlop-1.0\src\target\xdoclet\ejbdoclet does not exist!

The ejbdoclet goal is looking for a src/target/xdoclet/ejbdoclet folder that
doesn't exists. Shall I create it?

I've got the following package:

/src
  |
  java (src folder)
|
org (package begins)
  |
  --jemos
  |
  --xmlop
  |
  OneNormalClass.java
  SecondNormalClass.java
  FirstEJB.java (Entity)
  FirstBeanSession.java  (Session)

In the following property I declared  the following:

maven.xdoclet.xdoclet.fileset.0.include=**/*EJB.java, **/*Bean.java

Is it ok? (I mean the use of the comma).

Is there a standard directory structure I could follow when creating EJBs
with Maven?

Many thanks,

Marco

- Original Message - 
From: Konstantin Priblouda [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]; Marco Tedone
[EMAIL PROTECTED]
Sent: Monday, March 15, 2004 7:26 PM
Subject: Re: What does the XDoclet plugin expects?



 --- Marco Tedone [EMAIL PROTECTED] wrote:
  Hi, I'm reading the documentation on the XDoclet
  website about the Maven
  plugin. However, I don't know what the
  xdoclet:ejbdoclet goal expects in
  the maven.xml file. I've got a folder /src under
  which java, webapp, etc.
  are stored. When I point my cursor to /src and type
  maven
  xdoclet:ejbdoclet nothing happens.
 

 you will need some properties and dependencies to
 activate subtasks

 Like this:

 ---%-
 #message bundles
 maven.xdoclet.xdoclet.destDir=${basedir}/target/xdoclet/xdoclet
 maven.xdoclet.xdoclet.externalizer.0=true
 maven.xdoclet.xdoclet.externalizer.0.destinationFile={0}{1}.properties

 maven.xdoclet.xdoclet.propertiestranslator.0=true
 maven.xdoclet.xdoclet.fileset.0=true
 maven.xdoclet.xdoclet.fileset.0.include=**/*.java
 ---%-

 Here I activate 2 subtasks ( externalizer / properties
 translator ) ,
 specify  fileset for eintire xdoclet invocation, and
 some task specific
 settings ( for example name pattern for generated
 properties  )

 then I need to specify desired task ( xdoclet:xdoclet
 ) as pregoal,
 and possibly tune my project xml so  that generated
 artifacts are packaged , or included in classpath of
 unit tests.

 regards,




 =
 [ Konstantin Pribluda ( ko5tik ) ]
 Zu Verstärkung meines Teams suche ich ab Sofort einen
 Softwareentwickler[In] für die Festanstellung.
 Arbeitsort: Mainz
 Skills:  Programieren, Kentnisse in OpenSource-Bereich
 [ http://www.pribluda.de ]

 __
 Do you Yahoo!?
 Yahoo! Mail - More reliable, more storage, less spam
 http://mail.yahoo.com





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: What does the XDoclet plugin expects?

[Webb Morris]

You should be running maven from the jemos-xmlop-1.0 directory, not the src directory.

WM


--- Marco Tedone [EMAIL PROTECTED] wrote:
 I've defined your same properties, defined ejbdoclet as pregoal and I'm
 obtaining the following error:
 
 ant:javac srcdir
 D:\Projects\jemos-xmlop-1.0\src\target\xdoclet\ejbdoclet does not exist!
 
 The ejbdoclet goal is looking for a src/target/xdoclet/ejbdoclet folder that
 doesn't exists. Shall I create it?
 
 I've got the following package:
 
 /src
   |
   java (src folder)
 |
 org (package begins)
   |
   --jemos
   |
   --xmlop
   |
   OneNormalClass.java
   SecondNormalClass.java
   FirstEJB.java (Entity)
   FirstBeanSession.java  (Session)
 
 In the following property I declared  the following:
 
 maven.xdoclet.xdoclet.fileset.0.include=**/*EJB.java, **/*Bean.java
 
 Is it ok? (I mean the use of the comma).
 
 Is there a standard directory structure I could follow when creating EJBs
 with Maven?
 
 Many thanks,
 
 Marco
 
 - Original Message - 
 From: Konstantin Priblouda [EMAIL PROTECTED]
 To: Maven Users List [EMAIL PROTECTED]; Marco Tedone
 [EMAIL PROTECTED]
 Sent: Monday, March 15, 2004 7:26 PM
 Subject: Re: What does the XDoclet plugin expects?
 
 
 
  --- Marco Tedone [EMAIL PROTECTED] wrote:
   Hi, I'm reading the documentation on the XDoclet
   website about the Maven
   plugin. However, I don't know what the
   xdoclet:ejbdoclet goal expects in
   the maven.xml file. I've got a folder /src under
   which java, webapp, etc.
   are stored. When I point my cursor to /src and type
   maven
   xdoclet:ejbdoclet nothing happens.
  
 
  you will need some properties and dependencies to
  activate subtasks
 
  Like this:
 
  ---%-
  #message bundles
  maven.xdoclet.xdoclet.destDir=${basedir}/target/xdoclet/xdoclet
  maven.xdoclet.xdoclet.externalizer.0=true
  maven.xdoclet.xdoclet.externalizer.0.destinationFile={0}{1}.properties
 
  maven.xdoclet.xdoclet.propertiestranslator.0=true
  maven.xdoclet.xdoclet.fileset.0=true
  maven.xdoclet.xdoclet.fileset.0.include=**/*.java
  ---%-
 
  Here I activate 2 subtasks ( externalizer / properties
  translator ) ,
  specify  fileset for eintire xdoclet invocation, and
  some task specific
  settings ( for example name pattern for generated
  properties  )
 
  then I need to specify desired task ( xdoclet:xdoclet
  ) as pregoal,
  and possibly tune my project xml so  that generated
  artifacts are packaged , or included in classpath of
  unit tests.
 
  regards,
 
 
 
 
  =
  [ Konstantin Pribluda ( ko5tik ) ]
  Zu Verstärkung meines Teams suche ich ab Sofort einen
  Softwareentwickler[In] für die Festanstellung.
  Arbeitsort: Mainz
  Skills:  Programieren, Kentnisse in OpenSource-Bereich
  [ http://www.pribluda.de ]
 
  __
  Do you Yahoo!?
  Yahoo! Mail - More reliable, more storage, less spam
  http://mail.yahoo.com
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


__
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Generating EJBs with XDoclet plugin

[Marco Tedone]

Hi, I'm just starting to use the Maven plugin to build the EJBs.

I declared the xdoclet plugin as follows:

dependency
groupIdxdoclet/groupId
artifactIdmaven-xdoclet-plugin/artifactId
version1.2/version
typeplugin/type
urlhttp://xdoclet.sourceforge.net//url
/dependency

I've got also the following dependencies in my project:

dependency
groupIdxdoclet/groupId
artifactIdxdoclet/artifactId
version1.2/version
urlhttp://xdoclet.sourceforge.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-ejb-module/artifactId
version1.2/version
urlhttp://xdoclet.sourceforge.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-jboss-module/artifactId
version1.2/version
urlhttp://xdoclet.sourceforge.net//url
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxdoclet-jmx-module/artifactId
version1.2/version
urlhttp://xdoclet.sourceforge.net//url
/dependency

However, when I run

maven xdoclet:ejbdoclet I obtain the following exception:

BUILD FAILED
File.. file:/C:/Documents and
Settings/mtedone/.maven/plugins/maven-xdoclet-plugin-1.2/
Element... taskdef
Line.. 5746
Column 81
taskdef class xdoclet.modules.ejb.EjbDocletTask cannot be found
Total time: 4 seconds
Finished at: Sun Mar 14 19:26:09 GMT 2004

Obviously the EjbDocletTask class is not in the classpath, although I
declared it as a dependency. How could I solve this problem?

Many thanks,

Marco



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

xdoclet plugin?

[conradwt]

Hi, where can I download the xdoclet plugin?

Thanks,

-Conrad

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: xdoclet plugin?

[Rademacher Tobias]

Hi Conrad,

its bundled with xdoclet, not with maven. For more informations about most
of all avaiable plugins please see:

http://maven.apache.org/reference/plugins/index.html

Bye
Toby

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, January 28, 2004 9:52 PM
 To: [EMAIL PROTECTED]
 Subject: xdoclet plugin?
 
 
 Hi, where can I download the xdoclet plugin?
 
 Thanks,
 
 -Conrad
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: XDoclet plugin strange behavior

[Kevin Hagel]

http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-673
I filed this back in october, still unresolved.

Are you building from source?  The maven plugin source still uses the old
style, which has NEVER worked since I first started building XDoclet about 6
months ago.  I changed the /blah/XDocletsource/maven/project.xml file to
contain the following

dependency
idxdoclet+xdoclet-module/id
version@XDOCLET_VERSION@/version
/dependency
dependency
groupIdxdoclet/groupId
artifactIdxjavadoc/artifactId
version@XJAVADOC_VERSION@/version
/dependency

Without this fix XDoclet's maven plugin will not load.

- Original Message - 
From: __matthewHawthorne [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Sunday, January 04, 2004 10:55 AM
Subject: Re: XDoclet plugin strange behavior


 A week or so ago, I filed this as a bug with the Xdoclet team.  The
 plugin looks for the xjavadoc plugin with the groupId xjavadoc instead
 of xdoclet.  I haven't heard anything back.

 The frustrating part is that the only way I was able to figure out the
 error was by looking at the plugin's project.xml.

 To fix it, you must either put the jar into repo/xjavadoc/jars or use
 the jar override feature and put it wherever you want.  I requested that
 the xjavadoc jar be put into its own directory (not the xdoclet dir) on
 ibiblio, but the request was denied.


 Aleksandr Shneyderman wrote:
  Konstantin Priblouda wrote:
 
  Well, if yoyu use gourpid, you have to call your
  xjavadoc xdoclet-xjavadoc.whatever.jar
 
 
  According to the documentation the files are located according to the
  following pattern:
 
  ${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}
 
  So if my dependency looks something like the following:
dependency
artifactIdxjavadoc/artifactId
groupIdxdoclet/groupId
version1.0.2/version
typejar/type
/dependency
 
  Should not I expcet maven to find the jar if the file at location
  ${repo}/xdoclet/jars/xjavadoc-1.0.2.jar does exists?
 
  Thanks,
  Alex.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: XDoclet plugin strange behavior

[Konstantin Priblouda]

--- Aleksandr Shneyderman [EMAIL PROTECTED]
wrote:
 As you have probably noticed for the last couple of
 days I was 
 struggling with XDoclet plugin.
 What I did is I downloaded their 1.2 version,
 created xdoclet/jars 
 directory in my local repository,
 copied over the jars that come with the xdoclet. I
 then copied xdoclet's 
 maven-plugin jar to my plugins
 directory. 

Well, if yoyu use gourpid, you have to call your
xjavadoc 
xdoclet-xjavadoc.whatever.jar

If you do not use groupid, you shall place it in
maven repo/xjavadoc/jars/


regards,

=
[ Konstantin Pribluda ( ko5tik ) ]
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung. 
Arbeitsort: Mainz 
Skills:  Programieren, Kentnisse in OpenSource-Bereich
[ http://www.pribluda.de ]

__
Do you Yahoo!?
Find out what made the Top Yahoo! Searches of 2003
http://search.yahoo.com/top2003

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: XDoclet plugin strange behavior

[Aleksandr Shneyderman]

Konstantin Priblouda wrote:

Well, if yoyu use gourpid, you have to call your
xjavadoc 
xdoclet-xjavadoc.whatever.jar

According to the documentation the files are located according to the
following pattern:
${repo}/${groupId}/${type}s/${artifactId}-${version}.${type}

So if my dependency looks something like the following:
  dependency
  artifactIdxjavadoc/artifactId
  groupIdxdoclet/groupId
  version1.0.2/version
  typejar/type
  /dependency
Should not I expcet maven to find the jar if the file at location
${repo}/xdoclet/jars/xjavadoc-1.0.2.jar does exists?
Thanks,
Alex.




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]