[
https://issues.jboss.org/browse/FORGE-787?page=com.atlassian.jira.plugin....
]
Michal Matloka commented on FORGE-787:
--------------------------------------
1. ForgeEnvironmentImpl.getForgeHome uses system properties (System.getProperty method)
which finds nothing. Proper FORGE_HOME value is contained in environmental variables
(System.getenv())
2. ForgeEnvironmentImpl.getRuntimeVersion also returns null, when forge version property
should be set?
3. Generally ShellImpl constants contains interesting values e.g
{noformat}
FORGE_CONFIG_DIR=C:\Users\mich/.forge/
CWD=C:\/Users/mich/AppData/Local/Temp/abstractshelltest8530879172079707029.tmp/test
{noformat}
I don't know if this brings any problems.
4. When solving 1. and hardcoding 2. the ForgePlugin.getLatestAvailableDistribution does
not resolve 1.2.1 version. In maven central currently newest is 1.2.0. I don't know if
it should look for it in central or jboss repositories.
Forge update is not working correctly in Windows
------------------------------------------------
Key: FORGE-787
URL:
https://issues.jboss.org/browse/FORGE-787
Project: Forge
Issue Type: Bug
Affects Versions: 1.2.0.Final, 1.2.1.Final
Environment: Windows 8 64bit, JDK 1.7.0_13;Windows 7 64bit, Oracle JDK 1.7.0_13
Reporter: George Gastaldi
Assignee: Michal Matloka
Fix For: 1.2.2.Final
Running
{code}
forge update
{code}
in Forge 1.2.0.Final says that Forge is already up-to-date, instead of upgrading to
1.2.1.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira