Adding resolver
Hi folks, I'd like to contribute resolver to Ivy - similar to , but resolving from Bintray's JCenter instead of Maven Central. JCenter is a superset of Maven Central and should ease the configuration for obtaining artifacts which aren't present in ibiblio (as they will probably be found in JCenter). Groovy's Grape has JCenter as the first resolver in chain for that exact reason. The users will be given a simple way to add jcenter resolver (like they have today in Gradle by adding jcenter() to repositories). I believe it should be an easy task and will be glad to do it. What do you think? Baruch. -- JFrog Developer Advocate www.jfrog.com +972544954353 @jbaruch <https://twitter.com/jbaruch/> http://linkd.in/jbaruch
Re: Adding resolver
I can add optional attribute, will defaults to jcenter. How that sounds? On Mar 3, 2014 5:35 PM, "Xavier Hanin" wrote: > Sounds good to me too. > > Do you plan to have support for jcenter only (eg sg equivalent to name="jcenter" root="http://jcenter.bintray.com"; m2compatible="true"/>), > or > also support other bintray repos? > > > On Mon, Mar 3, 2014 at 3:34 PM, Charles Duffy wrote: > > > Sounds good to me! > > > > I'd be happy to review this patch, but be aware that my involvement may > be > > a bit deferred -- I recently changed jobs and am in the middle of a move > > (from Austin to Chicago); this is holding up some other obligations I > have > > to the Ivy project as well (around getting a 2.4.0 release out the door). > > > > > > On Mon, Mar 3, 2014 at 7:58 AM, JBaruch wrote: > > > > > Hi folks, > > > > > > I'd like to contribute resolver to Ivy - similar to > , > > > but resolving from Bintray's JCenter instead of Maven Central. > > > > > > JCenter is a superset of Maven Central and should ease the > configuration > > > for obtaining artifacts which aren't present in ibiblio (as they will > > > probably be found in JCenter). > > > > > > Groovy's Grape has JCenter as the first resolver in chain for that > exact > > > reason. > > > > > > The users will be given a simple way to add jcenter resolver (like they > > > have today in Gradle by adding jcenter() to repositories). > > > > > > I believe it should be an easy task and will be glad to do it. > > > > > > What do you think? > > > > > > > > > Baruch. > > > > > > -- > > > JFrog Developer Advocate > > > www.jfrog.com > > > +972544954353 > > > @jbaruch <https://twitter.com/jbaruch/> > > > http://linkd.in/jbaruch > > > > > > > > > -- > Xavier Hanin > Lead architect at 4SH France - http://www.4sh.fr/ > RESTX creator and lead developer - http://restx.io/ > BordeauxJUG creator - http://www.bordeauxjug.org/ > Apache Ivy Creator - http://ant.apache.org/ivy/ >
Re: Adding resolver
Here you go:) https://issues.apache.org/jira/browse/IVY-1474 Hope to see it merged soon. Thanks, Baruch. -- JFrog Developer Advocate www.jfrog.com +972544954353 @jbaruch <https://twitter.com/jbaruch/> http://linkd.in/jbaruch On Mon, Mar 3, 2014 at 11:11 PM, Xavier Hanin wrote: > Sounds good to me. > > > On Mon, Mar 3, 2014 at 4:39 PM, JBaruch wrote: > > > I can add optional attribute, will defaults to jcenter. > > > > How that sounds? > > On Mar 3, 2014 5:35 PM, "Xavier Hanin" wrote: > > > > > Sounds good to me too. > > > > > > Do you plan to have support for jcenter only (eg sg equivalent to > > > > name="jcenter" root="http://jcenter.bintray.com"; > m2compatible="true"/>), > > > or > > > also support other bintray repos? > > > > > > > > > On Mon, Mar 3, 2014 at 3:34 PM, Charles Duffy > wrote: > > > > > > > Sounds good to me! > > > > > > > > I'd be happy to review this patch, but be aware that my involvement > may > > > be > > > > a bit deferred -- I recently changed jobs and am in the middle of a > > move > > > > (from Austin to Chicago); this is holding up some other obligations I > > > have > > > > to the Ivy project as well (around getting a 2.4.0 release out the > > door). > > > > > > > > > > > > On Mon, Mar 3, 2014 at 7:58 AM, JBaruch wrote: > > > > > > > > > Hi folks, > > > > > > > > > > I'd like to contribute resolver to Ivy - similar to > > > , > > > > > but resolving from Bintray's JCenter instead of Maven Central. > > > > > > > > > > JCenter is a superset of Maven Central and should ease the > > > configuration > > > > > for obtaining artifacts which aren't present in ibiblio (as they > will > > > > > probably be found in JCenter). > > > > > > > > > > Groovy's Grape has JCenter as the first resolver in chain for that > > > exact > > > > > reason. > > > > > > > > > > The users will be given a simple way to add jcenter resolver (like > > they > > > > > have today in Gradle by adding jcenter() to repositories). > > > > > > > > > > I believe it should be an easy task and will be glad to do it. > > > > > > > > > > What do you think? > > > > > > > > > > > > > > > Baruch. > > > > > > > > > > -- > > > > > JFrog Developer Advocate > > > > > www.jfrog.com > > > > > +972544954353 > > > > > @jbaruch <https://twitter.com/jbaruch/> > > > > > http://linkd.in/jbaruch > > > > > > > > > > > > > > > > > > > > > -- > > > Xavier Hanin > > > Lead architect at 4SH France - http://www.4sh.fr/ > > > RESTX creator and lead developer - http://restx.io/ > > > BordeauxJUG creator - http://www.bordeauxjug.org/ > > > Apache Ivy Creator - http://ant.apache.org/ivy/ > > > > > > > > > -- > Xavier Hanin > Lead architect at 4SH France - http://www.4sh.fr/ > RESTX creator and lead developer - http://restx.io/ > BordeauxJUG creator - http://www.bordeauxjug.org/ > Apache Ivy Creator - http://ant.apache.org/ivy/ >
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Can we use this opportunity to sneak IVY-1474 in? Baruch. -- JFrog Developer Advocate www.jfrog.com +972544954353 @jbaruch <https://twitter.com/jbaruch/> http://linkd.in/jbaruch On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée wrote: > It was so obvious that this release candidate should be canceled that I > forgot to officially set it. Here it is. > > I see that the infra ticket is resolved. Jean-Louis spotted some issues > with it though. But I guess we will retry very soon. > > Nicolas > > > Le 9 nov. 2014 à 17:56, Nicolas Lalevée a > écrit : > > > > I have built a release candidate for Ivy 2.4.0 > > > > The git tag of this release is: > https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2 > > > > The artifacts has been published to: > https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093 > > > > Do you vote for the release of these binaries? > > > > [ ] Yes > > [ ] No > > > > Regards, > > Nicolas > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > > For additional commands, e-mail: dev-h...@ant.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Perfect, we are on it. On 3 Dec 2014 12:29, "Nicolas Lalevée" wrote: > I would still would like some doc. > > The doc in the code source is still broken and it make it difficult to > know how it is rendered. > In the mean time time, you could write a page. I will then ensure myself > that is proper included in the doc and rendered when the build will be > fixed. You can take this file as an exemple: > > https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD > < > https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD > > > > Nicolas > > > Le 2 déc. 2014 à 22:56, JBaruch a écrit : > > > > Can we use this opportunity to sneak IVY-1474 in? > > > > Baruch. > > > > -- > > JFrog Developer Advocate > > www.jfrog.com > > +972544954353 > > @jbaruch <https://twitter.com/jbaruch/> > > http://linkd.in/jbaruch > > > > On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée < > nicolas.lale...@hibnet.org> > > wrote: > > > >> It was so obvious that this release candidate should be canceled that I > >> forgot to officially set it. Here it is. > >> > >> I see that the infra ticket is resolved. Jean-Louis spotted some issues > >> with it though. But I guess we will retry very soon. > >> > >> Nicolas > >> > >>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée a > >> écrit : > >>> > >>> I have built a release candidate for Ivy 2.4.0 > >>> > >>> The git tag of this release is: > >> > https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2 > >>> > >>> The artifacts has been published to: > >> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093 > >>> > >>> Do you vote for the release of these binaries? > >>> > >>> [ ] Yes > >>> [ ] No > >>> > >>> Regards, > >>> Nicolas > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > >>> For additional commands, e-mail: dev-h...@ant.apache.org > >>> > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > >> For additional commands, e-mail: dev-h...@ant.apache.org > >> > >> > >
Re: [CANCELED][VOTE] Release Ivy 2.4.0
documentation added. Baruch. -- JFrog Developer Advocate www.jfrog.com +972544954353 @jbaruch <https://twitter.com/jbaruch/> http://linkd.in/jbaruch On Wed, Dec 3, 2014 at 1:37 PM, JBaruch wrote: > Perfect, we are on it. > On 3 Dec 2014 12:29, "Nicolas Lalevée" wrote: > >> I would still would like some doc. >> >> The doc in the code source is still broken and it make it difficult to >> know how it is rendered. >> In the mean time time, you could write a page. I will then ensure myself >> that is proper included in the doc and rendered when the build will be >> fixed. You can take this file as an exemple: >> >> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD >> < >> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD >> > >> >> Nicolas >> >> > Le 2 déc. 2014 à 22:56, JBaruch a écrit : >> > >> > Can we use this opportunity to sneak IVY-1474 in? >> > >> > Baruch. >> > >> > -- >> > JFrog Developer Advocate >> > www.jfrog.com >> > +972544954353 >> > @jbaruch <https://twitter.com/jbaruch/> >> > http://linkd.in/jbaruch >> > >> > On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée < >> nicolas.lale...@hibnet.org> >> > wrote: >> > >> >> It was so obvious that this release candidate should be canceled that I >> >> forgot to officially set it. Here it is. >> >> >> >> I see that the infra ticket is resolved. Jean-Louis spotted some issues >> >> with it though. But I guess we will retry very soon. >> >> >> >> Nicolas >> >> >> >>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée >> a >> >> écrit : >> >>> >> >>> I have built a release candidate for Ivy 2.4.0 >> >>> >> >>> The git tag of this release is: >> >> >> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2 >> >>> >> >>> The artifacts has been published to: >> >> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093 >> >>> >> >>> Do you vote for the release of these binaries? >> >>> >> >>> [ ] Yes >> >>> [ ] No >> >>> >> >>> Regards, >> >>> Nicolas >> >>> >> >>> >> >>> - >> >>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org >> >>> For additional commands, e-mail: dev-h...@ant.apache.org >> >>> >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org >> >> For additional commands, e-mail: dev-h...@ant.apache.org >> >> >> >> >> >>
Re: [VOTE] Ivy 2.4.0 Release - take 2
Sorry to nag here, but any chance you can sneak the bintray resolver in? Now, when it has documentation and everything? Pretty please? Baruch. -- JFrog Developer Advocate www.jfrog.com +972544954353 @jbaruch <https://twitter.com/jbaruch/> http://linkd.in/jbaruch On Wed, Dec 17, 2014 at 5:25 AM, Nicolas Lalevée wrote: > > > > Le 17 déc. 2014 à 04:09, Antoine Levy Lambert a écrit : > > > > Nicolas, Jean-Louis, what are your thoughts ? > > > > The problem reported by Stefan with the ivy.xml in the source archive > must be caused by something in the build process replacing the ivy.xml of > the source tree with an expanded version of the same file generated when > the task runs ? > > The purpose of this change is that it fixes the dependencies of Ivy. I see > no particular harm here. > > But as Stefan, generally speaking, I prefer the source release to be an > extract of the source repository. So there is no possible confusion. > > > I guess a minor edit in the build file to make this modified version of > ivy.xml go somewhere under the build folder should address this issue for > this release and the next ones. > > > > I have not spent myself a lot of time on ivy yet but I would like to > spend some in 2015 - or maybe even next week if my kids are busy out of the > house … > > > > I also know how it feels when one creates a release candidate and some > minor problems are found and one has to again go through 20 steps in a > ReleaseInstructions document … > > Actually releasing Ivy is quite straight forward, no issues with that. > See: http://ant.apache.org/ivy/history/trunk/dev/makerelease.html < > http://ant.apache.org/ivy/history/trunk/dev/makerelease.html> > Probably the signing of the artifacts can be more automatic. I have seen > there is ant target for that but I haven’t tested it yet. > > What trouble me more is what is the exact process to push artifacts into > Maven repo after the release. And we’ll need to figure out how to push it > into the Eclipse updatesite too. > > > But I am sure we will get there finally. > > I am sure too. We have to either be patient or actively act on it, > depending on our available time. > > > On Dec 14, 2014, at 5:43 AM, Stefan Bodewig wrote: > > > >> We should be using signed tags (git tag -s or -u) rather than > >> lightweight tags for releases. I know we haven't cut any releases from > >> git so far, so we'll be learning as we go along. > > I do not know how it works, but I’ll figure it out. And update the release > documentation. > > Nicolas > >
Re: [VOTE] Ivy 2.4.0 Release - take 2
Yay! Thanks, guys. Looking forward for the release. Baruch. -- JFrog Developer Advocate www.jfrog.com +972544954353 @jbaruch <https://twitter.com/jbaruch/> http://linkd.in/jbaruch On Wed, Dec 17, 2014 at 2:15 PM, Nicolas Lalevée wrote: > > Yes, it is already in the last attempt. > > Nicolas > > > Le 17 déc. 2014 à 22:56, anto...@gmx.de a écrit : > > > > Hi I think the bintray resolver is part of the future release. > > > > Antoine Levy-Lambert > > > > - Reply message - > > From: "JBaruch" > > To: "Ant Developers List" > > Subject: [VOTE] Ivy 2.4.0 Release - take 2 > > Date: Wed, Dec 17, 2014 3:47 PM > > > > Sorry to nag here, but any chance you can sneak the bintray resolver in? > > Now, when it has documentation and everything? > > Pretty please? > > > > Baruch. > > > > -- > > JFrog Developer Advocate > > www.jfrog.com > > +972544954353 > > @jbaruch <https://twitter.com/jbaruch/> > > http://linkd.in/jbaruch > > > > On Wed, Dec 17, 2014 at 5:25 AM, Nicolas Lalevée < > nicolas.lale...@hibnet.org > >> wrote: > >> > >> > >>> Le 17 déc. 2014 à 04:09, Antoine Levy Lambert a > écrit : > >>> > >>> Nicolas, Jean-Louis, what are your thoughts ? > >>> > >>> The problem reported by Stefan with the ivy.xml in the source archive > >> must be caused by something in the build process replacing the ivy.xml > of > >> the source tree with an expanded version of the same file generated when > >> the task runs ? > >> > >> The purpose of this change is that it fixes the dependencies of Ivy. I > see > >> no particular harm here. > >> > >> But as Stefan, generally speaking, I prefer the source release to be an > >> extract of the source repository. So there is no possible confusion. > >> > >>> I guess a minor edit in the build file to make this modified version of > >> ivy.xml go somewhere under the build folder should address this issue > for > >> this release and the next ones. > >>> > >>> I have not spent myself a lot of time on ivy yet but I would like to > >> spend some in 2015 - or maybe even next week if my kids are busy out of > the > >> house … > >>> > >>> I also know how it feels when one creates a release candidate and some > >> minor problems are found and one has to again go through 20 steps in a > >> ReleaseInstructions document … > >> > >> Actually releasing Ivy is quite straight forward, no issues with that. > >> See: http://ant.apache.org/ivy/history/trunk/dev/makerelease.html < > >> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html> > >> Probably the signing of the artifacts can be more automatic. I have seen > >> there is ant target for that but I haven’t tested it yet. > >> > >> What trouble me more is what is the exact process to push artifacts into > >> Maven repo after the release. And we’ll need to figure out how to push > it > >> into the Eclipse updatesite too. > >> > >>> But I am sure we will get there finally. > >> > >> I am sure too. We have to either be patient or actively act on it, > >> depending on our available time. > >> > >>> On Dec 14, 2014, at 5:43 AM, Stefan Bodewig > wrote: > >>> > >>>> We should be using signed tags (git tag -s or -u) rather than > >>>> lightweight tags for releases. I know we haven't cut any releases > from > >>>> git so far, so we'll be learning as we go along. > >> > >> I do not know how it works, but I’ll figure it out. And update the > release > >> documentation. > >> > >> Nicolas > >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
[GitHub] ant-ivy pull request: The default subject is `bintray`, not 'jcent...
GitHub user jbaruch opened a pull request: https://github.com/apache/ant-ivy/pull/5 The default subject is `bintray`, not 'jcenter` The code is good, typo is in the doc only. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jbaruch/ant-ivy patch-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ant-ivy/pull/5.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5 commit 5f1137a006590a03496419997d7b8638eb6d9b58 Author: Baruch Sadogursky Date: 2014-12-28T09:15:52Z The default subject is `bintray`, not 'jcenter` The code is good, typo is in the doc only. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
