692adc47f4
Move our GWT stuff around.
...
This avoids having it look like normal Java source and then confusing tools
because there are two copies of DefaultCollector.
2014-12-01 16:46:51 -08:00
aafa5c0a73
Update to more recent compiler plugin.
...
Also bumped source/target to 1.6. Hopefully this won't result in backlash from
cavemen still using JMustache on JDK 1.5.
2014-02-17 12:06:42 -08:00
93b66b757e
More test coverage plus Coveralls wiring.
2014-02-17 12:02:41 -08:00
6b866d3263
Try wiring up Coveralls Maven plugin.
2014-02-17 11:54:17 -08:00
b618e6dbd4
[maven-release-plugin] prepare for next development iteration
2014-02-13 10:16:36 -08:00
834759d04c
[maven-release-plugin] prepare release jmustache-1.9
2014-02-13 10:16:32 -08:00
9910bb691a
SBT updates, fixed GWT test depends.
2013-10-08 12:18:48 -07:00
3af55c2660
Some javadoc improvements.
2013-08-01 16:04:46 -07:00
3baec8221d
[maven-release-plugin] prepare for next development iteration
2013-04-05 11:03:35 -07:00
23c9ed91c8
[maven-release-plugin] prepare release jmustache-1.8
2013-04-05 11:03:26 -07:00
7e414b6c95
Use latest JUnit.
2013-04-02 12:54:20 -07:00
2889ee8692
Added standard Mustache specs tests suite.
...
The groups with failing tests are currently commented out (everything except
interpolation). The main reason for failures are due to the requirement that
standalone lines that contain nothing but whitespace be stripped from the
output.
2013-04-02 12:54:20 -07:00
f3afcda74f
[maven-release-plugin] prepare for next development iteration
2013-02-27 10:24:27 -08:00
96020e46de
[maven-release-plugin] prepare release jmustache-1.7
2013-02-27 10:24:18 -08:00
41eec508cb
[maven-release-plugin] prepare for next development iteration
2012-08-16 17:53:52 -07:00
21f2145222
[maven-release-plugin] prepare release jmustache-1.6
2012-08-16 17:53:45 -07:00
a899c466ca
Use latest test plugin.
2012-08-13 14:31:23 -07:00
049359cde3
Add Bundle-ActivationPolicy to OSGi manifest.
...
Set the Bundle-ActivationPolicy to 'lazy'. According to the OSGi wiki:
"This can improve performance in a system with many bundles, where
instead of starting them they may be placed into a lazy state, and
only activated when they are actually used."
-- http://wiki.osgi.org/wiki/Bundle-ActivationPolicy
'Lazy' is fine for jmustache, because it has no bundle activator,
and does not provide any OSGi services that need to be registered.
2012-08-13 14:42:47 +01:00
a1808fb3ef
POM tidying.
2012-06-08 08:34:48 -07:00
77991e52bb
Add OSGi headers in manifest file using maven-bundle-plugin.
...
Some of the automatically generated headers are suppressed because
they are for information only, and not very useful. These include
Bnd-LastModified, Include-Resource, Private-Package and Tool.
2012-05-25 15:54:39 +01:00
751123c067
[maven-release-plugin] prepare for next development iteration
2011-11-13 08:53:24 -08:00
ab3d6206e0
[maven-release-plugin] prepare release jmustache-1.5
2011-11-13 08:53:17 -08:00
407d999836
Further work on making JMustache work in GWT.
...
I've ironed out most of the kinks, but the GWT unit test still fails because
we're forced to do some sneaky things with java.io.Reader/Writer. I think it
will all work when compiled to JavaScript, so I need to check it in a real
project.
2011-10-29 15:31:27 -07:00
627da759c7
Include sources in jar for (eventual) GWT usage.
2011-10-13 20:49:33 -07:00
76e9d54683
Extracted the iteration over collections and creation of variable fetchers into
...
a pluggable component.
This allows scaling down to the GWT environment by hiding the reflection code
via GWT's super source mechanism.
And it allows scaling up to non-Java languages (like Scala) by allowing the
library client to extend the DefaultCollector and teach it about Scala
Iterators, Iterables and Maps.
I also just realized that GWT has no facilities for Reader and Writer, which is
going to complicate making things work in GWT even further. But for now, I'll
just leave things as is.
2011-10-13 20:35:46 -07:00
2b6066adce
[maven-release-plugin] prepare for next development iteration
2011-08-29 14:50:49 -07:00
447b109512
[maven-release-plugin] prepare release jmustache-1.4
2011-08-29 14:50:40 -07:00
71fdc8aa33
Specify correct license in POM.
2011-08-26 11:26:41 -07:00
553ab51357
[maven-release-plugin] prepare for next development iteration
2011-06-03 11:08:50 -07:00
ca50fe0b15
[maven-release-plugin] prepare release jmustache-1.3
2011-06-03 11:08:45 -07:00
6acca915b1
[maven-release-plugin] prepare for next development iteration
2011-04-13 16:18:42 -07:00
b38f17ea0f
[maven-release-plugin] prepare release jmustache-1.2
2011-04-13 16:18:35 -07:00
76f86ea665
[maven-release-plugin] prepare for next development iteration
2011-03-01 11:35:16 -08:00
13ac4f9b87
[maven-release-plugin] prepare release jmustache-1.1
2011-03-01 11:35:09 -08:00
4a1a125f87
Maybe these URLs will appease my fickle Maven mistress.
2011-03-01 11:34:20 -08:00
c94782fd9b
My release was borked, need to start over. Yay!
2011-03-01 11:31:55 -08:00
1d0f1b7a65
Prepare for 1.2-SNAPSHOT development. Go back to old GIT URL. I was apparently
...
using an ancient version of Maven that was not very GIT friendly.
2011-03-01 11:30:22 -08:00
74c19b2e5f
[maven-release-plugin] prepare release jmustache-1.1
2011-03-01 11:28:44 -08:00
d1d096ad84
Now I want some line wrapping.
2011-03-01 11:17:01 -08:00
6ca5e463da
We'll need a git: in there to let Maven know what's going on.
2011-03-01 11:16:34 -08:00
7ed35d55b5
Maybe Maven will like the https GIT URL better?
2011-03-01 11:15:55 -08:00
97c106defd
Update POM with Github URLs.
2010-10-24 09:47:49 -07:00
4f5b3d772d
[maven-release-plugin] prepare for next development iteration
2010-10-22 06:07:52 +00:00
e3dcf153b6
[maven-release-plugin] prepare release jmustache-1.0
2010-10-22 06:07:19 +00:00
3f42f0bb49
We're not yet version 1.0.
2010-10-21 19:31:55 +00:00
5640791b4b
Earnest beginnings.
2010-10-21 06:32:37 +00:00
Michael Bayne