Is there a reason that the jbi-maven-plugin installs/deploys the jar and zip
artifacts for a Service Archive build both as zip type maven artifacts? I
noticed that it is doing this and tried using the Fuse 3.4.0.5 bridge
examples and it does it there as well. This only appears to affect Service
Assembly jbi artifacts:
[INFO] Building jar:
C:\projects\apache-servicemix-3.4.0.5-fuse\examples\bridge\bridge-sa\target\bridge-sa-3.4.0.5-fuse.zip
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
C:\projects\apache-servicemix-3.4.0.5-fuse\examples\bridge\bridge-sa\target\bridge-sa-3.4.0.5-fuse.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing
C:\projects\apache-servicemix-3.4.0.5-fuse\examples\bridge\bridge-sa\target\bridge-sa-3.4.0.5-fuse.jar
to
C:\noscan\m2_repo\repository\org\apache\servicemix\samples\bridge\bridge-sa\3.4.0.5-fuse\bridge-sa-3.4.0.5-fuse.zip
[INFO] Installing
C:\projects\apache-servicemix-3.4.0.5-fuse\examples\bridge\bridge-sa\target\bridge-sa-3.4.0.5-fuse.zip
to
C:\noscan\m2_repo\repository\org\apache\servicemix\samples\bridge\bridge-sa\3.4.0.5-fuse\bridge-sa-3.4.0.5-fuse.zip
Ryan
