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

Problems when using tiles-maven-plugin ( was don't attach release-pom as a "pom" ) #2

Open
talios opened this issue Feb 25, 2016 · 0 comments

Comments

@talios
Copy link

talios commented Feb 25, 2016

Currently the plugin attaches the generated release-pom.xml to the project as a POM artifact on https://github.com/rvowles/release-pom/blob/master/src/main/groovy/com/bluetrainsoftware/maven/ReleasePomMojo.groovy#L202, unforuntely this means it gets deployed/renamed as a .pom file on release, which trips up the oss.sonatype.org validation.

I suspect this is related to tiles-maven-plugin usage however, as it seems the Sonatype validation is failing due to missing svm/developer/plugins sections etc.

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

No branches or pull requests

1 participant