maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <and...@hammar.net>
Subject Re: Maven Site Repository
Date Tue, 30 Nov 2010 18:55:29 GMT
Yes, using the maven site feature of Nexus Pro makes it one place less to
manage authorization (compared to having a separate web server).

/Anders

On Tue, Nov 30, 2010 at 18:03, Ron Wheeler
<rwheeler@artifact-software.com>wrote:

> Our artifacts go In our internal Nexus repo.
>
> Ron
>
>
> On 30/11/2010 11:42 AM, Mike Lenner wrote:
>
>> What are common practices in terms of where to deploy maven sites to?
>> I'm specifically asking for projects built internally within a company
>> (i.e. only available to internal users).  Initially I thought that our
>> artifact repository itself would be a logical place but that doesn't
>> seem to be a common practice.  Right now we're leveraging the
>> workspace used by Hudson when it executes it's CI build (navigating to
>> the target/site/ folder).  Do people just set up a standalone
>> webserver for this explicit purpose?
>>
>> Thanks,
>> Mike
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message