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

javac supports relative source paths as arguments #2112

Closed

Conversation

djsweet
Copy link

@djsweet djsweet commented Mar 15, 2016

As specified in MIXED_PROJECTS.md, this is done with the intent to
support multi-stage source interleaving between Clojure and Java.

Also changed in this patchset:

  • @-arguments passed to javac are now expanded
  • compilation of Java sources can be avoided even when not stored
    in a directory format mirroring the package format

As specified in MIXED_PROJECTS.md, this is done with the intent to
support multi-stage source interleaving between Clojure and Java.

Also changed in this patchset:

- @-arguments passed to javac are now expanded
- compilation of Java sources can be avoided even when not stored
  in a directory format mirroring the package format
@hypirion
Copy link
Collaborator

Thanks for this! It's a big one, but it's on my prioritised list of things to take a look at.

@hypirion hypirion added this to the 2.6.2 milestone Apr 25, 2016
@hypirion hypirion mentioned this pull request Jul 28, 2016
@cprice404
Copy link
Collaborator

I'm planning on seeing if I can grok this today, since I know that @hypirion would like to see it included in 2.7.0. However it looks like it's going to need a rebase before it can be merged.

@@ -0,0 +1,214 @@
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC
LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you intend to commit this file? Seems like it's maybe not necessary inside one of the test projects, and might cause confusion as to which is the actual license file for leiningen itself?

@hypirion hypirion modified the milestones: 2.6.2, 2.7.1 Aug 30, 2016
@hypirion
Copy link
Collaborator

hypirion commented Jun 3, 2017

I think this is a bit too big to merge in for something that very few people seem to request, as well as no replies on the comments made by @cprice404. Happy to discuss this further if you still think it's worth to add in.

I'd guess if you really need this, you can use lein-shell as a workaround.

@hypirion hypirion closed this Jun 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants