I ended up temporarily adding the relevant configuration to the
blueprint-web-osgi/pom.xml only. I thought yesterday it could be
something to do with my Ubuntu install, but the issue persisted today
even after I refreshed the OS and retried the process from the different
location.
Sorry about the noise,
Thanks, Sergey
On 04/11/13 22:07, Sergey Beryozkin wrote:
Hi All,
I'm trying to do a blueprint-web-osgi 1.0.1 release to address a
blueprint-core related Import-Package issue.
I'm getting stuck while doing release:prepare, it hangs at
[INFO] [INFO] --- maven-gpg-plugin:1.0-alpha-4:sign (default) @
org.apache.aries.blueprint.webosgi ---
Apparently it is a well-known issue, and while I did not see it before,
it is happening to me now,
The workaround is documented at [1] and is about explicitly configuring
a maven release plugin and adding
"<mavenExecutorId>forked-path</mavenExecutorId>"
to its configuration.
Would you be OK with me adding this kind of configuration to
parent/pom.xml ?
Or I can update only blueprint-web-osgi/pom.xml just to get past this
issue.
Comments are welcome
Thanks, Sergey
[1]
https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
