[jira] [Commented] (IVY-1444) maven tests artifacts cannot be downloaded because they are mapped to private configurations
[
https://issues.apache.org/jira/browse/IVY-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072407#comment-15072407
]
jaikiran pai commented on IVY-1444:
---
Nathan, I'm _not_ a Ivy committer, so can't say if that patch with get
accepted. But I think you should go ahead and open a pull request and just drop
a mail on the dev list asking for someone to review. There hasn't been much
activity on that list lately but a new committer Stephen Haberman has been
appointed, so I guess there might be some response to your review request.
> maven tests artifacts cannot be downloaded because they are mapped to private
> configurations
>
>
> Key: IVY-1444
> URL: https://issues.apache.org/jira/browse/IVY-1444
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
>Affects Versions: 2.3.0
>Reporter: subes
>Priority: Blocker
>
> To run an embedded hadoop server, one has to use hadoops test libraries since
> version 2.1.0-beta.
> Though fetching those test libraries fails with:
> {quote}
> configuration not public in xxx#yyy;2.1.0-rc2: 'test'. It was
> required from zzz#bbb;working test
> {quote}
> This is because the maven pom.xml converter creates this configuration entry:
> {quote}
> visibility="private"
> description="this scope indicates that the dependency is not
> required for normal use of the application, and is only available for the test
> compilation and execution phases."
> extends="runtime"/>
> {quote}
> This makes it impossible to download test artifacts with ivy. Then the
> question arises, why are those tests jars in the maven repos anyway?
> Is there any way how to download the actual test artifacts of maven modules?
> Maybe the pom.xml converter needs to be adjusted to generate:
> {quote}
> visibility="public"
> description="this scope indicates that the dependency is not
> required for normal use of the application, and is only available for the test
> compilation and execution phases."
> extends="runtime"/>
> {quote}
> To fix this...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IVY-1444) maven tests artifacts cannot be downloaded because they are mapped to private configurations
[
https://issues.apache.org/jira/browse/IVY-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15072408#comment-15072408
]
Nathan Clement commented on IVY-1444:
-
I am out of the office returning Mon 18 Jan 2015. Please contact Quickstream
Customer Care at quickstr...@qvalent.com or on 1300 726 370 if your enquiry is
urgent.
> maven tests artifacts cannot be downloaded because they are mapped to private
> configurations
>
>
> Key: IVY-1444
> URL: https://issues.apache.org/jira/browse/IVY-1444
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
>Affects Versions: 2.3.0
>Reporter: subes
>Priority: Blocker
>
> To run an embedded hadoop server, one has to use hadoops test libraries since
> version 2.1.0-beta.
> Though fetching those test libraries fails with:
> {quote}
> configuration not public in xxx#yyy;2.1.0-rc2: 'test'. It was
> required from zzz#bbb;working test
> {quote}
> This is because the maven pom.xml converter creates this configuration entry:
> {quote}
> visibility="private"
> description="this scope indicates that the dependency is not
> required for normal use of the application, and is only available for the test
> compilation and execution phases."
> extends="runtime"/>
> {quote}
> This makes it impossible to download test artifacts with ivy. Then the
> question arises, why are those tests jars in the maven repos anyway?
> Is there any way how to download the actual test artifacts of maven modules?
> Maybe the pom.xml converter needs to be adjusted to generate:
> {quote}
> visibility="public"
> description="this scope indicates that the dependency is not
> required for normal use of the application, and is only available for the test
> compilation and execution phases."
> extends="runtime"/>
> {quote}
> To fix this...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IVY-1444) maven tests artifacts cannot be downloaded because they are mapped to private configurations
[
https://issues.apache.org/jira/browse/IVY-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052380#comment-15052380
]
Nathan Clement commented on IVY-1444:
-
I made a change to fix this in my local repo:
https://github.com/apache/ant-ivy/commit/162283d3326e3790672b6699acf256c9abf5974c
I can submit a pull request if there's any chance it would be accepted.
> maven tests artifacts cannot be downloaded because they are mapped to private
> configurations
>
>
> Key: IVY-1444
> URL: https://issues.apache.org/jira/browse/IVY-1444
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
>Affects Versions: 2.3.0
>Reporter: subes
>Priority: Blocker
>
> To run an embedded hadoop server, one has to use hadoops test libraries since
> version 2.1.0-beta.
> Though fetching those test libraries fails with:
> {quote}
> configuration not public in xxx#yyy;2.1.0-rc2: 'test'. It was
> required from zzz#bbb;working test
> {quote}
> This is because the maven pom.xml converter creates this configuration entry:
> {quote}
> visibility="private"
> description="this scope indicates that the dependency is not
> required for normal use of the application, and is only available for the test
> compilation and execution phases."
> extends="runtime"/>
> {quote}
> This makes it impossible to download test artifacts with ivy. Then the
> question arises, why are those tests jars in the maven repos anyway?
> Is there any way how to download the actual test artifacts of maven modules?
> Maybe the pom.xml converter needs to be adjusted to generate:
> {quote}
> visibility="public"
> description="this scope indicates that the dependency is not
> required for normal use of the application, and is only available for the test
> compilation and execution phases."
> extends="runtime"/>
> {quote}
> To fix this...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IVY-1444) maven tests artifacts cannot be downloaded because they are mapped to private configurations
[
https://issues.apache.org/jira/browse/IVY-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796682#comment-13796682
]
subes commented on IVY-1444:
Well, because of this blocker I decided to give my attempts to migrate from
ant+ivy to maven another go. This time I found the solutions that prevented me
from migrating my platform. Right now I am busy with migrating my ~50 modules.
So I won't be providing a fix for this and a fix in ivy is not needed for me
anymore.
maven tests artifacts cannot be downloaded because they are mapped to private
configurations
Key: IVY-1444
URL: https://issues.apache.org/jira/browse/IVY-1444
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.3.0
Reporter: subes
Priority: Blocker
To run an embedded hadoop server, one has to use hadoops test libraries since
version 2.1.0-beta.
Though fetching those test libraries fails with:
{quote}
configuration not public in xxx#yyy;2.1.0-rc2: 'test'. It was
required from zzz#bbb;working test
{quote}
This is because the maven pom.xml converter creates this configuration entry:
{quote}
conf name=test
visibility=private
description=this scope indicates that the dependency is not
required for normal use of the application, and is only available for the test
compilation and execution phases.
extends=runtime/
{quote}
This makes it impossible to download test artifacts with ivy. Then the
question arises, why are those tests jars in the maven repos anyway?
Is there any way how to download the actual test artifacts of maven modules?
Maybe the pom.xml converter needs to be adjusted to generate:
{quote}
conf name=test
visibility=public
description=this scope indicates that the dependency is not
required for normal use of the application, and is only available for the test
compilation and execution phases.
extends=runtime/
{quote}
To fix this...
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (IVY-1444) maven tests artifacts cannot be downloaded because they are mapped to private configurations
[
https://issues.apache.org/jira/browse/IVY-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13793571#comment-13793571
]
Stephen Haberman commented on IVY-1444:
---
Oddly enough, Maven does allow importing test artifacts:
http://maven.apache.org/guides/mini/guide-attached-tests.html
So, I agree, to be compatibility, the Ivy test conf should be public.
This should be an easy fix...@subes, did you want to submit one? I can probably
put something together if you'd like me to.
Ivy committers, any thoughts?
maven tests artifacts cannot be downloaded because they are mapped to private
configurations
Key: IVY-1444
URL: https://issues.apache.org/jira/browse/IVY-1444
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.3.0
Reporter: subes
Priority: Blocker
To run an embedded hadoop server, one has to use hadoops test libraries since
version 2.1.0-beta.
Though fetching those test libraries fails with:
{quote}
configuration not public in xxx#yyy;2.1.0-rc2: 'test'. It was
required from zzz#bbb;working test
{quote}
This is because the maven pom.xml converter creates this configuration entry:
{quote}
conf name=test
visibility=private
description=this scope indicates that the dependency is not
required for normal use of the application, and is only available for the test
compilation and execution phases.
extends=runtime/
{quote}
This makes it impossible to download test artifacts with ivy. Then the
question arises, why are those tests jars in the maven repos anyway?
Is there any way how to download the actual test artifacts of maven modules?
Maybe the pom.xml converter needs to be adjusted to generate:
{quote}
conf name=test
visibility=public
description=this scope indicates that the dependency is not
required for normal use of the application, and is only available for the test
compilation and execution phases.
extends=runtime/
{quote}
To fix this...
--
This message was sent by Atlassian JIRA
(v6.1#6144)
