> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 20, 2003 6:12 AM
> To: Maven Developers List
> Subject: Re: RFC: Deployer properties
>
> "Michal Maczka" <[EMAIL PROTECTED]> wrote on 19/06/2003 10
"Michal Maczka" <[EMAIL PROTECTED]> wrote on 19/06/2003 10:48:48 PM:
> Please comment this:
>
>
> With new deployer API I am going to support deployment to many remote
> repositories.
> In reality many = 2 in most of the cases. But 2>1 ..
>
> I am proposing to use following properties:
>
> #th
Looks good. A few questions:
maven.repo.repo1.remote.group= goo
Is remote.group really needed? How is this different to pom.groupId?
maven.deploy.repo.ibiblio = http://www.ibiblio.org
maven.deploy.repo.ibiblio.directory = /maven
Is the extra deploy here a typo? If it is something different, what
Please comment this:
With new deployer API I am going to support deployment to many remote
repositories.
In reality many = 2 in most of the cases. But 2>1 ..
I am proposing to use following properties:
#the list of repositories. repo1, repo2 are aliases or nicknames of
repositories
maven.deploy
With new deployer API I am going to support deployment to many remote
repsoitories.
In reality many = 2 in most of the cases. But 2>1 ..
I am proposiing to use follwoing properties:
#the list of repositories. repo1, repo2 are aliases or nicknames of
repositories
maven.repo.deploy = repo1, repo2
