[
https://issues.apache.org/jira/browse/MNG-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697294#comment-14697294
]
Hervé Boutemy commented on MNG-5865:
------------------------------------
I can't reproduce your test case: {{[ERROR] Failed to execute goal on project
AnnotationConsumer: Could not resolve dependencies for project
com.vijay:AnnotationConsumer:jar:0.0.1-SNAPSHOT: Could not find artifact
com.vijay:CustomAnnotations:jar:0.0.1-SNAPSHOT}}
but IIUC, the Maven builds does what expected when run on command-line, isn't
it?
but the unexpected behaviour happens only when Maven is invoker through m2e?
Can you check configuration of the run in m2e? there are features in m2e for
artifacts resolution from Eclipse workspace that could cause you such issue
> 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
> 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)
