GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts2/pull/10
DeprecationInterceptor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/strutsathon/struts2 trunk
Alternatively you can review and apply
Github user lukaszlenart closed the pull request at:
https://github.com/apache/struts2/pull/10
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
Github user lukaszlenart closed the pull request at:
https://github.com/apache/struts/pull/1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this feature
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/2
Restricts direct access to JSP files
This PR moves all JSP files in example apps under `WEB-INF` and adds
security constraints to `web.xml` to avoid accessing JSP files directly. Thus
Github user lukaszlenart closed the pull request at:
https://github.com/apache/struts/pull/2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/3
Extends UrlValidator to support custom regex
This PR is related to
[WW-4198](https://issues.apache.org/jira/browse/WW-4198)
You can merge this pull request into a Git repository by running
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/4
WW-4187 correctly identify protocols to recognise if URL is path
This is related to [WW-4187](https://issues.apache.org/jira/browse/WW-4187)
You can merge this pull request into a Git repository
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/5
Feature: use JavaScript to support multiple actions instead action: prefix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/struts
Github user lukaszlenart closed the pull request at:
https://github.com/apache/struts/pull/3
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user lukaszlenart closed the pull request at:
https://github.com/apache/struts/pull/4
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38027870
Have you tested that?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/4#issuecomment-38027847
PR applied!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10740672
--- Diff: core/src/main/resources/template/simple/select.ftl ---
@@ -69,7 +69,13 @@
<#assign itemKey = stack.findValue(&
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10740666
--- Diff: core/src/main/resources/template/simple/radiomap.ftl ---
@@ -27,7 +27,13 @@
<#assign itemKey = stack.findValue(&
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10740655
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart closed the pull request at:
https://github.com/apache/struts/pull/5
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/5#issuecomment-38098723
Changes merged into develop
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10768356
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10769526
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10770140
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10771172
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10771988
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10784514
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10784708
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38155805
Where is JIRA issue for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38199004
You must have a strange setup, though. `XmlConfigurationProvider` is
instantiated per each configuration file, i.e. `struts-default.xml` (one),
`struts-plugin.xml
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38220286
What app do you use to check that? Simple struts2-blank is enough to
investigate that?
---
If your project is set up for it, you can reply to this email and have
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38222608
Ok, I will double check but it looks like this needs further refactoring -
it can be done later
---
If your project is set up for it, you can reply to this email and
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/7#discussion_r10886002
--- Diff: core/src/main/resources/template/simple/checkboxlist.ftl ---
@@ -29,7 +29,13 @@
<#else>
<#assig
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/7#issuecomment-38449857
Ping!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38965395
Whoa! You are right :-) `XmlConfigurationProvider` is created per config
file, eg. `struts-plugin.xml` but we can have many such files on classpath,
that's why
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/6#issuecomment-38966472
Please close this PR, patch applied.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/8
HttpInterceptor
New annotation and interceptor to allow limit access to action based on
used http request type, ie:
@GetOnly
public class MyAction extends ActionSupport
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/9#issuecomment-41319238
Can you open it against `develop` branch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/8#issuecomment-41368084
You don't have to use `@Action` annotation to convert class/method into
action, the Convention plugin can do it for you. Another thing is that you can
use wil
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/8#issuecomment-41376393
But then you limit usage of it only to the Convention plugin based
applications. Even with extending DTD and adding `httpMethod` to ``
you will have limitations of
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/11
Security: exclude Object's class methods
This fix is a follow up of the latest security issues discovered with
`ParametersInterceptor` to allow access object's `getClass` metho
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/10#issuecomment-41459539
Edit this Pull Request and change `source`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/10#issuecomment-41459530
You don't have to have `develop` branch, use your `master` branch and
`develop` branch from Struts
---
If your project is set up for it, you can reply to this
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/10#issuecomment-41459932
Step-by-step guideline
https://help.github.com/articles/creating-a-pull-request
---
If your project is set up for it, you can reply to this email and have your
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/8#issuecomment-41531020
Let's treat this as a Proof-of-Concept and if will work we can think about
further extensions (like extending `@Action` annotation)
---
If your project is set u
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/8#issuecomment-41649420
Ok, I wasn't sure about naming as well, I will rename the annotations to
`@HttpGet`, `@HttpPost`, etc
---
If your project is set up for it, you can reply to
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/8#issuecomment-41650283
Good questions, will check that. I have added `@AllowedMethod({GET, POST,
PUT})` to cover that case
---
If your project is set up for it, you can reply to this email
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/7#issuecomment-43715553
I think this is ready? Anything else to add?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-45061200
I'm not sure if this is the best idea, I mean hardcoding styles in tags -
they will always take precedence over CSS classes.
---
If your project is set up f
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-45182042
It can stay as is for now IMO, we can think about that with S2.5 or S3 -
remove hardcoded styles and used CSS classes instead. Then `simple` theme won't
provid
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-45182314
> BTW what is table.ftl and where it is used?
First I thought it's used by `debug.ftl` but I've checked that and it's not
- so it's so
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/15#issuecomment-45664015
Two issues with this PR:
- open a JIRA ticket and reference this PR from it
- open PR against `develop` branch, not `master`
---
If your project is set up
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/10#issuecomment-46402105
@dwaite yes, all the commits from your `develop` branch will be included,
should I skip changes to the `ChainingInterceptor`?
---
If your project is set up for it
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/12#discussion_r13902929
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/ognl/OgnlUtil.java ---
@@ -279,7 +279,8 @@ public Object compile(String expression) throws
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/17#issuecomment-46938658
Can you create JIRA ticket and link this PR to it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/17#issuecomment-46940928
Done :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/7#issuecomment-47312080
:eyes:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/18
Feature: list value localization
This is continuation of @abrin work started in #7
Closes [WW-4295](https://issues.apache.org/jira/browse/WW-4295)
Closes #7
You can merge this
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/7#issuecomment-47332091
The work continue in #18
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/18#issuecomment-47332904
@abrin can you review the changes or test them locally? I don't see value
in the changes right now as I don't now how do you want to use them. Check the
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-47334012
Is this ready for another shot?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-47358634
I'm going to postpone this PR, it will break Dojo plugin, we can include
the changes in S2.5 when Dojo plugin will be dropped as well.
---
If your project is s
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/16#discussion_r14322940
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/config/providers/XmlConfigurationProvider.java
---
@@ -425,7 +427,7 @@ protected void
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/19#issuecomment-50593699
Two issues:
- please open this PR against `develop` branch, not `master`
- please register an issue in JIRA and reference this branch from it
https
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575101
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575148
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -893,6 +889,10 @@ public int hashCode
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575196
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575215
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575275
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -246,35 +245,32 @@ public static String findDefaultText
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575748
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15575786
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15576953
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15633237
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/util/LocalizedTextUtil.java ---
@@ -136,13 +129,21 @@ public static void setReloadBundles
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/20#discussion_r15775329
--- Diff:
xwork-core/src/test/java/com/opensymphony/xwork2/util/LocalizedTextUtilTest.java
---
@@ -133,6 +133,11 @@ public void testDefaultMessage
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/20#issuecomment-51105487
This looks good, one tiny issue and I'm down ;-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/20#issuecomment-51437103
I assume it is ready to go... let's merge then!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/20#issuecomment-52092295
`DefaultBeanSelectionProviderTest` fails with:
```
junit.framework.ComparisonFailure: null
Expected :Replaced message for token tag
Actual :The form
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/21
Locale aware converters
Basically this PR introduces new converters which are `Locale` aware - they
will convert values based on current `Locale` provided by `LocaleProvider`
This
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/20#issuecomment-52599336
Ok, great! I will take a shot ;-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/23#issuecomment-53529533
Please create issue in JIRA and reference this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-53678677
Did you create appropriated JIRA ticket?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/14#issuecomment-53678964
https://issues.apache.org/jira/browse/WW-4355 :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/8#issuecomment-56310096
I've moved this branch into my fork - will work on that there
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/25
Http interceptor
This is continuation of work performed in #8
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lukaszlenart/struts http
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/25#issuecomment-56311272
@jogep @davelnewton this the final version - I've extended interceptor to
support multiple annotation on the same method, see
[here](https://github.com/lukaszl
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/25#issuecomment-56311503
This issues is related to https://issues.apache.org/jira/browse/WW-4404
---
If your project is set up for it, you can reply to this email and have your
reply appear
GitHub user lukaszlenart opened a pull request:
https://github.com/apache/struts/pull/26
Use js to support multiple buttons
WIP
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lukaszlenart/struts
use-js-to-support-multiple
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/29#issuecomment-62716399
Can you create JIRA ticket and link this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/29#issuecomment-62719415
All these builds issue are unrelated to this PR ;-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/30#issuecomment-62855204
Please create JIRA ticket and reference this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/31#issuecomment-66033091
Please create appropriate JIRA ticket and link it here
https://issues.apache.org/jira/browse/WW
---
If your project is set up for it, you can reply to this email
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/32#discussion_r21548312
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/ognl/OgnlValueStack.java ---
@@ -351,6 +351,8 @@ private Object tryFindValue(String expr
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/31#issuecomment-67930144
This won't work as Struts uses Java6 but I have added a new plugin to
support Java 8 so it can incorporated in that plugin
---
If your project is set up for it
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/32#discussion_r22206741
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/ognl/OgnlValueStack.java ---
@@ -351,6 +352,7 @@ private Object tryFindValue(String expr
Github user lukaszlenart commented on a diff in the pull request:
https://github.com/apache/struts/pull/32#discussion_r22218137
--- Diff:
xwork-core/src/main/java/com/opensymphony/xwork2/ognl/OgnlValueStack.java ---
@@ -351,6 +352,7 @@ private Object tryFindValue(String expr
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/24#issuecomment-68246309
@aleksandr-m can you close this PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/24#issuecomment-68297311
Thanks! I will write down `how to merge PRs` guide for committers :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/35#issuecomment-74625231
I'm not sure if this is a good solution, can you provide more details?
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/35#issuecomment-77833815
What I meant is that if `ValueStack` is missing in context something wrong
happened, so solution to null-check is error-prone :)
---
If your project is set up for
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/35#issuecomment-78003822
That's the case, can you explain what you mean by non-struts2 context?
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/35#issuecomment-78242017
So you can use a `StubValueContext` like this one
```java
public class StubValueStack implements ValueStack {
Map ctx = new HashMap
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/35#issuecomment-78426250
But you cannot pass `null` and expect that it will work properly, if you
want such behaviour add method with signature that doesn't expect `ValueStack`
---
If
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/31#issuecomment-104373960
Please re-open this PR against `master` branch
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user lukaszlenart commented on the pull request:
https://github.com/apache/struts/pull/35#issuecomment-104374138
Please re-open this PR against `master` branch
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
1 - 100 of 381 matches
Mail list logo
