We don't currently have plans to support this, but if you want to open up a proposal in JIRA, we can iterate on some ideas and try to make it work for 2.2.
Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 11/30/2006 03:46:53 PM: > Sorry Dan, I should be more specific. We're planning to have several > Muse projects, each with its own deployment descriptor. At some point, > we hope to deploy them all together as one application. I'm thinking > theoretically, we could even have one master project with EPRs pointing > to resources defined in other projects. > > So that's where I'm wondering if each project's descriptor can be > maintained separately, but combined into a master descriptor at > deployment time by using "import" statements. This would require > muse.xml to support a hierarchy-like feature, but I'm not sure if Muse > currently supports (or plans to support) this. > > > -----Original Message----- > From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 30, 2006 11:36 AM > To: [email protected] > Subject: Re: multiple muse.xml files > > We don't have any kind of importing... doesn't version control software > solve your problem? > > Dan > > > > "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 11/30/2006 > 02:14:22 PM: > > > Is there a way to have the muse.xml file import other child muse.xml > > files, and have Muse reference the master file? Does Muse support > this? > > > > In a distributed team, I'm wondering if it is possible to have each > > developer be responsible for defining certain resources and maintain > > their own muse.xml files. Then before deployment, we can have one > > master muse.xml file which imports the other xml files via the use of > > "import" statements. We do not want to cut-paste all into one file > > because a lot of problems can arise if many people are editting the > > same config file. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
