Fixing build problem introduced by removing encryption jars #595
Conversation
…jars When merging changes to the build.xml, I accidentally included some early experimentation that didn't get rolled back. Fixing the issue by reverting the compile-jruby target to its original form.
|
Hi. Since I reverted 5c5f203, I can't merge this PR as is. Could you fix the pull request? |
ghost
assigned 
|
Sorry, I'm a bit new to github, and I'm still figuring out how all the different pieces fit together. I merged everything from trunk back into my forked copy, synced that with my local copy, reintroduced my changes, and committed everything, which seems to have updated the pull request automatically. I did pick up a change I'm not sure about... It looks like a jzlib specification went from 1.1.2 to 1.1.0... I think that's something I just picked up when merging in jruby/master. At any rate, all targets are building as expected in my workspace now, and everything is synced up, so I think you can pull. |
|
We're almost there. Could you squash these commits into one, so that I can test it? |
|
Maybe almost :-) I've spent about an hour trying to figure out how to use git rebase to no avail. Only three of the four commits show up in the list, and they are interlaced with dozens of other commit messages. I've tried every combination of squash and pick that I can think of that seems reasonable (and a few that don't) and nothing ever seems to happen. Can you help me understand the process of merging commits? I've read the git help manual for rebase and probably a dozen blog posts on it at this point, and still don't quite understand what's going on. |
|
Sigh. I just made it worse. I really don't know what to do at this point. I'll try creating a new branch from HEAD and merging my changes in there and then giving you a pull request from that branch? |
|
@mamccr That build error on Travis seems to be persistent before your pull request, so I won't worry about it too much. I'll study the pull request soon, and get back to you. Thanks. |
|
Ok, sorry. I thought using github was going to be awesome, but I could not be more confused with what is happening. The handful of changes I want to convey are really quite simple. If there's some way I can start over and clear up all the noise, I'm happy to try. Just let me know what you need. |
This reverts commit e0a7301.
|
What's the status here? Perhaps you can just re-branch, from our master, apply all your changes there at once, and resubmit the PR? I'm going to have a look at your master now to see how it looks. |
|
Merged in f706048. I added an extra commit that properly formatted the excludes in antlib/dist.xml and confirmed that with the property set jar-complete produces a jar with no (j)openssl bits, no BouncyCastle, and no krypt. |
|
Awesome! Thanks so much, and sorry again for all the hassle. It's clearly time for me to read a book on git. |
...s
When merging changes to the build.xml, I accidentally included some
early experimentation that didn't get rolled back. Fixing the issue by
reverting the compile-jruby target to its original form.
Please note that the original changes to antlib/dist.xml should accompany this. I can't quite figure out what Github is doing here, but my intention is for the diff shown here to be applied to the code in my original pull request yesterday.
Very sorry for the churn!