Re: Self-organized meet-ups / workshops at Apache Con 2005
David Crossley wrote: Has anyone asked for a Birds-of-a-Feather session? I am not sure if non-registrants are allowed there, but maybe. Whatever, it would be a good chance for an extra meeting. I'm not familiar with them. What are they for and who would you ask about having one and inviting non-registrants. -- Ferdinand Soethe
Re: About unknow libraries within lib/core
David Crossley wrote: How do we know that users are not taking advantage of those jars for other purposes? Well, we do not know that, I guess that testing. We only can claim support for funcionality that is documented. And xsp is not documented as feature in our documentation, so I think that it should not been there. We had a discussion about including libraries, and I was the one that support adding them on forrest, so people could use them out of the box. But now I see that from the other point of view. For the standard distribution, you need only those libraries that are neede, if you want to custom forrest for other purposed, then cp $COCOON_HOME/lib/optional/castor*.jar $FORREST_HOME/lib/core is not a bit problem ¿right? I notice that you moved Chaperon jar too. It too can be used for far more than the wiki capabilities. I know, but within forrest we are only using for wiki, if someone want it for more, it can be copy that library back. Sorry for the noise, I am trying to tidy up where our libraries come from, so upgrade from cocoon is easier.. Cheers, cheche
Re: Self-organized meet-ups / workshops at Apache Con 2005
Thanks for explaining the fluffy things :-) David Crossley wrote: I don't know who to ask about either question. Start at http://www.apachecon.com/html/contact.html well I'm still wayting for a response to questions that I asked in March, but I'll give it another try. -- Ferdinand Soethe
BOF for Forrest
Hi, what is the procedure to apply for a room for additional and BOF meeting at ApacheCon. We'd like to have a BOF on Forrest and possibly one other meeting. Is it possible for non-registrants to participate in these? -- Ferdinand Soethe
Apache mail problem (Was Re: Self-organized meet-ups / workshops at Apache Con 2005)
Thorsten Scherler wrote: @all I think apache mail suffers from a worm called sober. The next attack is expected to happen in 10 days (around 26/27 May). It is once again a windows only thing. More information (in German) can be found http://www.spiegel.de/netzwelt/technologie/0,1518,356236,00.html. If Thorsten is correct about this (is he?), it is about time to start thinking about solutions. Don't know about you (except for Nicola Ken who only reads mail once a day :-) but I'm not too happy about these delays and the perspective for this to happen a couple of times each month. -- Ferdinand Soethe
Re: Self-organized meet-ups / workshops at Apache Con 2005
On Wed, 2005-05-18 at 10:54 +0200, Ferdinand Soethe wrote: Thorsten Scherler wrote: More or less. ;-) If I should explain a wee bit the plugin basics I used for the view package then I guess +1 hour would be fine. Better make it two then (You'll need one hour just to answer all my stupid beginners questions :-)) You mean in total 4 hours? ...then I guess everybody will bring his laptop to the workshop? ;-) ...and if Ross can come to the workshop he can help talking about the plugins as well. ;-) salu2 -- thorsten Together we stand, divided we fall! Hey you (Pink Floyd)
Re: Raw and process content directories
Ferdinand Soethe wrote: Maybe this has gotten lost in all the mail delays. Can anybody pls comment so that I can close FOR-470. Thanks, Ferdinand Soethe I wrote: Just to make sure I have this right before I rewrite any more documentation: In /docs/upgrading_07.html#raw I found: In 0.6 version, the raw content was placed in the src/documentation/content/ directory and potential sub-directories. In the generated site, these links would automatically function. Any linked file with .html extension was not processed and not adorned with Forrest skin and navigation menus. In 0.7 version, any file that is linked to, needs to be placed in the content/xdocs/ directory structure. Any linked file with .html extension is now processed and is adorned with Forrest skin and navigation menus. If you need to include files that are not linked to, then place them in the src/documentation/content/ directories as with the 0.6 version. So does any file that is linked to, needs to be placed in the content/xdocs/ really mean that I will get an error if I place a file that is linked to in the content-directory. Try it. Or does it mean can now be placed in either xdocs or content directory at my disgression depending on wether I want processing to happen or not. If you need to link to html files but want them to be un-processed, then place them in the src/documentation/content/ directories and add an entry to conf/cli.xconf to exclude them from processing. An FAQ describes the use of Cocoon's cli.xconf This last para seems to confirm the first version because otherwise I could just place the file into content rather than writing an exclusion rule. Thanks for making that clear. What FOR-470 is really about is needing someone to revise the self-documenting samples in the seed site. That would soon find out which methods work. Then clarify the upgrading_07 doc. Sorry, if i am going to try and explain it then i would rather go and do the job myself, because, like you i do not fully understand the ramifications of changing the behaviour from 0.6 version. The only way is to go and fix the seed site. --David
Re: Raw and process content directories
David Crossley wrote: Sorry, if i am going to try and explain it then i would rather go and do the job myself, because, like you i do not fully understand the ramifications of changing the behaviour from 0.6 version. The only way is to go and fix the seed site. OK, I didn't realize that nobody really knows, so I figured rather then testing against an unknown standard I'd rather ask. Will try and see what I get. -- Ferdinand Soethe
Re: About unknow libraries within lib/core
Ross Gardler wrote: Juan Jose Pablos wrote: For the standard distribution, you need only those libraries that are neede, if you want to custom forrest for other purposed, then cp $COCOON_HOME/lib/optional/castor*.jar $FORREST_HOME/lib/core is not a bit problem ¿right? I'm -1 on that method of extension, we should allow projects to have a lib directory. Extension jars go in there under the users control. That was just an example. customatize per-installation or per project is up to the sysadmin on that box... The point is that both are allow Cheers, Cheche
[JIRA] Commented: (FOR-500) ensure that all supporting libraries have a corresponding license
The following comment has been added to this issue: Author: Juan Jose Pablos Created: Wed, 18 May 2005 5:41 PM Body: I have added a few, but I am not able to find these ones: commons-jci-r159148.jar excalibur-pool-api-2.0.0.jar excalibur-pool-impl-2.0.0.jar excalibur-pool-instrumented-2.0.0.jar and I am not sure about this: oreilly.codepolicy.txt oreilly.permission.txt w3c-dtd-license.txt - View this comment: http://issues.cocoondev.org//browse/FOR-500?page=comments#action_12407 - View the issue: http://issues.cocoondev.org//browse/FOR-500 Here is an overview of the issue: - Key: FOR-500 Summary: ensure that all supporting libraries have a corresponding license Type: Task Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 17 May 2005 7:25 PM Updated: Wed, 18 May 2005 5:41 PM Description: Some old libraries and some of the recently updated libraries do not have an updated license file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-336) Table alignment problem with pelt and IE
The following comment has been added to this issue: Author: Addison Berry Created: Wed, 18 May 2005 7:37 PM Body: It looks like it has to do with the table being 100% (#content table in basics.css). I switched it to 99% to see and that eleiminates the problem of dropping it below the menu, but then, of course the table is only 99%. I'm sure it is IE being stupid and I'm sure there is a fix out there. I'll see if I can track down the IE hack to correct this. - View this comment: http://issues.cocoondev.org//browse/FOR-336?page=comments#action_12408 - View the issue: http://issues.cocoondev.org//browse/FOR-336 Here is an overview of the issue: - Key: FOR-336 Summary: Table alignment problem with pelt and IE Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.6 0.7-dev Assignee: Reporter: Stefano Mancarella Created: Wed, 27 Oct 2004 8:51 AM Updated: Wed, 18 May 2005 7:37 PM Environment: Forrest 0.6 Internet Explorer 6.0 Description: There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE. If a page contains a table, the table itself always starts below the menu in IE. So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself. To reproduce the problem do a forrest seed, add a table to index.xml (just below the body tag) and see the result in IE. The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE. Tested with both 0.6 and trunk. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-336) Table alignment problem with pelt and IE
The following issue has been updated: Updater: Addison Berry (mailto:[EMAIL PROTECTED]) Date: Wed, 18 May 2005 7:40 PM Comment: This is a page with the table set to 99%. Changes: Attachment changed to screenshot-ie99.jpg - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-336?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-336 Here is an overview of the issue: - Key: FOR-336 Summary: Table alignment problem with pelt and IE Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.6 0.7-dev Assignee: Reporter: Stefano Mancarella Created: Wed, 27 Oct 2004 8:51 AM Updated: Wed, 18 May 2005 7:40 PM Environment: Forrest 0.6 Internet Explorer 6.0 Description: There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE. If a page contains a table, the table itself always starts below the menu in IE. So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself. To reproduce the problem do a forrest seed, add a table to index.xml (just below the body tag) and see the result in IE. The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE. Tested with both 0.6 and trunk. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-500) ensure that all supporting libraries have a corresponding license
The following comment has been added to this issue: Author: David Crossley Created: Wed, 18 May 2005 8:21 PM Body: The orielly.* and W3C DTD ones are okay as is (see the mail archives). Found the excalibur pool license at archive.apache.org Found the commons-jci at Jakarta Commons in sandbox. - View this comment: http://issues.cocoondev.org//browse/FOR-500?page=comments#action_12410 - View the issue: http://issues.cocoondev.org//browse/FOR-500 Here is an overview of the issue: - Key: FOR-500 Summary: ensure that all supporting libraries have a corresponding license Type: Task Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 17 May 2005 7:25 PM Updated: Wed, 18 May 2005 8:21 PM Description: Some old libraries and some of the recently updated libraries do not have an updated license file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-336) Table alignment problem with pelt and IE
The following comment has been added to this issue:
Author: Addison Berry
Created: Wed, 18 May 2005 9:24 PM
Body:
Ok, this is simpler and hides from Moz properly.
#content table {
border: 0;
width: 100%;
}
/*Hack to get IE to render the table at 100%*/
* html #content table { margin-left: -3px; }
-
View this comment:
http://issues.cocoondev.org//browse/FOR-336?page=comments#action_12412
-
View the issue:
http://issues.cocoondev.org//browse/FOR-336
Here is an overview of the issue:
-
Key: FOR-336
Summary: Table alignment problem with pelt and IE
Type: Bug
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Skins (general issues)
Versions:
0.6
0.7-dev
Assignee:
Reporter: Stefano Mancarella
Created: Wed, 27 Oct 2004 8:51 AM
Updated: Wed, 18 May 2005 9:24 PM
Environment: Forrest 0.6
Internet Explorer 6.0
Description:
There's a strange (css?) problem using tables with the pelt skin and viewing
the result in IE.
If a page contains a table, the table itself always starts below the menu in IE.
So if the table is among the first elements of the page and the menu is long,
the result is a blank space before the table itself.
To reproduce the problem do a forrest seed, add a table to index.xml (just
below the body tag) and see the result in IE.
The problem doesn't show up in browsers of the Mozilla family, so maybe it's
due to a bug in IE.
Tested with both 0.6 and trunk.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Chaperon jar is required by core (Was: svn commit: r170628)
The chaperon jar is required by the core, so i have moved it back. Please, please move one jar and test, next jar, test. Can anyone see why Chaperon is required in the core? Here is output from doing 'forrest run' without Chaperon. Doing 'forrest' is okay no errors. -- 12:49:39.622 WARN!! Error for /index.html java.lang.NoClassDefFoundError: net/sourceforge/chaperon/process/LexicalProcessor at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:207) at org.mortbay.http.ContextLoader.loadClass(ContextLoader.java:171) at org.apache.cocoon.core.container.ComponentEnvironment.loadClass(ComponentEnvironment.java:59) at org.apache.cocoon.core.container.AbstractComponentHandler.getComponentHandler(AbstractComponentHandler.java:73) at org.apache.cocoon.core.container.CoreServiceManager.getComponentHandler(CoreServiceManager.java:585) at org.apache.cocoon.core.container.CoreServiceManager.addComponent(CoreServiceManager.java:474) at org.apache.cocoon.components.container.CocoonServiceManager.addComponent(CocoonServiceManager.java:58) at org.apache.cocoon.core.container.DefaultServiceSelector.configure(DefaultServiceSelector.java:121) at org.apache.cocoon.components.treeprocessor.sitemap.ComponentsSelector.configure(ComponentsSelector.java:121) at org.apache.avalon.framework.container.ContainerUtil.configure(ContainerUtil.java:240) at org.apache.cocoon.core.container.DefaultServiceSelector$Factory.setupInstance(DefaultServiceSelector.java:212) at org.apache.cocoon.core.container.ComponentFactory.newInstance(ComponentFactory.java:109) at org.apache.cocoon.core.container.ThreadSafeComponentHandler.doInitialize(ThreadSafeComponentHandler.java:52) at org.apache.cocoon.core.container.AbstractComponentHandler.initialize(AbstractComponentHandler.java:265) at org.apache.cocoon.core.container.AbstractComponentHandler.getComponentHandler(AbstractComponentHandler.java:121) at org.apache.cocoon.core.container.CoreServiceManager.getComponentHandler(CoreServiceManager.java:585) at org.apache.cocoon.core.container.CoreServiceManager.addComponent(CoreServiceManager.java:474) at org.apache.cocoon.components.container.CocoonServiceManager.addComponent(CocoonServiceManager.java:58) at org.apache.cocoon.core.container.CoreServiceManager.parseConfiguration(CoreServiceManager.java:637) at org.apache.cocoon.core.container.CoreServiceManager.configure(CoreServiceManager.java:175) at org.apache.cocoon.components.treeprocessor.sitemap.SitemapLanguage.createServiceManager(SitemapLanguage.java:80) at org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:328) at org.apache.cocoon.components.treeprocessor.TreeProcessor.buildConcreteProcessor(TreeProcessor.java:401) at org.apache.cocoon.components.treeprocessor.TreeProcessor.setupConcreteProcessor(TreeProcessor.java:348) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:247) at org.apache.cocoon.Cocoon.process(Cocoon.java:503) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1097) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:354) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1808) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1758) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:790) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807) at
[JIRA] Closed: (FOR-336) Table alignment problem with pelt and IE
Message: The following issue has been closed. Resolver: David Crossley Date: Wed, 18 May 2005 10:06 PM Addison, thanks for your contribution. Your tweak is now added to the trunk (i.e. 0.7-dev). - View the issue: http://issues.cocoondev.org//browse/FOR-336 Here is an overview of the issue: - Key: FOR-336 Summary: Table alignment problem with pelt and IE Type: Bug Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.6 0.7-dev Assignee: Reporter: Stefano Mancarella Created: Wed, 27 Oct 2004 8:51 AM Updated: Wed, 18 May 2005 10:06 PM Environment: Forrest 0.6 Internet Explorer 6.0 Description: There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE. If a page contains a table, the table itself always starts below the menu in IE. So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself. To reproduce the problem do a forrest seed, add a table to index.xml (just below the body tag) and see the result in IE. The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE. Tested with both 0.6 and trunk. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
