|
| Re: Searching for a tool to automate development process (+) [message #375683 is a reply to message #375680] |
Mon, 24 March 2008 04:35  |
 Matt Hollingsworth
Messages: 2
Registered: July 2009 |
Junior Member |
|
|
Vadim,
I believe that Buckminster would work well for the purposes that you have
described. If you could effectively split your source into seperate projects,
then you could use "virtual distros" (described here:
http://wiki.eclipse.org/Introduction_to_Buckminster under the section called
"put together a virtual distribution") to tie different components together
for your different clients. If you are using Eclipse (and not just "Headless"
Buckminster) and each of your modules is a seperate eclipse project, it will
be really easy since Buckminster will read the project files and see to it
that dependencies are resolved for you and all that.
Let us (news group or me) know if you need any help along the way, or help
getting started.
Good luck,
-Matt
On 3/20/2008 8:22:24 PM, Vadim Dmitriev wrote:
> Hi!
>
> (First of all, sorry for such a general post subject, but I haven't
> found any way to describe my problem shortly)
>
> Let me describe my current situation.
> Main software project of the company I am working in is a project that
> "cries for modularity". That is that project consists of about one
> hundred similiar small "modules". Currently we develop and maintain it
> as a whole. Problem is that our clients want only definite part of our
> application installed and every client wants unique set of modules...
> and prior to the deployment we have to check out project, manually
> delete modules that shouldn't be installed, modify configs... All that
> several times a week. Needless to say that someone do skrew it up once
> in a while and we begin it all again and again (with boss breathing down
> on our necks).
> Here comes an interesting part - our app is web (JSF) application
> actually, so we cannot just slice project into separate jars and load
> them all at a start-time. Project has to be "merged" at deployment time:
> jsp pages from all required modules copied to the WebContents folder,
> faces-configs merged into one file, java classes copied to the src/bin
> folders and so on.
> To ease maintenance (at least a little) my only idea is to split one big
> project into hundred little projects that will contain only files and
> configuration data directly related to them and maintain these projects
> independently.
> So development cycle will be:
> 1. check out little project
> 2. copy all that project's files to the "main project"
> 3. make changes to that little module's files and test them in the
> "whole project environment"
> 4. copy all changed related files back to the module project
> 5. commit changes back to svn
>
> Currently I'm looking for some tool that can automate that process
> (except third item, but who knows :) ). Maybe it'll require me to write
> several classes to handle all that copy/merge logic. During my search I
> came to the Buckminster project. I read a little about it and was really
> confused about was it actually does. Before starting deep digging I hope
> someone can tell me if Buckminster can automate described process. And
> more specifically - if Buckminster _is_ a proper tool to support such a
> develoment cycle. Maybe I'm going in totally wrong direction here.
>
> Thanks for your time!
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03084 seconds
] 
Search
Help
Register
Login
Home
