On Jul 6, 2013, at 5:32 PM, Henri Yandell wrote:
> On Tue, Jul 2, 2013 at 8:43 PM, Jeremy Boynes wrote:
> On Jul 2, 2013, at 9:41 AM, Henri Yandell wrote:
>>>
>>> I wouldn't expect to deploy the site from tags - a site is a live/current
>>> thing.
>>
>> The core site is a live/current thing, b
On Tue, Jul 2, 2013 at 8:43 PM, Jeremy Boynes wrote:
> On Jul 2, 2013, at 9:41 AM, Henri Yandell wrote:
> >
> > I wouldn't expect to deploy the site from tags - a site is a live/current
> > thing.
>
> The core site is a live/current thing, but there is also the
> documentation/reports etc. that
On Jul 2, 2013, at 9:41 AM, Henri Yandell wrote:
>
> I wouldn't expect to deploy the site from tags - a site is a live/current
> thing.
The core site is a live/current thing, but there is also the
documentation/reports etc. that would be associated with a specific tag. IOW,
the site could cont
On Mon, Jul 1, 2013 at 3:04 AM, Olivier Lamy wrote:
> Apologize for delayed response.
>
> 2013/6/26 Jeremy Boynes :
> > On Jun 25, 2013, at 7:54 AM, Henri Yandell wrote:
> >
> >> Help much appreciated - but do we want all the content of all the
> modules
> >> to be there?
> >>
> >> It feels to m
Apologize for delayed response.
2013/6/26 Jeremy Boynes :
> On Jun 25, 2013, at 7:54 AM, Henri Yandell wrote:
>
>> Help much appreciated - but do we want all the content of all the modules
>> to be there?
>>
>> It feels to me that the website does not map directly to the codebase. We
>> want an o
On Jun 25, 2013, at 7:54 AM, Henri Yandell wrote:
> Help much appreciated - but do we want all the content of all the modules
> to be there?
>
> It feels to me that the website does not map directly to the codebase. We
> want an overall site, and subsites for Standard and for RDC. We don't want
Help much appreciated - but do we want all the content of all the modules
to be there?
It feels to me that the website does not map directly to the codebase. We
want an overall site, and subsites for Standard and for RDC. We don't want
to have the 14 pom.xmls become a site structure, or the 4 pom.
Hi,
Can be easy :-)
mvn site site:stage and all the content of all modules will be in
${project.build.directory}/staging (target/staging).
But to achieve this and having something easy we must the site module
on the top!
Means here http://svn.apache.org/repos/asf/tomcat/taglibs/trunks/
As we don't
FYI that I'm digging into the Taglibs site to figure out how it is we go
from 15 Maven target/site directories to 1 site.
I'm then going to write a dumb shell script that copies the relevant parts
to a Tomcat site/taglibs checkout, allowing for the site to be updated. I'm
sure there's a very cleve
