Hi,
If you don't change them pom, it should compile fine.
Now, if you say you need a manifest file, you will need to create one
for each module, yes.
Thx, Eric
On 11/10/2012 20:55, Alan Mehio wrote:
I followed the instruction from the page
http://james.apache.org/server/3/dev-build.html
Having looked at the re-usable test jar file in relation to the exception I
am getting, I have modified the parent pom.xml for the jar plugin
from :
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.3.1</version>
</plugin>
To:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.3.1</version>
<configuration>
<useDefaultManifestFile>true</useDefaultManifestFile>
</configuration>
<executions>
<execution>
<goals>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
The question is I am getting another exception which is related to creating
the jar file
ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:2.3.1:test-jar (default) on
project james-server: Error assembling JAR: Man
ifest file: ....\james-server-3.0-beta1\target\classes\META-INF\MANIFEST.MF
does not exist. -> [Help 1
so for each module I have to create and empty manifest file
Does any body managed to build James 3.0-beta1
Regards,
Alan Mehio
--
@echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
