search

cloudtrends / maven-annotation-plugin

Automatically exported from code.google.com/p/maven-annotation-plugin
0 stars 0 forks source link

Add support for specifying includes/excludes to limit input sources to which annotation processing should be applied #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
2.0.0

Please provide any additional information below.

Original issue reported on code.google.com by ssla...@gmail.com on 22 Feb 2011 at 12:45

GoogleCodeExporter commented 9 years ago 
Hi 

great suggestion .... i'll plan this feature for next iteraction

Original comment by bartolom...@gmail.com on 22 Feb 2011 at 9:05

GoogleCodeExporter commented 9 years ago 
i've added 2 new configuration properties

<includes><!-- includes pattern , comma separated : default **/*.java-->
<excludes><!-- excludes pattern, comma separated

i've deployed a new 2.0.1-SNAPSHOT release ... could you test and confirm that 
works?

Original comment by bartolom...@gmail.com on 22 Feb 2011 at 7:35

GoogleCodeExporter commented 9 years ago 
Wow, that was quick. Tried includes filtering, it works (unlike same use case 
but with maven compiler plugin and eclipse which has issues [1]). Thanks! 
Although that configuration is a bit different compared to similar 
configurations of core maven plugins - typically includes would allow multiple 
include nested elements; excludes would allow multiple exclude nested elements. 
Not sure what is better.

[1] issue with maven-compiler-plugin and maven eclipse integration
https://bugs.eclipse.org/bugs/show_bug.cgi?id=335036#c1

Original comment by ssla...@gmail.com on 22 Feb 2011 at 11:33

GoogleCodeExporter commented 9 years ago 
as you say ... follow the standard should be better

i'll update configuration soon

Original comment by bartolom...@gmail.com on 23 Feb 2011 at 8:47

GoogleCodeExporter commented 9 years ago 
i've updated configuration using standard includes/excludes approach.  

No you can use :
<includes>
  <include></include>
  <include></include>  
</includes>

<excludes>
  <exclude></exclude>
  <exclude></exclude>
</excludes>

i've deployed a new 2.0.1-SNAPSHOT release ... could you test and confirm that 
works?

Thx in advance

Original comment by bartolom...@gmail.com on 24 Feb 2011 at 10:57

GoogleCodeExporter commented 9 years ago 
Works for me!

Regards,
Stevo.

Original comment by ssla...@gmail.com on 25 Feb 2011 at 12:09

GoogleCodeExporter commented 9 years ago 
thx

i've deployed the official release 2.0.1 with this feature

thx again for interest

Regards,
Bartolo

Original comment by bartolom...@gmail.com on 25 Feb 2011 at 8:03