[DOCU-206] Add JDK Version Troubleshooting Created: 03/Sep/11 Updated: 30/Dec/14 Resolved: 30/Dec/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Suzanne Deprez | Assignee: | Suzanne Deprez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
A troubleshooting item should be added to the Initialize Maven page stating that if the process that occurs when command is entered stops then the Java version should be verified to be JDK 1.6 by entering the version command for Maven (mvn --version). |
| Comments |
| Comment by Magnolia International [ 06/Sep/11 ] |
|
Seems pretty unlikely to be the direct reason you had issues is the jdk version. But it's possibly a side-effect of how it gets installed (on windows I assume) Just for the record - for when we try to isolate the issue - the problem was that the mvn nexus-maven-plugin:settings-download command somehow "blocked" while downloading artifacts (and/or the plugin itself) |
| Comment by Ruth Stocks [ 30/Dec/14 ] |
|
Documented at https://documentation.magnolia-cms.com/display/DOCS/Certified+stack#Certifiedstack-Java |