-
Notifications
You must be signed in to change notification settings - Fork 46
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
Proposal: Change the package name for the code and tests #20
Comments
Make sense, I will make the package change to |
Hi @oleg-nenashev , I made the changes and publish it soon. Thanks for the suggestion. |
Thank you!
…On Sun, Dec 20, 2020, 09:24 Aytunc BEKEN ***@***.***> wrote:
Closed #20
<#20>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAW4RIBIYV6XUKR7POJAHC3SVWYERANCNFSM4O5YLO5Q>
.
|
Released with 0.14-rc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the code uses the
org.jenkinsci.plugins.workflow.multibranch.yaml.pipeline;
package. A few concerns there:org.jenkinsci.plugins.workflow
is an old root for Pipeline plugins. Maybe it makes sense to useio.jenkins.plugins.pipeline
multibranch
does not seem to be needed, the code does not really depend on MultiBranch logicIf we do the change, it needs to happen before 1.0 release. It will be a breaking change, and I doubt it makes sense to spend time on data migration logic to prevent that.
The text was updated successfully, but these errors were encountered: