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 Added info about incremental compiling, cleaning after switching branches #1475

merged 1 commit into from Feb 3, 2014


Copy link

@DavidEGrayson DavidEGrayson commented Feb 2, 2014

When I started developing with JRuby I didn't know how to do a quick incremental compilation. I ran "mvn package" after every change to any Java code. Thankfully, @mkristian told me how to do it in this comment:

#1470 (comment)

@mkristian also said it would be necessary to clean the build after switching branches (i.e. from master to jruby-1_7) and I have confirmed that it is necessary with an experiment, as discussed in issue #1470.

I think it would be helpful to other new JRuby developers if this information was in, so I made this pull request to add it. I really don't know much about Maven or Java compilation but hopefully I got this right.

This pull request goes to the jruby-1_7 branch, which I think is the right way to do it. It should be merged into master too so people can see it easily on github. Thanks!

…ntence about cleaning after switching branches.

This information is derived from a comment by mkristian:
#1470 (comment)
mkristian added a commit that referenced this pull request Feb 3, 2014 Added info about incremental compiling, cleaning after switching branches

[skip ci]
@mkristian mkristian merged commit 05a15dc into jruby:jruby-1_7 Feb 3, 2014
1 check failed
1 check failed
default The Travis CI build failed
Copy link

@mkristian mkristian commented Feb 3, 2014

merged to master as well - thanx

@enebo enebo added this to the JRuby 1.7.11 milestone Feb 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants