You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Uwe Schindler (Jira)" <ji...@apache.org> on 2020/05/01 18:22:00 UTC
[jira] [Comment Edited] (LUCENE-9321) Port documentation task to
gradle
[ https://issues.apache.org/jira/browse/LUCENE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097573#comment-17097573 ]
Uwe Schindler edited comment on LUCENE-9321 at 5/1/20, 6:21 PM:
----------------------------------------------------------------
Sorry I still disagree with this:
- On Windows it takes minutes to copy the stuff to one place. In addition the whole Javadocs is hundreds of megabytes and I don't want them 2 times on my computer, just for packagaing AND linting purposes!
- The precommit / javadoc-lint task (as discussed with [~rcmuir] before in the other issue) is there to validate the links and the javadocs as a whole. Just to run this task I see no reason to copy all of this around.
In short: There's no problem in changing the JavaPlugin's javadocs output folder to place eventhing at a different target location. In addition, the "gradle clean" folder does everything correct. So what's the issue to change th output? The Maven packaging should also have no problem with that.
So why are you arguing to have the javadocs splattered around the build tree?
was (Author: thetaphi):
Sorry I still disagree with this:
- On Windows it takes minutes to copy the stuff to one place. In addition the whole Javadocs is hundreds of megabytes and I don't want them 2 times on my computer, just for packagaing AND linting purposes!
- The precommit / javadoc-lint task (as discussed with [~rcmuir] before in the other issue) is there to validate the links and the javadocs as a whole. Just to run this task I see no reason to copy all of this around.
In short: There's no problem in changing the JavaPlugin's javadocs output folder to place eventhing at a different target location. Even the "gradle clean" folder does everything correct. So what's the issue to change th output? The Maven packaging should also have no problem with that.
So why are you arguing to have the javadocs splattered around the build tree?
> Port documentation task to gradle
> ---------------------------------
>
> Key: LUCENE-9321
> URL: https://issues.apache.org/jira/browse/LUCENE-9321
> Project: Lucene - Core
> Issue Type: Sub-task
> Components: general/build
> Reporter: Tomoko Uchida
> Assignee: Tomoko Uchida
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This is a placeholder issue for porting ant "documentation" task to gradle. The generated documents should be able to be published on lucene.apache.org web site on "as-is" basis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org