Re: https://issues.apache.org/jira/browse/MNG-5895
Hi Karl Heinz, I would expect the problem to be in the maven-aether-provider. Aether does all the management, but it is this provider which decides what are dependencies. And yes, there's a cache: org.apache.maven.repository.internal.DefaultModelCache Robert On Mon, 18 Jul 2016 20:40:26 +0200, Karl Heinz Marbaise wrote: Hi, no one and idea ? Kind regards Karl Heinz On 7/17/16 11:46 AM, Karl Heinz Marbaise wrote: Hi, so after I found the issue related to reactor order (MNG-6057) (Thanks Robert for the tip which brought me to right direction) now I'm diving more into the problem related to the resolution of the artifacts which I have described related to maven-assembly-plugin after more testing I have found that it seemed to be related to the following line of code: @Requirement private RepositorySystem resolver; ... And the following line is the culprit (transition to Maven Core): result = resolver.resolve( req ); The request in maven-assembly-plugin seemed to be filled with the correct data: final MavenProject project = configSource.getProject(); ArtifactResolutionRequest req = new ArtifactResolutionRequest(); req.setLocalRepository( configSource.getLocalRepository() ); req.setResolveRoot( false ); req.setRemoteRepositories( repos ); req.setResolveTransitively( true ); req.setArtifact( project.getArtifact() ); req.setArtifactDependencies( dependencyArtifacts ); req.setManagedVersionMap( project.getManagedVersionMap() ); req.setCollectionFilter( filter ); req.setOffline( configSource.getMavenSession().isOffline() ); req.setForceUpdate( configSource.getMavenSession().getRequest().isUpdateSnapshots() ); req.setServers( configSource.getMavenSession().getRequest().getServers() ); req.setMirrors( configSource.getMavenSession().getRequest().getMirrors() ); req.setProxies( configSource.getMavenSession().getRequest().getProxies() ); And non of the above data does contain the wrong versions (1.7.2-SNAPSHOT), but I get always errors like this: [DEBUG] Could not find metadata com.soebes.examples.j2ee:service-client:1.7.2-SNAPSHOT/maven-metadata.xml in local (/Users/kama/.m2/repository) [WARNING] Missing POM for com.soebes.examples.j2ee:service-client:jar:1.7.2-SNAPSHOT: Error resolving project artifact: Could not find artifact com.soebes.examples.j2ee:service-client:pom:1.7.2-SNAPSHOT for project com.soebes.examples.j2ee:service-client:pom:1.7.2-SNAPSHOT [DEBUG] Could not find metadata com.soebes.examples.j2ee:webgui:1.7.2-SNAPSHOT/maven-metadata.xml in local (/Users/kama/.m2/repository) What I can't explain where those wrong version numbers are coming from? Is there a kind of cache involved which contains this versions ? Where is this defined? Can I clean it ? (RepositorySystem) At the moment I'm convinced that it is a Maven core issue. The RepositorySystem is an interface where two implementation exist:LegacyRepositorySystem and TestMavenRepositorySystem. So LegacyRepositorySystem contains an appropriate implementation of: public ArtifactResolutionResult resolve( ArtifactResolutionRequest request ) But I can't find a hint of where those wrong version numbers could come from cause the ArtifactResolutionRequest contains the correct data ... Anyone an idea? Hint ? Good questions? Kind regards Karl Heinz Marbaise So this looks at the moment like an issue in Maven core... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: https://issues.apache.org/jira/browse/MNG-5895
Hi, no one and idea ? Kind regards Karl Heinz On 7/17/16 11:46 AM, Karl Heinz Marbaise wrote: Hi, so after I found the issue related to reactor order (MNG-6057) (Thanks Robert for the tip which brought me to right direction) now I'm diving more into the problem related to the resolution of the artifacts which I have described related to maven-assembly-plugin after more testing I have found that it seemed to be related to the following line of code: @Requirement private RepositorySystem resolver; ... And the following line is the culprit (transition to Maven Core): result = resolver.resolve( req ); The request in maven-assembly-plugin seemed to be filled with the correct data: final MavenProject project = configSource.getProject(); ArtifactResolutionRequest req = new ArtifactResolutionRequest(); req.setLocalRepository( configSource.getLocalRepository() ); req.setResolveRoot( false ); req.setRemoteRepositories( repos ); req.setResolveTransitively( true ); req.setArtifact( project.getArtifact() ); req.setArtifactDependencies( dependencyArtifacts ); req.setManagedVersionMap( project.getManagedVersionMap() ); req.setCollectionFilter( filter ); req.setOffline( configSource.getMavenSession().isOffline() ); req.setForceUpdate( configSource.getMavenSession().getRequest().isUpdateSnapshots() ); req.setServers( configSource.getMavenSession().getRequest().getServers() ); req.setMirrors( configSource.getMavenSession().getRequest().getMirrors() ); req.setProxies( configSource.getMavenSession().getRequest().getProxies() ); And non of the above data does contain the wrong versions (1.7.2-SNAPSHOT), but I get always errors like this: [DEBUG] Could not find metadata com.soebes.examples.j2ee:service-client:1.7.2-SNAPSHOT/maven-metadata.xml in local (/Users/kama/.m2/repository) [WARNING] Missing POM for com.soebes.examples.j2ee:service-client:jar:1.7.2-SNAPSHOT: Error resolving project artifact: Could not find artifact com.soebes.examples.j2ee:service-client:pom:1.7.2-SNAPSHOT for project com.soebes.examples.j2ee:service-client:pom:1.7.2-SNAPSHOT [DEBUG] Could not find metadata com.soebes.examples.j2ee:webgui:1.7.2-SNAPSHOT/maven-metadata.xml in local (/Users/kama/.m2/repository) What I can't explain where those wrong version numbers are coming from? Is there a kind of cache involved which contains this versions ? Where is this defined? Can I clean it ? (RepositorySystem) At the moment I'm convinced that it is a Maven core issue. The RepositorySystem is an interface where two implementation exist:LegacyRepositorySystem and TestMavenRepositorySystem. So LegacyRepositorySystem contains an appropriate implementation of: public ArtifactResolutionResult resolve( ArtifactResolutionRequest request ) But I can't find a hint of where those wrong version numbers could come from cause the ArtifactResolutionRequest contains the correct data ... Anyone an idea? Hint ? Good questions? Kind regards Karl Heinz Marbaise So this looks at the moment like an issue in Maven core... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
https://issues.apache.org/jira/browse/MNG-5895
Hi, so after I found the issue related to reactor order (MNG-6057) (Thanks Robert for the tip which brought me to right direction) now I'm diving more into the problem related to the resolution of the artifacts which I have described related to maven-assembly-plugin after more testing I have found that it seemed to be related to the following line of code: @Requirement private RepositorySystem resolver; ... And the following line is the culprit (transition to Maven Core): result = resolver.resolve( req ); The request in maven-assembly-plugin seemed to be filled with the correct data: final MavenProject project = configSource.getProject(); ArtifactResolutionRequest req = new ArtifactResolutionRequest(); req.setLocalRepository( configSource.getLocalRepository() ); req.setResolveRoot( false ); req.setRemoteRepositories( repos ); req.setResolveTransitively( true ); req.setArtifact( project.getArtifact() ); req.setArtifactDependencies( dependencyArtifacts ); req.setManagedVersionMap( project.getManagedVersionMap() ); req.setCollectionFilter( filter ); req.setOffline( configSource.getMavenSession().isOffline() ); req.setForceUpdate( configSource.getMavenSession().getRequest().isUpdateSnapshots() ); req.setServers( configSource.getMavenSession().getRequest().getServers() ); req.setMirrors( configSource.getMavenSession().getRequest().getMirrors() ); req.setProxies( configSource.getMavenSession().getRequest().getProxies() ); And non of the above data does contain the wrong versions (1.7.2-SNAPSHOT), but I get always errors like this: [DEBUG] Could not find metadata com.soebes.examples.j2ee:service-client:1.7.2-SNAPSHOT/maven-metadata.xml in local (/Users/kama/.m2/repository) [WARNING] Missing POM for com.soebes.examples.j2ee:service-client:jar:1.7.2-SNAPSHOT: Error resolving project artifact: Could not find artifact com.soebes.examples.j2ee:service-client:pom:1.7.2-SNAPSHOT for project com.soebes.examples.j2ee:service-client:pom:1.7.2-SNAPSHOT [DEBUG] Could not find metadata com.soebes.examples.j2ee:webgui:1.7.2-SNAPSHOT/maven-metadata.xml in local (/Users/kama/.m2/repository) What I can't explain where those wrong version numbers are coming from? Is there a kind of cache involved which contains this versions ? Where is this defined? Can I clean it ? (RepositorySystem) At the moment I'm convinced that it is a Maven core issue. The RepositorySystem is an interface where two implementation exist:LegacyRepositorySystem and TestMavenRepositorySystem. So LegacyRepositorySystem contains an appropriate implementation of: public ArtifactResolutionResult resolve( ArtifactResolutionRequest request ) But I can't find a hint of where those wrong version numbers could come from cause the ArtifactResolutionRequest contains the correct data ... Anyone an idea? Hint ? Good questions? Kind regards Karl Heinz Marbaise So this looks at the moment like an issue in Maven core... - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: https://issues.apache.org/jira/browse/MNG-5895
Hi Karl Heinz, I think you should focus on the org.apache.maven.graph.DefaultGraphBuilder when you're talking about the reactor order. Robert On Fri, 01 Jul 2016 19:55:56 +0200, Karl Heinz Marbaise wrote: Hi, I have described two issues within this issue. First the changed reactor order based on using a property for the version and second the problem related to the version which is used for artifacts. At the moment I'm trying to identify the first issue...but currently I'm a little bit lost... May be one or more of the other devs can give me hint where to search in Maven Core for the problem or a hint how to solve the problem? I have also checked with the current master of 3.4.0-SNAPSHOT and see the same changed order of the reactor if i use a property for the version in such multi module build... The second issue I will investigate further if the first one has been done... Any help is appreciated...Many thanks in advance.. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: https://issues.apache.org/jira/browse/MNG-5895
Hi, I also realized that we currently having failing Maven Core IT[1] which is related to this subject[2] Kind regards Karl Heinz [1]: https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/core-integration-testing-maven-3-jdk-1.7/1820/console [2] https://issues.apache.org/jira/browse/MNG-5576 On 7/1/16 7:55 PM, Karl Heinz Marbaise wrote: Hi, I have described two issues within this issue. First the changed reactor order based on using a property for the version and second the problem related to the version which is used for artifacts. At the moment I'm trying to identify the first issue...but currently I'm a little bit lost... May be one or more of the other devs can give me hint where to search in Maven Core for the problem or a hint how to solve the problem? I have also checked with the current master of 3.4.0-SNAPSHOT and see the same changed order of the reactor if i use a property for the version in such multi module build... The second issue I will investigate further if the first one has been done... Any help is appreciated...Many thanks in advance.. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
https://issues.apache.org/jira/browse/MNG-5895
Hi, I have described two issues within this issue. First the changed reactor order based on using a property for the version and second the problem related to the version which is used for artifacts. At the moment I'm trying to identify the first issue...but currently I'm a little bit lost... May be one or more of the other devs can give me hint where to search in Maven Core for the problem or a hint how to solve the problem? I have also checked with the current master of 3.4.0-SNAPSHOT and see the same changed order of the reactor if i use a property for the version in such multi module build... The second issue I will investigate further if the first one has been done... Any help is appreciated...Many thanks in advance.. Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
