Gav wrote:
code/code is really meant for inline code fragments. If you are
intending for larger sections of code then there is the
blockcode/blockcode element [2].
I don't think it the norm to change mod files to suit styling requirements,
why can you not add italic or whatever to a CSS
David Crossley wrote:
If people want to revisit this decision then please
speak up ASAP.
I'm happy with our past decision.
I suppose an alternative is to completely abandon the
plugins/status.xml files. We could then prefix each
text entry with its plugin's name. Or we could have
a context
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 has an issue affecting its community integration.
This issue affects 1
Ross Gardler wrote:
Gav wrote:
code/code is really meant for inline code fragments. If you are
intending for larger sections of code then there is the
blockcode/blockcode element [2].
I don't think it the norm to change mod files to suit styling
requirements,
why can you not add italic
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
[
http://issues.apache.org/jira/browse/FOR-839?page=comments#action_12415509 ]
Ross Gardler commented on FOR-839:
--
As David pointed out on IRC (Forrest Friday) the problem is in:
[ http://issues.apache.org/jira/browse/FOR-839?page=all ]
Thorsten Scherler closed FOR-839:
-
Resolution: Fixed
Using the Muenchian Method for grouping
http://www.jenitennison.com/xslt/grouping/muenchian.html
projectInfo plugin does not list all
El vie, 09-06-2006 a las 12:06 +1000, David Crossley escribió:
We decided a while ago and reinforced it recently,
that the detailed changes about plugins go in to
the status.xml files within each plugin.
The top-level site-author/status.xml would hold stuff
related to the current core, the
El vie, 09-06-2006 a las 13:56 +1000, David Crossley escribió:
...
We also have a proposal or two in our archives, to use
committer Id rather than these RDG, DC, TWW, etc. for
the @dev attribute, so probably should not overload it.
I am +1 for using the committer Id.
salu2
--
thorsten
Thorsten Scherler wrote:
David Crossley escribi??:
...
We also have a proposal or two in our archives, to use
committer Id rather than these RDG, DC, TWW, etc. for
the @dev attribute, so probably should not overload it.
I am +1 for using the committer Id.
Me too. However, it has twice
[ http://issues.apache.org/jira/browse/FOR-839?page=all ]
Ross Gardler reopened FOR-839:
--
The applied solution does include all contributors, but it also creates
duplicate entries for contributors.
For example, Addison Berryappears three times in the
El vie, 09-06-2006 a las 10:44 +, Ross Gardler (JIRA) escribió:
[ http://issues.apache.org/jira/browse/FOR-839?page=all ]
Ross Gardler reopened FOR-839:
--
The applied solution does include all contributors, but it also creates
duplicate
[ http://issues.apache.org/jira/browse/FOR-839?page=all ]
Ross Gardler closed FOR-839:
Resolution: Fixed
Assign To: Thorsten Scherler
My mistake - I had a local change that was messing with Thorstens patch.
Sorry for the noise.
projectInfo
[ http://issues.apache.org/jira/browse/FOR-839?page=all ]
Ross Gardler reopened FOR-839:
--
Assign To: (was: Thorsten Scherler)
Reopening for a different reason now
This does not fix the issue. In fact the results are exactly the same as they
[ http://issues.apache.org/jira/browse/FOR-839?page=all ]
Ross Gardler closed FOR-839:
Resolution: Fixed
We nailed it in the end - thanks to Thorsten and David on Forrest Friday IRC
projectInfo plugin does not list all Contributors
Should we add a new context to status.xml for projectAdmin? This would
include things like new committer announcements, changes to project
guidelines etc.
I'm thinking specifically of the items that normally go into the board
report.
We can then create a new rendering in the projectInfo
[
http://issues.apache.org/jira/browse/FOR-876?page=comments#action_12415549 ]
Gavin commented on FOR-876:
---
I tried this and it works fine for me in a freshly seeded site.
pa href=lm:rewriteDemo/indexThis link is rewritten to
an offsite address/a
[
http://issues.apache.org/jira/browse/FOR-876?page=comments#action_12415552 ]
David Crossley commented on FOR-876:
Gavin are you sure that this works for you. As described in the linked mail
message, you need to try
Ross Gardler wrote:
Should we add a new context to status.xml for projectAdmin? This would
include things like new committer announcements, changes to project
guidelines etc.
We already have an admin context in site-author/status.xml
Not sure what it is used for so far.
I'm thinking
[
http://issues.apache.org/jira/browse/FOR-876?page=comments#action_12415573 ]
Juan Jose Pablos commented on FOR-876:
--
Both fail in the same way:
on main/webapp/forrest.xmap:265:48
map:generate src={lm:project.{0}}/
goes to
match
[ http://issues.apache.org/jira/browse/FOR-876?page=all ]
Ross Gardler closed FOR-876:
Resolution: Cannot Reproduce
I can confirm that Gavins observations are correct. I just did a fresh site and
the rewrite demo works.
The remote functionality was
[ http://issues.apache.org/jira/browse/FOR-713?page=all ]
Ross Gardler closed FOR-713:
Resolution: Cannot Reproduce
H.
I created this issue, but the sample in fresh-site does not illustrate the
problem that I describe.
I guess that I was
Ross Gardler wrote:
Should we add a new context to status.xml for projectAdmin? This would
include things like new committer announcements, changes to project
guidelines etc.
I'm thinking specifically of the items that normally go into the board
report.
We can then create a new
Ross Gardler (JIRA) wrote:
http://issues.apache.org/jira/browse/FOR-876
Ross Gardler closed FOR-876:
Resolution: Cannot Reproduce
I can confirm that Gavins observations are correct. I just did a fresh site
and the rewrite demo works.
The remote
David Crossley wrote:
Ross Gardler (JIRA) wrote:
http://issues.apache.org/jira/browse/FOR-876
Ross Gardler closed FOR-876:
Resolution: Cannot Reproduce
I can confirm that Gavins observations are correct. I just did a fresh site and
the rewrite demo
[
http://issues.apache.org/jira/browse/FOR-876?page=comments#action_12415629 ]
Juan Jose Pablos commented on FOR-876:
--
well, this must be an enviromental problem.
I can see this problem:
WARN(2006-06-10) 02:24.59:460 [access]
[ http://issues.apache.org/jira/browse/FOR-876?page=all ]
Juan Jose Pablos reopened FOR-876:
--
When I try to access
http://localhost:/samples/remoteDemo/index.html
I got the error, maybe is a problem with the $COCOON_HOME ?
locationmap demo in
27 matches
Mail list logo
