April 2014 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKRES-179) Build Fails in JDK8

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKRES-179: ----------------------------------------- Summary: Build Fails in JDK8 Key: SHRINKRES-179 URL: https://issues.jboss.org/browse/SHRINKRES-179 Project: ShrinkWrap Resolvers Issue Type: Bug Affects Versions: 2.2.0-alpha-2 Reporter: Andrew Rubinger Assignee: Karel Piwko In environment: {code}alr@distortion ~/business/jboss/git/shrinkwrap/resolver $ mvn -version Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T12:37:52-05:00) Maven home: /usr/local/Cellar/maven/3.2.1/libexec Java version: 1.8.0_05, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_05.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"{code} The build fails due to: {code}[INFO] Running post-build script: /Users/alr/business/jboss/git/shrinkwrap/resolver/maven-plugin/target/it/dependency-tree-scope/verify.bsh [INFO] Finished post-build script: /Users/alr/business/jboss/git/shrinkwrap/resolver/maven-plugin/target/it/dependency-tree-scope/verify.bsh [INFO] ..SUCCESS (1.4 s) [INFO] ------------------------------------------------- [INFO] Build Summary: [INFO] Passed: 3, Failed: 1, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------- [ERROR] The following builds failed: [ERROR] * dependency-tree/pom.xml{code} Available in the logs: https://shrinkwrap.ci.cloudbees.com/view/SWR/job/ShrinkWrap_Resolver_upst... -- 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] (SHRINKWRAP-481) Fix "mvn site" failure after "mvn clean install"

by Andrew Rubinger (JIRA)

Andrew Rubinger created SHRINKWRAP-481: ------------------------------------------ Summary: Fix "mvn site" failure after "mvn clean install" Key: SHRINKWRAP-481 URL: https://issues.jboss.org/browse/SHRINKWRAP-481 Project: ShrinkWrap Issue Type: Task Affects Versions: 1.2.2 Reporter: Andrew Rubinger Assignee: Karel Piwko While we've always needed to execute "mvn install" before "mvn site", the site plugin used to work. This is now failing on the CloudBees builds and the JavaDocs can no longer be built. For instance: https://shrinkwrap.ci.cloudbees.com/job/ShrinkWrap_upstream-master/84/ -- 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 closed SHRINKRES-177. --------------------------------- > 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] (SHRINKRES-178) Class path resolution should omit directories it does not understand

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-178?page=com.atlassian.jira.plu... ] Karel Piwko updated SHRINKRES-178: ---------------------------------- Summary: Class path resolution should omit directories it does not understand (was: Class path resolution should omit directories is does not understand) > Class path resolution should omit directories it 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-178) Class path resolution should omit directories it does not understand

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-178?page=com.atlassian.jira.plu... ] Karel Piwko closed SHRINKRES-178. --------------------------------- > Class path resolution should omit directories it 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] (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: -------------------------------------------- These are simple types... Should definitely possible. > 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] (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: -------------------------------------------- Thanks, George. I will have a look. What I can say is that the common descriptor approach cannot provide every possible common method. If we are able to generate 90% then we are in a very good shape. You can see in the pom.xml that the anchors for generating common classes, which are very specific for each descriptor and how many versions have to be generated. I'll do my best. 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] (SHRINKDESC-155) Missing methods in generated common parents

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/SHRINKDESC-155?page=com.atlassian.jira.pl... ] George Gastaldi commented on SHRINKDESC-155: -------------------------------------------- It is still missing some methods, like: {code} PersistenceCommonDescriptor config = ... PersistencePersistenceUnitCommType unit = config.createPersistenceUnit(); //These methods are missing unit.name(unitName).description(DEFAULT_UNIT_DESC).provider(provider.getProvider()); {code} > 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] (SHRINKWRAP-453) Paths in webarchives are not calculated correctly

by Andrew Rubinger (JIRA)

[ https://issues.jboss.org/browse/SHRINKWRAP-453?page=com.atlassian.jira.pl... ] Andrew Rubinger resolved SHRINKWRAP-453. ---------------------------------------- Fix Version/s: 1.2.3 Resolution: Done Upstream: b5253fd1242e908de922a02f3ff0ecf4676c7ce6 Thanks, [~pawandubey]! > 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 > Fix For: 1.2.3 > > > 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, 11 months

1
0
0 / 0

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

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/SHRINKRES-178?page=com.atlassian.jira.plu... ] Karel Piwko resolved SHRINKRES-178. ----------------------------------- Resolution: Done Pushed upstream in https://github.com/shrinkwrap/resolver/commit/7f5b0813db53ea6fe937a633d44... > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues April 2014