You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Afkham Azeez <af...@gmail.com> on 2010/12/26 06:51:50 UTC
Axis Website update
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;
**http://www.apache.org/*<http://www.apache.org/>
*
email: **azeez@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
*
*
Re: Axis Website update
Posted by Chanaka Jayasena <ch...@wso2.com>.
Thanks for the suggestion Nadir. I will take this in to account when
converting this to html.
Chanak
On Tue, Jan 18, 2011 at 1:51 AM, Nadir Amra <am...@us.ibm.com> wrote:
> Chanaka,
>
> Looks good, but Axis CPP, which generates c and C++ stubs, is not a Jjava
> project. I would suggest changing C Projects to C/C++ Projects and adding
> Axis/CPP there.
>
> Nadir Amra
>
>
> Chanaka Jayasena <ch...@wso2.com> wrote on 01/17/2011 03:35:02 AM:
>
> > From: Chanaka Jayasena <ch...@wso2.com>
> > To: java-dev@axis.apache.org
> > 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 replace the
> > existing design with this one?
> >
> > 1.
> https://issues.apache.org/jira/secure/attachment/12468538/fancydesign.png
> > 2. https://issues.apache.org/jira/browse/AXIS-2836
> >
> > thanks,
> > Chanaka
>
Re: Axis Website update
Posted by Nadir Amra <am...@us.ibm.com>.
Chanaka,
Looks good, but Axis CPP, which generates c and C++ stubs, is not a Jjava
project. I would suggest changing C Projects to C/C++ Projects and adding
Axis/CPP there.
Nadir Amra
Chanaka Jayasena <ch...@wso2.com> wrote on 01/17/2011 03:35:02 AM:
> From: Chanaka Jayasena <ch...@wso2.com>
> To: java-dev@axis.apache.org
> 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 replace the
> existing design with this one?
>
> 1.
https://issues.apache.org/jira/secure/attachment/12468538/fancydesign.png
> 2. https://issues.apache.org/jira/browse/AXIS-2836
>
> thanks,
> Chanaka
Re: Axis Website update
Posted by Chanaka Jayasena <ch...@wso2.com>.
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/fancydesign.png
2. https://issues.apache.org/jira/browse/AXIS-2836
thanks,
Chanaka
Re: Axis Website update
Posted by Chanaka Jayasena <ch...@wso2.com>.
Sure Ruwan I will join the hackathon tomorrow.
I updated the patch with Axis2 Transports link.
thanks,
Chanaka
On Tue, Jan 4, 2011 at 8:44 PM, Ruwan Linton <ru...@gmail.com> wrote:
> +1. Chanaka, shall we do this as a part of the Axis2 hackathon tomorrow?
>
> Axis main site anyway needs an update. Please note that we need to add a
> link to the Axis2 Transports from the main page as well. I don't see it on
> the image.
>
> Thanks,
> Ruwan
>
> On Tue, Jan 4, 2011 at 5:24 PM, Chanaka Jayasena <ch...@wso2.com> wrote:
>
>> I provided with a patch (AXIS2-4911) to update the axis.apache.org during
>> the last Axis2 Hackathon. Following is a screen shot of the page design.
>> https://issues.apache.org/jira/secure/attachment/12467409/screen.png
>>
>> If no one disagrees, shall we please update the site in to this?
>>
>> I also submitted patches for
>>
>> [1] Axis2 Java site - http://axis.apache.org/axis2/java/core/
>> (AXIS2-4912)
>>
>> [2] Apache Rampart - http://axis.apache.org/axis2/java/rampart/
>> (RAMPART-313)
>>
>> [3] Apache Sandesha - http://axis.apache.org/axis2/java/sandesha/(SANDESHA2-206)
>>
>> thanks,
>> Chanaka
>>
>>
>> On Tue, Dec 28, 2010 at 3:30 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> Yes,
>>> http://axis.apache.org/axis2?/(java|c)/(core|rampart|sandesha|savan|transports)<http://axis.apache.org/axis2?/(java%7Cc)/(core%7Crampart%7Csandesha%7Csavan%7Ctransports)>
>>> are generated sites, while the rest (in particular the home page at
>>> http://axis.apache.org) should eventually be published using some
>>> other means. Glen added a static index.html to the root, but this is
>>> not under version control; it only exists at
>>> people.apache.org:/www/axis.apache.org.
>>>
>>> Andreas
>>>
>>> On Tue, Dec 28, 2010 at 05:25, Afkham Azeez <af...@gmail.com> wrote:
>>> > I think we should be able to modify at least certain pages independent
>>> of
>>> > the latest release. For example, the home
>>> > page http://axis.apache.org/ looks so dull & incomplete. Chanaka had
>>> > prepared nicer looking pages with the projects logos and so on. We
>>> certainly
>>> > need to update that page at least.
>>> > Thanks
>>> > Azeez
>>> >
>>> > On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen <
>>> andreas.veithen@gmail.com>
>>> > wrote:
>>> >>
>>> >> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
>>> >> > So then updates to the site can only be done on a release boundary?
>>> >>
>>> >> The basic constraint is to maintain consistency between the published
>>> >> site and the site sources. In practice this indeed means that the site
>>> >> is only refreshed during a release. However:
>>> >>
>>> >> * One can do manual edits to the generated site, provided that the
>>> >> site sources are also updated (so that the updates are not lost when
>>> >> the site is regenerated). I did that with the Axis2 site in order to
>>> >> fix a couple of broken links after the 1.5.3 release. Unfortunately
>>> >> people tend to forget to update the site sources, leaving it to other
>>> >> people to clean up the mess when doing a new release (see r1042149 and
>>> >> r1042163).
>>> >> * Technically, nothing would prevent us from republishing the site
>>> >> from the trunk without doing a release. However, this means that the
>>> >> site may contain information (e.g. in the Javadoc) that is not
>>> >> applicable to any release. Also, I don't know any project at the ASF
>>> >> that does this.
>>> >>
>>> >> > If true, that does not seem too flexible, does it?
>>> >>
>>> >> Maven sites are fine for some type of documentation (such as Javadoc,
>>> >> reference documentation or information that doesn't change much), but
>>> >> it 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 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
>>> >> 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 solution.
>>> >>
>>> >> > Nadir Amra
>>> >> >
>>> >> >
>>> >> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010
>>> 11:04:50
>>> >> > AM:
>>> >> >
>>> >> >> From: Andreas Veithen <an...@gmail.com>
>>> >> >> To: java-dev@axis.apache.org
>>> >> >> Date: 12/27/2010 11:07 AM
>>> >> >> Subject: 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 to get them published
>>> is
>>> >> >> with the next release. If that is 1.6, then the changes will be
>>> >> >> included automatically. If the next release is 1.5.5, then the site
>>> >> >> changes need to be merged to the 1.5 branch first (I did that for
>>> >> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
>>> >> >> release from the 1.5 branch).
>>> >> >>
>>> >> >> Andreas
>>> >> >>
>>> >> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com>
>>> wrote:
>>> >> >> > 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.org
>>> >> >> > still been updated?
>>> >> >> >
>>> >> >> > --
>>> >> >> > Afkham Azeez
>>> >> >> > Senior Software Architect & Senior Manager; WSO2,
>>> >> >> > Inc.; http://wso2.com,
>>> >> >> >
>>> >> >> > Member; Apache Software Foundation; http://www.apache.org/
>>> >> >> > email: azeez@wso2.com cell: +94 77 3320919
>>> >> >> > blog: http://blog.afkham.org
>>> >> >> > twitter: http://twitter.com/afkham_azeez
>>> >> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>>> >> >> >
>>> >> >> > Lean . Enterprise . Middleware
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >> >>
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Afkham Azeez
>>> > Senior Software Architect & Senior Manager; WSO2, Inc.;
>>> http://wso2.com,
>>> >
>>> > Member; Apache Software Foundation; http://www.apache.org/
>>> > email: azeez@wso2.com cell: +94 77 3320919
>>> > blog: http://blog.afkham.org
>>> > twitter: http://twitter.com/afkham_azeez
>>> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>>> >
>>> > Lean . Enterprise . Middleware
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>
Re: Axis Website update
Posted by Ruwan Linton <ru...@gmail.com>.
+1. Chanaka, shall we do this as a part of the Axis2 hackathon tomorrow?
Axis main site anyway needs an update. Please note that we need to add a
link to the Axis2 Transports from the main page as well. I don't see it on
the image.
Thanks,
Ruwan
On Tue, Jan 4, 2011 at 5:24 PM, Chanaka Jayasena <ch...@wso2.com> wrote:
> I provided with a patch (AXIS2-4911) to update the axis.apache.org during
> the last Axis2 Hackathon. Following is a screen shot of the page design.
> https://issues.apache.org/jira/secure/attachment/12467409/screen.png
>
> If no one disagrees, shall we please update the site in to this?
>
> I also submitted patches for
>
> [1] Axis2 Java site - http://axis.apache.org/axis2/java/core/
> (AXIS2-4912)
>
> [2] Apache Rampart - http://axis.apache.org/axis2/java/rampart/
> (RAMPART-313)
>
> [3] Apache Sandesha - http://axis.apache.org/axis2/java/sandesha/(SANDESHA2-206)
>
> thanks,
> Chanaka
>
>
> On Tue, Dec 28, 2010 at 3:30 PM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> Yes,
>> http://axis.apache.org/axis2?/(java|c)/(core|rampart|sandesha|savan|transports)<http://axis.apache.org/axis2?/(java%7Cc)/(core%7Crampart%7Csandesha%7Csavan%7Ctransports)>
>> are generated sites, while the rest (in particular the home page at
>> http://axis.apache.org) should eventually be published using some
>> other means. Glen added a static index.html to the root, but this is
>> not under version control; it only exists at
>> people.apache.org:/www/axis.apache.org.
>>
>> Andreas
>>
>> On Tue, Dec 28, 2010 at 05:25, Afkham Azeez <af...@gmail.com> wrote:
>> > I think we should be able to modify at least certain pages independent
>> of
>> > the latest release. For example, the home
>> > page http://axis.apache.org/ looks so dull & incomplete. Chanaka had
>> > prepared nicer looking pages with the projects logos and so on. We
>> certainly
>> > need to update that page at least.
>> > Thanks
>> > Azeez
>> >
>> > On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen <
>> andreas.veithen@gmail.com>
>> > wrote:
>> >>
>> >> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
>> >> > So then updates to the site can only be done on a release boundary?
>> >>
>> >> The basic constraint is to maintain consistency between the published
>> >> site and the site sources. In practice this indeed means that the site
>> >> is only refreshed during a release. However:
>> >>
>> >> * One can do manual edits to the generated site, provided that the
>> >> site sources are also updated (so that the updates are not lost when
>> >> the site is regenerated). I did that with the Axis2 site in order to
>> >> fix a couple of broken links after the 1.5.3 release. Unfortunately
>> >> people tend to forget to update the site sources, leaving it to other
>> >> people to clean up the mess when doing a new release (see r1042149 and
>> >> r1042163).
>> >> * Technically, nothing would prevent us from republishing the site
>> >> from the trunk without doing a release. However, this means that the
>> >> site may contain information (e.g. in the Javadoc) that is not
>> >> applicable to any release. Also, I don't know any project at the ASF
>> >> that does this.
>> >>
>> >> > If true, that does not seem too flexible, does it?
>> >>
>> >> Maven sites are fine for some type of documentation (such as Javadoc,
>> >> reference documentation or information that doesn't change much), but
>> >> it 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 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
>> >> 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 solution.
>> >>
>> >> > Nadir Amra
>> >> >
>> >> >
>> >> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010
>> 11:04:50
>> >> > AM:
>> >> >
>> >> >> From: Andreas Veithen <an...@gmail.com>
>> >> >> To: java-dev@axis.apache.org
>> >> >> Date: 12/27/2010 11:07 AM
>> >> >> Subject: 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 to get them published
>> is
>> >> >> with the next release. If that is 1.6, then the changes will be
>> >> >> included automatically. If the next release is 1.5.5, then the site
>> >> >> changes need to be merged to the 1.5 branch first (I did that for
>> >> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
>> >> >> release from the 1.5 branch).
>> >> >>
>> >> >> Andreas
>> >> >>
>> >> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com>
>> wrote:
>> >> >> > 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.org
>> >> >> > still been updated?
>> >> >> >
>> >> >> > --
>> >> >> > Afkham Azeez
>> >> >> > Senior Software Architect & Senior Manager; WSO2,
>> >> >> > Inc.; http://wso2.com,
>> >> >> >
>> >> >> > Member; Apache Software Foundation; http://www.apache.org/
>> >> >> > email: azeez@wso2.com cell: +94 77 3320919
>> >> >> > blog: http://blog.afkham.org
>> >> >> > twitter: http://twitter.com/afkham_azeez
>> >> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>> >> >> >
>> >> >> > Lean . Enterprise . Middleware
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >> >>
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Afkham Azeez
>> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com
>> ,
>> >
>> > Member; Apache Software Foundation; http://www.apache.org/
>> > email: azeez@wso2.com cell: +94 77 3320919
>> > blog: http://blog.afkham.org
>> > twitter: http://twitter.com/afkham_azeez
>> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>> >
>> > Lean . Enterprise . Middleware
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
--
Ruwan Linton
Software Architect & Product Manager
WSO2 Inc.; http://wso2.org
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton
Re: Axis Website update
Posted by Chanaka Jayasena <ch...@wso2.com>.
I provided with a patch (AXIS2-4911) to update the axis.apache.org during
the last Axis2 Hackathon. Following is a screen shot of the page design.
https://issues.apache.org/jira/secure/attachment/12467409/screen.png
If no one disagrees, shall we please update the site in to this?
I also submitted patches for
[1] Axis2 Java site - http://axis.apache.org/axis2/java/core/ (AXIS2-4912)
[2] Apache Rampart - http://axis.apache.org/axis2/java/rampart/
(RAMPART-313)
[3] Apache Sandesha - http://axis.apache.org/axis2/java/sandesha/(SANDESHA2-206)
thanks,
Chanaka
On Tue, Dec 28, 2010 at 3:30 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Yes,
> http://axis.apache.org/axis2?/(java|c)/(core|rampart|sandesha|savan|transports)
> are generated sites, while the rest (in particular the home page at
> http://axis.apache.org) should eventually be published using some
> other means. Glen added a static index.html to the root, but this is
> not under version control; it only exists at
> people.apache.org:/www/axis.apache.org.
>
> Andreas
>
> On Tue, Dec 28, 2010 at 05:25, Afkham Azeez <af...@gmail.com> wrote:
> > I think we should be able to modify at least certain pages independent of
> > the latest release. For example, the home
> > page http://axis.apache.org/ looks so dull & incomplete. Chanaka had
> > prepared nicer looking pages with the projects logos and so on. We
> certainly
> > need to update that page at least.
> > Thanks
> > Azeez
> >
> > On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
> >> > So then updates to the site can only be done on a release boundary?
> >>
> >> The basic constraint is to maintain consistency between the published
> >> site and the site sources. In practice this indeed means that the site
> >> is only refreshed during a release. However:
> >>
> >> * One can do manual edits to the generated site, provided that the
> >> site sources are also updated (so that the updates are not lost when
> >> the site is regenerated). I did that with the Axis2 site in order to
> >> fix a couple of broken links after the 1.5.3 release. Unfortunately
> >> people tend to forget to update the site sources, leaving it to other
> >> people to clean up the mess when doing a new release (see r1042149 and
> >> r1042163).
> >> * Technically, nothing would prevent us from republishing the site
> >> from the trunk without doing a release. However, this means that the
> >> site may contain information (e.g. in the Javadoc) that is not
> >> applicable to any release. Also, I don't know any project at the ASF
> >> that does this.
> >>
> >> > If true, that does not seem too flexible, does it?
> >>
> >> Maven sites are fine for some type of documentation (such as Javadoc,
> >> reference documentation or information that doesn't change much), but
> >> it 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 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
> >> 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 solution.
> >>
> >> > Nadir Amra
> >> >
> >> >
> >> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010
> 11:04:50
> >> > AM:
> >> >
> >> >> From: Andreas Veithen <an...@gmail.com>
> >> >> To: java-dev@axis.apache.org
> >> >> Date: 12/27/2010 11:07 AM
> >> >> Subject: 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 to get them published
> is
> >> >> with the next release. If that is 1.6, then the changes will be
> >> >> included automatically. If the next release is 1.5.5, then the site
> >> >> changes need to be merged to the 1.5 branch first (I did that for
> >> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
> >> >> release from the 1.5 branch).
> >> >>
> >> >> Andreas
> >> >>
> >> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com>
> wrote:
> >> >> > 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.org
> >> >> > still been updated?
> >> >> >
> >> >> > --
> >> >> > Afkham Azeez
> >> >> > Senior Software Architect & Senior Manager; WSO2,
> >> >> > Inc.; http://wso2.com,
> >> >> >
> >> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> >> > email: azeez@wso2.com cell: +94 77 3320919
> >> >> > blog: http://blog.afkham.org
> >> >> > twitter: http://twitter.com/afkham_azeez
> >> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
> >> >> >
> >> >> > Lean . Enterprise . Middleware
> >> >> >
> >> >> >
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +94 77 3320919
> > blog: http://blog.afkham.org
> > twitter: http://twitter.com/afkham_azeez
> > linked-in: http://lk.linkedin.com/in/afkhamazeez
> >
> > Lean . Enterprise . Middleware
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Axis Website update
Posted by Andreas Veithen <an...@gmail.com>.
Yes, http://axis.apache.org/axis2?/(java|c)/(core|rampart|sandesha|savan|transports)
are generated sites, while the rest (in particular the home page at
http://axis.apache.org) should eventually be published using some
other means. Glen added a static index.html to the root, but this is
not under version control; it only exists at
people.apache.org:/www/axis.apache.org.
Andreas
On Tue, Dec 28, 2010 at 05:25, Afkham Azeez <af...@gmail.com> wrote:
> I think we should be able to modify at least certain pages independent of
> the latest release. For example, the home
> page http://axis.apache.org/ looks so dull & incomplete. Chanaka had
> prepared nicer looking pages with the projects logos and so on. We certainly
> need to update that page at least.
> Thanks
> Azeez
>
> On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
>> > So then updates to the site can only be done on a release boundary?
>>
>> The basic constraint is to maintain consistency between the published
>> site and the site sources. In practice this indeed means that the site
>> is only refreshed during a release. However:
>>
>> * One can do manual edits to the generated site, provided that the
>> site sources are also updated (so that the updates are not lost when
>> the site is regenerated). I did that with the Axis2 site in order to
>> fix a couple of broken links after the 1.5.3 release. Unfortunately
>> people tend to forget to update the site sources, leaving it to other
>> people to clean up the mess when doing a new release (see r1042149 and
>> r1042163).
>> * Technically, nothing would prevent us from republishing the site
>> from the trunk without doing a release. However, this means that the
>> site may contain information (e.g. in the Javadoc) that is not
>> applicable to any release. Also, I don't know any project at the ASF
>> that does this.
>>
>> > If true, that does not seem too flexible, does it?
>>
>> Maven sites are fine for some type of documentation (such as Javadoc,
>> reference documentation or information that doesn't change much), but
>> it 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 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
>> 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 solution.
>>
>> > Nadir Amra
>> >
>> >
>> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010 11:04:50
>> > AM:
>> >
>> >> From: Andreas Veithen <an...@gmail.com>
>> >> To: java-dev@axis.apache.org
>> >> Date: 12/27/2010 11:07 AM
>> >> Subject: 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 to get them published is
>> >> with the next release. If that is 1.6, then the changes will be
>> >> included automatically. If the next release is 1.5.5, then the site
>> >> changes need to be merged to the 1.5 branch first (I did that for
>> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
>> >> release from the 1.5 branch).
>> >>
>> >> Andreas
>> >>
>> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
>> >> > 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.org
>> >> > still been updated?
>> >> >
>> >> > --
>> >> > Afkham Azeez
>> >> > Senior Software Architect & Senior Manager; WSO2,
>> >> > Inc.; http://wso2.com,
>> >> >
>> >> > Member; Apache Software Foundation; http://www.apache.org/
>> >> > email: azeez@wso2.com cell: +94 77 3320919
>> >> > blog: http://blog.afkham.org
>> >> > twitter: http://twitter.com/afkham_azeez
>> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>> >> >
>> >> > Lean . Enterprise . Middleware
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://blog.afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Axis Website update
Posted by Andreas Veithen <an...@gmail.com>.
It's already mentioned here:
http://axis.apache.org/axis2/java/core/faq.html#a1
On Tue, Dec 28, 2010 at 13:55, Amila Suriarachchi
<am...@gmail.com> wrote:
> please add a nightly build (distribution) location too to the site.
>
> thanks,
> Amila.
>
> On Tue, Dec 28, 2010 at 9:55 AM, Afkham Azeez <af...@gmail.com> wrote:
>>
>> I think we should be able to modify at least certain pages independent of
>> the latest release. For example, the home
>> page http://axis.apache.org/ looks so dull & incomplete. Chanaka had
>> prepared nicer looking pages with the projects logos and so on. We certainly
>> need to update that page at least.
>> Thanks
>> Azeez
>>
>> On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen
>> <an...@gmail.com> wrote:
>>>
>>> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
>>> > So then updates to the site can only be done on a release boundary?
>>>
>>> The basic constraint is to maintain consistency between the published
>>> site and the site sources. In practice this indeed means that the site
>>> is only refreshed during a release. However:
>>>
>>> * One can do manual edits to the generated site, provided that the
>>> site sources are also updated (so that the updates are not lost when
>>> the site is regenerated). I did that with the Axis2 site in order to
>>> fix a couple of broken links after the 1.5.3 release. Unfortunately
>>> people tend to forget to update the site sources, leaving it to other
>>> people to clean up the mess when doing a new release (see r1042149 and
>>> r1042163).
>>> * Technically, nothing would prevent us from republishing the site
>>> from the trunk without doing a release. However, this means that the
>>> site may contain information (e.g. in the Javadoc) that is not
>>> applicable to any release. Also, I don't know any project at the ASF
>>> that does this.
>>>
>>> > If true, that does not seem too flexible, does it?
>>>
>>> Maven sites are fine for some type of documentation (such as Javadoc,
>>> reference documentation or information that doesn't change much), but
>>> it 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 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
>>> 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 solution.
>>>
>>> > Nadir Amra
>>> >
>>> >
>>> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010
>>> > 11:04:50 AM:
>>> >
>>> >> From: Andreas Veithen <an...@gmail.com>
>>> >> To: java-dev@axis.apache.org
>>> >> Date: 12/27/2010 11:07 AM
>>> >> Subject: 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 to get them published is
>>> >> with the next release. If that is 1.6, then the changes will be
>>> >> included automatically. If the next release is 1.5.5, then the site
>>> >> changes need to be merged to the 1.5 branch first (I did that for
>>> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
>>> >> release from the 1.5 branch).
>>> >>
>>> >> Andreas
>>> >>
>>> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
>>> >> > 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.org
>>> >> > still been updated?
>>> >> >
>>> >> > --
>>> >> > Afkham Azeez
>>> >> > Senior Software Architect & Senior Manager; WSO2,
>>> >> > Inc.; http://wso2.com,
>>> >> >
>>> >> > Member; Apache Software Foundation; http://www.apache.org/
>>> >> > email: azeez@wso2.com cell: +94 77 3320919
>>> >> > blog: http://blog.afkham.org
>>> >> > twitter: http://twitter.com/afkham_azeez
>>> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>>> >> >
>>> >> > Lean . Enterprise . Middleware
>>> >> >
>>> >> >
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>>> >>
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>
>>
>>
>> --
>> Afkham Azeez
>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>>
>> Member; Apache Software Foundation; http://www.apache.org/
>> email: azeez@wso2.com cell: +94 77 3320919
>> blog: http://blog.afkham.org
>> twitter: http://twitter.com/afkham_azeez
>> linked-in: http://lk.linkedin.com/in/afkhamazeez
>>
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Axis Website update
Posted by Amila Suriarachchi <am...@gmail.com>.
please add a nightly build (distribution) location too to the site.
thanks,
Amila.
On Tue, Dec 28, 2010 at 9:55 AM, Afkham Azeez <af...@gmail.com> wrote:
> I think we should be able to modify at least certain pages independent of
> the latest release. For example, the home page http://axis.apache.org/ looks
> so dull & incomplete. Chanaka had prepared nicer looking pages with the
> projects logos and so on. We certainly need to update that page at least.
>
> Thanks
> Azeez
>
>
> On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen <
> andreas.veithen@gmail.com> wrote:
>
>> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
>> > So then updates to the site can only be done on a release boundary?
>>
>> The basic constraint is to maintain consistency between the published
>> site and the site sources. In practice this indeed means that the site
>> is only refreshed during a release. However:
>>
>> * One can do manual edits to the generated site, provided that the
>> site sources are also updated (so that the updates are not lost when
>> the site is regenerated). I did that with the Axis2 site in order to
>> fix a couple of broken links after the 1.5.3 release. Unfortunately
>> people tend to forget to update the site sources, leaving it to other
>> people to clean up the mess when doing a new release (see r1042149 and
>> r1042163).
>> * Technically, nothing would prevent us from republishing the site
>> from the trunk without doing a release. However, this means that the
>> site may contain information (e.g. in the Javadoc) that is not
>> applicable to any release. Also, I don't know any project at the ASF
>> that does this.
>>
>> > If true, that does not seem too flexible, does it?
>>
>> Maven sites are fine for some type of documentation (such as Javadoc,
>> reference documentation or information that doesn't change much), but
>> it 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 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
>> 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 solution.
>>
>> > Nadir Amra
>> >
>> >
>> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010
>> 11:04:50 AM:
>> >
>> >> From: Andreas Veithen <an...@gmail.com>
>> >> To: java-dev@axis.apache.org
>> >> Date: 12/27/2010 11:07 AM
>> >> Subject: 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 to get them published is
>> >> with the next release. If that is 1.6, then the changes will be
>> >> included automatically. If the next release is 1.5.5, then the site
>> >> changes need to be merged to the 1.5 branch first (I did that for
>> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
>> >> release from the 1.5 branch).
>> >>
>> >> Andreas
>> >>
>> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
>> >> > 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.org
>> >> > still been updated?
>> >> >
>> >> > --
>> >> > Afkham Azeez
>> >> > Senior Software Architect & Senior Manager; WSO2, Inc.;
>> http://wso2.com,
>> >> >
>> >> > Member; Apache Software Foundation; http://www.apache.org/
>> >> > email: azeez@wso2.com cell: +94 77 3320919
>> >> > blog: http://blog.afkham.org
>> >> > twitter: http://twitter.com/afkham_azeez
>> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>> >> >
>> >> > Lean . Enterprise . Middleware
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
>
> --
> *Afkham Azeez*
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
> *
> *
> *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/>
> *
> email: **azeez@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
> *
> *
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Axis Website update
Posted by Afkham Azeez <af...@gmail.com>.
I think we should be able to modify at least certain pages independent of
the latest release. For example, the home page http://axis.apache.org/ looks
so dull & incomplete. Chanaka had prepared nicer looking pages with the
projects logos and so on. We certainly need to update that page at least.
Thanks
Azeez
On Tue, Dec 28, 2010 at 2:58 AM, Andreas Veithen
<an...@gmail.com>wrote:
> On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
> > So then updates to the site can only be done on a release boundary?
>
> The basic constraint is to maintain consistency between the published
> site and the site sources. In practice this indeed means that the site
> is only refreshed during a release. However:
>
> * One can do manual edits to the generated site, provided that the
> site sources are also updated (so that the updates are not lost when
> the site is regenerated). I did that with the Axis2 site in order to
> fix a couple of broken links after the 1.5.3 release. Unfortunately
> people tend to forget to update the site sources, leaving it to other
> people to clean up the mess when doing a new release (see r1042149 and
> r1042163).
> * Technically, nothing would prevent us from republishing the site
> from the trunk without doing a release. However, this means that the
> site may contain information (e.g. in the Javadoc) that is not
> applicable to any release. Also, I don't know any project at the ASF
> that does this.
>
> > If true, that does not seem too flexible, does it?
>
> Maven sites are fine for some type of documentation (such as Javadoc,
> reference documentation or information that doesn't change much), but
> it 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 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
> 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 solution.
>
> > Nadir Amra
> >
> >
> > Andreas Veithen <an...@gmail.com> wrote on 12/27/2010 11:04:50
> AM:
> >
> >> From: Andreas Veithen <an...@gmail.com>
> >> To: java-dev@axis.apache.org
> >> Date: 12/27/2010 11:07 AM
> >> Subject: 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 to get them published is
> >> with the next release. If that is 1.6, then the changes will be
> >> included automatically. If the next release is 1.5.5, then the site
> >> changes need to be merged to the 1.5 branch first (I did that for
> >> 1.5.4, and I plan to do the same for 1.5.5, if there is another
> >> release from the 1.5 branch).
> >>
> >> Andreas
> >>
> >> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
> >> > 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.org
> >> > still been updated?
> >> >
> >> > --
> >> > Afkham Azeez
> >> > Senior Software Architect & Senior Manager; WSO2, Inc.;
> http://wso2.com,
> >> >
> >> > Member; Apache Software Foundation; http://www.apache.org/
> >> > email: azeez@wso2.com cell: +94 77 3320919
> >> > blog: http://blog.afkham.org
> >> > twitter: http://twitter.com/afkham_azeez
> >> > linked-in: http://lk.linkedin.com/in/afkhamazeez
> >> >
> >> > Lean . Enterprise . Middleware
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
--
*Afkham Azeez*
Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
*
*
*Member; Apache Software Foundation;
**http://www.apache.org/*<http://www.apache.org/>
*
email: **azeez@wso2.com* <az...@wso2.com>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
*
*
Re: Axis Website update
Posted by Andreas Veithen <an...@gmail.com>.
On Mon, Dec 27, 2010 at 19:16, Nadir Amra <am...@us.ibm.com> wrote:
> So then updates to the site can only be done on a release boundary?
The basic constraint is to maintain consistency between the published
site and the site sources. In practice this indeed means that the site
is only refreshed during a release. However:
* One can do manual edits to the generated site, provided that the
site sources are also updated (so that the updates are not lost when
the site is regenerated). I did that with the Axis2 site in order to
fix a couple of broken links after the 1.5.3 release. Unfortunately
people tend to forget to update the site sources, leaving it to other
people to clean up the mess when doing a new release (see r1042149 and
r1042163).
* Technically, nothing would prevent us from republishing the site
from the trunk without doing a release. However, this means that the
site may contain information (e.g. in the Javadoc) that is not
applicable to any release. Also, I don't know any project at the ASF
that does this.
> If true, that does not seem too flexible, does it?
Maven sites are fine for some type of documentation (such as Javadoc,
reference documentation or information that doesn't change much), but
it 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 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
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 solution.
> Nadir Amra
>
>
> Andreas Veithen <an...@gmail.com> wrote on 12/27/2010 11:04:50 AM:
>
>> From: Andreas Veithen <an...@gmail.com>
>> To: java-dev@axis.apache.org
>> Date: 12/27/2010 11:07 AM
>> Subject: 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 to get them published is
>> with the next release. If that is 1.6, then the changes will be
>> included automatically. If the next release is 1.5.5, then the site
>> changes need to be merged to the 1.5 branch first (I did that for
>> 1.5.4, and I plan to do the same for 1.5.5, if there is another
>> release from the 1.5 branch).
>>
>> Andreas
>>
>> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
>> > 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.org
>> > still been updated?
>> >
>> > --
>> > Afkham Azeez
>> > Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>> >
>> > Member; Apache Software Foundation; http://www.apache.org/
>> > email: azeez@wso2.com cell: +94 77 3320919
>> > blog: http://blog.afkham.org
>> > twitter: http://twitter.com/afkham_azeez
>> > linked-in: http://lk.linkedin.com/in/afkhamazeez
>> >
>> > Lean . Enterprise . Middleware
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Axis Website update
Posted by Nadir Amra <am...@us.ibm.com>.
So then updates to the site can only be done on a release boundary? If
true, that does not seem too flexible, does it?
Nadir Amra
Andreas Veithen <an...@gmail.com> wrote on 12/27/2010 11:04:50
AM:
> From: Andreas Veithen <an...@gmail.com>
> To: java-dev@axis.apache.org
> Date: 12/27/2010 11:07 AM
> Subject: 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 to get them published is
> with the next release. If that is 1.6, then the changes will be
> included automatically. If the next release is 1.5.5, then the site
> changes need to be merged to the 1.5 branch first (I did that for
> 1.5.4, and I plan to do the same for 1.5.5, if there is another
> release from the 1.5 branch).
>
> Andreas
>
> On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
> > 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.org
> > still been updated?
> >
> > --
> > Afkham Azeez
> > Senior Software Architect & Senior Manager; WSO2, Inc.;
http://wso2.com,
> >
> > Member; Apache Software Foundation; http://www.apache.org/
> > email: azeez@wso2.com cell: +94 77 3320919
> > blog: http://blog.afkham.org
> > twitter: http://twitter.com/afkham_azeez
> > linked-in: http://lk.linkedin.com/in/afkhamazeez
> >
> > Lean . Enterprise . Middleware
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
Re: Axis Website update
Posted by Andreas Veithen <an...@gmail.com>.
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 that is 1.6, then the changes will be
included automatically. If the next release is 1.5.5, then the site
changes need to be merged to the 1.5 branch first (I did that for
1.5.4, and I plan to do the same for 1.5.5, if there is another
release from the 1.5 branch).
Andreas
On Sun, Dec 26, 2010 at 06:51, Afkham Azeez <af...@gmail.com> wrote:
> 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.org
> still been updated?
>
> --
> Afkham Azeez
> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com,
>
> Member; Apache Software Foundation; http://www.apache.org/
> email: azeez@wso2.com cell: +94 77 3320919
> blog: http://blog.afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org