You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Christian Grobmeier <gr...@gmail.com> on 2013/09/02 17:46:35 UTC
Nuking module sites
I believe these sites do not serve any purpose and are more confusing
than helping:
http://struts.apache.org/release/2.3.x/xwork-core/index.html
http://struts.apache.org/release/2.3.x/struts2-core/index.html
http://struts.apache.org/release/2.3.x/struts2-apps/index.html
http://struts.apache.org/release/2.3.x/struts2-plugins/index.html
http://struts.apache.org/release/2.3.x/struts2-osgi-bundles/index.html
http://struts.apache.org/release/2.3.x/struts2-archetypes/index.html
http://struts.apache.org/release/2.3.x/struts2-assembly/index.html (worst)
none of the module webpages are listing any relevant info. I would like
to svn rm all the /src/site folders from them.
This includes submodules of the submodules, like this:
http://struts.apache.org/release/2.3.x/struts2-plugins/struts2-javatemplates-plugin/index.html
Any objections?
Cheers
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Christian Grobmeier <gr...@gmail.com>.
Am 10.09.13 13:19, schrieb Lukasz Lenart:
> 2013/9/9 Christian Grobmeier <gr...@gmail.com>:
>> ...
> Throw them away ... we have other tools like Sonar [1], maybe it is
> bette to link to them
>
> [1] https://analysis.apache.org/dashboard/index/9936
You are right.
Just removed the files and linked to the analysis site
Thanks for the link!
>
> Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Lukasz Lenart <lu...@apache.org>.
2013/9/9 Christian Grobmeier <gr...@gmail.com>:
> Am 05.09.13 10:35, schrieb Lukasz Lenart:
>> 2013/9/5 Christian Grobmeier <gr...@gmail.com>:
>>>> I had a reason to add all those src/site's ;-)
>>> Is the reason still valid?
>> I cannot recall what it was ;-) So maybe it ins't valid anymore ;-)
>>
>>> I have no problem keeping them, as I found out how to remove it from the
>>> links section.
>>> Otherwise they do not seem to add value. But maybe i am missing the value?
>> The only value I see are the Dependencies reports (and maybe some
>> Checkstyles, etc) - the rest isn't important.
> Still in doubt if I should remove it now or not - i don't want to
> destroy anything which might have a use :-)
>
> Basically we can leave them in, as they are not longer linked. On the
> other hand, the reports seem to be generated
> even without a site.xml - which i found weird but ok.
>
> Also dependency reports can be created from the commandline. Question
> is, what is the user doing?
> Maybe we should only link the dependency reports from the sub
> components, but that would be a lot of work
Throw them away ... we have other tools like Sonar [1], maybe it is
bette to link to them
[1] https://analysis.apache.org/dashboard/index/9936
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Christian Grobmeier <gr...@gmail.com>.
Am 05.09.13 10:35, schrieb Lukasz Lenart:
> 2013/9/5 Christian Grobmeier <gr...@gmail.com>:
>>> I had a reason to add all those src/site's ;-)
>> Is the reason still valid?
> I cannot recall what it was ;-) So maybe it ins't valid anymore ;-)
>
>> I have no problem keeping them, as I found out how to remove it from the
>> links section.
>> Otherwise they do not seem to add value. But maybe i am missing the value?
> The only value I see are the Dependencies reports (and maybe some
> Checkstyles, etc) - the rest isn't important.
Still in doubt if I should remove it now or not - i don't want to
destroy anything which might have a use :-)
Basically we can leave them in, as they are not longer linked. On the
other hand, the reports seem to be generated
even without a site.xml - which i found weird but ok.
Also dependency reports can be created from the commandline. Question
is, what is the user doing?
Maybe we should only link the dependency reports from the sub
components, but that would be a lot of work
>
>
> Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Lukasz Lenart <lu...@apache.org>.
2013/9/5 Christian Grobmeier <gr...@gmail.com>:
>> I had a reason to add all those src/site's ;-)
> Is the reason still valid?
I cannot recall what it was ;-) So maybe it ins't valid anymore ;-)
> I have no problem keeping them, as I found out how to remove it from the
> links section.
> Otherwise they do not seem to add value. But maybe i am missing the value?
The only value I see are the Dependencies reports (and maybe some
Checkstyles, etc) - the rest isn't important.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Christian Grobmeier <gr...@gmail.com>.
Am 05.09.13 07:33, schrieb Lukasz Lenart:
> 2013/9/4 Christian Grobmeier <gr...@gmail.com>:
>> I have removed the "module" section in $root/src/site and now they
>> should not be linked.
>> I am a bit concerned with removing all src/site. I did that locally, but
>> the sites are still generated with default settings. I could exclude
>> them from the generation, but then I realized that I didn't understand
>> how the API docs from the plugs are generated. Do I need to take care on
>> that or is this an independent step?
> I had a reason to add all those src/site's ;-)
Is the reason still valid?
I have no problem keeping them, as I found out how to remove it from the
links section.
Otherwise they do not seem to add value. But maybe i am missing the value?
>
> Though, removing them shouldn't impact JavaDocs as they are generated
> during release process. I think you can test that with
> -Papache-release profile
>
>
> Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Lukasz Lenart <lu...@apache.org>.
2013/9/4 Christian Grobmeier <gr...@gmail.com>:
> I have removed the "module" section in $root/src/site and now they
> should not be linked.
> I am a bit concerned with removing all src/site. I did that locally, but
> the sites are still generated with default settings. I could exclude
> them from the generation, but then I realized that I didn't understand
> how the API docs from the plugs are generated. Do I need to take care on
> that or is this an independent step?
I had a reason to add all those src/site's ;-)
Though, removing them shouldn't impact JavaDocs as they are generated
during release process. I think you can test that with
-Papache-release profile
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Christian Grobmeier <gr...@gmail.com>.
Am 03.09.13 21:52, schrieb Christian Grobmeier:
> Am 03.09.13 15:03, schrieb Lukasz Lenart:
>> Hi,
>>
>> You must rather removed src/site from the source.
> Yes, i am planning to do that exactly.
>
> Still waiting a bit if somebody else wants to speak up
>
I have removed the "module" section in $root/src/site and now they
should not be linked.
I am a bit concerned with removing all src/site. I did that locally, but
the sites are still generated with default settings. I could exclude
them from the generation, but then I realized that I didn't understand
how the API docs from the plugs are generated. Do I need to take care on
that or is this an independent step?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Christian Grobmeier <gr...@gmail.com>.
Am 03.09.13 15:03, schrieb Lukasz Lenart:
> Hi,
>
> You must rather removed src/site from the source.
Yes, i am planning to do that exactly.
Still waiting a bit if somebody else wants to speak up
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Nuking module sites
Posted by Lukasz Lenart <lu...@apache.org>.
Hi,
You must rather removed src/site from the source.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/9/2 Christian Grobmeier <gr...@gmail.com>:
> I believe these sites do not serve any purpose and are more confusing
> than helping:
>
> http://struts.apache.org/release/2.3.x/xwork-core/index.html
> http://struts.apache.org/release/2.3.x/struts2-core/index.html
> http://struts.apache.org/release/2.3.x/struts2-apps/index.html
> http://struts.apache.org/release/2.3.x/struts2-plugins/index.html
> http://struts.apache.org/release/2.3.x/struts2-osgi-bundles/index.html
> http://struts.apache.org/release/2.3.x/struts2-archetypes/index.html
> http://struts.apache.org/release/2.3.x/struts2-assembly/index.html (worst)
>
> none of the module webpages are listing any relevant info. I would like
> to svn rm all the /src/site folders from them.
> This includes submodules of the submodules, like this:
>
> http://struts.apache.org/release/2.3.x/struts2-plugins/struts2-javatemplates-plugin/index.html
>
> Any objections?
>
> Cheers
> Christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org