A ValueEncoder that supports any mapper might be quite hard to accomplish. It's
not like there's some standard API on top of the driver, like JPA that we could
rely on.
Although the integration of morphia and mongo-jackson-mapper is very similar I
could bet that other mappers might take a comple
The CMS can be extended with either custom pre-processors that kick in
before the markdown compilation or we can write a new markdown element
that mimicks the scrollbar macro's behaviour.
Uli
Am Mo, 2.01.2012, 21:38 schrieb Bob Harner:
> We already have a separate documentation "component" within
Thanks! Now, finally, the documentation is formatting correctly for
those few Tapestry users who are forced to use IE. (The main problems
were the banner layout and the Related Articles.)
On Mon, Jan 2, 2012 at 8:03 AM, Ulrich Stärk wrote:
> done
>
> On 02.01.2012 13:46, Bob Harner wrote:
>> Mea
We already have a separate documentation "component" within the TAP5
"project" in JIRA. I like it that way and wouldn't want to have the
documentation in a separate Tapestry documentation "project", if
that's what you have in mind. We already have "Tapestry" and "Tapestry
5" projects, and that's al
On my endless TODO is to learn JIRA enough to customize it to our
needs ... for instance, to only allow a fix release when closing an
issue, etc.
On Mon, Jan 2, 2012 at 11:42 AM, "Ulrich Stärk" wrote:
> I'd rather solve this with a custom field config if possible. I don't like
> fragmenting the i
I'd rather solve this with a custom field config if possible. I don't like
fragmenting the issues over multiple Jira projects...
Uli
Am Mo, 2.01.2012, 16:55 schrieb Howard Lewis Ship:
> Wow .. the component templates page has gotten pretty huge. I think
> it should be broken up into multiple pa
Wow .. the component templates page has gotten pretty huge. I think
it should be broken up into multiple pages, using the {scrollbar}
macro.
On a related note; I've thought about creating a separate JIRA just
for documentation bugs. Why seperate? To reflect the fact that
documentation bugs are
done
On 02.01.2012 13:46, Bob Harner wrote:
> Meanwhile, can somebody go ahead and paste the current template from svn
> into the admin console? Thx
>
> Bob Harner
> On Jan 2, 2012 3:36 AM, "Ulrich Stärk" wrote:
>
>> Apache CMS does exactly that. You keep markdown (default, other document
>> pro
Meanwhile, can somebody go ahead and paste the current template from svn
into the admin console? Thx
Bob Harner
On Jan 2, 2012 3:36 AM, "Ulrich Stärk" wrote:
> Apache CMS does exactly that. You keep markdown (default, other document
> processors like jekyll
> possible) sources in version contro
Apache CMS does exactly that. You keep markdown (default, other document
processors like jekyll
possible) sources in version control and it generates the website for you
automatically and almost
instantly upon checkin. The downside is that only people with Apache accounts
can contribute. But
sen
10 matches
Mail list logo
