[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] Created: (MAVENUPLOAD-2116) Please add MigLayout to the auto rsynced list.
Please add MigLayout to the auto rsynced list. -- Key: MAVENUPLOAD-2116 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2116 Project: Maven Upload Requests Issue Type: New Feature Reporter: Mikael Grev "miglayout","rsync://[EMAIL PROTECTED]/maven/releases","rsync",Mikael Grev,[EMAIL PROTECTED],, The password is "maven". MigLayout is a LayoutManager for Swing & SWT. It is the #1 RFE for being added to SWT and #10 RFE for being added to the Java SDK. I own MiGInfoCom AB which owns MigLayout. Cheers, Mikael Grev -- 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] Moved: (MEV-591) Commons logging adapters is missing a POM file
[ http://jira.codehaus.org/browse/MEV-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved MAVENUPLOAD-2115 to MEV-591: -- Group ID: commons-logging Artifact ID: commons-logging-adapters Version: 1.1 Workflow: jira (was: Maven New) Key: MEV-591 (was: MAVENUPLOAD-2115) Project: Maven Evangelism (was: Maven Upload Requests) > Commons logging adapters is missing a POM file > -- > > Key: MEV-591 > URL: http://jira.codehaus.org/browse/MEV-591 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Paul Austin > > The commons-logging-adapters 1.1 is in the repository but there is no pom > file just the jar and the metadata. -- 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: (MRELEASE-326) Doens't resolve multiproject dependencies properly
[ http://jira.codehaus.org/browse/MRELEASE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139211#action_139211 ] Kalle Korhonen commented on MRELEASE-326: - This is the documented behavior of the release plugin right? By default, release:prepare doesn't run install goal. If you need it, you can configure it to run "clean install" as instructed at http://maven.apache.org/plugins/maven-release-plugin/examples/run-goals-before-commit.html > Doens't resolve multiproject dependencies properly > --- > > Key: MRELEASE-326 > URL: http://jira.codehaus.org/browse/MRELEASE-326 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-7 > Environment: Windows, JDK 1.6, Maven 2.08 >Reporter: Kuno Baeriswyl > Attachments: Stacktrace_release-plugin.txt > > > I'd try to make a release:prepare from a multiproject: > A (Multiproject POM) > B (Core Interfaces) > C (Component) > D (Core Impl) > E (Standalone Client) > F (EJB) > G (Client) > A is the parent project and contains the other project from B to G. Following > dependencies are defined : G -> F -> D -> B -> A > However, when it comes to build the Artifact G, the release plugin aborts, > because of missing Artifact F. But it's part of the Multiproject and was just > build before. The release plugin checks the remote repository for an existing > version. Which is non-sense, since I'm actually try to buld it right now... > Since the release plugin has already changed the pom from Snapshot to stable > version labels. I can now do "mvn install" and the missing Artefact will be > installed. And the second run of mvn release:prepare will succeed! Though, I > don't like this workaround and hope this can be fixed. > Thanks > Kuno -- 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=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] Closed: (MPLUGIN-57) Mojo fields @component and no @parameter annotations are still considered parameters and can't be distinguished when it became a Parameter Object
[ http://jira.codehaus.org/browse/MPLUGIN-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MPLUGIN-57. -- Resolution: Fixed Fix Version/s: 2.4 This was solved by the chosen fix for MPLUGIN-62. > Mojo fields @component and no @parameter annotations are still considered > parameters and can't be distinguished when it became a Parameter Object > - > > Key: MPLUGIN-57 > URL: http://jira.codehaus.org/browse/MPLUGIN-57 > Project: Maven 2.x Plugin Tools > Issue Type: Improvement >Reporter: Edwin Punzalan >Priority: Minor > Fix For: 2.4 > > > Two possible solutions: > 1] Do not consider fields with @component and no @parameter as a mojo > parameter > or > 2] Add a method boolean isComponent() in the Parameter Object to distinguish > them from actual parameters. > Btw, this causes @component fields to appear in the mojo parameters list. -- 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] Issue Comment Edited: (MNG-3333) range specified dependencies don't work
[ http://jira.codehaus.org/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139237#action_139237 ] brettporter edited comment on MNG- at 6/22/08 1:52 AM: looks like this was an issue with the metadata, and though I agree the hard dependency using the metadata is a bit weird, I think it's best we look to how artifact evolves was (Author: brettporter): looks like this was an issue with the metadata > range specified dependencies don't work > --- > > Key: MNG- > URL: http://jira.codehaus.org/browse/MNG- > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.1 >Reporter: Milos Kleint >Assignee: Brett Porter > Attachments: ranges.zip > > > current 2.1-SNAPSHOT > When a dependency is specified with version [1.0.4] the build of project > fails, so does project loading in the IDE. > Example project attached. -- 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] Closed: (MNG-3333) range specified dependencies don't work
[ http://jira.codehaus.org/browse/MNG-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-. - Assignee: Brett Porter Resolution: Cannot Reproduce Fix Version/s: (was: 2.1-alpha-1) looks like this was an issue with the metadata > range specified dependencies don't work > --- > > Key: MNG- > URL: http://jira.codehaus.org/browse/MNG- > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.1 >Reporter: Milos Kleint >Assignee: Brett Porter > Attachments: ranges.zip > > > current 2.1-SNAPSHOT > When a dependency is specified with version [1.0.4] the build of project > fails, so does project loading in the IDE. > Example project attached. -- 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
