At the moment, the build issues the following warning:

Building an Old (1.x) Archetype: consider migrating it to current 2.x Archetype.

We should investigate why we get this warning and then make the switch to the 2.x archetype format. (Note that I don’t think we get this warning accidentally, as part of bug ARCHETYPE-483; we use a version of the maven-archetype-plugin where this bug is fixed already.)

mvn archetype:generate
-DarchetypeArtifactId=spotbugs-archetype
-DarchetypeGroupId=com.github.spotbugs
-DarchetypeVersion=0.2.3

[ERROR] [ERROR] Some problems were encountered while processing the
[ERROR] Unresolveable build extension: Plugin org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8 or one of its dependencies could not be resolved: Failed to collect dependencies at org.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.8 -> org.sonatype.nexus:nexus-client-core:jar:2.14.3-02 @
[ERROR] Unknown packaging: maven-archetype @ line 8, column 14
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.github.spotbugs:spotbugs-archetype:0.2.3-SNAPSHOT (/xxxxxxx/myfindbug/spotbugs-archetype/pom.xml) has 2 errors
[ERROR] Unresolveable build extension: Plugin org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8 or one of its dependencies could not be resolved: Failed to collect dependencies at org.sonatype.plugins:nexus-staging-maven-plugin:jar:1.6.8 -> org.sonatype.nexus:nexus-client-core:jar:2.14.3-02: Failed to read artifact descriptor for org.sonatype.nexus:nexus-client-core:jar:2.14.3-02: Could not transfer artifact org.sonatype.nexus.buildsupport:nexus-buildsupport-commons:pom:2.14.3-02 from/to rso-public-grid (https://repository.sonatype.org/content/groups/sonatype-public-grid/): Remote host closed connection during handshake: SSL peer shut down incorrectly -> [Help 2]
[ERROR] Unknown packaging: maven-archetype @ line 8, column 14
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/PluginManagerException

i need help!!!

example: https://github.com/spotbugs/spotbugs-archetype/runs/3407947557?check_suite_focus=true#step:6:1880

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Deployment to maven failed.

The deployment to maven failed for an unknown reason.

Please check the logs on the CI server to see what happened.

Good luck with your project ✨

Your semantic-release bot 📦🚀

SpotBugs will release 3.1.0 final soon, then we can release v0.2.0 from this repo.
We also need to update following documents:

• http://spotbugs.readthedocs.io/en/latest/implement-plugin.html
• https://github.com/spotbugs/spotbugs-archetype#how-to-use

#131 moved the GPG sign from Travis to GitHub Actions, but it's not working as expected:
https://github.com/spotbugs/spotbugs-archetype/runs/2562113326

Build fails when I use :

mvn archetype:generate \
    -DarchetypeArtifactId=spotbugs-archetype \
    -DarchetypeGroupId=com.github.spotbugs \
    -DarchetypeVersion=0.2.4

You can see it here in this screenshot :

However, if you change the version to 0.2.0 instead of 0.2.4, Like shown in command given below, it works just fine:

mvn archetype:generate \
    -DarchetypeArtifactId=spotbugs-archetype \
    -DarchetypeGroupId=com.github.spotbugs \
    -DarchetypeVersion=0.2.0

Please refer the screenshot given below:

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Deployment to maven failed.

The deployment to maven failed for an unknown reason.

Please check the logs on the CI server to see what happened.

Good luck with your project ✨

Your semantic-release bot 📦🚀