October 2011 - shrinkwrap-issues - Jboss List Archives

[JBoss JIRA] (SHRINKWRAP-344) MavenDependencyResolver.loadMetadataFromPom should descend into a lower-level object

by Andrew Rubinger (Created) (JIRA)

MavenDependencyResolver.loadMetadataFromPom should descend into a lower-level object ------------------------------------------------------------------------------------ Key: SHRINKWRAP-344 URL: https://issues.jboss.org/browse/SHRINKWRAP-344 Project: ShrinkWrap Issue Type: Task Components: ext-resolver Reporter: Andrew Rubinger 12:17:38 PM) kpiwko: 3/ as what I call "void" method (12:17:42 PM) kpiwko: I gave you the example (12:17:44 PM) ALR: kpiwko: What's the void method in that line? (12:17:58 PM) ALR: "Prepares something for a different method"? (12:17:59 PM) kpiwko: the point is that loadEffectivePom does actually nothing (12:18:50 PM) kpiwko: if you don't call importXYZ() afterwards, internal state of the object is modified but you'll still get packaged nothing at all (12:20:08 PM) kpiwko: so, MavenDepedencyResolver.loadMetadataFromPom() is almost a "void" method as well (12:20:26 PM) kpiwko: I think we should support "void" methods (12:20:37 PM) kpiwko: and we should make their usage broader (12:20:41 PM) pil is now known as pil-dinner (12:22:47 PM) ALR: So just a terminology mismatch (12:22:51 PM) kpiwko: e.g. instead of having MavenDepedencyResolver.loadMetadataFrom() and MavenDepedencyResolver.loadDepedenciesFromPom() we should have a single "void" method and its call will expose a different interface which will allow user to includeLoadedDependencies() or activateLoadedRepositories(), method names are subject to change (12:22:52 PM) ALR: "void" methods return void. (12:22:58 PM) kpiwko: yep, I know (12:23:07 PM) ALR: So you wanna drill into something else. (12:23:18 PM) kpiwko: I was searching for better word but in vain (12:23:20 PM) ALR: HOw do you get back up to the MavenDependencyResolver level? (12:23:30 PM) ALR: In Descriptors it's "up" (12:23:40 PM) jose_freitas [~josefreit(a)189.101.213.101] entered the room. (12:23:52 PM) kpiwko: interesting (12:24:00 PM) kpiwko: there is no up concept in swr (12:24:10 PM) kpiwko: do you think it will help users? (12:24:36 PM) kpiwko: I don't think it is really needed (12:24:59 PM) ALR: kpiwko: Well, then you kinda break fluency. (12:25:07 PM) kpiwko: so user is not able to loadPom->includeAdditionalArtifacts->loadAnotherPom (12:25:21 PM) ALR: By drilling down into another object you then can't get back up to MavenDependencyResolver to continue messing w/ its properties. (12:25:38 PM) kpiwko: he has to loadPom->loadAnotherPom->addAdditionalArtifacts (12:25:41 PM) ALR: What's the motivation for this new level object then? (12:26:09 PM) jose_freitas: good afternoon guys. I'm ashamed for being late. (12:26:10 PM) kpiwko: reducing number of methods exposed to user (12:26:20 PM) ALR: Just to reflect that you need to call loadMetadataFromPom just before includeLoadedDependencies ? (12:26:21 PM) kpiwko: jose_freitas: welcome! Jaikiran jamezp jbossbot jbott jdlee jeand_ jhuska jose_freitas (12:26:27 PM) ALR: jose_freitas: Welcome, don't be ashamed. (12:26:32 PM) kpiwko: ALR: basically yes (12:26:34 PM) ALR: Grab the log and read along to catch up :) (12:27:16 PM) ALR: kpiwko: It's elegant so long as you can get back up IMO (12:27:35 PM) ALR: It's better than throwing IllegalStateException for not loading metadata from POM first (12:28:01 PM) jose_freitas: (just had a 4h hours meeting with an angry client.) (12:28:02 PM) ALR: kpiwko: OT: Be sure to "Like" facebook.com/arquillian (12:28:25 PM) kpiwko: how do you get an IDE to correctly resolve type with up()? (12:28:36 PM) kpiwko: if there are multiple entry points? (12:31:03 PM) ALR: <T> (12:31:40 PM) ALR: https://github.com/shrinkwrap/descriptors/blob/master/api-base/src/main/j... (12:32:02 PM) ALR: Then let each entry point define its own impl (12:33:12 PM) kpiwko: both in api-maven and impl-maven? (12:33:23 PM) ***kpiwko hard stop in one hour (12:33:50 PM) ALR: I'd have to see the cases further for all entry points (12:34:10 PM) ALR: But you could have N interfaces extending Child which supply T as well in api (12:34:22 PM) kpiwko: well, I think it is doable (12:34:31 PM) ALR: I suspect we're getting too fine-grained at this point. (12:34:37 PM) kpiwko: possibly (12:34:39 PM) ALR: Do we have enough to write up a JIRA a move on? (12:35:06 PM) kpiwko: I guess so (12:35:27 PM) ALR: OKee. So action item is a task to rework this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

6
6
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-337) Shrinkwrap maven resolver should be able to work offline after it worked online once: it should not download from the internet every time the test is running

by Geoffrey De Smet (JIRA)

Shrinkwrap maven resolver should be able to work offline after it worked online once: it should not download from the internet every time the test is running ------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: SHRINKWRAP-337 URL: https://issues.jboss.org/browse/SHRINKWRAP-337 Project: ShrinkWrap Issue Type: Bug Affects Versions: 1.0.0-beta-5 Reporter: Geoffrey De Smet Assignee: Karel Piwko Priority: Critical To reproduce: git clone https://github.com/kpiwko/blog.git kpiwko-blog cd kpiwko-blog // add jboss repo to ~/.m2/settings.xml Run tests => succeeds! // remove jboss repo from ~/.m2/settings.xml Run tests => Fails :( {code} 12:10:27.818 WARN - Failed downloading org/jboss/arquillian/arquillian-bom/1.0.0.CR5/arquillian-bom-1.0.0.CR5.pom from http://repo1.maven.org/maven2/, reason: org.apache.maven.wagon.ResourceDoesNotExistException: Could not find org/jboss/arquillian/arquillian-bom/1.0.0.CR5/arquillian-bom-1.0.0.CR5.pom in http://repo1.maven.org/maven2 12:10:28.077 WARN - Failed downloading org/jboss/arquillian/extension/arquillian-drone-bom/1.0.0.CR2/arquillian-drone-bom-1.0.0.CR2.pom from http://repo1.maven.org/maven2/, reason: org.apache.maven.wagon.ResourceDoesNotExistException: Could not find org/jboss/arquillian/extension/arquillian-drone-bom/1.0.0.CR2/arquillian-drone-bom-1.0.0.CR2.pom in http://repo1.maven.org/maven2 java.lang.RuntimeException: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.spec.WebArchive com.acme.ui.LoginScreenDefaultSeleniumTestCase.createDeployment() at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:160) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generateDeployment(AnnotationDeploymentScenarioGenerator.java:94) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.generate(AnnotationDeploymentScenarioGenerator.java:57) at org.jboss.arquillian.container.test.impl.client.deployment.DeploymentGenerator.generateDeployment(DeploymentGenerator.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:158) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:71) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:199) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.container.test.impl.client.deployment.AnnotationDeploymentScenarioGenerator.invoke(AnnotationDeploymentScenarioGenerator.java:156) ... 53 more Caused by: org.jboss.shrinkwrap.resolver.api.ResolutionException: Found 10 problems while building POM model from /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml1/ [ERROR] Non-resolvable import POM: Failed to resolve POM for org.jboss.arquillian:arquillian-bom:1.0.0.CR5 due to Could not find artifact org.jboss.arquillian:arquillian-bom:pom:1.0.0.CR5 in central (http://repo1.maven.org/maven2) @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 2/ [ERROR] Non-resolvable import POM: Failed to resolve POM for org.jboss.arquillian.extension:arquillian-drone-bom:1.0.0.CR2 due to Could not find artifact org.jboss.arquillian.extension:arquillian-drone-bom:pom:1.0.0.CR2 in central (http://repo1.maven.org/maven2) @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 3/ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 4/ [ERROR] 'dependencies.dependency.version' for org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 5/ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.extension:arquillian-drone-impl:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 6/ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.extension:arquillian-drone-selenium:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 7/ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.extension:arquillian-drone-selenium-server:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 8/ [ERROR] 'dependencies.dependency.version' for org.seleniumhq.selenium:selenium-java:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 9/ [ERROR] 'dependencies.dependency.version' for org.seleniumhq.selenium:selenium-server:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml 10/ [ERROR] 'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT, /home/gdesmet/projects/jboss/arquillian/kpiwko-blog/drone-selenium/pom.xml at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:154) at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:126) at org.jboss.shrinkwrap.resolver.impl.maven.MavenBuilderImpl.loadMetadataFromPom(MavenBuilderImpl.java:153) at com.acme.ui.Deployments.createLoginScreenDeployment(Deployments.java:43) at com.acme.ui.LoginScreenDefaultSeleniumTestCase.createDeployment(LoginScreenDefaultSeleniumTestCase.java:44) ... 58 more Caused by: org.apache.maven.model.building.ModelBuildingException: 10 problems were encountered while building the effective model for org.jboss.arquillian.extension.drone:drone-blog-selenium-example:1.0.0-SNAPSHOT [ERROR] Non-resolvable import POM: Failed to resolve POM for org.jboss.arquillian:arquillian-bom:1.0.0.CR5 due to Could not find artifact org.jboss.arquillian:arquillian-bom:pom:1.0.0.CR5 in central (http://repo1.maven.org/maven2) @ [ERROR] Non-resolvable import POM: Failed to resolve POM for org.jboss.arquillian.extension:arquillian-drone-bom:1.0.0.CR2 due to Could not find artifact org.jboss.arquillian.extension:arquillian-drone-bom:pom:1.0.0.CR2 in central (http://repo1.maven.org/maven2) @ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.junit:arquillian-junit-container:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-impl-maven:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.extension:arquillian-drone-impl:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.extension:arquillian-drone-selenium:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.jboss.arquillian.extension:arquillian-drone-selenium-server:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.seleniumhq.selenium:selenium-java:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.seleniumhq.selenium:selenium-server:jar is missing. @ [ERROR] 'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:422) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:374) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:365) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232) at org.jboss.shrinkwrap.resolver.impl.maven.MavenRepositorySystem.loadPom(MavenRepositorySystem.java:140) ... 62 more java.lang.NullPointerException at org.jboss.arquillian.drone.impl.DroneDestructor.destroyClassScopedDrone(DroneDestructor.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:180) at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:290) at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:45) at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:175) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:123) at org.junit.runner.JUnitCore.run(JUnitCore.java:157) at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:71) at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:199) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:62) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) {code} Other, better way to test it probably: - Run tests once => succeed. - Unplug network cable - Run tests again => fails. Everything should be in the local repository after the first test run. In this case there are no snapshots involved, but even snapshots don't get updates if the network is down. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
7
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-330) exclusion after includeDependenciesFromPom doesn't exclude artifacts

