12-19-2011 05:33 PM
I'm attempting to build a bundle using the Nuxeo IDE.
Everything seemed to install and configure correctly, however when I manually try to run maven on the POM file I get and error about maven looking for an assembly.xml file. I have not been able to find any reference to the appropriate assembly.xml configuration file layout/format. I understand what the assembly.xml file does so I don't need a definition, I need a reference to what it should contain if it is needed for Nuxeo dm.
Is this file needed? Or have I set up something incorrectly in the Nuxeo IDE setup?
Log of maven run and POM file follow:
[karl@BES nuxeo-platform-zaxis-mail-web]$
[karl@BES nuxeo-platform-zaxis-mail-web]$ mvn clean install
Warning: JAVA_HOME environment variable is not set.
[INFO] Scanning for projects...
... etc ...
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar: /home/karl/Desktop/nuxbundle/workspace/nuxeo-platform-zaxis-mail-web/target/nuxeo-zaxis-zmail-5.4.2-I20110404_0115.jar
[INFO] [nuxeo-distribution-tools:build {execution: packaging}]
BUILD FAILED
java.io.FileNotFoundException: /home/karl/Desktop/nuxbundle/workspace/nuxeo-platform-zaxis-mail-web/src/main/assemble/assembly.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:137)
at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:190)
at org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:140)
at org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
at org.nuxeo.build.ant.AntClient.run(AntClient.java:139)
at org.nuxeo.build.ant.AntClient.run(AntClient.java:87)
at org.nuxeo.build.maven.AntBuildMojo.execute(AntBuildMojo.java:242)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
... etc ...
Here is the POM file:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns= "http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">;
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.nuxeo.ecm.distribution</groupId>
<artifactId>nuxeo-distribution-tomcat</artifactId>
<version>5.4.2-I20110404_0115</version>
</parent>
<packaging>jar</packaging>
<groupId>nuxeo-platform-mygroup</groupId>
<artifactId>nuxeo-myproject</artifactId>
<dependencies>
... my dependencies ...
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<additionalProjectnatures>
<projectnature>org.nuxeo.ide.NuxeoNature</projectnature>
</additionalProjectnatures>
<classpathContainers>
<classpathContainer>org.eclipse.jdt.launching.JRE_CONTAINER</classpathContainer>
<classpathContainer>org.nuxeo.ide.SDK_CONTAINER</classpathContainer>
<classpathContainer>org.nuxeo.ide.SDK_TEST_CONTAINER</classpathContainer>
</classpathContainers>
</configuration>
</plugin>
</plugins>
</build>
<repositories>
<repository>
<id>public</id>
<url>http://maven.nuxeo.org/nexus/content/groups/public</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>public-snapshot</id>
<url>http://maven.nuxeo.org/nexus/content/groups/public-snapshot</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<updatePolicy>always</updatePolicy>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
</project>
12-19-2011 06:11 PM
You have the wrong parent project.
The nuxeo-distribution-tomcat project uses nuxeo's distribution tools to package a whole distribution, not a single bundle, and it uses the assembly.xml to define a set of ant targets for building the dist dir.
Just use nuxeo-features-parent as parent and everything should work:
<parent>
<groupId>org.nuxeo.ecm.platform</groupId>
<artifactId>nuxeo-features-parent</artifactId>
<version>5.5</version>
</parent>
You should probably take a look at some sample projects like this or use Nuxeo IDE.
12-19-2011 06:11 PM
You have the wrong parent project.
The nuxeo-distribution-tomcat project uses nuxeo's distribution tools to package a whole distribution, not a single bundle, and it uses the assembly.xml to define a set of ant targets for building the dist dir.
Just use nuxeo-features-parent as parent and everything should work:
<parent>
<groupId>org.nuxeo.ecm.platform</groupId>
<artifactId>nuxeo-features-parent</artifactId>
<version>5.5</version>
</parent>
You should probably take a look at some sample projects like this or use Nuxeo IDE.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.