ls appearing.
I think we replaced the StringBuffer with some unsynchronized chunked
implementation to avoid allocation of very large strings and unnecessary
synchronzation.
Alex
On Sun, Dec 11, 2016 at 7:18 AM, Claude Brisson wrote:
FYI, we got rid of the Executor pattern in the events API, and we
ON and XML, as long as they
perform safe operations on local data, and use modern libraries for the
generated data structures (org.json:json and the org.w3c.dom package,
although it's not very user friendly).
On 12/04/2016 07:57 AM, Michael Osipov wrote:
Am 2016-12-02 um 10:01 schrieb Claud
FYI, we got rid of the Executor pattern in the events API, and we now
always provide the current Context when calling handlers.
On 29/11/2016 23:25, Alex Fedotov wrote:
[...]
We have run into some other inefficient places. For example
ASTStringLiteral is buffering the entire content in the Str
On 09/12/2016 16:39, Michael Osipov wrote:
[...]
* All templates (!) (anything else?) from ImputStream are read with
that new input encoding, unless other stated
That's all, except a resource can also be a static text file, as in
#include('file').
Ah, and I expect input.encoding to be respec
I agree, we don't need to expose ExtProperties.
On 09/12/2016 17:07, Michael Osipov wrote:
Am 2016-12-09 um 13:05 schrieb Claude Brisson:
This issue has revealed another problem: we still have deprecated
initialization methods taking an ExtendedProperties object. But I had
totally overl
Hi.
On 09/12/2016 15:34, Michael Osipov wrote:
Hi folks,
the default encoding has been changed recently to UTF-8 [1], though I
still think that it requires some more description from a user's point
of view and more code cleanup
Feel free to help!
* All templates (!) (anything else?) from
[
https://issues.apache.org/jira/browse/VELOCITY-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735420#comment-15735420
]
Claude Brisson commented on VELOCITY-878:
-
Don't apologize! Your ticke
Plus, getting rid of ExtendedProperties can allow us to upgrade our
dependency to commons-collections v4.1.
hum.. to totally get rid of this dependency, in fact.
Claude
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.
It also means we have to get rid of the ResourceLoader base class, by
the way. I indented to only deprecate it in favor of ResourceLoader2,
but there is no way to keep it around.
Claude
On 09/12/2016 13:51, Claude Brisson wrote:
On 09/12/2016 13:09, Michael Osipov wrote:
Hi folks,
based
On 09/12/2016 13:09, Michael Osipov wrote:
Hi folks,
based on VELOCITY-878 I am confused why this shading approach has been
taken?
1. Commons Lang 3: I see no benefit in shading it at all, if you check
the shaded JAR, a huge amount of classes are shaded. Moreover, Commons
Lang is so popular
cy to commons-collections v4.1.
Claude
On 08/12/2016 19:10, Claude Brisson wrote:
Our first 2.0 JIRA entry! Champagne!
On 08/12/2016 17:38, Mary Helm (JIRA) wrote:
Mary Helm created VELOCITY-878:
--
Summary: commons collections is required at run
[
https://issues.apache.org/jira/browse/VELOCITY-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-878.
-
Resolution: Invalid
Assignee: Claude Brisson
The doc should be updated, because
Our first 2.0 JIRA entry! Champagne!
On 08/12/2016 17:38, Mary Helm (JIRA) wrote:
Mary Helm created VELOCITY-878:
--
Summary: commons collections is required at run time
Key: VELOCITY-878
URL: https://issues.apac
On 05/12/2016 13:11, Sergiu Dumitriu wrote:
[...]
==
---
velocity/engine/trunk/velocity-engine-core/src/main/java/org/apache/velocity/runtime/RuntimeInstance.java
(original)
+++
velocity/engine/trunk/velocity-engine-co
Hi.
On 01/12/2016 21:21, Michael Osipov wrote:
While I understand you idea, I do think that introducing stuff like
this a bad idea for several reasons:
1. Processing of structured, low-level data like XML, JSON, form data
always belongs to a controller and not to the view layer. The view
lay
This time, it's about tools reading external resources. I'd like to:
1) have ImportSupport and ImportTool also be available in generic tools
for absolute URLs, only the view versions being able to import a
relative URL
2) have XmlTool inherit from ImportSupport, to homogenize its behavior
wi
on to avoid unecessary string
buffering
So, still
[x] Leave at test build
Claude
On 18/11/2016 18:33, Nathan Bubna wrote:
+1 GA
On Wed, Nov 16, 2016 at 7:24 AM, Greg Huber wrote:
Thanks, works great for me.
[x] General Availability (GA)
+1 non binding.
On 16 November 2016 at 11:51, C
Thanks for the details.
I agree that the Context could be passed along with other standard
arguments. It has been done this way for backward compatibility, but
since we go 2.0, we can improve it. And even keep B.C. by introducing
new interfaces while deprecating the old ones.
It's about the
Am 2016-11-25 um 01:08 schrieb Claude Brisson:
By Olson TZ ID, I guess you refer to "zzz" (aka CET), and not ""
(aka Central European Time), don't you?
No, never ever use this braindead RFC three-letter timezones. They are
not standardized, not unambigious. Inv
Hi Alex.
Thanks for your feedback.
On 28/11/2016 20:52, Alex Fedotov wrote:
Hello All,
ContextAware interface in Velocity is not really workable in a
multi-threaded environment.
The handler is a singleton and setting the Context on the singleton from
multiple threads is not going to work well
6. I consider 435 to 441 being inconsisting to their counterpart 420
to 423.
Oh, you're speaking about line numbers in ConversionUtils.java... why is
it inconsistent? When we're speaking about date only, there is no
timezone or separator involved, so it's the same format.
Yes, but it seems
On 24/11/2016 20:41, Michael Osipov wrote:
Am 2016-11-24 um 17:40 schrieb Sergiu Dumitriu:
On 11/24/2016 02:29 AM, Claude Brisson wrote:
6. I consider 435 to 441 being inconsisting to their counterpart 420
to 423.
Oh, you're speaking about line numbers in ConversionUtils.java...
w
Glad to receive an enlightened opinion on the subject.
On 23/11/2016 20:59, Michael Osipov wrote:
Hi Claude,
not being subscribed to the Velocity dev list, though being a happy
Velocity user and Maven Doxia developer relying on Velocity, here are
my thoughts on this:
Having access to ISO 8
FYI
Forwarded Message
Subject: Re: svn commit: r1770547 - in
/velocity/tools/trunk/velocity-tools-generic/src/main/java/org/apache/velocity/tools:
ConversionUtils.java generic/DateTool.java
Date: Wed, 23 Nov 2016 20:59:43 +0100
From: Michael Osipov
To: cla...@reneg
3) use explicit format names: numberFormat, timeFormat, dateFormat and
timestampFormat, instead of a generic 'format' parameter defaulting to
an ubiquitous 'default' value. I'd also like to have the default formats
be the international formats used by HTML5 (RFC 3339).
+1000
:-)
The new form
Thanks again for your review.
On 21/11/2016 07:22, Sergiu Dumitriu wrote:
Although RFC 3339 says that "Applications [...] may choose, for the sake
of readability, to specify a full-date and full-time separated by (say)
a space character", the standard is to use T as a separator.
And if I'm alre
On 17/11/2016 19:10, Mike Kienenberger wrote:
On Thu, Nov 17, 2016 at 12:58 PM, Claude Brisson wrote:
There are several things I'd like to do for the tools before releasing them:
1) deprecate the ConversionTool:
- the only remaining feature is a toStrings() method (which does
spli
There are several things I'd like to do for the tools before releasing them:
1) deprecate the ConversionTool:
- date formatting and parsing methods are redundant with (and less
complete than) DateTool ones.
- number formatting and parsing methods are redundant with the
NumberTool and Ma
The Velocity Engine 2.0 RC3 test build has been available since the
12th, and the RC4 (which only contains trivial fixes) has just been
published.
Release notes:
*
https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.0/release-notes.html
Distribution:
* https://dist.apache.or
n Bubna wrote:
+1 for logical names and a configurable base.
On Fri, Nov 11, 2016 at 6:24 AM, Claude Brisson wrote:
In fact, the logger name (well, *base* logger name) is configurable. So we
can both be happy: we can have the default base logger name be
"org.apache.velocity", as lik
lds may be using it. I have looked at other maven plugins but nothing
would work for me, so I will need to create my own version going forward by
including the source locally.
Cheers
On 12 November 2016 at 20:49, Claude Brisson wrote:
Texen is unmaintained. But it is still available from Velocit
ent/repositories/orgapachevelocity-1012/>
?
orgapachevelocity-1011 gives a 404
On 12 November 2016 at 21:15, Claude Brisson wrote:
A new test build of Velocity Engine 2.0 is available (RC3).
No determination as to the quality ('alpha,' 'beta,' or 'GA') of Veloc
A new test build of Velocity Engine 2.0 is available (RC3).
No determination as to the quality ('alpha,' 'beta,' or 'GA') of
Velocity Engine 2.0 has been made, and at this time it is simply a "test
build". We welcome any comments you may have, and will take all feedback
into account if a quali
Texen is unmaintained. But it is still available from Velocity download
page http://velocity.apache.org/download.cgi
You may need to recompile it, but there are good chances that it sill
works with Velocity 2.0.
Claude
On 12/11/2016 12:38, Greg Huber wrote:
In my build I use velocity (a
its intuitive to set the debugging
name="foobar" name without having to dip into the code sounds great. The
package name is however the easiest to remember as its from the class you
are trying to debug (using attached source jar).
Thanks
On 11 November 2016 at 11:07, Claude Brisson w
11:14, Claude Brisson wrote:
Why not, but it should be done right now to take advantage of the
major version change.
I checked quickly, and it seems like all logging backends build the
loggers hierarchy using namespaces separated with dots, which can be
class names by convention but it is not a
ur hierarchy).
Thoughts?
Claude
On 10/11/2016 17:18, Mike Kienenberger wrote:
+1 to using several appropriate functional names if we are picking
loggers by String rather than by Class.
On Thu, Nov 10, 2016 at 11:11 AM, Claude Brisson wrote:
On 10/11/2016 15:56, Greg Huber wrote:
Yes it does
On 10/11/2016 15:56, Greg Huber wrote:
Yes it does when I use name="Velocity"
But as you are using the runtime instance logger its either on or off for
the whole package. Using a per class I think enables more filtering as you
can name="org.apache.velocity.app" level="DEBUG" purely for this pa
Any module anywhere can get a logger using one of the two static methods:
Logger org.slf4j.LoggerFactory.getLogger(String loggerName)
Logger org.slf4j.LoggerFactory.getLogger(Class targetClass)
Calling one or the other is a matter of taste. It does not *have* to be
the same logger anywhere in
When you restart a J2EE container, it will try to serialize the sessions
on disk to restore them when reloading. This can only works if
everything in the session is serializable, including the session toolbox
itself.
Since the RenderTool keeps references on a VelocityEngine, it cannot be
seri
!
On Wed, Nov 9, 2016 at 9:06 AM, Claude Brisson wrote:
Ok, I reproduced it. It happens when the method is overloaded with a
variant that takes no argument.
Guess there will be a third release candidate...
On 09/11/2016 17:44, Greg Huber wrote:
It seems to be returning the wrong class na
java.lang.IllegalArgumentException exception.
On 9 November 2016 at 16:09, Claude Brisson wrote:
I cannot reproduce it.
Is the thumbResource() method overloaded?
Do you have the full stacktrace?
On 09/11/2016 16:50, Greg Huber wrote:
Hello,
I am getting an error when a parameter on a method name is null, it says
change the variable to be blanks it works ok.
On 9 November 2016 at 14:50, Claude Brisson wrote:
A new test build of Velocity Engine 2.0 is available.
No determination as to the quality ('alpha,' 'beta,' or 'GA') of Velocity
Engine 2.0 has been made, and
*
https://repository.apache.org/content/repositories/orgapachevelocity-1011/
A vote regarding the quality of this test build will be initiated within
the next couple of days.
Regards,
Claude
On 07/11/2016 11:06, Claude Brisson wrote:
The test build of Velocity Engine 2.0 is available.
No
The standard way of using loggers is to have each class instantiate its
own Logger object, so that the logs correctly indicate the class where
the message was generated:
private static final Logger LOG =
LoggerFactory.getLogger(SomeTool.class);
Other ways of setting an explicit logger shou
On 08/11/2016 15:33, Sergiu Dumitriu wrote:
I don't see how this works. Who calls setLog?
The ToolContext.putVelocityEngine(engine) does:
putToolProperty(LOG_KEY, engine.getLog());
so "log" becomes a standard property which calls setLog() by
introspection on tools when present.
Basicall
+/* exact towards Float */
Nitpicking: this isn't exact, Long and Integer require more bits than
Float has to offer.
Absolutely true, that's why I don't call it a widening conversion as in
other comments. The 'exact' in the comment refers to the fact that we're
converting from an *e
s it is, with a warning in the docs,
after all tests do pass.
Claude
On 07/11/2016 17:22, Sergiu Dumitriu wrote:
On 11/07/2016 05:49 AM, Claude Brisson wrote:
Shall we keep this module active or archive it with Tools 3.0?
I can ask the question on the Struts dev list, if appropriate.
C
Shall we keep this module active or archive it with Tools 3.0?
I can ask the question on the Struts dev list, if appropriate.
Claude
-
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-m
The test build of Velocity Engine 2.0 is available.
No determination as to the quality ('alpha,' 'beta,' or 'GA') of
Velocity Engine 2.0 has been made, and at this time it is simply a "test
build". We welcome any comments you may have, and will take all feedback
into account if a quality vote
ty... Ah, I just got it: 2.x
and 2.0 should be *merged*.
Release notes in Jira are just a list of issues tied to a fix for
version.
There should be a link to navigate to see this in HTML form. Is that
what
you are looking for?
On Sunday, November 6, 2016, Claude Brisson wrote:
Nevermind.
to see this in HTML form. Is that what
you are looking for?
On Sunday, November 6, 2016, Claude Brisson wrote:
Nevermind. I'll put the release notes in the distribution folder.
On 06/11/2016 21:52, Nathan Bubna wrote:
I don't see a "Releases" either. Under the "Vers
[
https://issues.apache.org/jira/browse/VELOCITY-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson updated VELOCITY-866:
Fix Version/s: (was: 2.0)
2.x
think.
On Sun, Nov 6, 2016 at 12:20 PM, Claude Brisson wrote:
Hi all.
In the process of releasing engine v2.0, I'm supposed to create a release
note on JIRA, but although I can browse, create and release versions, I
don't see any 'Releases' menu entry nor any way to create th
Hi all.
In the process of releasing engine v2.0, I'm supposed to create a
release note on JIRA, but although I can browse, create and release
versions, I don't see any 'Releases' menu entry nor any way to create
this release note here:
https://issues.apache.org/jira/browse/VELOCITY/?selected
[
https://issues.apache.org/jira/browse/VELOCITY-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632130#comment-15632130
]
Claude Brisson commented on VELOCITY-869:
-
There probably won't be any
[
https://issues.apache.org/jira/browse/VELOCITY-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-836.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 1.7
infra did
affect the votes. I publish the artifact.
Claude
On 14/10/2016 16:16, Claude Brisson wrote:
Remove Antonio from the PMC, as he asked to go emeritus.
I just checked if I had enough karma to do it myself (editing of
private/committers/board/committee-info.txt), and it worked.
So no wor
blish the staging URL? I don't remember seeing it.
On Fri, Oct 14, 2016 at 8:56 AM, Claude Brisson wrote:
I change my vote to -1: I forgot Mike as new commiter... (sorry about that,
Mike!). Also, Dishara (who worked on the JSR 223 scripting) is not listed.
Ah, and Antonio asked to become e
. What do i need to do here? Sorry guys, not meaning to be slacking.
On Fri, Oct 14, 2016 at 6:14 AM, Antonio Petrelli <
antonio.petre...@gmail.com> wrote:
2016-10-14 14:56 GMT+02:00 Claude Brisson :
Ah, and Antonio asked to become emeritus (but the change hasn't been
pushed upwards, I
mind, I'll revert and redo the release procedure, keeping
your votes (3 binding votes from Sergiu, Nathan and myself), and
publishing the master pom artifact directly with those little changes.
If this democratic rules breaching does disturb anyone, please chime in.
Claude
On 11/10/201
On 11/10/2016 16:02, Mike Kienenberger wrote:
I took a look at the MyFaces release page, which in turn points to the
following url. Starting at this section, it does look like you now
have all of the pieces you need in place: prepare the release,
perform the release, close the respository, tak
ty-master ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-gpg-plugin:1.6:sign (sign-release-artifacts) @
velocity-master ---
You need a passphrase to unlock the secret key for
user: "Claude Brisson "
20
On 11/10/2016 14:43, Mike Kienenberger wrote:
On Tue, Oct 11, 2016 at 8:11 AM, Claude Brisson wrote:
(I don't know where snapshots and prepared releases do land on
https://repository.apache.org , I was unable to find them on
https://repository.apache.org after the release:prepare call,
Hi.
Before staging the release candidate for velocity-engine, I must first
release the version 2 of velocity-master.
It only contains a pom.xml with the list of PMCs and devs, and enumerate
the mailing lists, and can be seen here:
http://svn.apache.org/viewvc/velocity/maven/tags/velocity-ma
[
https://issues.apache.org/jira/browse/VELOCITY-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-752.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
Fixed by
[
https://issues.apache.org/jira/browse/VELOCITY-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-684.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
Fixed by
[
https://issues.apache.org/jira/browse/VELOCITY-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-683.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
Fixed by
e. I was
never quite certain about that default when i implemented it.
And Claude, thanks again for all the work on this. Velocity may not be
critical to my work these days, but it is still good to see it being
updated.
On Tue, Sep 13, 2016 at 11:23 AM, Claude Brisson wrote:
It may be the last big s
It may be the last big subject to address before releasing 2.0: how to
handle macro arguments?
Those three issues exhibit nasty side effects of the current behavior:
https://issues.apache.org/jira/browse/VELOCITY-683
https://issues.apache.org/jira/browse/VELOCITY-684
https://issues.apache.org
[
https://issues.apache.org/jira/browse/VELOCITY-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-867.
-
Resolution: Fixed
Fix Version/s: (was: 1.7.x)
That seems the way to go
[
https://issues.apache.org/jira/browse/VELOCITY-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484877#comment-15484877
]
Claude Brisson commented on VELOCITY-867:
-
Each subproject has its own is
You're right, that's better.
On 12/09/2016 17:56, Sergiu Dumitriu wrote:
Why not put this in the parent pom, so it also affects, the other modules?
On Sep 12, 2016 7:50 AM, wrote:
Author: cbrisson
Date: Mon Sep 12 11:49:56 2016
New Revision: 1760339
URL: http://svn.apache.org/viewvc?rev=176
[
https://issues.apache.org/jira/browse/VELOCITY-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-834.
-
In 2.x, thanks to applied patches from VELOCITY-801, VELOCITY-833 and
VELOCITY-841, the
[
https://issues.apache.org/jira/browse/VELOCITY-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-866.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.0
Seems
[
https://issues.apache.org/jira/browse/VELOCITY-875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-875.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
The
[
https://issues.apache.org/jira/browse/VELOCITY-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-868.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
All these
[
https://issues.apache.org/jira/browse/VELOCITY-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-867.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-857.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-856.
---
Resolution: Cannot Reproduce
Assignee: Claude Brisson
Fix Version/s: 2.x
I
[
https://issues.apache.org/jira/browse/VELOCITY-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-812.
---
Resolution: Invalid
Assignee: Claude Brisson
Fix Version/s: 2.x
Since it
[
https://issues.apache.org/jira/browse/VELOCITY-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-802.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
There is
[
https://issues.apache.org/jira/browse/VELOCITY-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-792.
-
Resolution: Fixed
Assignee: Claude Brisson
Resolved by the `lines` or 'struc
[
https://issues.apache.org/jira/browse/VELOCITY-783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-783.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
Fixed by
[
https://issues.apache.org/jira/browse/VELOCITY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-780.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-743.
---
Resolution: Won't Fix
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-736.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
We now
[
https://issues.apache.org/jira/browse/VELOCITY-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-719.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
Since
[
https://issues.apache.org/jira/browse/VELOCITY-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-713.
---
Resolution: Cannot Reproduce
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-652.
-
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.x
User
[
https://issues.apache.org/jira/browse/VELOCITY-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-678.
-
Resolution: Fixed
Assignee: Claude Brisson
Fixed by commit 1759426.
>
[
https://issues.apache.org/jira/browse/VELOCITY-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-677.
---
Resolution: Won't Fix
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-253.
-
Resolution: Implemented
Assignee: Claude Brisson
Implemented, with a switch, and
Thanks!
I'm sure it will happen one day, Nathan.
Yes, we ought to find some new philosophical debate...
Claude
On 30/08/2016 18:48, Nathan Bubna wrote:
Seriously unbelievable. Did i say i'd buy you a drink should you ever come
to town? Well, also, https://cdn.meme.am/instances/500x/53443254
[
https://issues.apache.org/jira/browse/VELOCITY-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451885#comment-15451885
]
Claude Brisson commented on VELOCITY-679:
-
Oh, I see : Jira eats do
[
https://issues.apache.org/jira/browse/VELOCITY-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-679.
---
Resolution: Not A Bug
Assignee: Claude Brisson
Issue title and comment aren&#
[
https://issues.apache.org/jira/browse/VELOCITY-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-849.
---
Resolution: Not A Bug
Assignee: Claude Brisson
Fix Version/s: 2.x
This kind
[
https://issues.apache.org/jira/browse/VELOCITY-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-845.
---
Resolution: Won't Fix
Assignee: Claude Brisson
Fix Version/s: 2.x
I
[
https://issues.apache.org/jira/browse/VELOCITY-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson closed VELOCITY-844.
---
Resolution: Cannot Reproduce
Assignee: Claude Brisson
Fix Version/s: 2.x
[
https://issues.apache.org/jira/browse/VELOCITY-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-798.
-
Resolution: Fixed
Fix Version/s: 2.x
Fixed by commit 1758467.
> Velocity wr
601 - 700 of 1132 matches
Mail list logo
