Yeah, I¹ve investigated doing this, but haven¹t gotten around to it. I will say that getting the general build and new workspace generation set up with buckminster even for our crazy structure took me less than a day, including reading the giant buckminster book they have :) The ancillary stuff like this is where more mature systems like maven still have a distinct advantage. And if this ultimately doesn¹t work out for some reason, I¹ll be sure to look you up for maven migration assistance. *evil grin*
Trip On 9/23/10 3:45 PM, "David Carver" <d_a_car...@yahoo.com> wrote: > Yep, and it correctly complains because that directory is already versioned > under another directory. If the structure was like trunk/Desktop/feature... > you would run into a simlar situation if you were just trying to check out to: > > features > plugins > > directories. > > The only way around this would be to checkout, and then copy the files...so > have a simple script that runs before the main buckminster build to move the > files into the proper format. > > I'm liking maven better and better everyday. :) > > Dave > > On 09/23/2010 01:30 PM, Trip Gilman wrote: >> Re: [dash-dev] Current promotion strategy for Buckminster Users The problem >> is they would all need to be checked out into the same directory. Here¹s >> what our repository looks like: >> >> >> >> Because we maintain a separate features/plugins structure in each component >> root, the hudson svn complains because the target directory is already a >> working copy. If there was an svn plugin that only did an export instead of >> checkout this would work with an accompanying rm rf bash script. That >> structure would have to be checked out into a single features/plugins >> structure rooted in the Hudson workspace for buckminster to pick them up >> properly. >> >> Trip >> >> >> On 9/23/10 3:23 PM, "David Carver" <d_a_car...@yahoo.com> wrote: >> >> >>> On 09/23/2010 12:14 PM, Trip Gilman wrote: >>> >>>> Re: [dash-dev] Current promotion strategy for Buckminster Users >>>> Now if someone can tell me how to get buckminster to perform an SVN >>>> update during the local resolver materialization step I¹d be golden. >>>> Currently I have to wipe the workspace if I want to build off of the latest >>>> revision. I can¹t use Hudson¹s built in SVN integration because we use >>>> multiple component roots in our repository that need to be checked out into >>>> the same build directory. >>>> >>>> >>> You should be able to add Multiple SVN checkouts for each of the >>> components, for Hudson. >>> >>> Dave >>> >>> >>> >> >> >> >> _______________________________________________ >> dash-dev mailing list >> dash-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/dash-dev >> > >
_______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
