You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Matthew T. Adams (Created) (JIRA)" <ji...@apache.org> on 2012/03/08 05:35:01 UTC
[jira] [Created] (JDO-708) Create JIRA "component" entry for
exectck & parent-pom modules
Create JIRA "component" entry for exectck & parent-pom modules
--------------------------------------------------------------
Key: JDO-708
URL: https://issues.apache.org/jira/browse/JDO-708
Project: JDO
Issue Type: Task
Affects Versions: JDO 3 maintenance release 1 (3.1)
Reporter: Matthew T. Adams
Fix For: JDO 3 maintenance release 1 (3.1)
The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too.
--
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] (JDO-708) Create JIRA "component" entry for
exectck & parent-pom modules
Posted by "Michelle Caisse (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226250#comment-13226250 ]
Michelle Caisse commented on JDO-708:
-------------------------------------
Wondering what the benefit is of this change over the existing setup?
> Create JIRA "component" entry for exectck & parent-pom modules
> --------------------------------------------------------------
>
> Key: JDO-708
> URL: https://issues.apache.org/jira/browse/JDO-708
> Project: JDO
> Issue Type: Task
> Components: site and infrastructure
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Matthew T. Adams
> Fix For: JDO 3 maintenance release 1 (3.1)
>
>
> The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too.
--
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] [Resolved] (JDO-708) Create JIRA "component" entry for
exectck & parent-pom modules
Posted by "Michael Bouschen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen resolved JDO-708.
----------------------------------
Resolution: Won't Fix
> Create JIRA "component" entry for exectck & parent-pom modules
> --------------------------------------------------------------
>
> Key: JDO-708
> URL: https://issues.apache.org/jira/browse/JDO-708
> Project: JDO
> Issue Type: Task
> Components: site and infrastructure
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Matthew T. Adams
> Fix For: JDO 3 maintenance release 1 (3.1)
>
>
> The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too.
--
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] (JDO-708) Create JIRA "component" entry for
exectck & parent-pom modules
Posted by "Michael Bouschen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-708:
---------------------------------
Component/s: site and infrastructure
> Create JIRA "component" entry for exectck & parent-pom modules
> --------------------------------------------------------------
>
> Key: JDO-708
> URL: https://issues.apache.org/jira/browse/JDO-708
> Project: JDO
> Issue Type: Task
> Components: site and infrastructure
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Matthew T. Adams
> Fix For: JDO 3 maintenance release 1 (3.1)
>
>
> The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too.
--
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] (JDO-708) Create JIRA "component" entry for
exectck & parent-pom modules
Posted by "Craig L Russell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226256#comment-13226256 ]
Craig L Russell commented on JDO-708:
-------------------------------------
It's not obvious to me that exectck needs a different JIRA component. The exectck is the execution mechanism for tck so to me they are both logically the same component although they have different physical packaging.
> Create JIRA "component" entry for exectck & parent-pom modules
> --------------------------------------------------------------
>
> Key: JDO-708
> URL: https://issues.apache.org/jira/browse/JDO-708
> Project: JDO
> Issue Type: Task
> Components: site and infrastructure
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Matthew T. Adams
> Fix For: JDO 3 maintenance release 1 (3.1)
>
>
> The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too.
--
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] (JDO-708) Create JIRA "component" entry for
exectck & parent-pom modules
Posted by "Michelle Caisse (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michelle Caisse updated JDO-708:
--------------------------------
Comment: was deleted
(was: Wondering what the benefit is of this change over the existing setup?)
> Create JIRA "component" entry for exectck & parent-pom modules
> --------------------------------------------------------------
>
> Key: JDO-708
> URL: https://issues.apache.org/jira/browse/JDO-708
> Project: JDO
> Issue Type: Task
> Components: site and infrastructure
> Affects Versions: JDO 3 maintenance release 1 (3.1)
> Reporter: Matthew T. Adams
> Fix For: JDO 3 maintenance release 1 (3.1)
>
>
> The exectck doesn't have a JIRA component entry, so it cannot be identified as a component when entering an issue. If the parent-pom module that is created as part of JDO-707 is accepted, then we also need to create a JIRA component for that, too.
--
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