[jira] [Resolved] (FELIX-5124) maven-bundle-plugin interferes with installAtEnd setting of maven-install-bundle
[
https://issues.apache.org/jira/browse/FELIX-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved FELIX-5124.
-
Resolution: Invalid
In the mean time I did some more tests and found other plug-ins and scenarios
which cause problems with the install plug-in. So I don't think that this is an
issue of the bundle plug-in.
Closing as invalid, sorry for the noise.
> maven-bundle-plugin interferes with installAtEnd setting of
> maven-install-bundle
>
>
> Key: FELIX-5124
> URL: https://issues.apache.org/jira/browse/FELIX-5124
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
>Reporter: Oliver Heger
> Attachments: install_test.zip
>
>
> The maven-install-plugin supports the _installAtEnd_ setting which differs
> the installation of artifacts in a multi-module build to the very end; the
> installation happens only if the whole build is successful (see
> https://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#installAtEnd).
> We wanted to use this feature in our project, but found out that even for
> successful builds the installation never happend. After each module a message
> was printed "Installing :: at end", but at the
> end of the build no installation was performed.
> Investigating this problem showed a relation to the maven-bundle-plugin (in
> its latest version 3.0.1): If the maven-bundle-plugin is declared in the
> top-level pom, installation works as expected. However, if the declaration is
> moved to a sub-module, the installation is skipped.
> I have created a sample maven project demonstrating the issue. The project
> consists of the top-level pom, a modules pom and two sub-modules for the API
> and the implementation of a dummy service. The maven-bundle-plugin
> declaration is commented out in the top-level pom; it is also declared in the
> modules pom. In this form, when building the project with {{mvn clean
> install}} the project artifacts are not installed. When the comments are
> removed to enable the declaration the installation takes place. I hope this
> helps to reproduce and further anylize the problem.
> I was not sure whether this is the correct place to report this problem
> because the maven-install-plugin is affected as well. However, the install
> plugin works well in normal scenarios. The maven-deploy-plugin has a similar
> setting (_deployAtEnd_), and it is affected by this issue, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-5124) maven-bundle-plugin interferes with installAtEnd setting of maven-install-bundle
Oliver Heger created FELIX-5124:
---
Summary: maven-bundle-plugin interferes with installAtEnd setting
of maven-install-bundle
Key: FELIX-5124
URL: https://issues.apache.org/jira/browse/FELIX-5124
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Reporter: Oliver Heger
The maven-install-plugin supports the _installAtEnd_ setting which differs the
installation of artifacts in a multi-module build to the very end; the
installation happens only if the whole build is successful (see
https://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#installAtEnd).
We wanted to use this feature in our project, but found out that even for
successful builds the installation never happend. After each module a message
was printed "Installing :: at end", but at the
end of the build no installation was performed.
Investigating this problem showed a relation to the maven-bundle-plugin (in its
latest version 3.0.1): If the maven-bundle-plugin is declared in the top-level
pom, installation works as expected. However, if the declaration is moved to a
sub-module, the installation is skipped.
I have created a sample maven project demonstrating the issue. The project
consists of the top-level pom, a modules pom and two sub-modules for the API
and the implementation of a dummy service. The maven-bundle-plugin declaration
is commented out in the top-level pom; it is also declared in the modules pom.
In this form, when building the project with {{mvn clean install}} the project
artifacts are not installed. When the comments are removed to enable the
declaration the installation takes place. I hope this helps to reproduce and
further anylize the problem.
I was not sure whether this is the correct place to report this problem because
the maven-install-plugin is affected as well. However, the install plugin works
well in normal scenarios. The maven-deploy-plugin has a similar setting
(_deployAtEnd_), and it is affected by this issue, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FELIX-5124) maven-bundle-plugin interferes with installAtEnd setting of maven-install-bundle
[
https://issues.apache.org/jira/browse/FELIX-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger updated FELIX-5124:
Attachment: install_test.zip
Maven test project demonstrating the problem.
> maven-bundle-plugin interferes with installAtEnd setting of
> maven-install-bundle
>
>
> Key: FELIX-5124
> URL: https://issues.apache.org/jira/browse/FELIX-5124
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
>Reporter: Oliver Heger
> Attachments: install_test.zip
>
>
> The maven-install-plugin supports the _installAtEnd_ setting which differs
> the installation of artifacts in a multi-module build to the very end; the
> installation happens only if the whole build is successful (see
> https://maven.apache.org/plugins/maven-install-plugin/install-mojo.html#installAtEnd).
> We wanted to use this feature in our project, but found out that even for
> successful builds the installation never happend. After each module a message
> was printed "Installing :: at end", but at the
> end of the build no installation was performed.
> Investigating this problem showed a relation to the maven-bundle-plugin (in
> its latest version 3.0.1): If the maven-bundle-plugin is declared in the
> top-level pom, installation works as expected. However, if the declaration is
> moved to a sub-module, the installation is skipped.
> I have created a sample maven project demonstrating the issue. The project
> consists of the top-level pom, a modules pom and two sub-modules for the API
> and the implementation of a dummy service. The maven-bundle-plugin
> declaration is commented out in the top-level pom; it is also declared in the
> modules pom. In this form, when building the project with {{mvn clean
> install}} the project artifacts are not installed. When the comments are
> removed to enable the declaration the installation takes place. I hope this
> helps to reproduce and further anylize the problem.
> I was not sure whether this is the correct place to report this problem
> because the maven-install-plugin is affected as well. However, the install
> plugin works well in normal scenarios. The maven-deploy-plugin has a similar
> setting (_deployAtEnd_), and it is affected by this issue, too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
