[ 
https://issues.apache.org/jira/browse/LUCENE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056084#comment-13056084
 ] 

Robert Muir commented on LUCENE-3228:
-------------------------------------

I am glad you had the same "WTF", although ant docs say its ok to use both, the 
current tasks in e.g. lucene have both the link attribute and nested 
link-without-href-wtf, and as i tried mixing linkoffline in different ways, it 
would appear to work, until i changed the link to javaBROKENURL.sun.com/...., 
etc.

I think we should go with this patch so we aren't downloading this junk 
anymore, it causes false build failures, the only trick I can think of is how 
to ensure lucene source releases build by themself without reaching back to 
dev-tools (i think this is broken on trunk at the moment, but it does work on 
3.x right now)

> build should allow you (especially hudson) to refer to a local javadocs 
> installation instead of downloading
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3228
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3228
>             Project: Lucene - Java
>          Issue Type: Task
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>         Attachments: LUCENE-3228.patch
>
>
> Currently, we fail on all javadocs warnings.
> However, you get a warning if it cannot download the package-list from sun.com
> So I think we should allow you optionally set a sysprop using linkoffline.
> Then we would get much less hudson "fake failures"
> I feel like Mike opened an issue for this already but I cannot find it.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to