Doh, never mind the renaming of the jar part, apparently that is expected behavior from the Servicemix page:
"The JBI Maven plugin now packages service assemblies (SA) in a ZIP file in the target folder. Older versions of the plugin would package it as a JAR first and only rename it while installing the SA in the local Maven repository, leaving a JAR file in the target folder." I didn't realize that was changed with 4.0 of servicemix. The initial problem with my top level build is the only reason I even noticed the change. :) Does anyone know when Servicemix 4.0 will be released? I'm curious to try it out. Thanks! On Fri, Dec 12, 2008 at 9:00 PM, Ryan Moquin <[email protected]> wrote: > A couple more things, if I build the parent project of one of the SAs > (which builds the service units), then it builds the zip, but it installs > the jar as a zip and then installs the zip as the zip: > > .. > > [INFO] Building jar: > C:\projects\trunk\service-jbi\service-sa\target\service-sa-1.0-SNAPSHOT.zip > [INFO] [jar:jar] > [INFO] Building jar: > C:\projects\trunk\service-jbi\service-sa\target\service-sa-1.0-SNAPSHOT.jar > > ... > > [INFO] Installing > C:\projects\trunk\service-jbi\service-sa\target\service-sa-1.0-SNAPSHOT.jar > to C:\m2_repo\re > pository\com\service-sa\1.0-SNAPSHOT\service-sa-1.0-SNAPSHOT.zip > [INFO] Installing > C:\projects\trunk\service-jbi\service-sa\target\service-sa-1.0-SNAPSHOT.zip > to > C:\m2_repo\repository\com\service-sa\1.0-SNAPSHOT\service-sa-1.0-SNAPSHOT.zip > > I didn't have this problem yesterday, and I haven't changed versions of > servicemix or maven2. It doesn't appear that there is any other difference > than that it's completely confused between jars and zips and the build > operates differently depending on which level I build at. > > > On Fri, Dec 12, 2008 at 8:44 PM, Ryan Moquin <[email protected]>wrote: > >> BTW - I'm using 4.0 of the plugin and Servicemix 3.3. >> >> >> On Fri, Dec 12, 2008 at 8:39 PM, Ryan Moquin <[email protected]>wrote: >> >>> I have a bit of a problem, and I'm not sure why or how it could have >>> started. Doing a rebuild of my projects, the jbi-maven-plugin has stopped >>> building a zip file of my service archives, it only builds a jar. After it >>> only builds the jar, it installs the jar as a zip file, i.e.: >>> >>> [INFO] Installing >>> C:\projects\service-sa\target\service-sa-1.0-SNAPSHOT.jar to >>> C:\m2_repo\repository\com\service-sa\1.0-SNAPSHOT\service-sa-1.0-SNAPSHOT.zip >>> >>> So basically, this is causing my some headaches with how I'm building my >>> distributions later on. Has this happened to anyone? The plugin seems to >>> work if I build the sa directly, but does not work if I build it from any of >>> my super projects. I do have jbi component projects that seem to build find >>> as well. It's just every one of my service archive projects that don't >>> build correctly. I can't even fathom what I could have changed that may >>> have caused this problem. >>> >>> Thanks, >>> Ryan >>> >> >> >
