Re: 3.0.0 on Linux
Garry, A shorter explanation of what's happening trying to build 3.3... I decided to start totally from scratch on a new machine. I installed JDK 1.8. Next I installed the latest enterprise developers version of Eclipse. Next I used the regular import-->git project, clone uri from https://github.com/apache/james-project.git. I deselected all branches except 3.3.x and downloaded. Finally I then did 'import-->maven-->existing maven project and pointed it to the git download folder. During the import it displayed 201 errors: "Plugin execution not covered by lifecycle configuration", 300+ warnings saying something about 'progress and finally did a popup about not finding mojo in the tools.jar file. This takes about 5 minutes to reproduce. If these steps are wrong to download and build 3.3, that should be obvious to someone. If these steps are right, can someone try the same process and see if they get the same errors? If they do, then someone who knows something is going to have to explain it. I think it's just you and me on this forum now. But hopefully, somebody from JAMES development will come back and finally explain what's happening. On 9/9/2019 11:38 AM, Jerry Malcolm wrote: Garry, I'm all for taking the shortest route to the latest code. Here is my full saga from a previous post: 1) On a clean eclipse workspace, File-->Import-->Git --- I selected "clone URI" and entered the James GIT clone URI: https://github.com/apache/james-project.git 2) I selected the 3.3.x branch (I guess that's what I want... (??) ) and said to also clone submodules. It downloaded to a folder. It created an eclipse project/package named james-server. But the project only had 3 files: model.di, model.notation, and model.uml. 3) On a whim, I decided to import again using "Maven existing project" and pointed to the extracted folder. That seemed to work for the most part. It initially gave me 10 errors saying "Plugin execution not covered by lifecycle configuration" and 16 more errors with "Project configuration not up to date with pom.xml". All with varying pom.xml files. I did a "quick fix" and it got rid of the 'not up to date' errors. I googled the lifecycle error and it said to edit all of the pom.xml files and add tags around the plugin tags. I tried in on a couple of the pom.xml files, and it did fix the errors (???). I then did a build, and it added one more error, something about an invalid mojo tag in a pom descriptor. Just for fun, I did a clean build, and that was a huge mistake. I now have 340 errors where it can't resolve DTOs in FlagsTest, EventSerializer in EventDispatcher, etc. Apparently 'clean' wipes out source files as well. Or it wipes out class files that are not part of the full build. So that's where I am. I can edit a bunch of pom.xml files and add tags. I can hopefully figure out how to fix mojo. And I can hope to remember to NEVER do a clean build again. But this just doesn't seem right that I have to go in and modify a bunch of source files just to get a clean build from a ship-level source package. I have zero confidence if I have to make all of these change that I really have an 'official' 3.3.x James. Suggestions? Where did I stray from the correct path? I'm beginning to feel like I belong in the class with the slow kids On 9/9/2019 11:13 AM, Garry Hurley wrote: Let's go to your James 3.3.0 problem. I ran into some issues with James early on, and that is why I signed up on this list. What is the issue with 3.3.0? What is the error you are getting? On Sun, Sep 8, 2019 at 2:20 PM Jerry Malcolm wrote: Hi Garry, You missed my point. I've been trying to get help on building 3.3.0 for over a week with no response (see my long list of posts). Since I can't get anyone to respond to my 3.3.0 build problem, I had to look for an alternative. I currently have a 3.0.0 beta 5 install that has worked for years on a Windows server. My only alternative until I get my 3.3.0 build problems resolved is to move that v3b5 to Linux since my windows server is going away. I have added custom code. So I can't just download the binaries. I would love to move to 3.3.0. But until I can figure out my build problems and/or get someone to respond to my questions, this is my only choice. Now my current ancient v3b5 that worked on Windows fails on Linux with OpenJPA issues (see prev post). I realize this is a completely volunteer forum. But I'm dying here. I've got to get some version of james running on my AWS Linux box. Can someone please find time to help? I'll take help on my 3.0.0 b5 OpenJPA issue and/or my 3.3.0 Eclipse build problems... just SOMETHING. Thx Jerry On 9/8/2019 2:31 AM, Garry Hurley wrote: 3.0.0 is kinda old. In fact, IIRC, it never made it out of Beta stage. 3.3.0 works and is stable, so unless you have some reason to use an older version, you should consider updating. Sent from
Re: 3.0.0 on Linux
Garry, I'm all for taking the shortest route to the latest code. Here is my full saga from a previous post: 1) On a clean eclipse workspace, File-->Import-->Git --- I selected "clone URI" and entered the James GIT clone URI: https://github.com/apache/james-project.git 2) I selected the 3.3.x branch (I guess that's what I want... (??) ) and said to also clone submodules. It downloaded to a folder. It created an eclipse project/package named james-server. But the project only had 3 files: model.di, model.notation, and model.uml. 3) On a whim, I decided to import again using "Maven existing project" and pointed to the extracted folder. That seemed to work for the most part. It initially gave me 10 errors saying "Plugin execution not covered by lifecycle configuration" and 16 more errors with "Project configuration not up to date with pom.xml". All with varying pom.xml files. I did a "quick fix" and it got rid of the 'not up to date' errors. I googled the lifecycle error and it said to edit all of the pom.xml files and add tags around the plugin tags. I tried in on a couple of the pom.xml files, and it did fix the errors (???). I then did a build, and it added one more error, something about an invalid mojo tag in a pom descriptor. Just for fun, I did a clean build, and that was a huge mistake. I now have 340 errors where it can't resolve DTOs in FlagsTest, EventSerializer in EventDispatcher, etc. Apparently 'clean' wipes out source files as well. Or it wipes out class files that are not part of the full build. So that's where I am. I can edit a bunch of pom.xml files and add tags. I can hopefully figure out how to fix mojo. And I can hope to remember to NEVER do a clean build again. But this just doesn't seem right that I have to go in and modify a bunch of source files just to get a clean build from a ship-level source package. I have zero confidence if I have to make all of these change that I really have an 'official' 3.3.x James. Suggestions? Where did I stray from the correct path? I'm beginning to feel like I belong in the class with the slow kids On 9/9/2019 11:13 AM, Garry Hurley wrote: Let's go to your James 3.3.0 problem. I ran into some issues with James early on, and that is why I signed up on this list. What is the issue with 3.3.0? What is the error you are getting? On Sun, Sep 8, 2019 at 2:20 PM Jerry Malcolm wrote: Hi Garry, You missed my point. I've been trying to get help on building 3.3.0 for over a week with no response (see my long list of posts). Since I can't get anyone to respond to my 3.3.0 build problem, I had to look for an alternative. I currently have a 3.0.0 beta 5 install that has worked for years on a Windows server. My only alternative until I get my 3.3.0 build problems resolved is to move that v3b5 to Linux since my windows server is going away. I have added custom code. So I can't just download the binaries. I would love to move to 3.3.0. But until I can figure out my build problems and/or get someone to respond to my questions, this is my only choice. Now my current ancient v3b5 that worked on Windows fails on Linux with OpenJPA issues (see prev post). I realize this is a completely volunteer forum. But I'm dying here. I've got to get some version of james running on my AWS Linux box. Can someone please find time to help? I'll take help on my 3.0.0 b5 OpenJPA issue and/or my 3.3.0 Eclipse build problems... just SOMETHING. Thx Jerry On 9/8/2019 2:31 AM, Garry Hurley wrote: 3.0.0 is kinda old. In fact, IIRC, it never made it out of Beta stage. 3.3.0 works and is stable, so unless you have some reason to use an older version, you should consider updating. Sent from my iPhone On Sep 8, 2019, at 12:07 AM, Jerry Malcolm wrote: I'm still waiting and hoping somebody can please explain why I can't build 3.3.0 on Eclipse. (See my other thread). But I'm on a deadline. y windows server is going away soon and I HAVE to get a mail solution onto AWS. (ANYBODY?? PLEASE HELP!) So in meantime, plan-B is to copy my current ancient v3b5 installation off of my Windows server to my AWS Linux instance. Since James is 100% java (good ol' "write once -- run anywhere"..., right?) I figured I could just copy the entire James installation folder and fix a couple of backslashes in file paths in config files, and it should run perfectly. Wrong-o. I literally copied the folder precisely, and changed to run.sh instead of run.bat. After a few expected startup messages, I get a bunch of OpenJPA warnings, followed by a bunch of errors telling me foreign keys are missing from my database, etc. (See log excerpt below). I went back to the running Windows instance. There is no reference anywhere in the Windows James log to jpa. Since the conf and lib folders are identical (as far as I can tell) between these two instances, I'm baffled. Why is OpenJPA getting upset with the Linux install and not the
Re: 3.0.0 on Linux
Let's go to your James 3.3.0 problem. I ran into some issues with James early on, and that is why I signed up on this list. What is the issue with 3.3.0? What is the error you are getting? On Sun, Sep 8, 2019 at 2:20 PM Jerry Malcolm wrote: > Hi Garry, > > You missed my point. I've been trying to get help on building 3.3.0 for > over a week with no response (see my long list of posts). Since I can't > get anyone to respond to my 3.3.0 build problem, I had to look for an > alternative. I currently have a 3.0.0 beta 5 install that has worked > for years on a Windows server. My only alternative until I get my 3.3.0 > build problems resolved is to move that v3b5 to Linux since my windows > server is going away. I have added custom code. So I can't just > download the binaries. I would love to move to 3.3.0. But until I can > figure out my build problems and/or get someone to respond to my > questions, this is my only choice. Now my current ancient v3b5 that > worked on Windows fails on Linux with OpenJPA issues (see prev post). > > I realize this is a completely volunteer forum. But I'm dying here. > I've got to get some version of james running on my AWS Linux box. Can > someone please find time to help? I'll take help on my 3.0.0 b5 OpenJPA > issue and/or my 3.3.0 Eclipse build problems... just SOMETHING. > > Thx > > Jerry > > On 9/8/2019 2:31 AM, Garry Hurley wrote: > > 3.0.0 is kinda old. In fact, IIRC, it never made it out of Beta stage. > 3.3.0 works and is stable, so unless you have some reason to use an older > version, you should consider updating. > > > > Sent from my iPhone > > > >> On Sep 8, 2019, at 12:07 AM, Jerry Malcolm > wrote: > >> > >> I'm still waiting and hoping somebody can please explain why I can't > build 3.3.0 on Eclipse. (See my other thread). But I'm on a deadline. My > windows server is going away soon and I HAVE to get a mail solution onto > AWS. (ANYBODY?? PLEASE HELP!) > >> > >> So in meantime, plan-B is to copy my current ancient v3b5 installation > off of my Windows server to my AWS Linux instance. Since James is 100% java > (good ol' "write once -- run anywhere"..., right?) I figured I could just > copy the entire James installation folder and fix a couple of backslashes > in file paths in config files, and it should run perfectly. Wrong-o. I > literally copied the folder precisely, and changed to run.sh instead of > run.bat. After a few expected startup messages, I get a bunch of OpenJPA > warnings, followed by a bunch of errors telling me foreign keys are missing > from my database, etc. (See log excerpt below). I went back to the running > Windows instance. There is no reference anywhere in the Windows James log > to jpa. Since the conf and lib folders are identical (as far as I can tell) > between these two instances, I'm baffled. Why is OpenJPA getting upset > with the Linux install and not the Windows install. My first thought was > something with case-sensitive file names. But I can't find any of those > situations. I'm not familiar with OpenJPA configuration. So these errors > mean nothing to me. What did I do wrong? (BTW... both instances point to > the same db... so I know the database is not corrupt). > >> > >> Can anybody help with this problem (or better... help me with the 3.3.0 > Eclipse disaster... I don't want to remain on v3b5 forever). > >> > >> Thx. > >> > >> Log entries: > >> > >> INFO 02:35:01,219 | james.dnsservice | Adding autodiscovered search > path ec2.internal. > >> INFO 02:35:01,220 | james.dnsservice | DNS Server is: 172.31.0.2 > >> INFO 02:35:01,226 | james.dnsservice | Registered cache, resolver and > search paths as DNSJava defaults > >> 185 James INFO [main] openjpa.Runtime - Starting OpenJPA 2.2.1 > >> 215 James INFO [main] openjpa.jdbc.JDBC - Using dictionary class > "org.apache.openjpa.jdbc.sql.MySQLDictionary". > >> 630 James WARN [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > >> 631 James WARN [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed > in the openjpa.MetaDataFactory configuration property could not be loaded > by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > >> 723 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage" listed in the > openjpa.MetaDataFactory configuration property could not be loaded by > sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > >> 723 James INFO [main] openjpa.MetaData - The class > "org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage" listed > in the openjpa.MetaDataFactory configuration property could not be loaded > by sun.misc.Launcher$AppClassLoader@764c12b6; ignoring. > >> 735 James INFO [main]
