[ 
https://issues.apache.org/jira/browse/FELIX-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281521#comment-13281521
 ] 

Carsten Ziegeler commented on FELIX-3519:
-----------------------------------------

Ah ok, thanks for the update!

Actually its a warning by intention to be compatible. Imagine you're writing a 
component for 1.0 of the spec but for some reason have an activate() method 
which is not intended to be called by SCR (and won't be called because of the 
1.0 compliance). In this case, an error would break the build and you would 
have no chance to get the build running other than renaming this method - which 
might not be possible for some reason.
                
> [SCR ANT] A activator method without parameters issue a warning and failes 
> the build
> ------------------------------------------------------------------------------------
>
>                 Key: FELIX-3519
>                 URL: https://issues.apache.org/jira/browse/FELIX-3519
>             Project: Felix
>          Issue Type: Bug
>          Components: SCR Annotations
>    Affects Versions: scr generator 1.1.4
>            Reporter: Daniel Kuffner
>              Labels: annotation, generate, scr, task
>
> The ANT SCR task will produce a warning in case the Component has 
> paramterless activate method like:
> public void activate() { ... }
> This problem can be fixed by adding a @Activate annnotation to the method.
> However it seems to be a bug that 
> 1. the problem will issue only a warning but breaks the build
> 2. I thought "activate()" is a valid signature.
> I propose either to issue the problem as an error (to make obviouse what 
> actually broke the build) or to let this warning not break the build.
> Here is my Task execution:
>  <scr srcdir="src/main/java" destdir="target/java" 
> classpathref="scr-classpath"
>            parseJavadoc="false" strictMode="false"
> generateAccessors="false" specVersion="1.1"/>

--
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

        

Reply via email to