Be more lenient of missing source directories

velo / maven-annotation-plugin

Automatically exported from code.google.com/p/maven-annotation-plugin

0 stars 0 forks source link

Be more lenient of missing source directories #30

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

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 davidkar...@gmail.com on 27 Jun 2011 at 12:55

GoogleCodeExporter commented 9 years ago

i agree with you

i'll work on

thx for feedback

Original comment by bartolom...@gmail.com on 27 Jun 2011 at 2:09

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

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 bartolom...@gmail.com on 28 Jun 2011 at 8:13

Changed state: Duplicate

GoogleCodeExporter commented 9 years ago

But not released et? I'm on 2.0.2

Original comment by davidkar...@gmail.com on 28 Jun 2011 at 1:44

GoogleCodeExporter commented 9 years ago

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 bartolom...@gmail.com on 28 Jun 2011 at 1:59

Changed state: Started

GoogleCodeExporter commented 9 years ago

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 bartolom...@gmail.com on 28 Jun 2011 at 2:14

GoogleCodeExporter commented 9 years ago

deployed in 2.0.3 official release

Original comment by bartolom...@gmail.com on 6 Jul 2011 at 10:42

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

Is the sync to central delayed?

Original comment by davidkar...@gmail.com on 6 Jul 2011 at 11:44

GoogleCodeExporter commented 9 years ago

i think so ... i'm investigating

Original comment by bartolom...@gmail.com on 6 Jul 2011 at 11:51

GoogleCodeExporter commented 9 years ago

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 davidkar...@gmail.com on 7 Jul 2011 at 2:13

GoogleCodeExporter commented 9 years ago

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 bartolom...@gmail.com on 7 Jul 2011 at 3:15

GoogleCodeExporter commented 9 years ago

The best would be if jfrog synced to central.

Original comment by davidkar...@gmail.com on 7 Jul 2011 at 4:33

GoogleCodeExporter commented 9 years ago

ABSOLUTELY AGREE

I'LL TRY TO DO A FOLLOW UP TO JFROG

Original comment by bartolom...@gmail.com on 8 Jul 2011 at 7:32