by Marek Schmidt (JIRA)

exclusion after includeDependenciesFromPom doesn't exclude artifacts -------------------------------------------------------------------- Key: SHRINKWRAP-330 URL: https://issues.jboss.org/browse/SHRINKWRAP-330 Project: ShrinkWrap Issue Type: Bug Components: ext-resolver Affects Versions: 1.0.0-beta-5 Reporter: Marek Schmidt .addAsLibraries(DependencyResolvers.use(MavenDependencyResolver.class) .includeDependenciesFromPom("pom.xml") .exclusion("foo:bar") .resolveAs(JavaArchive.class)); doesn't exclude foo:bar from included dependencies from pom.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
4
0 / 0

[JBoss JIRA] (SHRINKWRAP-345) MavenDependencyResolver resolves wrong version or scope for transitive dependencies when using <dependencyManagement>

by Mike Pettypiece (Created) (JIRA)

MavenDependencyResolver resolves wrong version or scope for transitive dependencies when using <dependencyManagement> --------------------------------------------------------------------------------------------------------------------- Key: SHRINKWRAP-345 URL: https://issues.jboss.org/browse/SHRINKWRAP-345 Project: ShrinkWrap Issue Type: Bug Components: ext-resolver Affects Versions: resolver-1.1.0-alpha-1 Reporter: Mike Pettypiece Using includesDependenciesFromPom() followed by resolveAsFiles() can produce a transitive dependency with the wrong scope or version if it is defined in the <dependencyManagment> section of the POM. e.g.: <dependencyManagement> <dependencies> <dependency> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> <version>1.1</version> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>commons-beanutils</groupId> <artifactId>commons-beanutils</artifactId> <version>1.7.0</version> <exclusions> <exclusion> <artifactId>servlet-api</artifactId> <groupId>javax.servlet</groupId> </exclusion> </exclusions> </dependency> <dependencies> common-beanutils depends on common-logging:1.0.3 but we've specified a higher version in the <dependencyManagement> section. A 'mvn package' will put common-logging:1.1 in the WEB-INF/lib directory but the following code will spit out a version of 1.0.3: File[] files = DependencyResolvers.use( MavenDependencyResolver.class ) .useCentralRepo( false ) .configureFrom( System.getProperty( "user.home" ) + "/.m2/settings.xml" ) .includeDependenciesFromPom( "pom.xml" ) .resolveAsFiles( new ScopeFilter( "compile", "runtime" ) ); for ( File f : files ) { System.out.println( f.getName() ); } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

7
7
0 / 0

[JBoss JIRA] (SHRINKWRAP-347) Shrinkwrap maven resolver doesn not support password prottected maven reposistory

by Sachin Patil (Created) (JIRA)

Shrinkwrap maven resolver doesn not support password prottected maven reposistory --------------------------------------------------------------------------------- Key: SHRINKWRAP-347 URL: https://issues.jboss.org/browse/SHRINKWRAP-347 Project: ShrinkWrap Issue Type: Bug Components: impl-base Affects Versions: 1.0.0-cr-1 Environment: Slackware64, jdk1.6.0.26, Reporter: Sachin Patil Fix For: resolver-1.1.0-alpha-1 Shrinkwrap maven resolver does not honor basic authentication mentioned in user settings.xml, if your are using password protected repository, maven artifact resolutions fails with following stack trace, Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact woodstox:wstx-asl:pom:3.2.1 from/to nexus (https://phobos.envista.com/mvn/content/groups/public): Not authorized. at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:975) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:966) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:707) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.flush(WagonRepositoryConnector.java:701) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.get(WagonRepositoryConnector.java:452) at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:456) ... 77 more Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Not authorized. at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:596) at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116) at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61) at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:615) at org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) I have already fixed this at https://github.com/sachin6870/resolver/commit/b005ae8c500819ba5b5e12a94ee.... Can you please verify this fix? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

6
7
0 / 0

[JBoss JIRA] (SHRINKWRAP-349) Backport SHRINKWRAP-273 fix to resolver

by Karel Piwko (Created) (JIRA)

