March 2014 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-174) Missleading Exception message when sonatype and eclipse Aether found on classpath

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-174?page=com.atlassian.jira.plu... ] Aslak Knutsen updated SHRINKRES-174: ------------------------------------ Description: "Unable to boostrap Aether repository system. Make sure you're running Maven 3.1.0 or newer." The build is running Maven 3.1.0. https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... Dependency:tree https://gist.github.com/alesj/9891834#file-gistfile1-txt-L43 was: https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... Dependency:tree https://gist.github.com/alesj/9891834#file-gistfile1-txt-L43 > Missleading Exception message when sonatype and eclipse Aether found on classpath > --------------------------------------------------------------------------------- > > Key: SHRINKRES-174 > URL: https://issues.jboss.org/browse/SHRINKRES-174 > Project: ShrinkWrap Resolvers > Issue Type: Enhancement > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Aslak Knutsen > Assignee: Andrew Rubinger > > "Unable to boostrap Aether repository system. Make sure you're running Maven 3.1.0 or newer." > The build is running Maven 3.1.0. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... > Dependency:tree > https://gist.github.com/alesj/9891834#file-gistfile1-txt-L43 -- 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

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-174) Missleading Exception message when sonatype and eclipse Aether found on classpath

by Aslak Knutsen (JIRA)

Aslak Knutsen created SHRINKRES-174: --------------------------------------- Summary: Missleading Exception message when sonatype and eclipse Aether found on classpath Key: SHRINKRES-174 URL: https://issues.jboss.org/browse/SHRINKRES-174 Project: ShrinkWrap Resolvers Issue Type: Enhancement Components: impl-maven Affects Versions: 2.1.0 Reporter: Aslak Knutsen Assignee: Andrew Rubinger https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... Dependency:tree https://gist.github.com/alesj/9891834#file-gistfile1-txt-L43 -- 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

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-116) Gradle support

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-116?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-116: ------------------------------------------ https://issues.jboss.org/browse/SHRINKRES-124 was merged. Now I have a plan to allow to add single dependencies from the project instead of full build output import. > Gradle support > -------------- > > Key: SHRINKRES-116 > URL: https://issues.jboss.org/browse/SHRINKRES-116 > Project: ShrinkWrap Resolvers > Issue Type: Feature Request > Affects Versions: 2.0.0-beta-2 > Reporter: Michal Matloka > Assignee: Michal Matloka > > ShrinkWrap Resolver was designed to support multiple dependency management/build systems. It seems that there are already people using Gradle wanting to use ShrinkWrap. API seems much more friendly than Aether ;) and probably even supports build in 'build' feature. > http://forums.gradle.org/gradle/topics/dependency_resolution_with_gradle_... > http://gradle.1045684.n5.nabble.com/Gradle-support-for-Arquillian-maybe-a... > https://community.jboss.org/message/772433 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-124) Embedded Gradle Importer

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-124?page=com.atlassian.jira.plu... ] Karel Piwko edited comment on SHRINKRES-124 at 3/26/14 8:18 AM: ---------------------------------------------------------------- Pushed upstream in https://github.com/shrinkwrap/resolver/commit/48ce6d3fee59a83fe79f9dd8adb... and https://github.com/shrinkwrap/resolver/commit/81a33764f5522825017e8391084... Thanks Michal! was (Author: kpiwko): Pushed upstream in https://github.com/shrinkwrap/resolver/commits/master Thanks Michal! > Embedded Gradle Importer > ------------------------ > > Key: SHRINKRES-124 > URL: https://issues.jboss.org/browse/SHRINKRES-124 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-alpha-1 > > > Importer of build output embedding Gradle Tooling API. > Working prototype is ready, but needs some internal refactors. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-124) Embedded Gradle Importer

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-124?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-124. ----------------------------------- Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commits/master Thanks Michal! > Embedded Gradle Importer > ------------------------ > > Key: SHRINKRES-124 > URL: https://issues.jboss.org/browse/SHRINKRES-124 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-alpha-1 > > > Importer of build output embedding Gradle Tooling API. > Working prototype is ready, but needs some internal refactors. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-124) Embedded Gradle Importer

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-124?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-124: ---------------------------------- Fix Version/s: 2.2.0-alpha-1 > Embedded Gradle Importer > ------------------------ > > Key: SHRINKRES-124 > URL: https://issues.jboss.org/browse/SHRINKRES-124 > Project: ShrinkWrap Resolvers > Issue Type: Sub-task > Reporter: Michal Matloka > Assignee: Michal Matloka > Fix For: 2.2.0-alpha-1 > > > Importer of build output embedding Gradle Tooling API. > Working prototype is ready, but needs some internal refactors. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-479) Use default file ending for Archives with defined name

by Thorben Janssen (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-479?page=com.atlassian.jira.pl... ] Thorben Janssen edited comment on SHRINKWRAP-479 at 3/21/14 4:49 AM: --------------------------------------------------------------------- Yes, I saw this warning. >From my point of view, this warning shows that a default file ending would be useful. ShrinkWrap already detects a possible error. So why not provide a default behaviour that avoids it? >From my point of view, there should be no need to specify the obvious. It is better to provide a default behaviour that fits for most of the cases. And only if I want to do something special / deviate from the standard, I need to provide more information. Like it is the case with the Java EE annotations. The container provides the default behaviour without any additional information. But if I want to do something different, I can do this by providing more information. was (Author: th.janssen): Yes, I saw this warning. >From my point of view, this warning shows that a default file ending would be useful. ShrinkWrap already detects a possible error. So why not provide a default behaviour that avoids it? >From my point of view, there should be no need to specify the obvious. It is better to provide a default behaviour that fits for most of the cases. And only if I want to do something special / deviate from the standard, I need to provide more information. Like it is the case with the Java EE annotations. The container provides the default behaviour without any additional information. But if want to do something different, I can do this by providing more information. > Use default file ending for Archives with defined name > ------------------------------------------------------ > > Key: SHRINKWRAP-479 > URL: https://issues.jboss.org/browse/SHRINKWRAP-479 > Project: ShrinkWrap > Issue Type: Feature Request > Reporter: Thorben Janssen > > If the name of an ShrinkWrap archive is defined during creation, the name has to include the correct file ending to ensure correct deployment in the container, e.g.: > ShrinkWrap.create(EnterpriseArchive.class, "MyArchive.ear"); > In most of the cases the file ending is the default file ending of the specified archive type. In these cases there is no need to specify the obvious and it is just a source of error. > Suggested change: > - Archive implementation defines default file ending > - default file ending is added to the specified archive name by default (if it does not match the end of the specified name) > - add additional method to support archives with none standard file endings, e.g.: ShrinkWrap.create(Class<T> type, String archiveName, boolean useDefaultFileEnding) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-479) Use default file ending for Archives with defined name

by Thorben Janssen (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-479?page=com.atlassian.jira.pl... ] Thorben Janssen commented on SHRINKWRAP-479: -------------------------------------------- Yes, I saw this warning. >From my point of view, this warning shows that a default file ending would be useful. ShrinkWrap already detects a possible error. So why not provide a default behaviour that avoids it? >From my point of view, there should be no need to specify the obvious. It is better to provide a default behaviour that fits for most of the cases. And only if I want to do something special / deviate from the standard, I need to provide more information. Like it is the case with the Java EE annotations. The container provides the default behaviour without any additional information. But if want to do something different, I can do this by providing more information. > Use default file ending for Archives with defined name > ------------------------------------------------------ > > Key: SHRINKWRAP-479 > URL: https://issues.jboss.org/browse/SHRINKWRAP-479 > Project: ShrinkWrap > Issue Type: Feature Request > Reporter: Thorben Janssen > > If the name of an ShrinkWrap archive is defined during creation, the name has to include the correct file ending to ensure correct deployment in the container, e.g.: > ShrinkWrap.create(EnterpriseArchive.class, "MyArchive.ear"); > In most of the cases the file ending is the default file ending of the specified archive type. In these cases there is no need to specify the obvious and it is just a source of error. > Suggested change: > - Archive implementation defines default file ending > - default file ending is added to the specified archive name by default (if it does not match the end of the specified name) > - add additional method to support archives with none standard file endings, e.g.: ShrinkWrap.create(Class<T> type, String archiveName, boolean useDefaultFileEnding) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-479) Use default file ending for Archives with defined name

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-479?page=com.atlassian.jira.pl... ] Aslak Knutsen commented on SHRINKWRAP-479: ------------------------------------------ btw, did you not see this warning from Arquillian? https://github.com/arquillian/arquillian-core/blob/master/container/test-... > Use default file ending for Archives with defined name > ------------------------------------------------------ > > Key: SHRINKWRAP-479 > URL: https://issues.jboss.org/browse/SHRINKWRAP-479 > Project: ShrinkWrap > Issue Type: Feature Request > Reporter: Thorben Janssen > > If the name of an ShrinkWrap archive is defined during creation, the name has to include the correct file ending to ensure correct deployment in the container, e.g.: > ShrinkWrap.create(EnterpriseArchive.class, "MyArchive.ear"); > In most of the cases the file ending is the default file ending of the specified archive type. In these cases there is no need to specify the obvious and it is just a source of error. > Suggested change: > - Archive implementation defines default file ending > - default file ending is added to the specified archive name by default (if it does not match the end of the specified name) > - add additional method to support archives with none standard file endings, e.g.: ShrinkWrap.create(Class<T> type, String archiveName, boolean useDefaultFileEnding) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-479) Use default file ending for Archives with defined name

by Thorben Janssen (JIRA)

Thorben Janssen created SHRINKWRAP-479: ------------------------------------------ Summary: Use default file ending for Archives with defined name Key: SHRINKWRAP-479 URL: https://issues.jboss.org/browse/SHRINKWRAP-479 Project: ShrinkWrap Issue Type: Feature Request Reporter: Thorben Janssen If the name of an ShrinkWrap archive is defined during creation, the name has to include the correct file ending to ensure correct deployment in the container, e.g.: ShrinkWrap.create(EnterpriseArchive.class, "MyArchive.ear"); In most of the cases the file ending is the default file ending of the specified archive type. In these cases there is no need to specify the obvious and it is just a source of error. Suggested change: - Archive implementation defines default file ending - default file ending is added to the specified archive name by default (if it does not match the end of the specified name) - add additional method to support archives with none standard file endings, e.g.: ShrinkWrap.create(Class<T> type, String archiveName, boolean useDefaultFileEnding) -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues March 2014