-
Notifications
You must be signed in to change notification settings - Fork 14
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
de.saumya.mojo group ID is hardcoded most places #37
Milestone
Comments
headius
added a commit
to headius/jruby
that referenced
this issue
Aug 3, 2023
This update is necessary to get JRuby 9.4.3.0 running throughout the JRuby/Maven stack, which is necessary to move to the new mavengems. See jruby/jruby-maven-plugins#126 See jruby/mavengem#9 There is also a change to replace the use of `jruby_plugin` in test/pom.rb with a normal `plugin` DSL call, due to the former hardcoding an old package for the jruby-maven-plugins. See jruby/maven-tools#37
headius
added a commit
to headius/jruby
that referenced
this issue
Aug 3, 2023
This update is necessary to get JRuby 9.4.3.0 running throughout the JRuby/Maven stack, which is necessary to move to the new mavengems. See jruby/jruby-maven-plugins#126 See jruby/mavengem#9 There are also changes to replace the use of `jruby_plugin` in several poms with a normal `plugin` DSL call, due to the former hardcoding an old package for the jruby-maven-plugins. See jruby/maven-tools#37
headius
added a commit
to headius/polyglot-maven
that referenced
this issue
Aug 3, 2023
This is part of work to update the entire JRuby/Maven stack, in order to update the version of JRuby used and to address API deprecations at rubygems.org. This PR updates JRuby to latest (9.4.3.0) and moves all plugins to their new org.jruby.maven group ID with latest versions. Part of the fix for jruby/maven-tools#37. We will need to coordinate getting this released along with the maven plugins in the very near term. Because of the rubygems.org API being shut down next week (the 8th), we are under the gun. See jruby/mavengem#9, jruby/jruby-maven-plugins#126, jruby/maven-tools#38 and jruby/jruby#7872.
headius
added a commit
to headius/polyglot-maven
that referenced
this issue
Aug 4, 2023
This is part of work to update the entire JRuby/Maven stack, in order to update the version of JRuby used and to address API deprecations at rubygems.org. This PR updates JRuby to latest (9.4.3.0) and moves all plugins to their new org.jruby.maven group ID with latest versions. Part of the fix for jruby/maven-tools#37. We will need to coordinate getting this released along with the maven plugins in the very near term. Because of the rubygems.org API being shut down next week (the 8th), we are under the gun. See jruby/mavengem#9, jruby/jruby-maven-plugins#126, jruby/maven-tools#38 and jruby/jruby#7872.
headius
added a commit
to headius/polyglot-maven
that referenced
this issue
Aug 4, 2023
This is part of work to update the entire JRuby/Maven stack, in order to update the version of JRuby used and to address API deprecations at rubygems.org. This PR updates JRuby to latest (9.4.3.0) and moves all plugins to their new org.jruby.maven group ID with latest versions. The maven-tools gem is updated to 1.2. Part of the fix for jruby/maven-tools#37. We will need to coordinate getting this released along with the maven plugins in the very near term. Because of the rubygems.org API being shut down next week (the 8th), we are under the gun. See jruby/mavengem#9, jruby/jruby-maven-plugins#126, jruby/maven-tools#38 and jruby/jruby#7872.
headius
added a commit
to headius/jruby
that referenced
this issue
Aug 4, 2023
This update is necessary to get JRuby 9.4.3.0 running throughout the JRuby/Maven stack, which is necessary to move to the new mavengems. See jruby/jruby-maven-plugins#126 See jruby/mavengem#9 There are also changes to replace the use of `jruby_plugin` in several poms with a normal `plugin` DSL call, due to the former hardcoding an old package for the jruby-maven-plugins. See jruby/maven-tools#37
headius
added a commit
to headius/jruby
that referenced
this issue
Aug 9, 2023
This update is necessary to get JRuby 9.4.3.0 running throughout the JRuby/Maven stack, which is necessary to move to the new mavengems. See jruby/jruby-maven-plugins#126 See jruby/mavengem#9 There are also changes to replace the use of `jruby_plugin` in several poms with a normal `plugin` DSL call, due to the former hardcoding an old package for the jruby-maven-plugins. See jruby/maven-tools#37
cstamas
added a commit
to takari/polyglot-maven
that referenced
this issue
Aug 25, 2023
This is part of work to update the entire JRuby/Maven stack, in order to update the version of JRuby used and to address API deprecations at rubygems.org. This PR updates JRuby to latest (9.4.3.0) and moves all plugins to their new org.jruby.maven group ID with latest versions. Part of the fix for jruby/maven-tools#37. (incorrectly tagged as #37 here before) We will need to coordinate getting this released along with the maven plugins in the very near term. Because of the rubygems.org API being shut down next week (the 8th), we are under the gun. See jruby/mavengem#9, jruby/jruby-maven-plugins#126, jruby/maven-tools#38 and jruby/jruby#7872.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently working on updating the JRuby/Maven stack, and ran into an issue with the
jruby_plugin
DSL because it hardcodes the group ID for JRuby/Maven plugins as "de.saumya.mojo".As part of work on jruby/mavengem#9 and jruby/jruby-maven-plugins#126 I have moved these projects under the "org.jruby.maven" group ID. When attempting to build JRuby after that move (working against snapshots of jruby-maven-plugins and mavengem) the build for JRuby's test dir failed to resolve de.saumya.mojo:gem-maven-plugin before the build could even run.
The issue appears to be twofold:
jruby_plugin
DSL hardcodes "de.saumya.mojo" as the group ID.The maven-tools will need to be updated to support both group IDs, most likely, and we'll need to investigate if and how we can isolate the execution of the pom.rb from the use of jruby-maven-plugins during the build.
For now I will be replacing the one use of
jruby_plugin
with a normalplugin
call.The text was updated successfully, but these errors were encountered: