You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Michael Mior <mm...@apache.org> on 2020/01/07 11:35:19 UTC
Gradle documentation update
I noticed when the changed was made from Maven to Gradle, the documentation
on the development page has not been updated. I can change the compilation
command, but could any IDE users update the documentation there?
--
Michael Mior
mmior@apache.org
Re: Gradle documentation update
Posted by Francis Chuang <fr...@apache.org>.
What I meant was that
https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d#diff-efedb3376e58f7bcc03c666d03682ce3R154
looked like it was built from calcite's master branch, so the
documentation is missing.
The site branch does not have any commits for gradle:
https://github.com/apache/calcite/commits/site
If the changes need to be published immediately, then the commits should
also be cherry-picked into the site branch, which can then be built.
I agree that the site vs master branch is not easy to work with. I am
working with infra to get automated builds implemented, so that we won't
have to manually push the site as a first step towards making it easier.
Francis
On 8/01/2020 7:58 am, Vladimir Sitnikov wrote:
>> Can you cherry pick the appropriate commits for the migration
>> into the site branch?
>
> What do you mean by that?
> Can we just revert the invalid commits and be done with it?
>
> I already suggested that the site update should be simplified,
> and now we have clear evidence that the current process of "site vs master"
> is prone to errors.
>
> Vladimir
>
Re: Gradle documentation update
Posted by Vladimir Sitnikov <si...@gmail.com>.
>Can you cherry pick the appropriate commits for the migration
>into the site branch?
What do you mean by that?
Can we just revert the invalid commits and be done with it?
I already suggested that the site update should be simplified,
and now we have clear evidence that the current process of "site vs master"
is prone to errors.
Vladimir
Re: Gradle documentation update
Posted by Francis Chuang <fr...@apache.org>.
Ah, I see the problem now. I always build the site from the site branch
(as there may be things on master that shouldn't be published before a
release). Can you cherry pick the appropriate commits for the migration
into the site branch? I'll rebuild and push the site.
Francis
On 8/01/2020 7:47 am, Vladimir Sitnikov wrote:
> Francis>There is
> Francis>
> https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d
> ,
> Francis>but there doesn't appear to be any changes to the build
> instructions for
> Francis>gradle.
>
> Here you go:
> https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d#diff-efedb3376e58f7bcc03c666d03682ce3R154
>
> It looks like you reverted that in
> https://github.com/apache/calcite-site/commit/86a9751a303872bad8b062b0a727a3375ad9eaa7
>
> Vladimir
>
Re: Gradle documentation update
Posted by Vladimir Sitnikov <si...@gmail.com>.
Francis>There is
Francis>
https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d
,
Francis>but there doesn't appear to be any changes to the build
instructions for
Francis>gradle.
Here you go:
https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d#diff-efedb3376e58f7bcc03c666d03682ce3R154
It looks like you reverted that in
https://github.com/apache/calcite-site/commit/86a9751a303872bad8b062b0a727a3375ad9eaa7
Vladimir
Re: Gradle documentation update
Posted by Francis Chuang <fr...@apache.org>.
I pushed the latest site files under the avatica folder only in that
commit. There were no changes to Calcite's site (everything other than
the avatica folder).
There is
https://github.com/apache/calcite-site/commit/81960613e7750a9191280719352ae941a7d6a22d,
but there doesn't appear to be any changes to the build instructions for
gradle.
Francis
On 8/01/2020 1:17 am, Vladimir Sitnikov wrote:
> It looks like Francis recently pushed "Update website for Avatica 1.16"
> which looks like
> 1,674 changed files with 167,295 additions and 628,539 deletions.
> https://github.com/apache/calcite-site/commit/3d92029cc7718e2b66d888dc9021047879145465
>
> Francis, can you please double-check?
>
> Vladimir
>
Re: Gradle documentation update
Posted by Vladimir Sitnikov <si...@gmail.com>.
It looks like Francis recently pushed "Update website for Avatica 1.16"
which looks like
1,674 changed files with 167,295 additions and 628,539 deletions.
https://github.com/apache/calcite-site/commit/3d92029cc7718e2b66d888dc9021047879145465
Francis, can you please double-check?
Vladimir
Re: Gradle documentation update
Posted by Stamatis Zampetakis <za...@gmail.com>.
Note that the master branch documentation [1][2] seems to be updated with
respect to gradle. The problem seems to be related with what is pushed in
git@github.com:apache/calcite-site.
[1] https://github.com/apache/calcite/blob/master/site/_docs/howto.md
[2] https://github.com/apache/calcite/blob/master/site/develop/index.md
On Tue, Jan 7, 2020 at 1:18 PM Forward Xu <fo...@gmail.com> wrote:
> OK, I can try to fix this.
>
> Feng Zhu <we...@gmail.com> 于2020年1月7日周二 下午8:05写道：
>
> > I also noticed the same problem several days ago when a colleague
> > complained he failed to build Calcite according to the documents on
> > website.
> >
> >
> > E.g.,
> >
> >
> https://calcite.apache.org/docs/howto.html#building-from-a-source-distribution
> >
> >
> >
> >
> >
> >
> >
> >
> > *$ git clone git://github.com/apache/calcite.git
> > <http://github.com/apache/calcite.git>$ cd calcite$ ./mvnw install $ mvn
> > clean$ mvn package... hacks ...$ mvn package -DskipGenerate*
> >
> > https://calcite.apache.org/develop/#download-source-build-and-run-tests
> >
> >
> > *$ git clone git://github.com/apache/calcite.git
> > <http://github.com/apache/calcite.git>$ cd calcite$ mvn install*
> >
> > Vladimir Sitnikov <si...@gmail.com> 于2020年1月7日周二 下午7:44写道：
> >
> > > Can you clarify an url which has stale information?
> > >
> > > Vladimir
> > >
> >
>
Re: Gradle documentation update
Posted by Forward Xu <fo...@gmail.com>.
OK, I can try to fix this.
Feng Zhu <we...@gmail.com> 于2020年1月7日周二 下午8:05写道：
> I also noticed the same problem several days ago when a colleague
> complained he failed to build Calcite according to the documents on
> website.
>
>
> E.g.,
>
> https://calcite.apache.org/docs/howto.html#building-from-a-source-distribution
>
>
>
>
>
>
>
>
> *$ git clone git://github.com/apache/calcite.git
> <http://github.com/apache/calcite.git>$ cd calcite$ ./mvnw install $ mvn
> clean$ mvn package... hacks ...$ mvn package -DskipGenerate*
>
> https://calcite.apache.org/develop/#download-source-build-and-run-tests
>
>
> *$ git clone git://github.com/apache/calcite.git
> <http://github.com/apache/calcite.git>$ cd calcite$ mvn install*
>
> Vladimir Sitnikov <si...@gmail.com> 于2020年1月7日周二 下午7:44写道：
>
> > Can you clarify an url which has stale information?
> >
> > Vladimir
> >
>
Re: Gradle documentation update
Posted by Feng Zhu <we...@gmail.com>.
I also noticed the same problem several days ago when a colleague
complained he failed to build Calcite according to the documents on website.
E.g.,
https://calcite.apache.org/docs/howto.html#building-from-a-source-distribution
*$ git clone git://github.com/apache/calcite.git
<http://github.com/apache/calcite.git>$ cd calcite$ ./mvnw install $ mvn
clean$ mvn package... hacks ...$ mvn package -DskipGenerate*
https://calcite.apache.org/develop/#download-source-build-and-run-tests
*$ git clone git://github.com/apache/calcite.git
<http://github.com/apache/calcite.git>$ cd calcite$ mvn install*
Vladimir Sitnikov <si...@gmail.com> 于2020年1月7日周二 下午7:44写道：
> Can you clarify an url which has stale information?
>
> Vladimir
>
Re: Gradle documentation update
Posted by Michael Mior <mm...@apache.org>.
Sorry for not specifying earlier, it's the pages linked below. If you
search for "mvn" and "pom.xml" you'll see the instances I mean. It
looks like the release documentation also still uses Maven.
https://calcite.apache.org/develop/
https://calcite.apache.org/docs/howto.html
--
Michael Mior
mmior@apache.org
Le mar. 7 janv. 2020 à 06:44, Vladimir Sitnikov
<si...@gmail.com> a écrit :
>
> Can you clarify an url which has stale information?
>
> Vladimir
Re: Gradle documentation update
Posted by Vladimir Sitnikov <si...@gmail.com>.
Can you clarify an url which has stale information?
Vladimir
Re: Gradle documentation update
Posted by Michael Mior <mm...@apache.org>.
Thanks Stamatis!
--
Michael Mior
mmior@apache.org
Le mer. 5 févr. 2020 à 07:29, Stamatis Zampetakis <za...@gmail.com> a écrit :
>
> The build instructions on the Website are still outdated (they still
> mention mvn).
> If nobody picks this up, I will try to align things tomorrow since more and
> more people encounter problems when building master.
>
> Best,
> Stamatis
>
> On Fri, Jan 24, 2020 at 12:01 AM Michael Mior <mm...@apache.org> wrote:
>
> > No, the site is updated apart from releases, but any changes aside
> > from a release are made manually. This is so that we can fix bugs on
> > the site or make updates not related to code while keeping the
> > documentation consistent with the latest released version.
> >
> > --
> > Michael Mior
> > mmior@apache.org
> >
> > Le jeu. 23 janv. 2020 à 17:42, Rui Wang <am...@apache.org> a écrit :
> > >
> > > Not sure if it is related: the change of reference.md that I submitted in
> > > [1] hasn't appeared on [2]
> > >
> > > Question: does the Calcite reference webpage only get updated when
> > > releasing? (if not it might have been overwritten by an older version).
> > >
> > >
> > > [1]: https://github.com/apache/calcite/pull/1587
> > > [2]: https://calcite.apache.org/docs/reference.html
> > >
> > >
> > > -Rui
> > >
> > > On Tue, Jan 21, 2020 at 6:00 PM Michael Mior <mm...@apache.org> wrote:
> > >
> > > > It looks like things are much simpler than I thought. In the current
> > > > state of the site branch, the Gradle changes (which happened since the
> > > > last Calcite release) have not been cherry picked onto the site
> > > > branch. I'm happy to do this although it means the directions will be
> > > > wrong when building from a release. I think this is better than being
> > > > wrong for the current master.
> > > > --
> > > > Michael Mior
> > > > mmior@apache.org
> > > >
> > > > Le mar. 7 janv. 2020 à 06:35, Michael Mior <mm...@apache.org> a écrit
> > :
> > > > >
> > > > > I noticed when the changed was made from Maven to Gradle, the
> > > > documentation on the development page has not been updated. I can
> > change
> > > > the compilation command, but could any IDE users update the
> > documentation
> > > > there?
> > > > > --
> > > > > Michael Mior
> > > > > mmior@apache.org
> > > >
> >
Re: Gradle documentation update
Posted by Julian Hyde <jh...@apache.org>.
No objection to SQLLine printing some helpful instructions, as long as there is a way for more advanced users to turn it off.
I can’t think of a mechanism in SQLLine to run a startup script, but there probably is one.
> On Feb 6, 2020, at 1:55 AM, Vladimir Sitnikov <si...@gmail.com> wrote:
>
>> If you notice anything weird let me know.
>
> Thank you.
>
> ---
>
> I recently found that ./sqlline is non-trivial, especially when non-expert
> is using it.
>
> What do you think if we make ./sqlline to print sample commands right after
> it starts?
>
> We have pre-defined data sets.
> What if ./sqlline printed a couple of lines right at the startup, so the
> user could copy-paste them to connect to the datasets?
>
> It would probably make sense to add !echo and !startupscript commands to
> Sqlline so
> Calcite's sqlline could print the welcome message and suggest the way to
> connect and
> it could even suggest a couple of SQLs to try.
>
> ---
>
> As a side note, it might be interesting to have Calcite playground.
> It could be like https://rextester.com/l/postgresql_online_compiler but
> with Calcite inside.
>
> Vladimir
Re: Gradle documentation update
Posted by Vladimir Sitnikov <si...@gmail.com>.
>If you notice anything weird let me know.
Thank you.
---
I recently found that ./sqlline is non-trivial, especially when non-expert
is using it.
What do you think if we make ./sqlline to print sample commands right after
it starts?
We have pre-defined data sets.
What if ./sqlline printed a couple of lines right at the startup, so the
user could copy-paste them to connect to the datasets?
It would probably make sense to add !echo and !startupscript commands to
Sqlline so
Calcite's sqlline could print the welcome message and suggest the way to
connect and
it could even suggest a couple of SQLs to try.
---
As a side note, it might be interesting to have Calcite playground.
It could be like https://rextester.com/l/postgresql_online_compiler but
with Calcite inside.
Vladimir
Re: Gradle documentation update
Posted by Stamatis Zampetakis <za...@gmail.com>.
I committed a few things on apache/site and pushed the changes to
apache/calcite-site.
The Gradle documentation in the Website looks to be fine now.
If you notice anything weird let me know.
Best,
Stamatis
On Wed, Feb 5, 2020 at 1:29 PM Stamatis Zampetakis <za...@gmail.com>
wrote:
> The build instructions on the Website are still outdated (they still
> mention mvn).
> If nobody picks this up, I will try to align things tomorrow since more
> and more people encounter problems when building master.
>
> Best,
> Stamatis
>
> On Fri, Jan 24, 2020 at 12:01 AM Michael Mior <mm...@apache.org> wrote:
>
>> No, the site is updated apart from releases, but any changes aside
>> from a release are made manually. This is so that we can fix bugs on
>> the site or make updates not related to code while keeping the
>> documentation consistent with the latest released version.
>>
>> --
>> Michael Mior
>> mmior@apache.org
>>
>> Le jeu. 23 janv. 2020 à 17:42, Rui Wang <am...@apache.org> a écrit :
>> >
>> > Not sure if it is related: the change of reference.md that I submitted
>> in
>> > [1] hasn't appeared on [2]
>> >
>> > Question: does the Calcite reference webpage only get updated when
>> > releasing? (if not it might have been overwritten by an older version).
>> >
>> >
>> > [1]: https://github.com/apache/calcite/pull/1587
>> > [2]: https://calcite.apache.org/docs/reference.html
>> >
>> >
>> > -Rui
>> >
>> > On Tue, Jan 21, 2020 at 6:00 PM Michael Mior <mm...@apache.org> wrote:
>> >
>> > > It looks like things are much simpler than I thought. In the current
>> > > state of the site branch, the Gradle changes (which happened since the
>> > > last Calcite release) have not been cherry picked onto the site
>> > > branch. I'm happy to do this although it means the directions will be
>> > > wrong when building from a release. I think this is better than being
>> > > wrong for the current master.
>> > > --
>> > > Michael Mior
>> > > mmior@apache.org
>> > >
>> > > Le mar. 7 janv. 2020 à 06:35, Michael Mior <mm...@apache.org> a
>> écrit :
>> > > >
>> > > > I noticed when the changed was made from Maven to Gradle, the
>> > > documentation on the development page has not been updated. I can
>> change
>> > > the compilation command, but could any IDE users update the
>> documentation
>> > > there?
>> > > > --
>> > > > Michael Mior
>> > > > mmior@apache.org
>> > >
>>
>
Re: Gradle documentation update
Posted by Stamatis Zampetakis <za...@gmail.com>.
The build instructions on the Website are still outdated (they still
mention mvn).
If nobody picks this up, I will try to align things tomorrow since more and
more people encounter problems when building master.
Best,
Stamatis
On Fri, Jan 24, 2020 at 12:01 AM Michael Mior <mm...@apache.org> wrote:
> No, the site is updated apart from releases, but any changes aside
> from a release are made manually. This is so that we can fix bugs on
> the site or make updates not related to code while keeping the
> documentation consistent with the latest released version.
>
> --
> Michael Mior
> mmior@apache.org
>
> Le jeu. 23 janv. 2020 à 17:42, Rui Wang <am...@apache.org> a écrit :
> >
> > Not sure if it is related: the change of reference.md that I submitted in
> > [1] hasn't appeared on [2]
> >
> > Question: does the Calcite reference webpage only get updated when
> > releasing? (if not it might have been overwritten by an older version).
> >
> >
> > [1]: https://github.com/apache/calcite/pull/1587
> > [2]: https://calcite.apache.org/docs/reference.html
> >
> >
> > -Rui
> >
> > On Tue, Jan 21, 2020 at 6:00 PM Michael Mior <mm...@apache.org> wrote:
> >
> > > It looks like things are much simpler than I thought. In the current
> > > state of the site branch, the Gradle changes (which happened since the
> > > last Calcite release) have not been cherry picked onto the site
> > > branch. I'm happy to do this although it means the directions will be
> > > wrong when building from a release. I think this is better than being
> > > wrong for the current master.
> > > --
> > > Michael Mior
> > > mmior@apache.org
> > >
> > > Le mar. 7 janv. 2020 à 06:35, Michael Mior <mm...@apache.org> a écrit
> :
> > > >
> > > > I noticed when the changed was made from Maven to Gradle, the
> > > documentation on the development page has not been updated. I can
> change
> > > the compilation command, but could any IDE users update the
> documentation
> > > there?
> > > > --
> > > > Michael Mior
> > > > mmior@apache.org
> > >
>
Re: Gradle documentation update
Posted by Michael Mior <mm...@apache.org>.
No, the site is updated apart from releases, but any changes aside
from a release are made manually. This is so that we can fix bugs on
the site or make updates not related to code while keeping the
documentation consistent with the latest released version.
--
Michael Mior
mmior@apache.org
Le jeu. 23 janv. 2020 à 17:42, Rui Wang <am...@apache.org> a écrit :
>
> Not sure if it is related: the change of reference.md that I submitted in
> [1] hasn't appeared on [2]
>
> Question: does the Calcite reference webpage only get updated when
> releasing? (if not it might have been overwritten by an older version).
>
>
> [1]: https://github.com/apache/calcite/pull/1587
> [2]: https://calcite.apache.org/docs/reference.html
>
>
> -Rui
>
> On Tue, Jan 21, 2020 at 6:00 PM Michael Mior <mm...@apache.org> wrote:
>
> > It looks like things are much simpler than I thought. In the current
> > state of the site branch, the Gradle changes (which happened since the
> > last Calcite release) have not been cherry picked onto the site
> > branch. I'm happy to do this although it means the directions will be
> > wrong when building from a release. I think this is better than being
> > wrong for the current master.
> > --
> > Michael Mior
> > mmior@apache.org
> >
> > Le mar. 7 janv. 2020 à 06:35, Michael Mior <mm...@apache.org> a écrit :
> > >
> > > I noticed when the changed was made from Maven to Gradle, the
> > documentation on the development page has not been updated. I can change
> > the compilation command, but could any IDE users update the documentation
> > there?
> > > --
> > > Michael Mior
> > > mmior@apache.org
> >
Re: Gradle documentation update
Posted by Rui Wang <am...@apache.org>.
Not sure if it is related: the change of reference.md that I submitted in
[1] hasn't appeared on [2]
Question: does the Calcite reference webpage only get updated when
releasing? (if not it might have been overwritten by an older version).
[1]: https://github.com/apache/calcite/pull/1587
[2]: https://calcite.apache.org/docs/reference.html
-Rui
On Tue, Jan 21, 2020 at 6:00 PM Michael Mior <mm...@apache.org> wrote:
> It looks like things are much simpler than I thought. In the current
> state of the site branch, the Gradle changes (which happened since the
> last Calcite release) have not been cherry picked onto the site
> branch. I'm happy to do this although it means the directions will be
> wrong when building from a release. I think this is better than being
> wrong for the current master.
> --
> Michael Mior
> mmior@apache.org
>
> Le mar. 7 janv. 2020 à 06:35, Michael Mior <mm...@apache.org> a écrit :
> >
> > I noticed when the changed was made from Maven to Gradle, the
> documentation on the development page has not been updated. I can change
> the compilation command, but could any IDE users update the documentation
> there?
> > --
> > Michael Mior
> > mmior@apache.org
>
Re: Gradle documentation update
Posted by Michael Mior <mm...@apache.org>.
It looks like things are much simpler than I thought. In the current
state of the site branch, the Gradle changes (which happened since the
last Calcite release) have not been cherry picked onto the site
branch. I'm happy to do this although it means the directions will be
wrong when building from a release. I think this is better than being
wrong for the current master.
--
Michael Mior
mmior@apache.org
Le mar. 7 janv. 2020 à 06:35, Michael Mior <mm...@apache.org> a écrit :
>
> I noticed when the changed was made from Maven to Gradle, the documentation on the development page has not been updated. I can change the compilation command, but could any IDE users update the documentation there?
> --
> Michael Mior
> mmior@apache.org
Re: Gradle documentation update
Posted by Stamatis Zampetakis <za...@gmail.com>.
Thanks for picking this up Michael!
I was hoping that we could have a release quite soon so that the branches
get synced but since you already did the work go ahead. No objections here.
Best,
Stamatis
On Tue, Jan 21, 2020 at 9:43 PM Julian Hyde <jh...@apache.org> wrote:
> Fine, but be sure to take down 'site-new' when it gets stale.
>
> On Tue, Jan 21, 2020 at 9:40 AM Michael Mior <mm...@apache.org> wrote:
> >
> > Starting with the latest release, I cherry picked the commits which
> > were added on the site branch. I've pushed this as "site-new". While I
> > think there may be a better solution long term, I'm being repeatedly
> > impacted by the broken documentation currently on the site which I'd
> > like to fix soon. If there are no objections, I'll force push this
> > branch to site later this week (making sure to check for any other
> > changes which might happen between now and then).
> > --
> > Michael Mior
> > mmior@apache.org
> >
> > Le jeu. 9 janv. 2020 à 06:24, forwardxu <23...@qq.com> a écrit :
> > >
> > > Well +1, Need to build a Jira to modify it?
> > > 在 2020/1/7 下午7:35，“Michael Mior”<mm...@apache.org> 写入:
> > >
> > > I noticed when the changed was made from Maven to Gradle, the
> documentation
> > > on the development page has not been updated. I can change the
> compilation
> > > command, but could any IDE users update the documentation there?
> > > --
> > > Michael Mior
> > > mmior@apache.org
> > >
> > >
> > >
>
Re: Gradle documentation update
Posted by Michael Mior <mm...@apache.org>.
I put this branch up only so others can look. I'll delete it
immediately after the site branch is fixed.
--
Michael Mior
mmior@apache.org
Le mar. 21 janv. 2020 à 15:43, Julian Hyde <jh...@apache.org> a écrit :
>
> Fine, but be sure to take down 'site-new' when it gets stale.
>
> On Tue, Jan 21, 2020 at 9:40 AM Michael Mior <mm...@apache.org> wrote:
> >
> > Starting with the latest release, I cherry picked the commits which
> > were added on the site branch. I've pushed this as "site-new". While I
> > think there may be a better solution long term, I'm being repeatedly
> > impacted by the broken documentation currently on the site which I'd
> > like to fix soon. If there are no objections, I'll force push this
> > branch to site later this week (making sure to check for any other
> > changes which might happen between now and then).
> > --
> > Michael Mior
> > mmior@apache.org
> >
> > Le jeu. 9 janv. 2020 à 06:24, forwardxu <23...@qq.com> a écrit :
> > >
> > > Well +1, Need to build a Jira to modify it?
> > > 在 2020/1/7 下午7:35，“Michael Mior”<mm...@apache.org> 写入:
> > >
> > > I noticed when the changed was made from Maven to Gradle, the documentation
> > > on the development page has not been updated. I can change the compilation
> > > command, but could any IDE users update the documentation there?
> > > --
> > > Michael Mior
> > > mmior@apache.org
> > >
> > >
> > >
Re: Gradle documentation update
Posted by Julian Hyde <jh...@apache.org>.
Fine, but be sure to take down 'site-new' when it gets stale.
On Tue, Jan 21, 2020 at 9:40 AM Michael Mior <mm...@apache.org> wrote:
>
> Starting with the latest release, I cherry picked the commits which
> were added on the site branch. I've pushed this as "site-new". While I
> think there may be a better solution long term, I'm being repeatedly
> impacted by the broken documentation currently on the site which I'd
> like to fix soon. If there are no objections, I'll force push this
> branch to site later this week (making sure to check for any other
> changes which might happen between now and then).
> --
> Michael Mior
> mmior@apache.org
>
> Le jeu. 9 janv. 2020 à 06:24, forwardxu <23...@qq.com> a écrit :
> >
> > Well +1, Need to build a Jira to modify it?
> > 在 2020/1/7 下午7:35，“Michael Mior”<mm...@apache.org> 写入:
> >
> > I noticed when the changed was made from Maven to Gradle, the documentation
> > on the development page has not been updated. I can change the compilation
> > command, but could any IDE users update the documentation there?
> > --
> > Michael Mior
> > mmior@apache.org
> >
> >
> >
Re: Gradle documentation update
Posted by Michael Mior <mm...@apache.org>.
Starting with the latest release, I cherry picked the commits which
were added on the site branch. I've pushed this as "site-new". While I
think there may be a better solution long term, I'm being repeatedly
impacted by the broken documentation currently on the site which I'd
like to fix soon. If there are no objections, I'll force push this
branch to site later this week (making sure to check for any other
changes which might happen between now and then).
--
Michael Mior
mmior@apache.org
Le jeu. 9 janv. 2020 à 06:24, forwardxu <23...@qq.com> a écrit :
>
> Well +1, Need to build a Jira to modify it?
> 在 2020/1/7 下午7:35，“Michael Mior”<mm...@apache.org> 写入:
>
> I noticed when the changed was made from Maven to Gradle, the documentation
> on the development page has not been updated. I can change the compilation
> command, but could any IDE users update the documentation there?
> --
> Michael Mior
> mmior@apache.org
>
>
>
Re: Gradle documentation update
Posted by forwardxu <23...@qq.com>.
Well +1, Need to build a Jira to modify it?
在 2020/1/7 下午7:35，“Michael Mior”<mm...@apache.org> 写入:
I noticed when the changed was made from Maven to Gradle, the documentation
on the development page has not been updated. I can change the compilation
command, but could any IDE users update the documentation there?
--
Michael Mior
mmior@apache.org