[Jboss-dev-forums] [Design of JBoss Labs] - Re: Project.xml globalisation

[wrzep <do-...@jb...>]

My next question is: Why we want to move all project info into project.xml?

IMHO, there are few things to improve here, but having all information in one file might not be really handy as it will make project.xml file longer and difficult to read.

Please consider the following use cases:

1. Setting up a new project.

More sophisticated project.xml means more efforts to just add a simple project. Even if user doesn't want to have downloads page, project specific ads and pools, we should include them in the project.xml template, which makes it less readable.

2. Adding a new file to the downloads section.

Someone wants to add a file to downloads. Let him go to his project dir in the cms. downloads.xml file catches his sight and he knows where he should go to do so.
If downloads conf were inside project.xml, he will be forced to browse the file searching for place where downloads are defined.

Having all information in one file might be tempting, but, to my way of thinking, it will make project configuration more complicated. I'd suggest considering what should be defined inside project.xml and what not so that we can keep it all simple ;-)

What's your opinion?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949065#3949065

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949065