rojects to C/C++ Projects and adding
> Axis/CPP there.
>
> Nadir Amra
>
>
> Chanaka Jayasena wrote on 01/17/2011 03:35:02 AM:
>
> > From: Chanaka Jayasena
> > To: [email protected]
> > Date: 01/17/2011 03:35 AM
> > Subject: Re: Axis Website
[email protected]
> Date: 01/17/2011 03:35 AM
> Subject: Re: Axis Website update
>
> Hi all,
>
> I created a new design for axis.apache.org site, with a bit
> different look and feeling. Sample screen is available at [1], and
> the JIRA created for the improvement is [2]. Shall we
Hi all,
I created a new design for axis.apache.org site, with a bit different look
and feeling. Sample screen is available at [1], and the JIRA created for the
improvement is [2]. Shall we replace the existing design with this one?
1. https://issues.apache.org/jira/secure/attachment/12468538/fanc
t is definitely not flexible enough for some type of content (e.g.
>>> >> tutorials). Some time ago there was a discussion about this and the
>>> >> consensus is that we need something else (which would be in addition
>>> >> to the Maven sites, at least
(which would be in addition
>> >> to the Maven sites, at least during a transition phase) that would
>> >> allow to publish content with a simpler procedure. At that time,
>> >> Confluence (with the auto-export plugin) was the only CMS available
>> >&g
e. At that time,
> >> Confluence (with the auto-export plugin) was the only CMS available
> >> and I like that system, although it's not perfect. However, the future
> >> of this at the ASF is uncertain because the infra team would like to
> >> get rid o
t with a simpler procedure. At that time,
>>> Confluence (with the auto-export plugin) was the only CMS available
>>> and I like that system, although it's not perfect. However, the future
>>> of this at the ASF is uncertain because the infra team would like to
>
simpler procedure. At that time,
>> Confluence (with the auto-export plugin) was the only CMS available
>> and I like that system, although it's not perfect. However, the future
>> of this at the ASF is uncertain because the infra team would like to
>> get rid of it in fav
t; Confluence (with the auto-export plugin) was the only CMS available
>> and I like that system, although it's not perfect. However, the future
>> of this at the ASF is uncertain because the infra team would like to
>> get rid of it in favor of their own custom built solutio
mra
> >
> >
> > Andreas Veithen wrote on 12/27/2010 11:04:50
> AM:
> >
> >> From: Andreas Veithen
> >> To: [email protected]
> >> Date: 12/27/2010 11:07 AM
> >> Subject: Re: Axis Website update
> >>
> >>
in favor of their own custom built solution.
> Nadir Amra
>
>
> Andreas Veithen wrote on 12/27/2010 11:04:50 AM:
>
>> From: Andreas Veithen
>> To: [email protected]
>> Date: 12/27/2010 11:07 AM
>> Subject: Re: Axis Website update
>>
>> The
ct: Re: Axis Website update
>
> The changes for AXIS2-4912 were applied to the site sources in the
> trunk. That was after I prepared the 1.5.4 release. The site currently
> online is the one generated from the 1.5.4 release and therefore
> doesn't contain these changes. The normal way
The changes for AXIS2-4912 were applied to the site sources in the
trunk. That was after I prepared the 1.5.4 release. The site currently
online is the one generated from the 1.5.4 release and therefore
doesn't contain these changes. The normal way to get them published is
with the next release. If
Chanaka had submitted a few site patches, and I think these have been
committed to the SVN. If so, why hasn't the site
http://axis.apache.orgstill been updated?
--
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**ht
14 matches
Mail list logo
