Dealing with project documentation
Hi,
we are starting up a project and the first thing we need to do is put some project documentation under version control. Are there already ideas/ways of working defined on how to do that? We tried a couple of ways (drag & drop in the package explorer), but working with documentation from the Package Explorer does not feel right. Besides that you have no way to structure your documentation (you are not allowed to create packages in non-Java projects). So we would probably need another view next to the Package Explorer specifically for documentation, or maybe project documentation could be made visible under Team Articacts. Another thing is that you want to set at least the restriction to the documentation project/component that parallel development (we dont want to merge Word documents, do we) is not allowed. Is there a way to do that? Kind regards, Ron de Jong |
2 answers
Ron,
Generally I use the "Resource perspective" of Eclipse (Window>Open Perspective>Other>Resource) when I want to map the organization of my project to a directory stucture which has nothing to do with Java. For the merging issue on Word document, I will ping somebody from the SCM team. kind regards Philippe |
Phillipe is right in that the resource perspective, or more specifically
the resource or project navigators will give you easier access to documentation projects. You can create the directory structure of your choice in these plain projects without having to worry about Jazz cruft. For now, we don't support marking files as locked for editing to avoid merging. However, this will be supported in the first product release. A+, Jean-Michel Philippe Krief wrote: Ron, |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.