16 Oct
2010
16 Oct
'10
1:10 p.m.
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?
Thanks
-Vincent
16 Oct
16 Oct
2:38 p.m.
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
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/
3:01 p.m.
On Oct 16, 2010, at 2:38 PM, Sergiu Dumitriu wrote:
On 10/16/2010 01:10 PM, Vincent Massol wrote:
We wouldn't want that developers have to checkout platform when they check the
enterprise trunk...
Thanks
-Vincent
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 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/
9:51 p.m.
On 10/16/2010 03:01 PM, Vincent Massol wrote:
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:
We wouldn't want that developers have to checkout platform when they check the
enterprise trunk...
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
> 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/
10:04 p.m.
On Oct 16, 2010, at 9:51 PM, Sergiu Dumitriu wrote:
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)
-Vincent
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:
We wouldn't want that developers have to checkout platform when they check the
enterprise trunk...
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 >> When branching enterprise, we update the
platform/core to point to the
>> appropriate core branch, and so on.
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/
10:25 p.m.
On Oct 16, 2010, at 10:21 PM, Sergiu Dumitriu wrote:
On 10/16/2010 10:04 PM, Vincent Massol wrote:
I don't feel it's breaking it, quite the opposite. I don't see a better
location.
This is also what we already have for platform:
http://svn.xwiki.org/svnroot/xwiki/platform/trunks
Thanks
-Vincent
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:
> 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...
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? >>>> When branching enterprise, we update
the platform/core to point to the
>>>> appropriate core branch, and so on.
17 Oct
17 Oct
2:17 a.m.
On 10/16/2010 10:25 PM, Vincent Massol wrote:
On Oct 16, 2010, at 10:21 PM, Sergiu Dumitriu wrote:
No, not really. It's true that there's a "trunks" under the top level
directory, but it's among other platform components, not interfering
with the classic trunk+branches+tags trio, which is standard. Anyway,
it's just a minor complaint, consider it a flat 0, since I don't see a
better place either.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On 10/16/2010 10:04 PM, Vincent Massol wrote:
I don't feel it's breaking it, quite the opposite. I don't see a better
location.
This is also what we already have for platform:
http://svn.xwiki.org/svnroot/xwiki/platform/trunks
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:
>
> On Oct 16, 2010, at 2:38 PM, Sergiu Dumitriu wrote:
>
>> 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...
>
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?
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)
3:16 p.m.
+1
On Sat, Oct 16, 2010 at 13:10, Vincent Massol <vincent(a)massol.net> 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?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
4:07 p.m.
+0
Thanks,
Marius
On 10/16/2010 02: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?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5136
days inactive
5137
days old
9 comments
4 participants
participants (4)
-
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol