You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "vijay (JIRA)" <ji...@apache.org> on 2015/07/29 18:14:04 UTC
[jira] [Updated] (MNG-5865) Maven gives successful Build message
and creates empty jar and fails to find compile time issues.
[ https://issues.apache.org/jira/browse/MNG-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vijay updated MNG-5865:
-----------------------
Attachment: CustomAnnotations-0.0.1-SNAPSHOT.zip
AnnotationConsumer.zip
AnnotationConsumer.zip is maven project for which build should have been in Failed status.
CustomAnnotations-0.0.1-SNAPSHOT.zip is zip version of jar file which is empty and does not contain any annotation required by AnnotationConsumer project.
> Maven gives successful Build message and creates empty jar and fails to find compile time issues.
> ---------------------------------------------------------------------------------------------------
>
> Key: MNG-5865
> URL: https://issues.apache.org/jira/browse/MNG-5865
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
> Affects Versions: 3.2.3
> Environment: apache-maven-3.2.3, jdk1.7.0_67, Eclipse Kepler, WIndows7
> Reporter: vijay
> Priority: Minor
> Labels: build, maven
> Fix For: waiting-for-feedback
>
> Attachments: AnnotationConsumer.zip, CustomAnnotations-0.0.1-SNAPSHOT.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)