[JIRA] Commented: (FOR-489) initial run of forrest from dist fails
The following comment has been added to this issue: Author: David Crossley Created: Thu, 5 May 2005 1:17 AM Body: It is important that this issue gets solved. You will get other problems if you don't use Forrest's packaged Ant. This sounds like the same type of issue that was fixed by http://issues.cocoondev.org/browse/FOR-471 David, please try the change that was suggested there. - View this comment: http://issues.cocoondev.org//browse/FOR-489?page=comments#action_12352 - View the issue: http://issues.cocoondev.org//browse/FOR-489 Here is an overview of the issue: - Key: FOR-489 Summary: initial run of forrest from dist fails Type: Bug Status: Unassigned Priority: Critical Project: Forrest Components: Launch 'forrest' Versions: 0.6 Assignee: Reporter: David Jung Created: Fri, 29 Apr 2005 11:32 AM Updated: Thu, 5 May 2005 1:17 AM Environment: Redhat Fedora Core 3, Sun JDK 1.5.0-b64 Description: Initial run of forrest per install instructions failed (first time user). Downloaded and untarred 0.6 dist. set env var FORREST_HOME in bash added FORREST_HOME/bin to path. cd'd into top-level and entered 'forrest' on cmd line Result was this: Apache Forrest. Run 'forrest -projecthelp' to list options /usr/bin/build-classpath: error: could not find ant-launcher Java extension for this JVM /usr/bin/build-classpath: error: All specified jars were not found I downloaded and tried an Apr28 snapshot with similar results. (it complained it needed to be built first. Running the build script gave the same error as above) - 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
Re: svn commit: r167890 - /forrest/trunk/site-author/content/xdocs/docs/faq.xml
Ferdinand Soethe wrote: > Ross Gardler wrote: > > RG> This only affects sites when generated from the command line interface > RG> (i.e. not when doing 'forrest run' or running as a webapp). To change it > RG> in non command line you need to override the sitemap redirects. > > RG> I haven't read all your changes in detail, but it looks like you > RG> improved a fair number of the FAQ entries. Cool! > > Thanks. I added that. > > Btw: Changing cli.xconf is now done in the programm directory thus > applying to all Forrests while the sitemap pattern is added > locally. > > Since there probably is a way, can anybody tell me where or how > to make that change to cli.xconf local to a project as well? Each project can have its own cli.xconf http://forrest.apache.org/0.7/docs/faq.html#cli-xconf --David
Re: Reverting changes
Nice info. :) salu2 On Tue, 2005-05-03 at 23:29 +0100, Ross Gardler wrote: > Recently I asked how I should revert a change in SVN, but no-one here > was sure how to do it smoothly. I promised to ask on a more appropriate > list, however, this recently appeared on the cocoon dev list: > > Antonio Gallardo wrote: > > > Hi: > > > > I want revert changes in src/java/org/apache/cocoon/util/NetUtils.java > > from HEAD to 53864. > > > > How to do this? > > > svn merge -r HEAD:53864 src/java/org/apache/cocoon/util/NetUtils.java > src/java/org/apache/cocoon/util/NetUtils.java > > > Vadim > > Also useful (from the same thread): > > http://svnbook.red-bean.com/en/1.0/ch04s04.html#svn-ch-4-sect-4.2 > > (although Antonio mentions that the docs are a little unclear) > > so now we have our answer ;-) > > Ross -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: To change or not to changing threads ( Re: Comment on index.html (Re: Where to change comments to configuration files))
Nicola Ken Barozzi wrote: Ferdinand Soethe wrote: ... Believe me, as I have already suffered consequences from my bad habit of sending quick mails ;-) Absolutely, we have all been there (and I still go there unfortunately). One of my blog entries describes how I *try* and manage the horrible flourish of email that Open Source often brings. http://www.jroller.com/page/rgardler/20050328#ten_tips_for_increasing_your (its more than 10 now - if you have any favourite tips I'd love to hear them) Ross
Re: [HEADSUP] viewHelper is now viewHelper.xhtml
On Tue, 2005-05-03 at 10:25 -0700, Diwaker Gupta wrote:
> Hi Thorsten,
>
> What are the main differences between this and the earlier implementations?
>
Actually there is no big difference besides the naming.
The earlier implementation was only xhtml focused, now I just clarified
that with the new naming convention.
I still need to clean up some code that got redundant (multiple format
in a contract definition) with the move but I hope that is now the final
name for the xhtml contracts and the user will not note the changes
under the hood.
The naming convention for new formats is now ...viewHelper.{format}
This way it will become easy to implement new format without the need to
modify the viewHelper.
In the future we will use as well another naming convention for the dir
structure in projects. Right now all project contracts have to be
in .../templates/{contract}.ft but this will change
to .../templates/{format}/{contract}.ft
Sorry for answering so late but I just started in a new company and
still have to install/setup my workspace.
salu2
> Thanks,
> Diwaker
>
> On 5/3/05, Thorsten Scherler <[EMAIL PROTECTED]> wrote:
> > Hello devs,
> >
> > I am implementing another format for the viewHelper. That forced me to
> > rename the current implementation to viewHelper.xhtml.
> >
> > *You have to* rename the forrest.properties of your projects that are
> > using the view/viewHelper!!!
> >
> > BTW we need to discuss the contracts that we have right now. For now it
> > is possible to implement more then one format within a contract, but IMO
> > that do not make much sense. I recommend that a contract is implementing
> > just 1 format.
> >
> > WDYT?
> >
> > salu2
> > --
> > thorsten
> >
> > "Together we stand, divided we fall!"
> > Hey you (Pink Floyd)
> >
> >
>
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: To change or not to changing threads ( Re: Comment on index.html (Re: Where to change comments to configuration files))
Ferdinand Soethe wrote: ... My problem is not different threads but the temptation of sending instant replies. I just needed to take the time, read all new stuff and then respond to avoid this. Instant replies also tend to lower the signal2noise ratio, can create tensions in case of important discussions, make it easy to mistakenly send a private letter to public, and make mails less polished and difficult to understand. As a general case, waiting some time will always help, and also ease the personal tension. Updating mail once a day or at most hourly also helps. Believe me, as I have already suffered consequences from my bad habit of sending quick mails ;-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
[Fwd: Re: SISSL compatible with ASL?]
The legal-discuss list came up with the attached, summary is that the MSOffice plugin will have to be hosted elsewhere. I'll put it in the Burrokeet CVS. Any Forest committer requiring CVS access over there need only ask for it. Ross Original Message Date: Tue, 3 May 2005 16:17:07 -0700 (PDT) From: Brian Behlendorf <[EMAIL PROTECTED]> To: Ross Gardler <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: Re: SISSL compatible with ASL? The ASL-licensed works can be combined with SISSL-licensed works without the license on one part encumbering the license on the other. However SISSL-licensed works can not be sublicensed under the ASL, which means you can not incorporate the SISSL licensed works into a work that as a whole is licensed under the ASL. Which means the SISSL works must be kept out of CVS/SVN and treated like an external dependency. As best I can tell. Brian On Tue, 3 May 2005, Ross Gardler wrote: Over at Apache Forrest we have a plugin that needs to include the API libs from OpenOffice.org (no source code). However, we are unsure if the Sun Industry Standards Source License (SISSL) is compatible with the ASL. OOo is Tri licensed under the GPL, LGPL (obviously, not compatible) and the Sun Industry Standards Source License (SISSL), so we are considering the SISSL. The FAQ at http://www.openoffice.org/FAQs/faq-licensing.html#1 seems to imply that it should be compatible: "This licensing structure provides the necessary flexibility for combination of OpenOffice.org technologies with projects using other licenses (e.g. MPL, Apache, Artistic, etc.)." However, being no legal experts we have no idea if this objective is realised. Can someone with a little more understanding of these things pass verdict? The SISSL license can be seen at http://www.openoffice.org/license.html Thanks, Ross - DISCLAIMER: Discussions on this list are informational and educational only, are not privileged and do not constitute legal advice. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r167890 - /forrest/trunk/site-author/content/xdocs/docs/faq.xml
Ross Gardler wrote: RG> This only affects sites when generated from the command line interface RG> (i.e. not when doing 'forrest run' or running as a webapp). To change it RG> in non command line you need to override the sitemap redirects. RG> I haven't read all your changes in detail, but it looks like you RG> improved a fair number of the FAQ entries. Cool! Thanks. I added that. Btw: Changing cli.xconf is now done in the programm directory thus applying to all Forrests while the sitemap pattern is added locally. Since there probably is a way, can anybody tell me where or how to make that change to cli.xconf local to a project as well? -- Ferdinand Soethe
[EMAIL PROTECTED]: Project forrest-forrestbar (in module forrest) failed
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-forrestbar has an issue affecting its community integration. This issue affects 1 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - forrest-forrestbar : Apache Forrest is an XML standards-oriented documentation fr... Full details are available at: http://brutus.apache.org/gump/public/forrest/forrest-forrestbar/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -DEBUG- Extracted fallback artifacts from Gump Repository The following work was performed: http://brutus.apache.org/gump/public/forrest/forrest-forrestbar/gump_work/build_forrest_forrest-forrestbar.html Work Name: build_forrest_forrest-forrestbar (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/home/gump/workspaces2/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dversion=04052005 forrestbar [Working Directory: /usr/local/gump/public/workspace/forrest/tools/forrestbar] CLASSPATH: /opt/jdk1.4/lib/tools.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-swing.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar - Buildfile: build.xml BUILD FAILED java.lang.NoClassDefFoundError: org/xml/sax/ext/Attributes2 at org.apache.xerces.parsers.AbstractSAXParser.(Unknown Source) at org.apache.xerces.parsers.SAXParser.(Unknown Source) at org.apache.xerces.parsers.SAXParser.(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.(Unknown Source) at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source) at org.apache.tools.ant.util.JAXPUtils.newSAXParser(JAXPUtils.java:212) at org.apache.tools.ant.util.JAXPUtils.getNamespaceXMLReader(JAXPUtils.java:169) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:187) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:140) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:90) at org.apache.tools.ant.Main.runBuild(Main.java:653) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:150) at org.apache.tools.ant.Main.main(Main.java:240) Total time: 0 seconds java.lang.NoClassDefFoundError: org/xml/sax/ext/Attributes2 at org.apache.xerces.parsers.AbstractSAXParser.(Unknown Source) at org.apache.xerces.parsers.SAXParser.(Unknown Source) at org.apache.xerces.parsers.SAXParser.(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl.(Unknown Source) at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source) at org.apache.tools.ant.util.JAXPUtils.newSAXParser(JAXPUtils.java:212) at org.apache.tools.ant.util.JAXPUtils.getNamespaceXMLReader(JAXPUtils.java:169) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:187) at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:140) at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:90) at org.apache.tools.ant.Main.runBuild(Main.java:653) at org.apache.tools.ant.Main.startAnt(Main.java:187) at org.apache.tools.ant.Main.start(Main.java:150) at org.apache.tools.ant.Main.main(Main.java:240) org/xml/sax/ext/Attributes2 - To subscribe to this information via syndicated feeds: - RSS: http://brutus.apache.org/gump/public/forrest/forrest-forrestbar/rss.xml - Atom: http://brutus.apache.org/gump/public/forrest/forrest-forrestbar/atom.xml == Gump Tracking Only === Produced by Gump version 2.2. Gump Run 3104052005, brutus:brutus-public:3104052005 Gump E-mail Identifier (unique within run) #29. -- Apache Gump http://gump.apache.org/ [Instance: brutus]
To change or not to changing threads ( Re: Comment on index.html (Re: Where to change comments to configuration files))
In 'Re: Comment on index.html (Re: Where to change comments to configuration files)' Ross Gardler wrote: FS> Sorry, I shouldn't respond to messages one by one. That way I missed FS> your solution in 'Re: Inkonsistency in implementation of default file FS> and site.xml and what to do about it' when I wrote my reply. RG> One of the reasons for keeping everything in one thread. This particular RG> issue spanned three different threads because of subject changes. It's RG> sometimes very difficult to know when to change the subject. I always RG> try not too unless I have totally changed the direction the thread is RG> taking. I've started to move discussions to a new thread as soon as the topic changes significantly. The main reason being that in searching the archives I have often come across lng threads that touched the subject I was looking for once and then discussed something else for the next 100 messages. And since you can't be sure you have to read carefully through all of them. I also like the fact that I can clearly see that a threat is moving on to something else (perhaps something I'm not interested in) so that I don't need to follow this new thread. At least that's the theorie. My problem is not different threads but the temptation of sending instant replies. I just needed to take the time, read all new stuff and then respond to avoid this. -- Ferdinand Soethe
[JIRA] Created: (FOR-491) Dead link in http://forrest.apache.org/0.7/docs/index.html
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-491 Here is an overview of the issue: - Key: FOR-491 Summary: Dead link in http://forrest.apache.org/0.7/docs/index.html Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Assignee: Reporter: Ferdinand Soethe Created: Wed, 4 May 2005 2:13 AM Updated: Wed, 4 May 2005 2:13 AM Description: Link http://forrest.apache.org/0.8/ in (menu documentation other versions - 0.8) http://forrest.apache.org/0.7/docs/index.html is currently dead. - 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
