February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-788) Add support for Updating Maven Pom Dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-788?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-788: ---------------------------------- Status: Closed (was: Pull Request Sent) Assignee: George Gastaldi Resolution: Done Thanks [~aslak] ! > Add support for Updating Maven Pom Dependencies > ----------------------------------------------- > > Key: FORGE-788 > URL: https://issues.jboss.org/browse/FORGE-788 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 1.2.2.Final > > > The command will run trough current pom and all children to check if there are newer version of the defined artifacts available in the Maven repositories. > If one is found, the user will be prompted to see if he wants to update, ignore or see a complete list of available newer versions. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-788) Add support for Updating Maven Pom Dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-788?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-788: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/287 > Add support for Updating Maven Pom Dependencies > ----------------------------------------------- > > Key: FORGE-788 > URL: https://issues.jboss.org/browse/FORGE-788 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.1.Final > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > The command will run trough current pom and all children to check if there are > newer version of the defined artifacts available in the Maven repositories. > If one is found, the user will be prompted to see if he wants to update, > ignore or see a complete list of available newer versions. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-788) Add support for Updating Maven Pom Dependencies

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-788?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-788: ---------------------------------- Description: The command will run trough current pom and all children to check if there are newer version of the defined artifacts available in the Maven repositories. If one is found, the user will be prompted to see if he wants to update, ignore or see a complete list of available newer versions. was: The command will run trough current pom and all children to check if there are newer version of the defined artifacts available in the Maven repositories. If one is found, the user will be prompted to see if he wants to update, ignore or see a complete list of available newer versions. > Add support for Updating Maven Pom Dependencies > ----------------------------------------------- > > Key: FORGE-788 > URL: https://issues.jboss.org/browse/FORGE-788 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.1.Final > Reporter: George Gastaldi > Fix For: 1.2.2.Final > > > The command will run trough current pom and all children to check if there are newer version of the defined artifacts available in the Maven repositories. > If one is found, the user will be prompted to see if he wants to update, ignore or see a complete list of available newer versions. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-788) Add support for Updating Maven Pom Dependencies

by George Gastaldi (JIRA)

George Gastaldi created FORGE-788: ------------------------------------- Summary: Add support for Updating Maven Pom Dependencies Key: FORGE-788 URL: https://issues.jboss.org/browse/FORGE-788 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.2.1.Final Reporter: George Gastaldi Fix For: 1.2.2.Final The command will run trough current pom and all children to check if there are newer version of the defined artifacts available in the Maven repositories. If one is found, the user will be prompted to see if he wants to update, ignore or see a complete list of available newer versions. -- 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

13 years, 2 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ 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. > 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

13 years, 2 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/FORGE-787?page=com.atlassian.jira.plugin.... ] Michal Matloka reopened FORGE-787: ---------------------------------- problem still occurs for me > 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

13 years, 2 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-787?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-787. --------------------------------- Resolution: Done Forge will look for the current configured repositories. It takes some time (up to 24h) to synchronize the artifacts with the central repository. In a clean installation of forge (without having JBoss repositories configured in settings.xml), the update will only work if the artifact is already published in central > 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

13 years, 2 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ 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

13 years, 3 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/FORGE-787?page=com.atlassian.jira.plugin.... ] Michal Matloka updated FORGE-787: --------------------------------- Environment: Windows 8 64bit, JDK 1.7.0_13;Windows 7 64bit, Oracle JDK 1.7.0_13 (was: Windows 8 64bit, JDK 1.7.0_13) > 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

13 years, 3 months

1
0
0 / 0

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/FORGE-787?page=com.atlassian.jira.plugin.... ] Michal Matloka reassigned FORGE-787: ------------------------------------ Assignee: Michal Matloka > 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 > 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013