RE: [m2] new ejbdoclet+webdoclet plugin announcement
Hi there,
After a couple of attempts I got the webdoclet working. I´ve used the xdoclet
plugin with a webdoclet task. Please see POM below:
org.codehaus.mojo
xdoclet-maven-plugin
1.0-alpha-2
generate-sources
xdoclet
Note that I had to provide the 'destdir' attribute. Hope this can be default in
the future.
Regards,
Dário
-Original Message-
From: Dário Luís Coneglian Oliveros
Sent: terça-feira, 6 de dezembro de 2005 15:59
To: Maven Users List
Subject: RE: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Ashley,
I´ve been having problem with the webdoclet plugin and can´t figure out how to
get it working.
Still not sure which plugin to use (xdoclet or webdoclet) nor its respective
repository.
Here´s a snippet of my POM:
org.codehaus.mojo
xdoclet-maven-plugin
1.0-alpha-2
generate-sources
xdoclet
It seems that no action is taken when running 'mvn compile' even though it
displays that task was executed. See output below:
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
[INFO] Executed tasks
Then I tried to change the POM by replacing the plugins section according to
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/webdoclet-maven-plugin/sample-ear-proj/trading-web/pom.xml.
No success at all. This time the webdoclet-maven-plugin couldn´t be found.
Output
--
Reason: Unable to download the artifact from any repository
org.codehaus.mojo:webdoclet-maven-plugin:1.0-beta-1:pom
--
Any tips ?
Thanks,
Dário
-Original Message-
From: Ashley Williams [mailto:[EMAIL PROTECTED]
Sent: sexta-feira, 25 de novembro de 2005 09:03
To: Maven Users List
Subject: Re: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Marcel,
Reading between the lines I think you are asking if you need to have
an ant
installation on your machine - the answer is no, since the plugin
brings in
ant as one of its dependencies.
Some background: everybody has their own theory but mine is that
maven intends
to replace all of the functionality of the ant tasks out there - and
as a long term
goal I see no problem with that. However in the short term I see the
following problems:
1. I need stuff that works well right now and can't wait for months
and years. Even
when we do get maven replacements they won't have had the advantage
of being
extensively user tested for quite some time.
2. Everybody knows ant syntax so familiarity is a big plus for
somebody coming to maven
for the first time. I do wish that even when pure maven replacements
come along they would
retain syntax compatibility with a reasonable subset of ant.
3. With the other ant integration stuff we already have in maven we
don't have the
ability to easily map maven properties to ant attributes (correct me
if I'm wrong). For me this
seemingly small point ends up being a real killer as I personally
find it very troublesome
to supply values such as destDir="{project.output}/generated-sources/
main/java" (see I've
probably got that wrong and I'd have to look it up!!!) by hand and
keep them all synchronized.
4. I create a temporary build file because I really can't get to
grips with the slippery
ant api. Many methods are be private so I'd have to use reflection,
also seeing problems
such as running tasks individually would work but run them as part of
the same build
would fail. Glad to abandon that approach.
---
On balance I do look forward to the ant-maven integration plugins
being retired
but can't see it happening any time soon.
- Ashley
On 25 Nov 2005, at 08:11, Marcel Dullaart wrote:
> Hi Ashley,
>
> sounds good, I'll try-out the webdoclet ASAP.
> Since you create an ant script on the fly, does that mean that
> using your
> xdoclet plugin requires ant?
> Is that a good idea?
>
> Cheers,
> Marcel
> Ashley Williams <[EMAIL PROTECTED]> wrote on 25-11-2005 01:08:04:
>
>> I have placed new ejbdoclet and webdoclet plugins in the sandbox here
>> https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/
>>
>> And to see their use in a sample ear project try the following link:
>> https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear-
>> proj/
>>
>> ---
>>
>> Briefly they provide the following features:
>>
>> 1. Familiar ant xdoclet syntax can be used in configuration
>>
>> 2. Maven proper
RE: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Ashley,
I´ve been having problem with the webdoclet plugin and can´t figure out how to
get it working.
Still not sure which plugin to use (xdoclet or webdoclet) nor its respective
repository.
Here´s a snippet of my POM:
org.codehaus.mojo
xdoclet-maven-plugin
1.0-alpha-2
generate-sources
xdoclet
It seems that no action is taken when running 'mvn compile' even though it
displays that task was executed. See output below:
[INFO] [xdoclet:xdoclet {execution: default}]
[INFO] Initializing DocletTasks!!!
[INFO] Executing tasks
[INFO] Executed tasks
Then I tried to change the POM by replacing the plugins section according to
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/webdoclet-maven-plugin/sample-ear-proj/trading-web/pom.xml.
No success at all. This time the webdoclet-maven-plugin couldn´t be found.
Output
--
Reason: Unable to download the artifact from any repository
org.codehaus.mojo:webdoclet-maven-plugin:1.0-beta-1:pom
--
Any tips ?
Thanks,
Dário
-Original Message-
From: Ashley Williams [mailto:[EMAIL PROTECTED]
Sent: sexta-feira, 25 de novembro de 2005 09:03
To: Maven Users List
Subject: Re: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Marcel,
Reading between the lines I think you are asking if you need to have
an ant
installation on your machine - the answer is no, since the plugin
brings in
ant as one of its dependencies.
Some background: everybody has their own theory but mine is that
maven intends
to replace all of the functionality of the ant tasks out there - and
as a long term
goal I see no problem with that. However in the short term I see the
following problems:
1. I need stuff that works well right now and can't wait for months
and years. Even
when we do get maven replacements they won't have had the advantage
of being
extensively user tested for quite some time.
2. Everybody knows ant syntax so familiarity is a big plus for
somebody coming to maven
for the first time. I do wish that even when pure maven replacements
come along they would
retain syntax compatibility with a reasonable subset of ant.
3. With the other ant integration stuff we already have in maven we
don't have the
ability to easily map maven properties to ant attributes (correct me
if I'm wrong). For me this
seemingly small point ends up being a real killer as I personally
find it very troublesome
to supply values such as destDir="{project.output}/generated-sources/
main/java" (see I've
probably got that wrong and I'd have to look it up!!!) by hand and
keep them all synchronized.
4. I create a temporary build file because I really can't get to
grips with the slippery
ant api. Many methods are be private so I'd have to use reflection,
also seeing problems
such as running tasks individually would work but run them as part of
the same build
would fail. Glad to abandon that approach.
---
On balance I do look forward to the ant-maven integration plugins
being retired
but can't see it happening any time soon.
- Ashley
On 25 Nov 2005, at 08:11, Marcel Dullaart wrote:
> Hi Ashley,
>
> sounds good, I'll try-out the webdoclet ASAP.
> Since you create an ant script on the fly, does that mean that
> using your
> xdoclet plugin requires ant?
> Is that a good idea?
>
> Cheers,
> Marcel
> Ashley Williams <[EMAIL PROTECTED]> wrote on 25-11-2005 01:08:04:
>
>> I have placed new ejbdoclet and webdoclet plugins in the sandbox here
>> https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/
>>
>> And to see their use in a sample ear project try the following link:
>> https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear-
>> proj/
>>
>> ---
>>
>> Briefly they provide the following features:
>>
>> 1. Familiar ant xdoclet syntax can be used in configuration
>>
>> 2. Maven properties are automatically applied to the ant task - for
>> example
>> you don't have to specify attributes such as destDir="target/
>> generated-sources",
>> because the plugin applies a list of known mappings!
>>
>> 3. Can execute plugins in the same mvn session - eg a pom.xml that
>> kicks off
>> an ejb and then web build won't bomb out.
>>
>> 4. Works by creating an actual build.xml file on the fly.
>>
>> - Ashley
>>
>> -
>> 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: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Marcel,
Reading between the lines I think you are asking if you need to have
an ant
installation on your machine - the answer is no, since the plugin
brings in
ant as one of its dependencies.
Some background: everybody has their own theory but mine is that
maven intends
to replace all of the functionality of the ant tasks out there - and
as a long term
goal I see no problem with that. However in the short term I see the
following problems:
1. I need stuff that works well right now and can't wait for months
and years. Even
when we do get maven replacements they won't have had the advantage
of being
extensively user tested for quite some time.
2. Everybody knows ant syntax so familiarity is a big plus for
somebody coming to maven
for the first time. I do wish that even when pure maven replacements
come along they would
retain syntax compatibility with a reasonable subset of ant.
3. With the other ant integration stuff we already have in maven we
don't have the
ability to easily map maven properties to ant attributes (correct me
if I'm wrong). For me this
seemingly small point ends up being a real killer as I personally
find it very troublesome
to supply values such as destDir="{project.output}/generated-sources/
main/java" (see I've
probably got that wrong and I'd have to look it up!!!) by hand and
keep them all synchronized.
4. I create a temporary build file because I really can't get to
grips with the slippery
ant api. Many methods are be private so I'd have to use reflection,
also seeing problems
such as running tasks individually would work but run them as part of
the same build
would fail. Glad to abandon that approach.
---
On balance I do look forward to the ant-maven integration plugins
being retired
but can't see it happening any time soon.
- Ashley
On 25 Nov 2005, at 08:11, Marcel Dullaart wrote:
Hi Ashley,
sounds good, I'll try-out the webdoclet ASAP.
Since you create an ant script on the fly, does that mean that
using your
xdoclet plugin requires ant?
Is that a good idea?
Cheers,
Marcel
Ashley Williams <[EMAIL PROTECTED]> wrote on 25-11-2005 01:08:04:
I have placed new ejbdoclet and webdoclet plugins in the sandbox here
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/
And to see their use in a sample ear project try the following link:
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear-
proj/
---
Briefly they provide the following features:
1. Familiar ant xdoclet syntax can be used in configuration
2. Maven properties are automatically applied to the ant task - for
example
you don't have to specify attributes such as destDir="target/
generated-sources",
because the plugin applies a list of known mappings!
3. Can execute plugins in the same mvn session - eg a pom.xml that
kicks off
an ejb and then web build won't bomb out.
4. Works by creating an actual build.xml file on the fly.
- Ashley
-
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: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Srepfler,
It should be quite similar to achieve the same behavior for hibernate
etc since there are only 2 stages to writing plugins of your own.
To start with copy the ejbdoclet plugin (rename as necessary) and then:
1. Edit the dependencies in the pom.xml file. The dependencies will
be used to form the ant taskdef classpath - I believe you won't need
to alter them as I included rather too many in the ejbdoclet pom.xml,
so that likely includes the hibernate dependencies.
2. Edit the mojo. I've included the code snipped below and if you
know xpath you'll immediately see the left hand side is the xpath for
the ant attribute and the right hand side is the constant that will
be used to set it's value, meaning users of the plugin don't have to.
For example notice that ejbdoclet/@destDir ant attribute will have
the generated java source directory assigned to it.
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");
Don't know if it's feasible (don't know enough about writing plugins)
but in future I'd like to make it so that you don't have to write
a plugin, just simply provide a properties file with the mappings.
On 25 Nov 2005, at 04:01, Srepfler Srgjan wrote:
Hi Ashley,
Can you please tell me what would it take to make similar doclets
but for hibernate or if you know there are already some existing ones?
Thanks
Ashley Williams wrote:
I have placed new ejbdoclet and webdoclet plugins in the sandbox here
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/
And to see their use in a sample ear project try the following link:
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear-
proj/
---
Briefly they provide the following features:
1. Familiar ant xdoclet syntax can be used in configuration
2. Maven properties are automatically applied to the ant task -
for example
you don't have to specify attributes such as destDir="target/
generated-sources",
because the plugin applies a list of known mappings!
3. Can execute plugins in the same mvn session - eg a pom.xml
that kicks off
an ejb and then web build won't bomb out.
4. Works by creating an actual build.xml file on the fly.
- Ashley
-
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: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Ashley, sounds good, I'll try-out the webdoclet ASAP. Since you create an ant script on the fly, does that mean that using your xdoclet plugin requires ant? Is that a good idea? Cheers, Marcel Ashley Williams <[EMAIL PROTECTED]> wrote on 25-11-2005 01:08:04: > I have placed new ejbdoclet and webdoclet plugins in the sandbox here > https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/ > > And to see their use in a sample ear project try the following link: > https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear-proj/ > > --- > > Briefly they provide the following features: > > 1. Familiar ant xdoclet syntax can be used in configuration > > 2. Maven properties are automatically applied to the ant task - for > example > you don't have to specify attributes such as destDir="target/ > generated-sources", > because the plugin applies a list of known mappings! > > 3. Can execute plugins in the same mvn session - eg a pom.xml that > kicks off > an ejb and then web build won't bomb out. > > 4. Works by creating an actual build.xml file on the fly. > > - Ashley > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [m2] new ejbdoclet+webdoclet plugin announcement
Hi Ashley, Can you please tell me what would it take to make similar doclets but for hibernate or if you know there are already some existing ones? Thanks Ashley Williams wrote: I have placed new ejbdoclet and webdoclet plugins in the sandbox here https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/ And to see their use in a sample ear project try the following link: https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/sample-ear-proj/ --- Briefly they provide the following features: 1. Familiar ant xdoclet syntax can be used in configuration 2. Maven properties are automatically applied to the ant task - for example you don't have to specify attributes such as destDir="target/ generated-sources", because the plugin applies a list of known mappings! 3. Can execute plugins in the same mvn session - eg a pom.xml that kicks off an ejb and then web build won't bomb out. 4. Works by creating an actual build.xml file on the fly. - Ashley - 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]
