You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Alan Mehio <al...@googlemail.com> on 2012/10/11 21:55:21 UTC
Apache James 3.0-beta1 build using maven 3.0.4
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
Re: Apache James 3.0-beta1 build using maven 3.0.4
Posted by Alan Mehio <al...@googlemail.com>.
Eric,
Many thanks for your reply. Actually I am in the process of starting from
scratch now. I have manage to build james since my ast.jar was corrupted
and I manually download a one from maven repo. Now it is building without
any change but I need to start from eclipse using m2eclipse plugin but I am
still facing the var and config needs to setup on the two newly created
project as recommended from the site since they contain the database base
(derby connection )and other..
I will give it a try today and see what happens.
Cheers
Alan M
On 12 October 2012 13:17, Eric Charles <er...@u-mangate.com> wrote:
> 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<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: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: Apache James 3.0-beta1 build using maven 3.0.4
Posted by Eric Charles <er...@u-mangate.com>.
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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org