Re: [m2][javadoc-plugin] currentYear, inceptionYear

2007-04-02 Thread shinsato

Here's an answer for anyone else who may have stumbled around unnecessarily
for this one, as did I.  The unclear documentation in the javadoc-mojo is
only really clarified if you look at the source code.  The {x} items
referenced are place holders for different things, they are not standard
${x} property values.  The organizationName is converted to
MavenProject.getOrganization, which is set in the project's pom.xml. 
organization/ is an object right under the top level project/ root.  The
same is true for inceptionYear, for example...

project
  ...
  organization
nameCodehaus Mojo/name
urlhttp://mojo.codehaus.org/url
  /organization
  inceptionYear2006/inceptionYear
  ...
/project

The {currentYear} is a placeholder for the current Calendar year which the
javadoc mojo programmatically looks up.  You can't set that one.

 Harold
-- 
View this message in context: 
http://www.nabble.com/-m2--javadoc-plugin--currentYear%2C-inceptionYear-tf2507450s177.html#a9800936
Sent from the Maven - Users mailing list archive at Nabble.com.


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



[m2][javadoc-plugin] currentYear, inceptionYear

2006-10-25 Thread Feniks Nator

Hello,

from:
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
I see that the default value for the 'botttom' parameter of the javadoc
plugin has the followig value:

Copyright copy; {inceptionYear}-{currentYear} {organizationName}. All
Rights Reserved.
But I can't figure out how these values are replaced: {inceptionYear},
{currentYear}, {organizationName}
Why isn't it ${propertyName}?
I assume {inceptionYear} is mapped on ${project.inceptionYear} (or
${inceptionYear}) that can be available in the maven POM.
What if it is not present? Where does the value come from, is it current
year?

Same for {currentYear}, is this replaced by maven, or is this part of the
javadoc tool itself?
And what about organizationName ?

Thanks


Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-08 Thread Stephen Duncan
I apologize for the vagueness, but to make sure the request didn't get
lost, I created: http://jira.codehaus.org/browse/MPLUGIN-13

-Stephen

On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:
 On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
  On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
   To include javadocs, jxr, and surefire (testing) reports to your site,
   as examples, add the following to your POM:
  
 reporting
 plugins
 plugin
 groupIdorg.apache.maven.plugins/groupId
 
   artifactIdmaven-javadoc-plugin/artifactId
 /plugin
  
 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdjxr-maven-plugin/artifactId
 /plugin
  
 plugin
 groupIdorg.codehaus.mojo/groupId
 
   artifactIdsurefire-report-maven-plugin/artifactId
 /plugin
 /plugins
 /reporting
  
   -Stephen
 
  Thanks, Stephen
 
  You might actually want to mention that in the maven-javadoc-plugin
  documentation.
 
  Oleg
 

 No problem.  I think I might need to set up a custom signature for my
 Maven mailing list e-mails that includes the line I am not a Maven
 developer, though!

 Maven gurus: since this is on the whole documentation topic, and
 potentially a good case for improved documentation through
 automation...  Is there some way we can get plugins that can provide
 reports to automatically have some documentation that 1) states that
 they can be used as a report and 2) indicates the basics of how to add
 a report, as the documentation for this in the main guides isn't
 exactly easy to find...

 --
 Stephen Duncan Jr
 www.stephenduncanjr.com



--
Stephen Duncan Jr
www.stephenduncanjr.com

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



[m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Oleg Kalnichevski
Folks,

I am currently in the process of migrating Jakarta HttpComponents
project (formerly known as Commons HttpClient) from Maven1 to Maven2. I
got the most of the fundamental stuff already in place. However, I am
having difficulties with some of the reports that used to be quite easy
with Maven1. 

Is there a way to get Maven2 generate a javadocs report along with all
the standard reports when generating and deploying the web site? I know
there is a Javadocs plugin, which pretty much does the job. However,
having to run it separately and then manually coping the resultant
javadocs from PROJECT_HOME/target to PROJECT_HOME/target/site is
quite a bit of a nuisance 

Javadoc Plugin documentation was of no help to me. I hope I am missing
something obvious

Cheers,

Oleg





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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Stephen Duncan
To include javadocs, jxr, and surefire (testing) reports to your site,
as examples, add the following to your POM:

reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin

plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjxr-maven-plugin/artifactId
/plugin

plugin
groupIdorg.codehaus.mojo/groupId

artifactIdsurefire-report-maven-plugin/artifactId
/plugin
/plugins
/reporting

-Stephen

On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
 Folks,

 I am currently in the process of migrating Jakarta HttpComponents
 project (formerly known as Commons HttpClient) from Maven1 to Maven2. I
 got the most of the fundamental stuff already in place. However, I am
 having difficulties with some of the reports that used to be quite easy
 with Maven1.

 Is there a way to get Maven2 generate a javadocs report along with all
 the standard reports when generating and deploying the web site? I know
 there is a Javadocs plugin, which pretty much does the job. However,
 having to run it separately and then manually coping the resultant
 javadocs from PROJECT_HOME/target to PROJECT_HOME/target/site is
 quite a bit of a nuisance

 Javadoc Plugin documentation was of no help to me. I hope I am missing
 something obvious

 Cheers,

 Oleg





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




--
Stephen Duncan Jr
www.stephenduncanjr.com

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Oleg Kalnichevski
On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
 To include javadocs, jxr, and surefire (testing) reports to your site,
 as examples, add the following to your POM:
 
   reporting
   plugins
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
   /plugin
   
   plugin
   groupIdorg.codehaus.mojo/groupId
   artifactIdjxr-maven-plugin/artifactId
   /plugin
 
   plugin
   groupIdorg.codehaus.mojo/groupId
   
 artifactIdsurefire-report-maven-plugin/artifactId
   /plugin
   /plugins
   /reporting
 
 -Stephen

Thanks, Stephen

You might actually want to mention that in the maven-javadoc-plugin
documentation.

Oleg

 
 On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
  Folks,
 
  I am currently in the process of migrating Jakarta HttpComponents
  project (formerly known as Commons HttpClient) from Maven1 to Maven2. I
  got the most of the fundamental stuff already in place. However, I am
  having difficulties with some of the reports that used to be quite easy
  with Maven1.
 
  Is there a way to get Maven2 generate a javadocs report along with all
  the standard reports when generating and deploying the web site? I know
  there is a Javadocs plugin, which pretty much does the job. However,
  having to run it separately and then manually coping the resultant
  javadocs from PROJECT_HOME/target to PROJECT_HOME/target/site is
  quite a bit of a nuisance
 
  Javadoc Plugin documentation was of no help to me. I hope I am missing
  something obvious
 
  Cheers,
 
  Oleg
 
 
 
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 --
 Stephen Duncan Jr
 www.stephenduncanjr.com
 
 -
 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][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Stephen Duncan
On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
 On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
  To include javadocs, jxr, and surefire (testing) reports to your site,
  as examples, add the following to your POM:
 
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
/plugin
 
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjxr-maven-plugin/artifactId
/plugin
 
plugin
groupIdorg.codehaus.mojo/groupId

  artifactIdsurefire-report-maven-plugin/artifactId
/plugin
/plugins
/reporting
 
  -Stephen

 Thanks, Stephen

 You might actually want to mention that in the maven-javadoc-plugin
 documentation.

 Oleg


No problem.  I think I might need to set up a custom signature for my
Maven mailing list e-mails that includes the line I am not a Maven
developer, though!

Maven gurus: since this is on the whole documentation topic, and
potentially a good case for improved documentation through
automation...  Is there some way we can get plugins that can provide
reports to automatically have some documentation that 1) states that
they can be used as a report and 2) indicates the basics of how to add
a report, as the documentation for this in the main guides isn't
exactly easy to find...

--
Stephen Duncan Jr
www.stephenduncanjr.com

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Wayne Fay
For now, add it as a MiniGuide, call it MiniGuide-Reporting or
something... I'm actually working on a few MiniGuides the last couple
of days, based on conversations here in user@ and some on dev@ and
will upload them at some point.

http://docs.codehaus.org/display/MAVENUSER/Mini+Guides

Sign up for a Confluence account and post away...

Wayne


On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:
 On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
  On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
   To include javadocs, jxr, and surefire (testing) reports to your site,
   as examples, add the following to your POM:
  
 reporting
 plugins
 plugin
 groupIdorg.apache.maven.plugins/groupId
 
   artifactIdmaven-javadoc-plugin/artifactId
 /plugin
  
 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdjxr-maven-plugin/artifactId
 /plugin
  
 plugin
 groupIdorg.codehaus.mojo/groupId
 
   artifactIdsurefire-report-maven-plugin/artifactId
 /plugin
 /plugins
 /reporting
  
   -Stephen
 
  Thanks, Stephen
 
  You might actually want to mention that in the maven-javadoc-plugin
  documentation.
 
  Oleg
 

 No problem.  I think I might need to set up a custom signature for my
 Maven mailing list e-mails that includes the line I am not a Maven
 developer, though!

 Maven gurus: since this is on the whole documentation topic, and
 potentially a good case for improved documentation through
 automation...  Is there some way we can get plugins that can provide
 reports to automatically have some documentation that 1) states that
 they can be used as a report and 2) indicates the basics of how to add
 a report, as the documentation for this in the main guides isn't
 exactly easy to find...

 --
 Stephen Duncan Jr
 www.stephenduncanjr.com

 -
 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][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Stephen Duncan
Well, it is in the Getting Started guide under Configuring Reports:
http://maven.apache.org/guides/getting-started/index.html##How do I
create documentation?

The only other useful info I could imagine is a list of available
report-generating plugins, but I'm not sure a Mini-Guide is the
appropriate place.  Somewhere else on the wiki maybe?

-Stephen

On 3/7/06, Wayne Fay [EMAIL PROTECTED] wrote:
 For now, add it as a MiniGuide, call it MiniGuide-Reporting or
 something... I'm actually working on a few MiniGuides the last couple
 of days, based on conversations here in user@ and some on dev@ and
 will upload them at some point.

 http://docs.codehaus.org/display/MAVENUSER/Mini+Guides

 Sign up for a Confluence account and post away...

 Wayne


 On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:
  On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
   On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
To include javadocs, jxr, and surefire (testing) reports to your site,
as examples, add the following to your POM:
   
  reporting
  plugins
  plugin
  
groupIdorg.apache.maven.plugins/groupId
  
artifactIdmaven-javadoc-plugin/artifactId
  /plugin
   
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdjxr-maven-plugin/artifactId
  /plugin
   
  plugin
  groupIdorg.codehaus.mojo/groupId
  
artifactIdsurefire-report-maven-plugin/artifactId
  /plugin
  /plugins
  /reporting
   
-Stephen
  
   Thanks, Stephen
  
   You might actually want to mention that in the maven-javadoc-plugin
   documentation.
  
   Oleg
  
 
  No problem.  I think I might need to set up a custom signature for my
  Maven mailing list e-mails that includes the line I am not a Maven
  developer, though!
 
  Maven gurus: since this is on the whole documentation topic, and
  potentially a good case for improved documentation through
  automation...  Is there some way we can get plugins that can provide
  reports to automatically have some documentation that 1) states that
  they can be used as a report and 2) indicates the basics of how to add
  a report, as the documentation for this in the main guides isn't
  exactly easy to find...
 
  --
  Stephen Duncan Jr
  www.stephenduncanjr.com
 
  -
  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]




--
Stephen Duncan Jr
www.stephenduncanjr.com

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Stephen Duncan
Ok, I went ahead and made a Wiki Page for reporting plugins:
http://docs.codehaus.org/display/MAVENUSER/Reporting+Plugins

For now I just added the ones I use.

-Stephen

On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:
 Well, it is in the Getting Started guide under Configuring Reports:
 http://maven.apache.org/guides/getting-started/index.html##How do I
 create documentation?

 The only other useful info I could imagine is a list of available
 report-generating plugins, but I'm not sure a Mini-Guide is the
 appropriate place.  Somewhere else on the wiki maybe?

 -Stephen

 On 3/7/06, Wayne Fay [EMAIL PROTECTED] wrote:
  For now, add it as a MiniGuide, call it MiniGuide-Reporting or
  something... I'm actually working on a few MiniGuides the last couple
  of days, based on conversations here in user@ and some on dev@ and
  will upload them at some point.
 
  http://docs.codehaus.org/display/MAVENUSER/Mini+Guides
 
  Sign up for a Confluence account and post away...
 
  Wayne
 
 
  On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:
   On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:
On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
 To include javadocs, jxr, and surefire (testing) reports to your site,
 as examples, add the following to your POM:

   reporting
   plugins
   plugin
   
 groupIdorg.apache.maven.plugins/groupId
   
 artifactIdmaven-javadoc-plugin/artifactId
   /plugin

   plugin
   groupIdorg.codehaus.mojo/groupId
   
 artifactIdjxr-maven-plugin/artifactId
   /plugin

   plugin
   groupIdorg.codehaus.mojo/groupId
   
 artifactIdsurefire-report-maven-plugin/artifactId
   /plugin
   /plugins
   /reporting

 -Stephen
   
Thanks, Stephen
   
You might actually want to mention that in the maven-javadoc-plugin
documentation.
   
Oleg
   
  
   No problem.  I think I might need to set up a custom signature for my
   Maven mailing list e-mails that includes the line I am not a Maven
   developer, though!
  
   Maven gurus: since this is on the whole documentation topic, and
   potentially a good case for improved documentation through
   automation...  Is there some way we can get plugins that can provide
   reports to automatically have some documentation that 1) states that
   they can be used as a report and 2) indicates the basics of how to add
   a report, as the documentation for this in the main guides isn't
   exactly easy to find...
  
   --
   Stephen Duncan Jr
   www.stephenduncanjr.com
  
   -
   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]
 
 


 --
 Stephen Duncan Jr
 www.stephenduncanjr.com



--
Stephen Duncan Jr
www.stephenduncanjr.com

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Wendy Smoak
On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:

 Ok, I went ahead and made a Wiki Page for reporting plugins:
 http://docs.codehaus.org/display/MAVENUSER/Reporting+Plugins

 For now I just added the ones I use.

Thanks. :)  I added a more complex example of using reportSets
configure more than one report from the Javadoc plugin -- the normal
HTML Javadoc plus .dot files from UMLGraph.

--
Wendy

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Stephen Duncan
Very cool!  I didn't know about that, thanks!

On 3/7/06, Wendy Smoak [EMAIL PROTECTED] wrote:
 On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:

  Ok, I went ahead and made a Wiki Page for reporting plugins:
  http://docs.codehaus.org/display/MAVENUSER/Reporting+Plugins
 
  For now I just added the ones I use.

 Thanks. :)  I added a more complex example of using reportSets
 configure more than one report from the Javadoc plugin -- the normal
 HTML Javadoc plus .dot files from UMLGraph.

 --
 Wendy

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




--
Stephen Duncan Jr
www.stephenduncanjr.com

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Subhash Chandran
The doclet docletgr.spinellis.umlgraph.doclet.UmlGraph/doclet is not
working for me... should I add any snapshot repository details in my pom?

--
Regards,
Subhash Chandran S

Cross platform OpenSource Java based file encryption software:
http://www.WizTools.org/project/WizCrypt/


 On 3/7/06, Wendy Smoak [EMAIL PROTECTED] wrote:
  On 3/7/06, Stephen Duncan [EMAIL PROTECTED] wrote:
 
   Ok, I went ahead and made a Wiki Page for reporting plugins:
   http://docs.codehaus.org/display/MAVENUSER/Reporting+Plugins
  
   For now I just added the ones I use.
 
  Thanks. :)  I added a more complex example of using reportSets
  configure more than one report from the Javadoc plugin -- the normal
  HTML Javadoc plus .dot files from UMLGraph.
 
  --
  Wendy
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Stephen Duncan Jr
 www.stephenduncanjr.com

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




Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Wendy Smoak
On 3/7/06, Subhash Chandran [EMAIL PROTECTED] wrote:

 The doclet docletgr.spinellis.umlgraph.doclet.UmlGraph/doclet is not
 working for me... should I add any snapshot repository details in my pom?

There is more info about UMLGraph and m2 here:
 * http://wiki.wsmoak.net/cgi-bin/wiki.pl?UMLGraph

(AFAIK, it's not available in any Maven repo.)

I'll add that to the Maven User space, sorry for the confusion.

--
Wendy

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



Re: [m2][Javadoc plugin] Javadoc report with Maven2

2006-03-07 Thread Steven Coco

I wonder if I can bend your ear for another simple question about JavaDoc:

I can't figure out how to specify the overview file.  I have: 
src/main/java/overview.html for an overview file.  In the JavaDoc plugin 
configuration, no matter what I try, I can't get anything inside the 
overview element to resolve to this file location.  The plugin always 
throws an error if I specify overview saying that it can't find what I 
specified.  Any help?


I appreciate it.

Steven.



On 3/7/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote:

 On Tue, 2006-03-07 at 17:25 -0500, Stephen Duncan wrote:
  To include javadocs, jxr, and surefire (testing) reports to your 
site,

  as examples, add the following to your POM:
 
  reporting
  plugins
  plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-javadoc-plugin/artifactId
  /plugin
 
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdjxr-maven-plugin/artifactId
  /plugin
 
  plugin
  groupIdorg.codehaus.mojo/groupId
  artifactIdsurefire-report-maven-plugin/artifactId
  /plugin
  /plugins
  /reporting
 
  -Stephen


 Thanks, Stephen

 You might actually want to mention that in the maven-javadoc-plugin
 documentation.

 Oleg
 


No problem. I think I might need to set up a custom signature for my
Maven mailing list e-mails that includes the line I am not a Maven
developer, though!

Maven gurus: since this is on the whole documentation topic, and
potentially a good case for improved documentation through
automation... Is there some way we can get plugins that can provide
reports to automatically have some documentation that 1) states that
they can be used as a report and 2) indicates the basics of how to add
a report, as the documentation for this in the main guides isn't
exactly easy to find...

--
Stephen Duncan Jr
www.stephenduncanjr.com




[m2] javadoc plugin and offline links

2006-01-25 Thread D D
Hi,

I'm  trying to use the javadoc plugin (beta-3) in offline mode. It looked like 
it was not taking into account the offlineLinks parameter, so i looked into the 
sources and found something strange (in JavadocReport.java, line 829):

if ( !isOffline )
{
addLinkArguments( arguments );
addLinkofflineArguments( arguments );
...
}

Is not the linkoffline parameter intended to link the javadoc when i am 
offline? Is it a bug or maybe i did not correcly understand the code.

Thanks

David DIDIER



-
 Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs 
exceptionnels pour appeler la France et l'international.Téléchargez la version 
beta.

Re: [m2] Javadoc plugin - using alternate UMLGraph doclet?

2006-01-14 Thread Wendy Smoak
On 1/9/06, Wendy Smoak [EMAIL PROTECTED] wrote:
 I tried configuring the javadoc plugin,
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-javadoc-plugin/artifactId
 configuration
docletgr.spinellis.umlgraph.doclet.UmlGraph/doclet

This conversation moved to [EMAIL PROTECTED], but since I know at least one
other person is
interested in using UMLGraph with Maven 2, I thought I would share
what I've learned so far.

The alternate UMLGraph doclet is working with Maven 2 and I've gotten
as far as producing the .dot files, but haven't yet attempted to get
m2 to run Graphviz to transform them into images.  A shell script is
*so* much simpler... ;)

You can find a sample pom and links to relevant JIRA tickets here:
  http://wiki.wsmoak.net/cgi-bin/wiki.pl?Maven/Javadoc

HTH,
--
Wendy

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



[m2] Javadoc plugin - using alternate UMLGraph doclet?

2006-01-09 Thread Wendy Smoak
How do I do this (from Ant):
  javadoc sourcepathref=uml.source.path packagenames=* package=true
   doclet name=gr.spinellis.umlgraph.doclet.UmlGraph
   path=${basedir}/lib/UMLGraph.jar
   param name=-d value=${uml.dir}/
   param name=-views/
   /doclet
   /javadoc
in m2?

I tried configuring the javadoc plugin,
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
configuration
   docletgr.spinellis.umlgraph.doclet.UmlGraph/doclet
   
docletPathc:\java\m2-repository\umlgraph\UMLGraph\4.2-SNAPSHOT\UMLGraph-4.2-SNAPSHOT.jar/docletPath
additionalParam-views/additionalParam
/configuration
 /plugin

But I get:
[INFO] An error has occurred in JavaDocs report generation.
Embedded error: Exit code: 1 - javadoc: error - invalid flag: -sourcePath

The usage information that prints out includes:
-sourcepath pathlist
(with a lowercase 'p'.  Not sure if that matters...)

Any ideas?  Assuming I did get it to work, my next question is how to
get both this and the normal Javadoc, IOW how to get the javadoc
plugin to run twice.  Or does this need to be a separate plugin?

Thanks!
Wendy

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



[m2] javadoc plugin configuration

2005-12-01 Thread Martin van der Plas

Hi,

Who can tell me in which part in pom.xml the javadoc plugin should be 
configured? It can be done in the plugins section of the pom or in the 
plugins section of the report section in the pom.


Thanks

--
Groeten,

   Martin

mailto:[EMAIL PROTECTED]
tel: +31 (0) 20-7988464
mob: +31 (0) 6-21551921



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



Re: [m2] javadoc plugin configuration

2005-12-01 Thread Allan Ramirez

Hi,

Please refer to this page 
http://maven.apache.org/guides/mini/guide-configuring-plugins.html


regards,
-allan

Martin van der Plas wrote:


Hi,

Who can tell me in which part in pom.xml the javadoc plugin should be 
configured? It can be done in the plugins section of the pom or in the 
plugins section of the report section in the pom.


Thanks



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

Re: [m2] javadoc plugin configuration

2005-12-01 Thread Brett Porter
I think we need to elaborate on that with regards to reports.

Generally, you should configure it in the reporting section.
Configuration there applies to both the site, and when run on the
command line, and adding the plugin there adds the report to the
generated site.

Configuration in the build section is only used during the normal
lifecycle or the command line invocation (eg javadoc:javadoc).
Configuration should go there if you do not want the report on the
site, or the configuration differs from what is on the site (eg, some
plugins have a fail build option).

Cheers,
Brett

On 12/2/05, Allan Ramirez [EMAIL PROTECTED] wrote:
 Hi,

 Please refer to this page
 http://maven.apache.org/guides/mini/guide-configuring-plugins.html

 regards,
 -allan

 Martin van der Plas wrote:

  Hi,
 
  Who can tell me in which part in pom.xml the javadoc plugin should be
  configured? It can be done in the plugins section of the pom or in the
  plugins section of the report section in the pom.
 
  Thanks
 



 -
 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]



[m2] javadoc plugin issues

2005-11-18 Thread Anuerin Diaz
hi,

  i have a a couple of issues with using the javadoc plugin. i am
looking forward to a similar result like the one found in
http://qdox.codehaus.org/maven-reports.html where multiple reports are
attached in the generated site. i have attached the maven-javadoc
plugin in the reporting elements of my pom file and the plugin is
being called during site generation, however:

  the target/apidoc/index.html is always renders an empty page (but
not an empty file). the generation was successful because i can the
actual javadocs for each module class and the other files in the
apidoc directory seems to contain the correct entries (e.g.
index-all.html, overview-*.html) and could navigate to the actual
class javadoc from there.

  my html skills are virtually nonexistent but i think the most
pertinent part of the index.html page is the part i quoted below. the
other parts of the html page seems to be rendered perfectly (sidebars,
footers, etc.)
===
div id=bodyColumn
div id=contentBox/div
/div

div class=clear
hr /
/div
===


   my second issue with the javadoc plugin when it is used together
with the clover plugin. the javadoc plugin is causing the
clover-plugin to fail. used on its own the clover plugin works fine
but if i declare the javadoc and clover plugins at the same time then
the clover plugin will fail with a Can't find bundle for base name
clover-report, locale fi_FI.  changing the regional settings of my
workstation to en_US provides a temporary solution but not something
that management will endorse. as far as i can see the clover plugin
does not have a configuration setting for locale, and i am still
confused why this problem will only surface if the javadoc plugin is
also activated.

  my third issue with the javadoc was only found when i tried setting
the locale attribute to en_US to fix my second issue. javadoc
execution will always fail with a Embedded error: Exit code: 1 -
javadoc: option -locale must be first on the command line. message
even though it is the only configuration item for the javadoc plugin
on my pom.

  am i doing using these plugins incorrectly? thanks.

ciao!

--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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



Re: [m2] javadoc plugin issues

2005-11-18 Thread Anuerin Diaz
i just browsed JIRA and the second issue is the same as the one in
http://jira.codehaus.org/browse/MNG-1572. i will attach my scenario on
that issue if it would help in detecting the real cause.

ciao!

On 11/18/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
 hi,

  i have a a couple of issues with using the javadoc plugin. i am
 looking forward to a similar result like the one found in
 http://qdox.codehaus.org/maven-reports.html where multiple reports are
 attached in the generated site. i have attached the maven-javadoc
 plugin in the reporting elements of my pom file and the plugin is
 being called during site generation, however:

  the target/apidoc/index.html is always renders an empty page (but
 not an empty file). the generation was successful because i can the
 actual javadocs for each module class and the other files in the
 apidoc directory seems to contain the correct entries (e.g.
 index-all.html, overview-*.html) and could navigate to the actual
 class javadoc from there.

  my html skills are virtually nonexistent but i think the most
 pertinent part of the index.html page is the part i quoted below. the
 other parts of the html page seems to be rendered perfectly (sidebars,
 footers, etc.)
 ===
div id=bodyColumn
div id=contentBox/div
/div

div class=clear
hr /
/div
 ===


   my second issue with the javadoc plugin when it is used together
 with the clover plugin. the javadoc plugin is causing the
 clover-plugin to fail. used on its own the clover plugin works fine
 but if i declare the javadoc and clover plugins at the same time then
 the clover plugin will fail with a Can't find bundle for base name
 clover-report, locale fi_FI.  changing the regional settings of my
 workstation to en_US provides a temporary solution but not something
 that management will endorse. as far as i can see the clover plugin
 does not have a configuration setting for locale, and i am still
 confused why this problem will only surface if the javadoc plugin is
 also activated.

  my third issue with the javadoc was only found when i tried setting
 the locale attribute to en_US to fix my second issue. javadoc
 execution will always fail with a Embedded error: Exit code: 1 -
 javadoc: option -locale must be first on the command line. message
 even though it is the only configuration item for the javadoc plugin
 on my pom.

  am i doing using these plugins incorrectly? thanks.

 ciao!

 --

 Programming, an artform that fights back

 Anuerin G. Diaz
 Registered Linux User #246176
 Friendly Linux Board @ http://mandrivausers.org/index.php
 http://capsule.ramfree17.org , when you absolutely have nothing else
 better to do



--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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



Re: [m2] javadoc plugin issues

2005-11-18 Thread Jos Dirksen
To add something to the first issue. This is solved in subversion. If
you check out the plugin and build it, you should get a javadoc plugin
that doesn't show you an empty page, but shows the javadoc index page.

Jos

On 11/18/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
 i just browsed JIRA and the second issue is the same as the one in
 http://jira.codehaus.org/browse/MNG-1572. i will attach my scenario on
 that issue if it would help in detecting the real cause.

 ciao!

 On 11/18/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
  hi,
 
   i have a a couple of issues with using the javadoc plugin. i am
  looking forward to a similar result like the one found in
  http://qdox.codehaus.org/maven-reports.html where multiple reports are
  attached in the generated site. i have attached the maven-javadoc
  plugin in the reporting elements of my pom file and the plugin is
  being called during site generation, however:
 
   the target/apidoc/index.html is always renders an empty page (but
  not an empty file). the generation was successful because i can the
  actual javadocs for each module class and the other files in the
  apidoc directory seems to contain the correct entries (e.g.
  index-all.html, overview-*.html) and could navigate to the actual
  class javadoc from there.
 
   my html skills are virtually nonexistent but i think the most
  pertinent part of the index.html page is the part i quoted below. the
  other parts of the html page seems to be rendered perfectly (sidebars,
  footers, etc.)
  ===
 div id=bodyColumn
 div id=contentBox/div
 /div
 
 div class=clear
 hr /
 /div
  ===
 
 
my second issue with the javadoc plugin when it is used together
  with the clover plugin. the javadoc plugin is causing the
  clover-plugin to fail. used on its own the clover plugin works fine
  but if i declare the javadoc and clover plugins at the same time then
  the clover plugin will fail with a Can't find bundle for base name
  clover-report, locale fi_FI.  changing the regional settings of my
  workstation to en_US provides a temporary solution but not something
  that management will endorse. as far as i can see the clover plugin
  does not have a configuration setting for locale, and i am still
  confused why this problem will only surface if the javadoc plugin is
  also activated.
 
   my third issue with the javadoc was only found when i tried setting
  the locale attribute to en_US to fix my second issue. javadoc
  execution will always fail with a Embedded error: Exit code: 1 -
  javadoc: option -locale must be first on the command line. message
  even though it is the only configuration item for the javadoc plugin
  on my pom.
 
   am i doing using these plugins incorrectly? thanks.
 
  ciao!
 
  --
 
  Programming, an artform that fights back
 
  Anuerin G. Diaz
  Registered Linux User #246176
  Friendly Linux Board @ http://mandrivausers.org/index.php
  http://capsule.ramfree17.org , when you absolutely have nothing else
  better to do
 


 --

 Programming, an artform that fights back

 Anuerin G. Diaz
 Registered Linux User #246176
 Friendly Linux Board @ http://mandrivausers.org/index.php
 http://capsule.ramfree17.org , when you absolutely have nothing else
 better to do

 -
 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] javadoc plugin issues

2005-11-18 Thread Anuerin Diaz
thanks for the heads-up. anybody have a roadmap on when it is going to
be released to the public repositories? ill try building it on my own
but the last time i downloaded a plugin's source code i was not able
to make it run. i cant install subversion in my workstation so i had
to download everythng via the viewcvs site.

going offtopic, i dont know if i was imagining it but a couple of days
ago i saw a link at the bottom of each page that said download
tarball and i thought it would allow people like me to get the
complete sourcefiles outside of doing it via subversion. however i am
looking for that link today and i cant find them.

ciao!

On 11/18/05, Jos Dirksen [EMAIL PROTECTED] wrote:
 To add something to the first issue. This is solved in subversion. If
 you check out the plugin and build it, you should get a javadoc plugin
 that doesn't show you an empty page, but shows the javadoc index page.

 Jos

 On 11/18/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
  i just browsed JIRA and the second issue is the same as the one in
  http://jira.codehaus.org/browse/MNG-1572. i will attach my scenario on
  that issue if it would help in detecting the real cause.
 
  ciao!
 
  On 11/18/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
   hi,
  
i have a a couple of issues with using the javadoc plugin. i am
   looking forward to a similar result like the one found in
   http://qdox.codehaus.org/maven-reports.html where multiple reports are
   attached in the generated site. i have attached the maven-javadoc
   plugin in the reporting elements of my pom file and the plugin is
   being called during site generation, however:
  
the target/apidoc/index.html is always renders an empty page (but
   not an empty file). the generation was successful because i can the
   actual javadocs for each module class and the other files in the
   apidoc directory seems to contain the correct entries (e.g.
   index-all.html, overview-*.html) and could navigate to the actual
   class javadoc from there.
  
my html skills are virtually nonexistent but i think the most
   pertinent part of the index.html page is the part i quoted below. the
   other parts of the html page seems to be rendered perfectly (sidebars,
   footers, etc.)
   ===
  div id=bodyColumn
  div id=contentBox/div
  /div
  
  div class=clear
  hr /
  /div
   ===
  
  
 my second issue with the javadoc plugin when it is used together
   with the clover plugin. the javadoc plugin is causing the
   clover-plugin to fail. used on its own the clover plugin works fine
   but if i declare the javadoc and clover plugins at the same time then
   the clover plugin will fail with a Can't find bundle for base name
   clover-report, locale fi_FI.  changing the regional settings of my
   workstation to en_US provides a temporary solution but not something
   that management will endorse. as far as i can see the clover plugin
   does not have a configuration setting for locale, and i am still
   confused why this problem will only surface if the javadoc plugin is
   also activated.
  
my third issue with the javadoc was only found when i tried setting
   the locale attribute to en_US to fix my second issue. javadoc
   execution will always fail with a Embedded error: Exit code: 1 -
   javadoc: option -locale must be first on the command line. message
   even though it is the only configuration item for the javadoc plugin
   on my pom.
  
am i doing using these plugins incorrectly? thanks.
  
   ciao!
  
   --
  
   Programming, an artform that fights back
  
   Anuerin G. Diaz
   Registered Linux User #246176
   Friendly Linux Board @ http://mandrivausers.org/index.php
   http://capsule.ramfree17.org , when you absolutely have nothing else
   better to do
  
 
 
  --
 
  Programming, an artform that fights back
 
  Anuerin G. Diaz
  Registered Linux User #246176
  Friendly Linux Board @ http://mandrivausers.org/index.php
  http://capsule.ramfree17.org , when you absolutely have nothing else
  better to do
 
  -
  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]




--

Programming, an artform that fights back

Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do

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



[m2] javadoc plugin

2005-10-21 Thread Samuel Le Berrigaud
Hi,

there is a bug in the current javadoc plugin regarding the site
integration. The link to the javadoc leads to blank page.

The javadoc is correctly generated, however the index page of the
javadoc is overwritten by a blank index page.

I found the bug come from the JavadocReport class of the plugin, this:

public String getOutputName()
{
return apidocs/index;
}

give the plugin its incorrect behavior.

I corrected this to :

public String getOutputName()
{
return javadoc;
}

And I add the following document to my src/site/apt directory:

--
Javadoc

  You can find the javadoc at {{{apidocs/index.html}apidocs/index.html}}
--

This can obviously not be a premanent solution but it works fine for me for now.
I don't know how to integrate this simple APT page into the plugin
directly, if anyone has any hint for me. I would glad to put some
effort on this and the contribute creating a JIRA bug and providing a
first patch maybe...

Thanks,

--
Samuel Le Berrigaud


Re: [m2] javadoc plugin

2005-10-21 Thread David Sag

Would you like to add your fix to the
bug report in Jira?

http://jira.codehaus.org/browse/MNG-1249

Kind regards,
Dave Sag 




 

Samuel Le Berrigaud [EMAIL PROTECTED] wrote
on 21/10/2005 12:54:02 PM:

 Hi,
 
 there is a bug in the current javadoc plugin regarding the site
 integration. The link to the javadoc leads to blank page.
 
 The javadoc is correctly generated, however the index page of the
 javadoc is overwritten by a blank index page.
 
 I found the bug come from the JavadocReport class of the plugin, this:
 
   public String getOutputName()
   {
 return apidocs/index;
   }
 
 give the plugin its incorrect behavior.
 
 I corrected this to :
 
   public String getOutputName()
   {
 return javadoc;
   }
 
 And I add the following document to my src/site/apt directory:
 
 --
 Javadoc
 
  You can find the javadoc at {{{apidocs/index.html}apidocs/index.html}}
 --
 
 This can obviously not be a premanent solution but it works fine for
 me for now.
 I don't know how to integrate this simple APT page into the plugin
 directly, if anyone has any hint for me. I would glad to put some
 effort on this and the contribute creating a JIRA bug and providing
a
 first patch maybe...
 
 Thanks,
 
 --
 Samuel Le Berrigaud


Re: [m2] javadoc plugin and linkoffline

2005-09-26 Thread Martin Skopp

Hi,

Trygve Laugstøl schrieb:

I was thinking something like this:

offlineLinks
  offlineLink
urla/url
packageListUrlb/packageListUrl -- is this really required?
  /offlineLink
/offlineLinks


Yeah, I would also appreciate keeping naming in sync with the 
javadoc-plugin propertly


maven.javadoc.offlineLinks

See http://maven.apache.org/reference/plugins/javadoc/properties.html

Thanks
--
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com

This email is intended to be viewed with a nonproportional font.


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



Re: [m2] javadoc plugin and linkoffline - online links in offline mode

2005-09-26 Thread Martin Skopp

Hi Trygve,

Trygve Laugstøl schrieb:

I was thinking something like this:

offlineLinks
  offlineLink
urla/url
packageListUrlb/packageListUrl -- is this really required?
  /offlineLink
/offlineLinks


It's required to specify a *online URL* and a *offline local path* when 
you want to generates *online links* in offline mode, see 
http://maven.apache.org/reference/plugins/javadoc/faq.html#offlineLinks 
for and example with the maven.javadoc.offlineLinks property.


To generate offline links in offline mode, the local path is sufficient, 
of course.


Regards,
--
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com

This email is intended to be viewed with a nonproportional font.


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



Re: [m2] javadoc plugin and linkoffline

2005-09-23 Thread c_inconnu3

Hi,

I agree with Trygve, it should be better to have something like that

offlineLinks
 offlineLink
   *extdocURL*http://java.sun.com/j2se/1.4.2/docs/api/*/extdocURL*
   *packagelistLoc*my/local/path/to/package-list*/packagelistLoc*
 /offlineLink
 offlineLink
   *extdocURL*...*/extdocURL*
   *packagelistLoc*...*/packagelistLoc*
 /offlineLink
/offlineLinks

rather than an ugly

linkofflinea b, c d/linkoffline

wich could possibly be very very long...

David



Trygve Laugstøl a écrit :


On Thu, 2005-09-22 at 18:46 -0400, Vincent Siveton wrote:
 


Hi Trygve,

   


Try to specify linkoffline as a comma separated list of path or URL.
   


I think it would be best to make the linkoffline a List of Strings, it's
more readable and easier to process for other tools.
 


I agree with you.
I propose linkofflinea b, c d/linkoffline as David tried.
   



I was thinking something like this:

offlineLinks
 offlineLink
   urla/url
   packageListUrlb/packageListUrl -- is this really required?
 /offlineLink
/offlineLinks

 


Is there a reason for the parameter to be named linkoffline instead of
offline-link? Is that the parameter to the javadoc tool?
 


linkoffline is the parameter from the javadoc documentation:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#linkofflin
e
offlineLinkS is the parameter of m1 javadoc plugin.
   



I'd like to keep that name, it's IMO more intuitive.

--
Trygve


-
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]



[m2] javadoc plugin and linkoffline

2005-09-22 Thread c_inconnu3

Hi,

I am trying to generate javadoc with M2 b1. My pom contains :

   reporting
   plugins
   plugin
   groupIdorg.apache.maven.plugins/groupId
   artifactIdmaven-javadoc-plugin/artifactId
   version2.0-beta-1/version
   configuration
   
linkofflinehttp://java.sun.com/j2se/1.4.2/docs/api/ 
../root/src/javadoc/j2sdk-1.4.2//linkoffline

   source1.4/source
   /configuration
   /plugin
   ...
   /plugins
   /reporting

but i got :

[INFO] [javadoc:javadoc]
[INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package 
-source 1.4 -sourcePath D:\projets\ndd\root\..\ndd
14-base\src\main\java -classpath 
D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\

3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\
1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\comm
ons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar -author 
-bottom Copyright null DD. All Rights Reserved
. -charset ISO-8859-1 -d 
D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle NDD Base 
project 0.20-SN
APSHOT API -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/ 
../root/src/javadoc/j2sdk-1.4.2/ -stylesheetfile D:\proj
ets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use -version 
-windowtitle NDD Base project 0.20-SNA

PSHOT API @files
javadoc: Illegal package name: 
D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css

Loading source file myfile1
Loading source file myfile2
..
1 error
[INFO] 


[ERROR] BUILD ERROR
[INFO] 


[INFO] Diagnosis: An error has occurred in JavaDocs report generation.
[INFO] 


[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: An error has occurred in 
JavaDocs report generation.
   at 
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:98)
   at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
   at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)

   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
   at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
   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:324)
   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.reporting.MavenReportException: An error has 
occurred in javadoc report generation.
   at 
org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:841)
   at 
org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:583)
   at 
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:92)

   ... 16 more
Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1
   at 
org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:835)

   ... 18 more
[INFO] 


[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Sep 22 21:35:45 CEST 2005
[INFO] Final Memory: 2M/4M
[INFO] 




Is there something wrong in my pom ?

Thanks

David DIDIER



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



Re: [m2] javadoc plugin and linkoffline

2005-09-22 Thread Vincent Siveton
Hi

Try to specify linkoffline as a comma separated list of path or URL.

Cheers,

Vincent

2005/9/22, c_inconnu3 [EMAIL PROTECTED]:
 Hi,

 I am trying to generate javadoc with M2 b1. My pom contains :

reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.0-beta-1/version
configuration

 linkofflinehttp://java.sun.com/j2se/1.4.2/docs/api/
 ../root/src/javadoc/j2sdk-1.4.2//linkoffline
source1.4/source
/configuration
/plugin
...
/plugins
/reporting

 but i got :

 [INFO] [javadoc:javadoc]
 [INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package
 -source 1.4 -sourcePath D:\projets\ndd\root\..\ndd
 14-base\src\main\java -classpath
 D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\
 3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\
 1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\comm
 ons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar -author
 -bottom Copyright null DD. All Rights Reserved
 . -charset ISO-8859-1 -d
 D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle NDD Base
 project 0.20-SN
 APSHOT API -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/
 ../root/src/javadoc/j2sdk-1.4.2/ -stylesheetfile D:\proj
 ets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use -version
 -windowtitle NDD Base project 0.20-SNA
 PSHOT API @files
 javadoc: Illegal package name:
 D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css
 Loading source file myfile1
 Loading source file myfile2
 ..
 1 error
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Diagnosis: An error has occurred in JavaDocs report generation.
 [INFO]
 
 [ERROR] Cause:
 org.apache.maven.plugin.MojoExecutionException: An error has occurred in
 JavaDocs report generation.
at
 org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:98)
at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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:324)
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.reporting.MavenReportException: An error has
 occurred in javadoc report generation.
at
 org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:841)
at
 org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:583)
at
 org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:92)
... 16 more
 Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1
at
 org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:835)
... 18 more
 [INFO]
 
 [INFO] Total time: 2 seconds
 [INFO] Finished at: Thu Sep 22 21:35:45 CEST 2005
 [INFO] Final Memory: 2M/4M
 [INFO]
 


 Is there something wrong in my pom ?

 Thanks

 David DIDIER



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




Re: [m2] javadoc plugin and linkoffline

2005-09-22 Thread c_inconnu3

I tried

linkofflinea b, c d/linkoffline

but the generated command is then :

javadoc.exe ... -linkoffline a b -linkoffline c d ...

i looked the javadoc documentation and it seems that the syntax should be : 


javadoc.exe ... -linkoffline a b -linkoffline c d ...

(without )



Hi

Try to specify linkoffline as a comma separated list of path or URL.

Cheers,

Vincent

2005/9/22, c_inconnu3 [EMAIL PROTECTED]:
 


Hi,

I am trying to generate javadoc with M2 b1. My pom contains :

  reporting
  plugins
  plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-javadoc-plugin/artifactId
  version2.0-beta-1/version
  configuration

linkofflinehttp://java.sun.com/j2se/1.4.2/docs/api/
../root/src/javadoc/j2sdk-1.4.2//linkoffline
  source1.4/source
  /configuration
  /plugin
  ...
  /plugins
  /reporting

but i got :

[INFO] [javadoc:javadoc]
[INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package
-source 1.4 -sourcePath D:\projets\ndd\root\..\ndd
14-base\src\main\java -classpath
D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\
3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\
1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\comm
ons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar -author
-bottom Copyright null DD. All Rights Reserved
. -charset ISO-8859-1 -d
D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle NDD Base
project 0.20-SN
APSHOT API -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/
../root/src/javadoc/j2sdk-1.4.2/ -stylesheetfile D:\proj
ets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use -version
-windowtitle NDD Base project 0.20-SNA
PSHOT API @files
javadoc: Illegal package name:
D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css
Loading source file myfile1
Loading source file myfile2
..
1 error
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Diagnosis: An error has occurred in JavaDocs report generation.
[INFO]

[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: An error has occurred in
JavaDocs report generation.
  at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:98)
  at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357)
  at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479)
  at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460)
  at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442)
  at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
  at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
  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:324)
  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.reporting.MavenReportException: An error has
occurred in javadoc report generation.
  at
org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:841)
  at
org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:583)
  at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:92)
  ... 16 more
Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1
  at
org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:835)
  ... 18 more
[INFO]

[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Sep 22 21:35:45 CEST 2005
[INFO] Final Memory: 2M/4M
[INFO]



Is there something wrong in my pom ?

Thanks

David DIDIER




Re: [m2] javadoc plugin and linkoffline

2005-09-22 Thread Vincent Siveton
Seems to be a bug. Please fill an issue in JIRA.

Thanks,

Vincent

2005/9/22, c_inconnu3 [EMAIL PROTECTED]:
 I tried

 linkofflinea b, c d/linkoffline

 but the generated command is then :

 javadoc.exe ... -linkoffline a b -linkoffline c d ...

 i looked the javadoc documentation and it seems that the syntax should be :

 javadoc.exe ... -linkoffline a b -linkoffline c d ...

 (without )


 Hi
 
 Try to specify linkoffline as a comma separated list of path or URL.
 
 Cheers,
 
 Vincent
 
 2005/9/22, c_inconnu3 [EMAIL PROTECTED]:
 
 
 Hi,
 
 I am trying to generate javadoc with M2 b1. My pom contains :
 
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.0-beta-1/version
configuration
 
 linkofflinehttp://java.sun.com/j2se/1.4.2/docs/api/
 ../root/src/javadoc/j2sdk-1.4.2//linkoffline
source1.4/source
/configuration
/plugin
...
/plugins
/reporting
 
 but i got :
 
 [INFO] [javadoc:javadoc]
 [INFO] C:\Programmation\j2sdk1.4.2_08\jre\..\bin\javadoc.exe -package
 -source 1.4 -sourcePath D:\projets\ndd\root\..\ndd
 14-base\src\main\java -classpath
 D:\projets\ndd\root\..\base\target\classes;d:\temp\maven2\repository\junit\junit\
 3.8.1\junit-3.8.1.jar;d:\temp\maven2\repository\log4j\log4j\1.2.9\log4j-1.2.9.jar;d:\temp\maven2\repository\commons-io\commons-io\
 1.0\commons-io-1.0.jar;d:\temp\maven2\repository\commons-lang\commons-lang\2.1\commons-lang-2.1.jar;d:\temp\maven2\repository\comm
 ons-primitives\commons-primitives\1.0\commons-primitives-1.0.jar -author
 -bottom Copyright null DD. All Rights Reserved
 . -charset ISO-8859-1 -d
 D:\projets\ndd\root\..\base\target\javadoc\apidocs -doctitle NDD Base
 project 0.20-SN
 APSHOT API -linkoffline http://java.sun.com/j2se/1.4.2/docs/api/
 ../root/src/javadoc/j2sdk-1.4.2/ -stylesheetfile D:\proj
 ets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css -use -version
 -windowtitle NDD Base project 0.20-SNA
 PSHOT API @files
 javadoc: Illegal package name:
 D:\projets\ndd\root\..\base\target\javadoc\apidocs\stylesheet.css
 Loading source file myfile1
 Loading source file myfile2
 ..
 1 error
 [INFO]
 
 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] Diagnosis: An error has occurred in JavaDocs report generation.
 [INFO]
 
 [ERROR] Cause:
 org.apache.maven.plugin.MojoExecutionException: An error has occurred in
 JavaDocs report generation.
at
 org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:98)
at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:357)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:479)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:460)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:442)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
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:324)
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.reporting.MavenReportException: An error has
 occurred in javadoc report generation.
at
 org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:841)
at
 org.apache.maven.plugin.javadoc.JavadocReport.generate(JavadocReport.java:583)
at
 org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:92)
... 16 more
 Caused by: org.apache.maven.reporting.MavenReportException: Exit code: 1
at
 org.apache.maven.plugin.javadoc.JavadocReport.executeReport(JavadocReport.java:835)
... 18 more
 [INFO]
 
 [INFO] Total 

Re: [m2] javadoc plugin and linkoffline

2005-09-22 Thread Trygve Laugstøl
On Thu, 2005-09-22 at 16:13 -0400, Vincent Siveton wrote:
 Hi
 
 Try to specify linkoffline as a comma separated list of path or URL.

I think it would be best to make the linkoffline a List of Strings, it's
more readable and easier to process for other tools.

Is there a reason for the parameter to be named linkoffline instead of
offline-link? Is that the parameter to the javadoc tool?

--
Trygve


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



RE: [m2] javadoc plugin and linkoffline

2005-09-22 Thread Vincent Siveton
Hi Trygve,

  Try to specify linkoffline as a comma separated list of path or URL.
 
 I think it would be best to make the linkoffline a List of Strings, it's
 more readable and easier to process for other tools.

I agree with you.
I propose linkofflinea b, c d/linkoffline as David tried.
 
 Is there a reason for the parameter to be named linkoffline instead of
 offline-link? Is that the parameter to the javadoc tool?

linkoffline is the parameter from the javadoc documentation:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#linkofflin
e
offlineLinkS is the parameter of m1 javadoc plugin.

Cheers,

Vincent


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



RE: [m2] javadoc plugin and linkoffline

2005-09-22 Thread Trygve Laugstøl
On Thu, 2005-09-22 at 18:46 -0400, Vincent Siveton wrote:
 Hi Trygve,
 
   Try to specify linkoffline as a comma separated list of path or URL.
  
  I think it would be best to make the linkoffline a List of Strings, it's
  more readable and easier to process for other tools.
 
 I agree with you.
 I propose linkofflinea b, c d/linkoffline as David tried.

I was thinking something like this:

offlineLinks
  offlineLink
urla/url
packageListUrlb/packageListUrl -- is this really required?
  /offlineLink
/offlineLinks

  Is there a reason for the parameter to be named linkoffline instead of
  offline-link? Is that the parameter to the javadoc tool?
 
 linkoffline is the parameter from the javadoc documentation:
 http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/javadoc.html#linkofflin
 e
 offlineLinkS is the parameter of m1 javadoc plugin.

I'd like to keep that name, it's IMO more intuitive.

--
Trygve


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