Author |
Message
|
pcelari |
Posted: Tue Feb 28, 2012 8:27 am Post subject: importing project: how to import part of a msgflow project? |
|
|
Chevalier
Joined: 31 Mar 2006 Posts: 411 Location: New York
|
Hello,
is it possible to import only part of a project?
Everytime, I import a project, the whole project first gets deleted before the import. But I only want to import some of the flows in the project file.
This seems to be a trivial thing to do, but the importer doesn't allow it. This makes synchronizing code between developers a pain. A few times, completed work got overriden.
I must have missed sth using the export/import utility.
Any hint on that? _________________ pcelari
-----------------------------------------
- a master of always being a newbie |
|
Back to top |
|
 |
lancelotlinc |
Posted: Tue Feb 28, 2012 8:30 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Developers who share the same project should share all the flows in the project. If not, put the flows not shared by developers in a different project.
Are you using source control? If not, why not? Don't bother developing anything until you have a solid version management system in place. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 28, 2012 8:31 am Post subject: Re: importing project: how to avoid overriding everything? |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
pcelari wrote: |
Any hint on that? |
Don't use the project interchange format? Seriously, you can get quite a lot of mileage just zipping stuff up (another option on the import/export wizard).
But for parallel development syncronized between a team of developers download a copy of SubVersion and use that. All the syncronization you need, built in. Later, you can download ant & build bar files from the repository with all the benefits that brings. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Feb 28, 2012 8:35 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
lancelotlinc wrote: |
Developers who share the same project should share all the flows in the project. If not, put the flows not shared by developers in a different project. |
1 project, 10 developers, each developer given responsibility for a different flow, all or some of the flows co-dependant (flow A updates a database that flow B uses). It's a common development situation and once you go into testing and the bug fixing starts it's like spinning plates.
Even if you have source code control, which you should have with a team of 10. Even if you're not building from it, which is a good idea with a team of 10.
Been there, done that, got bitten. I think we've touched on this before. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Feb 28, 2012 9:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can look at jazz.net for another free alternative to Subversion. |
|
Back to top |
|
 |
paintpot |
Posted: Tue Feb 28, 2012 9:18 am Post subject: |
|
|
Centurion
Joined: 19 Sep 2005 Posts: 112 Location: UK
|
Totally agree with the other posts.
For your current (hopefully temporary) need - import into a new workspace and then pick out the bits you need. This isn't a sustainable model, but might be ok for a few test / play projects. |
|
Back to top |
|
 |
pcelari |
Posted: Tue Feb 28, 2012 12:59 pm Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006 Posts: 411 Location: New York
|
Thanks so much for sharing your insight.
Weired, it never downed on my that there're alternatives than using the project interchange format for output. Using file system option resolve the difficulty once and for all.
I'll look into using the suggestioned free version control tools.
Again, thanks a lot! _________________ pcelari
-----------------------------------------
- a master of always being a newbie |
|
Back to top |
|
 |
|