You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/01/12 18:55:59 UTC
[jira] Created: (JCRSITE-1) Create new project-level Jackrabbit
parent POM
Create new project-level Jackrabbit parent POM
----------------------------------------------
Key: JCRSITE-1
URL: https://issues.apache.org/jira/browse/JCRSITE-1
Project: Jackrabbit Site
Issue Type: Task
Components: parent
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Fix For: parent 2.0
The current {{org.apache.jackrabbit:jackrabbit-parent}} POM contains dependency management and other settings that are related to specific Jackrabbit components. Since we are now moving many components to the new JCR Commons subproject we should have a more generic project-level parent POM that only specifies global configuration like project members, mailing lists, and perhaps some generic settings of the Jackrabbit build environment.
I plan to identify this parent POM as {{org.apache.jackrabbit:parent}} as I'd like to reserve the "jackrabbit-" artifactId prefix for the component that are part of the core Jackrabbit repository build.
I'd like to start the versioning of this parent POM at 2.0 as an upgrade from the jackrabbit-parent 1.x POMs we now have, and create 2.x versions until upgrading to 3.0 for some major change like a TLP reorganization or switch to the next major Maven version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRSITE-1) Create new project-level Jackrabbit
parent POM
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCRSITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663327#action_12663327 ]
Felix Meschberger commented on JCRSITE-1:
-----------------------------------------
Re Parent POM versioning: Since this global parent POM will probably change seldom, we will not need to branch it or otherwise apply fine-grained version control. As such a single increasing number like 2 or 3 would probably do (as is done in other projects, too).
In addition, I suggest we also immediately release this POM, such that our projects may refer to a released version parent pom.
> Create new project-level Jackrabbit parent POM
> ----------------------------------------------
>
> Key: JCRSITE-1
> URL: https://issues.apache.org/jira/browse/JCRSITE-1
> Project: Jackrabbit Site
> Issue Type: Task
> Components: parent
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: parent 2.0
>
>
> The current {{org.apache.jackrabbit:jackrabbit-parent}} POM contains dependency management and other settings that are related to specific Jackrabbit components. Since we are now moving many components to the new JCR Commons subproject we should have a more generic project-level parent POM that only specifies global configuration like project members, mailing lists, and perhaps some generic settings of the Jackrabbit build environment.
> I plan to identify this parent POM as {{org.apache.jackrabbit:parent}} as I'd like to reserve the "jackrabbit-" artifactId prefix for the component that are part of the core Jackrabbit repository build.
> I'd like to start the versioning of this parent POM at 2.0 as an upgrade from the jackrabbit-parent 1.x POMs we now have, and create 2.x versions until upgrading to 3.0 for some major change like a TLP reorganization or switch to the next major Maven version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCRSITE-1) Create new project-level Jackrabbit
parent POM
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCRSITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663338#action_12663338 ]
Jukka Zitting commented on JCRSITE-1:
-------------------------------------
Re: versioning. A single number is fine.
Re: releasing. Agreed. I'm just giving this a bit more time to see how things end up structured in JCR Commons. That shouldn't affect the parent POM, but you never know...
> Create new project-level Jackrabbit parent POM
> ----------------------------------------------
>
> Key: JCRSITE-1
> URL: https://issues.apache.org/jira/browse/JCRSITE-1
> Project: Jackrabbit Site
> Issue Type: Task
> Components: parent
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: parent 2.0
>
>
> The current {{org.apache.jackrabbit:jackrabbit-parent}} POM contains dependency management and other settings that are related to specific Jackrabbit components. Since we are now moving many components to the new JCR Commons subproject we should have a more generic project-level parent POM that only specifies global configuration like project members, mailing lists, and perhaps some generic settings of the Jackrabbit build environment.
> I plan to identify this parent POM as {{org.apache.jackrabbit:parent}} as I'd like to reserve the "jackrabbit-" artifactId prefix for the component that are part of the core Jackrabbit repository build.
> I'd like to start the versioning of this parent POM at 2.0 as an upgrade from the jackrabbit-parent 1.x POMs we now have, and create 2.x versions until upgrading to 3.0 for some major change like a TLP reorganization or switch to the next major Maven version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCRSITE-1) Create new project-level Jackrabbit
parent POM
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCRSITE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCRSITE-1.
---------------------------------
Resolution: Fixed
I think I have the new parent POM in a pretty good shape now in https://svn.apache.org/repos/asf/jackrabbit/parent/trunk/. Resolving as Fixed.
> Create new project-level Jackrabbit parent POM
> ----------------------------------------------
>
> Key: JCRSITE-1
> URL: https://issues.apache.org/jira/browse/JCRSITE-1
> Project: Jackrabbit Site
> Issue Type: Task
> Components: parent
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: parent 2.0
>
>
> The current {{org.apache.jackrabbit:jackrabbit-parent}} POM contains dependency management and other settings that are related to specific Jackrabbit components. Since we are now moving many components to the new JCR Commons subproject we should have a more generic project-level parent POM that only specifies global configuration like project members, mailing lists, and perhaps some generic settings of the Jackrabbit build environment.
> I plan to identify this parent POM as {{org.apache.jackrabbit:parent}} as I'd like to reserve the "jackrabbit-" artifactId prefix for the component that are part of the core Jackrabbit repository build.
> I'd like to start the versioning of this parent POM at 2.0 as an upgrade from the jackrabbit-parent 1.x POMs we now have, and create 2.x versions until upgrading to 3.0 for some major change like a TLP reorganization or switch to the next major Maven version.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.