You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "marijan milicevic (Created) (JIRA)" <ji...@apache.org> on 2012/03/05 15:39:57 UTC
[jira] [Created] (RAVE-503) Move rave parent into rave trunk
Move rave parent into rave trunk
---------------------------------
Key: RAVE-503
URL: https://issues.apache.org/jira/browse/RAVE-503
Project: Rave
Issue Type: Improvement
Reporter: marijan milicevic
Priority: Minor
Now that Rave has a git mirror, svn still needs to be used to checkout parent project. Please see suggestion Jukka Zitting posted in following issue:
https://issues.apache.org/jira/browse/INFRA-4123
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-503) Move rave parent into rave trunk
Posted by "Ate Douma (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222386#comment-13222386 ]
Ate Douma commented on RAVE-503:
--------------------------------
Actually, I'm -1 on this.
The 'problem' of having to checkout the parent project should be mostly not existent IMO.
The parent pom should be regarded as a 'TLP' level pom, e.g. defining the standards and common requirements for the whole of Apache Rave.
When we move to TLP releasing the parent pom also becomes easier/quicker.
In general the rave-project, as well as future other independent child modules with their own life-cycle (trunk/tag/branches) should only need to rely on a *released* parent pom.
Right now we still only have rave-project as a child of the rave-parent pom, but I expect this will change in the future. Merging now the parent pom in rave-project would means we'll have to revert that back later again.
BTW: while the suggestion from Jukka (INFRA-4123) might make sense for TIKA, for instance Jackrabbit (and plenty other projects) also uses its own and standalone parent pom module.
> Move rave parent into rave trunk
> ---------------------------------
>
> Key: RAVE-503
> URL: https://issues.apache.org/jira/browse/RAVE-503
> Project: Rave
> Issue Type: Improvement
> Reporter: marijan milicevic
> Priority: Minor
>
> Now that Rave has a git mirror, svn still needs to be used to checkout parent project. Please see suggestion Jukka Zitting posted in following issue:
> https://issues.apache.org/jira/browse/INFRA-4123
> Also, git mirror (https://github.com/apache/rave) should be mentioned on Rave site
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (RAVE-503) Move rave parent into rave trunk
Posted by "marijan milicevic (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
marijan milicevic updated RAVE-503:
-----------------------------------
Description:
Now that Rave has a git mirror, svn still needs to be used to checkout parent project. Please see suggestion Jukka Zitting posted in following issue:
https://issues.apache.org/jira/browse/INFRA-4123
Also, git mirror (https://github.com/apache/rave) should be mentioned on Rave site
was:
Now that Rave has a git mirror, svn still needs to be used to checkout parent project. Please see suggestion Jukka Zitting posted in following issue:
https://issues.apache.org/jira/browse/INFRA-4123
> Move rave parent into rave trunk
> ---------------------------------
>
> Key: RAVE-503
> URL: https://issues.apache.org/jira/browse/RAVE-503
> Project: Rave
> Issue Type: Improvement
> Reporter: marijan milicevic
> Priority: Minor
>
> Now that Rave has a git mirror, svn still needs to be used to checkout parent project. Please see suggestion Jukka Zitting posted in following issue:
> https://issues.apache.org/jira/browse/INFRA-4123
> Also, git mirror (https://github.com/apache/rave) should be mentioned on Rave site
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (RAVE-503) Move rave parent into rave trunk
Posted by "marijan milicevic (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222433#comment-13222433 ]
marijan milicevic commented on RAVE-503:
----------------------------------------
sounds like a good enough reason to keep it as it is
> Move rave parent into rave trunk
> ---------------------------------
>
> Key: RAVE-503
> URL: https://issues.apache.org/jira/browse/RAVE-503
> Project: Rave
> Issue Type: Improvement
> Reporter: marijan milicevic
> Priority: Minor
>
> Now that Rave has a git mirror, svn still needs to be used to checkout parent project. Please see suggestion Jukka Zitting posted in following issue:
> https://issues.apache.org/jira/browse/INFRA-4123
> Also, git mirror (https://github.com/apache/rave) should be mentioned on Rave site
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira