[jira] Created: (JELLY-276) Parameter name is not taken into account on log tags
Parameter name is not taken into account on log tags
Key: JELLY-276
URL: https://issues.apache.org/jira/browse/JELLY-276
Project: Commons Jelly
Issue Type: Bug
Affects Versions: 1.1
Reporter: Felipe Leme
I wrote the following Jelly script:
retVal: ${retVal}
And the output was:
Apr 24, 2007 1:43:02 PM org.apache.commons.jelly.tags.log.InfoTag doTag
INFO: retVal: SUCCESS
My understanding is that it should print the log name instead of the class name:
Apr 24, 2007 1:43:02 PM test.jelly doTag
INFO: retVal: SUCCESS
But I might be wrong (it might be a commons-logging setup issue).
-- Felipe
PS: it's necessary to add a new component for tag-log ,and also update the
releases (I didn't have access to do so)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (JELLY-204) [junit][PATCH] Better error messages when assertEquals fails
[ http://issues.apache.org/jira/browse/JELLY-204?page=all ]
Felipe Leme closed JELLY-204:
-
Resolution: Fixed
Fixed on SVN.
> [junit][PATCH] Better error messages when assertEquals fails
>
>
> Key: JELLY-204
> URL: http://issues.apache.org/jira/browse/JELLY-204
> Project: jelly
> Type: Improvement
> Reporter: Felipe Leme
> Assignee: Felipe Leme
> Priority: Minor
> Attachments: JELLY-204
>
> When assertEquals fails, only the JEXL representation of the expression is
> shown, not the actual/expected values, which makes it hard do diagnosticate
> what's wrong. For instance:
> Expected expression: 5
> Actual expression: ${oneLineNoNewLine.length().toString()}
> So, I'm sending a patch that would instead show the following (in the example
> above):
> Expected expression: (5)=(5)
> Actual expression: (${oneLineNoNewLine.length().toString()})=(6)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (JELLY-205) adds a new line to files that does not ends with one
[ http://issues.apache.org/jira/browse/JELLY-205?page=all ] Felipe Leme reassigned JELLY-205: - Assign To: Felipe Leme > adds a new line to files that does not ends with one > > > Key: JELLY-205 > URL: http://issues.apache.org/jira/browse/JELLY-205 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Assignee: Felipe Leme > Attachments: JELLY-205.patch, JELLY-205.zip > > See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (JELLY-203) [Util] [PATCH] Test cases for jelly-tags-util has wrong package
[ http://issues.apache.org/jira/browse/JELLY-203?page=all ] Felipe Leme reassigned JELLY-203: - Assign To: Felipe Leme > [Util] [PATCH] Test cases for jelly-tags-util has wrong package > --- > > Key: JELLY-203 > URL: http://issues.apache.org/jira/browse/JELLY-203 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Assignee: Felipe Leme > Priority: Minor > Attachments: JELLY-203 > > Some of the test cases uses the class org.apache.commons.jelly.util.Customer, > but that class is located at org/apache/commons/jelly/tags/util. I'm > attaching a patch that fixes this issue. > . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (JELLY-204) [junit][PATCH] Better error messages when assertEquals fails
[ http://issues.apache.org/jira/browse/JELLY-204?page=all ]
Felipe Leme reassigned JELLY-204:
-
Assign To: Felipe Leme
> [junit][PATCH] Better error messages when assertEquals fails
>
>
> Key: JELLY-204
> URL: http://issues.apache.org/jira/browse/JELLY-204
> Project: jelly
> Type: Improvement
> Reporter: Felipe Leme
> Assignee: Felipe Leme
> Priority: Minor
> Attachments: JELLY-204
>
> When assertEquals fails, only the JEXL representation of the expression is
> shown, not the actual/expected values, which makes it hard do diagnosticate
> what's wrong. For instance:
> Expected expression: 5
> Actual expression: ${oneLineNoNewLine.length().toString()}
> So, I'm sending a patch that would instead show the following (in the example
> above):
> Expected expression: (5)=(5)
> Actual expression: (${oneLineNoNewLine.length().toString()})=(6)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-205) adds a new line to files that does not ends with one
[ http://issues.apache.org/jira/browse/JELLY-205?page=comments#action_12373426 ] Felipe Leme commented on JELLY-205: --- Hi Paul, Actually, I've committed the test cases and the fix itself (I'm not a Commons committer, but a Jakarta committer...); what I couldn't do was to mark the issue as closed (I don't have such permission on Jira). -- Felipe > adds a new line to files that does not ends with one > > > Key: JELLY-205 > URL: http://issues.apache.org/jira/browse/JELLY-205 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Attachments: JELLY-205.patch, JELLY-205.zip > > See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-173) Support for XML Schema
[ http://issues.apache.org/jira/browse/JELLY-173?page=comments#action_12373221 ] Felipe Leme commented on JELLY-173: --- HIi Paul, I haven't had a chance to give it a try yet, but I have a question: what's Jelly current status? I mean, are there any plans to release new version of the taglibs? -- Felipe > Support for XML Schema > -- > > Key: JELLY-173 > URL: http://issues.apache.org/jira/browse/JELLY-173 > Project: jelly > Type: New Feature > Components: taglib.xml > Reporter: Felipe Leme > > There is a bug on the maven-ear-plugin regarding support to genera > In order to fix a maven-ear-plugin bug > (http://jira.codehaus.org/browse/MPEAR-30), I need to generate a XML-Schema > based XML document, but looks like the taglib doesn't allow it. > I can see 2 possible solutions: > 1.Add more attributes to the tag. Example: > http://java.sun.com/xml/ns/j2ee"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; > version="1.4"> > 2.Create a new tag specifically for this purpose. Example: > http://java.sun.com/xml/ns/j2ee"; > xsi="http://www.w3.org/2001/XMLSchema-instance"; > schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; > version="1.4"> > If there is another alternative, please let me know. > -- Felipe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-173) Support for XML Schema
[ http://issues.apache.org/jira/browse/JELLY-173?page=comments#action_12373220 ] Felipe Leme commented on JELLY-173: --- HIi Paul, I haven't had a chance to give it a try yet, but I have a question: what's Jelly current status? I mean, are there any plans to release new version of the taglibs? -- Felipe > Support for XML Schema > -- > > Key: JELLY-173 > URL: http://issues.apache.org/jira/browse/JELLY-173 > Project: jelly > Type: New Feature > Components: taglib.xml > Reporter: Felipe Leme > > There is a bug on the maven-ear-plugin regarding support to genera > In order to fix a maven-ear-plugin bug > (http://jira.codehaus.org/browse/MPEAR-30), I need to generate a XML-Schema > based XML document, but looks like the taglib doesn't allow it. > I can see 2 possible solutions: > 1.Add more attributes to the tag. Example: > http://java.sun.com/xml/ns/j2ee"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; > version="1.4"> > 2.Create a new tag specifically for this purpose. Example: > http://java.sun.com/xml/ns/j2ee"; > xsi="http://www.w3.org/2001/XMLSchema-instance"; > schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; > version="1.4"> > If there is another alternative, please let me know. > -- Felipe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-204) [junit][PATCH] Better error messages when assertEquals fails
[
http://issues.apache.org/jira/browse/JELLY-204?page=comments#action_12373218 ]
Felipe Leme commented on JELLY-204:
---
Fixed (thanks to the new 'one Jakarta Karma to rule them all' policy :-), but I
don't have the permissions to close the Jira issue
> [junit][PATCH] Better error messages when assertEquals fails
>
>
> Key: JELLY-204
> URL: http://issues.apache.org/jira/browse/JELLY-204
> Project: jelly
> Type: Improvement
> Reporter: Felipe Leme
> Priority: Minor
> Attachments: JELLY-204
>
> When assertEquals fails, only the JEXL representation of the expression is
> shown, not the actual/expected values, which makes it hard do diagnosticate
> what's wrong. For instance:
> Expected expression: 5
> Actual expression: ${oneLineNoNewLine.length().toString()}
> So, I'm sending a patch that would instead show the following (in the example
> above):
> Expected expression: (5)=(5)
> Actual expression: (${oneLineNoNewLine.length().toString()})=(6)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-205) adds a new line to files that does not ends with one
[ http://issues.apache.org/jira/browse/JELLY-205?page=comments#action_12373217 ] Felipe Leme commented on JELLY-205: --- Fixed (thanks to the new 'one Jakarta Karma to rule them all' policy :-), but I don't have the permissions to close the Jira issue > adds a new line to files that does not ends with one > > > Key: JELLY-205 > URL: http://issues.apache.org/jira/browse/JELLY-205 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Attachments: JELLY-205.patch, JELLY-205.zip > > See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-203) [Util] [PATCH] Test cases for jelly-tags-util has wrong package
[ http://issues.apache.org/jira/browse/JELLY-203?page=comments#action_12373216 ] Felipe Leme commented on JELLY-203: --- Fixed (thanks to the new 'one Jakarta Karma to rule them all' policy :-), but I don't have the permissions to close the Jira issue > [Util] [PATCH] Test cases for jelly-tags-util has wrong package > --- > > Key: JELLY-203 > URL: http://issues.apache.org/jira/browse/JELLY-203 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Priority: Minor > Attachments: JELLY-203 > > Some of the test cases uses the class org.apache.commons.jelly.util.Customer, > but that class is located at org/apache/commons/jelly/tags/util. I'm > attaching a patch that fixes this issue. > . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-194) New tag that copy text files replacing Jelly properties
[
http://issues.apache.org/jira/browse/JELLY-194?page=comments#action_12368040 ]
Felipe Leme commented on JELLY-194:
---
Any clue when/if these issues (JELLY-194, JELLY-203, JELLY-204 and JELLY-205)
will make it to the codebase?
In particular, I think this feature is very useful - everytime I start a
project in a new company, I need to create a small project only to provide such
tag...
> New tag that copy text files replacing Jelly properties
> ---
>
> Key: JELLY-194
> URL: http://issues.apache.org/jira/browse/JELLY-194
> Project: jelly
> Type: New Feature
> Components: taglib.util
> Versions: 1.0
> Reporter: Felipe Leme
> Attachments: JELLY-194.patch1, JELLY-194.patch2
>
> Hi,
> It would be nice if there was a Jelly tag similar to that would
> copy text files replacing the Jelly properties.
> For instance, I need to copy a datasource XML definition to JBoss before
> running Cactus (on maven), but each developer in my project has its own
> database schema. So, I could have a XML file like this:
>
>
> ${ds.username}
> ${ds.password}
>
> And then something like this on maven.xml:
>
> toFile="${env.JBOSS_HOME}/server/default/deploy"/>
>
> If you think such tag is useful (and hence would be incorporated on Jelly), I
> could write the tag and test cases and then submit a patch (I'm just not sure
> what's the best name for it).
> -- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-173) Support for XML Schema
[ http://issues.apache.org/jira/browse/JELLY-173?page=comments#action_12316150 ] Felipe Leme commented on JELLY-173: --- Hi Paul, Ok, I will try, although I can't promisse when. Anyway, which version of Jelly should I try? 1.0 or the cvs/svn code? Tks, -- Felipe > Support for XML Schema > -- > > Key: JELLY-173 > URL: http://issues.apache.org/jira/browse/JELLY-173 > Project: jelly > Type: New Feature > Components: taglib.xml > Reporter: Felipe Leme > > There is a bug on the maven-ear-plugin regarding support to genera > In order to fix a maven-ear-plugin bug > (http://jira.codehaus.org/browse/MPEAR-30), I need to generate a XML-Schema > based XML document, but looks like the taglib doesn't allow it. > I can see 2 possible solutions: > 1.Add more attributes to the tag. Example: > http://java.sun.com/xml/ns/j2ee"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; > version="1.4"> > 2.Create a new tag specifically for this purpose. Example: > http://java.sun.com/xml/ns/j2ee"; > xsi="http://www.w3.org/2001/XMLSchema-instance"; > schemaLocation="http://java.sun.com/xml/ns/j2ee > http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; > version="1.4"> > If there is another alternative, please let me know. > -- Felipe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-205) adds a new line to files that does not ends with one
[ http://issues.apache.org/jira/browse/JELLY-205?page=comments#action_12314164 ] Felipe Leme commented on JELLY-205: --- Hello all, Any news on the status of this bug (and also JELLY_205)? > adds a new line to files that does not ends with one > > > Key: JELLY-205 > URL: http://issues.apache.org/jira/browse/JELLY-205 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Attachments: JELLY-205.patch, JELLY-205.zip > > See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-194) New tag that copy text files replacing Jelly properties
[ http://issues.apache.org/jira/browse/JELLY-194?page=history ]
Felipe Leme updated JELLY-194:
--
Attachment: JELLY-194.patch2
Full patch, where the new tag (CopyTextTag) and the existing LoadTextTag now
derives from AbstractTextTag.
The patch also contains the cumulative fixes for JELLY-203 and JELLY-205
(although neither
this patch nor the patches for these other issues include changes to
xdocs/changes.xml).
-- Felipe
> New tag that copy text files replacing Jelly properties
> ---
>
> Key: JELLY-194
> URL: http://issues.apache.org/jira/browse/JELLY-194
> Project: jelly
> Type: New Feature
> Components: taglib.util
> Versions: 1.0
> Reporter: Felipe Leme
> Attachments: JELLY-194.patch1, JELLY-194.patch2
>
> Hi,
> It would be nice if there was a Jelly tag similar to that would
> copy text files replacing the Jelly properties.
> For instance, I need to copy a datasource XML definition to JBoss before
> running Cactus (on maven), but each developer in my project has its own
> database schema. So, I could have a XML file like this:
>
>
> ${ds.username}
> ${ds.password}
>
> And then something like this on maven.xml:
>
> toFile="${env.JBOSS_HOME}/server/default/deploy"/>
>
> If you think such tag is useful (and hence would be incorporated on Jelly), I
> could write the tag and test cases and then submit a patch (I'm just not sure
> what's the best name for it).
> -- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-194) New tag that copy text files replacing Jelly properties
[ http://issues.apache.org/jira/browse/JELLY-194?page=history ]
Felipe Leme updated JELLY-194:
--
Attachment: JELLY-194.patch1
dIon,
Using or is not enough because these tags would
try to
execute the text as a Jelly script, instead of simply returning the text with
the expressions
evaluated.
So, I'm providing an initial patch that adds a new tag called CopyText (I will
provide another patch
where this tag and LoadText extends from a common class).
> New tag that copy text files replacing Jelly properties
> ---
>
> Key: JELLY-194
> URL: http://issues.apache.org/jira/browse/JELLY-194
> Project: jelly
> Type: New Feature
> Components: taglib.util
> Versions: 1.0
> Reporter: Felipe Leme
> Attachments: JELLY-194.patch1
>
> Hi,
> It would be nice if there was a Jelly tag similar to that would
> copy text files replacing the Jelly properties.
> For instance, I need to copy a datasource XML definition to JBoss before
> running Cactus (on maven), but each developer in my project has its own
> database schema. So, I could have a XML file like this:
>
>
> ${ds.username}
> ${ds.password}
>
> And then something like this on maven.xml:
>
> toFile="${env.JBOSS_HOME}/server/default/deploy"/>
>
> If you think such tag is useful (and hence would be incorporated on Jelly), I
> could write the tag and test cases and then submit a patch (I'm just not sure
> what's the best name for it).
> -- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-205) adds a new line to files that does not ends with one
[ http://issues.apache.org/jira/browse/JELLY-205?page=history ] Felipe Leme updated JELLY-205: -- Attachment: JELLY-205.patch Here is a patch with the fix and more test cases. PS: this patch also include the fix for JELLY_203 > adds a new line to files that does not ends with one > > > Key: JELLY-205 > URL: http://issues.apache.org/jira/browse/JELLY-205 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Attachments: JELLY-205.patch, JELLY-205.zip > > See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-205) adds a new line to files that does not ends with one
[ http://issues.apache.org/jira/browse/JELLY-205?page=history ] Felipe Leme updated JELLY-205: -- Attachment: JELLY-205.zip > adds a new line to files that does not ends with one > > > Key: JELLY-205 > URL: http://issues.apache.org/jira/browse/JELLY-205 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Attachments: JELLY-205.zip > > See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (JELLY-205) adds a new line to files that does not ends with one
adds a new line to files that does not ends with one Key: JELLY-205 URL: http://issues.apache.org/jira/browse/JELLY-205 Project: jelly Type: Bug Components: taglib.util Reporter: Felipe Leme Attachments: JELLY-205.zip See attached test case (I will try to fix it and provide a full patch). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-204) [junit][PATCH] Better error messages when assertEquals fails
[ http://issues.apache.org/jira/browse/JELLY-204?page=history ]
Felipe Leme updated JELLY-204:
--
Attachment: JELLY-204
> [junit][PATCH] Better error messages when assertEquals fails
>
>
> Key: JELLY-204
> URL: http://issues.apache.org/jira/browse/JELLY-204
> Project: jelly
> Type: Improvement
> Reporter: Felipe Leme
> Priority: Minor
> Attachments: JELLY-204
>
> When assertEquals fails, only the JEXL representation of the expression is
> shown, not the actual/expected values, which makes it hard do diagnosticate
> what's wrong. For instance:
> Expected expression: 5
> Actual expression: ${oneLineNoNewLine.length().toString()}
> So, I'm sending a patch that would instead show the following (in the example
> above):
> Expected expression: (5)=(5)
> Actual expression: (${oneLineNoNewLine.length().toString()})=(6)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (JELLY-204) [junit][PATCH] Better error messages when assertEquals fails
[junit][PATCH] Better error messages when assertEquals fails
Key: JELLY-204
URL: http://issues.apache.org/jira/browse/JELLY-204
Project: jelly
Type: Improvement
Reporter: Felipe Leme
Priority: Minor
Attachments: JELLY-204
When assertEquals fails, only the JEXL representation of the expression is
shown, not the actual/expected values, which makes it hard do diagnosticate
what's wrong. For instance:
Expected expression: 5
Actual expression: ${oneLineNoNewLine.length().toString()}
So, I'm sending a patch that would instead show the following (in the example
above):
Expected expression: (5)=(5)
Actual expression: (${oneLineNoNewLine.length().toString()})=(6)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (JELLY-203) [Util] [PATCH] Test cases for jelly-tags-util has wrong package
[Util] [PATCH] Test cases for jelly-tags-util has wrong package --- Key: JELLY-203 URL: http://issues.apache.org/jira/browse/JELLY-203 Project: jelly Type: Bug Components: taglib.util Reporter: Felipe Leme Priority: Minor Attachments: JELLY-203 Some of the test cases uses the class org.apache.commons.jelly.util.Customer, but that class is located at org/apache/commons/jelly/tags/util. I'm attaching a patch that fixes this issue. . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (JELLY-203) [Util] [PATCH] Test cases for jelly-tags-util has wrong package
[ http://issues.apache.org/jira/browse/JELLY-203?page=history ] Felipe Leme updated JELLY-203: -- Attachment: JELLY-203 > [Util] [PATCH] Test cases for jelly-tags-util has wrong package > --- > > Key: JELLY-203 > URL: http://issues.apache.org/jira/browse/JELLY-203 > Project: jelly > Type: Bug > Components: taglib.util > Reporter: Felipe Leme > Priority: Minor > Attachments: JELLY-203 > > Some of the test cases uses the class org.apache.commons.jelly.util.Customer, > but that class is located at org/apache/commons/jelly/tags/util. I'm > attaching a patch that fixes this issue. > . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-194) New tag that copy text files replacing Jelly properties
[
http://issues.apache.org/jira/browse/JELLY-194?page=comments#action_57468 ]
Felipe Leme commented on JELLY-194:
---
Ok, here is how to implement it using "pure" Jelly tags:
I still think a tag would be useful though (or at least a FAQ entry somewhere
:-)
-- Felipe
> New tag that copy text files replacing Jelly properties
> ---
>
> Key: JELLY-194
> URL: http://issues.apache.org/jira/browse/JELLY-194
> Project: jelly
> Type: New Feature
> Components: taglib.util
> Versions: 1.0
> Reporter: Felipe Leme
>
> Hi,
> It would be nice if there was a Jelly tag similar to that would
> copy text files replacing the Jelly properties.
> For instance, I need to copy a datasource XML definition to JBoss before
> running Cactus (on maven), but each developer in my project has its own
> database schema. So, I could have a XML file like this:
>
>
> ${ds.username}
> ${ds.password}
>
> And then something like this on maven.xml:
>
> toFile="${env.JBOSS_HOME}/server/default/deploy"/>
>
> If you think such tag is useful (and hence would be incorporated on Jelly), I
> could write the tag and test cases and then submit a patch (I'm just not sure
> what's the best name for it).
> -- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-194) New tag that copy text files replacing Jelly properties
[
http://issues.apache.org/jira/browse/JELLY-194?page=comments#action_57457 ]
Felipe Leme commented on JELLY-194:
---
dIon,
Yes, it probably can be done using a combination of other tags (in my case, I'm
using Ant replace, i.e., I have @USERNAME@ and @PASSWORD@ in the XML file and
use ant tags inside Jelly to replace the values).
But I think it would be more useful/reusable if we could do everything in just
one operation (well, at least I think that's a common operation).
-- Felipe
> New tag that copy text files replacing Jelly properties
> ---
>
> Key: JELLY-194
> URL: http://issues.apache.org/jira/browse/JELLY-194
> Project: jelly
> Type: New Feature
> Components: taglib.util
> Versions: 1.0
> Reporter: Felipe Leme
>
> Hi,
> It would be nice if there was a Jelly tag similar to that would
> copy text files replacing the Jelly properties.
> For instance, I need to copy a datasource XML definition to JBoss before
> running Cactus (on maven), but each developer in my project has its own
> database schema. So, I could have a XML file like this:
>
>
> ${ds.username}
> ${ds.password}
>
> And then something like this on maven.xml:
>
> toFile="${env.JBOSS_HOME}/server/default/deploy"/>
>
> If you think such tag is useful (and hence would be incorporated on Jelly), I
> could write the tag and test cases and then submit a patch (I'm just not sure
> what's the best name for it).
> -- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (JELLY-194) New tag that copy text files replacing Jelly properties
New tag that copy text files replacing Jelly properties
---
Key: JELLY-194
URL: http://issues.apache.org/jira/browse/JELLY-194
Project: jelly
Type: New Feature
Components: taglib.util
Versions: 1.0
Reporter: Felipe Leme
Hi,
It would be nice if there was a Jelly tag similar to that would copy
text files replacing the Jelly properties.
For instance, I need to copy a datasource XML definition to JBoss before
running Cactus (on maven), but each developer in my project has its own
database schema. So, I could have a XML file like this:
${ds.username}
${ds.password}
And then something like this on maven.xml:
If you think such tag is useful (and hence would be incorporated on Jelly), I
could write the tag and test cases and then submit a patch (I'm just not sure
what's the best name for it).
-- Felipe
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (JELLY-173) Support for XML Schema
Support for XML Schema -- Key: JELLY-173 URL: http://nagoya.apache.org/jira/browse/JELLY-173 Project: jelly Type: New Feature Components: taglib.xml Reporter: Felipe Leme There is a bug on the maven-ear-plugin regarding support to genera In order to fix a maven-ear-plugin bug (http://jira.codehaus.org/browse/MPEAR-30), I need to generate a XML-Schema based XML document, but looks like the taglib doesn't allow it. I can see 2 possible solutions: 1.Add more attributes to the tag. Example: http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4"> 2.Create a new tag specifically for this purpose. Example: http://java.sun.com/xml/ns/j2ee"; xsi="http://www.w3.org/2001/XMLSchema-instance"; schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"; version="1.4"> If there is another alternative, please let me know. -- Felipe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (JELLY-157) New tag that generates sorted collection
[ http://issues.apache.org/jira/browse/JELLY-157?page=comments#action_54678 ] Felipe Leme commented on JELLY-157: --- Hi Dion, Thanks for implementing it. BTW, could you please notify when a new version will be available on ibiblio (even if its a timestamped release)? -- Felipe > New tag that generates sorted collection > > > Key: JELLY-157 > URL: http://issues.apache.org/jira/browse/JELLY-157 > Project: jelly > Type: New Feature > Components: taglib.util > Versions: 1.0 > Reporter: Felipe Leme > Priority: Minor > Fix For: 1.0 > > A cool tag would be one that takes one collection (or map) and returns a new > collection/map, sorted by a given property (on each of the collection's elements). > This tag could be used, for instance, on Maven's multiproject plugin to generate a > sorted report of sub-projects: > sortingProperty="name"/> > Such tag shouldn't be hard to implement, but I haven't the time to do the full job > right now (i.e., writing the tag, test cases, documentation, etc...), but I can give > it a shot in the near future, if there is enough interested on such feature (in > other words, if someone is willing to commit the changes :-). > -- Felipe -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
