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/
Re: VMBuild needs volunteers
Hi, If I can help I will (propably not a 24/7 support :-) ). 2008/3/8, Wendy Smoak [EMAIL PROTECTED]: We have a Continuum instance available for ASF projects to use: http://vmbuild.apache.org/continuum/groupSummary.action This is our (internal) public face, and it would be great to have more volunteers keeping an eye on it! It was down this morning, so I re-started it (at 11AM MST.) I didn't investigate why it was unhappy. One thing we really need to do is upgrade it to the latest version. I'm hesitant to take that on alone, but maybe someone else is braver than I, or 2-3 people might collaborate to get it done and documented. Sure won't be so easy (is all the build history important ?) And there are 11 open issues: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=10410component=12311662resolution=-1sorter/field=prioritysorter/order=DESC There is some documentation here: http://cwiki.apache.org/confluence/display/vmbuild/Home (This needs to be moved into svn to better conform with other infra documentation, something that's been on my list for a while now...) Ok but where ? (something like https://svn.apache.org/repos/asf/vmbuild or https://svn.apache.org/repos/asf/continuum/vmbuild). Using a site write with the maven format (apt xdoc) ? -- Wendy
Re: Confused about the branches
2008/3/4, Brett Porter [EMAIL PROTECTED]: On 05/03/2008, at 5:18 AM, Olivier Lamy wrote: 2008/3/4, Brett Porter [EMAIL PROTECTED]: On 04/03/2008, at 10:47 AM, Olivier Lamy wrote: Agree on this. Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which prevent using xml-rpc :-(. Cool - shall we just start using the 1.2 bucket in JIRA? There are only 14 issues there now so maybe we could keep that to 20-30 issues all together and release it. +1 ok, I'll get my stuff in there I found these changes on trunk that are not on the branch: r617400. (The rest is documentation) I found these changes on the branch that are not on trunk: r627196, r620613, r620612, r620611 I think we should just merge all those from the branch to trunk, set it as v1.2, and close the branch for now? +1. (Perso, I don't really like the idea of starting a parrallel branch/trunk a la mvn 2.1 :-) ) I'll merge the changes to trunk - but will wait to hear other's opinions on this too before changing the branch It looks we don't have any objections/opinions. All changes from branch has been merged. I will rename the version in the trunk to 1.2 (tomorow). If no objections, I will change root pom to not have anymore maven pom as parent. Sounds good - do you think we should have a Continuum parent POM like we do for Archiva? https://svn.apache.org/repos/asf/continuum/parent/trunk ? A new pom without parent ? (I can certainly copy some contents from the maven parent pom) With an ASF parent instead of the Maven one, yep. Question : do we have to change the groupId in the poms : org.apache.maven.continuum - org.apache.continuum ( java package too ? looks a big bang) I don't see any downside to doing this :) - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Confused about the branches
There are some other branches residing in Continuum SVN. Should we remove any (or all) of the following if they are not in active development? I know (id-refactor and key-based-refactor can go) # continuum-acegi # continuum-site_1.1 # gbuild # id-refactor # key-based-refactor # osworkflow-integration # release-integration Cheers, Rahul Brett Porter wrote: Hi, I'm a bit confused about the current branch scenarios, we have 1.2 on a branch and 2.0 on trunk. Several changes have been made on each, and none merged to the other. Can I suggest we merge all branch changes to trunk, rename trunk to 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use that for bugfixes only? WDYT? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/