Be more lenient of missing source directories

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by [email protected] on 27 Jun 2011 at 12:55

[GoogleCodeExporter]

i agree with you

i'll work on

thx for feedback

Original comment by [email protected] on 27 Jun 2011 at 2:09

• Changed state: Accepted

[GoogleCodeExporter]

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

Original comment by [email protected] on 28 Jun 2011 at 8:13

• Changed state: Duplicate

[GoogleCodeExporter]

But not released et? I'm on 2.0.2

Original comment by [email protected] on 28 Jun 2011 at 1:44

[GoogleCodeExporter]

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

Original comment by [email protected] on 28 Jun 2011 at 1:59

• Changed state: Started

[GoogleCodeExporter]

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

Original comment by [email protected] on 28 Jun 2011 at 2:14

[GoogleCodeExporter]

deployed in 2.0.3 official release

Original comment by [email protected] on 6 Jul 2011 at 10:42

• Changed state: Fixed

[GoogleCodeExporter]

Is the sync to central delayed?

Original comment by [email protected] on 6 Jul 2011 at 11:44

[GoogleCodeExporter]

i think so ... i'm investigating

Original comment by [email protected] on 6 Jul 2011 at 11:51

[GoogleCodeExporter]

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/annomoj
o/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/annomoj
o/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/annomoj
o/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.

Original comment by [email protected] on 7 Jul 2011 at 2:13

[GoogleCodeExporter]

hi, i understand your need

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

i'll evaluate a backport

Original comment by [email protected] on 7 Jul 2011 at 3:15

[GoogleCodeExporter]

The best would be if jfrog synced to central.

Original comment by [email protected] on 7 Jul 2011 at 4:33

[GoogleCodeExporter]

ABSOLUTELY AGREE

I'LL TRY TO DO A FOLLOW UP TO JFROG

Original comment by [email protected] on 8 Jul 2011 at 7:32