[jira] Assigned: (COCOON-2007) cocoon-block-deployer plugin falis to build war file

2007-02-09 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati reassigned COCOON-2007:


Assignee: Giacomo Pati

 cocoon-block-deployer plugin falis to build war file
 

 Key: COCOON-2007
 URL: https://issues.apache.org/jira/browse/COCOON-2007
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
Priority: Critical
 Fix For: 2.2-dev (Current SVN)

 Attachments: deployer-pom.diff


 cocoon-block-deployer plugin can't build war file probably because of version 
 mismatch of dependency in cocoon-block-deployer pom (2.0.1) and root pom 
 pluginManagement (2.0.2).
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Internal error in the plugin manager executing goal 
 'org.apache.maven.plugins:maven-war-plugin:2.0.1:war': Unable to find the 
 mojo 'org.apache.maven.plugins:maven-war-plugin:2.0.1:war' in the plugin 
 'org.apache.maven.plugins:maven-war-plugin'
 Component descriptor cannot be found in the component repository: 
 org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-war-plugin:2.0.1:war.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (COCOON-2007) cocoon-block-deployer plugin falis to build war file

2007-02-09 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati closed COCOON-2007.


Resolution: Fixed

patch applied

 cocoon-block-deployer plugin falis to build war file
 

 Key: COCOON-2007
 URL: https://issues.apache.org/jira/browse/COCOON-2007
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
Priority: Critical
 Fix For: 2.2-dev (Current SVN)

 Attachments: deployer-pom.diff


 cocoon-block-deployer plugin can't build war file probably because of version 
 mismatch of dependency in cocoon-block-deployer pom (2.0.1) and root pom 
 pluginManagement (2.0.2).
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] Internal error in the plugin manager executing goal 
 'org.apache.maven.plugins:maven-war-plugin:2.0.1:war': Unable to find the 
 mojo 'org.apache.maven.plugins:maven-war-plugin:2.0.1:war' in the plugin 
 'org.apache.maven.plugins:maven-war-plugin'
 Component descriptor cannot be found in the component repository: 
 org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-war-plugin:2.0.1:war.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Assigned: (COCOON-2004) cocoon-block-deployer missed renaming of cocoon-block-fw

2007-02-06 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati reassigned COCOON-2004:


Assignee: Giacomo Pati

 cocoon-block-deployer missed renaming of cocoon-block-fw
 

 Key: COCOON-2004
 URL: https://issues.apache.org/jira/browse/COCOON-2004
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
Priority: Critical
 Attachments: web.xml.diff


 cocoon-block-deployer-plugin missed renaming of cocoon-block-fw
 In the used web.xml is still the old class 
 org.apache.cocoon.blocks.DispatcherServlet used which will result in a CNF 
 exception

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Closed: (COCOON-2004) cocoon-block-deployer missed renaming of cocoon-block-fw

2007-02-06 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati closed COCOON-2004.


Resolution: Fixed

patch applied, thanks Felix 

 cocoon-block-deployer missed renaming of cocoon-block-fw
 

 Key: COCOON-2004
 URL: https://issues.apache.org/jira/browse/COCOON-2004
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
Priority: Critical
 Attachments: web.xml.diff


 cocoon-block-deployer-plugin missed renaming of cocoon-block-fw
 In the used web.xml is still the old class 
 org.apache.cocoon.blocks.DispatcherServlet used which will result in a CNF 
 exception

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Assigned: (COCOON-1983) MIssed renaming of log4j.xconf to log4j.xml

2007-01-16 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati reassigned COCOON-1983:


Assignee: Giacomo Pati

 MIssed renaming of log4j.xconf to log4j.xml
 ---

 Key: COCOON-1983
 URL: https://issues.apache.org/jira/browse/COCOON-1983
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
 Fix For: 2.2-dev (Current SVN)

 Attachments: patch.txt


 MIssed renaming of log4j.xconf to log4j.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Closed: (COCOON-1983) MIssed renaming of log4j.xconf to log4j.xml

