You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/01/11 07:09:34 UTC

[jira] Created: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

subprojects should use file system parent poms as parent poms in general
------------------------------------------------------------------------

                 Key: GERONIMO-3747
                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: buildsystem
    Affects Versions: 2.1
            Reporter: David Jencks
             Fix For: 2.1


After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon closed GERONIMO-3747.
----------------------------------

    Resolution: Fixed

Module parentage has been updated so that the module's parent is ../pom.xml.  All bits under {{framework/\*}} are now in the {{org.apache.geronimo.framework}} groupId.  Other bits under {{plugins/\*}} are still using {{org.apache.geronimo.modules}} and {{org.apache.geronimo.configs}}, which should be changed, but can wait until 2.2.

In addition the {{components/\*}} and {{applications/\*}} modules have been relocated under {{plugins}}.

> subprojects should use file system parent poms as parent poms in general
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-3747
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.1
>            Reporter: David Jencks
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated GERONIMO-3747:
-----------------------------------

    Attachment: GERONIMO-3747-step-1.diff.zip

> subprojects should use file system parent poms as parent poms in general
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-3747
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.1
>            Reporter: David Jencks
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561261#action_12561261 ] 

David Jencks commented on GERONIMO-3747:
----------------------------------------

This patch appears to work perfectly for me...  I got far into the testsuite before getting bored and shutting it off.

> subprojects should use file system parent poms as parent poms in general
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-3747
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.1
>            Reporter: David Jencks
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated GERONIMO-3747:
-----------------------------------

    Attachment: GERONIMO-3747-step-1.diff.zip

> subprojects should use file system parent poms as parent poms in general
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-3747
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.1
>            Reporter: David Jencks
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated GERONIMO-3747:
-----------------------------------

    Attachment: GERONIMO-3747-step-1.diff.zip

> subprojects should use file system parent poms as parent poms in general
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-3747
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.1
>            Reporter: David Jencks
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>         Attachments: GERONIMO-3747-step-1.diff.zip, GERONIMO-3747-step-1.diff.zip
>
>
> After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (GERONIMO-3747) subprojects should use file system parent poms as parent poms in general

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon reassigned GERONIMO-3747:
--------------------------------------

    Assignee: Jason Dillon

> subprojects should use file system parent poms as parent poms in general
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-3747
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3747
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 2.1
>            Reporter: David Jencks
>            Assignee: Jason Dillon
>             Fix For: 2.1
>
>
> After the move of most stuff into plugins, the parent pom is usually still o.a.g.modules/modules or o.a.g.configs/configs.  I think this is a really bad idea.  I think the main thing that needs to be changed is to move the car plugin setup code into the root pom.  However I'm not sure if this is possible.... bit of a chicken/egg situation?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.