[
https://issues.apache.org/jira/browse/FOR-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12875375#action_12875375
]
David Crossley commented on FOR-1170:
-
Please see how it was handled with skins above
[
https://issues.apache.org/jira/browse/FOR-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12875391#action_12875391
]
David Crossley commented on FOR-1168:
-
I presume that this is handled in main/webapp
One very important reason for designing the plugin system
the way that we did, was to ensure that each plugin has
its own community supporting it.
-David
[
https://issues.apache.org/jira/browse/FOR-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12875433#action_12875433
]
David Crossley commented on FOR-1168:
-
I reckon that this is a good solution.
However
Gav... wrote:
David Crossley wrote:
One very important reason for designing the plugin system
the way that we did, was to ensure that each plugin has
its own community supporting it.
That doesn't seem to be the case to me at the moment, ...
That is one reason that i raised this issue
David Crossley wrote:
Tim Williams wrote:
The draft
release doc in the plugins directory suggests that its possible to
release plugins independent of the core but couldn't we, for now, just
as well continue to do what we do and release the plugins with the
core?
Ah, but it sounds
[
https://issues.apache.org/jira/browse/FOR-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1190:
Component/s: Plugin: input.dtdx
DTD Document Documentation lists empty links
and website, Example Sites, Plugins
(general issues)
Reporter: David Crossley
Follow the Apache Project Branding Guidelines
http://apache.org/foundation/marks/pmcs
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Sjur Moshagen wrote:
Here's my output:
jar:
Building jar:
/usr/local/forrest/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/build/org.apache.forrest.plugin.internal.dispatcher.jar
Did you see this bug (now fixed).
https://issues.apache.org/jira/browse/FOR-1195
the
Gav... wrote:
We are now listed at [1] and [2] with nice zero (0) against our name.
Gav...
[1] - http://ci.apache.org/projects/rat-master-summary.html
[2] - http://ci.apache.org/projects/forrest/rat-output.html
Fantastic, thanks.
I will update oour Forrest reference to it.
-David
Sina K. Heshmati wrote:
I think we should stop using the svncommit and svncheckout tasks since:
- There's almost no documentation available for them.
- They don't remove the need for executing the svn command.
Maybe we could consider using [1], which is BTW released under ASL 1.1 [2].
Tim Williams wrote:
Anyone else getting:
compile:
[javac] Compiling 1 source file to
/Users/twilliams/Development/forrest/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/build/classes
[javac]
Components: Plugins (general issues)
Affects Versions: 0.9-dev
Reporter: David Crossley
Fix For: 0.9-dev
Doing 'forrest clean-site' or 'forrest clean' does deal with the site stuff
for a plugin's site.
However, doing '...ant clean' does not remove the plugin's build
[
https://issues.apache.org/jira/browse/FOR-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-1195.
---
Resolution: Fixed
Fixed.
the plugins 'clean' target should remove previously built classes
[
https://issues.apache.org/jira/browse/FOR-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1170:
Fix Version/s: 0.9-dev
(was: 0.10)
Component/s: Plugin
Project: Forrest
Issue Type: Task
Components: Documentation and website, Plugins (general issues)
Reporter: David Crossley
The ability to add trademark statements was added with FOR-1170 as part of
the need to improve project branding.
We applied
Tim Williams wrote:
I guess I've never investigated how forrestbot actually works, but
this jsvn library is terrible. I can't find any documentation and all
the useful links are broken. I was trying to find out if there was a
--no-auth-cache equivalent for that svncheckout task. I wonder
Gav... wrote:
maybe:
rm -Rf ~/.ssh/auth
I suppose that you mean ~/.subversion/auth
Yeah already tried that in desperation. Tried again now
but same issue.
So now you have removed the auth/svn.ssh directory, can you still
commit normally to trunk, using the same password
Gav... wrote:
I'd like to add our RAT report
(http://ci.apache.org/projects/forrest/rat-output.txt)
to the http://ci.apache.org/projects/rat-master-summary.html page.
To do that, I need to produce an .xml output, not the .txt version currently
produced.
Any problems with me doing that
Tim Williams wrote:
David Crossley wrote:
Tim Williams wrote:
Just a guess, if you use keychain, is it out of sync with a recently
updated password change?
Thanks for trying. No, it is not that. The ASF Committers
password is there, and i can commit okay.
However, it is just my
We do have a process sorted out for releasing of Forrest core.
[1] How to release Forrest
http://forrest.apache.org/procedures/release/How_to_release.html
I reckon that it meets the ASF requirements. Please see
this email where i have before tried to ensure that we do:
[2]
Tim Williams wrote:
David Crossley wrote:
The release process issue? relative to plugins I assume?
Yep, as i said, i reckon that our core releae process is fine.
Just the release process for each plugin needs attention.
The draft
release doc in the plugins directory suggests that its
I am still having this trouble deploying our website.
Would another committer please see how they go:
$] cat $FORREST_HOME/etc/publishing_our_site.txt
Note that i have confirmed my $FORREST_HOME/deploy.svn.settings file.
I can commit changes to the sources.
Just having trouble with:
$]
Tim Williams wrote:
Just a guess, if you use keychain, is it out of sync with a recently
updated password change?
Thanks for trying. No, it is not that. The ASF Committers
password is there, and i can commit okay.
However, it is just my local forrestbot that is not working.
That is why i
[
https://issues.apache.org/jira/browse/FOR-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12575227#action_12575227
]
David Crossley edited comment on FOR-1069 at 5/20/10 3:11 AM
Tim, it is great that you are helping to follow-up on the ECCN issue.
My mind has gone all rusty on this topic. I also struggled at the time
to understand and deal with the job. So i am having trouble answering
your FOR-1069 comments.
I suppose that we make the task more complex because we
[
https://issues.apache.org/jira/browse/FOR-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868074#action_12868074
]
David Crossley commented on FOR-985:
Yes, i agree that it is now broken. Tried various
At the recent ASF Members Meeting in March 2010
there were 23 new members elected.
Congratulations to Brian Dube and Tim Williams.
With the elections, each ASF member who votes considers
their own criteria. So thanks to you both for whatever
stood out.
-David
Brian M Dube wrote:
Sjur Moshagen wrote:
I'm not able to build my site anymore, due to the following error:
X [0] linkmap.html BROKEN:
ElemTemplateElement error: carry-body-attribs
I was finally able to track down the cause of the error
/FOR-1193
Project: Forrest
Issue Type: Task
Components: Core operations, Plugin: output.pdf
Affects Versions: 0.9-dev
Reporter: David Crossley
Recently the Cocoon-2.1 FOP Block was updated, so we might be able to remove
our home-grown version.
See
[
https://issues.apache.org/jira/browse/FOR-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12867090#action_12867090
]
David Crossley commented on FOR-1193:
-
Some snippets from our PDF Plugin's changes file
Thorsten, it seems that your Subversion client has configuration problems.
Missing eol-style and should not be executable.
See:
http://apache.org/dev/#svn
http://apache.org/dev/version-control.html#https-svn-config
-David
Author: thorsten
Date: Wed May 5 15:28:14 2010
New Revision: 941344
(Moved from user list. Please see background in thread
Subject: For input string: :0
http://thread.gmane.org/gmane.text.xml.forrest.user/4903)
more below ...
Richard Suematsu wrote:
Ok, I must be doing something wrong because I tried this on my mac at
home and I get the same error. Let me
[
https://issues.apache.org/jira/browse/FOR-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12862986#action_12862986
]
David Crossley commented on FOR-1123:
-
Another useful forrest-dev thread, where Carsten
Reporter: David Crossley
Some Cocoon Blocks have started in the Forrest whiteboard.
These need a well-defined release procedure, voting, and such.
Anything that goes beyond this developer group needs to be properly released.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/FOR-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12862988#action_12862988
]
David Crossley commented on FOR-1191:
-
Some links:
More info at http://apache.org/dev
: Forrest
Issue Type: Sub-task
Components: Project administration
Reporter: David Crossley
The rest of Forrest uses a manual license system where we have a *.license.txt
file for each supporting product and we add its license to top-level
LICENSE.txt and any required
Tim Williams wrote:
Well, if the dispatcher is all that changed in such a release, we
could do a 0.91 afterwards. I think there's another consideration
that I didn't mention too. I feel irresponsible releasing software
that we can't support and I'm concerned that this would be the case
[
https://issues.apache.org/jira/browse/FOR-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861253#action_12861253
]
David Crossley commented on FOR-644:
Yes that is correct. Just before release is the ideal
[
https://issues.apache.org/jira/browse/FOR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859593#action_12859593
]
David Crossley commented on FOR-1177:
-
Thanks. I had a look too. The way the jar
[
https://issues.apache.org/jira/browse/FOR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley reopened FOR-1177:
-
Thanks for doing that part of the task.
We also need to follow the license requirements:
e.g.
http
On Mon, Apr 12, 2010 David Crossley wrote:
...
[java] X [0] forrest-issues.html
BROKEN: /export/home/config/forrestbot-trunk/conf/work/forrest-docs/. (Is a
directory)
...
Now that Jira is back online, we seem to be getting this problem
[
https://issues.apache.org/jira/browse/FOR-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley reopened FOR-831:
Assignee: (was: Forrest Developers)
Removing the Assignee.
Dispatcher Build, Clean and Deploy
Tim Williams wrote:
Ok, I think that answers it. I *think* the issues is retrieved from a
file generator which likely only resolves resources directly from a
URL - I suspect it isn't a full client good enough to follow a 302
redirect. I suspect switching to a requestgenerator would have
Automated build for forrest-docs FAILED
...
[java] X [0] forrest-issues.html
BROKEN: /export/home/config/forrestbot-trunk/conf/work/forrest-docs/. (Is a
directory)
...
Now that Jira is back online, we seem to be getting this problem
on every run,
Automated build for forrest-sample-2 FAILED
[java]
[java]
[java] X [0] linkmap.htmlBROKEN:
Could not resolve locationmap location.
I get that same error doing 'build.sh test' locally.
The build of this Dispatcher sample were okay on
David Crossley wrote:
Gav... wrote:
I've altered the zone setup to point to Java 1.5
Thanks. However please note that most scripts and
config are under version control in the forrest/zone SVN.
So don't just edit them on the server.
http://forrest.apache.org/zone.html
I've also
Would another committer try to publish the Forrest project docs:
$] cat etc/publishing_our_site.txt
I haven't tried since before the recent SVN access changes.
Note that i have edited my $FORREST_HOME/deploy.svn.settings file.
I can commit changes to the sources.
Just having recent trouble
Gav... wrote:
From: David Crossley
I haven't tried since before the recent SVN access changes.
hmm, LDAP has been introduced but this shouldn't have affected svn access in
any way.
Your old svn password is still your svn password. The main change is that
your people.a.o changed
I did just now use https://svn.apache.org/change-password
to sync the two.
However the situation is still the same.
-David
Gav... wrote:
The Cocoon 2.1 docs are being built twice a day on our zone.
http://forrest.zones.apache.org/ft/build/cocoon-docs/2.1/index.html
However, the official documentation for Cocoon 2.1 docs at
http://cocoon.apache.org/2.1/
has not been updated since 2008.
I suggest
Gav... wrote:
I've altered the zone setup to point to Java 1.5
Thanks. However please note that most scripts and
config are under version control in the forrest/zone SVN.
So don't just edit them on the server.
http://forrest.apache.org/zone.html
I've also set the recipient to myself
Gav... wrote:
This vote is to move 'trunk' to using java version 1.5.
+1
Gav... wrote:
I see Davids thread 'strange dispatcher behaviour after merge' is exactly the
same problems
as I am getting now. David, I see no follow up solution, what did you do to
get it going again?
I also note Brian says he is not having any issues either, Brian, what did
you need
Done, though it takes a couple hours to be published.
All the best Roger, and to the club.
-David
Brian M Dube wrote:
I'm still looking into all this, but how are you and the zone testing
the dispatcher with 1.4.x? There features there that require 1.5 to
build.
The zone does a 'clean; build' every 2 hours. Java 1.4.2 is the
base until the Forrest project decides to move forward.
Brian M Dube wrote:
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
This edit prompted me to browse through this file for the first time
in a while. I didn't see it noted anywhere to turn off debug symbols
and to turn on code optimization as part of the
Cyriaque Dupoirieux wrote:
Brian M Dube a ?crit :
This last bit doesn't belong in this thread, but I noticed it while
looking into this issue and I'm being lazy. The icon-b.png
error. Maybe not everyone experiences it, but I believe it has been
brought up before.
Yes this build error
Cyriaque Dupoirieux wrote:
I don't succeed to generate the basic forrest seed with the dispatcher.
I just tried a fresh seed site, and no such problems here
(Macintosh with either java-1.5 or 1.4.2).
Also the forrestbot on the zone server is not reporting such problems
(Solaris 10 with
Affects Versions: 0.8, 0.7
Reporter: David Crossley
Fix For: 0.9-dev
Around January 2008 the PDF plugin was upgraded, gaining functionality that was
only relevant to forrest-0.9-dev. It was re-deployed without changing the
version numbers in the plugin descriptor
[
https://issues.apache.org/jira/browse/FOR-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791818#action_12791818
]
David Crossley commented on FOR-1187:
-
See discussions at:
Re: How to merge FOP94-branch
Components: Other
Reporter: David Crossley
Fix For: 0.9-dev
If there is no project logo, then Forrest generates one using SVG. However that
is not wide enough to accommodate some project names. Also the right-hand end
is hard against the edge.
--
This message
[
https://issues.apache.org/jira/browse/FOR-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-1186.
---
Resolution: Fixed
generated project-logo via SVG not wide enough for project name
[
https://issues.apache.org/jira/browse/FOR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-95:
--
Affects Version/s: 0.9-dev
Following through on that linked discussion, Cameron did some investigation
Thorsten Scherler wrote:
One thing we did not had before in any release is that we have some
maven artifacts in our svn rep.
whiteboard/cocoon-2.2-blocks
Are we going to deploy those to the maven rep?
We have decided in the past to use Ivy, and gradually integrate
that with our build
Components: zones.a.o administration
Reporter: David Crossley
The forrest.properties file for our forrest-sample-2 has some manual edits
to enable the Dispatcher. This was a quick fix to get a sample site. It is an
SVN checkout of the normal seed-sample with server-side edits
Brian M Dube wrote:
Brian M Dube wrote:
Aside from the Java version issue, forrest-sample-2 still tries to
pull in o.a.f.themes.core.
I've adjusted forrest.properties in
/var/apache2/htdocs/ft/work/svn/forrest-sample-2.
Yes, and i had to remove the config for another old plugin
to
[
https://issues.apache.org/jira/browse/FOR-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12786761#action_12786761
]
David Crossley commented on FOR-1185:
-
That is an automated SVN checkout of course. Here
Tim Williams wrote:
reason I ask, is that we have FOR-1198 and FOR-796 both as blockers
No such issue. Rather FOR-1108 and FOR-796.
-David
Brian M Dube wrote:
David Crossley wrote:
Dispatcher seems to have some strange behaviours after the recent merge.
It sounds like someone needs to get the PMC to agree on
increasing the base Java version.
I don't think I was around for the last Java version bump. What would
keep us
Dispatcher seems to have some strange behaviours after the recent merge.
I don't have much time, so here is a quick dump of notes.
Perhaps someone else can raise Jira issues for them.
Using Java-1.5
1) Rebuild forrest. All seems okay.
2) cd
Tim Williams wrote:
This is fairly trivial, but I'm thinking we'd help things by
separating those issues that simply need to be done as a part of
every release vs. actual issues targeted at a specific release. I
see two ways to help:
a) Add a new version with, instead of a -dev
[
https://issues.apache.org/jira/browse/FOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-241:
---
Affects Version/s: 0.9-dev
0.8
character entities (e.g. ampersand) are expanded
[
https://issues.apache.org/jira/browse/FOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-241.
--
Resolution: Fixed
Fix Version/s: (was: 0.10)
0.9-dev
I did some tests
David Crossley wrote:
Brian M Dube wrote:
David Crossley (JIRA) wrote:
The zone machine update is not scheduled, as far as i know (i just heard
it being talked about on one of the Infra lists).
Is this happening? I haven't been able to access helios for at least a
day.
I have
David Crossley wrote:
Our forrestbot on the zone server is not running at the moment.
See https://issues.apache.org/jira/browse/FOR-1179
and the replies to this dev list.
Other than monitor the infrastructure mail lists and #asfinfra
and perhaps help, there is not much we can do.
So
[
https://issues.apache.org/jira/browse/FOR-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-630:
---
Priority: Major (was: Critical)
I disagree. I see many items that are still relevant. But don't need
[
https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-1183.
---
Resolution: Fixed
I checked again, and yes can confirm that it now works. Something at the Jira
end
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
Tim Williams wrote:
FOR-855 verify the license situation prior to each release
- housekeeping
I believe Davids work with RAT fixes this issue.
No it does
[
https://issues.apache.org/jira/browse/FOR-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley reopened FOR-1183:
-
Hmmm, found a search which exhibits the problem (so re-opening).
Use Forrestbar to do the following
Affects Versions: 0.9-dev
Reporter: David Crossley
Fix For: 0.9-dev
After the last release, an issue was brought to our attention about using
unreleased code from other projects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add
[
https://issues.apache.org/jira/browse/FOR-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781758#action_12781758
]
David Crossley commented on FOR-1184:
-
Here is the last part of the discussion:
Date
[
https://issues.apache.org/jira/browse/FOR-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781759#action_12781759
]
David Crossley commented on FOR-1184:
-
There are also some other unreleased jars for some
[
https://issues.apache.org/jira/browse/FOR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781275#action_12781275
]
David Crossley commented on FOR-1177:
-
To try to clarify ... Please see comments above
Ross Gardler wrote:
David Crossley wrote:
Ross Gardler wrote:
Tim Williams wrote:
FOR-855 verify the license situation prior to each release
- housekeeping
I believe Davids work with RAT fixes this issue.
No it does not. There is much more to the job that that.
I meant
Ross Gardler wrote:
Tim Williams wrote:
FOR-855 verify the license situation prior to each release
- housekeeping
I believe Davids work with RAT fixes this issue.
No it does not. There is much more to the job that that.
FOR-1177 ? ? ? ?where does forrest use Rhino
Not a blocker
Tim Williams wrote:
The following are the issues considered blockers. I feel
comfortable moving others under lazy consensus to the next release,
Oh, good on you Tim. I meant to say something a few days ago
when you started to review the Issues situation. That is what
it takes to start things
Our forrestbot on the zone server is not running at the moment.
See https://issues.apache.org/jira/browse/FOR-1179
and the replies to this dev list.
Other than monitor the infrastructure mail lists and #asfinfra
and perhaps help, there is not much we can do.
So be aware that it will not be
administration
Reporter: David Crossley
The zones.apache.org is going to be having its machine and OS updated soon.
We need to plan for migration of our forrestbot installation.
Most of the config is in SVN, and some info is at
http://forrest.apache.org/zone.html
Need
[
https://issues.apache.org/jira/browse/FOR-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-676.
--
Resolution: Fixed
I think that it is fixed. Doing 'svn log' shows that i did quite a bit of
fine-tuning
[
https://issues.apache.org/jira/browse/FOR-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-1083.
---
Resolution: Fixed
Closing this duplicate of FOR-955
switch to Cocoon 2.1.x
[
https://issues.apache.org/jira/browse/FOR-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1092:
Fix Version/s: 0.10
Affects Version/s: 0.10
Investigate this for our v0.10
review our
[
https://issues.apache.org/jira/browse/FOR-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1091:
Fix Version/s: 0.10
Description: We need to review our main/webapp/WEB-INF/cocoon.xconf
[
https://issues.apache.org/jira/browse/FOR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12779793#action_12779793
]
David Crossley commented on FOR-413:
I changed the linkmap-to-document.xsl stylesheet
[
https://issues.apache.org/jira/browse/FOR-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1171:
Fix Version/s: (was: 0.9-dev)
0.10
Moving to 0.10-dev version. I have trouble
[
https://issues.apache.org/jira/browse/FOR-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-1173.
---
Resolution: Fixed
Assignee: (was: David Crossley)
add demonstration of using xml source
[
https://issues.apache.org/jira/browse/FOR-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1138:
Fix Version/s: (was: 0.9-dev)
0.10
Affects Version/s
[
https://issues.apache.org/jira/browse/FOR-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777388#action_12777388
]
David Crossley commented on FOR-1016:
-
I stumbled across this today via the Cocoon users
[
https://issues.apache.org/jira/browse/FOR-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley updated FOR-1016:
Summary: upgrade our packaged Cocoon to use current Cocoon-2.2 (was:
upgrade our packaged Cocoon
[
https://issues.apache.org/jira/browse/FOR-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12776869#action_12776869
]
David Crossley commented on FOR-1177:
-
Here is one discussion thread:
Subject: cocoon
401 - 500 of 3078 matches
Mail list logo
