If src/main/java doesn't exist the plugin will fail. Can this be relaxed so that the plugin can be declared as a top-level plugin, but won't fail when the directory is missing.

Printing a warning should suffice - or make it configurable.

i agree with you

i'll work on

thx for feedback

after further investigation i've seen that the problem has been already handled

see http://code.google.com/p/maven-annotation-plugin/issues/detail?id=25

But not released et? I'm on 2.0.2

sorry i've check again ....

the Issue 25 refers to "no source files exist" and not "no source folder exist"

i'll fix it soon

Thx for feedback

i've deployed a release 2.0.3-SNAPSHOT in SONATYPE repository http://oss.sonatype.org/content/repositories/snapshots

Please try it and send me feedback ... so i can arrange a new stable release

thx

deployed in 2.0.3 official release

Is the sync to central delayed?

i think so ... i'm investigating

I noticed that the latest release depend on a jfrog artifact which doesn't exist in central - only in their repo: ownloading: http://repo.jfrog.org/artifactory/plugins-releases-local/org/jfrog/maven/annomojo/maven-plugin-tools-anno/1.4.0/maven-plugin-tools-anno-1.4.0.pom 3K downloaded (maven-plugin-tools-anno-1.4.0.pom) Downloading: http://repo.jfrog.org/artifactory/plugins-releases-local/org/jfrog/maven/annomojo/maven-plugin-anno-parent/1.4.0/maven-plugin-anno-parent-1.4.0.pom 7K downloaded (maven-plugin-anno-parent-1.4.0.pom) Downloading: http://repo.jfrog.org/artifactory/plugins-releases-local/org/jfrog/maven/annomojo/maven-plugin-anno/1.4.0/maven-plugin-anno-1.4.0.pom

Do you know if that artifact will be distributed to central? I try to limit the number of repos to depend on.

hi, i understand your need

i've seen that the release 1.3.1 is deployed in public repo

i'll evaluate a backport

The best would be if jfrog synced to central.

ABSOLUTELY AGREE

I'LL TRY TO DO A FOLLOW UP TO JFROG