[
http://issues.apache.org/jira/browse/FOR-578?page=comments#action_12318789 ]
Sjur N. Moshagen commented on FOR-578:
--
Sorry for my stupid mistake - I really believed I had the filenames right:-/ -
it is working as it should when the filenames were cor
[ http://issues.apache.org/jira/browse/FOR-617?page=all ]
Diwaker Gupta resolved FOR-617:
---
Fix Version: 0.8-dev
Resolution: Fixed
The DOAP file is available at http://forrest.apache.org/doap.xml
I've heard from Mark Hedlund at O'Reilly:
"Thanks
Tim Williams wrote:
> Ross Gardler wrote:
> > Tim Williams wrote:
> > >
> > > I guess, I just think JIRA is not well suited for allowing people to
> > > get their mind around the big picture of where we might be heading.
> >
> > I would think it is the way we are using Jira that is the problem, no
Gav wrote:
> From: "Ross Gardler" <[EMAIL PROTECTED]>
>
> |
> | Jira has powerful filtering facilities, email notification (although it
> | seems to be broken right now), XML feeds and the like. We should utilise
> | it to keep track of what we *should* be doing. For example, would it be
> | u
Ross Gardler wrote:
> Tim Williams wrote:
>
> >4) It would answer a question I've been having lately -- how do we
> >know when 0.8, 0.9, etc. is "done" and ready for release? Having a
> >feature list would allow us to check off sets of features, thus
> >knowing that we're ready for release when a
Ross Gardler wrote:
>
> Jira has powerful filtering facilities, email notification (although it
> seems to be broken right now), ...
I have it working with an experimental filter to
notify me about any open issues with attachments.
Are you not able to do personal notifications,
or are you havin
Ross Gardler wrote:
> Ferdinand Soethe wrote:
> >
> >However I can already state that this is not going to reduce our build
> >time because of the way checksums works:
> >
> >- Create or update a checksum for each document each time it is build
> >- Next time compare that checksum to the checksum f
[ http://issues.apache.org/jira/browse/FOR-583?page=all ]
Thorsten Scherler resolved FOR-583:
---
Resolution: Fixed
I applied more or less all patches. I had some problems because some patches
where not made from the whiteboard.
Besides I did not c
[ http://issues.apache.org/jira/browse/FOR-621?page=all ]
Thorsten Scherler updated FOR-621:
--
Summary: Enable views as well for resource-types (aka doc-types) (was:
Enable views as well for document doctype)
Fix Version: 0.8-dev
On Sun, 2005-08-14 at 21:56 +0100, Ross Gardler wrote:
> Thorsten Scherler (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/FOR-621?page=all ]
> >
> > Thorsten Scherler updated FOR-621:
> > --
> >
> > Fix Version: 0.9
> >Priority: Minor (w
On Sun, 2005-08-14 at 21:56 +0100, Ross Gardler wrote:
> Thorsten Scherler (JIRA) wrote:
> > [ http://issues.apache.org/jira/browse/FOR-624?page=all ]
> >
> > Thorsten Scherler updated FOR-624:
> > --
> >
> > Fix Version: 0.9
> >Priority: Minor (w
[ http://issues.apache.org/jira/browse/FOR-624?page=all ]
Thorsten Scherler updated FOR-624:
--
Fix Version: 0.8-dev
(was: 0.9)
> Different output formats with views
> ---
>
> Key: FOR-624
>
[ http://issues.apache.org/jira/browse/FOR-624?page=all ]
Thorsten Scherler updated FOR-624:
--
Summary: Different output formats with views (was: Scope of views)
Priority: Major (was: Minor)
> Different output formats with views
>
- Original Message -
From: "Ross Gardler" <[EMAIL PROTECTED]>
|
| Jira has powerful filtering facilities, email notification (although it
| seems to be broken right now), XML feeds and the like. We should utilise
| it to keep track of what we *should* be doing. For example, would it be
|
[ http://issues.apache.org/jira/browse/FOR-583?page=all ]
Work on FOR-583 started by Thorsten Scherler
> Pelt compatible [views/templates] skin
> --
>
> Key: FOR-583
> URL: http://issues.apache.org/jira/browse/FOR-583
> Project:
[ http://issues.apache.org/jira/browse/FOR-583?page=all ]
Thorsten Scherler reassigned FOR-583:
-
Assign To: Thorsten Scherler (was: Diwaker Gupta)
> Pelt compatible [views/templates] skin
> --
>
> Key: FO
Tim Williams wrote:
On 8/14/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
Tim Williams wrote:
...
There isn't an immediate need for the latter, but there is a need for
the former, so why the question? Do you have another solution for the
forrest locationmap in mind?
nope, just wanted to k
On 8/14/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
> Tim Williams wrote:
> > On 8/13/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
> >
>
> ...
>
> >>In addition to this it is important that we keep track of what is going
> >>on in terms of strategy. There are so many great ideas here in Forrest
>
[ http://issues.apache.org/jira/browse/FOR-232?page=all ]
Ross Gardler closed FOR-232:
Resolution: Won't Fix
Skins are to be deprecated in 0.8 in favour of forrest:views
> skin fetching cleanup
> -
>
> Key: FOR-232
>
[ http://issues.apache.org/jira/browse/FOR-183?page=all ]
Ross Gardler closed FOR-183:
Resolution: Won't Fix
Skins are to be deprecated in 0.8 in favour of forrest:views
> New and consistent skin layout
> --
>
> Key
[ http://issues.apache.org/jira/browse/FOR-201?page=all ]
Ross Gardler closed FOR-201:
Resolution: Won't Fix
This issue is being addressed by forrest:views which will deprecate skins in 0.8
> Common template to add alternate views in docs
> ---
On 8/14/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
> Tim Williams wrote:
> > Is it enough to have locationmaps mounted as a sibling to components
> > and locator? or, should we support mounting inside match statements as
> > well? I think this first way supports our Forrest internal needs of
> >
[I'm replying onlist so we can discuss easily, I'll post summaries to
the issue when we reach a conclusion.]
Thorsten Scherler (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-632?page=comments#action_12318751 ]
Thorsten Scherler commented on FOR-632:
-
Tim Williams wrote:
Is it enough to have locationmaps mounted as a sibling to components
and locator? or, should we support mounting inside match statements as
well? I think this first way supports our Forrest internal needs of
project-level locations preferenced to app-level locations, I just
d
Thorsten Scherler (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-621?page=all ]
Thorsten Scherler updated FOR-621:
--
Fix Version: 0.9
Priority: Minor (was: Major)
Actually I see this as a major requirement. It is *very* powerful.
I
Thorsten Scherler (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-624?page=all ]
Thorsten Scherler updated FOR-624:
--
Fix Version: 0.9
Priority: Minor (was: Major)
This is definitely a major issue that will have to be fixed for 0.8 -
Tim Williams wrote:
On 8/13/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
...
In addition to this it is important that we keep track of what is going
on in terms of strategy. There are so many great ideas here in Forrest
that we simply can't implement them all.
Jira is the tool for keeping tr
[
http://issues.apache.org/jira/browse/FOR-623?page=comments#action_12318758 ]
Ross Gardler commented on FOR-623:
--
Err..no.. I wrote that on the plane on the way home from ApacheCon, my memory
does not work properly some times...
> Possibly too many confi
On 8/13/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
> We are getting larger as a developer base. As a consequence there is an
> increasing tendencies for small numbers of devs to work on different
> sections of the code base. As a result we are becoming a little
> disorganised - one virtual team no
[ http://issues.apache.org/jira/browse/FOR-626?page=all ]
Thorsten Scherler updated FOR-626:
--
Priority: Minor (was: Major)
> Reusing Cocoon Portal Engine
>
>
> Key: FOR-626
> URL: http://issues.apache.org/
[ http://issues.apache.org/jira/browse/FOR-625?page=all ]
Thorsten Scherler updated FOR-625:
--
Priority: Minor (was: Major)
> Scope of themes
> ---
>
> Key: FOR-625
> URL: http://issues.apache.org/jira/browse/FOR-625
>
[ http://issues.apache.org/jira/browse/FOR-624?page=all ]
Thorsten Scherler updated FOR-624:
--
Fix Version: 0.9
Priority: Minor (was: Major)
> Scope of views
> --
>
> Key: FOR-624
> URL: http://issues.apache.org/jira
[ http://issues.apache.org/jira/browse/FOR-623?page=all ]
Thorsten Scherler updated FOR-623:
--
Summary: Possibly too many configuration files for views (was:
Configuration of views)
Fix Version: 0.9
Priority: Minor (was: Major)
Can you
[ http://issues.apache.org/jira/browse/FOR-621?page=all ]
Thorsten Scherler updated FOR-621:
--
Fix Version: 0.9
Priority: Minor (was: Major)
> Enable views as well for document doctype
> -
>
> Key:
[ http://issues.apache.org/jira/browse/FOR-573?page=all ]
Tim Williams reassigned FOR-573:
Assign To: Tim Williams
> Provide locationmap mounting capability
> ---
>
> Key: FOR-573
> URL: http://issues
[ http://issues.apache.org/jira/browse/FOR-621?page=all ]
Thorsten Scherler updated FOR-621:
--
Summary: Enable views as well for document doctype (was: Deciding which
view to use)
The doctype should be *another* possibility to resolve a view. It should
Is it enough to have locationmaps mounted as a sibling to components
and locator? or, should we support mounting inside match statements as
well? I think this first way supports our Forrest internal needs of
project-level locations preferenced to app-level locations, I just
don't know that I see u
[
http://issues.apache.org/jira/browse/FOR-632?page=comments#action_12318751 ]
Thorsten Scherler commented on FOR-632:
---
"However, this is not a perfect solution since there is now way of knowing what
format the contract produces." -> That is not 100%
38 matches
Mail list logo
