-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
localRepository
deprecated in Maven 3.9.1
#264
Comments
Thanks for pointing this out, yet it's not that easy ;-) I was able to switch to the new APIs in the plugin, but when I tried to use it with my example app I've got
and have no idea what's wrong :( |
@lukaszlenart Do you have a WIP PR with the changes you did already? |
@akuhtz I pushed a SNAPSHOT version into OSS - 2.4.0-SNAPSHOT, just configure the repo: <pluginRepositories>
<pluginRepository>
<id>oss-snapshots</id>
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
<layout>default</layout>
<name>OSS Sonatype Snapshots</name>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories> |
Right now I get
|
@lukaszlenart I hope I fixed it with #271 . Can you try on your side? |
This time
but I think I know what's wrong |
#272 let's the build pass with maven-3.8.8 and 3.9.1 |
Thanks a lot @akuhtz ! It works, pushed a new SNAPSHOT into OSS, please double check and I will prepare a new release :) |
@lukaszlenart It works for me, too 👍 |
Cool, could you approve the PR? |
Done. |
I wanted to swing back and say thank you all for responding an addressing this so quickly. I got sidetracked with some other bugs with unrelated plugins, but now I've got a chance to upgrade this plugin and it looks like it fixed the issue. Great work. Much appreciated! |
On Windows 10 I just upgraded to Maven 3.9.1 and my builds that include
launch4j:2.1.3:launch4j
are now showing:(I have the Launch4J Maven Plugin defined in a parent project but only enabled under certain conditions, so basically I now get this warning all over the place even if the Launch4J Maven Plugin isn't being used in a project, because it is still referenced just not enabled.)
The warning speaks for itself. This seems to be from MNG-7706, implemented in apache/maven#1012. It's also listed in the v3.9.1 deprecation list.
Hopefully this is some easy change to make to update to the latest approach for getting some value? I think there are more technical details in the ticket MNG-7706 (which I haven't had a chance to read thoroughly yet).
The text was updated successfully, but these errors were encountered: