16 Oct
2010
16 Oct
'10
10:21 p.m.
On 10/16/2010 10:04 PM, Vincent Massol wrote:
On Oct 16, 2010, at 9:51 PM, Sergiu Dumitriu wrote:
OK, so it would be:
svnroot/xwiki/enterprise/
|- branches
|- tags
|- trunk
|- trunks
This is breaking a bit the t+b+t convention, so I don't like it that much.
On 10/16/2010 03:01 PM, Vincent Massol wrote:
People who want to build enterprise will checkout enterprise/trunk as they do now,
nothing is changed from now.
People who want to check out enterprise + platform at once will checkout
enterprise/trunks (new)
On Oct 16, 2010, at 2:38 PM, Sergiu Dumitriu wrote:
Something's not clear, I thought this is the same thing, except that
it's in a different structure. Doesn't your trunks proposal also imply
checking out the platform? On 10/16/2010 01:10 PM, Vincent Massol wrote:
> Hi devs,
>
> I'd like to create svn externals for enterprise in enterprise/trunks that would
build both platform and enterprise. I would put a pom.xml in trunks for doing that.
>
> The need is to have a single maven multi module project to run Clover on (otherwise
it's more complex for setting up Clover).
>
> WDYT?
I'm not sure trunks is the best option. We could have some svn externals
directly in the enterprise directory.
svnroot/xwiki/enterprise/trunk/
|- database
|- distribution
|- distribution-test/
|- installers/
|- platform
|- /core/ -> svnroot/xwiki/platform/core/trunk/
|- ...
|- web
|- wiki
We wouldn't want that developers have to checkout platform when they check the
enterprise trunk...
>>> When branching enterprise, we update the platform/core to point to the
>>> appropriate core branch, and so on.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/