Backport SHRINKWRAP-273 fix to resolver --------------------------------------- Key: SHRINKWRAP-349 URL: https://issues.jboss.org/browse/SHRINKWRAP-349 Project: ShrinkWrap Issue Type: Feature Request Components: ext-resolver Affects Versions: 1.0.0-beta-5 Reporter: Karel Piwko Assignee: Karel Piwko Priority: Minor Fix For: resolver-2.0.0-alpha-1 ShrinkWrap project is compiled to be backward compatible with Java 5. However, current configuration convinces Eclipse that project itself is is Java 1.5 version, which is not true. The leads to very annoying errors, especially when an interface method implementation is annotated with @Override. User must manually change project configuration after each import. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-297) Apply Formatting and Checkstyle Rules

by Andrew Rubinger (JIRA)

Apply Formatting and Checkstyle Rules ------------------------------------- Key: SHRINKWRAP-297 URL: https://issues.jboss.org/browse/SHRINKWRAP-297 Project: ShrinkWrap Issue Type: Task Reporter: Andrew Rubinger Assignee: Andrew Rubinger Let's get universal formatting enforced on the project. A good example of Checkstyle configs and IDE formatter/cleanup rules are in the AS7 project. Apply and bulk-format the codebase. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] (SHRINKWRAP-350) Cyclic dependency in WarTestCase

by Andrew Rubinger (Created) (JIRA)

Cyclic dependency in WarTestCase -------------------------------- Key: SHRINKWRAP-350 URL: https://issues.jboss.org/browse/SHRINKWRAP-350 Project: ShrinkWrap Issue Type: Bug Components: ext-resolver Reporter: Andrew Rubinger Assignee: Andrew Rubinger The WarTestCase is depending upon artifacts created during the build: {code}WebArchive archive = ShrinkWrap.create(MavenImporter.class, "testWithTestArtifacts.war").loadEffectivePom("pom.xml") .importBuildOutput().importTestBuildOutput().importTestDependencies().as(WebArchive.class); .importBuildOutput().as(WebArchive.class);{code} This sucks in dependencies upon artifacts that may not yet have been built when releasing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-273) Importing ShrinkWrap into Intellij leaves a broken setup of 1.6 source code with a 1.5 target

by Carlo de Wolf (JIRA)

Importing ShrinkWrap into Intellij leaves a broken setup of 1.6 source code with a 1.5 target --------------------------------------------------------------------------------------------- Key: SHRINKWRAP-273 URL: https://issues.jboss.org/browse/SHRINKWRAP-273 Project: ShrinkWrap Issue Type: Bug Reporter: Carlo de Wolf Priority: Minor It would appear that Intellij does not like the following section: {code:xml}  <plugin> <artifactId>maven-compiler-plugin</artifactId> <inherited>true</inherited> <configuration> <source>1.5</source> <target>1.5</target> <showDeprecation>false</showDeprecation> <showWarnings>true</showWarnings> <optimize>true</optimize> <compilerVersion>1.6</compilerVersion> <fork>true</fork> <argLine>-Xmx512M</argLine> <executable>${JAVA_HOME}/bin/javac</executable> </configuration> </plugin> {code} This creates (Intellij) Modules with language level 5 and Java Compiler -> Additional command line parameters parameters '-target 1.5'. This leads to errors appearing in the editor. Setting the correct Language level on the Module leads to a javac failure. Ideally the Modules should default to the Project language level (with the exception of shrinkwrap-api (and others?)). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (SHRINKWRAP-261) Shorthand for including maven artifacts

by Nicklas Karlsson (JIRA)

Shorthand for including maven artifacts --------------------------------------- Key: SHRINKWRAP-261 URL: https://issues.jboss.org/browse/SHRINKWRAP-261 Project: ShrinkWrap Issue Type: Feature Request Components: ext-resolver Affects Versions: 1.0.0-alpha-12 Reporter: Nicklas Karlsson Priority: Minor It would be handy to have a shortcut for including maven artifacts, something along the lines of MavenArtifact.resolve(Coordinate.of("joda-time", "joda-time", "1.6")).as(GenericArchive.class) or MavenArtifact.resolve("joda-time:joda-time:1.6").as(GenericArchive.class) or Maven.artifact("joda-time:joda-time:1.6") -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

8
23
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

shrinkwrap-issues October 2011