Re: svn changes in james/project

2006-10-01 Thread Stefano Bagnara
Noel J. Bergman wrote: It contains the commons informations for the James project (website, repositories, developers, licenses). Think at it as the AbstractPOM for our POMs (m2 has many Object Oriented things in its architecture) It seems to me that the site/ structure was being used for that

RE: svn changes in james/project

2006-09-30 Thread Noel J. Bergman
Stefano Bagnara wrote (merged from two replies): > Noel J. Bergman wrote: > > AGAIN, why isn't the project/ directory under site/, which IS known to the > > mailer? I have raised this before, and not gotten a reply. > It is under project because it does not contains only site specific things. >

Re: svn changes in james/project

2006-09-30 Thread Stefano Bagnara
Noel J. Bergman wrote: I just reorganized james/project folder in svn AGAIN, why isn't the project/ directory under site/, which IS known to the mailer? I have raised this before, and not gotten a reply. --- Noel About the "AGAIN" and "not gotten a reply" maybe you missed this threa

Re: svn changes in james/project

2006-09-30 Thread Stefano Bagnara
Noel J. Bergman wrote: I just reorganized james/project folder in svn AGAIN, why isn't the project/ directory under site/, which IS known to the mailer? I have raised this before, and not gotten a reply. It is under project because it does not contains only site specific things. In fact the

RE: svn changes in james/project

2006-09-30 Thread Noel J. Bergman
> I just reorganized james/project folder in svn AGAIN, why isn't the project/ directory under site/, which IS known to the mailer? I have raised this before, and not gotten a reply. --- Noel - To unsubscribe, e-mail:

svn changes in james/project

2006-09-30 Thread Stefano Bagnara
I just reorganized james/project folder in svn to include the tags/trunk/branches structure that I forgot to create when moving it out of sandbox. So I created the 3 folders, I moved all the previous content to "trunk" and I updated all of the pom.xml to include the new "trunk" path in their