Skip to content

Add Spring-specific styling to Gradle Plugin's documentation #16327

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

hsellik
Copy link
Contributor

@hsellik hsellik commented Mar 26, 2019

This commit replaces the default Asciidoctor styling with
Spring specific styling.

First, we need to unzip the contents of the Spring Asciidoctor
documentation resources provided by the
io.spring.docsresources:spring-docs-resources distribution zip. This
is done in a /target/refdocs folder. We then copy all files from
src/main/asciidoc to the same location, and then launch the generation
process.

Closes gh-15990

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Mar 26, 2019
Copy link
Member

@snicoll snicoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for opening your first PR.

The change to single file to multiple files broke the creation of the zip that does not contain the documentation anymore. I've just pushed a similar polish for the actuator doc. Would you mind taking a look and update your PR so that the ZIP contains the same content?

Also, I question the creation of attributes.adoc as part of this PR and would like that change to be reverted unless absolutely necessary for the task at hand.

Thanks!

@snicoll snicoll added type: documentation A documentation update status: waiting-for-feedback We need additional information before we can continue and removed status: waiting-for-triage An issue we've not yet triaged labels Mar 29, 2019
@snicoll snicoll added this to the 2.2.x milestone Mar 29, 2019
hsellik added 2 commits March 29, 2019 18:49
This commit replaces the default Asciidoctor styling with
Spring specific styling.

First, we need to unzip the contents of the Spring Asciidoctor
documentation resources provided by the
`io.spring.docsresources:spring-docs-resources` distribution zip. This
is done in a `/target/refdocs` folder. We then copy all files from
`src/main/asciidoc` to the same location, and then launch the generation
process.

Closes spring-projectsgh-15990
This commit will put adoc attributes back to index.adoc and fix the
issue where documentation was not properly packaged into a zip file.

Closes spring-projectsgh-16327
@hsellik
Copy link
Contributor Author

hsellik commented Mar 29, 2019

@snicoll, Thank you for the hint.

Updated the PR (34a545e) and zip contains the docs as in actuator plugin. Also reverted attributes.adoc.

@snicoll snicoll removed the status: waiting-for-feedback We need additional information before we can continue label Mar 31, 2019
@snicoll snicoll self-assigned this Mar 31, 2019
@snicoll snicoll modified the milestones: 2.2.x, 2.2.0.M2 Apr 2, 2019
snicoll pushed a commit that referenced this pull request Apr 2, 2019
This commit replaces the default Asciidoctor styling with
Spring specific styling.

First, we need to unzip the contents of the Spring Asciidoctor
documentation resources provided by the
`io.spring.docsresources:spring-docs-resources` distribution zip. This
is done in a `/target/refdocs` folder. We then copy all files from
`src/main/asciidoc` to the same location, and then launch the generation
process.

See gh-16327
@snicoll snicoll closed this in c4b1a22 Apr 2, 2019
snicoll added a commit that referenced this pull request Apr 2, 2019
* pr/16327:
  Polish "Add Spring-specific styling to Gradle Plugin's documentation"
  Add Spring-specific styling to Gradle Plugin's documentation
@pivotal-issuemaster
Copy link

@hsellik Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@snicoll snicoll reopened this Apr 2, 2019
@snicoll
Copy link
Member

snicoll commented Apr 2, 2019

@hsellik it looks like you haven't signed the CLA. Please sign it ASAP or we'll have to revert this contribution.

@wilkinsona
Copy link
Member

@snicoll I think that was the CLA bot making a mistake. According to #16182, @hsellik has already signed.

@snicoll
Copy link
Member

snicoll commented Apr 2, 2019

Thanks Andy. That PR was flagged as first time contributor and I did ask rob to check our records first so something must be different (different email address?)

@wilkinsona
Copy link
Member

They both use the same email address as far as I can tell. Perhaps the bot has been confused by all the other commits on #16182 and it's generated a false positive there for it having been signed.

@pivotal-issuemaster
Copy link

@hsellik Thank you for signing the Contributor License Agreement!

@hsellik
Copy link
Contributor Author

hsellik commented Apr 2, 2019

They both use the same email address as far as I can tell. Perhaps the bot has been confused by all the other commits on #16182 and it's generated a false positive there for it having been signed.

Oh, sorry. The reason was that I changed my GitHub username. Didn't think it will have this effect.

@wilkinsona
Also, the #16182 was my very first contribution to Open Source, therefore I made a mistake of pushing it to the master. Should I make a new PR so #16182 could be closed?

@snicoll
Copy link
Member

snicoll commented Apr 3, 2019

Oh, sorry. The reason was that I changed my GitHub username. Didn't think it will have this effect.

Yeah that's probably it. Thanks for signing the CLA in any case.

@snicoll snicoll closed this Apr 3, 2019
@snicoll
Copy link
Member

snicoll commented Apr 3, 2019

Should I make a new PR so #16182 could be closed?

No need, I just synced the PR and you're all set. Thanks for your contributions so far!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: documentation A documentation update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add Spring-specific styling to the Gradle Plugin's documentation
5 participants