slawekjaranowski merged PR #119:
URL: https://github.com/apache/maven-install-plugin/pull/119
--
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: issues-uns
slawekjaranowski merged PR #102:
URL: https://github.com/apache/maven-install-plugin/pull/102
--
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: issues-uns
slawekjaranowski commented on PR #119:
URL:
https://github.com/apache/maven-install-plugin/pull/119#issuecomment-2676671415
> https://github.com/apache/maven-compiler-plugin/pull/287/files
>
> there you also added templates, why not here? (same question as deploy
plugin PR)
No
slawekjaranowski commented on PR #102:
URL:
https://github.com/apache/maven-install-plugin/pull/102#issuecomment-2635880588
> we already have many Jira to GH Issues migration started
https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching
can we share progress, le
hboutemy commented on PR #102:
URL:
https://github.com/apache/maven-install-plugin/pull/102#issuecomment-2635819697
we already have many Jira to GH Issues migration started
https://cwiki.apache.org/confluence/display/MAVEN/JIRA+to+GitHub+Issues+switching
can we share progress, learnings,
slawekjaranowski commented on PR #102:
URL:
https://github.com/apache/maven-install-plugin/pull/102#issuecomment-2635778629
> Compared with our PRs like this. Only difference is that in some (for
exmaple resources) a small PR_automation.yml was also added to label things.
But I think it's
