Re: [PR] IVY-1485, IVY-1661: collect dependency properties by conf [ant-ivy]

2025-08-01 Thread via GitHub
maartenc commented on PR #109: URL: https://github.com/apache/ant-ivy/pull/109#issuecomment-3145729705 Thank you for your contributions, I'll try to look at them in the next couple of weeks. -- This is an automated message from the Apache Git Service. To respond to the message, please log

[PR] IVY-1485, IVY-1661: collect dependency properties by conf [ant-ivy]

2025-08-01 Thread via GitHub
/jira/browse/IVY-1485 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For queries about this service, please contact

[GitHub] ant-ivy pull request #65: IVY-1485 Ensure dependency is applicable to all co...

2018-02-06 Thread twogee
Github user twogee closed the pull request at: https://github.com/apache/ant-ivy/pull/65 --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy issue #65: IVY-1485 Ensure dependency is applicable to all configura...

2018-02-06 Thread jaikiran
Github user jaikiran commented on the issue: https://github.com/apache/ant-ivy/pull/65 These changes don't solve the real issue. The details of this issue are part of the discussion in ant dev mailing list, where I explained what the real issue is. I do have a completely different cod

[GitHub] ant-ivy issue #65: IVY-1485 Ensure dependency is applicable to all configura...

2018-02-01 Thread twogee
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/65 @jaikiran please let me know if you did some addition coding, otherwise I hope you would rather focus on JUnit 5 😄 --- - To uns

[GitHub] ant-ivy pull request #65: IVY-1485 Ensure dependency is applicable to all co...

2018-02-01 Thread twogee
GitHub user twogee opened a pull request: https://github.com/apache/ant-ivy/pull/65 IVY-1485 Ensure dependency is applicable to all configurations I adopted a patch by @tbingaman You can merge this pull request into a Git repository by running: $ git pull https://github.com

Re: IVY-1485

2017-08-07 Thread Gintautas Grigelionis
>> I went through JIRA issues and noticed >> https://issues.apache.org/jira/browse/IVY-1485 was discussed relatively >> recently ;-) Anybody looking into it? >> >> Gintas >> >> P.S. JIRA li

Re: IVY-1485

2017-08-07 Thread Jaikiran Pai
I'm looking into that JIRA. I'll assigned it to my name now. -Jaikiran On 06/08/17 12:52 PM, Gintautas Grigelionis wrote: I went through JIRA issues and noticed https://issues.apache.org/jira/browse/IVY-1485 was discussed relatively recently ;-) Anybody looking into it? Gintas

IVY-1485

2017-08-06 Thread Gintautas Grigelionis
I went through JIRA issues and noticed https://issues.apache.org/jira/browse/IVY-1485 was discussed relatively recently ;-) Anybody looking into it? Gintas P.S. JIRA lists about 100 documentation related issues. Should be a low hanging fruit...

Re: IVY-1485, resolve report and resolved versions

2017-05-26 Thread Nicolas Lalevée
is an option [3], > defaulting to true [4]. > > Two options: > - continue to support the property file and correctly produce it to fix > IVY-1485 [5]. > - drop this property file, make the xml report always produced, and make the > deliver re

Re: IVY-1485, resolve report and resolved versions

2017-05-26 Thread J Pai
is the resolve may not be produced, it is an option [3], defaulting to true [4]. Two options: - continue to support the property file and correctly produce it to fix IVY-1485 [5]. - drop this property file, make the xml report always produced, and make the deliver read the report rather than the pr

IVY-1485, resolve report and resolved versions

2017-05-26 Thread Nicolas Lalevée
is the resolve may not be produced, it is an option [3], defaulting to true [4]. Two options: - continue to support the property file and correctly produce it to fix IVY-1485 [5]. - drop this property file, make the xml report always produced, and make the deliver read the report rather than