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 better
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 in
-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,
distributionSiteare not related AT ALL to
maven.repo.central
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 ... but
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 support
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
-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
