Thorsten Scherler wrote:
> Hello guys,
>
> I have a question about Adobe Indesign license.
>
> Would it be ok to partly reverse engineer the inx - format for us within
> a plugin?
>
> I am not talking about the whole format. I am talking about some
> attributes and storing habits of values.
I
Done. That clarifies the Roadmap.
Do any people out in the Forrest dev community
know other things that we can do to improve our use
of Jira? Or point to projects that use it well.
--David
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Ross, during the move of the status/changes/todo processing
into the projectInfo plugin, the status.xml file was removed
at main/fresh-site/status.xml ... Was that deliberate?
...
I did remove it because I moved the functionality from
Hello guys,
I have a question about Adobe Indesign license.
Would it be ok to partly reverse engineer the inx - format for us within
a plugin?
I am not talking about the whole format. I am talking about some
attributes and storing habits of values.
The idea would be to have inx-templates (expo
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-471
Here is an overview of the issue:
-
Key
[EMAIL PROTECTED] wrote:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-470
Here is an overview of the issue:
---
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
What i am proposing now is an extra step. Remove the option
"HEAD version" entirely from Jira. I think it is superfluous.
Sorry - I'm reading too fast this morning.
If a bug is introduced into head (i.e. wasn't in the previous release)
Ross Gardler wrote:
David Crossley wrote:
Just a quick note, gotta rush out now. Yes there was stacks of discussion
on this topic, but its good to be sure that we all understand, and maybe
there is a flaw.
The docs that are currently at docs/dev/ are 0.7-dev
They will move to /docs/ when the next r
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-470
Here is an overview of the issue:
-
Key
Ross Gardler wrote:
> David Crossley wrote:
> >Just a quick note, gotta rush out now. Yes there was stacks of discussion
> >on this topic, but its good to be sure that we all understand, and maybe
> >there is a flaw.
> >
> >The docs that are currently at docs/dev/ are 0.7-dev
> >They will move to /
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project forrest-test has an issue affecting its community integration.
This issue affects
The following comment has been added to this issue:
Author: David Crossley
Created: Fri, 18 Mar 2005 5:20 AM
Body:
And another one ...
2005-03-17
problem with docs at forrest.apache.org/docs/dev/'
http://marc.theaimsgroup.com/?t=0508874
The following comment has been added to this issue:
Author: David Crossley
Created: Fri, 18 Mar 2005 5:18 AM
Body:
Some discussion on this topic ...
2004-11-02
website documentation version
http://marc.theaimsgroup.com/?t=10993759641
2004-11-10
[HEADS-UP] doc reorg
http://mar
Ross Gardler wrote:
> David Crossley wrote:
> >Ross, during the move of the status/changes/todo processing
> >into the projectInfo plugin, the status.xml file was removed
> >at main/fresh-site/status.xml ... Was that deliberate?
> >
> >http://svn.apache.org/viewcvs?view=rev&rev=156244
>
> Ahhh...
David Crossley wrote:
Ross Gardler wrote:
Johannes Schaefer wrote:
So far this works fine.
Now I need to insert the search term dynamically
from the form on the page. I simply don't know how
to do that. Do I need to create a Cocoon action?
One way would be to use the request generator in Cocoon
David Crossley wrote:
Ross, during the move of the status/changes/todo processing
into the projectInfo plugin, the status.xml file was removed
at main/fresh-site/status.xml ... Was that deliberate?
http://svn.apache.org/viewcvs?view=rev&rev=156244
Ahhh... hmmm... yes... well... errr... I should hav
Ross Gardler wrote:
> Johannes Schaefer wrote:
>
> >So far this works fine.
> >
> >Now I need to insert the search term dynamically
> >from the form on the page. I simply don't know how
> >to do that. Do I need to create a Cocoon action?
>
> One way would be to use the request generator in Cocoon
Ross Gardler wrote:
> David Crossley wrote:
> >What i am proposing now is an extra step. Remove the option
> >"HEAD version" entirely from Jira. I think it is superfluous.
>
> Sorry - I'm reading too fast this morning.
>
> If a bug is introduced into head (i.e. wasn't in the previous release)
>
Ross, during the move of the status/changes/todo processing
into the projectInfo plugin, the status.xml file was removed
at main/fresh-site/status.xml ... Was that deliberate?
http://svn.apache.org/viewcvs?view=rev&rev=156244
--David
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse t
David Crossley wrote:
Cyriaque Dupoirieux wrote:
Ok, Ross,
I was wrong once again, I was not looking in the good direction...
In fact, my status.xml declared a before the tag.
(I use this section to describe - in my history of modification -
the rules I apply to choose the next version of
Ross Gardler wrote:
> David Crossley wrote:
> >We need to be continually cleaning up our Jira issue tracker.
> >There is a lot of clutter and it means that we cannot have a
> >good view of our situation.
> >
> >We recently defined a stack categories. That helps to provide
> >other ways to browse th
Cyriaque Dupoirieux wrote:
I don't explain this strange behavior, our problem is that no DTD
controls the status.xml...
Yes. This is something that needs to be sorted out now that we have the
projectInfo plugin.
Ross
Johannes Schaefer wrote:
...
So far this works fine.
Now I need to insert the search term dynamically
from the form on the page. I simply don't know how
to do that. Do I need to create a Cocoon action?
One way would be to use the request generator in Cocoon (
http://cocoon.apache.org/2.1/userdocs/
Cyriaque Dupoirieux wrote:
> Ok, Ross,
>
>I was wrong once again, I was not looking in the good direction...
>In fact, my status.xml declared a before the tag.
>(I use this section to describe - in my history of modification -
> the rules I apply to choose the next version of my sit
David Crossley wrote:
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse the outstanding issues.
Today i removed the
Ok, Ross,
I was wrong once again, I was not looking in the good direction...
In fact, my status.xml declared a before the tag.
(I use this section to describe - in my history of modification -
the rules I apply to choose the next version of my site (3 digits
version...))
When I real
OK, here is what I've done and some questions.
To experiment I created a project with a local
sitemap.xmap [1]. This contains a fixed search
request to the google search server at port 4664.
"format=xml" gives us a nice XML file back where
we can extract and present the information [2]
So far this
We need to be continually cleaning up our Jira issue tracker.
There is a lot of clutter and it means that we cannot have a
good view of our situation.
We recently defined a stack categories. That helps to provide
other ways to browse the outstanding issues.
Today i removed the 0.6.1 release versi
The ASF infrastructure is doing work on the servers over this
extended weekend. So you may find that some services are not
available. The websites will automatically fail-over to another
server. The mail is the priority, and they will try to have
it up again ASAP. The SVN and ViewCVS will probably
30 matches
Mail list logo
