[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986996#comment-16986996 ] Ben M. commented on MDEP-204: - Any ETA for MDEP v3.1.2? Thanks :) > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavić >Assignee: Robert Scholte >Priority: Major > Fix For: 3.1.2 > > Attachments: mvn-dependency-go-offline-failing-example.zip > > Time Spent: 40m > Remaining Estimate: 0h > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944690#comment-16944690 ] Hudson commented on MDEP-204: - Build failed in Jenkins: Maven TLP » maven-dependency-plugin » master #35 See https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/master/35/ > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavić >Assignee: Robert Scholte >Priority: Major > Fix For: 3.1.2 > > Attachments: mvn-dependency-go-offline-failing-example.zip > > Time Spent: 40m > Remaining Estimate: 0h > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921029#comment-16921029 ] Maarten Mulders commented on MDEP-204: -- I've made an attempt to rewrite this goal. It passes existing integration tests, and the one that I've added for this issue. There's a PR [at GitHub|https://github.com/apache/maven-dependency-plugin/pull/20]. > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic >Priority: Major > Attachments: mvn-dependency-go-offline-failing-example.zip > > Time Spent: 10m > Remaining Estimate: 0h > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[
https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919527#comment-16919527
]
Robert Scholte commented on MDEP-204:
-
I would expect that the code will be very similar to the
{{ResolvePluginsMojo}}. The have the some purpose, but just a different set of
artifacts.
> go-offline fails to resolve artifact available in maven reactor
> ---
>
> Key: MDEP-204
> URL: https://issues.apache.org/jira/browse/MDEP-204
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
>Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
>Reporter: Stevo Slavic
>Priority: Major
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be
> able to resolve all dependencies as they are only intermodule dependencies
> within same multimodule project which haven't been installed yet but are
> available in maven reactor so can be considered as resolvable in offline mode
> - instead dependency:go-offline fails to resolve these dependencies.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[
https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919521#comment-16919521
]
Maarten Mulders commented on MDEP-204:
--
I've shortly discussed this with [~rfscholte] and we've analysed the situation.
It seems to us that we cannot use the default Maven dependency resolution
mechanism here, as it doesn't allow to exclude certain artifacts (for example,
those we _know_ are in the Reactor).
I would propose to rewrite this Mojo so it roughly does the following:
* analyse the dependencies for the current module
* see if any of those are in the Reactor already
* attempt to resolve all dependencies that are _not_ in the reactor.
Regarding the latter, I think we could do it by following the logic in
{{MojoExecutor}}'s {{ensureDependenciesAreResolved}} method, except when we
invoke the {{LifeCycleDependencyResolver}} we supply the artifacts that are
already in the Reactor.
> go-offline fails to resolve artifact available in maven reactor
> ---
>
> Key: MDEP-204
> URL: https://issues.apache.org/jira/browse/MDEP-204
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
>Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
>Reporter: Stevo Slavic
>Priority: Major
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be
> able to resolve all dependencies as they are only intermodule dependencies
> within same multimodule project which haven't been installed yet but are
> available in maven reactor so can be considered as resolvable in offline mode
> - instead dependency:go-offline fails to resolve these dependencies.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[
https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16919331#comment-16919331
]
Maarten Mulders commented on MDEP-204:
--
It seems that when the project is not going to be packaged, nor going to be
compiled, the {{org.apache.maven.ReactorReader}} considers the project output
dir to be non-present.
Because of this, the {{org.apache.maven.ReactorReader}} considers the requested
artifact as not part of the Reactor. The
{{org.apache.maven.repository.internal.DefaultVersionResolver}} that invoked it
then decides to contact the remote repositories to see if they have the
artifact.
> go-offline fails to resolve artifact available in maven reactor
> ---
>
> Key: MDEP-204
> URL: https://issues.apache.org/jira/browse/MDEP-204
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
>Affects Versions: 2.0, 2.1
> Environment: maven 2.1.0
>Reporter: Stevo Slavic
>Priority: Major
> Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be
> able to resolve all dependencies as they are only intermodule dependencies
> within same multimodule project which haven't been installed yet but are
> available in maven reactor so can be considered as resolvable in offline mode
> - instead dependency:go-offline fails to resolve these dependencies.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16917956#comment-16917956 ] Maarten Mulders commented on MDEP-204: -- I wouldn't mind to take a look at this and see if I can do something about it. However, I've already spent a few hours trying to debug where this is actually failing, and I can't really find where I should start. So any pointers where the problem might reside are more than welcome... > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic >Priority: Major > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697416#comment-16697416 ] Hauke Jäger commented on MDEP-204: -- [~jbochenski], thank you a lot. I will definitely give it a try. [~michael-o] you're absolutely right. I shouldn't be complaining and instead solve it myself and maybe contribute it, if I get it to work. > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic >Priority: Major > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697414#comment-16697414 ] Jakub Bochenski commented on MDEP-204: -- You might be interested in https://github.com/qaware/go-offline-maven-plugin > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic >Priority: Major > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16697148#comment-16697148 ] Michael Osipov commented on MDEP-204: - [~yegair], granted. That's pretty sad from your POV. Consider that this is a volunteer project, none of us gets paid for this. > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic >Priority: Major > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16696607#comment-16696607 ] Hauke Jäger commented on MDEP-204: -- I just stumbled on this issue which is still present in 3.6.0 and I honestly have to say i can't believe this is still open after almost 10 years of time to fix it. We are living in the times of Docker multi stage builds but Maven makes it very hard to being used there. I will have to go for Gradle... > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic >Priority: Major > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16300110#comment-16300110 ] Eugene Tenkaev commented on MDEP-204: - Still not work on 3.0.2, it not allows to run in CircleCI service, wtf? > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970203#comment-15970203 ] Michael Osipov commented on MDEP-204: - Still fails with 3.0.0. > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15032155#comment-15032155 ] Bill Burcham commented on MDEP-204: --- An important use-case that didn't exist when this ticket was created is Docker. A Dockerized project typically has a Dockerfile at the root of the project. The Dockerfile contains instructions for building an image. In the Dockerfile, it is useful to separate two kinds of processing: 1. downloading external dependencies 2. compiling (local) sources This is the pattern for Dockerfiles in Python, Ruby, Node/JavaScript and others. The value of structuring the Dockerfile this way is that after building an initial image, subsequent source code changes do not incur the work in (1). This shortens the edit-compile-run loop. It might seem that mvn dependency:go-offline is ideally suited to (1) except for the fact that it fails when a local project (A) depends on another local project (B) if B has not yet been compiled and installed. But B cannot be installed until after step (2). Indeed, what is the point of go-offline, if it only (in general) succeeds after install? If mvn install succeeds, all external dependencies will have been cached locally, obviating the need to run mvn dependency:go-offline at all. Right? > go-offline fails to resolve artifact available in maven reactor > --- > > Key: MDEP-204 > URL: https://issues.apache.org/jira/browse/MDEP-204 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: go-offline >Affects Versions: 2.0, 2.1 > Environment: maven 2.1.0 >Reporter: Stevo Slavic > Attachments: mvn-dependency-go-offline-failing-example.zip > > > Attached is example project, for which IMO dependency:go-offline should be > able to resolve all dependencies as they are only intermodule dependencies > within same multimodule project which haven't been installed yet but are > available in maven reactor so can be considered as resolvable in offline mode > - instead dependency:go-offline fails to resolve these dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] Commented: (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=270219#comment-270219 ] Corneil du Plessis commented on MDEP-204: - I'm amazed that this issue is still unresolved. Does no one use dependency:go-offline for multi-module projects? go-offline fails to resolve artifact available in maven reactor --- Key: MDEP-204 URL: http://jira.codehaus.org/browse/MDEP-204 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: go-offline Affects Versions: 2.0, 2.1 Environment: maven 2.1.0 Reporter: Stevo Slavic Assignee: Brian Fox Attachments: mvn-dependency-go-offline-failing-example.zip Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=198747#action_198747 ] jonathan gold commented on MDEP-204: I'd also like to request that the plugin be changed to be reactor aware. I have projects with intermodule dependencies, and it appears that the only way I can use the dependency:tree plugin is to first install my project into my local repo. Full context of the discussion is here: http://markmail.org/message/z2sya75pynr3ia2k?q=list:org%2Eapache%2Emaven%2Eusers go-offline fails to resolve artifact available in maven reactor --- Key: MDEP-204 URL: http://jira.codehaus.org/browse/MDEP-204 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: go-offline Affects Versions: 2.0, 2.1 Environment: maven 2.1.0 Reporter: Stevo Slavic Assignee: Brian Fox Attachments: mvn-dependency-go-offline-failing-example.zip Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-204) go-offline fails to resolve artifact available in maven reactor
[ http://jira.codehaus.org/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=198762#action_198762 ] Brian Fox commented on MDEP-204: patches welcome ;-) go-offline fails to resolve artifact available in maven reactor --- Key: MDEP-204 URL: http://jira.codehaus.org/browse/MDEP-204 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: go-offline Affects Versions: 2.0, 2.1 Environment: maven 2.1.0 Reporter: Stevo Slavic Assignee: Brian Fox Attachments: mvn-dependency-go-offline-failing-example.zip Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
