-
Notifications
You must be signed in to change notification settings - Fork 156
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
in pom files, set name to have 'Apache Pekko ...' #1006
Comments
Do you mean the |
artifactId must stay as |
I just gave it a try for demo project, it's ok, I am preparing a PR for pekko
|
@laglangyue I would hold off a bit as we are trying to verify if we actually need to do this, @pjfanning Has more details. If we do end up needing to do this we will also likely end up creating an abstraction in https://github.com/pjfanning/sbt-pekko-build |
okey, waitting for this |
changes made |
Our poms are generated by sbt and the name in the pom closely matches the artifactId
https://repo1.maven.org/maven2/org/apache/pekko/pekko-stream_3/1.0.2/pekko-stream_3-1.0.2.pom
See name=pekko-stream, artifactId=pekko-stream_3
We only set the name in sbt but if we change it, it affects the artifactId. We need to keep the artifactId as is.
But for this pom, we should have name=Apache Pekko Stream (or something like that - Apache Pekko bit is the key).
Requirement comes in https://lists.apache.org/thread/wmp9g94fo2yb4tsg238467d6hx72dbml
Liable to become something that can block our releases and graduation to be a TLP.
I have tried a few sbt changes but nothing that gets the results that we need.
The text was updated successfully, but these errors were encountered: