[jira] [Commented] (OGNL-8) use javacc to generate AST* and OGNLParser Java sources
[
https://issues.apache.org/jira/browse/OGNL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121005#comment-13121005
]
Simone Tripodi commented on OGNL-8:
---
Hi Daniel,
I am worried you got us wrong, let's clarify misunderstanding before it is too
late: there's nothing about lack of merit to patches, Apache projects are 100%
community driven and, according to what Christian (one of the OGNL
mentor/committer) reported in his
[comment|https://issues.apache.org/jira/browse/OGNL-8?focusedCommentId=13119941&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13119941]
{quote}
[...] generates the parsers sources into /target/generated-sources/java and
adds the folder to the classpath [...]
{quote}
It doesn't mean *your* patch cannot be committed, simply needed little
improvements before be committed.
I personally haven't had the time to read both patches, but since Christian is
taking care of it, I strongly believe he is working in the way we all have this
issue fixed, thanks also to the community support that people like you are
volunteering on submitting patches. You will be indeed added in the
contributors list, since you are participating on fixing issues.
You, and smart volunteering people like you, are more than welcome, and we are
happy to see new lifeblood participating on commons components. Please hijack
your energies on submitting patches and take in consideration you are in a
friendly environment! :)
> use javacc to generate AST* and OGNLParser Java sources
> ---
>
> Key: OGNL-8
> URL: https://issues.apache.org/jira/browse/OGNL-8
> Project: OGNL
> Issue Type: Task
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
> Attachments: OGNL-8-keep-custom-AST.patch, OGNL-8.patch,
> patch-ognl-8-v1.patch, patch-ognl-8-v2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MATH-685) Add method "addToEntry" to the "RealVector" interface
Add method "addToEntry" to the "RealVector" interface
-
Key: MATH-685
URL: https://issues.apache.org/jira/browse/MATH-685
Project: Commons Math
Issue Type: Wish
Reporter: Gilles
Assignee: Gilles
Priority: Trivial
Fix For: 3.0
Method "addToEntry":
{code}
m.addToEntry(i, j, addend);
{code}
as a shortcut to:
{code}
m.setEntry(i, j, m.getEntry(i, j) + addend);
{code}
It has been argued (on the "dev" ML) that some functional style would be a
powerful and elegant way to implement a whole set of related functionality
("scale", "scaleAndAdd", etc.). However some simple things (like when the
"addend" depends on "i" and "j") cannot be achieved without writing many more
lines of code.
Method "addToEntry" exists in "RealMatrix". If and when some satisfactory
solution is found in order to remove it there, "RealVector" can always be
aligned with it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VALIDATOR-297) Punycode url is not valid
[ https://issues.apache.org/jira/browse/VALIDATOR-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rytov updated VALIDATOR-297: -- Affects Version/s: 1.3.1 Release > Punycode url is not valid > - > > Key: VALIDATOR-297 > URL: https://issues.apache.org/jira/browse/VALIDATOR-297 > Project: Commons Validator > Issue Type: Bug >Affects Versions: 1.3.1 Release >Reporter: Alexander Rytov > > commons validator doesnt pass the "http://xn--d1abbgf6aiiy.xn--p1ai"; url > because isValidAuthority check on 2-4 symbols top-level domains -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (VALIDATOR-297) Punycode url is not valid
Punycode url is not valid - Key: VALIDATOR-297 URL: https://issues.apache.org/jira/browse/VALIDATOR-297 Project: Commons Validator Issue Type: Bug Reporter: Alexander Rytov commons validator doesnt pass the "http://xn--d1abbgf6aiiy.xn--p1ai"; url because isValidAuthority check on 2-4 symbols top-level domains -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OGNL-8) use javacc to generate AST* and OGNLParser Java sources
[ https://issues.apache.org/jira/browse/OGNL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120985#comment-13120985 ] Daniel Pitts commented on OGNL-8: - This comment may come across as my ego, but I'm more curious why this thread has gone the way it has. My OGNL-8-keep-custom-AST.patch works and I think it could be used as a starting point. Someone can add the eclipse stuff after my patch is applied. It compiles. The tests are successful. The generated files are under target/. Why are we trying to patch with the other patches? What is the perceived merit of the other patches; or what is the lack of merit to my patch? > use javacc to generate AST* and OGNLParser Java sources > --- > > Key: OGNL-8 > URL: https://issues.apache.org/jira/browse/OGNL-8 > Project: OGNL > Issue Type: Task >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Attachments: OGNL-8-keep-custom-AST.patch, OGNL-8.patch, > patch-ognl-8-v1.patch, patch-ognl-8-v2.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DAEMON-219) prunsrv error 1067 and crash on Windows 7
[ https://issues.apache.org/jira/browse/DAEMON-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120923#comment-13120923 ] Gary D. Gregory commented on DAEMON-219: Hello, Is anyone contemplating answers to these questions? Gary > prunsrv error 1067 and crash on Windows 7 > - > > Key: DAEMON-219 > URL: https://issues.apache.org/jira/browse/DAEMON-219 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Affects Versions: 1.0.7 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) > Maven home: C:\Java\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_24, vendor: Sun Microsystems Inc. > Java home: C:\Program Files\Java\jdk1.6.0_24\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" >Reporter: Gary D. Gregory > Attachments: NoKey.PNG, SystemLdeService3.txt, > WER8D3F.tmp.WERInternalMetadata.xml, WERA3BC.tmp.appcompat.txt, > WERA3BD.tmp.mdmp, commons-daemon.2011-10-03.log, install-lde-service.cmd, > ldeservice3-stderr.2011-10-03.log, ldeservice3-stdout.2011-10-03.log > > > I've defined attached cmd file on Windows 7 to install a service. > I try to run the service with "prunsrv //TS/LdeService3" and I get "Commons > Daemon Service Runner has stopped working" > Attaching all details. > Is there more debug logging I can turn on? The current debug output seems > minimal. > This is probably a configuration user error but I cannot tell due to the lack > of logging. > Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OGNL-8) use javacc to generate AST* and OGNLParser Java sources
[
https://issues.apache.org/jira/browse/OGNL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120820#comment-13120820
]
Maurizio Cucchiara commented on OGNL-8:
---
Anyway, the error I got is:
{{Cannot find file to patch: ognl.jjt}}
that it would seem that some generated file, in some way, go under version
control.
> use javacc to generate AST* and OGNLParser Java sources
> ---
>
> Key: OGNL-8
> URL: https://issues.apache.org/jira/browse/OGNL-8
> Project: OGNL
> Issue Type: Task
>Reporter: Olivier Lamy
>Assignee: Olivier Lamy
> Attachments: OGNL-8-keep-custom-AST.patch, OGNL-8.patch,
> patch-ognl-8-v1.patch, patch-ognl-8-v2.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OGNL-8) use javacc to generate AST* and OGNLParser Java sources
[ https://issues.apache.org/jira/browse/OGNL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120816#comment-13120816 ] Maurizio Cucchiara commented on OGNL-8: --- Hi guys, unfortunately I am not able to apply Christian's patch, I guess because I have not any directory called javacc or jtree under /src/main path. Am I missing something? Christian, is it your patch against the trunk? Should I apply another patch before yours? > use javacc to generate AST* and OGNLParser Java sources > --- > > Key: OGNL-8 > URL: https://issues.apache.org/jira/browse/OGNL-8 > Project: OGNL > Issue Type: Task >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Attachments: OGNL-8-keep-custom-AST.patch, OGNL-8.patch, > patch-ognl-8-v1.patch, patch-ognl-8-v2.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
