You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Francisco Olarte (Created) (JIRA)" <ji...@apache.org> on 2011/12/13 18:17:30 UTC

[jira] [Created] (FELIX-3269) maven SCR plugin @Property is not properly parsed.

maven SCR plugin @Property is not properly parsed.
--------------------------------------------------

                 Key: FELIX-3269
                 URL: https://issues.apache.org/jira/browse/FELIX-3269
             Project: Felix
          Issue Type: Bug
          Components: Maven SCR Plugin
    Affects Versions: maven-scr-plugin-1.7.4
         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
            Reporter: Francisco Olarte


When parsing the following property annotations:
-------------
    //
    @Property(value = "127.0.0.1" //
    , label = "Server host" //
    , description = "IP address of host to connect to." //
    )
    final static String HOST = "host";
    // 
    @Property(intValue = 5000 //
    , label = "Yate server port" //
    , description = "Port number to connect to, <=0 to disable this server." //
    )
    final static String PORT = "port";
    //
    @Property(value = "" //
    , label = "Server name" //
    , description = "Name for this server." //
    )
    final static String NAME = "name";
    //
    @Property(value = "ALL" //
    , label = "Server purpose" //
    , description = "What this served is going to be used for, used to filter them." //
    )
-------------

The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:

-------------
    <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
        <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
        <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
        <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
        <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
    </OCD>
------------

Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).



--
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] [Closed] (FELIX-3269) @Property is not properly parsed.

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

Carsten Ziegeler closed FELIX-3269.
-----------------------------------

    Assignee: Carsten Ziegeler
    
> @Property is not properly parsed.
> ---------------------------------
>
>                 Key: FELIX-3269
>                 URL: https://issues.apache.org/jira/browse/FELIX-3269
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.7.4
>         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
>            Reporter: Francisco Olarte
>            Assignee: Carsten Ziegeler
>             Fix For: maven-scr-plugin-1.8.0, scr ant task 1.2.0, scr generator 1.2.0
>
>
> When parsing the following property annotations:
> -------------
>     //
>     @Property(value = "127.0.0.1" //
>     , label = "Server host" //
>     , description = "IP address of host to connect to." //
>     )
>     final static String HOST = "host";
>     // 
>     @Property(intValue = 5000 //
>     , label = "Yate server port" //
>     , description = "Port number to connect to, <=0 to disable this server." //
>     )
>     final static String PORT = "port";
>     //
>     @Property(value = "" //
>     , label = "Server name" //
>     , description = "Name for this server." //
>     )
>     final static String NAME = "name";
>     //
>     @Property(value = "ALL" //
>     , label = "Server purpose" //
>     , description = "What this served is going to be used for, used to filter them." //
>     )
> -------------
> The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:
> -------------
>     <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
>         <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
>         <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
>         <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
>         <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
>     </OCD>
> ------------
> Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (FELIX-3269) @Property is not properly parsed.

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

Carsten Ziegeler updated FELIX-3269:
------------------------------------

    Summary: @Property is not properly parsed.  (was: maven SCR plugin @Property is not properly parsed.)
    
> @Property is not properly parsed.
> ---------------------------------
>
>                 Key: FELIX-3269
>                 URL: https://issues.apache.org/jira/browse/FELIX-3269
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.7.4
>         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
>            Reporter: Francisco Olarte
>             Fix For: maven-scr-plugin-1.8.0, scr ant task 1.2.0, scr generator 1.2.0
>
>
> When parsing the following property annotations:
> -------------
>     //
>     @Property(value = "127.0.0.1" //
>     , label = "Server host" //
>     , description = "IP address of host to connect to." //
>     )
>     final static String HOST = "host";
>     // 
>     @Property(intValue = 5000 //
>     , label = "Yate server port" //
>     , description = "Port number to connect to, <=0 to disable this server." //
>     )
>     final static String PORT = "port";
>     //
>     @Property(value = "" //
>     , label = "Server name" //
>     , description = "Name for this server." //
>     )
>     final static String NAME = "name";
>     //
>     @Property(value = "ALL" //
>     , label = "Server purpose" //
>     , description = "What this served is going to be used for, used to filter them." //
>     )
> -------------
> The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:
> -------------
>     <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
>         <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
>         <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
>         <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
>         <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
>     </OCD>
> ------------
> Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FELIX-3269) maven SCR plugin @Property is not properly parsed.

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

Carsten Ziegeler resolved FELIX-3269.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: maven-scr-plugin-1.8.0

QDox has been removed, so this should be resolved
                
> maven SCR plugin @Property is not properly parsed.
> --------------------------------------------------
>
>                 Key: FELIX-3269
>                 URL: https://issues.apache.org/jira/browse/FELIX-3269
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.7.4
>         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
>            Reporter: Francisco Olarte
>             Fix For: maven-scr-plugin-1.8.0
>
>
> When parsing the following property annotations:
> -------------
>     //
>     @Property(value = "127.0.0.1" //
>     , label = "Server host" //
>     , description = "IP address of host to connect to." //
>     )
>     final static String HOST = "host";
>     // 
>     @Property(intValue = 5000 //
>     , label = "Yate server port" //
>     , description = "Port number to connect to, <=0 to disable this server." //
>     )
>     final static String PORT = "port";
>     //
>     @Property(value = "" //
>     , label = "Server name" //
>     , description = "Name for this server." //
>     )
>     final static String NAME = "name";
>     //
>     @Property(value = "ALL" //
>     , label = "Server purpose" //
>     , description = "What this served is going to be used for, used to filter them." //
>     )
> -------------
> The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:
> -------------
>     <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
>         <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
>         <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
>         <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
>         <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
>     </OCD>
> ------------
> Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FELIX-3269) maven SCR plugin @Property is not properly parsed.

Posted by "Carsten Ziegeler (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169200#comment-13169200 ] 

Carsten Ziegeler commented on FELIX-3269:
-----------------------------------------

Yes, we use qdox for parsing the source which really has it's limitations - If you write all attributes in a single source code line it should work

We can't pick up the annotations from the class file as they are not contained :) As Felix pointed out with FELIX-3247 this will be solved and we wont use QDox anymore. Hopefully all these problems are fixed by then
Otherwise we would need to fix bugs in qdox which might not be that easy
                
> maven SCR plugin @Property is not properly parsed.
> --------------------------------------------------
>
>                 Key: FELIX-3269
>                 URL: https://issues.apache.org/jira/browse/FELIX-3269
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.7.4
>         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
>            Reporter: Francisco Olarte
>
> When parsing the following property annotations:
> -------------
>     //
>     @Property(value = "127.0.0.1" //
>     , label = "Server host" //
>     , description = "IP address of host to connect to." //
>     )
>     final static String HOST = "host";
>     // 
>     @Property(intValue = 5000 //
>     , label = "Yate server port" //
>     , description = "Port number to connect to, <=0 to disable this server." //
>     )
>     final static String PORT = "port";
>     //
>     @Property(value = "" //
>     , label = "Server name" //
>     , description = "Name for this server." //
>     )
>     final static String NAME = "name";
>     //
>     @Property(value = "ALL" //
>     , label = "Server purpose" //
>     , description = "What this served is going to be used for, used to filter them." //
>     )
> -------------
> The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:
> -------------
>     <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
>         <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
>         <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
>         <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
>         <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
>     </OCD>
> ------------
> Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).

--
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] (FELIX-3269) maven SCR plugin @Property is not properly parsed.

Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169144#comment-13169144 ] 

Felix Meschberger commented on FELIX-3269:
------------------------------------------

Thanks for your report.

I would assume that this issue should be "solving itself" with FELIX-3247.
                
> maven SCR plugin @Property is not properly parsed.
> --------------------------------------------------
>
>                 Key: FELIX-3269
>                 URL: https://issues.apache.org/jira/browse/FELIX-3269
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.7.4
>         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
>            Reporter: Francisco Olarte
>
> When parsing the following property annotations:
> -------------
>     //
>     @Property(value = "127.0.0.1" //
>     , label = "Server host" //
>     , description = "IP address of host to connect to." //
>     )
>     final static String HOST = "host";
>     // 
>     @Property(intValue = 5000 //
>     , label = "Yate server port" //
>     , description = "Port number to connect to, <=0 to disable this server." //
>     )
>     final static String PORT = "port";
>     //
>     @Property(value = "" //
>     , label = "Server name" //
>     , description = "Name for this server." //
>     )
>     final static String NAME = "name";
>     //
>     @Property(value = "ALL" //
>     , label = "Server purpose" //
>     , description = "What this served is going to be used for, used to filter them." //
>     )
> -------------
> The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:
> -------------
>     <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
>         <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
>         <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
>         <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
>         <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
>     </OCD>
> ------------
> Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).

--
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] (FELIX-3269) maven SCR plugin @Property is not properly parsed.

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

Carsten Ziegeler updated FELIX-3269:
------------------------------------

    Fix Version/s: scr ant task 1.2.0
                   scr generator 1.2.0
    
> maven SCR plugin @Property is not properly parsed.
> --------------------------------------------------
>
>                 Key: FELIX-3269
>                 URL: https://issues.apache.org/jira/browse/FELIX-3269
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.7.4
>         Environment: Ubuntu linux 11.10, amd64, Java 1.6 - seems to be a parser issue.
>            Reporter: Francisco Olarte
>             Fix For: maven-scr-plugin-1.8.0, scr ant task 1.2.0, scr generator 1.2.0
>
>
> When parsing the following property annotations:
> -------------
>     //
>     @Property(value = "127.0.0.1" //
>     , label = "Server host" //
>     , description = "IP address of host to connect to." //
>     )
>     final static String HOST = "host";
>     // 
>     @Property(intValue = 5000 //
>     , label = "Yate server port" //
>     , description = "Port number to connect to, <=0 to disable this server." //
>     )
>     final static String PORT = "port";
>     //
>     @Property(value = "" //
>     , label = "Server name" //
>     , description = "Name for this server." //
>     )
>     final static String NAME = "name";
>     //
>     @Property(value = "ALL" //
>     , label = "Server purpose" //
>     , description = "What this served is going to be used for, used to filter them." //
>     )
> -------------
> The metatype.xml is incorrectly generated ( extra chars from the source picked up into attribut name of AD element for port:
> -------------
>     <OCD id="com.peoplecall.yate.server" name="Configuracion de socket" description="Conexiones a los servidores de yate.">
>         <AD id="host" type="String" default="127.0.0.1" name="Server host" description="IP address of host to connect to."/>
>         <AD id="port" type="Integer" default="5000" name="/&#10;       &quot;Yate server port" description="Port number to connect to, &lt;=0 to disable this server."/>
>         <AD id="name" type="String" default="" name="Server name" description="Name for this server."/>
>         <AD id="purpose" type="String" default="ALL" name="Server purpose" description="What this served is going to be used for, used to filter them."/>
>     </OCD>
> ------------
> Notice it only happens in the non-string property, even if I use the same comment pattern as the others. I think this is related to a previously reported ( by me ) bug: https://issues.apache.org/jira/browse/FELIX-3234 and due to the SCR plugin reparsing the source code ( I suppose there is a reason for not going to the .class file to pick up annotations ).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira