[jira] [Commented] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050267#comment-15050267 ] Andy Jefferson commented on SUREFIRE-1042: -- It isn't about any parameter "being buggy". It's about changes introduced after 2.10 that weren't backwards compatible (in a minor release!), and no apparent consideration being made for people who want what it previously did. > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN >Assignee: Tibor Digana > Attachments: test.zip > > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048201#comment-15048201 ] Andy Jefferson commented on SUREFIRE-1042: -- [~tibor17] Well that removes the stack trace BUT also removes the test by test listing. For example, when I have 2 test classes I get the following with v2.10 --- T E S T S --- Running mydomain.test.Simple2Test Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec Running mydomain.test.SimpleTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! Results : Failed tests: testSimple(mydomain.test.SimpleTest): Failed test : is failed for some reason or other Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 but with this config and 2.16+ I get --- T E S T S --- Failed tests: SimpleTest.testSimple:14 Failed test : is failed for some reason or other Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 So no, that is not acceptable really. It loses too much info that is seen as the tests run > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN >Assignee: Tibor Digana > Attachments: test.zip > > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045150#comment-15045150 ] Andy Jefferson edited comment on SUREFIRE-1042 at 12/7/15 4:13 PM: --- Not sure why a "test" is required for such basic behaviour but anyway. The attached simple maven project has a single Java class to compile, and single test (which simply calls JUnit fail to simulate a failing test). The console output is Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec <<< FAILURE! - in mydomain.test.SimpleTest testSimple(mydomain.test.SimpleTest) Time elapsed: 0.003 sec <<< FAILURE! java.lang.AssertionError: Failed test : is failed for some reason or other at org.junit.Assert.fail(Assert.java:93) at mydomain.test.SimpleTest.testSimple(SimpleTest.java:14) Results : Failed tests: SimpleTest.testSimple:14 Failed test : is failed for some reason or other THIS IS REGARDLESS OF USE (or not) OF -Dmaven.test.redirectTestOutputToFile=true Perhaps now some way can be provided to get old behaviour? Thanks! For the record, the output to the console that you would get running the same with v2.10 of surefire plugin is Running mydomain.test.SimpleTest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec <<< FAILURE! Results : Failed tests: testSimple(mydomain.test.SimpleTest): Failed test : is failed for some reason or other No stacktraces, just clean output that people can then drill down into the failures as they wish was (Author: andy): Not sure why a "test" is required for such basic behaviour but anyway. The attached simple maven project has a single Java class to compile, and single test (which simply calls JUnit fail to simulate a failing test). The console output is Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec <<< FAILURE! - in mydomain.test.SimpleTest testSimple(mydomain.test.SimpleTest) Time elapsed: 0.003 sec <<< FAILURE! java.lang.AssertionError: Failed test : is failed for some reason or other at org.junit.Assert.fail(Assert.java:93) at mydomain.test.SimpleTest.testSimple(SimpleTest.java:14) Results : Failed tests: SimpleTest.testSimple:14 Failed test : is failed for some reason or other THIS IS REGARDLESS OF USE (or not) OF -Dmaven.test.redirectTestOutputToFile=true Perhaps now some way can be provided to get old behaviour? Thanks! > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN > Attachments: test.zip > > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Jefferson updated SUREFIRE-1042: - Attachment: test.zip Not sure why a "test" is required for such basic behaviour but anyway. The attached simple maven project has a single Java class to compile, and single test (which simply calls JUnit fail to simulate a failing test). The console output is Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec <<< FAILURE! - in mydomain.test.SimpleTest testSimple(mydomain.test.SimpleTest) Time elapsed: 0.003 sec <<< FAILURE! java.lang.AssertionError: Failed test : is failed for some reason or other at org.junit.Assert.fail(Assert.java:93) at mydomain.test.SimpleTest.testSimple(SimpleTest.java:14) Results : Failed tests: SimpleTest.testSimple:14 Failed test : is failed for some reason or other THIS IS REGARDLESS OF USE (or not) OF -Dmaven.test.redirectTestOutputToFile=true Perhaps now some way can be provided to get old behaviour? Thanks! > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN > Attachments: test.zip > > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1042) Provide way of running tests so that stack trace isn't dumped onto console
[ https://issues.apache.org/jira/browse/SUREFIRE-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580453#comment-14580453 ] Andy Jefferson commented on SUREFIRE-1042: -- Yes, no difference > Provide way of running tests so that stack trace isn't dumped onto console > -- > > Key: SUREFIRE-1042 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1042 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.13, 2.14, 2.15, 2.16 > Environment: Maven 3.x, Linux >Reporter: DN > > We never used to get stack traces from any failed tests (asserts) being > dumped onto the console. "Upgrading" to 2.16 means that they now get dumped > onto the console (UGLY IMHO). Can we at least have the option of the previous > output behaviour (2.10 for example)? If there already is a way of achieving > this, please advise, I couldn't find anything that had an effect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] Created: (MDEPLOY-90) Deploy should be allowed in offline mode when the repo is a file:
Deploy should be allowed in offline mode when the repo is a file: - Key: MDEPLOY-90 URL: http://jira.codehaus.org/browse/MDEPLOY-90 Project: Maven 2.x Deploy Plugin Issue Type: Improvement Affects Versions: 2.3 Reporter: Andy Jefferson When the repo being deployed to is on the same machine why should offline mode prohibit operation? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (MPPDF-62) OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1
[ http://jira.codehaus.org/browse/MPPDF-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Jefferson resolved MPPDF-62. - Resolution: Fixed Fix Version/s: 2.5.2 Thx. Problem resolved with TOC at end > OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1 > -- > > Key: MPPDF-62 > URL: http://jira.codehaus.org/browse/MPPDF-62 > Project: Maven 1.x PDF Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Andy Jefferson > Fix For: 2.5.2 > > > The following project > svn co > https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform.datanucleus.org/trunk > datanucleus > when running "maven clean pdf" runs fine when using Maven1.0 and plugin > 2.2.1. Just tried with Maven1.1 and plugin 2.5.1 and it gives > [java] [INFO] [297] > [java] [INFO] [298] > [java] [INFO] [299] > [java] [INFO] [300] > [java] [INFO] [301] > [java] [INFO] [302] > [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap > space > [java] at java.lang.String.(String.java:208) > [java] at java.lang.StringBuilder.toString(StringBuilder.java:431) > [java] at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > [java] at java.lang.Integer.parseInt(Integer.java:447) > [java] at java.lang.Integer.parseInt(Integer.java:497) > [java] at > org.apache.fop.layout.FontInfo.createFontKey(FontInfo.java:130) > [java] at org.apache.fop.layout.FontState.(FontState.java:112) > [java] at > org.apache.fop.fo.PropertyManager.getFontState(PropertyManager.java:117) > [java] at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:292) > [java] at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:360) > [java] at > org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.java:236) > [java] at org.apache.fop.fo.flow.Table.layout(Table.java:302) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) > [java] at > org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) > [java] at > org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) > [java] at > org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) > [java] at > org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) > [java] at > org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > [java] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > [java] at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > [java] at org.apache.fop.apps.Driver.render(Driver.java:498) > It was running through quite quick til it got to 250 or so then slower and > slower. > Obviously will be different on each machine, but I have > setenv MAVEN_OPTS "-Xmx512m -Xms512m" > but have tried also with 1024 for both > Anything I can set to get around this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPPDF-62) OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1
[ http://jira.codehaus.org/browse/MPPDF-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139443#action_139443 ] Andy Jefferson commented on MPPDF-62: - Thx. Tried the 2.5.2-SNAPSHOT with "end" and "none" and there's no OutOfMemoryError now!. However I no longer get the projectLogo/companyLogo displayed. No idea if that is related to what you changed, but with my previous 2.2.1 + "plugin-resources" from 2.5.1 it had no problem displaying the companyLogo. > OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1 > -- > > Key: MPPDF-62 > URL: http://jira.codehaus.org/browse/MPPDF-62 > Project: Maven 1.x PDF Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Andy Jefferson > > The following project > svn co > https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform.datanucleus.org/trunk > datanucleus > when running "maven clean pdf" runs fine when using Maven1.0 and plugin > 2.2.1. Just tried with Maven1.1 and plugin 2.5.1 and it gives > [java] [INFO] [297] > [java] [INFO] [298] > [java] [INFO] [299] > [java] [INFO] [300] > [java] [INFO] [301] > [java] [INFO] [302] > [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap > space > [java] at java.lang.String.(String.java:208) > [java] at java.lang.StringBuilder.toString(StringBuilder.java:431) > [java] at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > [java] at java.lang.Integer.parseInt(Integer.java:447) > [java] at java.lang.Integer.parseInt(Integer.java:497) > [java] at > org.apache.fop.layout.FontInfo.createFontKey(FontInfo.java:130) > [java] at org.apache.fop.layout.FontState.(FontState.java:112) > [java] at > org.apache.fop.fo.PropertyManager.getFontState(PropertyManager.java:117) > [java] at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:292) > [java] at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:360) > [java] at > org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.java:236) > [java] at org.apache.fop.fo.flow.Table.layout(Table.java:302) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) > [java] at > org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) > [java] at > org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) > [java] at > org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) > [java] at > org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) > [java] at > org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > [java] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > [java] at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > [java] at org.apache.fop.apps.Driver.render(Driver.java:498) > It was running through quite quick til it got to 250 or so then slower and > slower. > Obviously will be different on each machine, but I have > setenv MAVEN_OPTS "-Xmx512m -Xms512m" > but have tried also with 1024 for both > Anything I can set to get around this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPPDF-62) OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1
[ http://jira.codehaus.org/browse/MPPDF-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139418#action_139418 ] Andy Jefferson commented on MPPDF-62: - Hi Lukas, thx for investigating it. I have no particular requirement for the TOC. The PDF bookmarks are more important anyway IMHO. But if you could add an option for TOC with options like "start", "end", "none" then you're catering for all tastes. In terms of when you run fop from the command line, aren't you also using Xerces/Xalan/Batik in that process? No idea what has changed in Xerces/Xalan between 2.4 and 2.7/8 so can't help on why that should matter. > OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1 > -- > > Key: MPPDF-62 > URL: http://jira.codehaus.org/browse/MPPDF-62 > Project: Maven 1.x PDF Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Andy Jefferson > > The following project > svn co > https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform.datanucleus.org/trunk > datanucleus > when running "maven clean pdf" runs fine when using Maven1.0 and plugin > 2.2.1. Just tried with Maven1.1 and plugin 2.5.1 and it gives > [java] [INFO] [297] > [java] [INFO] [298] > [java] [INFO] [299] > [java] [INFO] [300] > [java] [INFO] [301] > [java] [INFO] [302] > [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap > space > [java] at java.lang.String.(String.java:208) > [java] at java.lang.StringBuilder.toString(StringBuilder.java:431) > [java] at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > [java] at java.lang.Integer.parseInt(Integer.java:447) > [java] at java.lang.Integer.parseInt(Integer.java:497) > [java] at > org.apache.fop.layout.FontInfo.createFontKey(FontInfo.java:130) > [java] at org.apache.fop.layout.FontState.(FontState.java:112) > [java] at > org.apache.fop.fo.PropertyManager.getFontState(PropertyManager.java:117) > [java] at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:292) > [java] at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:360) > [java] at > org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.java:236) > [java] at org.apache.fop.fo.flow.Table.layout(Table.java:302) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) > [java] at > org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) > [java] at > org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) > [java] at > org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) > [java] at > org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) > [java] at > org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > [java] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > [java] at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > [java] at org.apache.fop.apps.Driver.render(Driver.java:498) > It was running through quite quick til it got to 250 or so then slower and > slower. > Obviously will be different on each machine, but I have > setenv MAVEN_OPTS "-Xmx512m -Xms512m" > but have tried also with 1024 for both > Anything I can set to get around this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPPDF-62) OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1
[ http://jira.codehaus.org/browse/MPPDF-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139245#action_139245 ] Andy Jefferson commented on MPPDF-62: - Taking the "plugin-resources" files from 2.5.1 and putting them into the plugin for 2.2.1 results in a working plugin that seems to have all of the fixes that have gone in since 2.2.1 (contents page not coping with > 10 sections, not including images in same directory, etc) yet doesn't give OOME. Of the other diffs in these plugin versions that I can see 2.2.1 : Fop (0.20.5), Batik=1.5.0, xerces=2.4, xalan=2.4.1 2.5.1 : Fop=0.20.5, Batik=1.5.0-fop-0.20.5, xerces=2.8, xalan=2.7 Any ideas? At least now I can build a custom version of this plugin and have something working, but would be nice to have this done officially and someone in the know can understand why the official latest release gives OutOfMemoryError on significant size PDF generation. > OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1 > -- > > Key: MPPDF-62 > URL: http://jira.codehaus.org/browse/MPPDF-62 > Project: Maven 1.x PDF Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Andy Jefferson > > The following project > svn co > https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform.datanucleus.org/trunk > datanucleus > when running "maven clean pdf" runs fine when using Maven1.0 and plugin > 2.2.1. Just tried with Maven1.1 and plugin 2.5.1 and it gives > [java] [INFO] [297] > [java] [INFO] [298] > [java] [INFO] [299] > [java] [INFO] [300] > [java] [INFO] [301] > [java] [INFO] [302] > [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap > space > [java] at java.lang.String.(String.java:208) > [java] at java.lang.StringBuilder.toString(StringBuilder.java:431) > [java] at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > [java] at java.lang.Integer.parseInt(Integer.java:447) > [java] at java.lang.Integer.parseInt(Integer.java:497) > [java] at > org.apache.fop.layout.FontInfo.createFontKey(FontInfo.java:130) > [java] at org.apache.fop.layout.FontState.(FontState.java:112) > [java] at > org.apache.fop.fo.PropertyManager.getFontState(PropertyManager.java:117) > [java] at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:292) > [java] at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:360) > [java] at > org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.java:236) > [java] at org.apache.fop.fo.flow.Table.layout(Table.java:302) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) > [java] at > org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) > [java] at > org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) > [java] at > org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) > [java] at > org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) > [java] at > org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > [java] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > [java] at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > [java] at org.apache.fop.apps.Driver.render(Driver.java:498) > It was running through quite quick til it got to 250 or so then slower and > slower. > Obviously will be different on each machine, but I have > setenv MAVEN_OPTS "-Xmx512m -Xms512m" > but have tried also with 1024 for both > Anything I can set to get around this ? -- This mes
[jira] Commented: (MPPDF-62) OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1
[ http://jira.codehaus.org/browse/MPPDF-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139212#action_139212 ] Andy Jefferson commented on MPPDF-62: - OOME also occurs using Maven 1.0 and 2.5.1 plugin, concluding that the issue is likely the plugin (and its dependencies) and not the version of Maven. I'm using JDK1.5_12 on Linux btw > OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1 > -- > > Key: MPPDF-62 > URL: http://jira.codehaus.org/browse/MPPDF-62 > Project: Maven 1.x PDF Plugin > Issue Type: Bug >Affects Versions: 2.5.1 >Reporter: Andy Jefferson > > The following project > svn co > https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform.datanucleus.org/trunk > datanucleus > when running "maven clean pdf" runs fine when using Maven1.0 and plugin > 2.2.1. Just tried with Maven1.1 and plugin 2.5.1 and it gives > [java] [INFO] [297] > [java] [INFO] [298] > [java] [INFO] [299] > [java] [INFO] [300] > [java] [INFO] [301] > [java] [INFO] [302] > [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap > space > [java] at java.lang.String.(String.java:208) > [java] at java.lang.StringBuilder.toString(StringBuilder.java:431) > [java] at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > [java] at java.lang.Integer.parseInt(Integer.java:447) > [java] at java.lang.Integer.parseInt(Integer.java:497) > [java] at > org.apache.fop.layout.FontInfo.createFontKey(FontInfo.java:130) > [java] at org.apache.fop.layout.FontState.(FontState.java:112) > [java] at > org.apache.fop.fo.PropertyManager.getFontState(PropertyManager.java:117) > [java] at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:292) > [java] at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:360) > [java] at > org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.java:236) > [java] at org.apache.fop.fo.flow.Table.layout(Table.java:302) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) > [java] at > org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) > [java] at > org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) > [java] at > org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) > [java] at > org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) > [java] at > org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) > [java] at > org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > [java] at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > [java] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown > Source) > [java] at > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > [java] at org.apache.fop.apps.Driver.render(Driver.java:498) > It was running through quite quick til it got to 250 or so then slower and > slower. > Obviously will be different on each machine, but I have > setenv MAVEN_OPTS "-Xmx512m -Xms512m" > but have tried also with 1024 for both > Anything I can set to get around this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPPDF-62) OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1
OutOfMemoryError using Maven 1.1 and v2.5.1 but works with Maven1.0 and v2.2.1 -- Key: MPPDF-62 URL: http://jira.codehaus.org/browse/MPPDF-62 Project: Maven 1.x PDF Plugin Issue Type: Bug Affects Versions: 2.5.1 Reporter: Andy Jefferson The following project svn co https://datanucleus.svn.sourceforge.net/svnroot/datanucleus/documentation/accessplatform.datanucleus.org/trunk datanucleus when running "maven clean pdf" runs fine when using Maven1.0 and plugin 2.2.1. Just tried with Maven1.1 and plugin 2.5.1 and it gives [java] [INFO] [297] [java] [INFO] [298] [java] [INFO] [299] [java] [INFO] [300] [java] [INFO] [301] [java] [INFO] [302] [java] Exception in thread "main" java.lang.OutOfMemoryError: Java heap space [java] at java.lang.String.(String.java:208) [java] at java.lang.StringBuilder.toString(StringBuilder.java:431) [java] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) [java] at java.lang.Integer.parseInt(Integer.java:447) [java] at java.lang.Integer.parseInt(Integer.java:497) [java] at org.apache.fop.layout.FontInfo.createFontKey(FontInfo.java:130) [java] at org.apache.fop.layout.FontState.(FontState.java:112) [java] at org.apache.fop.fo.PropertyManager.getFontState(PropertyManager.java:117) [java] at org.apache.fop.fo.flow.TableCell.layout(TableCell.java:292) [java] at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:360) [java] at org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.java:236) [java] at org.apache.fop.fo.flow.Table.layout(Table.java:302) [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) [java] at org.apache.fop.fo.flow.Block.layout(Block.java:257) [java] at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154) [java] at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110) [java] at org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400) [java] at org.apache.fop.fo.pagination.PageSequence.format(PageSequence.java:338) [java] at org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:262) [java] at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:223) [java] at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) [java] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) [java] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) [java] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) [java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) [java] at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) [java] at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) [java] at org.apache.fop.apps.Driver.render(Driver.java:498) It was running through quite quick til it got to 250 or so then slower and slower. Obviously will be different on each machine, but I have setenv MAVEN_OPTS "-Xmx512m -Xms512m" but have tried also with 1024 for both Anything I can set to get around this ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPTEST-75) Final test failure leads to strange formatted error
[ http://jira.codehaus.org/browse/MPTEST-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101588 ] Andy Jefferson commented on MPTEST-75: -- Thx :-) - last time I tried to find such settings there were no docs (but that was maybe 2 yrs ago). Glad its moving forward, and sorry for the erroneous bug report > Final test failure leads to strange formatted error > --- > > Key: MPTEST-75 > URL: http://jira.codehaus.org/browse/MPTEST-75 > Project: Maven 1.x Test Plugin > Issue Type: Bug >Affects Versions: 1.8.2 >Reporter: Andy Jefferson >Assignee: Lukas Theussl > > When running JUnit tests with Maven 1.1.0 on Linux if the final test fails I > get non-standard output. To attempt to explain better ... > [junit] Running org.jpox.tests.NondurableIdTest > [junit] Tests run: 3, Failures: 2, Errors: 0, Time elapsed: 5.947 sec > [junit] [ERROR] Test org.jpox.tests.NondurableIdTest FAILED > [junit] Running org.jpox.tests.ObjectFCOTest > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.471 sec > [junit] Running org.jpox.tests.PersistenceManagerFactoryImplTest > [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 25.693 sec > [junit] Running org.jpox.tests.PersistenceManagerImplTest > [junit] Tests run: 49, Failures: 1, Errors: 0, Time elapsed: 8.589 sec > [junit] [ERROR] Test org.jpox.tests.PersistenceManagerImplTest FAILED > [junit] Running org.jpox.tests.SequenceTest > [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.072 sec > [junit] Running org.jpox.tests.SerializationTest > [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 3.607 sec > [junit] Running org.jpox.tests.TransactionTest > [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.142 sec > [junit] Running org.jpox.tests.TypeManagerTest > [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.016 sec > [junit] Running org.jpox.tests.TypeStorageTest > [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 11.486 sec > [junit] Running org.jpox.tests.TypesMappingTest > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.016 sec > [junit] Running org.jpox.tests.ViewTest > [junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 2.33 sec > --- > >> Unable to obtain goal [test:test] > >> Test org.jpox.tests.ViewTest failed > --- > BUILD FAILED > So normally when a test fails you get the line [ERROR] but when its the final > test you dont get that and get the ugly "Unable to obtain goal" etc. Why is > it not displaying the final test correctly? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPTEST-75) Final test failure leads to strange formatted error
[ http://jira.codehaus.org/browse/MPTEST-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101543 ] Andy Jefferson commented on MPTEST-75: -- Ahh, ok. So what should I be using to get the same behaviour as Maven 1.0.2 ? (because my settings are the same as I used there). I want it to plough on regardless. > Final test failure leads to strange formatted error > --- > > Key: MPTEST-75 > URL: http://jira.codehaus.org/browse/MPTEST-75 > Project: Maven 1.x Test Plugin > Issue Type: Bug >Affects Versions: 1.8.2 >Reporter: Andy Jefferson > > When running JUnit tests with Maven 1.1.0 on Linux if the final test fails I > get non-standard output. To attempt to explain better ... > [junit] Running org.jpox.tests.NondurableIdTest > [junit] Tests run: 3, Failures: 2, Errors: 0, Time elapsed: 5.947 sec > [junit] [ERROR] Test org.jpox.tests.NondurableIdTest FAILED > [junit] Running org.jpox.tests.ObjectFCOTest > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.471 sec > [junit] Running org.jpox.tests.PersistenceManagerFactoryImplTest > [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 25.693 sec > [junit] Running org.jpox.tests.PersistenceManagerImplTest > [junit] Tests run: 49, Failures: 1, Errors: 0, Time elapsed: 8.589 sec > [junit] [ERROR] Test org.jpox.tests.PersistenceManagerImplTest FAILED > [junit] Running org.jpox.tests.SequenceTest > [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.072 sec > [junit] Running org.jpox.tests.SerializationTest > [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 3.607 sec > [junit] Running org.jpox.tests.TransactionTest > [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.142 sec > [junit] Running org.jpox.tests.TypeManagerTest > [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.016 sec > [junit] Running org.jpox.tests.TypeStorageTest > [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 11.486 sec > [junit] Running org.jpox.tests.TypesMappingTest > [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.016 sec > [junit] Running org.jpox.tests.ViewTest > [junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 2.33 sec > --- > >> Unable to obtain goal [test:test] > >> Test org.jpox.tests.ViewTest failed > --- > BUILD FAILED > So normally when a test fails you get the line [ERROR] but when its the final > test you dont get that and get the ugly "Unable to obtain goal" etc. Why is > it not displaying the final test correctly? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPTEST-75) Final test failure leads to strange formatted error
Final test failure leads to strange formatted error --- Key: MPTEST-75 URL: http://jira.codehaus.org/browse/MPTEST-75 Project: Maven 1.x Test Plugin Issue Type: Bug Affects Versions: 1.8.2 Reporter: Andy Jefferson When running JUnit tests with Maven 1.1.0 on Linux if the final test fails I get non-standard output. To attempt to explain better ... [junit] Running org.jpox.tests.NondurableIdTest [junit] Tests run: 3, Failures: 2, Errors: 0, Time elapsed: 5.947 sec [junit] [ERROR] Test org.jpox.tests.NondurableIdTest FAILED [junit] Running org.jpox.tests.ObjectFCOTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.471 sec [junit] Running org.jpox.tests.PersistenceManagerFactoryImplTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 25.693 sec [junit] Running org.jpox.tests.PersistenceManagerImplTest [junit] Tests run: 49, Failures: 1, Errors: 0, Time elapsed: 8.589 sec [junit] [ERROR] Test org.jpox.tests.PersistenceManagerImplTest FAILED [junit] Running org.jpox.tests.SequenceTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.072 sec [junit] Running org.jpox.tests.SerializationTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 3.607 sec [junit] Running org.jpox.tests.TransactionTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.142 sec [junit] Running org.jpox.tests.TypeManagerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.016 sec [junit] Running org.jpox.tests.TypeStorageTest [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 11.486 sec [junit] Running org.jpox.tests.TypesMappingTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.016 sec [junit] Running org.jpox.tests.ViewTest [junit] Tests run: 5, Failures: 0, Errors: 1, Time elapsed: 2.33 sec --- >> Unable to obtain goal [test:test] >> Test org.jpox.tests.ViewTest failed --- BUILD FAILED So normally when a test fails you get the line [ERROR] but when its the final test you dont get that and get the ugly "Unable to obtain goal" etc. Why is it not displaying the final test correctly? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DOXIA-104) Support use of custom properties in XDOC files
[ http://jira.codehaus.org/browse/DOXIA-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97637 ] Andy Jefferson commented on DOXIA-104: -- Yes, I'm aware that if things are validated against XSDs then that wont validate but it is a perfectly reasonable requirement to be able to specify a page to be in a particular horizontal and vertical navigation position. If there is some other way of providing this then please tell me what it is. If M2/Doxia is never going to support flexible horizontal/vertical navs that we require (in some way), then M2 will never be an option for us since site generation is a key part of any project > Support use of custom properties in XDOC files > -- > > Key: DOXIA-104 > URL: http://jira.codehaus.org/browse/DOXIA-104 > Project: doxia > Issue Type: Task >Affects Versions: 1.0-alpha-8 >Reporter: Andy Jefferson >Priority: Critical > > In the JPOX Maven1 use of "site" we tagged all (XDOC) docs like this > > > Application Identity > Persistence > 1_2 > > ... > > since XDOCs werent validated against any DTD etc. > Then in site.jsl we could access these properties via > > > > With Maven2 I don't see how I can do this. I define my own skin for JPOX and > in site.vm I have $title, $authors but nothing more. Delving into Doxia I see > where they were set up. No allowance for users own properties. > The requirement for JPOX is that we have a large number of documents, and we > tag each doc for particular categories ... which will then appear on the web > site as horizontal navigation (the default Maven skin only has the navColumn > ... vertical navigation). By being able to tag docs into > categories/subcategories etc we can then generate a site that the user > selects a horizontal nav category, and then a horizontal nav sub-category, > and they see vertical navigation within that subcategory. This was possible > with Maven1 due to the above ability. Without an equivalent in Maven2 we > cannot switch over. > The JPOX docs (from Maven1) are available at > http://www.jpox.org/docs/1_2/index.html > so you can understand what is being talked about here. If you need any more > info let me know. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-1241) Schedule fails to start due to derby database column being too small
[ http://jira.codehaus.org/browse/CONTINUUM-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97411 ] Andy Jefferson commented on CONTINUUM-1241: --- The JPOX log defines what SQL is invoked, with what values passed in. You can easily consult your schema for what the table is defined as. So why not post them back here so there is basis for comment? Probably there is some column that only accepts data up to a particular size and maybe Continuum is alowing input to be greater? (guessing) > Schedule fails to start due to derby database column being too small > > > Key: CONTINUUM-1241 > URL: http://jira.codehaus.org/browse/CONTINUUM-1241 > Project: Continuum > Issue Type: Bug > Components: Core system >Affects Versions: 1.0.3 > Environment: Linux >Reporter: Derek Clarkson >Priority: Critical > > When the schedular trys to start a build we get the following error: > INFO | jvm 1| 2007/04/10 10:30:08 | ERROR 22001: A truncation error was > encountered trying to shrink VARCHAR > '/Magrathea/trunk/bizstation-magrathea/customer-core/src/main&' to length 255. > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.error.StandardException.newException(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.SQLChar.hasNonBlankChars(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.SQLVarchar.normalize(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.iapi.types.DataTypeDescriptor.normalize(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.NormalizeResultSet.normalizeRow(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.NormalizeResultSet.getNextRowCore(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.DMLWriteResultSet.getNextRowCore(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.execute.InsertResultSet.open(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.request.Request.executeUpdate(Request.java:78) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:258) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.StoreManager.insert(StoreManager.java:739) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.state.StateManagerImpl.internalMakePersistent(StateManagerImpl.java:3415) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.state.StateManagerImpl.makePersistent(StateManagerImpl.java:3388) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.AbstractPersistenceManager.internalMakePersistent(AbstractPersistenceManager.java:1146) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.AbstractPersistenceManager.makePersistentInternal(AbstractPersistenceManager.java:1187) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.scostore.InverseListStore.validateElementForWriting(InverseListStore.java:1061) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.scostore.InverseListStore.internalAdd(InverseListStore.java:672) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.scostore.AbstractListStore.addAll(AbstractListStore.java:322) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.mapping.CollectionMapping.postInsert(CollectionMapping.java:236) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.request.InsertRequest.execute(InsertRequest.java:396) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.jpox.store.rdbms.table.ClassTable.insert(ClassTable.java:2146) > INFO | jvm 1| 2007/04/10 10:30:08 | at > org.j
[jira] Commented: (CONTINUUM-1181) Continuum aborts when running Postgres under JBoss
[ http://jira.codehaus.org/browse/CONTINUUM-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97410 ] Andy Jefferson commented on CONTINUUM-1181: --- Postgresql supports IIRC lowercase, and mixed case quoted identifiers. The default used by JPOX will be mixed case quoted, but you can easily set that property to "LowerCase". No idea what that has to do with this issue since no JPOX info is provided ... like log entries, exception, stack trace > Continuum aborts when running Postgres under JBoss > -- > > Key: CONTINUUM-1181 > URL: http://jira.codehaus.org/browse/CONTINUUM-1181 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.1-alpha-1 > Environment: MS Windows XP Pro SP2 > postgres 8.1.4-1 with JDBC Driver postgresql-8.1-408.jdbc3 > JBoss 4.0.5.GA >Reporter: thierry lach > Fix For: 1.1-alpha-2 > > > I'm trying to get Continuum to store its data in a postgres database while > running under JBoss and I'm getting an exception. It seems that someone is > trying to change the transaction isolation during a transaction. > Excerpt from JBoss logs follows... > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - Starting Continuum. > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - < Continuum 1.1-SNAPSHOT started! > > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - --- > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -\ ^__^ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > - \ (oo)\___ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -(__)\ )\/\ > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -||w | > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum > -|| || > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO Continuum - > 2007-02-21 12:56:02,613 [ScannerThread] INFO ContinuumInitializer:default > - Continuum initializer running ... > 2007-02-21 12:56:02,644 [ScannerThread] WARN LocalManagedConnectionFactory > - Error resetting transaction isolation > org.postgresql.util.PSQLException: Cannot change transaction isolation level > in the middle of a transaction. > at > org.postgresql.jdbc2.AbstractJdbc2Connection.setTransactionIsolation(AbstractJdbc2Connection.java:733) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.cleanup(BaseWrapperManagedConnection.java:189) > at > org.jboss.resource.connectionmanager.InternalManagedConnectionPool.returnConnection(InternalManagedConnectionPool.java > :320) > at > org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.returnConnection(JBossManagedConnectionPool.java:620) > at > org.jboss.resource.connectionmanager.BaseConnectionManager2.returnManagedConnection > (BaseConnectionManager2.java:363) > at > org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:623) > at > org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle > (BaseWrapperManagedConnection.java:266) > at > org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129) > at > org.jpox.store.rdbms.adapter.DatabaseAdapter.getConnection(DatabaseAdapter.java > :928) > at > org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTransaction.java:324) > at > org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:356) > at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached > (PlexusJdoUtils.java:346) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1302) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached( > JdoContinuumStore.java:1287) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1282) > at > org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached > (JdoContinuumStore.java:1277) > at > org.apache.maven.continuum.store.JdoContinuumStore.getSystemConfiguration(JdoContinuumStore.java:1375) > at > org.apache.maven.continuum.initialization.DefaultContinuumInitializer.initialize > (DefaultContinuu
[jira] Commented: (CONTINUUM-1188) JPox relies on java being on the path, but maven does not, so fails with a file not found exception
[ http://jira.codehaus.org/browse/CONTINUUM-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97409 ] Andy Jefferson commented on CONTINUUM-1188: --- FYI JPOX provides persistence of Java objects to datastores, used by Continuum. Obviously the JPOX enhancer requires Java to be able to run, just as it requires jdo2-api.jar to be in the CLASSPATH - all documented clearly in the JPOX docs. This issue is Continuum-specific > JPox relies on java being on the path, but maven does not, so fails with a > file not found exception > --- > > Key: CONTINUUM-1188 > URL: http://jira.codehaus.org/browse/CONTINUUM-1188 > Project: Continuum > Issue Type: Bug >Affects Versions: 1.1-alpha-1 > Environment: ubuntu 6.10 >Reporter: Nigel Magnay >Priority: Trivial > Fix For: 1.1-alpha-# > > > This may be a jpox bug (whatever jpox is), but you get a file not found > exception if java isn't on your path. > "Error while executing the JPox tool 'org.jpox.enhancer.JPOXEnhancer'" > if build.sh checked that it was, it would avoid this failure case. > Also it relies on javax files being available, so the docs should probably > tell you how to get these. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-104) Support use of custom properties in XDOC files
Support use of custom properties in XDOC files -- Key: DOXIA-104 URL: http://jira.codehaus.org/browse/DOXIA-104 Project: doxia Issue Type: Task Affects Versions: 1.0-alpha-8 Reporter: Andy Jefferson Priority: Critical In the JPOX Maven1 use of "site" we tagged all (XDOC) docs like this Application Identity Persistence 1_2 ... since XDOCs werent validated against any DTD etc. Then in site.jsl we could access these properties via With Maven2 I don't see how I can do this. I define my own skin for JPOX and in site.vm I have $title, $authors but nothing more. Delving into Doxia I see where they were set up. No allowance for users own properties. The requirement for JPOX is that we have a large number of documents, and we tag each doc for particular categories ... which will then appear on the web site as horizontal navigation (the default Maven skin only has the navColumn ... vertical navigation). By being able to tag docs into categories/subcategories etc we can then generate a site that the user selects a horizontal nav category, and then a horizontal nav sub-category, and they see vertical navigation within that subcategory. This was possible with Maven1 due to the above ability. Without an equivalent in Maven2 we cannot switch over. The JPOX docs (from Maven1) are available at http://www.jpox.org/docs/1_2/index.html so you can understand what is being talked about here. If you need any more info let me know. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85784 ] Andy Jefferson commented on CONTINUUM-994: -- Was fixed in JPOX 1.1.6 > New indexes created during continuum startup when using postgresql > -- > > Key: CONTINUUM-994 > URL: http://jira.codehaus.org/browse/CONTINUUM-994 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Richard C. L. Li > Fix For: 1.1 > > > I used postgresql 8.1.4 with continuum and everytime when continuum startup, > it creates a set of indexes. I configured to restart continuum once a day > and after 2 months it generated tens of indexes in every table. > I guessed this maybe the problem of the the UPPER CASE of the table and > column names, this may make the detection of indexes fails and the JDO > recreate everytime it startup. > Workaround: after starting continuum for the first time and set the property > org.jpox.autoCreateSchema to false so that indexes will not recreated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-994) New indexes created during continuum startup when using postgresql
[ http://jira.codehaus.org/browse/CONTINUUM-994?page=comments#action_82571 ] Andy Jefferson commented on CONTINUUM-994: -- JPOX had an issue of this form some time ago. This was fixed (JPOX releases are now up to 1.1.5 so perhaps using something recent would help). All recent versions dont have it. > New indexes created during continuum startup when using postgresql > -- > > Key: CONTINUUM-994 > URL: http://jira.codehaus.org/browse/CONTINUUM-994 > Project: Continuum > Issue Type: Bug > Components: Database >Affects Versions: 1.0.3 >Reporter: Richard C. L. Li > > I used postgresql 8.1.4 with continuum and everytime when continuum startup, > it creates a set of indexes. I configured to restart continuum once a day > and after 2 months it generated tens of indexes in every table. > I guessed this maybe the problem of the the UPPER CASE of the table and > column names, this may make the detection of indexes fails and the JDO > recreate everytime it startup. > Workaround: after starting continuum for the first time and set the property > org.jpox.autoCreateSchema to false so that indexes will not recreated. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MAVEN-1125) ant:java fork issues
[ http://jira.codehaus.org/browse/MAVEN-1125?page=all ] Andy Jefferson updated MAVEN-1125: -- Attachment: maven-console-test.jar Attached jar attempts to reproduce this. To run with Ant You need jpox-1.1.0.jar, jdo2-api-2.0.jar, hsqldb-1.8.0.4.jar, log4j-1.2.8.jar in your maven local repo, and set the maven local repo location in build.xml Type "ant clean compile run", and it runs fine, prompting for input and returning it. To run with Maven (1.0.2) Type "maven clean jar run" Gives java.lang.NoClassDefFoundError: org/w3c/dom/Document (xml-apis, xml-resolver, xercesImpl are listed as dependencies) Either there's something I can add to maven.xml/project.xml to get this to work, or something is incorrect in Maven. Maybe there's something I've got wrong in maven.xml ? > ant:java fork issues > > > Key: MAVEN-1125 > URL: http://jira.codehaus.org/browse/MAVEN-1125 > Project: Maven > Issue Type: Bug >Affects Versions: 1.0-rc2 > Environment: Linux, JDK1.4.2 >Reporter: Andy Jefferson > Attachments: maven-console-test.jar > > > I have a Java app that I want to invoke via Maven. The Java app uses stdin > and stdout. > If I invoke using ant:java using "fork=true" then stdin doesn not respond > correctly. That is, the app prompts, but the user can type to their hearts > content and nothing reaches the app. > If I invoke using ant:java using "fork=false" then I get strange XML related > errors about unresolved references org/w3c/dom/Node, org/w3c/dom/Document -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVEN-1125) ant:java fork issues
[ http://jira.codehaus.org/browse/MAVEN-1125?page=comments#action_71100 ] Andy Jefferson commented on MAVEN-1125: --- If I take a very simple Java app that accepts input on System.in and reads it using a BufferedReader and does nothing more complicated then using fork=false will work :-) Sadly I want to do something more complicated. When I bring in other things (like XML parsing) then I get the xml-apis messages. I then add your jars to the dependencies and they get resolved (why I should have to do this is another issue since I haven't specified ANYTHING in project.xml to impose any restriction on XML parsing. I simply selected to run with JDK1.4.2_11 ... all other choices were made by Maven itself. My project.xml contains entries for log4j, jpox, and javax.jdo/jdo2-api ONLY). I then bring in reflection to my (simple) app. It then gives Caused by: java.lang.NoClassDefFoundError: sun/reflect/ConstructorAccessorImpl at sun.misc.Unsafe.defineClass(Native Method) at sun.reflect.ClassDefiner.defineClass(ClassDefiner.java:45) at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) at sun.reflect.MethodAccessorGenerator.generateConstructor(MethodAccessorGenerator.java:76) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:30) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:70) so Maven (1.0.2) is doing something with the CLASSPATH and basic JDK classes (since they are part of the JDK i am using and that Maven is running with) are no longer found whereas they are by using a plain Ant (1.6.1) run with fork=false. *This is the issue*. [My current JDK is j2sdk1.4.2_11 on Linux] Let's just forget the fork=true case since I shouldn't have to fork just to get something working > ant:java fork issues > > > Key: MAVEN-1125 > URL: http://jira.codehaus.org/browse/MAVEN-1125 > Project: Maven > Issue Type: Bug >Affects Versions: 1.0-rc2 > Environment: Linux, JDK1.4.2 >Reporter: Andy Jefferson > > I have a Java app that I want to invoke via Maven. The Java app uses stdin > and stdout. > If I invoke using ant:java using "fork=true" then stdin doesn not respond > correctly. That is, the app prompts, but the user can type to their hearts > content and nothing reaches the app. > If I invoke using ant:java using "fork=false" then I get strange XML related > errors about unresolved references org/w3c/dom/Node, org/w3c/dom/Document -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVEN-1125) ant:java fork issues
[ http://jira.codehaus.org/browse/MAVEN-1125?page=comments#action_71099 ] Andy Jefferson commented on MAVEN-1125: --- Hi Arnaud, so if i dont want to fork the JVM (and I dont see why I should since I want console input from my sample application), what do i need to do in maven.xml ? or project.xml ? I have (in maven.xml) With fork=false I just tried adding your versions of xml-apis, xml-resolver, xercesImpl to project.xml (previously I had nothing specified for those -- just entries for my own app jars) and I get java.lang.NoClassDefFoundError: sun/reflect/ConstructorAccessorImpl (using JDK 1.4.2_11) With fork=true, then it never reads the console input. What do i do to get Ant to read from the console when fork=true ? What do I specify in this setInputHandler ? (in the above maven.xml snippet) All I want to do is run a sample (Java) app that uses console input via Maven. It works via an Ant task (using fork=false) so I dont see a good reason why not with Maven. > ant:java fork issues > > > Key: MAVEN-1125 > URL: http://jira.codehaus.org/browse/MAVEN-1125 > Project: Maven > Issue Type: Bug >Affects Versions: 1.0-rc2 > Environment: Linux, JDK1.4.2 >Reporter: Andy Jefferson > > I have a Java app that I want to invoke via Maven. The Java app uses stdin > and stdout. > If I invoke using ant:java using "fork=true" then stdin doesn not respond > correctly. That is, the app prompts, but the user can type to their hearts > content and nothing reaches the app. > If I invoke using ant:java using "fork=false" then I get strange XML related > errors about unresolved references org/w3c/dom/Node, org/w3c/dom/Document -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVEN-1125) ant:java fork issues
[ http://jira.codehaus.org/browse/MAVEN-1125?page=comments#action_71097 ] Andy Jefferson commented on MAVEN-1125: --- Hi, this was closed in March (didnt receive a notification) and finally came back to the issue. I read the "more succinct report" that it refers to and the "solution" does nothing for me. How am i to use ant:java with fork=false and avoid the xml-apis messages ? How am I to use ant:java with fork=true and get the input ? What do i pass in to the "InputHandler" ? Point me to a doc at least that defines this, please Is this fixed in Maven 1.1-beta-X for ant fork=false ? No, I dont use Maven 2 yet. Would it work there ? > ant:java fork issues > > > Key: MAVEN-1125 > URL: http://jira.codehaus.org/browse/MAVEN-1125 > Project: Maven > Issue Type: Bug >Affects Versions: 1.0-rc2 > Environment: Linux, JDK1.4.2 >Reporter: Andy Jefferson > > I have a Java app that I want to invoke via Maven. The Java app uses stdin > and stdout. > If I invoke using ant:java using "fork=true" then stdin doesn not respond > correctly. That is, the app prompts, but the user can type to their hearts > content and nothing reaches the app. > If I invoke using ant:java using "fork=false" then I get strange XML related > errors about unresolved references org/w3c/dom/Node, org/w3c/dom/Document -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
