Skip to content
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

Compiling from source at 1.7.9 fails due to unsatisfied maven dependencies #1363

Closed
BanzaiMan opened this issue Dec 26, 2013 · 10 comments
Closed
Assignees
Milestone

Comments

@BanzaiMan
Copy link
Member

@BanzaiMan BanzaiMan commented Dec 26, 2013

To reproduce:

  1. mv ~/.m2 ~/m2
  2. git clone https://github.com/jruby/jruby.git
  3. cd jruby; git checkout 1.7.9
  4. mvn

This resolves dependency on joni at 2.1.1-SNAPSHOT for some reason, but it is not found anywhere.

@BanzaiMan
Copy link
Member Author

@BanzaiMan BanzaiMan commented Dec 26, 2013

@nirvdrum
Copy link
Contributor

@nirvdrum nirvdrum commented Dec 26, 2013

I believe this was already reported to @enebo and he and @mkristian came up with a way to prevent it in the future.

@BanzaiMan
Copy link
Member Author

@BanzaiMan BanzaiMan commented Dec 26, 2013

@nirvdrum Does "in the future" mean that it is impossible to fix this for 1.7.9?

@nirvdrum
Copy link
Contributor

@nirvdrum nirvdrum commented Dec 26, 2013

I believe "in the future" means 1.7.10, since 1.7.9 was already tagged and released. See #1323. But I certainly don't want to speak for others.

@mkristian
Copy link
Member

@mkristian mkristian commented Dec 26, 2013

the tagged version has this SNAPSHOT dependencies. well if you want to
branch off from that tag then you can just remove the -SNAPSHOT in
./core/pom.xml

as for the maven artifact on maven central that thing is broken and there
are few possible workarounds but better wait for jruby-1.7.10 unless there
is dire need for 1.7.9

@BanzaiMan
Copy link
Member Author

@BanzaiMan BanzaiMan commented Dec 26, 2013

Well, it just means that Travis can't use 1.7.9 in the 1.8 mode (which currently requires compilation from source) without someone flexing some muscles.

If 1.7.10 is slated for release reasonably soon, I guess we can wait.

@mpapis
Copy link
Contributor

@mpapis mpapis commented Dec 26, 2013

I think I can add patch for that I rvm.
On Dec 26, 2013 7:20 PM, "Christian Meier" notifications@github.com wrote:

the tagged version has this SNAPSHOT dependencies. well if you want to
branch off from that tag then you can just remove the -SNAPSHOT in
./core/pom.xml

as for the maven artifact on maven central that thing is broken and there
are few possible workarounds but better wait for jruby-1.7.10 unless there
is dire need for 1.7.9


Reply to this email directly or view it on GitHubhttps://github.com//issues/1363#issuecomment-31230087
.

@mkristian
Copy link
Member

@mkristian mkristian commented Dec 26, 2013

@mpapis it is really the core/pom.xml with that -SNAPSHOT @enebo has released joni-2.1.1 already and it is on maven central

@BanzaiMan
Copy link
Member Author

@BanzaiMan BanzaiMan commented Dec 26, 2013

All right, then. I'll blame @enebo and close this ticket. There is nothing further to do.

@enebo
Copy link
Member

@enebo enebo commented Dec 28, 2013

Yeah this was definitely my fault (although I 100% did try and look for
SNAPSHOTS -- I just failed). Deep down inside though I blame Maven :)

-Tom

On Thu, Dec 26, 2013 at 4:12 PM, Hiro Asari notifications@github.comwrote:

All right, then. I'll blame @enebo https://github.com/enebo and close
this ticket. There is nothing further to do.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1363#issuecomment-31238073
.

blog: http://blog.enebo.com twitter: tom_enebo
mail: tom.enebo@gmail.com

@enebo enebo modified the milestones: JRuby 1.7.10, JRuby 1.7.11 Feb 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants