felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Bridner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4241) Change default output directory for SCR annotations to ${project.build.directory}/classes
Date Mon, 14 Oct 2013 09:51:41 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794019#comment-13794019

Marc Bridner commented on FELIX-4241:

Can't seem to attach files since the issue is closed, so here's a [link|http://www.bridner.com/test.zip].
Import as existing maven project

The issue shows up as:
Source folder 'src/main/java' in project 'com.something.scr' cannot output to distinct source
folder 'target/classes'

It results from a combination of this change and the way we explicitly trigger the scr-plugin
through the m2e lifecycle management plugin (that we need for other reasons). Changing outputDirectory
or removing the scr-plugin from lifecycle management solves it.

As long as its possible to change the outputDirectory property everything is fine :)

Eclipse Juno, Eclipse Kepler
m2e 1.4.0
Tycho project configurator 0.6.0

> Change default output directory for SCR annotations to ${project.build.directory}/classes
> -----------------------------------------------------------------------------------------
>                 Key: FELIX-4241
>                 URL: https://issues.apache.org/jira/browse/FELIX-4241
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven SCR Plugin
>    Affects Versions: maven-scr-plugin 1.14.0
>            Reporter: Robert Munteanu
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: maven-scr-plugin 1.15.0
>         Attachments: FELIX-4242-1.patch
> Currently the plugin outputs the generated files under ${project.build.directory}/scr-plugin-generated
. This change allows it to place its contents in the same place as the java compiled classes
and the MANIFEST.MF generated by the maven-bundle-plugin. 
> The result is that the exploded bundle contents is placed into a single directory and
can be used by tooling - such as the Sling IDE tools - to incrementally update a bundle running
in an OSGi container without going through a full maven package + deploy cycle.

This message was sent by Atlassian JIRA

View raw message