What command are you using to do that? I just ran "mvn javadoc:javadoc"
from the config dir and it worked. Could it be a file encoding issue?
Jeanfrancois Arcand wrote:
> Salut,
>
> now I'm getting:
>
>> Generating
>> /home/jfarcand/workspace/grizzly/release/code/contribs/grizzly-config/target/site/apidocs/stylesheet.css...
>>
>> [INFO] Generating "Test JavaDocs" report.
>> [WARNING] Source files encoding has not been set, using platform
>> encoding UTF-8, i.e. build is platform dependent!
>> Loading source files for package com.sun.grizzly.config.dom...
>> Constructing Javadoc information...
>> 1 error
>> 2 warnings
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error during page generation
>>
>> Embedded error: Error rendering Maven report: Exit code: 1 - javadoc:
>> warning - No source files for package com.sun.grizzly.config.dom
>> javadoc: warning - No source files for package
>> com.sun.grizzly.config.dom
>> javadoc: error - No public or protected classes found to document.
>>
>> Command line was:/usr/java/jdk1.6.0_04/jre/../bin/javadoc @options
>
> when doing mvn site. Any idea (I don't underatnd why it fail!)
>
> A+
>
> -- Jeanfrancois
>
> Justin Lee wrote:
>> OK. I had to dig through the glassfish poms to find where it was
>> finding those dependencies. That commit should fix it.
>>
>> Shing Wai Chan wrote:
>>> I just update my grizzly workspace and see the following:
>>> WAGON_VERSION: 1.0-beta-1
>>> Downloading:
>>> http://download.java.net/maven/2//com/sun/enterprise/hk2-maven-plugin/0.3.41/hk2-maven-plugin-0.3.41.pom
>>>
>>> Downloading:
>>> http://repo1.maven.org/maven2/com/sun/enterprise/hk2-maven-plugin/0.3.41/hk2-maven-plugin-0.3.41.pom
>>>
>>> Downloading:
>>> http://download.java.net/maven/2/com/sun/enterprise/hk2-maven-plugin/0.3.41/hk2-maven-plugin-0.3.41.pom
>>>
>>> Downloading:
>>> http://repository.codehaus.org/com/sun/enterprise/hk2-maven-plugin/0.3.41/hk2-maven-plugin-0.3.41.pom
>>>
>>> Downloading:
>>> http://repo1.maven.org/maven2/com/sun/enterprise/hk2-maven-plugin/0.3.41/hk2-maven-plugin-0.3.41.pom
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Error building POM (may not be this project's POM).
>>>
>>>
>>> Project ID: com.sun.enterprise:hk2-maven-plugin
>>>
>>> Reason: POM 'com.sun.enterprise:hk2-maven-plugin' not found in
>>> repository: Unable to download the artifact from any repository
>>>
>>> com.sun.enterprise:hk2-maven-plugin:pom:0.3.41
>>>
>>> from the specified remote repositories:
>>> java.net (http://download.java.net/maven/2),
>>> codehaus (http://repository.codehaus.org),
>>> glassfish (http://download.java.net/maven/2/),
>>> central (http://repo1.maven.org/maven2)
>>> for project com.sun.enterprise:hk2-maven-plugin
>>>
>>> Is it related to this?
>>> Thanks.
>>> Shing Wai Chan
>>>
>>> Justin Lee wrote:
>>>> OK. I'll commit it so you can take a look at it while I fix that
>>>> test. I did move some classes from glassfish->grizzly which makes
>>>> me nervous a bit. I'd like more experienced hands to make sure
>>>> what I have is (politically) correct. I've tried to excise as many
>>>> glassfish deps as I can which makes certain parts of this more
>>>> awkward than I like but I decided to focus on getting it working
>>>> first then refactoring out those deps with input from the wider
>>>> community. I'm going to talk to Nazrul/Kedar today about branching
>>>> glassfish (or using an existing branch) and trying to finish the
>>>> integration on that end.
>>>>
>>>> But feedback would be very much appreciated. I know there are a
>>>> lot of rough edges here that could use some smoothing over.
>>>>
>>>> Jeanfrancois Arcand wrote:
>>>>> Salut,
>>>>>
>>>>> Justin Lee wrote:
>>>>>> :)
>>>>>
>>>>> :-) Great! You should commit so it gets included in 1.9.6 (this is
>>>>> a start!)
>>>>>
>>>>>>
>>>>>> Now I'm running a test with a basic xml file and have a
>>>>>> question. Do we want to imply the presence of certain elements
>>>>>> (like Http) or require them in the document. My preference is to
>>>>>> require them in the document for now and relax that requirement
>>>>>> down the road as we build in better defaults. Requiring them up
>>>>>> front now would let us move on to things like glassfish
>>>>>> integration which, imo, is a more pressing need. Opinions?
>>>>>
>>>>> I agree. I like the step by step approach...but this steps is
>>>>> quite big!!!
>>>>>
>>>>> A+
>>>>>
>>>>> -- Jeanfrancois
>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>>>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>