RE: Deploy API (artifact plugin)

2003-06-30 Thread Michal Maczka
> -Original Message- > From: Rafal Krzewski [mailto:[EMAIL PROTECTED] > Sent: Monday, June 30, 2003 11:17 AM > To: Maven Developers List > Subject: Re: Deploy API (artifact plugin) > > Michal Maczka wrote: > > > For the moment I have tested my API with us

Re: Deploy API (artifact plugin)

2003-06-30 Thread Rafal Krzewski
Michal Maczka wrote: > For the moment I have tested my API with username, user password > kept in properties file. I think such approach is not acceptable. > > You can use command line to pass properties to maven: > > maven war:deloy -Dmaven.repo.ibiblio.password = ** > > This is already

RE: Deploy API (artifact plugin)

2003-06-29 Thread dion
http://www.multitask.com.au Michal Maczka <[EMAIL PROTECTED]> wrote on 27/06/2003 06:12:25 PM: > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Friday, June 27, 2003 6:16 AM > > To: Maven Developers Lis

RE: Deploy API (artifact plugin)

2003-06-27 Thread Michal Maczka
> > > I would avoid the command line passed password. It is much less secure > on unix than the password kept in a file. Command line can be seen by > simple ps commands, or e.g. linux systems store the in the /proc > filesystem. > It should be used only from command files. > > incze > I want to

Re: Deploy API (artifact plugin)

2003-06-27 Thread Incze Lajos
> BTW: > > For the moment I have tested my API with username, user password > kept in properties file. I think such approach is not acceptable. > > You can use command line to pass properties to maven: > > maven war:deloy -Dmaven.repo.ibiblio.password = ** > > > This is already better

RE: Deploy API (artifact plugin)

2003-06-27 Thread Michal Maczka
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, June 27, 2003 6:16 AM > To: Maven Developers List > Subject: RE: Deploy API (artifact plugin) > > I think I've asked this before, but AFAIK, > > distribut

RE: Deploy API (artifact plugin)

2003-06-26 Thread Martin Skopp
On Thu, 2003-06-26 at 10:44, Michal Maczka wrote: > 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

RE: Deploy API (artifact plugin)

2003-06-26 Thread dion
ROTECTED]> wrote on 26/06/2003 06:44:19 PM: > > > > -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) > >

RE: Deploy API (artifact plugin)

2003-06-26 Thread Michal Maczka
> -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

Re: Deploy API (artifact plugin)

2003-06-25 Thread Martin Skopp
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 ad

Re: Deploy API (artifact plugin)

2003-06-25 Thread Rafal Krzewski
Michal Maczka wrote: > I have progressed with Deployer API. Good to hear that. Incosistency among plugins in this regard was a big drawback IMO. Everything looks good, but... #list of repositories to which we will deploy maven.repo.repos= R1, R2, R3, R4, ibiblio ^ maven.repo.lis

Deploy API (artifact plugin)

2003-06-25 Thread Michal Maczka
I have progressed with Deployer API. To make it clear - we have actually 3 types of repositories: local (single instance) remote-readonly remote-writable Maven can now deploy to many remote repositories. Deployers are just simple one shoot file copiers - See: org.apache.maven.deploy.