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 2006/11/29 00:29:27 UTC

[jira] Created: (GERONIMO-2602) default compile scope is overloaded with 2 meanings in PlanProcessorMojo

default compile scope is overloaded with 2 meanings in PlanProcessorMojo
------------------------------------------------------------------------

                 Key: GERONIMO-2602
                 URL: http://issues.apache.org/jira/browse/GERONIMO-2602
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: buildsystem
    Affects Versions: 1.2, 2.0
            Reporter: David Jencks
         Assigned To: David Jencks
             Fix For: 1.2, 2.0


We try to map maven scopes to geronimo ImportTypes.  However the default maven "compile" scope is mapped to two different import types depending on whether it is explicitly specified.  Unfortunately sometimes maven fills in the default for you if it is blank, so this doesn't always work.

I'm changing it so ImportType.SERVICES is not available from the PlanProcessorMojo and 


runtime >> ImportType.CLASSES
compile >> ImportType.ALL



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (GERONIMO-2602) default compile scope is overloaded with 2 meanings in PlanProcessorMojo

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-2602?page=comments#action_12454178 ] 
            
David Jencks commented on GERONIMO-2602:
----------------------------------------

fixed in 1.2 rev 480281

> default compile scope is overloaded with 2 meanings in PlanProcessorMojo
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-2602
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2602
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.2, 2.0
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2, 2.0
>
>
> We try to map maven scopes to geronimo ImportTypes.  However the default maven "compile" scope is mapped to two different import types depending on whether it is explicitly specified.  Unfortunately sometimes maven fills in the default for you if it is blank, so this doesn't always work.
> I'm changing it so ImportType.SERVICES is not available from the PlanProcessorMojo and 
> runtime >> ImportType.CLASSES
> compile >> ImportType.ALL

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (GERONIMO-2602) default compile scope is overloaded with 2 meanings in PlanProcessorMojo

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-2602?page=all ]

David Jencks closed GERONIMO-2602.
----------------------------------

    Resolution: Fixed

fixed in trunk rev 480326.

> default compile scope is overloaded with 2 meanings in PlanProcessorMojo
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-2602
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2602
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.2, 2.0
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: 1.2, 2.0
>
>
> We try to map maven scopes to geronimo ImportTypes.  However the default maven "compile" scope is mapped to two different import types depending on whether it is explicitly specified.  Unfortunately sometimes maven fills in the default for you if it is blank, so this doesn't always work.
> I'm changing it so ImportType.SERVICES is not available from the PlanProcessorMojo and 
> runtime >> ImportType.CLASSES
> compile >> ImportType.ALL

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira