[jira] Closed: (DOXIASITETOOLS-39) Velocity > 1.5 can't parse default-site.vm
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig closed DOXIASITETOOLS-39. Resolution: Fixed Fix Version/s: 1.2 This has fixed the Gump build of doxia-site-renderer. It won't help with the other problems until the Maven plugins Cactus and other projects use have been updated, but this is not your business. As for the "fix version", I assumed trunk is going to be 1.2 one day. Thanks Lukas > Velocity > 1.5 can't parse default-site.vm > -- > > Key: DOXIASITETOOLS-39 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-39 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Doc renderer, Site renderer >Affects Versions: 1.0, 1.1 >Reporter: Stefan Bodewig >Priority: Minor > Fix For: 1.2 > > > This is an issue detected by Gump which runs Maven builds but replaces > dependencies with the trunk versions of things built by Gump rather than the > version a project asks for. > The Cargo build - see > http://gump.zones.apache.org/gump/test/cargo/cargo/gump_work/build_cargo_cargo.html > - fails because Velocity doesn't like the line > #set ( $documentHeader = "" ) > because \" is not an escape sequence for Velocity (anymore?). > I've taken this to the velocity list - > http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3c87ocdlps07@v35516.1blu.de%3e > - and received the feedback that backslash > escaping was not supported - and likely never has been - and you should > either use single > quotes inside the double quotes or use something like > #set( $Q = '"' ) > #set ( $documentHeader = " I realize that it probably works for you right now using Velocity 1.5, that's > why I used Improvement rather than bug as category. Still it may be worth to > find a solution that works for the version of Velocity you want to use as > well as future versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIASITETOOLS-39) Velocity > 1.5 can't parse default-site.vm
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231587#action_231587 ] Stefan Bodewig commented on DOXIASITETOOLS-39: -- I agree single quotes are a natural solution. Whether it is worth upgrading, I don't know. It's not as if upgrading from Doxia 1.0 to 1.1 would be painless ;-) More seriously,the reason I went to the Velocity developer list first was that I intended to get a backwards incompatibility fixed before the final release. In this case I think the Velocity devs have a point, though, in that the current template simply isn't really correct. Gump is intended to be there to catch this type of changes before they become final, it is just that not enough projects are actively participating to make it a success. > Velocity > 1.5 can't parse default-site.vm > -- > > Key: DOXIASITETOOLS-39 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-39 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Doc renderer, Site renderer >Affects Versions: 1.0, 1.1 >Reporter: Stefan Bodewig >Priority: Minor > > This is an issue detected by Gump which runs Maven builds but replaces > dependencies with the trunk versions of things built by Gump rather than the > version a project asks for. > The Cargo build - see > http://gump.zones.apache.org/gump/test/cargo/cargo/gump_work/build_cargo_cargo.html > - fails because Velocity doesn't like the line > #set ( $documentHeader = "" ) > because \" is not an escape sequence for Velocity (anymore?). > I've taken this to the velocity list - > http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3c87ocdlps07@v35516.1blu.de%3e > - and received the feedback that backslash > escaping was not supported - and likely never has been - and you should > either use single > quotes inside the double quotes or use something like > #set( $Q = '"' ) > #set ( $documentHeader = " I realize that it probably works for you right now using Velocity 1.5, that's > why I used Improvement rather than bug as category. Still it may be worth to > find a solution that works for the version of Velocity you want to use as > well as future versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIASITETOOLS-39) Velocity > 1.5 can't parse default-site.vm
[
http://jira.codehaus.org/browse/DOXIASITETOOLS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231568#action_231568
]
Stefan Bodewig commented on DOXIASITETOOLS-39:
--
Lukas, I fully understand your sentiment and in fact this is what I'd ask if
anybody reported a bug that I cannot reproduce in my projects as well. The
problem here is, I am not a Doxia user, nor a Maven user - I wouldn't even know
where to start if I tried to provide a test.
Let's take this a few steps backwards.
First, this is what the template reads:
{noformat}
#set ( $documentHeader = "" )
#set ( $documentHeader = $documentHeader.replaceAll( "\\", "" ) )
{noformat}
The first line tries to create an XML declaration with double-quotes and tries
to escape the double-quotes with a backslash. The Velocity developers say
backslashes have never worked as escape character for double-quotes in string
literals and I trust them. At least they don't work in Velocity 1.7.
The second line strips backslashes. If the backslash escaping of the first
line worked, there wouldn't be any backslash in $documentHeader and the line
was unneeded. I take this as a hint that the first line really doesn't work as
expected and the second line is a workaround to get what you really wanted.
The first approach suggested to me (in the initial description) using $Q is
supposed to work with any version of Velocity, doubling the double-quotes may
require a newer version of Velocity. Either approach should make the second
line unnessary,
The current template doesn't work with Velocity 1.7 since they now use an
explicit grammer and ANTLR and the template violates the grammar - see
http://vmgump.apache.org/gump/public/doxia/doxia-site-renderer-test/gump_work/build_doxia_doxia-site-renderer-test.html
for a more isolated test.
I don't know how else I could help, in particular since I'm not affected by the
problem myself at all.
> Velocity > 1.5 can't parse default-site.vm
> --
>
> Key: DOXIASITETOOLS-39
> URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-39
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Doc renderer, Site renderer
>Affects Versions: 1.0, 1.1
>Reporter: Stefan Bodewig
>Priority: Minor
>
> This is an issue detected by Gump which runs Maven builds but replaces
> dependencies with the trunk versions of things built by Gump rather than the
> version a project asks for.
> The Cargo build - see
> http://gump.zones.apache.org/gump/test/cargo/cargo/gump_work/build_cargo_cargo.html
> - fails because Velocity doesn't like the line
> #set ( $documentHeader = "" )
> because \" is not an escape sequence for Velocity (anymore?).
> I've taken this to the velocity list -
> http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3c87ocdlps07@v35516.1blu.de%3e
> - and received the feedback that backslash
> escaping was not supported - and likely never has been - and you should
> either use single
> quotes inside the double quotes or use something like
> #set( $Q = '"' )
> #set ( $documentHeader = " I realize that it probably works for you right now using Velocity 1.5, that's
> why I used Improvement rather than bug as category. Still it may be worth to
> find a solution that works for the version of Velocity you want to use as
> well as future versions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIASITETOOLS-39) Velocity > 1.5 can't parse default-site.vm
[ http://jira.codehaus.org/browse/DOXIASITETOOLS-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231518#action_231518 ] Stefan Bodewig commented on DOXIASITETOOLS-39: -- Let me start with a disclaimer: I'm not a velocity developer and not a doxia user, I'm just an observer and maybe a messenger between velocity and doxia. 8-) I see Velocity 1.7-beta1 inside the central repo (groupId is org.apache.velocity now) and don't think there is a final release, yet. The feedback I received from the velocity developers is that while the parser may have accepted your template with older versions, it likely never has done what you intended it to do. If you now tell me that it works for you, I don't know how to respond to that. Quotes cannot be escaped by \ in Velocity templates. > Velocity > 1.5 can't parse default-site.vm > -- > > Key: DOXIASITETOOLS-39 > URL: http://jira.codehaus.org/browse/DOXIASITETOOLS-39 > Project: Maven Doxia Sitetools > Issue Type: Improvement > Components: Doc renderer, Site renderer >Affects Versions: 1.0, 1.1 >Reporter: Stefan Bodewig >Priority: Minor > > This is an issue detected by Gump which runs Maven builds but replaces > dependencies with the trunk versions of things built by Gump rather than the > version a project asks for. > The Cargo build - see > http://gump.zones.apache.org/gump/test/cargo/cargo/gump_work/build_cargo_cargo.html > - fails because Velocity doesn't like the line > #set ( $documentHeader = "" ) > because \" is not an escape sequence for Velocity (anymore?). > I've taken this to the velocity list - > http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3c87ocdlps07@v35516.1blu.de%3e > - and received the feedback that backslash > escaping was not supported - and likely never has been - and you should > either use single > quotes inside the double quotes or use something like > #set( $Q = '"' ) > #set ( $documentHeader = " I realize that it probably works for you right now using Velocity 1.5, that's > why I used Improvement rather than bug as category. Still it may be worth to > find a solution that works for the version of Velocity you want to use as > well as future versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-400) Velocity > 1.5 can't parse default-site.vm
[ http://jira.codehaus.org/browse/DOXIA-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231305#action_231305 ] Stefan Bodewig commented on DOXIA-400: -- Later feedback from the Velocity list suggest that your template probably doesn't work with Velocity 1.5 either, it just doesn't fail as spectacular as it does with Velocity 1.7. The suggestion from the Velocity developers list is to upgrade your dependency to 1.7 and double the quotes. See http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3caanlktikwywkre=wt4um7rwva=ecutap2=js+hetc4...@mail.gmail.com%3e > Velocity > 1.5 can't parse default-site.vm > -- > > Key: DOXIA-400 > URL: http://jira.codehaus.org/browse/DOXIA-400 > Project: Maven Doxia > Issue Type: Improvement > Components: Site Renderer >Affects Versions: 1.0 >Reporter: Stefan Bodewig >Priority: Minor > > This is an issue detected by Gump which runs Maven builds but replaces > dependencies with the trunk versions of things built by Gump rather than the > version a project asks for. > The Cargo build - see > http://gump.zones.apache.org/gump/test/cargo/cargo/gump_work/build_cargo_cargo.html > - fails because Velocity doesn't like the line > #set ( $documentHeader = "" ) > because \" is not an escape sequence for Velocity (anymore?). > I've taken this to the velocity list - > http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3c87ocdlps07@v35516.1blu.de%3e > - and received the feedback that backslash > escaping was not supported - and likely never has been - and you should > either use single > quotes inside the double quotes or use something like > #set( $Q = '"' ) > #set ( $documentHeader = " I realize that it probably works for you right now using Velocity 1.5, that's > why I used Improvement rather than bug as category. Still it may be worth to > find a solution that works for the version of Velocity you want to use as > well as future versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-400) Velocity > 1.5 can't parse default-site.vm
Velocity > 1.5 can't parse default-site.vm -- Key: DOXIA-400 URL: http://jira.codehaus.org/browse/DOXIA-400 Project: Maven Doxia Issue Type: Improvement Components: Site Renderer Affects Versions: 1.0 Reporter: Stefan Bodewig Priority: Minor This is an issue detected by Gump which runs Maven builds but replaces dependencies with the trunk versions of things built by Gump rather than the version a project asks for. The Cargo build - see http://gump.zones.apache.org/gump/test/cargo/cargo/gump_work/build_cargo_cargo.html - fails because Velocity doesn't like the line #set ( $documentHeader = "" ) because \" is not an escape sequence for Velocity (anymore?). I've taken this to the velocity list - http://mail-archives.apache.org/mod_mbox/velocity-dev/201008.mbox/%3c87ocdlps07@v35516.1blu.de%3e - and received the feedback that backslash escaping was not supported - and likely never has been - and you should either use single quotes inside the double quotes or use something like #set( $Q = '"' ) #set ( $documentHeader = "http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2098) Please sync XMLUnit's repository into central
Please sync XMLUnit's repository into central - Key: MAVENUPLOAD-2098 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2098 Project: Maven Upload Requests Issue Type: Wish Reporter: Stefan Bodewig The sync line would be "xmlunit","[EMAIL PROTECTED]:/home/groups/x/xm/xmlunit/htdocs/repo","rsync_ssh","Stefan Bodewig","[EMAIL PROTECTED]",, The rsync URL corresponds to http://xmlunit.sourceforge.net/repo/ I'm one of the project admins, see http://sourceforge.net/projects/xmlunit I've tried to subscribe to [EMAIL PROTECTED] (using [EMAIL PROTECTED]) but my request seems to be stuck in the moderation queue. The central repo already contains older releases of XMLUnit. Would it be a good idea to add those to XMLUnit's repo or should we only add our newer releases? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MAVENUPLOAD-1619) Please upload XMLUnit for Java 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig reopened MAVENUPLOAD-1619: - Sorry for the delay, I've been on vacation. As requested I've added an optional dependency on JUnit, so please upload the artifact. The XMLUnit developers (me ;-) do not intend to build XMLUnit using Maven, but we do want to provide it via the repository because our users asked for it. The dependency on JUnit is non-optional at compile time, but as I said, we don't build with Maven, so marking it as optional (as it is at runtime) will be fine for us. > Please upload XMLUnit for Java 1.1 > -- > > Key: MAVENUPLOAD-1619 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1619 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Stefan Bodewig >Assignee: Carlos Sanchez > > XMLUnit for Java 1.1 has been released today. > http://xmlunit.sf.net/ > I am listed as a project admin at http://sourceforge.net/projects/xmlunit/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1619) Please upload XMLUnit for Java 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101327 ] Stefan Bodewig commented on MAVENUPLOAD-1619: - As both of you are certainly aware, I'm not a Maven person at all. If I mark the dependency as optional, what will be Maven's default behavior for our TestNG users who happen to use Maven for their builds? Will Maven download JUnit as well unless they explicitly override it? I really want the default to be that the transitive dependency is ignored and user's need to ask for JUnit explicitly. If this can be done with an optional dependency I'll be happy to add it. Oh, and if you could tell me how to mark a dependency as optional, I'd really appreciate it. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html doesn't contain the word "optional". > Please upload XMLUnit for Java 1.1 > -- > > Key: MAVENUPLOAD-1619 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1619 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Stefan Bodewig > > XMLUnit for Java 1.1 has been released today. > http://xmlunit.sf.net/ > I am listed as a project admin at http://sourceforge.net/projects/xmlunit/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-1619) Please upload XMLUnit for Java 1.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101296 ] Stefan Bodewig commented on MAVENUPLOAD-1619: - Hi Henri, I've updated the POM to include name and scm information and should now have all elements required by http://maven.apache.org/guides/mini/guide-central-repository-upload.html. The jar has been updated. Yes, we do have two classes that depend on JUnit (three if you want to be strict), but we don't list JUnit as a dependency for good reasons (or so we think). There are two kinds of users of XMLUnit: * people who write JUnit tests and use the two classes of XMLUnit that depend on JUnit. These people already know they need JUnit (because the already use it themselves) and don't need us to provide a transitive dependency. * people who use the rest of XMLUnit via its API and don't use JUnit at all. They may use XMLUnit together with TestNG or outside of any tests at all. We really wouldn't want to force those people to manually exclude the transitive dependency on JUnit introduced by XMLUnit. We feel it is to our user's benefit to not list a dependency on JUnit. I hope you understand our indent. Thanks Stefan > Please upload XMLUnit for Java 1.1 > -- > > Key: MAVENUPLOAD-1619 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1619 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Stefan Bodewig > > XMLUnit for Java 1.1 has been released today. > http://xmlunit.sf.net/ > I am listed as a project admin at http://sourceforge.net/projects/xmlunit/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1619) Please upload XMLUnit for Java 1.1
Please upload XMLUnit for Java 1.1 -- Key: MAVENUPLOAD-1619 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1619 Project: maven-upload-requests Issue Type: Wish Reporter: Stefan Bodewig XMLUnit for Java 1.1 has been released today. http://xmlunit.sf.net/ I am listed as a project admin at http://sourceforge.net/projects/xmlunit/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
