Re: Building James 3.3.0 in Eclipse
Thanks for the info, Garry. But I'm still confused. Are you saying that it is no longer possible to build from the source on Eclipse? I realize the team may be pushing docker. But there are still non-docker binaries that got built someway. I just want to recreate those binaries with my code additions. But first I want to just build with the official source untouched and verify that works. Then I'll add my changes and rebuild. You said the .git files are from the .git repository. I don't doubt that. But I'm not a git guru. I'm still not sure how to fix the errors I'm getting (~400+ of these): org.apache.maven.plugin.MojoExecutionException: .git directory is not found! Please specify a valid [dotGitDirectory] in your pom.xml I do not know anything about pom syntax. I have no clue how/where to "specify a valid [dotGitDirectory] in your pom.xml" (times 400) Does this error mean that there isn't a gitDirectory defined in the pom.xml and there should be? Or does it mean that one is defined somewhere and the specified directory doesn't exist on my file system? I guess it'd be too much to ask for this error message to include the directory it found and which of the 400 pom.xml files the error refers to. (Sorry... I'm just frustrated at less-than-useful error messages). Did I download an invalid source zip? Is there a different zip (or additional zips that contain the correct pom files? ) I simply went to github and downloaded the latest source zip file. Where do I start? I really don't want to have to learn how to build on Linux unless there's an official word that says Eclipse is no longer supported as a build platform. I need to use Eclipse to debug my code. I just want to download the correct source, import it into Eclipse, and build it. I just can't understand why I can't get anywhere near a successful build. What am I doing wrong? Jerry On 8/31/2019 5:25 PM, Garry Hurley wrote: Jerry, I had to download the source, run configure and make on a Linux system. The problem is that the source is made to build onto a docker system on Windows. Those of us who choose not to run docker and run a real operating system often have issues. Those .git files are from the .git repository. If you did a git clone, create your workspace from the local git repo or import existing maven projects into eclipse from the repo. This serves two purposes. 1, it allows you to keep your project up to date and 2, it allows you to commit if you have any changes to the existing code you want to push up for others. I haven’t built anything after 3.3.0 was finalizedbecause the government finally approved 3.3.0 for use (ironically, they had been insisting that 3.0.4beta was safe to use in production and I outright refused to put that in place). Sent from my iPhone On Aug 31, 2019, at 6:02 PM, Jerry Malcolm wrote: Something else I just found... the link to a tutorial at http://blog.bonnydoonmedia.com/post.cfm/walkthrough-tutorials-compiling-apache-james-v3-with-eclipse in the Eclipse build section is dead. No DNS entry. On 8/31/2019 4:54 PM, Jerry Malcolm wrote: Correction... the build instructions page link should be: https://james.apache.org/server/3/dev-build.html On 8/31/2019 4:52 PM, Jerry Malcolm wrote: I'm trying to build the latest stable James 3.3.0 in Eclipse. -- The link to the 3.3.0 source zip on the downloads page is dead (https://www.apache.org/dyn/closer.lua/james/server/3.3.0/james-server-sources-3.3.0.zip) -- I figured out the correct link: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip and downloaded the zip. But the zip contains ONLY the primary source files and no pom.xml, etc files. -- I finally went to git and downloaded a zip that contained everything. -- But the fun just kept happening... I tried to import the project into Eclipse, but got over 500 errors. A large chunk of these errors was that every pom file has an invalid or missing a "dotGit" folder name. -- Also, I tried following the instructions here: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip -- In the section titled "prepare projects" it says to copy files from: server/container/spring/src/main/config/james and from server/container/src/main/config/james Apparently, the folder structures have completely changed since that was written. Neither of those folder exist, and it wasn't obvious where they moved to. -- I know enough about eclipse to get by. I know nothing about maven (and for now would like to keep it as close to that way as possible). I just want to add a few tweaks to James 3.3 that I added back in v3b5 and get the latest james into production. I'm sure there's something missing or some setting wrong in Eclipse or in the Maven plug-in. I did a complete clean install of Eclipse (Java EE version) and Maven on a different machine just to make sure there were no issues with
Re: Building James 3.3.0 in Eclipse
Jerry, I had to download the source, run configure and make on a Linux system. The problem is that the source is made to build onto a docker system on Windows. Those of us who choose not to run docker and run a real operating system often have issues. Those .git files are from the .git repository. If you did a git clone, create your workspace from the local git repo or import existing maven projects into eclipse from the repo. This serves two purposes. 1, it allows you to keep your project up to date and 2, it allows you to commit if you have any changes to the existing code you want to push up for others. I haven’t built anything after 3.3.0 was finalizedbecause the government finally approved 3.3.0 for use (ironically, they had been insisting that 3.0.4beta was safe to use in production and I outright refused to put that in place). Sent from my iPhone > On Aug 31, 2019, at 6:02 PM, Jerry Malcolm wrote: > > Something else I just found... the link to a tutorial at > http://blog.bonnydoonmedia.com/post.cfm/walkthrough-tutorials-compiling-apache-james-v3-with-eclipse > in the Eclipse build section is dead. No DNS entry. > > >> On 8/31/2019 4:54 PM, Jerry Malcolm wrote: >> Correction... the build instructions page link should be: >> https://james.apache.org/server/3/dev-build.html >> >> >>> On 8/31/2019 4:52 PM, Jerry Malcolm wrote: >>> I'm trying to build the latest stable James 3.3.0 in Eclipse. >>> >>> -- The link to the 3.3.0 source zip on the downloads page is dead >>> (https://www.apache.org/dyn/closer.lua/james/server/3.3.0/james-server-sources-3.3.0.zip) >>> >>> >>> -- I figured out the correct link: >>> http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip >>> and downloaded the zip. But the zip contains ONLY the primary source >>> files and no pom.xml, etc files. >>> >>> -- I finally went to git and downloaded a zip that contained everything. >>> >>> -- But the fun just kept happening... I tried to import the project into >>> Eclipse, but got over 500 errors. A large chunk of these errors was that >>> every pom file has an invalid or missing a "dotGit" folder name. >>> >>> -- Also, I tried following the instructions here: >>> http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip >>> -- In the section titled "prepare projects" it says to copy files from: >>> server/container/spring/src/main/config/james and from >>> server/container/src/main/config/james Apparently, the folder structures >>> have completely changed since that was written. Neither of those folder >>> exist, and it wasn't obvious where they moved to. >>> >>> -- I know enough about eclipse to get by. I know nothing about maven (and >>> for now would like to keep it as close to that way as possible). I just >>> want to add a few tweaks to James 3.3 that I added back in v3b5 and get the >>> latest james into production. I'm sure there's something missing or some >>> setting wrong in Eclipse or in the Maven plug-in. I did a complete clean >>> install of Eclipse (Java EE version) and Maven on a different machine just >>> to make sure there were no issues with my original Eclipse. No change. >>> >>> Any help on resolving the hundreds of import errors and where to find all >>> of these files that have moved since the instructions were written will be >>> appreciated. I'm at a total loss. I really just need to get this thing >>> to build. >>> >>> Thanks. >>> >>> Jerry >>> >>> >> >> - >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> > > - > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: Building James 3.3.0 in Eclipse
Something else I just found... the link to a tutorial at http://blog.bonnydoonmedia.com/post.cfm/walkthrough-tutorials-compiling-apache-james-v3-with-eclipse in the Eclipse build section is dead. No DNS entry. On 8/31/2019 4:54 PM, Jerry Malcolm wrote: Correction... the build instructions page link should be: https://james.apache.org/server/3/dev-build.html On 8/31/2019 4:52 PM, Jerry Malcolm wrote: I'm trying to build the latest stable James 3.3.0 in Eclipse. -- The link to the 3.3.0 source zip on the downloads page is dead (https://www.apache.org/dyn/closer.lua/james/server/3.3.0/james-server-sources-3.3.0.zip) -- I figured out the correct link: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip and downloaded the zip. But the zip contains ONLY the primary source files and no pom.xml, etc files. -- I finally went to git and downloaded a zip that contained everything. -- But the fun just kept happening... I tried to import the project into Eclipse, but got over 500 errors. A large chunk of these errors was that every pom file has an invalid or missing a "dotGit" folder name. -- Also, I tried following the instructions here: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip -- In the section titled "prepare projects" it says to copy files from: server/container/spring/src/main/config/james and from server/container/src/main/config/james Apparently, the folder structures have completely changed since that was written. Neither of those folder exist, and it wasn't obvious where they moved to. -- I know enough about eclipse to get by. I know nothing about maven (and for now would like to keep it as close to that way as possible). I just want to add a few tweaks to James 3.3 that I added back in v3b5 and get the latest james into production. I'm sure there's something missing or some setting wrong in Eclipse or in the Maven plug-in. I did a complete clean install of Eclipse (Java EE version) and Maven on a different machine just to make sure there were no issues with my original Eclipse. No change. Any help on resolving the hundreds of import errors and where to find all of these files that have moved since the instructions were written will be appreciated. I'm at a total loss. I really just need to get this thing to build. Thanks. Jerry - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Re: Building James 3.3.0 in Eclipse
Correction... the build instructions page link should be: https://james.apache.org/server/3/dev-build.html On 8/31/2019 4:52 PM, Jerry Malcolm wrote: I'm trying to build the latest stable James 3.3.0 in Eclipse. -- The link to the 3.3.0 source zip on the downloads page is dead (https://www.apache.org/dyn/closer.lua/james/server/3.3.0/james-server-sources-3.3.0.zip) -- I figured out the correct link: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip and downloaded the zip. But the zip contains ONLY the primary source files and no pom.xml, etc files. -- I finally went to git and downloaded a zip that contained everything. -- But the fun just kept happening... I tried to import the project into Eclipse, but got over 500 errors. A large chunk of these errors was that every pom file has an invalid or missing a "dotGit" folder name. -- Also, I tried following the instructions here: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip -- In the section titled "prepare projects" it says to copy files from: server/container/spring/src/main/config/james and from server/container/src/main/config/james Apparently, the folder structures have completely changed since that was written. Neither of those folder exist, and it wasn't obvious where they moved to. -- I know enough about eclipse to get by. I know nothing about maven (and for now would like to keep it as close to that way as possible). I just want to add a few tweaks to James 3.3 that I added back in v3b5 and get the latest james into production. I'm sure there's something missing or some setting wrong in Eclipse or in the Maven plug-in. I did a complete clean install of Eclipse (Java EE version) and Maven on a different machine just to make sure there were no issues with my original Eclipse. No change. Any help on resolving the hundreds of import errors and where to find all of these files that have moved since the instructions were written will be appreciated. I'm at a total loss. I really just need to get this thing to build. Thanks. Jerry - To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
Building James 3.3.0 in Eclipse
I'm trying to build the latest stable James 3.3.0 in Eclipse. -- The link to the 3.3.0 source zip on the downloads page is dead (https://www.apache.org/dyn/closer.lua/james/server/3.3.0/james-server-sources-3.3.0.zip) -- I figured out the correct link: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip and downloaded the zip. But the zip contains ONLY the primary source files and no pom.xml, etc files. -- I finally went to git and downloaded a zip that contained everything. -- But the fun just kept happening... I tried to import the project into Eclipse, but got over 500 errors. A large chunk of these errors was that every pom file has an invalid or missing a "dotGit" folder name. -- Also, I tried following the instructions here: http://mirrors.gigenet.com/apache/james/server/3.3.0/james-project-3.3.0-src.zip -- In the section titled "prepare projects" it says to copy files from: server/container/spring/src/main/config/james and from server/container/src/main/config/james Apparently, the folder structures have completely changed since that was written. Neither of those folder exist, and it wasn't obvious where they moved to. -- I know enough about eclipse to get by. I know nothing about maven (and for now would like to keep it as close to that way as possible). I just want to add a few tweaks to James 3.3 that I added back in v3b5 and get the latest james into production. I'm sure there's something missing or some setting wrong in Eclipse or in the Maven plug-in. I did a complete clean install of Eclipse (Java EE version) and Maven on a different machine just to make sure there were no issues with my original Eclipse. No change. Any help on resolving the hundreds of import errors and where to find all of these files that have moved since the instructions were written will be appreciated. I'm at a total loss. I really just need to get this thing to build. Thanks. Jerry
Re: "Getting Started" with JAMES using Docker
Hi Tellier,
Thanks for the response. You're suggestion is a perfect solution. Just
add the option to the quick start: if you know docker, do this way. If
you want do it the traditional way, here's the steps.
Thanks.
Jerry
On 8/30/2019 12:04 AM, Tellier Benoit wrote:
Hi Jerry,
Yes thanks to your report, the image had been updated. Thanks!
Just an unsolicited opinion for the James folks...
there is an implied assumption that the user understands docker and
has it installed. Nothing against docker. But it has not yet attained
ubiquity.
Well, thanks for the feedback.
IMO you see it the wrong way.
IF you have/are-familiar-with docker you can get a one
line try - which is awesome.
If you do not have it, you can follow one of the many non-docker tutorials.
CF: http://james.apache.org/server/install.html
Regarding "windows support" we are actively looking for some
contributors... Most of us don't have a license...
I'm not going to answer docker sysadmin related issues here.
Maybe the key output would be to enrich the **Get started with James**
section in order to also link "non-docker install options".
Would you agree with such a proposal?
Thanks again for your feedback, it's really helpful.
Best regards,
Benoit
On 30/08/2019 11:40, Jerry Malcolm wrote:
Hi, Aleksanda,
I really appreciate your information. I believe that someone realized
the image wasn't there and quietly got it posted overnight. When I
reran the command it worked, at least somewhat.
Just an unsolicited opinion for the James folks... I'm not sure that one
line command as the first thing a new user will see is quite ready for
prime-time. As I mentioned in my first post yesterday, there is an
implied assumption that the user understands docker and has it
installed. Nothing against docker. But it has not yet attained
ubiquity. My guess is a lot of new James users will have no idea what
it is or where to get it, either for Linux or Windows. And if that's the
case, there's no alternative pointer on that home page for non-docker
install. Next, the docker install failed for me because port 25 was
already in use since aws ec2 Linux automatically installs sendmail and
starts it up. Maybe all new James users will implicitly understand what
that error means and how to fix it. Finally, docker got to the point of
creating the dummy user ids and locked up. Had to kill my puTTY
session. No idea how to try to start/stop the james service and see how
much, if any of it, is installed and runable.
I'm not trying to be negative. That one line install is great if it
really works for the majority. But if a user (even a veteran of JAMES
for ~15 years like me) has the problems I've encountered, I would
strongly suggest a detailed followup page to go to when the one line
install crashes and burns. If I wasn't a seasoned user of James, and
rather a first-timer with this supposedly 'super easy' experience to
get it up and running, I might decide to go another direction for my MTA
needs. I think we can head that off with a pointer to more info and
what to do if things don't go right on that one-line install.
Thx
Jerry
On 8/29/2019 2:53 AM, Aleksandar Stoisavljevic wrote:
Hi Jerry,
I'll try to be brief and not to come into many details of how Docker is
working.
For that, I suggest that you go through some video materials and/or to
find
some
really extensive documentation on Internet (blogs, posts, Docker
documentation, books, etc.)
In the meantime, I'll try to explain what happened in your case.
Obviously you've installed Docker correctly as we can see from command
response.
There are actually two concepts in Docker that you have to distinguish:
Docker Image and
Docker Container.
Docker Container is "running version" of Docker Image.
When you stated:
[ec2-user@ip-172-31-47-236 ~]$ docker run -p "25:25" -p "143:143"
linagora/james-jpa-sample:3.3.0
It actually means that it will try to run Docker Container, listening on
host ports 25 and 143, and Container should
be of a Docker Image "linagora/james-jpa-sample:3.3.0".
That image, "linagora/james-jpa-sample:3.3.0", should be availabe either
locally or placed somewhere on Internet, so
Docker can access it and grab it. For this kind of Docker Image store,
usually people use Docker Hub (https://hub.docker.com/),
but there are also other Docker Repositories (private or public).
As you don't have it locally, that Docker Image
("linagora/james-jpa-sample:3.3.0"), therefore you've got that
information
in reponse:
"Unable to find image 'linagora/james-jpa-sample:3.3.0' locally".
At that moment, Docker Engine will try to grab that image from Docker
Hub.
But unfortunately, I don't see that 3.3.0 version of that image exists.
You can go to URL
(https://hub.docker.com/r/linagora/james-jpa-sample/tags)
for yourself and make sure that it doesn't exists.
I don't know how did you get that 3.3.0, maybe it is in some outdated
documentation, but I suggest that you try either
