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 David Leangen <ap...@leangen.net> on 2020/04/26 10:58:23 UTC
Building JAMES
Hi!
I am trying to build JAMES from HEAD using mvn install. It is my expectation (from working with other projects) that I should just be able to build “out of the box”.
My first question: is my expectation correct? Am I supposed to be able to build JAMES without any compilation errors?
If so, is anybody willing to help me understand the problems so I can make PRs to fix the build issues?
If not: what is the expected path to be able to use the source code. It is not clear to me from the documentation (which only seems to discuss building the websites).
Thanks!
=David
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Building JAMES
Posted by Pablo Pita Leira <pa...@pitagoral.com>.
On 06.05.20 16:44, Raphaël Ouazana-Sustowski wrote:
> On my Linux box `mvn -DskipTests clean package` is working fine (I can
> even add -T1C to make it faster). I skip tests because there are very
> long (about 2h) and better reproducibe via Docker.
On my Ubuntu Linux box, at the end I also have succeeded to compile the
project. It required some actions. First, no JAVA_HOME is defined, so
the build failed. For that, launch maven defining it:
JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 mvn -DskipTests clean package
The build then failed at:
mock-smtp-server: Building image tarball failed, perhaps you should make
sure your credentials for 'registry-1.docker.io/library/openjdk' are set
up correctly. See
https://github.com/GoogleContainerTools/jib/blob/master/docs/faq.md#what-should-i-do-when-the-registry-responds-with-unauthorized
for help:
From the help, my installation has docker-credential-secretservice, so
this is added to the .docker/config.json:
|{"credsStore":"||secretservice"}|
Trying again, it came another error related to reaching the maximum
number of openfiles:
[ERROR]
/home/pablo/dev/jp/james-project/server/container/guice/cassandra-rabbitmq-guice/src/main/java/org/apache/james/modules/DistributedTaskManagerModule.java:[43,8]
error while writing
org.apache.james.modules.DistributedTaskManagerModule:
/home/pablo/dev/jp/james-project/server/container/guice/cassandra-rabbitmq-guice/target/classes/org/apache/james/modules/DistributedTaskManagerModule.class:
Too many open files
For this one, I increased that number in /etc/sysctl.conf
fs.file-max = 2097152
And in the bash session,
ulimit -n 4096
Check it: ulimit -aHS
After that, the james-project finally compiled.
Re: Building JAMES
Posted by Raphaël Ouazana-Sustowski <ro...@apache.org>.
Le 01/05/2020 à 07:39, David Leangen (Apache) a écrit :
>> If you are not able to install Java 11 on your build machine, and prefer
>> using Docker I recommend that you use the tested docker image for
>> compilation. See: https://github.com/apache/james-project/#java-11
> The build worked using Docker as you recommended.
>
> FYI, for the fun of it, I also installed Java 11 on my Mac and tried to compile without Docker, but the build failed.
>
> james-project$ java -version
> openjdk version "11.0.7" 2020-04-14
> OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
> OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.7+10, mixed mode)
>
> [INFO] Apache James :: Server :: Task :: Memory implementation FAILURE [ 40.001 s]
>
> [ERROR] Tests run: 32, Failures: 0, Errors: 32, Skipped: 0, Time elapsed: 0.089 s <<< FAILURE! - in org.apache.james.task.MemoryTaskManagerTest
> [ERROR] additionalInformationShouldBeUpdatedWhenFailed Time elapsed: 0.018 s <<< ERROR!
> java.lang.NoSuchMethodError: 'void org.apache.james.task.MemoryTaskManager.<init>(org.apache.james.task.Hostname)'
> at org.apache.james.task.MemoryTaskManagerTest.setUp(MemoryTaskManagerTest.java:33)
>
> [ERROR] getStatusShouldReturnCompletedWhenRunSuccessfully Time elapsed: 0 s <<< ERROR!
> java.lang.NoSuchMethodError: 'void org.apache.james.task.MemoryTaskManager.<init>(org.apache.james.task.Hostname)'
> at org.apache.james.task.MemoryTaskManagerTest.setUp(MemoryTaskManagerTest.java:33)
>
> Should I file a bug?
>
Yes probably. Which version of Maven are you using?
On my Linux box `mvn -DskipTests clean package` is working fine (I can
even add -T1C to make it faster). I skip tests because there are very
long (about 2h) and better reproducibe via Docker.
Regards,
Raphaël.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Building JAMES
Posted by "David Leangen (Apache)" <ap...@leangen.net>.
> If you are not able to install Java 11 on your build machine, and prefer
> using Docker I recommend that you use the tested docker image for
> compilation. See: https://github.com/apache/james-project/#java-11
The build worked using Docker as you recommended.
FYI, for the fun of it, I also installed Java 11 on my Mac and tried to compile without Docker, but the build failed.
james-project$ java -version
openjdk version "11.0.7" 2020-04-14
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.7+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.7+10, mixed mode)
[INFO] Apache James :: Server :: Task :: Memory implementation FAILURE [ 40.001 s]
[ERROR] Tests run: 32, Failures: 0, Errors: 32, Skipped: 0, Time elapsed: 0.089 s <<< FAILURE! - in org.apache.james.task.MemoryTaskManagerTest
[ERROR] additionalInformationShouldBeUpdatedWhenFailed Time elapsed: 0.018 s <<< ERROR!
java.lang.NoSuchMethodError: 'void org.apache.james.task.MemoryTaskManager.<init>(org.apache.james.task.Hostname)'
at org.apache.james.task.MemoryTaskManagerTest.setUp(MemoryTaskManagerTest.java:33)
[ERROR] getStatusShouldReturnCompletedWhenRunSuccessfully Time elapsed: 0 s <<< ERROR!
java.lang.NoSuchMethodError: 'void org.apache.james.task.MemoryTaskManager.<init>(org.apache.james.task.Hostname)'
at org.apache.james.task.MemoryTaskManagerTest.setUp(MemoryTaskManagerTest.java:33)
Should I file a bug?
Cheers,
=David
Re: Building JAMES
Posted by Raphaël Ouazana-Sustowski <ro...@apache.org>.
Hello,
Le 01/05/2020 à 00:02, David Leangen (Apache) a écrit :
> However….
>
> I am still not yet able to import the projects into Eclipse, so first things first.
Unfortunately we are aware of this issue. As far as I know Eclipse is
not able to handle the version of Scala we are using for some of our
modules. If anyone has an idea to fix this, it is very welcome. In the
mean time, we are all using IntelliJ to develop on James...
Regards,
Raphaël.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Building JAMES
Posted by "David Leangen (Apache)" <ap...@leangen.net>.
Thank you!!
That worked, and I now understand what the documentation is trying to explain. Actually in hindsight it’s fairly obvious.
On that note, since I am still pretty ignorant about most of James, I have the “advantage” of being able to see the project documentation as an outsider. I hope to be able to use James quite a lot from now, so I am interested in helping to improve the documentation.
I will start another thread on that topic.
Thanks for helping me get started. :-)
However….
I am still not yet able to import the projects into Eclipse, so first things first.
Cheers,
=David
On Apr 30, 2020 23:17 +0900, Raphaël Ouazana-Sustowski <ro...@apache.org>, wrote:
> Hello,
>
> The last error message is strange, I cannot explain it.
>
> If you are not able to install Java 11 on your build machine, and prefer
> using Docker I recommend that you use the tested docker image for
> compilation. See: https://github.com/apache/james-project/#java-11
>
> Regards,
>
> Raphaël.
>
> Le 30/04/2020 à 13:55, David Leangen a écrit :
> > I’m back to making another attempt at building. :-)
> >
> > I am not able to update my development machine to use java 11, so I am trying with docker like this:
> >
> > docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-openjdk-11 mvn clean install
> >
> >
> > But I quickly run into this problem:
> >
> > [INFO] Apache James :: Testing :: Base .................... FAILURE [ 38.634 s]
> >
> > [ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:3.0.1:revision (get-the-git-infos) on project testing-base: Could not complete Mojo execution...: GIT-Command 'git describe --dirty=-dirty --match=* --abbrev=7' did not finish in 30000 milliseconds -> [Help 1]
> >
> >
> > The plugin doesn’t seem to work in this environment, so I skipped it by adding `-Dmaven.gitcommitid.skip=true` to the run parameters.
> >
> > Q: Will this cause any problems once I can eventually build successfully?
> >
> > New result:
> >
> > [INFO] Apache James Cassandra backend ..................... FAILURE [ 57.902 s]
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project apache-james-backends-cassandra: There are test failures.
> > [ERROR]
> > [ERROR] Please refer to /usr/src/mymaven/backends-common/cassandra/target/surefire-reports for the individual test results.
> > [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
> >
> > So I disabled tests and tried again.
> >
> >
> > The build continues almost to the end (60 minutes on my machine), and unfortunately ends with this:
> >
> > [INFO] Apache James :: Server :: Web Admin server integration tests :: Common FAILURE [ 12.443 s]
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-webadmin-integration-test-common: Compilation failure: Compilation failure:
> > [ERROR] /usr/src/mymaven/server/protocols/webadmin-integration-test/webadmin-integration-test-common/src/main/java/org/apache/james/webadmin/integration/JwtFilterIntegrationTest.java:[34,33] cannot find symbol
> > [ERROR] symbol: class WebAdminUtils
> > [ERROR] location: package org.apache.james.webadmin
> >
> > Sadly, I still cannot run `mvn eclipse:eclipse`, so I still cannot make any PRs. Looks like I’ll need some help getting started, if that is possible.
> >
> >
> > Cheers,
> > =David
> >
> >
> >
> > > On Apr 27, 2020, at 15:49, David Leangen (Apache) <ap...@leangen.net> wrote:
> > >
> > > Thanks for the clarification. That will push me in the right direction.
> > >
> > > If I ever get it built someday, then I’ll try to remember to submit a PR to mention the version requirement somewhere in the docs.
> > >
> > > I’ll just concentrate on the pre-built for now version then.
> > >
> > > Cheers,
> > > =David
> > > On Apr 27, 2020 15:44 +0900, Matthieu Baechler <ma...@apache.org>, wrote:
> > > > On Mon, 2020-04-27 at 15:32 +0900, David Leangen (Apache) wrote:
> > > > > Thank you, Rene.
> > > > >
> > > > > Is that a hard requirement? If so, then I will have to wait until we
> > > > > update to Java 11 (which is not scheduled at this time), so I’ll
> > > > > likely have to abandon for now.
> > > > >
> > > > > Shouldn’t it be possible to compile in Java 8, though? This page
> > > > > states that JRE8 is the requirement:
> > > > >
> > > > > —> https://james.apache.org/server/quick-start.html
> > > > This guide is about deploying an already-compile James server.
> > > >
> > > > Up to James 3.5 (which has a pending release), you could run with Java
> > > > 8 JRE.
> > > >
> > > > Starting with James 3.6, you'll need Java 11.
> > > >
> > > > What you are trying to do is to compile it yourself, the requirements
> > > > are differents.
> > > >
> > > > For some times now (probably 3.4) we use Java 11 compiler but target
> > > > Java 8.
> > > >
> > > > Cheers,
> > > >
> > > > -- Matthieu Baechler
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> > > > For additional commands, e-mail: server-user-help@james.apache.org
> > > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
Re: Building JAMES
Posted by Raphaël Ouazana-Sustowski <ro...@apache.org>.
Hello,
The last error message is strange, I cannot explain it.
If you are not able to install Java 11 on your build machine, and prefer
using Docker I recommend that you use the tested docker image for
compilation. See: https://github.com/apache/james-project/#java-11
Regards,
Raphaël.
Le 30/04/2020 à 13:55, David Leangen a écrit :
> I’m back to making another attempt at building. :-)
>
> I am not able to update my development machine to use java 11, so I am trying with docker like this:
>
> docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-openjdk-11 mvn clean install
>
>
> But I quickly run into this problem:
>
> [INFO] Apache James :: Testing :: Base .................... FAILURE [ 38.634 s]
>
> [ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:3.0.1:revision (get-the-git-infos) on project testing-base: Could not complete Mojo execution...: GIT-Command 'git describe --dirty=-dirty --match=* --abbrev=7' did not finish in 30000 milliseconds -> [Help 1]
>
>
> The plugin doesn’t seem to work in this environment, so I skipped it by adding `-Dmaven.gitcommitid.skip=true` to the run parameters.
>
> Q: Will this cause any problems once I can eventually build successfully?
>
> New result:
>
> [INFO] Apache James Cassandra backend ..................... FAILURE [ 57.902 s]
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project apache-james-backends-cassandra: There are test failures.
> [ERROR]
> [ERROR] Please refer to /usr/src/mymaven/backends-common/cassandra/target/surefire-reports for the individual test results.
> [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
>
> So I disabled tests and tried again.
>
>
> The build continues almost to the end (60 minutes on my machine), and unfortunately ends with this:
>
> [INFO] Apache James :: Server :: Web Admin server integration tests :: Common FAILURE [ 12.443 s]
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-webadmin-integration-test-common: Compilation failure: Compilation failure:
> [ERROR] /usr/src/mymaven/server/protocols/webadmin-integration-test/webadmin-integration-test-common/src/main/java/org/apache/james/webadmin/integration/JwtFilterIntegrationTest.java:[34,33] cannot find symbol
> [ERROR] symbol: class WebAdminUtils
> [ERROR] location: package org.apache.james.webadmin
>
> Sadly, I still cannot run `mvn eclipse:eclipse`, so I still cannot make any PRs. Looks like I’ll need some help getting started, if that is possible.
>
>
> Cheers,
> =David
>
>
>
>> On Apr 27, 2020, at 15:49, David Leangen (Apache) <ap...@leangen.net> wrote:
>>
>> Thanks for the clarification. That will push me in the right direction.
>>
>> If I ever get it built someday, then I’ll try to remember to submit a PR to mention the version requirement somewhere in the docs.
>>
>> I’ll just concentrate on the pre-built for now version then.
>>
>> Cheers,
>> =David
>> On Apr 27, 2020 15:44 +0900, Matthieu Baechler <ma...@apache.org>, wrote:
>>> On Mon, 2020-04-27 at 15:32 +0900, David Leangen (Apache) wrote:
>>>> Thank you, Rene.
>>>>
>>>> Is that a hard requirement? If so, then I will have to wait until we
>>>> update to Java 11 (which is not scheduled at this time), so I’ll
>>>> likely have to abandon for now.
>>>>
>>>> Shouldn’t it be possible to compile in Java 8, though? This page
>>>> states that JRE8 is the requirement:
>>>>
>>>> —> https://james.apache.org/server/quick-start.html
>>> This guide is about deploying an already-compile James server.
>>>
>>> Up to James 3.5 (which has a pending release), you could run with Java
>>> 8 JRE.
>>>
>>> Starting with James 3.6, you'll need Java 11.
>>>
>>> What you are trying to do is to compile it yourself, the requirements
>>> are differents.
>>>
>>> For some times now (probably 3.4) we use Java 11 compiler but target
>>> Java 8.
>>>
>>> Cheers,
>>>
>>> -- Matthieu Baechler
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Building JAMES
Posted by David Leangen <ap...@leangen.net>.
I’m back to making another attempt at building. :-)
I am not able to update my development machine to use java 11, so I am trying with docker like this:
docker run -it --rm --name my-maven-project -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-openjdk-11 mvn clean install
But I quickly run into this problem:
[INFO] Apache James :: Testing :: Base .................... FAILURE [ 38.634 s]
[ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:3.0.1:revision (get-the-git-infos) on project testing-base: Could not complete Mojo execution...: GIT-Command 'git describe --dirty=-dirty --match=* --abbrev=7' did not finish in 30000 milliseconds -> [Help 1]
The plugin doesn’t seem to work in this environment, so I skipped it by adding `-Dmaven.gitcommitid.skip=true` to the run parameters.
Q: Will this cause any problems once I can eventually build successfully?
New result:
[INFO] Apache James Cassandra backend ..................... FAILURE [ 57.902 s]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project apache-james-backends-cassandra: There are test failures.
[ERROR]
[ERROR] Please refer to /usr/src/mymaven/backends-common/cassandra/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
So I disabled tests and tried again.
The build continues almost to the end (60 minutes on my machine), and unfortunately ends with this:
[INFO] Apache James :: Server :: Web Admin server integration tests :: Common FAILURE [ 12.443 s]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-webadmin-integration-test-common: Compilation failure: Compilation failure:
[ERROR] /usr/src/mymaven/server/protocols/webadmin-integration-test/webadmin-integration-test-common/src/main/java/org/apache/james/webadmin/integration/JwtFilterIntegrationTest.java:[34,33] cannot find symbol
[ERROR] symbol: class WebAdminUtils
[ERROR] location: package org.apache.james.webadmin
Sadly, I still cannot run `mvn eclipse:eclipse`, so I still cannot make any PRs. Looks like I’ll need some help getting started, if that is possible.
Cheers,
=David
> On Apr 27, 2020, at 15:49, David Leangen (Apache) <ap...@leangen.net> wrote:
>
> Thanks for the clarification. That will push me in the right direction.
>
> If I ever get it built someday, then I’ll try to remember to submit a PR to mention the version requirement somewhere in the docs.
>
> I’ll just concentrate on the pre-built for now version then.
>
> Cheers,
> =David
> On Apr 27, 2020 15:44 +0900, Matthieu Baechler <ma...@apache.org>, wrote:
>> On Mon, 2020-04-27 at 15:32 +0900, David Leangen (Apache) wrote:
>>> Thank you, Rene.
>>>
>>> Is that a hard requirement? If so, then I will have to wait until we
>>> update to Java 11 (which is not scheduled at this time), so I’ll
>>> likely have to abandon for now.
>>>
>>> Shouldn’t it be possible to compile in Java 8, though? This page
>>> states that JRE8 is the requirement:
>>>
>>> —> https://james.apache.org/server/quick-start.html
>>
>> This guide is about deploying an already-compile James server.
>>
>> Up to James 3.5 (which has a pending release), you could run with Java
>> 8 JRE.
>>
>> Starting with James 3.6, you'll need Java 11.
>>
>> What you are trying to do is to compile it yourself, the requirements
>> are differents.
>>
>> For some times now (probably 3.4) we use Java 11 compiler but target
>> Java 8.
>>
>> Cheers,
>>
>> -- Matthieu Baechler
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
Re: Building JAMES
Posted by "David Leangen (Apache)" <ap...@leangen.net>.
Thanks for the clarification. That will push me in the right direction.
If I ever get it built someday, then I’ll try to remember to submit a PR to mention the version requirement somewhere in the docs.
I’ll just concentrate on the pre-built for now version then.
Cheers,
=David
On Apr 27, 2020 15:44 +0900, Matthieu Baechler <ma...@apache.org>, wrote:
> On Mon, 2020-04-27 at 15:32 +0900, David Leangen (Apache) wrote:
> > Thank you, Rene.
> >
> > Is that a hard requirement? If so, then I will have to wait until we
> > update to Java 11 (which is not scheduled at this time), so I’ll
> > likely have to abandon for now.
> >
> > Shouldn’t it be possible to compile in Java 8, though? This page
> > states that JRE8 is the requirement:
> >
> > —> https://james.apache.org/server/quick-start.html
>
> This guide is about deploying an already-compile James server.
>
> Up to James 3.5 (which has a pending release), you could run with Java
> 8 JRE.
>
> Starting with James 3.6, you'll need Java 11.
>
> What you are trying to do is to compile it yourself, the requirements
> are differents.
>
> For some times now (probably 3.4) we use Java 11 compiler but target
> Java 8.
>
> Cheers,
>
> -- Matthieu Baechler
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
Re: Building JAMES
Posted by Matthieu Baechler <ma...@apache.org>.
On Mon, 2020-04-27 at 15:32 +0900, David Leangen (Apache) wrote:
> Thank you, Rene.
>
> Is that a hard requirement? If so, then I will have to wait until we
> update to Java 11 (which is not scheduled at this time), so I’ll
> likely have to abandon for now.
>
> Shouldn’t it be possible to compile in Java 8, though? This page
> states that JRE8 is the requirement:
>
> —> https://james.apache.org/server/quick-start.html
This guide is about deploying an already-compile James server.
Up to James 3.5 (which has a pending release), you could run with Java
8 JRE.
Starting with James 3.6, you'll need Java 11.
What you are trying to do is to compile it yourself, the requirements
are differents.
For some times now (probably 3.4) we use Java 11 compiler but target
Java 8.
Cheers,
-- Matthieu Baechler
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Building JAMES
Posted by "David Leangen (Apache)" <ap...@leangen.net>.
Thank you, Rene.
Is that a hard requirement? If so, then I will have to wait until we update to Java 11 (which is not scheduled at this time), so I’ll likely have to abandon for now.
Shouldn’t it be possible to compile in Java 8, though? This page states that JRE8 is the requirement:
—> https://james.apache.org/server/quick-start.html
Cheers,
=David
On Apr 27, 2020 13:44 +0900, Rene Cordier <rc...@apache.org>, wrote:
> Hi David,
>
> I think you are trying to compile the latest code from master branch
> right? A move has been made lately towards java 11 on it if I'm correct.
> Try to compile and run with Java11 instead?
>
> Regards,
> Rene.
>
> On 27/04/2020 06:06, David Leangen (Apache) wrote:
> > Hi!
> >
> > This is the first error:
> >
> > [INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ 0.659 s]
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-util: Fatal error compiling: invalid flag: --release -> [Help 1]
> >
> > Googling tells me to comment out the “release” flag in maven-compiler-plugin, so I try that (though I don’t understand why) and get a different error:
> >
> > [INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ 0.551 s]
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-util: Fatal error compiling: invalid target release: 11 -> [Help 1]
> >
> > Yeah, that makes sense. I am still on Java 8. So I modify the target.jdk version to 8 and make a bit of progress:
> >
> > [INFO] Apache James :: Core Domain Objects ................ FAILURE [ 0.597 s]
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-core: Compilation failure: Compilation failure:
> > [ERROR] /Users/dleangen/libs/james-project/core/src/main/java/org/apache/james/core/builder/MimeMessageBuilder.java:[400,46] no suitable method found for toArray(InternetAd[...]::new)
> >
> > Hmmmm. This is in the code. I just want to compile, not debug at this point. This makes me think that the project is currently being neglected. :-(
> >
> > Ok, let me try to omit the core project (though that does not sound like a promising approach).
> >
> > [INFO] Apache James Cassandra backend ..................... FAILURE [ 18.471 s]
> >
> > [ERROR] Failed to execute goal on project apache-james-backends-cassandra: Could not resolve dependencies for project org.apache.james:apache-james-backends-cassandra:jar:3.6.0-SNAPSHOT: Could not find artifact org.apache.james:james-core:jar:3.6.0-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
> >
> > Yeah, like I expected.
> >
> > Ok, so try mvn eclipse:eclipse without building the project, then? I only get this far:
> >
> > [INFO] Apache James :: Test helpers for Mailet ............ FAILURE [ 1.859 s]
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process (process-resource-bundles) on project apache-mailet-test: Execution process-resource-bundles of goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process failed: Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing:
> > [ERROR] 1) org.apache.james:james-core:jar:3.6.0-SNAPSHOT
> > [ERROR] 2) org.apache.james:apache-james-mailbox-api:jar:3.6.0-SNAPSHOT
> >
> > Perhaps only a simple fix is required to get everything compiling, but since I have never yet looked at any of the code base, I don’t know. I can’t even set it up in my Eclipse yet because I cannot run mvn eclipse:eclipse until I can get the projects to compile.
> >
> > I’m sure someone with enough motivation could figure out a way around these issues, but I thought that the golden rule was that the project should compile out of the box. That’s why I asked my original question.
> >
> > Cheers,
> > =David
> >
> > On Apr 27, 2020 02:39 +0900, Jerry Malcolm <te...@malcolms.com>, wrote:
> > > Sadly I realized a while back that it does not build out of the box.
> > > Through much trial and error, I finally got the build to complete.
> > > However, even with that, for some reason I still get several errors.
> > > Apparently they aren't fatal errors. I have learned that if there is
> > > really something wrong, the build won't complete. However, if the maven
> > > build gets to the end, even if there were errors reported, the build
> > > works. I would really like to understand this better. If the 'errors'
> > > I get aren't really critical, seems they should be warnings. I build
> > > and use James. But it doesn't give me a whole load of confidence that
> > > there were errors in the build, even though the build doesn't abort on them.
> > >
> > > What kind of errors are you getting? Does the build stop on those errors?
> > >
> > > Jerry
> > >
> > > On 4/26/2020 5:58 AM, David Leangen wrote:
> > > > Hi!
> > > >
> > > > I am trying to build JAMES from HEAD using mvn install. It is my expectation (from working with other projects) that I should just be able to build “out of the box”.
> > > >
> > > > My first question: is my expectation correct? Am I supposed to be able to build JAMES without any compilation errors?
> > > >
> > > >
> > > > If so, is anybody willing to help me understand the problems so I can make PRs to fix the build issues?
> > > >
> > > > If not: what is the expected path to be able to use the source code. It is not clear to me from the documentation (which only seems to discuss building the websites).
> > > >
> > > >
> > > > Thanks!
> > > > =David
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> > > > For additional commands, e-mail: server-user-help@james.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> > > For additional commands, e-mail: server-user-help@james.apache.org
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
Re: Building JAMES
Posted by Rene Cordier <rc...@apache.org>.
Hi David,
I think you are trying to compile the latest code from master branch
right? A move has been made lately towards java 11 on it if I'm correct.
Try to compile and run with Java11 instead?
Regards,
Rene.
On 27/04/2020 06:06, David Leangen (Apache) wrote:
> Hi!
>
> This is the first error:
>
> [INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ 0.659 s]
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-util: Fatal error compiling: invalid flag: --release -> [Help 1]
>
> Googling tells me to comment out the “release” flag in maven-compiler-plugin, so I try that (though I don’t understand why) and get a different error:
>
> [INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ 0.551 s]
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-util: Fatal error compiling: invalid target release: 11 -> [Help 1]
>
> Yeah, that makes sense. I am still on Java 8. So I modify the target.jdk version to 8 and make a bit of progress:
>
> [INFO] Apache James :: Core Domain Objects ................ FAILURE [ 0.597 s]
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-core: Compilation failure: Compilation failure:
> [ERROR] /Users/dleangen/libs/james-project/core/src/main/java/org/apache/james/core/builder/MimeMessageBuilder.java:[400,46] no suitable method found for toArray(InternetAd[...]::new)
>
> Hmmmm. This is in the code. I just want to compile, not debug at this point. This makes me think that the project is currently being neglected. :-(
>
> Ok, let me try to omit the core project (though that does not sound like a promising approach).
>
> [INFO] Apache James Cassandra backend ..................... FAILURE [ 18.471 s]
>
> [ERROR] Failed to execute goal on project apache-james-backends-cassandra: Could not resolve dependencies for project org.apache.james:apache-james-backends-cassandra:jar:3.6.0-SNAPSHOT: Could not find artifact org.apache.james:james-core:jar:3.6.0-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
>
> Yeah, like I expected.
>
> Ok, so try mvn eclipse:eclipse without building the project, then? I only get this far:
>
> [INFO] Apache James :: Test helpers for Mailet ............ FAILURE [ 1.859 s]
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process (process-resource-bundles) on project apache-mailet-test: Execution process-resource-bundles of goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process failed: Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing:
> [ERROR] 1) org.apache.james:james-core:jar:3.6.0-SNAPSHOT
> [ERROR] 2) org.apache.james:apache-james-mailbox-api:jar:3.6.0-SNAPSHOT
>
> Perhaps only a simple fix is required to get everything compiling, but since I have never yet looked at any of the code base, I don’t know. I can’t even set it up in my Eclipse yet because I cannot run mvn eclipse:eclipse until I can get the projects to compile.
>
> I’m sure someone with enough motivation could figure out a way around these issues, but I thought that the golden rule was that the project should compile out of the box. That’s why I asked my original question.
>
> Cheers,
> =David
>
> On Apr 27, 2020 02:39 +0900, Jerry Malcolm <te...@malcolms.com>, wrote:
>> Sadly I realized a while back that it does not build out of the box.
>> Through much trial and error, I finally got the build to complete.
>> However, even with that, for some reason I still get several errors.
>> Apparently they aren't fatal errors. I have learned that if there is
>> really something wrong, the build won't complete. However, if the maven
>> build gets to the end, even if there were errors reported, the build
>> works. I would really like to understand this better. If the 'errors'
>> I get aren't really critical, seems they should be warnings. I build
>> and use James. But it doesn't give me a whole load of confidence that
>> there were errors in the build, even though the build doesn't abort on them.
>>
>> What kind of errors are you getting? Does the build stop on those errors?
>>
>> Jerry
>>
>> On 4/26/2020 5:58 AM, David Leangen wrote:
>>> Hi!
>>>
>>> I am trying to build JAMES from HEAD using mvn install. It is my expectation (from working with other projects) that I should just be able to build “out of the box”.
>>>
>>> My first question: is my expectation correct? Am I supposed to be able to build JAMES without any compilation errors?
>>>
>>>
>>> If so, is anybody willing to help me understand the problems so I can make PRs to fix the build issues?
>>>
>>> If not: what is the expected path to be able to use the source code. It is not clear to me from the documentation (which only seems to discuss building the websites).
>>>
>>>
>>> Thanks!
>>> =David
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Building JAMES
Posted by "David Leangen (Apache)" <ap...@leangen.net>.
Hi!
This is the first error:
[INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ 0.659 s]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-util: Fatal error compiling: invalid flag: --release -> [Help 1]
Googling tells me to comment out the “release” flag in maven-compiler-plugin, so I try that (though I don’t understand why) and get a different error:
[INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ 0.551 s]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-server-util: Fatal error compiling: invalid target release: 11 -> [Help 1]
Yeah, that makes sense. I am still on Java 8. So I modify the target.jdk version to 8 and make a bit of progress:
[INFO] Apache James :: Core Domain Objects ................ FAILURE [ 0.597 s]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project james-core: Compilation failure: Compilation failure:
[ERROR] /Users/dleangen/libs/james-project/core/src/main/java/org/apache/james/core/builder/MimeMessageBuilder.java:[400,46] no suitable method found for toArray(InternetAd[...]::new)
Hmmmm. This is in the code. I just want to compile, not debug at this point. This makes me think that the project is currently being neglected. :-(
Ok, let me try to omit the core project (though that does not sound like a promising approach).
[INFO] Apache James Cassandra backend ..................... FAILURE [ 18.471 s]
[ERROR] Failed to execute goal on project apache-james-backends-cassandra: Could not resolve dependencies for project org.apache.james:apache-james-backends-cassandra:jar:3.6.0-SNAPSHOT: Could not find artifact org.apache.james:james-core:jar:3.6.0-SNAPSHOT in apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1]
Yeah, like I expected.
Ok, so try mvn eclipse:eclipse without building the project, then? I only get this far:
[INFO] Apache James :: Test helpers for Mailet ............ FAILURE [ 1.859 s]
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process (process-resource-bundles) on project apache-mailet-test: Execution process-resource-bundles of goal org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process failed: Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing:
[ERROR] 1) org.apache.james:james-core:jar:3.6.0-SNAPSHOT
[ERROR] 2) org.apache.james:apache-james-mailbox-api:jar:3.6.0-SNAPSHOT
Perhaps only a simple fix is required to get everything compiling, but since I have never yet looked at any of the code base, I don’t know. I can’t even set it up in my Eclipse yet because I cannot run mvn eclipse:eclipse until I can get the projects to compile.
I’m sure someone with enough motivation could figure out a way around these issues, but I thought that the golden rule was that the project should compile out of the box. That’s why I asked my original question.
Cheers,
=David
On Apr 27, 2020 02:39 +0900, Jerry Malcolm <te...@malcolms.com>, wrote:
> Sadly I realized a while back that it does not build out of the box.
> Through much trial and error, I finally got the build to complete.
> However, even with that, for some reason I still get several errors.
> Apparently they aren't fatal errors. I have learned that if there is
> really something wrong, the build won't complete. However, if the maven
> build gets to the end, even if there were errors reported, the build
> works. I would really like to understand this better. If the 'errors'
> I get aren't really critical, seems they should be warnings. I build
> and use James. But it doesn't give me a whole load of confidence that
> there were errors in the build, even though the build doesn't abort on them.
>
> What kind of errors are you getting? Does the build stop on those errors?
>
> Jerry
>
> On 4/26/2020 5:58 AM, David Leangen wrote:
> > Hi!
> >
> > I am trying to build JAMES from HEAD using mvn install. It is my expectation (from working with other projects) that I should just be able to build “out of the box”.
> >
> > My first question: is my expectation correct? Am I supposed to be able to build JAMES without any compilation errors?
> >
> >
> > If so, is anybody willing to help me understand the problems so I can make PRs to fix the build issues?
> >
> > If not: what is the expected path to be able to use the source code. It is not clear to me from the documentation (which only seems to discuss building the websites).
> >
> >
> > Thanks!
> > =David
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> > For additional commands, e-mail: server-user-help@james.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
Re: Building JAMES
Posted by Jerry Malcolm <te...@malcolms.com>.
Sadly I realized a while back that it does not build out of the box.
Through much trial and error, I finally got the build to complete.
However, even with that, for some reason I still get several errors.
Apparently they aren't fatal errors. I have learned that if there is
really something wrong, the build won't complete. However, if the maven
build gets to the end, even if there were errors reported, the build
works. I would really like to understand this better. If the 'errors'
I get aren't really critical, seems they should be warnings. I build
and use James. But it doesn't give me a whole load of confidence that
there were errors in the build, even though the build doesn't abort on them.
What kind of errors are you getting? Does the build stop on those errors?
Jerry
On 4/26/2020 5:58 AM, David Leangen wrote:
> Hi!
>
> I am trying to build JAMES from HEAD using mvn install. It is my expectation (from working with other projects) that I should just be able to build “out of the box”.
>
> My first question: is my expectation correct? Am I supposed to be able to build JAMES without any compilation errors?
>
>
> If so, is anybody willing to help me understand the problems so I can make PRs to fix the build issues?
>
> If not: what is the expected path to be able to use the source code. It is not clear to me from the documentation (which only seems to discuss building the websites).
>
>
> Thanks!
> =David
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org