July 2013 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-144) Upgrade to Maven 3.1.0

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-144?page=com.atlassian.jira.plu... ] Andrew Rubinger edited comment on SHRINKRES-144 at 7/18/13 3:21 PM: -------------------------------------------------------------------- I have similar reservations about this issue as expressed in SHRINKRES-140. What specifically are the benefits from these upgrades that would be worth measuring against the risk introduced by bringing in new components? was (Author: alrubinger): I have similar reservations about this issues as expressed in SHRINKRES-140. What specifically are the benefits from these upgrades that would be worth measuring against the risk introduced by bringing in new components? > Upgrade to Maven 3.1.0 > ---------------------- > > Key: SHRINKRES-144 > URL: https://issues.jboss.org/browse/SHRINKRES-144 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Affects Versions: 2.0.0 > Reporter: Michal Matloka > Assignee: Michal Matloka > > Maven 3.1.0 was recently released. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-144) Upgrade to Maven 3.1.0

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-144?page=com.atlassian.jira.plu... ] Andrew Rubinger commented on SHRINKRES-144: ------------------------------------------- I have similar reservations about this issues as expressed in SHRINKRES-140. What specifically are the benefits from these upgrades that would be worth measuring against the risk introduced by bringing in new components? > Upgrade to Maven 3.1.0 > ---------------------- > > Key: SHRINKRES-144 > URL: https://issues.jboss.org/browse/SHRINKRES-144 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Affects Versions: 2.0.0 > Reporter: Michal Matloka > Assignee: Michal Matloka > > Maven 3.1.0 was recently released. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] Andrew Rubinger commented on SHRINKRES-140: ------------------------------------------- Appreciate the feedback from you both. [~mmatloka], do you mind if we follow [~gastaldi]'s suggestion to wait for a locked API from Aether? Right now I see latest available is aether-0.9.0.M2, and I think we'd be wise to wait until milestone releases are completed. > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Michal Matloka > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] George Gastaldi edited comment on SHRINKRES-140 at 7/18/13 11:43 AM: --------------------------------------------------------------------- I know that the Forge team has little or no influence under the development of ShrinkWrap Resolver, however I think that it may be better that this migration be postponed until the Eclipse Aether team releases a final version of their API, for the sake of stability of ShrinkWrap Resolver. was (Author: gastaldi): I know that the Forge team has little or no influence under the development of ShrinkWrap Resolver, however I thin that it may be better that this migration be postponed until the Eclipse Aether team releases a final version of their API, for the sake of stability of ShrinkWrap Resolver. > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Michal Matloka > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] George Gastaldi commented on SHRINKRES-140: ------------------------------------------- I know that the Forge team has little or no influence under the development of ShrinkWrap Resolver, however I thin that it may be better that this migration be postponed until the Eclipse Aether team releases a final version of their API, for the sake of stability of ShrinkWrap Resolver. > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Michal Matloka > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-140: ------------------------------------------ I am aware that this introduces risk. However e.g. Forge guys suggests it brings major performance improvement so they have resigned from concept of swr usage until it will migrate to eclipse one FORGE-803. > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Michal Matloka > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-140) Update Aether implementation to org.eclipse.aether one

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-140?page=com.atlassian.jira.plu... ] Andrew Rubinger commented on SHRINKRES-140: ------------------------------------------- What is the motivating force here? Are there specific updates we need to pull in? Keep in mind that the implementation we have is working and tested under the hood, and upgrades for upgrades sake can lead to incompatible runtime changes across point releases. We aim to be as stable as possible at this point, so what is the virtue of swapping the underlying implementation at this time and introducing risk? > Update Aether implementation to org.eclipse.aether one > ------------------------------------------------------ > > Key: SHRINKRES-140 > URL: https://issues.jboss.org/browse/SHRINKRES-140 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Components: impl-maven > Affects Versions: 2.0.0-beta-5 > Reporter: Karel Piwko > Assignee: Michal Matloka > > Aether is now a part of org.eclipse foundation. We should update to newer version when they release first stable version. > Update should not affect user at all, it should comprise of replacing imports with new ones. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-132) MavenImport should have different name

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-132?page=com.atlassian.jira.plu... ] Andrew Rubinger commented on SHRINKRES-132: ------------------------------------------- MavenBuilder isn't amazingly descriptive to me. POMBuilder? Else we can discuss other options and agree on a name. Yes, as Karel notes, we can do the name change going forward, but must maintain API forward-compatibility by providing a @Deprecated indirection to the new stuff. No client code (ie. existing tests) may change. S, ALR > MavenImport should have different name > -------------------------------------- > > Key: SHRINKRES-132 > URL: https://issues.jboss.org/browse/SHRINKRES-132 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0 > Reporter: Karel Piwko > Assignee: Michal Matloka > Priority: Minor > > MavenImporter is now able to build the project from pom.xml. This means that MavenImporter name is no longer valid, as it does not promote the fact that project will be build from scratch. > It might be MavenBuilder instead. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-132) MavenImport should have different name

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-132?page=com.atlassian.jira.plu... ] Michal Matloka updated SHRINKRES-132: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/shrinkwrap/resolver/pull/49 > MavenImport should have different name > -------------------------------------- > > Key: SHRINKRES-132 > URL: https://issues.jboss.org/browse/SHRINKRES-132 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Components: impl-maven > Affects Versions: 2.0.0 > Reporter: Karel Piwko > Assignee: Michal Matloka > Priority: Minor > > MavenImporter is now able to build the project from pom.xml. This means that MavenImporter name is no longer valid, as it does not promote the fact that project will be build from scratch. > It might be MavenBuilder instead. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-144) Upgrade to Maven 3.1.0

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-144?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-144: ------------------------------------------ Dependencies from org.apache.maven - maven-mode, maven-settings, maven-settings-builder etc which are currently from 3.0.5. Please look also on SHRINKRES-140 comment :) So this upgrade probably requieres also aether upgrade to eclipse one. > Upgrade to Maven 3.1.0 > ---------------------- > > Key: SHRINKRES-144 > URL: https://issues.jboss.org/browse/SHRINKRES-144 > Project: ShrinkWrap Resolvers > Issue Type: Component Upgrade > Affects Versions: 2.0.0 > Reporter: Michal Matloka > Assignee: Michal Matloka > > Maven 3.1.0 was recently released. -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues July 2013