> -----Original Message----- > From: Martin Skopp [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 8:40 AM > To: Maven Developers List > Subject: Re: Deploy API (artifact plugin) > > On Wed, 2003-06-25 at 15:20, Michal Maczka wrote: > > I have progressed with Deployer API. > > Wow, that *really* looks good... > > > #list of repositories to which we will deploy > > maven.repo.repos= R1, R2, R3, R4, ibiblio > > Is there really need for this property? > I am just afraid of users forgetting to add to this property which will > raise question on the mailinglist.... > > Possible reaons from my point of view: > > a) convenience for Michal :-) > He does not need to loop over all properties check for a maven.repo.* > match... >
I think that looping over project properties is quite dangerous. If you use project inheritance, sometimes you might be interested in overriding some properties of parent project. In this case you cannot switch off any repository defined in parent project, And you should not be aware of them. But you are 100% right that it should be simpler. That's why I asked for comments, hoping that somebody will have an idea how to simplify. BTW: It's even more complicated then I have described last time. Silently I assume existence of default (central repository). Some setting of this repository are matching </distributionDirectory> </distributionSite> Tags in POM This repository is silently named "central". It's clear that in POM there is no place for some properties of this repository (like username, password, passpharse of private key, proxy host etc). Other settings used this repository are currently described in (BTW: why they are there? It's very hard to find them!) http://maven.apache.org/reference/plugins/jar/properties.html Namely: maven.repo.central maven.repo.central.directory maven.username maven.remote.group I will try to hack my code to make it backward compatible ... but among those settings you won't find e.g. user's password. I need to know it. :( For the moment using my (poor!!) naming convention you can use: #(don't have to use it if tag </distributionSite> was used in POM maven.repo.central=www.apache.org #(don't have to use it if tag </distributionSite> was used) maven.repo.central.directory= maven.repo.central.username maven.repo.central.group maven.repo.central.password maven.repo.central.passphrase maven.repo.central.privatekey maven.repo.central.port maven.repo.central.proxy.host maven.repo.central.proxy.port maven.repo.central.proxy.username maven.repo.central.proxy.password I think that it is more consistent...but way too complicated. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
