Trouble building maven-plugins parent pom in Continuum
I added maven/plugins/trunk/pom.xml to Continuum 1.1 and forced a build of the maven-plugins parent pom. (This is my own instance, not vmbuild or the maven zone.) It's using the default --non-recursive build definition, so I don't understand this error: INFO | jvm 1| 2008/03/09 09:55:55 | edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDOFatalUserException: Attempt to store value /maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt (from /maven/plugins/branches/maven-dependency-plugin-MDEP-100/src/site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt:591694) in column NAME that has maximum length of 255. Please correct your data! The full stack trace from the logs is here: http://wiki.wsmoak.net/cgi-bin/wiki.pl?Continuum/MavenPluginsError Any ideas? -- Wendy
Re: Trouble building maven-plugins parent pom in Continuum
Even though it uses --non-recursive to build, the checkout does not exclude any subdirectories. This would occur in the checkout/update and building changesets. On 10/03/2008, at 4:08 AM, Wendy Smoak wrote: I added maven/plugins/trunk/pom.xml to Continuum 1.1 and forced a build of the maven-plugins parent pom. (This is my own instance, not vmbuild or the maven zone.) It's using the default --non-recursive build definition, so I don't understand this error: INFO | jvm 1| 2008/03/09 09:55:55 | edu.emory.mathcs.backport.java.util.concurrent.ExecutionException: javax.jdo.JDOFatalUserException: Attempt to store value /maven/plugins/trunk/maven-dependency-plugin/src/site/apt/examples/ resolving-conflicts-using-the-dependency-tree.apt (from /maven/plugins/branches/maven-dependency-plugin-MDEP-100/src/ site/apt/examples/resolving-conflicts-using-the-dependency-tree.apt: 591694) in column NAME that has maximum length of 255. Please correct your data! The full stack trace from the logs is here: http://wiki.wsmoak.net/cgi-bin/wiki.pl?Continuum/MavenPluginsError Any ideas? -- Wendy -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Trouble building maven-plugins parent pom in Continuum
On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter [EMAIL PROTECTED] wrote: Even though it uses --non-recursive to build, the checkout does not exclude any subdirectories. This would occur in the checkout/update and building changesets. Is a build error and Please correct your data! the right response here, or can Continuum do something useful like truncate the data and keep going? -- Wendy
Re: Trouble building maven-plugins parent pom in Continuum
I think Continuum needs to allow longer values in here - it certainly should not error out. On 10/03/2008, at 7:13 AM, Wendy Smoak wrote: On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter [EMAIL PROTECTED] wrote: Even though it uses --non-recursive to build, the checkout does not exclude any subdirectories. This would occur in the checkout/update and building changesets. Is a build error and Please correct your data! the right response here, or can Continuum do something useful like truncate the data and keep going? -- Wendy -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Trouble building maven-plugins parent pom in Continuum
Hi, Currently the max size for this field is 512. class nameChangeFile/name packageNameorg.apache.maven.continuum.model.scm/packageName version1.0.9+/version fields field name stash.maxSize=512name/name version1.0.9+/version typeString/type /field Which doens't look enough. 1024 ? -- Olivier 2008/3/9, Brett Porter [EMAIL PROTECTED]: I think Continuum needs to allow longer values in here - it certainly should not error out. On 10/03/2008, at 7:13 AM, Wendy Smoak wrote: On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter [EMAIL PROTECTED] wrote: Even though it uses --non-recursive to build, the checkout does not exclude any subdirectories. This would occur in the checkout/update and building changesets. Is a build error and Please correct your data! the right response here, or can Continuum do something useful like truncate the data and keep going? -- Wendy -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Trouble building maven-plugins parent pom in Continuum
512 should be - the error Wendy got was going over 255. On 10/03/2008, at 9:08 AM, Olivier Lamy wrote: Hi, Currently the max size for this field is 512. class nameChangeFile/name packageNameorg.apache.maven.continuum.model.scm/packageName version1.0.9+/version fields field name stash.maxSize=512name/name version1.0.9+/version typeString/type /field Which doens't look enough. 1024 ? -- Olivier 2008/3/9, Brett Porter [EMAIL PROTECTED]: I think Continuum needs to allow longer values in here - it certainly should not error out. On 10/03/2008, at 7:13 AM, Wendy Smoak wrote: On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter [EMAIL PROTECTED] wrote: Even though it uses --non-recursive to build, the checkout does not exclude any subdirectories. This would occur in the checkout/update and building changesets. Is a build error and Please correct your data! the right response here, or can Continuum do something useful like truncate the data and keep going? -- Wendy -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
