Re: Listing remote repositories ´artifacts

[di...@multitask.com.au]

Not yet....
--
dIon Gillard, Multitask Consulting
Blog:      http://www.freeroller.net/page/dion/Weblog
Work:      http://www.multitask.com.au


"Paulo Silveira" <pa...@paulo.com.br> wrote on 11/04/2003 01:03:42 PM:

> Hello
> 
> Somtimes I have to go to ibiblio/maven to check out if an artifact
> already exists over there.
> Is there any maven blah:blah that lists all artifacts in my remote
> repositories? 
> 
> Thanks
> 
> ------------------------
> Paulo Silveira
> http://www.paulo.com.br/
> http://www.guj.com.br/
> 
> 
> > -----Original Message-----
> > From: Ben Walding [mailto:default0001@walding.com] 
> > Sent: sexta-feira, 11 de abril de 2003 04:58
> > To: Maven Users List
> > Subject: Re: CVS checkouts in Maven
> > 
> > 
> > Do not confuse what maven does with what Maven products do.
> > 
> > Or to be more explicit,  maven is just a build tool (a highly 
> > sophisticated build tool that also produces deliverables and 
> > encourages 
> > "best practices").  What will ultimately be created is a continuous 
> > integration tool that is maven aware.  This tool would not be part of 
> > maven, but it would be part of Maven group of products. 
> > 
> > eg. overlord is not part of maven, but it is to be part of the Maven 
> > group of products.
> > 
> > 
> > Theory A: That being said, maybe if on build failure, a build:failure 
> > goal was run, then we could hook goals off that. And orthogonally a 
> > build:success was run.
> > 
> > Theory B:
> > After thinking about theory A, we need to think about the fact that 
> > there is a build:start hidden away but disabled.  Orthogonally, there 
> > should be build:end, one could hook onto that and determine the build 
> > status and do things at that point.
> > 
> > 
> > 
> > I ultimately see an orchestra of Maven products working in harmony to 
> > produce a symphony of software.
> > 
> > Shoot me now.
> > 
> > 
> > Lester Ward wrote:
> > 
> > >>there is nothing inherent in Maven for
> > >>sending messages upon a failed build. That's not Maven's concern.
> > >> 
> > >>
> > >
> > >You could argue that it should be, depending on your 
> > interpretation of 
> > >the stated goal of "making the build process easy". I think 
> > that what 
> > >some (maybe many) people want to do with Maven is automate a 
> > periodic 
> > >(probably
> > >daily) build process. That is certainly what I am doing and, 
> > I suspect, what
> > >the original poster was getting at as well.
> > >
> > >An automated build system needs both of the things the 
> > original poster
> > >mentioned: CVS checkouts and e-mail notification, something 
> > that Maven 
> > >does not consider part of its standard build process.
> > >
> > >Naturally, both of these actions can be scripted into a 
> > build process, 
> > >so I can also see the argument that Maven .shouldn't. have these 
> > >features built-in. Still, one of the main concepts behind 
> > Maven that I 
> > >remember hearing is that Maven tries to take what you would 
> > normally do 
> > >in 20 lines of code and do it in zero. It seems to me like, 
> > since most 
> > >of the information you need is already in the project.xml 
> > file, adding 
> > >auto CVS checkout for your own project and e-mail notification on 
> > >failure (driven by properties that default to off) would not 
> > be a huge 
> > >deal to put into Maven.
> > >
> > >Having these features built into Maven would basically eliminate the 
> > >need for the maven.xml files in nearly all of my Mavenized 
> > projects, as 
> > >generally the only thing I use maven.xml for is to do a CVS update 
> > >before compilation.
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > >For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > 
> > >
> > 
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> > 
> > 
> > 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org