-
Notifications
You must be signed in to change notification settings - Fork 50
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 Maven plugin #314
Comments
Closed
truhroth
pushed a commit
that referenced
this issue
Sep 30, 2024
truhroth
pushed a commit
that referenced
this issue
Sep 30, 2024
truhroth
pushed a commit
that referenced
this issue
Sep 30, 2024
ascheman
added a commit
that referenced
this issue
Sep 30, 2024
ascheman
added a commit
that referenced
this issue
Sep 30, 2024
truhroth
pushed a commit
that referenced
this issue
Oct 16, 2024
truhroth
pushed a commit
that referenced
this issue
Oct 16, 2024
truhroth
pushed a commit
that referenced
this issue
Oct 16, 2024
truhroth
pushed a commit
that referenced
this issue
Nov 9, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
ascheman
added a commit
that referenced
this issue
Nov 20, 2024
ascheman
added a commit
that referenced
this issue
Nov 20, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
ascheman
pushed a commit
that referenced
this issue
Nov 20, 2024
truhroth
pushed a commit
that referenced
this issue
Nov 26, 2024
ascheman
pushed a commit
that referenced
this issue
Dec 14, 2024
ascheman
pushed a commit
that referenced
this issue
Jan 24, 2025
ascheman
pushed a commit
that referenced
this issue
Jan 24, 2025
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
And make it compilable (but exclude it from test execution until we can call Maven appropriately from Maven). POMs should use the just built Maven plugin (version)
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
The POM is only used to generate the Plugin descriptor. Build and test is moved back to Gradle.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
Perhaps it was left from some merge action?
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
We must ensure that other modules from the Gradle tree are not only built but also published to some internal repository. The Maven based Plugin descriptor (and the helper descriptor) needs to include all (transitive) dependencies of the Mojo.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
The final jar needs to contain several files built by and for Maven as it is required for Maven plugins.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
They need to be build with Gradle though they are only relevant to the Maven plugin.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
It seems the respective publishing tasks are not completely executed though they have internal dependencies to each other. Additionally, when executed together with "clean", parts of the publications are missing, in particular the Gradle plugin marker POM.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
ascheman
pushed a commit
that referenced
this issue
Jan 24, 2025
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
with other integration tests (CLI and Gradle plugin) as all should check for the same files to produce a comparable result.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
It is enough to require pom packaging for simple documentation tasks, as they have a much smaller life cycle.
ascheman
added a commit
that referenced
this issue
Jan 24, 2025
as the integration tests builds the full READMEs of all components. Then check them for consistency with each UI, i.e., with CLI, Gradle, and Maven.
ascheman
pushed a commit
that referenced
this issue
Jan 24, 2025
ascheman
added a commit
that referenced
this issue
Jan 26, 2025
Should be re-enabled later in the course of #372
ascheman
pushed a commit
that referenced
this issue
Jan 27, 2025
ascheman
added a commit
that referenced
this issue
Jan 27, 2025
Should be re-enabled later in the course of #372
Delivered with 2.0.0-rc3 |
ascheman
added a commit
that referenced
this issue
Jan 27, 2025
Builds and integration tests copy many files to the mavenBuildRepo. But JReleaser only wants to find the files for upload to Maven Central. Therefore we copy those file to a `mavenStagingRepo`. Somehow this seems to also have solved occasional flaws wrt signing the artifacts which is necessary for Maven Central.
ascheman
added a commit
that referenced
this issue
Jan 27, 2025
Builds and integration tests copy many files to the mavenBuildRepo. But JReleaser only wants to find the files for upload to Maven Central. Therefore we copy those file to a `mavenStagingRepo`. Somehow this seems to also have solved occasional flaws wrt signing the artifacts which is necessary for Maven Central.
ascheman
added a commit
that referenced
this issue
Jan 27, 2025
Builds and integration tests copy many files to the mavenBuildRepo. But JReleaser only wants to find the files for upload to Maven Central. Therefore we copy those file to a `mavenStagingRepo`. Somehow this seems to also have solved occasional flaws wrt signing the artifacts which is necessary for Maven Central.
ascheman
added a commit
that referenced
this issue
Feb 7, 2025
ascheman
added a commit
that referenced
this issue
Feb 7, 2025
by fixing/adding current implementation links (CLI + Plugins)
ascheman
added a commit
that referenced
this issue
Feb 7, 2025
for README files on GitHub. And fix some typos.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a user of HSC I would like to use HSC from Maven as well.
The text was updated successfully, but these errors were encountered: