[
https://jira.codehaus.org/browse/MSANDBOX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSANDBOX-43.
----------------------------------
Resolution: Won't Fix
outdated project, closing as won't fix.
> Annotation proccessing tool plugin introduction
> ------------------------------------------------
>
> Key: MSANDBOX-43
> URL: https://jira.codehaus.org/browse/MSANDBOX-43
> Project: Maven Sandbox (retired)
> Issue Type: New Feature
> Reporter: Juraj Burian
> Priority: Minor
> Attachments: maven-apt-plugin.zip
>
>
> Hi,
> I have first working and (partially) tested prototype of Apt plugin. (see
> attachment)
> Behavior:
> - plugin is associated with phase:generate-sources.
> - src/main/gen directory is the default value for generated sources. (created
> if it's missing) config entry: <generated> .... </generated>
> - src/test/gen directory is the default value for generated test sources.
> config entry: <testDenerated> .... </testGenerated>
> - all switches are supported except -factorypath (any suggestion how to do
> it?) see copy of my yesterday mail (see bellow).
> - during execution new compile source root is introduced :
> project.addCompileSourceRoot( getGenerated() );
> and new resource is introduced too:
> Resource resource = new Resource();
> resource.setDirectory( getGenerated() );
> resource.addExclude( "**/*.java" );
> project.addResource( resource );
> I hope that it's useful for you :-) .
> Best regards & have nice day
> JuBu
> Yesterday mail:
> Hi,
> We are working on jboss-aop & APT plugins implementation.
> We encountered the folowing problem (in general):
> We need to split classpath into several parts. In other words, we need to
> group dependencies.
> For example, when running JBoss AOP it is necessary to supply classpath where
> aspects are found and a different classpath where classes that should be
> weaved are (ie. 2 different classpath).
> We can see 2 possible solutions:
> 1) Adding properties to dependency (as in Maven1). That could be used to
> distinguish between different dependency groups.
> 2) Adding group attribute to <depencies> xml tag and allowing to have more
> than one <dependencies> sections. group attribute would be propagated to
> individual dependency objects.
> 3) any other idea?
> In our opinion this "dependency grouping" may be required in many plugins
> (JBoss AOP, AspectJ, APT, ...).
> Best regards,
> JUBU
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
