distributionSite and distributionDirectory are used for 'publishing' the 
generated site and other artifacts, the central repo is a global space 
where many projects artifacts are published.
--
dIon Gillard, Multitask Consulting
Blog:      http://blogs.codehaus.org/people/dion/
Work:      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 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.
> > 
> 
> 
> Last time you asked:
> 
> "
> >   <siteAddress>maven.apache.org</siteAddress>
> >   <siteDirectory>/www/maven.apache.org/</siteDirectory>
> This is the web site address and directory, not a repo???"
> 
> :)
> 
> I was sure that you just wanted to get sure that I use distributionSite 
and
> distributionDirectory.
> 
> 
> 
> distributionSite is not described in
> http://maven.apache.org/reference/project-descriptor.html
> 
> 
> While
> distributionDirectory:
> 
> Optional. The directory on the web server where the final distributions 
will
> be published. This is used when the distributions are deployed 
> 
> (the word deployed is a hyper link which points to "site" plugin)
> 
> 
> I though that "final distributions" are the distribution of artifacts
> delivered by projects: jars, javadoc, project src zipped, 
> 
> Now I see I finaly understand that you might want e.g to publish
> "distribution" of 
> entire project at sourceforge... and not to deploy to any repository.
> 
> 
> 
> If I am still wrong: can you then explain briefly the difference?
> 
> I want to centralized the code which does remote copying of the files
> And I see now that "distribution" requires special handling ...  I 
will/want
> to change my code to support it. 
> 
> 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 still not perfect.
> 
> I will try to implement/use(if I find one) simple "Prompter" which will 
ask
> to type your password (eventually to enter other required parameters 
which
> are missing)
> 
> regards
> 
> 
> Michal
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

Reply via email to