[GitHub] [cocoon] tcurdt commented on pull request #36: Update xsp block to java 8 and fix minor bugs

tcurdt commented on PR #36: URL: https://github.com/apache/cocoon/pull/36#issuecomment-1328134580 Looking good to me. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To uns

[jira] [Closed] (COCOON-2366) XSP block doesn't compile with Java 8

[ https://issues.apache.org/jira/browse/COCOON-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel closed COCOON-2366. Resolution: Fixed > XSP block doesn't compile wit

[jira] [Assigned] (COCOON-2366) XSP block doesn't compile with Java 8

[ https://issues.apache.org/jira/browse/COCOON-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alfred Nathaniel reassigned COCOON-2366: Assignee: Alfred Nathaniel > XSP block doesn't compile wit

[jira] [Created] (COCOON-2366) XSP block doesn't compile with Java 8

Alfred Nathaniel created COCOON-2366: Summary: XSP block doesn't compile with Java 8 Key: COCOON-2366 URL: https://issues.apache.org/jira/browse/COCOON-2366 Project: Cocoon Issue

[jira] [Commented] (COCOON-2366) XSP block doesn't compile with Java 8

izza compilers as options is rather nostalgic. The Eclipse JDT compiler included in the standard Cocoon distribution is quite sufficient. > XSP block doesn't compile with Java 8 > - > > Key: COCOON-2366 >

[jira] [Commented] (COCOON-2366) XSP block doesn't compile with Java 8

http://svn.apache.org/viewvc?view=revision&revision=1853873 > XSP block doesn't compile with Java 8 > - > > Key: COCOON-2366 > URL: https://issues.apache.org/jira/browse/COCOON-2366 > Projec

Re: XSP block

how do you know when it is safe to free the memory? 3. XSP is really old technique and is not maintained by anyone (again officially, at dev/commits list). I'm not the one willing to take costs of XSP maintenance in C2.2 therefore I'll probably vote -1 for any actions leading to releas

Re: XSP block

x27;m not the one willing to take costs of XSP maintenance in C2.2 therefore I'll probably vote -1 for any actions leading to release of XSP block for C2.2. This is my first such a strong voice in this case but I firmly believe it's a high time have a concrete opinion. XSP is

XSP block (was: Type 'serverpages' does not exist for 'map:generate')

o take costs of XSP maintenance in C2.2 therefore I'll probably vote -1 for any actions leading to release of XSP block for C2.2. This is my first such a strong voice in this case but I firmly believe it's a high time have a concrete opinion. XSP is a really mature technology which har

Re: XSP block dependencies

On 07.02.2008 11:11, Alfred Nathaniel wrote: I now added exclusion rules to all our explicit dependencies which pick up the old avalon-framework through transitive dependencies. Thanks very much, Alfred. That's really appreciated! Joerg

Re: XSP block dependencies

On Mon, 2007-11-26 at 08:45 +0100, Reinhard Poetz wrote: > The problem is that the groupId of the Avalon framework changed and that's > the > root of all evil in this case. We ever never need a dependency on Avalon > 4.1.3 > but how to express this in the managedDependencies section? > > The o

Re: XSP block dependencies

Joerg Heinicke pisze: > On 25.11.2007 10:45 Uhr, Grzegorz Kossakowski wrote: > > >> Just check file target/site/dependencies.html. You will find >> everything (or even more) you need there. > > Oh man, I have not even had the idea of looking into an output > directory, I just expected it on the

Re: XSP block dependencies

Can you point me at the poms I should look at to see this? Reinhard Poetz wrote: Ralph Goers wrote: Is the cocoon build really trying to rely on transitive dependency verions? Very bad idea. Versions of every dependency cocoon uses directly or indirectly should be specified in the managedDepen

Re: XSP block dependencies

Ralph Goers wrote: Is the cocoon build really trying to rely on transitive dependency verions? Very bad idea. Versions of every dependency cocoon uses directly or indirectly should be specified in the managedDependencies. The problem is that the groupId of the Avalon framework changed and that

Re: XSP block dependencies

Is the cocoon build really trying to rely on transitive dependency verions? Very bad idea. Versions of every dependency cocoon uses directly or indirectly should be specified in the managedDependencies. Joerg Heinicke wrote: Found this thread on the user list which has the same symptoms: http

Re: XSP block dependencies

On 25.11.2007 23:47 Uhr, Joerg Heinicke wrote: PS: There is also an error somewhere with the dependencies I think. XSP block includes Avalon Framework 4.1.3 instead of 4.3.1 which causes bunch of problems in Eclipse. How to trace the dependencies? Grek sent once a mail with "mvn project

XSP block dependencies (was: servlet service samples)

On 25.11.2007 10:45 Uhr, Grzegorz Kossakowski wrote: PS: There is also an error somewhere with the dependencies I think. XSP block includes Avalon Framework 4.1.3 instead of 4.3.1 which causes bunch of problems in Eclipse. How to trace the dependencies? Grek sent once a mail with "mvn pr

[continuum] BUILD SUCCESSFUL: xsp Block Implementation

27;. [INFO] [INFO] Building xsp Block Implementation [INFO]task-segment: [clean, source:jar, deploy] [INFO] [INFO] [clean:clean] [INFO] Deleting directory /home/maven/continuum-1.0.3/apps/continuum/working-directory/

Re: [continuum] BUILD FAILURE: xsp Block Implementation

On 7/20/06 10:40 AM, in article [EMAIL PROTECTED], "Sylvain Wallez" <[EMAIL PROTECTED]> wrote: >> [INFO] Compilation failure >> >> /home/maven/continuum-1.0.3/apps/continuum/working-directory/167/src/main/jav >> a/org/apache/cocoon/components/language/generator/ProgramGeneratorImpl.java:[ >> 1

[continuum] BUILD FAILURE: xsp Block Implementation

: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'source'. [INFO] [INFO] Building xsp Block Implementa

[continuum] BUILD FAILURE: xsp Block Implementation

: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'source'. [INFO] [INFO] Building xsp Block Implementa

Re: [continuum] BUILD FAILURE: xsp Block Implementation

on-xsp-impl/pom.xml > /cocoon/trunk/core/cocoon-core/pom.xml > > > Output: > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'source'. > [INFO]

[continuum] BUILD FAILURE: xsp Block Implementation

: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'source'. [INFO] [INFO] Building xsp Block Implementation [INFO]task-segment: [clean, source:jar, dep

[continuum] BUILD ERROR: xsp Block Samples

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/153/buildId/947 Build statistics: State: Error Previous State: Ok Started at: Thu, 11 May 2006 01:26:58 + Finished at: Thu, 11 May 2006 01:27:00 + Total ti

[continuum] BUILD ERROR: xsp Block Implementation

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/152/buildId/913 Build statistics: State: Error Previous State: Ok Started at: Thu, 11 May 2006 01:25:58 + Finished at: Thu, 11 May 2006 01:26:01 + Total ti

[continuum] BUILD ERROR: xsp Block

Online report : http://cocoon.zones.apache.org:12000/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/151/buildId/912 Build statistics: State: Error Previous State: Ok Started at: Thu, 11 May 2006 01:25:51 + Finished at: Thu, 11 May 2006 01:25:58 + Total ti

[jira] Updated: (COCOON-1458) jython jar not added to war in XSP block on build

/python/hello generates the folloing error: Resource not found org/python/core/PyObject org.apache.cocoon.ResourceNotFoundException: org/python/core/PyObject cause: org.apache.cocoon.ResourceNotFoundException: org/python/core/PyObject Copying jython-2.1.jar into $TOMCAT_H

Re: trunk doesn't work without xsp block

Max Pfingsthorn hippo.nl> writes: > I've build the trunk with all blocks disabled but forms, template and ajax. > When I do "cocoon servlet" now, it gives a FileNotFoundException I had the same issue on Friday. A simple build clean fixed it for me. Jörg

trunk doesn't work without xsp block

Hi! I've build the trunk with all blocks disabled but forms, template and ajax. When I do "cocoon servlet" now, it gives a FileNotFoundException for C:\Projects\svn\cocoon-2.2-present\build\webapp\WEB-INF\xconf\cocoon-xsp.xconf which is referenced by C:\Projects\svn\cocoon-2.2-present\build\weba

Move ClassLoaderManager to XSP block

Does someone care if I would move the ClassLoaderManager to the XSP block? This component is only used there and is imho not needed by any other block, so I think it makes sense to move it. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco

DO NOT REPLY [Bug 33763] - jython jar not added to war in XSP block on build

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33763] - jython jar not added to war in XSP block on build

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 33763] New: - jython jar not added to war in XSP block on build

gzilla/show_bug.cgi?id=33763 Summary: jython jar not added to war in XSP block on build Product: Cocoon 2 Version: Current SVN 2.1 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Com

Re: XSP block status

. Perhaps someone with more knowledge about this class could take a look and see if they can solve this? - Source samples. Some use xsp's. Move these to xsp block or remove them altogether? I'm in favour of removing them. But I can't decide that. Me too. I don't th

Re: XSP block status

more knowledge about this class could take a look and see if they can solve this? - Source samples. Some use xsp's. Move these to xsp block or remove them altogether? I'm in favour of removing them. But I can't decide that. Me too. I don't think there remains an appro

Re: XSP block status

On Mar 11, 2004, at 8:35 PM, Reinhard Pötz wrote: leo leonid wrote: On Mar 11, 2004, at 6:50 PM, Reinhard Pötz wrote: leo leonid wrote: Hi, I just updated my projects from woody to cocoon forms (absolutely painless, BTW). How did you do the upgrade? I used your ant task ($COCOON_HOME/build

Re: XSP block status

leo leonid wrote: On Mar 11, 2004, at 6:50 PM, Reinhard Pötz wrote: leo leonid wrote: Hi, I just updated my projects from woody to cocoon forms (absolutely painless, BTW). How did you do the upgrade? I used your ant task ($COCOON_HOME/build.sh woody2CocoonForms-renaming). It did the job qu

Re: XSP block status

On Mar 11, 2004, at 6:50 PM, Reinhard Pötz wrote: leo leonid wrote: Hi, I just updated my projects from woody to cocoon forms (absolutely painless, BTW). How did you do the upgrade? I used your ant task ($COCOON_HOME/build.sh woody2CocoonForms-renaming). It did the job quite perfectly. Only

Re: XSP block status

knowledge about this class could > take a look and see if they can solve this? > > - Source samples. Some use xsp's. Move these to xsp block or remove them > altogether? I'm in favour of removing them. But I can't decide that. > - I18n samples. Needs voluntee

Re: XSP block status

Am Do, den 11.03.2004 schrieb leo leonid um 18:24: > Hi, > > I just updated my projects from woody to cocoon forms (absolutely > painless, BTW). I see it similar, a simple s/woody/forms/g, and most of the work is done. I doesn't see a real need to keep the woody block, but anyway... > Unfortun

Re: XSP block status

leo leonid wrote: Hi, I just updated my projects from woody to cocoon forms (absolutely painless, BTW). How did you do the upgrade? -- Reinhard

Re: XSP block status

unfortunate and maybe unnecessary. Perhaps someone with more knowledge about this class could take a look and see if they can solve this? - Source samples. Some use xsp's. Move these to xsp block or remove them altogether? - I18n samples. Needs volunteer. - simpleform samples. Needs volu

XSP block status

? - Source samples. Some use xsp's. Move these to xsp block or remove them altogether? - I18n samples. Needs volunteer. - simpleform samples. Needs volunteer. - session-fw patches are executed before xsp patches but depend on them. Move xsp specific stuff from session-fw to xsp. - some b