4 Replies Latest reply on Mar 7, 2013 8:08 AM by garethahealy

Deploying bundles to FMC

garethahealy Mar 6, 2013 4:18 AM

I have installed FMC on a RHEL and installed 2 containers (root, child) on another RHEL box. I am trying to understand the best way to deploy my bundles to FMC, so they can be pushed out to the containers.

I saw this and it seems that the suggested way would be to use a distributionManagement tag, which i have configured in my pom - i've attached a cut down version. I've also attached the maven log (mvn -Pdeploy-dev install deploy) as i dont think the files are being uploaded to the FMC server - my ~/.m2/repository directory is empty, which i expected to have the bundles in.

Any ideas where i am doing wrong?

example-pom.xml 2.1 KB
maven log.txt 749.3 KB

1. Re: Deploying bundles to FMC

garethahealy Mar 6, 2013 11:29 AM (in response to garethahealy)

I found out what i was doing wrong, i needed to also replace the in my deploy-dev profile.

I am getting an error back now which is: Return code is: 406, ReasonPhrase:Not Acceptable.

But i presume thats because of my server setup/firewall.

Failed to upload MD5 checksum for C:\Users\gareth.healy\.m2\repository\com\boohoo\boohoo-esb\1.0-SNAPSHOT\maven-metadata-fabric-maven-proxy-snapshots.xml: Failed to transfer file: http://:8107/maven/upload/com/boohoo/boohoo-esb/1.0-SNAPSHOT/maven-metadata.xml.md5. Return code is: 406, ReasonPhrase:Not Acceptable. org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://:8107/maven/upload/com/boohoo/boohoo-esb/1.0-SNAPSHOT/maven-metadata.xml.md5. Return code is: 406, ReasonPhrase:Not Acceptable.
        at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:562)
        at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:471)
        at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.putFromStream(AbstractHttpClientWagon.java:465)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksum(WagonRepositoryConnector.java:886)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.uploadChecksums(WagonRepositoryConnector.java:861)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:818)
        at org.sonatype.aether.connector.wagon.WagonRepositoryConnector.put(WagonRepositoryConnector.java:475)
        at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:305)
        at org.sonatype.aether.impl.internal.DefaultDeployer.deploy(DefaultDeployer.java:211)
        at org.sonatype.aether.impl.internal.DefaultRepositorySystem.deploy(DefaultRepositorySystem.java:443)
        at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:137)
        at org.apache.maven.plugin.deploy.AbstractDeployMojo.deploy(AbstractDeployMojo.java:167)
        at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:149)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Actions
2. Re: Deploying bundles to FMC

garethahealy Mar 7, 2013 6:15 AM (in response to garethahealy)
Am still having problems with deploying to FMC. I noticed in the FMC log, there are some StringIndexOutOfBoundsExceptions.

From looking at the code its expecting a jar file to split on but obviously it cant as its been given the maven-metadata.xml file.

I've read this and i think everything is setup correctly.

karaf.log 46.3 KB

maven.log 412.4 KB
Actions
3. Re: Deploying bundles to FMC

stlewis Mar 7, 2013 7:40 AM (in response to garethahealy)

Yes, it looks like you have everything set up right. The proxy originally just accepted files that weren't jars just fine, not sure when this crept in. I've gone ahead and raised this issue for it.
Actions
4. Re: Deploying bundles to FMC

garethahealy Mar 7, 2013 8:08 AM (in response to stlewis)

Thanks Stan.
Actions

Go to original post