[jira] [Updated] (FELIX-3750) relativePath is ignored

["Hayo (JIRA)" <ji...@apache.org>]

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

Hayo updated FELIX-3750:
------------------------

    Description: 
A relative path to parent project is ignored. 

Snippet from child project:

<project..
   	<parent>
		<groupId>kn.acon</groupId>
		<artifactId>CONFIGURATION</artifactId>
		<version>3.0.</version>
		<relativePath>../CONFIGURATION/pom.xml</relativePath>
	</parent>
	<packaging>bundle</packaging>
	<artifactId>CONFIGURATION_INTTEST</artifactId>
	<name>${project.artifactId}</name>

Snippet from parent aggregator project:
...
	<packaging>pom</packaging>
	<artifactId>CONFIGURATION</artifactId>
	<name>${project.artifactId}</name>
    <modules>
        <module>../CONFIGURATION_INTTEST</module>
    </modules>
...
    <build>
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>org.apache.felix</groupId>
                    <artifactId>maven-bundle-plugin</artifactId>
                    <version>2.3.7</version>
...
The effect is that the project cannot be initially compiled, because the child project cannot look up the plugin version in parent project. Workaround: comment out <modules> section, mvn install, comment in.
Also, any change in parent project needs two compile cycles to become effective.

To get the child project compiling again, it is sufficient to remove the maven-bundle-plugin <plugin> section. Changing <packaging> to jar alone does not help here.

  was:
A relative path to parent project is ignored. 

Snippet from child project:

<project..
   	<parent>
		<groupId>kn.acon</groupId>
		<artifactId>CONFIGURATION</artifactId>
		<version>3.0.</version>
		<relativePath>../CONFIGURATION/pom.xml</relativePath>
	</parent>
	<packaging>bundle</packaging>
	<artifactId>CONFIGURATION_INTTEST</artifactId>
	<name>${project.artifactId}</name>

Snippet from parent aggregator project:
...
	<packaging>pom</packaging>
	<artifactId>CONFIGURATION</artifactId>
	<name>${project.artifactId}</name>
    <modules>
        <module>../CONFIGURATION_INTTEST</module>
    </modules>
...
    <build>
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>org.apache.felix</groupId>
                    <artifactId>maven-bundle-plugin</artifactId>
                    <version>2.3.7</version>
...
The effect is that the project cannot be initially compiled, because the child project cannot look up the plugin version in parent project. Workaround: comment out <modules> section, mvn install, comment in.
Also, any change in parent project needs two compile cycles to become effective.

    
> relativePath is ignored
> -----------------------
>
>                 Key: FELIX-3750
>                 URL: https://issues.apache.org/jira/browse/FELIX-3750
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.3.7
>         Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: C:\Java\apache-maven-3.0.4
> Java version: 1.6.0_33, vendor: Sun Microsystems Inc.
> Java home: C:\Java\jdk1.6.0_33\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>            Reporter: Hayo
>              Labels: maven
>
> A relative path to parent project is ignored. 
> Snippet from child project:
> <project..
>    	<parent>
> 		<groupId>kn.acon</groupId>
> 		<artifactId>CONFIGURATION</artifactId>
> 		<version>3.0.</version>
> 		<relativePath>../CONFIGURATION/pom.xml</relativePath>
> 	</parent>
> 	<packaging>bundle</packaging>
> 	<artifactId>CONFIGURATION_INTTEST</artifactId>
> 	<name>${project.artifactId}</name>
> Snippet from parent aggregator project:
> ...
> 	<packaging>pom</packaging>
> 	<artifactId>CONFIGURATION</artifactId>
> 	<name>${project.artifactId}</name>
>     <modules>
>         <module>../CONFIGURATION_INTTEST</module>
>     </modules>
> ...
>     <build>
>         <pluginManagement>
>             <plugins>
>                 <plugin>
>                     <groupId>org.apache.felix</groupId>
>                     <artifactId>maven-bundle-plugin</artifactId>
>                     <version>2.3.7</version>
> ...
> The effect is that the project cannot be initially compiled, because the child project cannot look up the plugin version in parent project. Workaround: comment out <modules> section, mvn install, comment in.
> Also, any change in parent project needs two compile cycles to become effective.
> To get the child project compiling again, it is sufficient to remove the maven-bundle-plugin <plugin> section. Changing <packaging> to jar alone does not help here.

--
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