[forge-issues] [JBoss JIRA] (FORGE-787) Forge update is not working correctly in Windows

[ https://issues.jboss.org/browse/FORGE-787?page=com.atlassian.jira.plugin.... ] Michal Matloka commented on FORGE-787: -------------------------------------- 1. Maybe jboss repositories could be used as default for forge update? Otherwise after release users without jboss ropositories will see what I've seen yesterday and in pesimistic situation they might get discouraged. Or on release page you'd have to add a small note concerning repositories. 2. Forge update still gives "Forge is up to date". But reason appears to be simple. I was trying also to getn forge 1.2.1 as dependency to test project. mvn clean install displays "xxx was cached in the local repository, resolution will not be reattempted until the update interval of xxx has elapsed or updates are forced". So Aether also does not find 1.2.1. After deleting forge folders from local repository, the version 1.2.1 was found by forge. When using mvn application -U parameter is used to force update. When using aether the following policy can be set: {noformat} session.setUpdatePolicy(RepositoryPolicy.UPDATE_POLICY_ALWAYS); {noformat} Question is if it should be used for all resolved artifacts or only for forge update or we assume normal user won't have this type of situation. -- 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