7 Apr
2011
7 Apr
'11
7 p.m.
Hi devs,
The idea is to have the same version and same release for everything related to commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole xwiki-commons
* No need for git modules (svn externals previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
* xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds the
parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
* all other git repos uses "xwiki-commons-pom" as their parent
Note that for JIRA we would have 3 jira projects to make it easy for users (because jira
doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
Note that if we agree we would do the same for xwiki-platform (ie move platform tools in
xwiki-platform).
Here's my +1
Thanks
-Vincent
7 Apr
7 Apr
7:04 p.m.
New subject: [xwiki-devs] [VOTE] Group commons-pom, commons-tools and commons-core together
+1
On Thu, Apr 7, 2011 at 19:00, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
The idea is to have the same version and same release for everything related to commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole xwiki-commons
* No need for git modules (svn externals previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
* xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds
the parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
* all other git repos uses "xwiki-commons-pom" as their parent
Note that for JIRA we would have 3 jira projects to make it easy for users (because jira
doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
Note that if we agree we would do the same for xwiki-platform (ie move platform tools in
xwiki-platform).
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
7:10 p.m.
New subject: [xwiki-devs] [VOTE] Group commons-pom, commons-tools and commons-core together
+1
Denis
On Thu, Apr 7, 2011 at 19:04, Thomas Mortagne <thomas.mortagne(a)xwiki.com>wrote;wrote:
+1
On Thu, Apr 7, 2011 at 19:00, Vincent Massol <vincent(a)massol.net> wrote:
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
Hi devs,
The idea is to have the same version and same release for everything
related to
commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole
xwiki-commons
* No need for git modules (svn externals
previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license
and verification)
* xwiki-commons/pom.xml has an artifact id of
"xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as
parent and
adds the parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an
artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses
xwiki-commons/pom.xml as
parent
* all other git repos uses
"xwiki-commons-pom" as their parent
Note that for JIRA we would have 3 jira projects to make it easy for
users
(because jira doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
Note that if we agree we would do the same for xwiki-platform (ie move
platform
tools in xwiki-platform).
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
7:55 p.m.
New subject: [xwiki-devs] [VOTE] Group commons-pom, commons-tools and commons-core together
On 04/07/2011 07:00 PM, Vincent Massol wrote:
Hi devs,
The idea is to have the same version and same release for everything related to commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole xwiki-commons
* No need for git modules (svn externals previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
* xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds
the parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
* all other git repos uses "xwiki-commons-pom" as their parent
+1.
Note that for JIRA we would have 3 jira projects to
make it easy for users (because jira doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
I'm not sure 3 projects are needed. Why not a single XWiki-commons
project, with different submodules? Especially since they are released
together and have the same version.
Note that if we agree we would do the same for
xwiki-platform (ie move platform tools in xwiki-platform).
WDYM? The tools are already there.
Here's my +1
Thanks
-Vincent
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
8:04 p.m.
On Apr 7, 2011, at 7:55 PM, Sergiu Dumitriu wrote:
They're git repos now and not in the xwiki-platform git repo.
Thanks
-Vincent
On 04/07/2011 07:00 PM, Vincent Massol wrote:
what is a submodule in jira?
Hi devs,
The idea is to have the same version and same release for everything related to commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole xwiki-commons
* No need for git modules (svn externals previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
* xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds
the parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
* all other git repos uses "xwiki-commons-pom" as their parent
+1.
Note that for JIRA we would have 3 jira projects
to make it easy for users (because jira doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
I'm not sure 3 projects are needed. Why not a single XWiki-commons project, with
different submodules? Especially since they are released together and have the same
version. Note that if
we agree we would do the same for xwiki-platform (ie move platform tools in
xwiki-platform).
WDYM? The tools are already there. > Here's my +1
>
> Thanks
> -Vincent
8:38 p.m.
New subject: [xwiki-devs] [VOTE] Group commons-pom, commons-tools and commons-core together
On 04/07/2011 08:04 PM, Vincent Massol wrote:
They're git repos now and not in the xwiki-platform git repo.
I see, I was thinking about the final subdirectory structure, without
thinking of repositories and submodules.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
On Apr 7, 2011, at 7:55 PM, Sergiu Dumitriu wrote:
Sorry, I meant components.
On 04/07/2011 07:00 PM, Vincent Massol wrote:
what is a submodule in jira? Hi devs,
The idea is to have the same version and same release for everything related to commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole xwiki-commons
* No need for git modules (svn externals previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
* xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds
the parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
* all other git repos uses "xwiki-commons-pom" as their parent
+1.
Note that for JIRA we would have 3 jira projects
to make it easy for users (because jira doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
I'm not sure 3 projects are needed. Why not a single XWiki-commons project, with
different submodules? Especially since they are released together and have the same
version. Note that if we agree we would do the same for
xwiki-platform (ie move platform tools in xwiki-platform).
WDYM? The tools are already there.
8:44 p.m.
On Apr 7, 2011, at 8:38 PM, Sergiu Dumitriu wrote:
They're git repos now and not in the xwiki-platform git repo.
I see, I was thinking about the final subdirectory structure, without
thinking of repositories and submodules.
--
Sergiu Dumitriu
On 04/07/2011 08:04 PM, Vincent Massol wrote:
The problem is that you can have nested components so we would need to prefix all current
components with "Core -" and introduce the tool ones with "Tools -" +
the pom one with "Pom -".
I think it's going to be confusing for users and their focus is going to be core
modules mostly, not tools nor top level pom.
What we could do though is log anything related to tools and top level pom in the existing
"Build, Infrastructure and Tests". I like that idea. WDYT?
Thanks
-Vincent
On Apr 7, 2011, at 7:55 PM, Sergiu Dumitriu wrote:
Sorry, I meant components. On 04/07/2011 07:00 PM, Vincent Massol wrote:
what is a submodule in jira? Hi devs,
The idea is to have the same version and same release for everything related to commons.
Rationale:
* Stop the spread of a git repos (see https://github.com/xwiki).
* Make it even easier to release. Only one command to release the whole xwiki-commons
* No need for git modules (svn externals previously)
The proposal is:
xwiki-commons/ (git repo)
|_ xwiki-commons-pom/
|_ xwiki-commons-tools/
|_ xwiki-commons-core/
|_ pom.xml
Details:
* xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
* xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
* xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and adds
the parts related to the tools (license and verification)
* xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
* xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
* all other git repos uses "xwiki-commons-pom" as their parent
+1.
Note that for JIRA we would have 3 jira projects
to make it easy for users (because jira doesn't allow nested components):
* XWiki Commons POM
* XWiki Commons Tools
* XWiki Commons Core
I'm not sure 3 projects are needed. Why not a single XWiki-commons project, with
different submodules? Especially since they are released together and have the same
version. Note that if
we agree we would do the same for xwiki-platform (ie move platform tools in
xwiki-platform).
WDYM? The tools are already there.
8 Apr
8 Apr
11:15 a.m.
New subject: [xwiki-devs] [VOTE] Group commons-pom, commons-tools and commons-core together
On Thu, Apr 7, 2011 at 20:44, Vincent Massol <vincent(a)massol.net> wrote:
On Apr 7, 2011, at 8:38 PM, Sergiu Dumitriu wrote:
Make sense indeed.
On 04/07/2011 08:04 PM, Vincent Massol wrote:
The problem is that you can have nested components so we would need to prefix all current
components with "Core -" and introduce the tool ones with "Tools -" +
the pom one with "Pom -".
I think it's going to be confusing for users and their focus is going to be core
modules mostly, not tools nor top level pom.
What we could do though is log anything related to tools and top level pom in the
existing "Build, Infrastructure and Tests". I like that idea. WDYT?
On Apr 7, 2011, at 7:55 PM, Sergiu Dumitriu wrote:
Sorry, I meant components. On 04/07/2011 07:00 PM, Vincent Massol wrote:
> Hi devs,
>
> The idea is to have the same version and same release for everything related to
commons.
>
> Rationale:
> * Stop the spread of a git repos (see https://github.com/xwiki).
> * Make it even easier to release. Only one command to release the whole
xwiki-commons
> * No need for git modules (svn externals previously)
>
> The proposal is:
>
> xwiki-commons/ (git repo)
> |_ xwiki-commons-pom/
> |_ xwiki-commons-tools/
> |_ xwiki-commons-core/
> |_ pom.xml
>
> Details:
>
> * xwiki-commons/pom.xml contains everything that's currently in
xwiki-commons-pom/pom.xml *except* the parts related to the tools (license and
verification)
> * xwiki-commons/pom.xml has an artifact id of "xwiki-commons"
> * xwiki-commons/xwiki-commons-pom/pom.xml has xwiki-commons/pom.xml as parent and
adds the parts related to the tools (license and verification)
> * xwiki-commons/xwiki-commons-pom/pom.xml has an artifact id of
"xwiki-commons-pom"
> * xwiki-commons/xwiki-commons-tools/pom.xml uses xwiki-commons/pom.xml as parent
> * all other git repos uses "xwiki-commons-pom" as their parent
+1.
> Note that for JIRA we would have 3 jira projects to make it easy for users (because
jira doesn't allow nested components):
> * XWiki Commons POM
> * XWiki Commons Tools
> * XWiki Commons Core
I'm not sure 3 projects are needed. Why not a single XWiki-commons project, with
different submodules? Especially since they are released together and have the same
version.
what is a submodule in jira?
Thanks
-Vincent
I see, I was thinking about the final subdirectory structure, without
thinking of repositories and submodules.
--
Sergiu Dumitriu _______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
> Note that if we agree we would do the same for
xwiki-platform (ie move platform tools in xwiki-platform).
WDYM? The tools are already there.
They're git repos now and not in the xwiki-platform git repo.
4963
days inactive
4964
days old
7 comments
4 participants
participants (4)
-
Denis Gervalle -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol