[ 
https://issues.apache.org/jira/browse/MCOMPILER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hervé Boutemy closed MCOMPILER-249.
-----------------------------------
    Resolution: Not A Problem
      Assignee: Hervé Boutemy

I chose "Not A Problem" in the resolution list (I'm not convinced of this 
value, but could not find better alternative)

what is important is to be ok that we can't do anything in 
maven-compiler-plugin if the compiler is at fault

> Maven gives successful Build message and creates empty jar  and fails to find 
>  compile time issues.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-249
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-249
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 3.2, 3.3
>         Environment: apache-maven-3.2.3, jdk1.7.0_67, Eclipse Kepler, WIndows7
>            Reporter: vijay
>            Assignee: Hervé Boutemy
>              Labels: build, maven
>         Attachments: AnnotationConsumer.zip, 
> CustomAnnotations-0.0.1-SNAPSHOT.zip, CustomAnnotations.zip
>
>
> I have created one maven  project "AnnotationConsumer" which uses custom 
> annotation "@COBDate". This custom annotation is present in another maven 
> project "CustomAnnotations". Now the customannotation jar is empty and does 
> not contain any annotations. So ideally build of project "AnnotationConsumer" 
>  should have been failed with error message like COBDate not found or 
> compilation fails. But the thing is that in eclipse Maven  Build run it 
> completes successfully without any error message and creates empty jar file 
> AnnotationConsumer.jar. 
> I tried to build project "AnnotationConsumer" from command prompt also with 
> the same result.
> This looks major issue because build creates empty jar but gives successful 
> build  message, creating confusion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to