Re: JavaDoc-Report crashes with TestNG

2008-08-26 Thread WolfgangRoessler

No, otherwise I wouldn't have asked here *g*.
Could you create one?

Greets
Wolfgang


Brett Porter wrote:
> 
> Thanks - have you an identified an existing JIRA issue for this?
> 
> - Brett
> 
> 2008/8/26 WolfgangRoessler <[EMAIL PROTECTED]>:
>>
>> Hi Brett,
>>
>> that works. If I set the scope to compile (or the default), the
>> javadoc-generation works. Another solution is to configure a report
>> without
>> test-classes:
>> 
>>
>>
>>javadoc
>>
>>
>> 
>>
>> Thanks and greets
>> Wolfgang
>>
>>
>> Brett Porter wrote:
>>>
>>> That looks like a bug in the javadoc plugin that it isn't using test
>>> scoped dependencies for the test javadoc (if you change the scope of
>>> testng to "compile" or "runtime", does it work even though it is not
>>> correct?)
>>>
>>> I'm not sure about the doclet exception - looks like a javadoc error -
>>> does running javadoc standalone work?
>>>
>>> - Brett
>>>
>>> 2008/8/26 WolfgangRoessler <[EMAIL PROTECTED]>:
>>>>
>>>> Unfortunately this doesn't work, too.
>>>>
>>>> Here are some snippets of my pom:
>>>>  
>>>>
>>>>org.testng
>>>>testng
>>>>5.8
>>>>jdk15
>>>>test
>>>>
>>>>  
>>>>  
>>>>
>>>>
>>>>org.apache.maven.plugins
>>>>maven-javadoc-plugin
>>>>
>>>>1.6
>>>>true
>>>>
>>>>
>>>>
>>>>  
>>>>
>>>> And here part of the error messages (debug-mode):
>>>> While building project:
>>>> Group-Id: prototype.codequality
>>>> Artifact-Id: top
>>>> Version: 0.0.1-SNAPSHOT
>>>> From file: S:\src\Exploratory
>>>> Prototypes\CodeQualityTools\src\top\pom.xml
>>>> Reason: Error during page generation
>>>>
>>>> org.apache.maven.doxia.siterenderer.RendererException: Error rendering
>>>> Maven
>>>> report: Exit code: 1 - S:\src\Exploratory
>>>> Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:3:
>>>> package org.testng does not exist
>>>> import org.testng.Assert;
>>>> ^
>>>> S:\src\Exploratory
>>>> Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:4:
>>>> package org.testng.annotations does not exist
>>>> import org.testng.annotations.Test;
>>>> ^
>>>> ...
>>>> java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot
>>>> be
>>>> cast to com.sun.javadoc.AnnotationTypeDoc
>>>>at
>>>> com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
>>>>at
>>>> com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811)
>>>> ...
>>>>
>>>> Greets
>>>> Wolfgang
>>>>
>>>>
>>>> Brett Porter wrote:
>>>>>
>>>>> I think you need to set  instead. If that doesn't work, please
>>>>> describe what the "crash" looks like.
>>>>>
>>>>> Cheers,
>>>>> Brett
>>>>>
>>>>> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>>>>>
>>>>>> I set the javadocVersion, but the plugin still crashes.
>>>>>>
>>>>>> - Wolfgang
>>>>>>
>>>>>>
>>>>>> Brett Porter wrote:
>>>>>>>
>>>>>>> Do you need to configure it to use Java's 1.5 source level?
>>>>>>>
>>>>>>> - Brett
>>>>>>>
>>>>>>> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>

Re: JavaDoc-Report crashes with TestNG

2008-08-26 Thread WolfgangRoessler

Hi Brett,

that works. If I set the scope to compile (or the default), the
javadoc-generation works. Another solution is to configure a report without
test-classes:



javadoc


   

Thanks and greets
Wolfgang


Brett Porter wrote:
> 
> That looks like a bug in the javadoc plugin that it isn't using test
> scoped dependencies for the test javadoc (if you change the scope of
> testng to "compile" or "runtime", does it work even though it is not
> correct?)
> 
> I'm not sure about the doclet exception - looks like a javadoc error -
> does running javadoc standalone work?
> 
> - Brett
> 
> 2008/8/26 WolfgangRoessler <[EMAIL PROTECTED]>:
>>
>> Unfortunately this doesn't work, too.
>>
>> Here are some snippets of my pom:
>>  
>>
>>org.testng
>>testng
>>5.8
>>jdk15
>>test
>>
>>  
>>  
>>
>>
>>org.apache.maven.plugins
>>maven-javadoc-plugin
>>
>>1.6
>>true
>>
>>
>>
>>  
>>
>> And here part of the error messages (debug-mode):
>> While building project:
>> Group-Id: prototype.codequality
>> Artifact-Id: top
>> Version: 0.0.1-SNAPSHOT
>> From file: S:\src\Exploratory Prototypes\CodeQualityTools\src\top\pom.xml
>> Reason: Error during page generation
>>
>> org.apache.maven.doxia.siterenderer.RendererException: Error rendering
>> Maven
>> report: Exit code: 1 - S:\src\Exploratory
>> Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:3:
>> package org.testng does not exist
>> import org.testng.Assert;
>> ^
>> S:\src\Exploratory
>> Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:4:
>> package org.testng.annotations does not exist
>> import org.testng.annotations.Test;
>> ^
>> ...
>> java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot
>> be
>> cast to com.sun.javadoc.AnnotationTypeDoc
>>at
>> com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
>>at
>> com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811)
>> ...
>>
>> Greets
>> Wolfgang
>>
>>
>> Brett Porter wrote:
>>>
>>> I think you need to set  instead. If that doesn't work, please
>>> describe what the "crash" looks like.
>>>
>>> Cheers,
>>> Brett
>>>
>>> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>>>
>>>> I set the javadocVersion, but the plugin still crashes.
>>>>
>>>> - Wolfgang
>>>>
>>>>
>>>> Brett Porter wrote:
>>>>>
>>>>> Do you need to configure it to use Java's 1.5 source level?
>>>>>
>>>>> - Brett
>>>>>
>>>>> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have configured the maven-javadoc-plugin in the reporting section.
>>>>>> Unfortunately when generating the report, the plugin crashes. The
>>>>>> exceptions
>>>>>> look like it has problems with the @Test annotation of TestNG. Any
>>>>>> ideas
>>>>>> or
>>>>>> solutions what happens?
>>>>>>
>>>>>> Greets
>>>>>> Wolfgang Roessler
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.html
>>>>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>> -
>>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Brett Porter
>>>>> Blog: http://blogs.exis

JDepend for pom-project

2008-08-25 Thread WolfgangRoessler

Hello,

I have a multi-module project. The top project has the packaging type "pom"
and I have configured jdepend-maven-plugin in the reporting section, so that
jdepend gets executed for all modules. But the build stops when executing
jdepend for the top project with the following message:

Directory does not exist: S:\src\Exploratory
Prototypes\CodeQualityTools\src\top\target\classes

It looks like JDepend does not work for pom-projects. Any solutions for
this? Do I have to configure JDepend for each module?

Greets
Wolfgang
-- 
View this message in context: 
http://www.nabble.com/JDepend-for-pom-project-tp19151632p19151632.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: JavaDoc-Report crashes with TestNG

2008-08-25 Thread WolfgangRoessler

Unfortunately this doesn't work, too.

Here are some snippets of my pom:
  

org.testng
testng
5.8
jdk15
test

  
  


org.apache.maven.plugins
maven-javadoc-plugin

1.6
true



  

And here part of the error messages (debug-mode):
While building project:
Group-Id: prototype.codequality
Artifact-Id: top
Version: 0.0.1-SNAPSHOT
>From file: S:\src\Exploratory Prototypes\CodeQualityTools\src\top\pom.xml
Reason: Error during page generation

org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven
report: Exit code: 1 - S:\src\Exploratory
Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:3:
package org.testng does not exist
import org.testng.Assert;
 ^
S:\src\Exploratory
Prototypes\CodeQualityTools\src\top\top-module1\src\test\java\codequality\top\module1\TestClassInModule1.java:4:
package org.testng.annotations does not exist
import org.testng.annotations.Test;
 ^
...
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be
cast to com.sun.javadoc.AnnotationTypeDoc
at
com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
at
com.sun.tools.doclets.internal.toolkit.util.Util.isDeprecated(Util.java:811)
...

Greets
Wolfgang


Brett Porter wrote:
> 
> I think you need to set  instead. If that doesn't work, please
> describe what the "crash" looks like.
> 
> Cheers,
> Brett
> 
> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>
>> I set the javadocVersion, but the plugin still crashes.
>>
>> - Wolfgang
>>
>>
>> Brett Porter wrote:
>>>
>>> Do you need to configure it to use Java's 1.5 source level?
>>>
>>> - Brett
>>>
>>> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>>>
>>>> Hello,
>>>>
>>>> I have configured the maven-javadoc-plugin in the reporting section.
>>>> Unfortunately when generating the report, the plugin crashes. The
>>>> exceptions
>>>> look like it has problems with the @Test annotation of TestNG. Any
>>>> ideas
>>>> or
>>>> solutions what happens?
>>>>
>>>> Greets
>>>> Wolfgang Roessler
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.html
>>>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Brett Porter
>>> Blog: http://blogs.exist.com/bporter/
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19140451.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> 
> -- 
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19151139.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Taglist and Dashboard

2008-08-25 Thread WolfgangRoessler

Hello,

I want to include the report of taglist-maven-plugin into my maven-dashboard
report. I found out, that currently the taglist-plugin does not support
xml-output and therefore cannot be aggregated by the dashboard-plugin. I
know there is a patch for this available. When will this patch be
incorporated and a new snapshot-release be available?

Greets
Wolfgang
-- 
View this message in context: 
http://www.nabble.com/Taglist-and-Dashboard-tp19143343p19143343.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: JavaDoc-Report crashes with TestNG

2008-08-25 Thread WolfgangRoessler

I set the javadocVersion, but the plugin still crashes.

- Wolfgang


Brett Porter wrote:
> 
> Do you need to configure it to use Java's 1.5 source level?
> 
> - Brett
> 
> 2008/8/25 WolfgangRoessler <[EMAIL PROTECTED]>:
>>
>> Hello,
>>
>> I have configured the maven-javadoc-plugin in the reporting section.
>> Unfortunately when generating the report, the plugin crashes. The
>> exceptions
>> look like it has problems with the @Test annotation of TestNG. Any ideas
>> or
>> solutions what happens?
>>
>> Greets
>> Wolfgang Roessler
>> --
>> View this message in context:
>> http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> 
> -- 
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19140451.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



JavaDoc-Report crashes with TestNG

2008-08-25 Thread WolfgangRoessler

Hello,

I have configured the maven-javadoc-plugin in the reporting section.
Unfortunately when generating the report, the plugin crashes. The exceptions
look like it has problems with the @Test annotation of TestNG. Any ideas or
solutions what happens?

Greets
Wolfgang Roessler
-- 
View this message in context: 
http://www.nabble.com/JavaDoc-Report-crashes-with-TestNG-tp19139379p19139379.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



eclipse:to-maven ... pom-version problems

2008-04-02 Thread WolfgangRoessler

Hello,

I have a problem when using eclipse:to-maven. For example
org.eclipse.emf:ecore has a dependency to org.eclipse.runtime:core with a
version range [3.2.0,4.00). Unfortunately the version of
org.eclipse.runtime:core is something like 3.2.0-v20071103 so maven can't
resolve the version. Are there any solutions for this problem? (except for
using make-artifacts which generates different artifactIds).

Thanks
Wolfgang
-- 
View this message in context: 
http://www.nabble.com/eclipse%3Ato-maven-...-pom-version-problems-tp16465803s177p16465803.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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