jira-importer commented on issue #226: URL: https://github.com/apache/maven-install-plugin/issues/226#issuecomment-2771853122
**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** commented Am torn here... this "watch" thing (if am right, it relies on [this](https://github.com/apache/karaf/blob/main/bundle/core/src/main/java/org/apache/karaf/bundle/core/internal/BundleWatcherImpl.java#L209) and especially on [Parser](https://github.com/apache/karaf/blob/b21ac87194dd9820e20eb1cf16539f8a7d4f4ff6/util/src/main/java/org/apache/karaf/util/maven/Parser.java#L422) and these are "naive" implementations of maven repo. In other words, while in maven2 times the local and remote repositories were pretty much similar (you could produce non-timestamped versions), this was intentionally changed in Maven3. So, "assuming" you take GAV and turn it into path may not be true anymore, especially as Maven3.9+ and above will introduce ["split repository"](https://maven.apache.org/resolver/local-repository.html#split-local-repository) and other nice things. So, to me this for sure is not "install" (local repository involved), but you cannot support "deploy" to remote repository (due timestamped snapshot, Parser does not use maven metadata to figure out timestamped version), hence, this (to me) yields more like https://maven.apache.org/plugins/maven-stage-plugin/copy-mojo.html or alike, but here again "remote vs remote" repository is in play. So maybe a 3rd plugin that is dedicated (and uses same layout as Parser supports) is the proper solution, as Parser does not implements "local" nor "remote" repository in Maven3 sense. Is merely a hack. In short, your own mojo that implements same layout as is supported by Parser is the way to go. -- 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-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
