|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
Including builder resolver in ivyI'd like to propose that the new "builder" resolver be included in ivy. In
order to do this however, other developers need to vote yes or no. So I'd ask that you please let the list know your opinion. Quick summary: The Builder Resolver is a new Ivy resolver that supports downloading, extracting and repackaging (as necessary) artifacts on-demand. It allows for a clearer separation between two jobs which don't necessarily go together: maintaining Ivy meta-data, and hosting the actual artifacts. In addition, it's easy to use the builder resolver to build a normal repository containing artifacts. The most important aspect of this new resolver is that it makes it much easier to create and maintain a public Ivy repository, something that IMHO is sorely lacking right now. And the Ivy RoundUp project is already doing just that (note Ivy RoundUp is a completely separate project from ivy itself). Some links... * Builder resolver patch<http://ivyroundup.googlecode.com/svn/wiki/files/builder-resolver.patch> * Builder resolver documentation<http://ivyroundup.googlecode.com/svn/wiki/files/builder.html> * Ivy RoundUp project <http://code.google.com/p/ivyroundup/> This has also been discussed recently in a couple of threads (here<http://www.nabble.com/Ivy-RoundUp-Repository---feedback-requested-td16704469.html>and here <http://www.nabble.com/Open-source-ivy-files-project--to16437122.html> ). Thanks for your feedback. -Archie -- Archie L. Cobbs |
|
|
Re: Including builder resolver in ivyOn Mon, May 5, 2008 at 7:04 PM, Archie Cobbs <archie@...> wrote:
> I'd like to propose that the new "builder" resolver be included in ivy. In > order to do this however, other developers need to vote yes or no. So I'd > ask that you please let the list know your opinion. > > Quick summary: > > The Builder Resolver is a new Ivy resolver that supports downloading, > extracting and repackaging (as necessary) artifacts on-demand. It allows > for > a clearer separation between two jobs which don't necessarily go together: > maintaining Ivy meta-data, and hosting the actual artifacts. In addition, > it's easy to use the builder resolver to build a normal repository > containing artifacts. > > The most important aspect of this new resolver is that it makes it much > easier to create and maintain a public Ivy repository, something that IMHO > is sorely lacking right now. And the Ivy RoundUp project is already doing > just that (note Ivy RoundUp is a completely separate project from ivy > itself). > > Some links... > > * Builder resolver > patch< > http://ivyroundup.googlecode.com/svn/wiki/files/builder-resolver.patch> > * Builder resolver > documentation<http://ivyroundup.googlecode.com/svn/wiki/files/builder.html > > > * Ivy RoundUp project <http://code.google.com/p/ivyroundup/> > > This has also been discussed recently in a couple of threads > (here< > http://www.nabble.com/Ivy-RoundUp-Repository---feedback-requested-td16704469.html > >and > here <http://www.nabble.com/Open-source-ivy-files-project--to16437122.html > > > ). > > Thanks for your feedback. I'm +1 to include this in Ivy core. The patch is well written, documented and tested. More importantly, I think the work Archie has began on the Ivy roundup repository will be a great asset for the community, if enough people start using it. Integrating the builder resolver in Ivy core will help drive adoption of this new repository IMO. The only thing I dislike with this resolver is its name. The 'builder' name makes people think this resolver compiles modules, while it just repackage them if necessary. Hence I prefer to use another name. Xavier > > > -Archie > > -- > Archie L. Cobbs > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ |
|
|
Re: Including builder resolver in ivyRE "Builder": it just struck me that this resolver is
sort of a decorator over existing URL functionality. What about [Decorator|Decorated]Resolver? -Matt --- Xavier Hanin <xavier.hanin@...> wrote: > On Mon, May 5, 2008 at 7:04 PM, Archie Cobbs > <archie@...> wrote: > > > I'd like to propose that the new "builder" > resolver be included in ivy. In > > order to do this however, other developers need to > vote yes or no. So I'd > > ask that you please let the list know your > opinion. > > > > Quick summary: > > > > The Builder Resolver is a new Ivy resolver that > supports downloading, > > extracting and repackaging (as necessary) > artifacts on-demand. It allows > > for > > a clearer separation between two jobs which don't > necessarily go together: > > maintaining Ivy meta-data, and hosting the actual > artifacts. In addition, > > it's easy to use the builder resolver to build a > normal repository > > containing artifacts. > > > > The most important aspect of this new resolver is > that it makes it much > > easier to create and maintain a public Ivy > repository, something that IMHO > > is sorely lacking right now. And the Ivy RoundUp > project is already doing > > just that (note Ivy RoundUp is a completely > separate project from ivy > > itself). > > > > Some links... > > > > * Builder resolver > > patch< > > > > > * Builder resolver > > > documentation<http://ivyroundup.googlecode.com/svn/wiki/files/builder.html > > > > > * Ivy RoundUp project > <http://code.google.com/p/ivyroundup/> > > > > This has also been discussed recently in a couple > of threads > > (here< > > > http://www.nabble.com/Ivy-RoundUp-Repository---feedback-requested-td16704469.html > > >and > > here > <http://www.nabble.com/Open-source-ivy-files-project--to16437122.html > > > > > ). > > > > Thanks for your feedback. > > > I'm +1 to include this in Ivy core. The patch is > well written, documented > and tested. More importantly, I think the work > Archie has began on the Ivy > roundup repository will be a great asset for the > community, if enough people > start using it. Integrating the builder resolver in > Ivy core will help drive > adoption of this new repository IMO. > > The only thing I dislike with this resolver is its > name. The 'builder' name > makes people think this resolver compiles modules, > while it just repackage > them if necessary. Hence I prefer to use another > name. > > Xavier > > > > > > > -Archie > > > > -- > > Archie L. Cobbs > > > > > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Including builder resolver in ivyOn Tue, May 6, 2008 at 11:27 AM, Xavier Hanin <xavier.hanin@...>
wrote: > > I'd like to propose that the new "builder" resolver be included in ivy. > In > > order to do this however, other developers need to vote yes or no. So > I'd > > ask that you please let the list know your opinion. > > The only thing I dislike with this resolver is its name. The 'builder' > name > makes people think this resolver compiles modules, while it just repackage > them if necessary. Hence I prefer to use another name. > Another possible name that might better convey what it does is "Extractor Resolver". I don't really have any strong preference on the name though. Thanks, -Archie -- Archie L. Cobbs |
|
|
Re: Including builder resolver in ivyLe 6 mai 08 à 18:27, Xavier Hanin a écrit : > On Mon, May 5, 2008 at 7:04 PM, Archie Cobbs <archie@...> > wrote: > >> I'd like to propose that the new "builder" resolver be included in >> ivy. In >> order to do this however, other developers need to vote yes or no. >> So I'd >> ask that you please let the list know your opinion. >> >> Quick summary: >> >> The Builder Resolver is a new Ivy resolver that supports downloading, >> extracting and repackaging (as necessary) artifacts on-demand. It >> allows >> for >> a clearer separation between two jobs which don't necessarily go >> together: >> maintaining Ivy meta-data, and hosting the actual artifacts. In >> addition, >> it's easy to use the builder resolver to build a normal repository >> containing artifacts. >> >> The most important aspect of this new resolver is that it makes it >> much >> easier to create and maintain a public Ivy repository, something >> that IMHO >> is sorely lacking right now. And the Ivy RoundUp project is >> already doing >> just that (note Ivy RoundUp is a completely separate project from ivy >> itself). >> >> Some links... >> >> * Builder resolver >> patch< >> http://ivyroundup.googlecode.com/svn/wiki/files/builder-resolver.patch >> > >> * Builder resolver >> documentation<http://ivyroundup.googlecode.com/svn/wiki/files/builder.html >>> >> * Ivy RoundUp project <http://code.google.com/p/ivyroundup/> >> >> This has also been discussed recently in a couple of threads >> (here< >> http://www.nabble.com/Ivy-RoundUp-Repository---feedback-requested-td16704469.html >>> and >> here <http://www.nabble.com/Open-source-ivy-files-project--to16437122.html >>> >> ). >> >> Thanks for your feedback. > > > I'm +1 to include this in Ivy core. The patch is well written, > documented > and tested. More importantly, I think the work Archie has began on > the Ivy > roundup repository will be a great asset for the community, if > enough people > start using it. Integrating the builder resolver in Ivy core will > help drive > adoption of this new repository IMO. For the same reasons I am in favor of adding it. I have though some worries about adding new features, as I don't manage to have a global and comprehensive view of every Ivy features. On the other way I see that Archie is very active on Ivy, so I am confident about the maintenance of this component. So +1 for me. Nicolas > The only thing I dislike with this resolver is its name. The > 'builder' name > makes people think this resolver compiles modules, while it just > repackage > them if necessary. Hence I prefer to use another name. > > Xavier > >> >> >> -Archie >> >> -- >> Archie L. Cobbs >> > > > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Including builder resolver in ivyLe 6 mai 08 à 18:43, Archie Cobbs a écrit : > On Tue, May 6, 2008 at 11:27 AM, Xavier Hanin <xavier.hanin@...> > wrote: > >>> I'd like to propose that the new "builder" resolver be included in >>> ivy. >> In >>> order to do this however, other developers need to vote yes or no. >>> So >> I'd >>> ask that you please let the list know your opinion. >> >> The only thing I dislike with this resolver is its name. The >> 'builder' >> name >> makes people think this resolver compiles modules, while it just >> repackage >> them if necessary. Hence I prefer to use another name. >> > > Another possible name that might better convey what it does is > "Extractor > Resolver". > > I don't really have any strong preference on the name though. From the IvyRoundUp documentation: Athough named the "builder" resolver, the only build operations currently supported are extracting files from archives, packaging files into archives, and moving and copying files. In the future more general build operations may be supported, once appropriate security controls are in place. So I would say that it is *packaging* modules into an Ivy publishable structure. A packaging process that can, for some module just do some copy, jar and unjar, and for others some possible call to javac. Then I am in favor of renaming it PackagerResolver. Nicolas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: Including builder resolver in ivyOn Wed, May 7, 2008 at 6:40 AM, Nicolas Lalevée <nicolas.lalevee@...>
wrote: > So I would say that it is *packaging* modules into an Ivy publishable > structure. A packaging process that can, for some module just do some copy, > jar and unjar, and for others some possible call to javac. > > Then I am in favor of renaming it PackagerResolver. > I like this name too. Any objections to renaming it "Packager Resolver" ? If not, I'll go ahead and update the patch and docs. Let me know before tomorrow if possible. Thanks, -Archie -- Archie L. Cobbs |
|
|
Re: Including builder resolver in ivyOn Wed, May 7, 2008 at 9:05 AM, Archie Cobbs <archie@...> wrote:
> On Wed, May 7, 2008 at 6:40 AM, Nicolas Lalevée < > nicolas.lalevee@...> wrote: > >> So I would say that it is *packaging* modules into an Ivy publishable >> structure. A packaging process that can, for some module just do some copy, >> jar and unjar, and for others some possible call to javac. >> >> Then I am in favor of renaming it PackagerResolver. >> > > I like this name too. Any objections to renaming it "Packager Resolver" ? > > If not, I'll go ahead and update the patch and docs. Let me know before > tomorrow if possible. > OK the name has been changed to "packager resolver" and the Ivy RoundUp repository site (which also hosts the ivy patch file) has been updated. Thanks, -Archie -- Archie L. Cobbs |
| Free Forum Powered by Nabble | Forum Help |