Support classpath configuration via .classpath files.

[daw42]

This PR allows for configuration of the classpath on a per-project basis via .cson files. The user can place a .linter-javac.cson file within their project and the linter will use the classpath that is provided within the file.

Additionally, it will execute the javac command in the directory of the .cson file so it is possible to use paths that are relative to the .cson configuration file.

• README.md updated with documentation
• Requires season for CSON parsing

This makes it much more convenient to configure different classpaths for each project.

[keplersj]

Linter clang used to do something similar and it was not helpful in the
long run.

I would much prefer if a .classpath file like that used by linter-scalac
could be used by this.

On Thu, Aug 6, 2015, 7:37 PM daw42 notifications@github.com wrote:

This PR allows for configuration of the classpath on a per-project basis
via .cson files. The user can place a .linter-javac.cson file within
their project and the linter will use the classpath that is provided within
the file.

Additionally, it will execute the javac command in the directory of the
.cson file so it is possible to use paths that are relative to the .cson
configuration file.

• README.md updated with documentation
• Requires season for CSON parsing

This makes it much more convenient to configure different classpaths for

each project.

You can view, comment on, or merge this pull request online at:

#30
Commit Summary

• Support classpath configuration via cson files.

File Changes

• M README.md
  https://github.com/AtomLinter/linter-javac/pull/30/files#diff-0 (24)
• M lib/init.coffee
  https://github.com/AtomLinter/linter-javac/pull/30/files#diff-1 (40)
• M package.json
  https://github.com/AtomLinter/linter-javac/pull/30/files#diff-2 (3)

Patch Links:

• https://github.com/AtomLinter/linter-javac/pull/30.patch
• https://github.com/AtomLinter/linter-javac/pull/30.diff

—
Reply to this email directly or view it on GitHub
#30.

[daw42]

Hi @k2b6s9j, I looked at the linter-scalac repo, and it looks very similar to what this PR does. The only significant difference is that I'm using CSON, and they use a flat file. The advantage of CSON is that we can expand to support more configuration in the future if necessary.

[keplersj]

I understand that. But the problem is that this file only supports the
Scala Linter for Atom. We should not be trying to create a new standard
where there is already one, especially where the JVM is concerned.

On Fri, Aug 7, 2015, 2:29 PM daw42 notifications@github.com wrote:

Hi @k2b6s9j https://github.com/k2b6s9j, I looked at the linter-scalac
repo, and it looks very similar to what this PR does. The only
significant difference is that I'm using CSON, and they use a flat file.
The advantage of CSON is that we can expand to support more configuration
in the future if necessary.

—
Reply to this email directly or view it on GitHub
#30 (comment)
.

[daw42]

I understand that. But the problem is that this file only supports the
Scala Linter for Atom.

Did you mean the javac linter?

Ok, I'll update to use .classpath

[keplersj]

Sorry. Yes I meant that. Thank you.

On Fri, Aug 7, 2015, 2:44 PM daw42 notifications@github.com wrote:

I understand that. But the problem is that this file only supports the
Scala Linter for Atom.

Did you mean the javac linter?

Ok, I'll update to use .classpath

—
Reply to this email directly or view it on GitHub
#30 (comment)
.

[daw42]

Updated, thanks.

[daw42]

Do you need anything else in order to merge this?

Thanks.

[steelbrain]

@k2b6s9j has been busy throughout the weekend I think. He'll have a look into this soon, hopefully.

[keplersj]

Awesome! This will be in the next minor update!