felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-509) Add support for explicit source directory include/exclude via plugin configuration
Date Tue, 11 Mar 2008 07:08:46 GMT

     [ https://issues.apache.org/jira/browse/FELIX-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carsten Ziegeler updated FELIX-509:
-----------------------------------

    Affects Version/s: maven-scr-plugin-1.0.3
                       maven-scr-plugin-1.0.2
                       maven-scr-plugin-1.0.1
        Fix Version/s:     (was: felix-1.0.4)
                       maven-scr-plugin-1.0.4

> Add support for explicit source directory include/exclude via plugin configuration
> ----------------------------------------------------------------------------------
>
>                 Key: FELIX-509
>                 URL: https://issues.apache.org/jira/browse/FELIX-509
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin-1.0.1, maven-scr-plugin-1.0.2, maven-scr-plugin-1.0.3
>            Reporter: Rodrigo Madera
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: maven-scr-plugin-1.0.4
>
>
> As discussed on the Felix Users mailing list regarding a problem with a third-party component
(non relevant but QDox in that specific case), there was a clear indication that having the
ability to control which directories are processed by the Maven SCR Plugin would be helpful.
> This feature would allow things like:
> 	<configuration>
> 		<exclude>target/generated-sources</exclude>
> 	</configuration>
> Current Implementation:
> The JavaClassDescriptorManager constructor gets all source directories from MavenProject.getCompileSourceRoots().
The exclusion should be coded here consulting the plugin configuration block.
> Since the plugin is currently "include all exclude explicit" there may be no purpose
in actually having an include directive, unless it would support sub-tree checking, which
would complicate things quite a bit (as in exclude target/foo but include target/foo/bar).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message