Ok, I created FELIX-3794 [1] to track this enhancement. Thanks and Regards Felix
[1] https://issues.apache.org/jira/browse/FELIX-3794 Am 30.11.2012 um 15:04 schrieb Carsten Ziegeler: > This is configurable, either one file or separate ones where separate > is now the default. > > Yes, we could do that - right now all files get the highest used > version within the bundle. > > Carsten > > 2012/11/30 Felix Meschberger <[email protected]>: >> Hi, >> >> Just wondering in this context: Do we write one descriptor file per >> component ? >> >> If so, we could easily have the appropriate version applied on a >> per-component level. >> >> Regards >> Felix >> >> Am 30.11.2012 um 12:29 schrieb Carsten Ziegeler (JIRA): >> >>> >>> [ >>> https://issues.apache.org/jira/browse/FELIX-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >>> ] >>> >>> Carsten Ziegeler updated FELIX-3788: >>> ------------------------------------ >>> >>> Summary: specVersion incorrectly determined, depends on class order >>> (was: [SCR MAVEN] specVersion incorrectly determined, depends on class >>> order) >>> >>>> specVersion incorrectly determined, depends on class order >>>> ---------------------------------------------------------- >>>> >>>> Key: FELIX-3788 >>>> URL: https://issues.apache.org/jira/browse/FELIX-3788 >>>> Project: Felix >>>> Issue Type: Bug >>>> Components: Maven SCR Plugin >>>> Affects Versions: maven-scr-plugin-1.8.0 >>>> Environment: Linux 3.5.0-18-generic (Ubuntu 12.10) x64, Oracle Java >>>> 1.6.0_31, Apache Maven 3.0.4 (r1232337) >>>> Reporter: Felix Oghină >>>> Assignee: Carsten Ziegeler >>>> Fix For: maven-scr-plugin-1.8.2, scr ant task 1.2.2, scr >>>> generator 1.2.2 >>>> >>>> >>>> When running the generate-scr-scrdescriptor goal the scr-plugin will not >>>> properly detect what specVersion to use. I have not explicitly specified >>>> the specVersion to use (either in pom.xml or in the @Component annotation) >>>> and yet it tries to use version 1.1, because the first class that it finds >>>> is compatible with it. However, the next classes use 1.2 features (e.g. >>>> ReferencePolicyOption.GREEDY), so the build fails. >>>> This becomes quite the heisenbug when the build works for some users (e.g. >>>> Jenkins), but doesn't for others, because the order in which it processes >>>> classes is different. >>> >>> -- >>> This message is automatically generated by JIRA. >>> If you think it was sent incorrectly, please contact your JIRA >>> administrators >>> For more information on JIRA, see: http://www.atlassian.com/software/jira >> > > > > -- > Carsten Ziegeler > [email protected]
