Hi Maik,

finally I had a look at the Javadoc problem and I could identify the cause of 
the problem. In one of those package.html file theres was some Javascript code 
hidden—in this case as simple as javascript:void(0)—which made the Javadoc task 
to stop execution and thus did prevent creation of the missing html files we 
were searching for.

Besides some other little fixes I removed that Javascript and voila I am 
getting all files I had expected. I just pushed a commit on master, please 
check if it is correctly building the Javadoc files on the Jenkins server.

jw


> Am 06.04.2017 um 10:26 schrieb Musall, Maik <m...@selbstdenker.ag>:
> 
> Hey guys,
> 
> seems like no one is able to help. But now I tried generating the javadocs on 
> the console, and when I do "ant docs", I also end up with a directory 
> dist/wonder/Documentation/api that only contains com and er subdirectories, 
> but no index.html and stuff.
> 
> (I also had encoding errors to overcome because ant would see utf-8 sources 
> as ascii, fix is in https://github.com/maiksd/wonder/tree/docs-fixes.)
> 
> Now, if someone can help resolving this to a point that javadocs can be build 
> on the console from the current wonder repo, I might be able to take it from 
> there.
> 
> Maik
> 
> 
>> Am 28.03.2017 um 20:24 schrieb Musall, Maik <m...@selbstdenker.ag>:
>> 
>> Hi Johann,
>> 
>> here's the config.xml from the Wonder7 job. It's basically the same as on 
>> the old Jenkins. (I hope this attachment makes it through the mailing list 
>> server.)
>> 
>> Maik
>> 
> <config.xml>
>> 
>> 
>> 
>>> Am 28.03.2017 um 15:07 schrieb Johann Werner <j...@oyosys.de>:
>>> 
>>> Hi Maik,
>>> 
>>> can you tell us what Jenkins config you did? Perhaps screenshots of the job 
>>> configuration page? You should not need any special plugins to create the 
>>> Javadocs, just the existing Wonder build.xml, ant and the correct job setup 
>>> ;-)
>>> 
>>> jw
>>> 
>>> 
>>>> Am 22.03.2017 um 01:16 schrieb Maik Musall <m...@selbstdenker.ag>:
>>>> 
>>>> Hi Paul,
>>>> 
>>>> I mainly copied the old config over, but the previous jenkins version was 
>>>> very old, and this one is now current. I don’t know if that could 
>>>> influence things. I tend to think it doesn’t. But perhaps I’m missing some 
>>>> plugin or something.
>>>> 
>>>> Maik
>>>> 
>>>>> Am 22.03.2017 um 00:50 schrieb Paul Hoadley <pa...@logicsquad.net>:
>>>>> 
>>>>> Hi Maik,
>>>>> 
>>>>> On 22 Mar 2017, at 01:40, Musall, Maik <m...@selbstdenker.ag> wrote:
>>>>> 
>>>>>> In regard to the javadoc, I mostly get the same result in jenkins as I 
>>>>>> get with a local cmdline build. I was hoping someone with better ant 
>>>>>> skills can take a look.
>>>>> 
>>>>> I’ve never tried to build the Javadocs from source, but it must be 
>>>>> doable. Maik, were you able to copy over the configuration from the old 
>>>>> Jenkins instance, or have you had to set this up from scratch? Pascal, do 
>>>>> you have a few minutes to take a look at some stage?
>>>>> 
>>>>> 
>>>>> --
>>>>> Paul Hoadley
>>>>> http://logicsquad.net/
>>>>> 
>>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/maik%40selbstdenker.ag
>> 
>> This email sent to m...@selbstdenker.ag
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to