Re: improve documentation for UploadedFilesAware

2024-03-25 Thread Łukasz Lenart
pon., 25 mar 2024 o 10:00 Greg Huber napisał(a): > > OK great. More of a chance of it being read 🙂. Thanks, merged > I guess this new version includes all the "old versions" security stuff > from past issues, and is not a new code base. Yes, it only uses a different mechanism to pass uploaded

Re: improve documentation for UploadedFilesAware

2024-03-25 Thread Greg Huber
OK great.  More of a chance of it being read 🙂. I guess this new version includes all the "old versions" security stuff from past issues, and is not a new code base. As the old one is deprecated, and we all rush and upgrade, their may be more resources put in trying to break it.  Maybe better

Re: improve documentation for UploadedFilesAware

2024-03-24 Thread Lukasz Lenart
pon., 18 mar 2024 o 14:42 Greg Huber napisał(a): > > OK...I did not spot the link in the text. I repeated the links in the Examples sections of both Cheers Lukasz - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For

Re: improve documentation for UploadedFilesAware

2024-03-18 Thread Greg Huber
OK...I did not spot the link in the text. On Mon, 18 Mar 2024 at 12:59, Łukasz Lenart wrote: > pon., 18 mar 2024 o 13:05 Greg Huber napisał(a): > > > > > See [this page] for more examples and advanced configuration. > > > > Which page? > > On these pages, a very first sentence > > https://stru

Re: improve documentation for UploadedFilesAware

2024-03-18 Thread Łukasz Lenart
pon., 18 mar 2024 o 13:05 Greg Huber napisał(a): > > > See [this page] for more examples and advanced configuration. > > Which page? On these pages, a very first sentence https://struts.staged.apache.org/core-developers/action-file-upload-interceptor https://struts.staged.apache.org/core-develope

Re: improve documentation for UploadedFilesAware

2024-03-18 Thread Greg Huber
See [this page] for more examples and advanced configuration. Which page? I reverted this idea and UploadedFile isn't generic. that would be in 7.0.0_M4? I used _M3 to test it. On 18/03/2024 11:56, Lukasz Lenart wrote: pon., 18 mar 2024 o 08:21 Greg Huber napisał(a): Rechecking these :

Re: improve documentation for UploadedFilesAware

2024-03-18 Thread Lukasz Lenart
pon., 18 mar 2024 o 08:21 Greg Huber napisał(a): > > Rechecking these : > > Could not see the link from from the interceptor pages to these detailed > help pages. Add a link after Examples? > > File Upload Interceptor > > Parameters > Extending the Interceptor > Examples > > > Or a

Re: improve documentation for UploadedFilesAware

2024-03-18 Thread Greg Huber
stream stuff. return this.uploadedFiles.stream().map(UploadedFile::getContentType).toArray(); otherwise without streams List>uploads =this.uploadedFiles; if(uploads !=null&&uploads.size()>0){ for(inti =0;i pon., 26 lut 2024 o 12:08 Greg Hubernapisał(a): The documenta

Re: improve documentation for UploadedFilesAware

2024-03-17 Thread Lukasz Lenart
-upload-interceptor > >>>> > >>>> would benefit a similar detail page, updated and with the stream stuff. > >>>> > >>>> return > >>> this.uploadedFiles.stream().map(UploadedFile::getContentType).toArray(); > &g

Re: improve documentation for UploadedFilesAware

2024-03-17 Thread Greg Huber
enefit a similar detail page, updated and with the stream stuff. return this.uploadedFiles.stream().map(UploadedFile::getContentType).toArray(); otherwise without streams List>uploads =this.uploadedFiles; if(uploads !=null&&uploads.size()>0){ for(inti =0;i pon., 26 lut 2

Re: improve documentation for UploadedFilesAware

2024-03-17 Thread Lukasz Lenart
gt; > > if(uploads !=null&&uploads.size()>0){ > > > > > > for(inti =0;i > > > > > String file uploads.get(i).getOriginalName(); > > > > > > // destroy the temporary file created > > > > > > uploads.get(i).d

Re: improve documentation for UploadedFilesAware

2024-03-14 Thread Greg Huber
e()>0){ > > > > for(inti =0;i > > > String file uploads.get(i).getOriginalName(); > > > > // destroy the temporary file created > > > > uploads.get(i).delete(); > > > > } > > > > } > > > > On 12/03/2024 19:48, Lukasz Lenart wrote: >

Re: improve documentation for UploadedFilesAware

2024-03-14 Thread Łukasz Lenart
elete(); > > } > > } > > On 12/03/2024 19:48, Lukasz Lenart wrote: > > pon., 26 lut 2024 o 12:08 Greg Huber napisał(a): > >> The documentation only lists one file > >> > >> |public void withUploadedFiles(List uploadedFiles) { if > >>

Re: improve documentation for UploadedFilesAware

2024-03-14 Thread Greg Huber
er napisał(a): The documentation only lists one file |public void withUploadedFiles(List uploadedFiles) { if (!uploadedFiles.isEmpty()) { this.uploadedFile = uploadedFiles.get(0); this.fileName = uploadedFile.getName(); this.contentType = uploadedFile.getContentType(); this.originalName = uploaded

Re: improve documentation for UploadedFilesAware

2024-03-12 Thread Lukasz Lenart
pon., 26 lut 2024 o 12:08 Greg Huber napisał(a): > > The documentation only lists one file > > |public void withUploadedFiles(List uploadedFiles) { if > (!uploadedFiles.isEmpty()) { this.uploadedFile = uploadedFiles.get(0); > this.fileName = uploadedFile.getName()

improve documentation for UploadedFilesAware

2024-02-26 Thread Greg Huber
The documentation only lists one file |public void withUploadedFiles(List uploadedFiles) { if (!uploadedFiles.isEmpty()) { this.uploadedFile = uploadedFiles.get(0); this.fileName = uploadedFile.getName(); this.contentType = uploadedFile.getContentType(); this.originalName

[GitHub] [struts-site] lukaszlenart merged pull request #195: WW-5301 Update documentation for struts-deferred.xml

2023-05-23 Thread via GitHub
lukaszlenart merged PR #195: URL: https://github.com/apache/struts-site/pull/195 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@struts.

[GitHub] [struts-site] kusalk opened a new pull request, #195: WW-5301 Update documentation for struts-deferred.xml

2023-05-23 Thread via GitHub
kusalk opened a new pull request, #195: URL: https://github.com/apache/struts-site/pull/195 WW-5301 -- -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-

[GitHub] [struts] lukaszlenart merged pull request #682: Improve [WW-4434] - add documentation and rename existing ftl to achieve the wanted behaviour

2023-05-16 Thread via GitHub
lukaszlenart merged PR #682: URL: https://github.com/apache/struts/pull/682 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@struts.apach

[GitHub] [struts] fischey opened a new pull request, #682: Improve [WW-4434] - add documentation and rename existing ftl to achieve the wanted behaviour

2023-05-05 Thread via GitHub
in the simple theme. With this PR I want to improve the documentation and fix the current available ftl so that others will not get this error too :-) Best regards fischey -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[GitHub] [struts-site] lukaszlenart merged pull request #184: WW-5268 Update documentation with struts.excludedPackageExemptClasses…

2023-02-28 Thread via GitHub
lukaszlenart merged PR #184: URL: https://github.com/apache/struts-site/pull/184 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@struts.

[GitHub] [struts-site] kusalk opened a new pull request, #184: WW-5268 Update documentation with struts.excludedPackageExemptClasses…

2023-02-28 Thread via GitHub
kusalk opened a new pull request, #184: URL: https://github.com/apache/struts-site/pull/184 WW-5268 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[GitHub] [struts-site] lukaszlenart merged pull request #183: Adds initial documentation on OGNL cache configuration

2023-02-06 Thread via GitHub
lukaszlenart merged PR #183: URL: https://github.com/apache/struts-site/pull/183 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@struts.

[GitHub] [struts-site] JCgH4164838Gh792C124B5 opened a new pull request, #183: Adds initial documentation on OGNL cache configuration

2023-01-22 Thread via GitHub
JCgH4164838Gh792C124B5 opened a new pull request, #183: URL: https://github.com/apache/struts-site/pull/183 Hello Struts Development Team. This is an initial attempt to add some documentation on OGNL cache configuration. Not sure if the templating structure is OK or not. Please

[GitHub] [struts-site] lukaszlenart merged pull request #154: Possible site tag documentation updates for WW-5093.

2021-02-19 Thread GitBox
lukaszlenart merged pull request #154: URL: https://github.com/apache/struts-site/pull/154 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

[GitHub] [struts-site] lukaszlenart commented on pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-20 Thread GitBox
lukaszlenart commented on pull request #154: URL: https://github.com/apache/struts-site/pull/154#issuecomment-748813722 Looks good to me, LGTM 👍 This is an automated message from the Apache Git Service. To respond to the mes

[GitHub] [struts-site] JCgH4164838Gh792C124B5 edited a comment on pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-19 Thread GitBox
JCgH4164838Gh792C124B5 edited a comment on pull request #154: URL: https://github.com/apache/struts-site/pull/154#issuecomment-748528953 Hello @yasserzamani and @lukaszlenart . Thanks for the information on the staged site, as that really helps confirming the output. 😄 I applied

[GitHub] [struts-site] JCgH4164838Gh792C124B5 commented on pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-19 Thread GitBox
JCgH4164838Gh792C124B5 commented on pull request #154: URL: https://github.com/apache/struts-site/pull/154#issuecomment-748528953 Hello @yasserzamani and @lukaszlenart . Thanks for the information on the staged site, as that really helps confirming the output. 😄 I applied the pa

[GitHub] [struts-site] lukaszlenart commented on a change in pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-13 Thread GitBox
lukaszlenart commented on a change in pull request #154: URL: https://github.com/apache/struts-site/pull/154#discussion_r541911157 ## File path: source/core-developers/accessing-application-session-request-objects.md ## @@ -50,16 +50,24 @@ is an alternative way to access the r

[GitHub] [struts-site] lukaszlenart commented on a change in pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-13 Thread GitBox
lukaszlenart commented on a change in pull request #154: URL: https://github.com/apache/struts-site/pull/154#discussion_r541910942 ## File path: source/tag-developers/set-tag.md ## @@ -25,9 +25,10 @@ The scopes available are as follows: - `session` - the value will be set in s

[GitHub] [struts-site] yasserzamani commented on a change in pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-13 Thread GitBox
yasserzamani commented on a change in pull request #154: URL: https://github.com/apache/struts-site/pull/154#discussion_r541903584 ## File path: source/core-developers/accessing-application-session-request-objects.md ## @@ -50,16 +50,24 @@ is an alternative way to access the r

[GitHub] [struts-site] yasserzamani commented on pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-13 Thread GitBox
yasserzamani commented on pull request #154: URL: https://github.com/apache/struts-site/pull/154#issuecomment-743991610 Thanks a lot! BTW with thanks to @lukaszlenart , you can review a staged site at https://struts.staged.apache.org/ which reflects the PR changes I think (That's also visi

[GitHub] [struts-site] JCgH4164838Gh792C124B5 commented on pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-12 Thread GitBox
JCgH4164838Gh792C124B5 commented on pull request #154: URL: https://github.com/apache/struts-site/pull/154#issuecomment-743875878 Hi. I have not attempted any documentation site update PRs before, so hopefully the styling is OK. If anything needs to be changed, please let me know

[GitHub] [struts-site] JCgH4164838Gh792C124B5 opened a new pull request #154: Possible site tag documentation updates for WW-5093.

2020-12-12 Thread GitBox
JCgH4164838Gh792C124B5 opened a new pull request #154: URL: https://github.com/apache/struts-site/pull/154 Possible site tag documentation updates for WW-5093. - Minor updates to set, text and url tag text, to clarify scope and behaviour. - Minor clarifications on "acce

[GitHub] [struts-site] lukaszlenart commented on pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-09-06 Thread GitBox
lukaszlenart commented on pull request #149: URL: https://github.com/apache/struts-site/pull/149#issuecomment-688051754 LGTM 👍 This is an automated message from the Apache Git Service. To respond to the message, please log o

[GitHub] [struts-site] lukaszlenart merged pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-09-06 Thread GitBox
lukaszlenart merged pull request #149: URL: https://github.com/apache/struts-site/pull/149 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

[GitHub] [struts-site] gchatz22 edited a comment on pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-08-28 Thread GitBox
gchatz22 edited a comment on pull request #149: URL: https://github.com/apache/struts-site/pull/149#issuecomment-682771689 Thank you for your comments @yasserzamani ! Applied your changes and as said will also be waiting for @apache/struts-committers opinion --

[GitHub] [struts-site] gchatz22 edited a comment on pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-08-28 Thread GitBox
gchatz22 edited a comment on pull request #149: URL: https://github.com/apache/struts-site/pull/149#issuecomment-682771689 Thank you for your comments @yasserzamani ! Applied your changes and as said will also be waiting for @apache/struts-committers opinion. -

[GitHub] [struts-site] gchatz22 edited a comment on pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-08-28 Thread GitBox
gchatz22 edited a comment on pull request #149: URL: https://github.com/apache/struts-site/pull/149#issuecomment-682771689 Thank you for your comments @yasserzamani ! Applied your changes and as said will also be waiting for @[apache/struts-committers](https://github.com/orgs/apache/teams/

[GitHub] [struts-site] gchatz22 commented on pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-08-28 Thread GitBox
gchatz22 commented on pull request #149: URL: https://github.com/apache/struts-site/pull/149#issuecomment-682771689 Thank you for your comments @yasserzamani ! Applied your changes and as said will also be waiting for @apache/struts-committers opinion.

[GitHub] [struts-site] yasserzamani commented on a change in pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-08-28 Thread GitBox
yasserzamani commented on a change in pull request #149: URL: https://github.com/apache/struts-site/pull/149#discussion_r479367165 ## File path: source/core-developers/coep-interceptor.md ## @@ -0,0 +1,43 @@ +--- +layout: default +title: COEP Interceptor +parent: +title: In

[GitHub] [struts-site] salcho opened a new pull request #149: Adding documentation for Fetch Metadata, Cross-Origin Opener Poliy & Cross-Origin Embedder Policy

2020-08-28 Thread GitBox
pache/struts/pull/432) in the past few months while CSP is still being reviewed (https://github.com/apache/struts/pull/430). This PR updates documentation to reflect the new interceptors (not CSP!), their parameters, usage and brief explanations of what these security mitigations are and how they

Re: Documentation

2017-11-23 Thread Lukasz Lenart
2017-11-19 19:43 GMT+01:00 Yasser Zamani : > Maybe it's better to have docs for each release separately (I thought > about when we delete a deprecated option then we cannot handle related > docs nicely). > > I investigated how Jekyll's users do such things and found [1]. I took a > look and it seem

Re: Documentation

2017-11-19 Thread Yasser Zamani
On 11/16/2017 9:16 AM, Lukasz Lenart wrote:> @sdutry <https://github.com/sdutry> an another branch is a nice idea, I > think this would work. > > Anyway, as we do not provide a separated copy of documentation per each > release (as it used to be), we have to be sur

Re: Documentation

2017-10-30 Thread Lukasz Lenart
2017-10-30 18:58 GMT+01:00 Nate Drake : > http://struts.apache.org/docs/security-bulletins.html returns a 404. > Should it redirect to > https://cwiki.apache.org/confluence/display/WW/Security+Bulletins ? Good point, I have added a redirect Regards -- Łukasz + 48 606 323 122 http://www.lenart.o

Re: Documentation

2017-10-30 Thread Nate Drake
http://struts.apache.org/docs/security-bulletins.html returns a 404. Should it redirect to https://cwiki.apache.org/confluence/display/WW/Security+Bulletins ? On Mon, Oct 30, 2017 at 9:16 AM, Christoph Nenning < christoph.nenn...@lex-com.net> wrote: > > > > Hi, > > > > I have finally switched our

Re: Documentation

2017-10-30 Thread Christoph Nenning
> > Hi, > > I have finally switched our docs plus added some redirects to support > old links. If something is broken, let me know :) > > awesome that it's finally done! I love the "Edit on GitHub" button :) Regards, Christoph This Email was scanned by proofpoint

Re: Documentation

2017-10-27 Thread Lukasz Lenart
Hi, I have finally switched our docs plus added some redirects to support old links. If something is broken, let me know :) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: dev-unsubscr...

Re: Documentation

2017-10-10 Thread Lukasz Lenart
2017-10-09 11:33 GMT+02:00 Christoph Nenning : >> Does anyone use it? > > I don't :) Me too ;-) > IMHO most people don't download distributions anymore. They use dependency > managers (maven, gradle) and search for docs and help online. > > But as long as we provide a distribution zip it makes se

Re: Documentation

2017-10-09 Thread Christoph Nenning
ds, Christoph > From: Lukasz Lenart > To: Struts Developers List , > Date: 06.10.2017 18:47 > Subject: Re: Documentation > > I think we are close to end of the migration. One thing left: should > we still distribute the docs with Struts release? Does anyone use it? > Maybe

Re: Documentation

2017-10-06 Thread Lukasz Lenart
I think we are close to end of the migration. One thing left: should we still distribute the docs with Struts release? Does anyone use it? Maybe we can introduce a PDF version of the docs and distribute them instead? Do you know a good MD to PDF converter? Regards -- Łukasz + 48 606 323 122 htt

Re: Documentation

2017-09-28 Thread Yasser Zamani
On 9/27/2017 2:21 PM, Yasser Zamani wrote: > All docs of plugins converted as carefully as I could :) > > Honestly, snippet.rb was my first Ruby coding (was very enjoyable) :) If > you're a Ruby expert too, please feel free if it could be better. > > Sincerely Yours, > Yasser. I am improving

Re: Documentation

2017-09-27 Thread Lukasz Lenart
2017-09-27 12:51 GMT+02:00 Yasser Zamani : > All docs of plugins converted as carefully as I could :) > > Honestly, snippet.rb was my first Ruby coding (was very enjoyable) :) If > you're a Ruby expert too, please feel free if it could be better. Great work! I'm not a Ruby expert so I assume every

Re: Documentation

2017-09-27 Thread Yasser Zamani
On 9/25/2017 5:30 PM, Yasser Zamani wrote: > > > On 9/25/2017 5:22 PM, Lukasz Lenart wrote: >> 2017-09-25 15:46 GMT+02:00 Yasser Zamani : >>> So if I understood well, this tag isn't needed anymore, because during >>> this work and transition, we can copy and paste that snippets from their >>> u

Re: Documentation

2017-09-25 Thread Lukasz Lenart
2017-09-25 16:00 GMT+02:00 Yasser Zamani : > Aha... you're right. That helps us to copy/paste much faster! I finished > and tested that now. I'll PR it tomorrow or one day later when I > finished the whole plugin-developers.md processing :) osm! Regards -- Łukasz + 48 606 323 122 http://www.len

Re: Documentation

2017-09-25 Thread Yasser Zamani
On 9/25/2017 5:22 PM, Lukasz Lenart wrote: > 2017-09-25 15:46 GMT+02:00 Yasser Zamani : >> So if I understood well, this tag isn't needed anymore, because during >> this work and transition, we can copy and paste that snippets from their >> url into new docs md files. If it is what we want at end

Re: Documentation

2017-09-25 Thread Lukasz Lenart
2017-09-25 15:46 GMT+02:00 Yasser Zamani : > So if I understood well, this tag isn't needed anymore, because during > this work and transition, we can copy and paste that snippets from their > url into new docs md files. If it is what we want at end, so let do it > now during transition. Am I right

Re: Documentation

2017-09-25 Thread Yasser Zamani
d related docs as I will share it with my >> plugin-developers.md's PR tomorrow or one day later :) > > Great! Just one note: we do plan move all code snippets into docs, I > mean right now we have two places where the documentation exists - > Java source code (snippets) a

Re: Documentation

2017-09-25 Thread Lukasz Lenart
pers.md's PR tomorrow or one day later :) Great! Just one note: we do plan move all code snippets into docs, I mean right now we have two places where the documentation exists - Java source code (snippets) and struts-site repo. It would be good to have all in one place. Regards -- Łukasz + 48

Re: Documentation

2017-09-25 Thread Yasser Zamani
On 9/23/2017 4:23 PM, Yasser Zamani wrote: > > > On 9/20/2017 11:36 AM, Yasser Zamani wrote: >> >> >> On 9/20/2017 10:58 AM, Lukasz Lenart wrote: >>> 2017-09-20 7:44 GMT+02:00 Lukasz Lenart : 2017-09-19 20:23 GMT+02:00 Yasser Zamani : > I reviewed [1] and it seems it does not convert e

Re: Documentation

2017-09-23 Thread Yasser Zamani
On 9/20/2017 11:36 AM, Yasser Zamani wrote: > > > On 9/20/2017 10:58 AM, Lukasz Lenart wrote: >> 2017-09-20 7:44 GMT+02:00 Lukasz Lenart : >>> 2017-09-19 20:23 GMT+02:00 Yasser Zamani : I reviewed [1] and it seems it does not convert every thing (e.g. I think it should can convert #Ta

Re: Documentation

2017-09-20 Thread Yasser Zamani
On 9/20/2017 10:58 AM, Lukasz Lenart wrote: > 2017-09-20 7:44 GMT+02:00 Lukasz Lenart : >> 2017-09-19 20:23 GMT+02:00 Yasser Zamani : >>> I reviewed [1] and it seems it does not convert every thing (e.g. I >>> think it should can convert #Tag Developers Guide# to # Tag Developers >>> Guide) and w

Re: Documentation

2017-09-20 Thread Yasser Zamani
Sreenivas, To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org On 9/20/2017 9:01 AM, Sreenivas M wrote: > To unsubscribe, e-mail:dev-unsubscr...@struts.apache.org - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org

Re: Documentation

2017-09-20 Thread Lukasz Lenart
2017-09-20 7:44 GMT+02:00 Lukasz Lenart : > 2017-09-19 20:23 GMT+02:00 Yasser Zamani : >> I reviewed [1] and it seems it does not convert every thing (e.g. I >> think it should can convert #Tag Developers Guide# to # Tag Developers >> Guide) and we still need do further editing, right? or we can de

Re: Documentation

2017-09-19 Thread Lukasz Lenart
2017-09-19 20:23 GMT+02:00 Yasser Zamani : > I reviewed [1] and it seems it does not convert every thing (e.g. I > think it should can convert #Tag Developers Guide# to # Tag Developers > Guide) and we still need do further editing, right? or we can develop > the converter if still there are a lot

Re: Documentation

2017-09-19 Thread Sreenivas M
Kindly remove me from this grouo On 14 Jul 2017 11:05 pm, "Ken McWilliams" wrote: > That page looks pretty good, it is quite clear and well formatted. And > covers an exceptional range from hello-world with view only action, all the > way to overrides at the end. > > Two very small errors: > 1)

Re: Documentation

2017-09-19 Thread Yasser Zamani
On 9/18/2017 11:46 AM, Lukasz Lenart wrote: > 2017-09-15 11:09 GMT+02:00 Yasser Zamani : >> May I help you in documentation transition from Confluence ? If I had a >> read-only version of *source code* of Confluence's docs, then I think I >> may able write a conver

Re: Documentation

2017-09-18 Thread Lukasz Lenart
2017-09-18 10:34 GMT+02:00 Christoph Nenning : >> I'm not sure what to do with >> https://cwiki.apache.org/confluence/display/WW/Migration+Guide - if >> this also should be migrated or not. > > I would prefer to migrate it. Linked Version Notes and Release Notes, too. > > Is this suitable for relea

Re: Documentation

2017-09-18 Thread Christoph Nenning
> From: Lukasz Lenart > To: Struts Developers List , > Date: 18.09.2017 09:17 > Subject: Re: Documentation > > 2017-09-15 11:09 GMT+02:00 Yasser Zamani : > > May I help you in documentation transition from Confluence ? If I had a > > read-only version of *source

Re: Documentation

2017-09-18 Thread Lukasz Lenart
2017-09-15 11:09 GMT+02:00 Yasser Zamani : > May I help you in documentation transition from Confluence ? If I had a > read-only version of *source code* of Confluence's docs, then I think I > may able write a convertor code then prepare it's output as a PR against > '

Re: Documentation

2017-09-15 Thread Yasser Zamani
May I help you in documentation transition from Confluence ? If I had a read-only version of *source code* of Confluence's docs, then I think I may able write a convertor code then prepare it's output as a PR against 'struts-site/master'. On 8/1/2017 9:38 AM, Lukasz Lenart

Re: Documentation

2017-07-31 Thread Lukasz Lenart
Hi, I have create a Jenkins job to automatically update our website, so you can commit/push changes directly to the 'master' branch of the 'struts-site' repo and within 15 minutes changes should be deployed to prod ;-) Still working on doing the same for Confluence docs ... but I will probably fa

Re: Documentation

2017-07-16 Thread Lukasz Lenart
Thanks Ken! Fixed and just a raminder, if you have an account on GitHub you can edit and fix all the pages by yourself :) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2017-07-14 19:35 GMT+02:00 Ken McWilliams : > That page looks pretty good, it is quite clear and well formatted.

Re: Documentation

2017-07-14 Thread Ken McWilliams
That page looks pretty good, it is quite clear and well formatted. And covers an exceptional range from hello-world with view only action, all the way to overrides at the end. Two very small errors: 1) A line which reads: The Convention Plugin will pre-configure all of you action classes when Stru

Re: Documentation

2017-07-13 Thread Lukasz Lenart
Moved the Convention Plugin (as a part of the Core Developers Guide) http://struts.apache.org/plugins/convention/ 2017-06-01 13:56 GMT+02:00 Lukasz Lenart : > I have pushed a first raw export, need some work ;) > > 2017-05-30 9:55 GMT+02:00 Christoph Nenning : >>> >>> I think we can go "live" wit

Re: Documentation

2017-06-01 Thread Lukasz Lenart
I have pushed a first raw export, need some work ;) 2017-05-30 9:55 GMT+02:00 Christoph Nenning : >> >> I think we can go "live" with the new Getting Started guide? >> http://struts.apache.org/getting-started/index.html > > +1 > > >> >> And the next I would like to migrate this >> https://cwiki.ap

Re: Documentation

2017-05-30 Thread Christoph Nenning
> > I think we can go "live" with the new Getting Started guide? > http://struts.apache.org/getting-started/index.html +1 > > And the next I would like to migrate this > https://cwiki.apache.org/confluence/display/WW/Core+Developers+Guide +1 Great to see progress :) Regards, Christoph Th

Re: Documentation

2017-05-29 Thread Lukasz Lenart
I think we can go "live" with the new Getting Started guide? http://struts.apache.org/getting-started/index.html And the next I would like to migrate this https://cwiki.apache.org/confluence/display/WW/Core+Developers+Guide Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2017-04-1

Re: Documentation

2017-04-12 Thread Christoph Nenning
> > Navigation links are back > http://struts.apache.org/getting-started/exception-handling.html > +1 > 2017-04-10 7:42 GMT+02:00 Lukasz Lenart : > > 2017-04-06 13:15 GMT+02:00 Christoph Nenning > : > >> One thing I noticed is the old version contains a navigation block with > >> next and

Re: Documentation

2017-04-12 Thread Lukasz Lenart
Navigation links are back http://struts.apache.org/getting-started/exception-handling.html 2017-04-10 7:42 GMT+02:00 Lukasz Lenart : > 2017-04-06 13:15 GMT+02:00 Christoph Nenning : >> One thing I noticed is the old version contains a navigation block with >> next and prev links at the bottom. Tha

Re: Documentation

2017-04-09 Thread Lukasz Lenart
2017-04-06 13:15 GMT+02:00 Christoph Nenning : > One thing I noticed is the old version contains a navigation block with > next and prev links at the bottom. That seems to be missing in new > version. Good point, I will put it back Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ -

Re: Documentation

2017-04-09 Thread Lukasz Lenart
2017-04-06 13:47 GMT+02:00 Johannes Geppert : > I agree, looks much better than before! > > Just wonder why in the log setup the reference is to log4j instead to > log4j2 implementation. It's a copy of the existing Getting started guide which is a bit outdated but this is WIP and it's very easy to

Re: New Documentation/Question on Site

2017-04-06 Thread Lukasz Lenart
2017-04-06 15:24 GMT+02:00 Louis Smith : > I very much like the new look of the site, and the 2 new pages from > Christopher. > > I do have one question - where is the roadmap showing the future of > Struts? Plans for Java 8, Struts 3, etc. You can check this page [1], but it must be updated to r

New Documentation/Question on Site

2017-04-06 Thread Louis Smith
I very much like the new look of the site, and the 2 new pages from Christopher. I do have one question - where is the roadmap showing the future of Struts? Plans for Java 8, Struts 3, etc. Thanks again for all the great and hard work you all do on Struts. My clients have been using it for over

Re: Documentation

2017-04-06 Thread Johannes Geppert
I agree, looks much better than before! Just wonder why in the log setup the reference is to log4j instead to log4j2 implementation. Best Regards Johannes # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2017-04-06 13:15 GMT+02:0

Re: Documentation

2017-04-06 Thread Christoph Nenning
> > 2017-02-02 20:32 GMT+01:00 Aleksandr Mashchenko : > >> Maybe this can help: http://www.viaboxx.de/code/confluence2md/ > > > > Thanks, I was able to use it but it exports everything directly into > > one file :\ but I can still used to start working on new Getting > > started guide :) > > This

Re: Documentation

2017-04-01 Thread Lukasz Lenart
Done, for titles there is no simple solution, but with small JS I convert an existing "title" attribute into a code block header title, wdyt? https://github.com/apache/struts-site/blame/master/source/getting-started/how-to-create-a-struts2-web-application.md#L50-L55 2017-04-01 10:02 GMT+02:00 Luk

Re: Documentation

2017-04-01 Thread Lukasz Lenart
2017-04-01 0:14 GMT+02:00 Stefaan Dutry : > The adjusted page looks good. > > The only thing i'm missing compared to the original page is: > * syntax highlighting in code blocks > * title for code blocks > > Are those no longer possible with the markdown approach? (especialy > syntax highlighting)

Re: Documentation

2017-03-31 Thread Stefaan Dutry
The adjusted page looks good. The only thing i'm missing compared to the original page is: * syntax highlighting in code blocks * title for code blocks Are those no longer possible with the markdown approach? (especialy syntax highlighting) ---

Re: Documentation

2017-03-30 Thread Lukasz Lenart
2017-02-15 21:00 GMT+01:00 Lukasz Lenart : > 2017-02-02 20:32 GMT+01:00 Aleksandr Mashchenko : >> Maybe this can help: http://www.viaboxx.de/code/confluence2md/ > > Thanks, I was able to use it but it exports everything directly into > one file :\ but I can still used to start working on new Gettin

Re: Documentation

2017-02-15 Thread Lukasz Lenart
2017-02-02 20:32 GMT+01:00 Aleksandr Mashchenko : > Maybe this can help: http://www.viaboxx.de/code/confluence2md/ Thanks, I was able to use it but it exports everything directly into one file :\ but I can still used to start working on new Getting started guide :) Regards -- Łukasz + 48 606 32

Re: Documentation

2017-02-06 Thread Christoph Nenning
ption to use ssh. Regards, Christoph > From: Lukasz Lenart > To: Struts Developers List , > Date: 04.02.2017 10:02 > Subject: Re: Documentation > > 2017-02-04 8:26 GMT+01:00 Stefaan Dutry : > > I would like to start by saying that i didn't claim my way was better

Re: Documentation

2017-02-04 Thread Lukasz Lenart
2017-02-04 8:26 GMT+01:00 Stefaan Dutry : > I would like to start by saying that i didn't claim my way was better. Yes, I know that, don't get me wrong I just want to know if I am missing something and maybe there is a better way :) > -) why https way > No need to set up ssh keys. (so basicaly

Re: Documentation

2017-02-03 Thread Stefaan Dutry
I would like to start by saying that i didn't claim my way was better. -) why https way No need to set up ssh keys. (so basicaly just lazyness from my part) -) How do you update your fork with changes from origin to avoid a merge commit? Thanks for pointing this out. This is something i did

Re: Documentation

2017-02-03 Thread Lukasz Lenart
2017-02-03 20:19 GMT+01:00 Stefaan Dutry : > Personaly i can understand everything in there. Cool, thanks :) > However i tend to do things differently myself. > > How i usualy work: > * I use clone with https way Why? > 1. Fork the repository to my own account > 2. clone the repository localy,

Re: Documentation

2017-02-03 Thread Stefaan Dutry
Personaly i can understand everything in there. However i tend to do things differently myself. How i usualy work: * I use clone with https way 1. Fork the repository to my own account 2. clone the repository localy, making my fork 'origin' (git clone ) 3. add the original repository as a remote

Re: Documentation

2017-02-03 Thread Lukasz Lenart
2017-02-03 16:06 GMT+01:00 Greg Huber : > How would one resync the github fork with the struts orignal version? You don't have to :) You are always starting off the master from origin Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ -

Re: Documentation

2017-02-03 Thread Greg Huber
How would one resync the github fork with the struts orignal version? On 3 February 2017 at 14:22, Lukasz Lenart wrote: > Can you review this section? > http://struts.apache.org/submitting-patches.html#contributing-with-github > > Is it clear how to prepare a repo, add fork and create branch/P

Re: Documentation

2017-02-03 Thread Lukasz Lenart
Can you review this section? http://struts.apache.org/submitting-patches.html#contributing-with-github Is it clear how to prepare a repo, add fork and create branch/PR? Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2017-02-02 20:32 GMT+01:00 Aleksandr Mashchenko : > Maybe this c

Re: Documentation

2017-02-02 Thread Aleksandr Mashchenko
Maybe this can help: http://www.viaboxx.de/code/confluence2md/ --- Regards, Aleksandr - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org

  1   2   3   4   5   6   >