2007-01-16 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati closed COCOON-1983.


Resolution: Fixed

patch applied

 MIssed renaming of log4j.xconf to log4j.xml
 ---

 Key: COCOON-1983
 URL: https://issues.apache.org/jira/browse/COCOON-1983
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
 Fix For: 2.2-dev (Current SVN)

 Attachments: patch.txt


 MIssed renaming of log4j.xconf to log4j.xml

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Assigned: (COCOON-1982) MIssing backslash in log4j.xml

2007-01-16 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati reassigned COCOON-1982:


Assignee: Giacomo Pati

 MIssing backslash in log4j.xml
 --

 Key: COCOON-1982
 URL: https://issues.apache.org/jira/browse/COCOON-1982
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
Priority: Trivial
 Fix For: 2.2-dev (Current SVN)

 Attachments: patch.txt


 Can't parse chunk: {org.apache.cocoon.work.directory}/cocoon-logs/log4j.log 
 /
 param name=Append value=false /
 layout class=org.apache.log4j.PatternLayout
 param name=ConversionPattern value=%t %-5p %c{2} - %m%n/
 /layout
 /appender
 line 1:35: unexpected char: '/'
 at 
 org.antlr.stringtemplate.language.ActionLexer.nextToken(ActionLexer.java:217)
 at antlr.TokenBuffer.fill(TokenBuffer.java:69)
 at antlr.TokenBuffer.LA(TokenBuffer.java:80)
 at antlr.LLkParser.LA(LLkParser.java:52)
 at 
 org.antlr.stringtemplate.language.ActionParser.templatesExpr(ActionParser.java:182)
 at 
 org.antlr.stringtemplate.language.ActionParser.action(ActionParser.java:117)
 at 
 org.antlr.stringtemplate.StringTemplate.parseAction(StringTemplate.java:845)
 at 
 org.antlr.stringtemplate.language.TemplateParser.action(TemplateParser.java:151)
 at 
 org.antlr.stringtemplate.language.TemplateParser.template(TemplateParser.java:119)
 at 
 org.antlr.stringtemplate.StringTemplate.breakTemplateIntoChunks(StringTemplate.java:821)
 at 
 org.antlr.stringtemplate.StringTemplate.setTemplate(StringTemplate.java:428)
 at 
 org.antlr.stringtemplate.StringTemplate.init(StringTemplate.java:333)
 at 
 org.antlr.stringtemplate.StringTemplate.init(StringTemplate.java:318)
 at 
 org.apache.cocoon.maven.deployer.monolithic.MonolithicCocoonDeployer.writeStringTemplateToFile(MonolithicCocoonDeployer.java:237)
 at 
 org.apache.cocoon.maven.deployer.monolithic.MonolithicCocoonDeployer.deploy(MonolithicCocoonDeployer.java:114)
 at 
 org.apache.cocoon.maven.deployer.AbstractDeployMojo.blockDeploymentMonolithicCocoon(AbstractDeployMojo.java:255)
 at 
 org.apache.cocoon.maven.deployer.DeployExplodedMojo.execute(DeployExplodedMojo.java:66)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Closed: (COCOON-1982) MIssing backslash in log4j.xml

2007-01-16 Thread Giacomo Pati (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Giacomo Pati closed COCOON-1982.


Resolution: Fixed

patch applied

 MIssing backslash in log4j.xml
 --

 Key: COCOON-1982
 URL: https://issues.apache.org/jira/browse/COCOON-1982
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Felix Knecht
 Assigned To: Giacomo Pati
Priority: Trivial
 Fix For: 2.2-dev (Current SVN)

 Attachments: patch.txt


 Can't parse chunk: {org.apache.cocoon.work.directory}/cocoon-logs/log4j.log 
 /
 param name=Append value=false /
 layout class=org.apache.log4j.PatternLayout
 param name=ConversionPattern value=%t %-5p %c{2} - %m%n/
 /layout
 /appender
 line 1:35: unexpected char: '/'
 at 
 org.antlr.stringtemplate.language.ActionLexer.nextToken(ActionLexer.java:217)
 at antlr.TokenBuffer.fill(TokenBuffer.java:69)
 at antlr.TokenBuffer.LA(TokenBuffer.java:80)
 at antlr.LLkParser.LA(LLkParser.java:52)
 at 
 org.antlr.stringtemplate.language.ActionParser.templatesExpr(ActionParser.java:182)
 at 
 org.antlr.stringtemplate.language.ActionParser.action(ActionParser.java:117)
 at 
 org.antlr.stringtemplate.StringTemplate.parseAction(StringTemplate.java:845)
 at 
 org.antlr.stringtemplate.language.TemplateParser.action(TemplateParser.java:151)
 at 
 org.antlr.stringtemplate.language.TemplateParser.template(TemplateParser.java:119)
 at 
 org.antlr.stringtemplate.StringTemplate.breakTemplateIntoChunks(StringTemplate.java:821)
 at 
 org.antlr.stringtemplate.StringTemplate.setTemplate(StringTemplate.java:428)
 at 
 org.antlr.stringtemplate.StringTemplate.init(StringTemplate.java:333)
 at 
 org.antlr.stringtemplate.StringTemplate.init(StringTemplate.java:318)
 at 
 org.apache.cocoon.maven.deployer.monolithic.MonolithicCocoonDeployer.writeStringTemplateToFile(MonolithicCocoonDeployer.java:237)
 at 
 org.apache.cocoon.maven.deployer.monolithic.MonolithicCocoonDeployer.deploy(MonolithicCocoonDeployer.java:114)
 at 
 org.apache.cocoon.maven.deployer.AbstractDeployMojo.blockDeploymentMonolithicCocoon(AbstractDeployMojo.java:255)
 at 
 org.apache.cocoon.maven.deployer.DeployExplodedMojo.execute(DeployExplodedMojo.java:66)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Closed: (COCOON-1689) Cannot save a cform containing a multivalued field with more than 9 values !

2005-11-23 Thread Giacomo Pati (JIRA)
 [ http://issues.apache.org/jira/browse/COCOON-1689?page=all ]
 
Giacomo Pati closed COCOON-1689:


Resolution: Fixed

 Cannot save a cform containing a multivalued field with more than 9 values !
 

  Key: COCOON-1689
  URL: http://issues.apache.org/jira/browse/COCOON-1689
  Project: Cocoon
 Type: Bug
   Components: Blocks: Forms
 Versions: 2.1.8, 2.2-dev (Current SVN), 2.1.9-dev (current SVN)
 Reporter: Philippe Gassmann
 Priority: Minor


 An UnsupportedOperationException occurs when trying to save a form containing 
 a multivalued field with more that 9 values. Here is the explanation : 
 here is the incriminated code in MultiValueJXPathBinding.java:doSave(): 
 Iterator rowPointers = multiValueContext.iteratePointers(this.rowPath);
 List l = new ArrayList();
 while( rowPointers.hasNext() )
 {
 Pointer p = (Pointer)rowPointers.next();
 l.add(p.asPath());
 }
 Collections.sort(l);
 for( int i = l.size()-1; i = 0; i-- )
 {
 multiValueContext.removePath((String)l.get(i));
 }
 This code is wrong : 
 The p.asPath returns something like /doc/node[x] 
 if the iterator contains more than 9 values x will be written in TWO 
 characters so, the result of Collections.sort(l) return for 10 values : 
 /doc/node[10]
 /doc/node[1]
 /doc/node[2]
 /doc/node[3]
 /doc/node[4]
 /doc/node[5]
 /doc/node[6]
 /doc/node[7]
 /doc/node[8]
 /doc/node[9]
 so the first node to be deleted is 9. the last is 10. but when trying to 
 delete the 10th node it does not exist anymore !
 A UnsupportedOperationException is thrown.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira