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

Add publishing of source archives #133

Merged
merged 4 commits into from
Mar 10, 2024

Conversation

tudortimi
Copy link
Owner

@tudortimi tudortimi commented Mar 10, 2024

This only implements a very limited part of publishing of source archive. It only considers SystemVerilog code which resides in the conventional location src/main/sv. This should be enough to implement also the complementary side of consuming a source archive (going deep), before implementing all types of sources (going wide).

This will be part of the artifact that will be published by the project. The other part, aside from sources, will be metadata necessary to compile them.

Currently, the task assumes that the SV source is in the conventional location. This will be fixed later to work in the general case.
This can only be done by creating the artifact from a `SoftwareComponent`. This actually has to be a `SoftwareComponentInternal`, however, otherwise Gradle will complain about cast errors in the Maven publishing code. Unfortunately we have to implement an internal API.
Defining custom components is possible using the public API: https://docs.gradle.org/8.6/userguide/publishing_customization.html#sec:publishing-custom-components.

The name of the variant is not configurable anymore. It's just going to be the name of the configuration we used to define the variant. This is not a big deal, as the name is not used anywhere, only its attributes matter.
We can add an example project that consumes this artifact once we implement that part.
@tudortimi tudortimi merged commit 8d7a57a into master Mar 10, 2024
1 check passed
@tudortimi tudortimi deleted the add-publishing-of-source-archives branch March 10, 2024 11:20
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

1 participant