Skip to content
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

Attach Javadoc jar to build #25

Closed

Conversation

stevenschlansker
Copy link
Contributor

@hgschmie
Copy link
Contributor

Any specific reason (the javadoc jar does get built for releases) that it should also be built for every normal build? Happy to add it (the same is done for sources); in that case I would drop it from the oss release profile.

@hgschmie
Copy link
Contributor

@stevenschlansker
Copy link
Contributor Author

Oh, I think release only is fine. I think the problem I had was that the non-OSS ones do not attach javadoc.

So maybe the better fix is to add this to the non-OSS release profile.

@hgschmie
Copy link
Contributor

I consider closing this, as the javadoc jar is built as part of the release.

@hgschmie hgschmie closed this in 93a7d41 Nov 23, 2016
hgschmie pushed a commit to hgschmie/basepom that referenced this pull request Nov 23, 2016
@stevenschlansker stevenschlansker deleted the attach-javadoc branch November 23, 2016 17:26
hgschmie pushed a commit to hgschmie/basepom that referenced this pull request Oct 29, 2019
Introduces a new setting "basepom.javadoc.skip" to skip the generation
of javadoc jars. This is unconditionally turned off for the oss
release profile.

Fixes basepom#25.
hgschmie pushed a commit to hgschmie/basepom that referenced this pull request Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants