rJava inside packrat
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
rJava inside packrat has wierd behaviour.
If I launch rJava from a packrat repo, in the first run in throws exception, but on the second run works perfectly.
Do you have any ideas how that can happen?
> library(rJava)
> .jinit()
Exception in thread "Rengine Thread" Error in .jinit() : unable to find the RJavaTools class
> .jinit()
[1] 0
> sessionInfo()
R version 3.1.1 (2014-07-10)
Platform: x86_64-pc-linux-gnu (64-bit)
locale:
[1] LC_CTYPE=en_IE.UTF-8 LC_NUMERIC=C
[3] LC_TIME=en_IE.UTF-8 LC_COLLATE=en_IE.UTF-8
[5] LC_MONETARY=en_IE.UTF-8 LC_MESSAGES=en_IE.UTF-8
[7] LC_PAPER=en_IE.UTF-8 LC_NAME=en_IE.UTF-8
[9] LC_ADDRESS=en_IE.UTF-8 LC_TELEPHONE=en_IE.UTF-8
[11] LC_MEASUREMENT=en_IE.UTF-8 LC_IDENTIFICATION=en_IE.UTF-8
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] rJava_0.9-8 rj_2.0.3-2
loaded via a namespace (and not attached):
[1] packrat_0.4.6-1 rj.gd_1.1.3-1 tools_3.1.1
Running it installed in /usr/local indicates no issue
I have created issue in rJava repo
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported sequence in a packrat repository: library(rJava), then .jinit() twice, using the supplied R and package versions. Compare this with the installation under /usr/local and review the linked rJava issue; done means the first-run failure is explained and a reproducible resolution or clear upstream boundary is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100