slachiewicz opened a new pull request, #181:
URL: https://github.com/apache/maven-doap-plugin/pull/181
`writeReleases()` builds the `doap:file-release` artifact from
`project.getPackaging()` only, so for a jar/war/etc.-packaged ASF project it
points at the packaged artifact in the repo instead of the distributed
`*-source-release.zip`, as this issue requested.
Adds two mojo parameters, `fileReleaseClassifier` and `fileReleaseType`, to
override the artifact resolved for `file-release`, e.g.:
```xml
<configuration>
<fileReleaseClassifier>source-release</fileReleaseClassifier>
<fileReleaseType>zip</fileReleaseType>
</configuration>
```
`isArtifactInRepository`'s existence check previously built its Aether
coordinates without a classifier, which would have silently broken this feature
(checking the wrong artifact); that's now classifier-aware too. Default
behavior (no override) is unchanged.
Not covered by a new test: no existing test in this module drives
`writeReleases` far enough to hit metadata/artifact resolution against a real
repository (every test pom logs "No versioning was found... Ignored DOAP
`<release/>` tag"), so this mirrors existing test coverage rather than adding a
first test for that path. Verified with `mvn test` (13/13 passing) and `mvn
spotless:check`.
Fixes #102
*This change was created with AI assistance.*
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
