April 2014 - shrinkwrap-issues - Jboss List Archives

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

by Michal Matloka (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-124?page=com.atlassian.jira.plu... ] Michal Matloka commented on SHRINKRES-124: ------------------------------------------ I have pushed updated sample https://github.com/mmatloka/arquillian-gradle-sample/ to use the SWR 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-178) Class path resolution should omit directories is does not understand

by Karel Piwko (JIRA)

Karel Piwko created SHRINKRES-178: ------------------------------------- Summary: Class path resolution should omit directories is does not understand Key: SHRINKRES-178 URL: https://issues.jboss.org/browse/SHRINKRES-178 Project: ShrinkWrap Resolvers Issue Type: Bug Components: impl-maven Affects Versions: 2.1.0 Reporter: Karel Piwko Assignee: Karel Piwko Fix For: 2.2.0-alpha-2 During classpath resolution, there might be directory entries added manually to the classpath. These entries does not follow target/*.jar format, so they should be ignored while parsed. Currently, parsing fails with following exception: {code} Caused by: java.lang.NullPointerException at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.createPomFileInfo(ClasspathWorkspaceReader.java:273) at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.getPomFileInfo(ClasspathWorkspaceReader.java:266) at org.jboss.shrinkwrap.resolver.impl.maven.aether.ClasspathWorkspaceReader.findArtifact(ClasspathWorkspaceReader.java:172) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:342) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:262) at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:239) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:320) at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:461) at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:261) at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:342) at org.jboss.shrinkwrap.resolver.impl.maven.bootstrap.MavenRepositorySystem.resolveDependencies(MavenRepositorySystem.java:138) at org.jboss.shrinkwrap.resolver.impl.maven.MavenWorkingSessionImpl.resolveDependencies(MavenWorkingSessionImpl.java:266) at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.using(MavenStrategyStageBaseImpl.java:71) at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:53) at org.jboss.shrinkwrap.resolver.impl.maven.MavenStrategyStageBaseImpl.withTransitivity(MavenStrategyStageBaseImpl.java:40) at org.jboss.soa.qa.operation.selector.SimpleHttpOperationSelectorTest.createDeployment(SimpleHttpOperationSelectorTest.java:70) ... 61 more {code} -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-177. ----------------------------------- Fix Version/s: 2.2.0-alpha-2 Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/7b4a1157683edf3a1ff99140a84... Thanks! > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > Fix For: 2.2.0-alpha-2 > > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-155) Missing methods in generated common parents

by Ralf Battenfeld (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-155?page=com.atlassian.jira.pl... ] Ralf Battenfeld commented on SHRINKDESC-155: -------------------------------------------- Hi George If you have time, can you double check this: https://github.com/rbattenfeld/descriptors/tree/SHRINKDESC-155 Let me know if that is good enough. Regards, Ralf > Missing methods in generated common parents > ------------------------------------------- > > Key: SHRINKDESC-155 > URL: https://issues.jboss.org/browse/SHRINKDESC-155 > Project: ShrinkWrap Descriptors > Issue Type: Feature Request > Components: api-javaee > Affects Versions: 2.0.0-alpha-6 > Reporter: George Gastaldi > Assignee: Ralf Battenfeld > > Some common parents generated from SHRINKDESC-151 do not have all the required methods declared in the common interface. > For example: > - JavaeeServletMappingCommonType > -- see https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > - WebAppCommonDescriptor > -- see https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > Other parent interfaces might be missing methods as well, they should be reviewed and have the common methods created. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Tadeas Kriz (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Work on SHRINKRES-177 started by Tadeas Kriz. > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SHRINKRES-177) Version range resolution fails if metadata file doesn't exist in local repository

by Tadeas Kriz (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-177?page=com.atlassian.jira.plu... ] Tadeas Kriz reassigned SHRINKRES-177: ------------------------------------- Assignee: Tadeas Kriz (was: Andrew Rubinger) > Version range resolution fails if metadata file doesn't exist in local repository > --------------------------------------------------------------------------------- > > Key: SHRINKRES-177 > URL: https://issues.jboss.org/browse/SHRINKRES-177 > Project: ShrinkWrap Resolvers > Issue Type: Bug > Components: impl-maven > Affects Versions: 2.1.0 > Reporter: Tadeas Kriz > Assignee: Tadeas Kriz > > When version range resolution in Aether can't find local metadata file, it adds an exception into exception list. Shrinkwrap-Resolver then checks if the list is empty and if it's not, it fails. And that's why the resolution doesn't work in this case. > https://github.com/shrinkwrap/resolver/blob/master/impl-maven/src/main/ja... -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-154) ShrinkWrap Descriptors BOM should contain ShrinkWrap Descriptors DepChains

by Antonin Stefanutti (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-154?page=com.atlassian.jira.pl... ] Antonin Stefanutti commented on SHRINKDESC-154: ----------------------------------------------- The {{[shrinkwrap-descriptors-bom:2.0.0-alpha-6|http://search.maven.org/#artifactdetails%7Corg.jboss.shrinkwrap.descriptors%7Cshrinkwrap-descriptors-bom%7C2.0.0-alpha-6%7Cpom]}} artifact deployed in Maven central does not contain the fix. It seems that the pull request hasn't been merged in the {{2.0.0-X}} branch prior to the {{2.0.0-alpha-6}} release: [https://github.com/shrinkwrap/descriptors/blob/2.0.0-X/bom/pom.xml]. > ShrinkWrap Descriptors BOM should contain ShrinkWrap Descriptors DepChains > --------------------------------------------------------------------------- > > Key: SHRINKDESC-154 > URL: https://issues.jboss.org/browse/SHRINKDESC-154 > Project: ShrinkWrap Descriptors > Issue Type: Bug > Affects Versions: 2.0.0-alpha-5 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.0.0-alpha-6 > > -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SHRINKDESC-155) Missing methods in generated common parents

by Ralf Battenfeld (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-155?page=com.atlassian.jira.pl... ] Ralf Battenfeld commented on SHRINKDESC-155: -------------------------------------------- Right, this was in but then accidentally removed. I have to check why... Sorry for this. I will work on this. > Missing methods in generated common parents > ------------------------------------------- > > Key: SHRINKDESC-155 > URL: https://issues.jboss.org/browse/SHRINKDESC-155 > Project: ShrinkWrap Descriptors > Issue Type: Feature Request > Components: api-javaee > Affects Versions: 2.0.0-alpha-6 > Reporter: George Gastaldi > Assignee: Ralf Battenfeld > > Some common parents generated from SHRINKDESC-151 do not have all the required methods declared in the common interface. > For example: > - JavaeeServletMappingCommonType > -- see https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > - WebAppCommonDescriptor > -- see https://github.com/forge/javaee-descriptors/blob/master/api/src/main/java... > Other parent interfaces might be missing methods as well, they should be reviewed and have the common methods created. -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-453) Paths in webarchives are not calculated correctly

by Pawan Dubey (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-453?page=com.atlassian.jira.pl... ] Pawan Dubey commented on SHRINKWRAP-453: ---------------------------------------- [~michael.vorburger] Thanks for posting it here. [~alrubinger] knows about this though. I have to submit a patch for this. > Paths in webarchives are not calculated correctly > ------------------------------------------------- > > Key: SHRINKWRAP-453 > URL: https://issues.jboss.org/browse/SHRINKWRAP-453 > Project: ShrinkWrap > Issue Type: Bug > Components: api > Affects Versions: 1.1.2 > Environment: Win7x64, JDK1.7.0_17x32, JBOSS 7.1.3.Final, Arquillian 1.0.3Final, JUnit 4.11 > Reporter: Stefan Hösel > > When creating a WebArchive via ShrinkWrap from a directory that is an exploded war file, paths inside this archive (generated with "arquillian.xml/arquillian/engine/property[deploymentExportPath]->target/deployments") generated invalid in some cases. > When investigating the sources I found "org.jboss.shrinkwrap.impl.base.importer.ExplodedImporterImpl.calculatePath(File root, File child)" uses "String.replaceFirst" to replace the occurance of rootPath in childPath to create a local war file path. My path of the directory that needs compression contains *brackets*, which (as well as other path elements, e.g. ".") are interpreted as regular expression tokens and therefore don't match. > The resulting archive can not be delpoyed in AS and tests can not be performed automatically. > The code to create the WebArchive looks like this: > {{ShrinkWrap._create_(WebArchive.{color:gray}*class*{color}, resultingWarFileNameAsString)}} > {{.as(ExplodedImporter.{color:gray}*class*{color}).importDirectory(absolutePathToExplodedWarDirectoryAsFile)}} > {{.as(WebArchive.{color:gray}*class*{color});}} -- 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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SHRINKWRAP-453) Paths in webarchives are not calculated correctly

by Michael Vorburger (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-453?page=com.atlassian.jira.pl... ] Michael Vorburger commented on SHRINKWRAP-453: ---------------------------------------------- https://github.com/shrinkwrap/shrinkwrap/pull/86 ? > Paths in webarchives are not calculated correctly > ------------------------------------------------- > > Key: SHRINKWRAP-453 > URL: https://issues.jboss.org/browse/SHRINKWRAP-453 > Project: ShrinkWrap > Issue Type: Bug > Components: api > Affects Versions: 1.1.2 > Environment: Win7x64, JDK1.7.0_17x32, JBOSS 7.1.3.Final, Arquillian 1.0.3Final, JUnit 4.11 > Reporter: Stefan Hösel > > When creating a WebArchive via ShrinkWrap from a directory that is an exploded war file, paths inside this archive (generated with "arquillian.xml/arquillian/engine/property[deploymentExportPath]->target/deployments") generated invalid in some cases. > When investigating the sources I found "org.jboss.shrinkwrap.impl.base.importer.ExplodedImporterImpl.calculatePath(File root, File child)" uses "String.replaceFirst" to replace the occurance of rootPath in childPath to create a local war file path. My path of the directory that needs compression contains *brackets*, which (as well as other path elements, e.g. ".") are interpreted as regular expression tokens and therefore don't match. > The resulting archive can not be delpoyed in AS and tests can not be performed automatically. > The code to create the WebArchive looks like this: > {{ShrinkWrap._create_(WebArchive.{color:gray}*class*{color}, resultingWarFileNameAsString)}} > {{.as(ExplodedImporter.{color:gray}*class*{color}).importDirectory(absolutePathToExplodedWarDirectoryAsFile)}} > {{.as(WebArchive.{color:gray}*class*{color});}} -- 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

11 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues April 2014