Eclipse Development Environment - Java problems

[mc tan]

Hi,

I am trying to setup idempiere 7.1 environment but am getting a whole list of java problems in eclipse (see attached).

However, I have managed to run mvn verify successfully.

My environment is:

1) Windows 10

2) OpenJDK11.05

3) eclipse 2019-12

4) Idempiere 7.1

5) postgres 9.6

thanks

mc

[mc tan]

Forgotten about the list of plugin errors too  (see attached).

[Heng Sin Low]

this are warnings, not errors. it is safe to ignore.

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/35d183f4-22c0-4251-b3b5-468a6855a884%40googlegroups.com.

[mc tan]

HI HengSin,

I launched eclipse today and I am getting the attached Java errors. Rebuilding didnt work.

Do you know why this is so? Do I need to do maven verify again?

On Sunday, 1 March 2020 16:43:03 UTC+8, hengsin wrote:

this are warnings, not errors. it is safe to ignore.

On Sun, Mar 1, 2020 at 3:13 PM mc tan <gos...@gmail.com> wrote:

Hi,

I am trying to setup idempiere 7.1 environment but am getting a whole list of java problems in eclipse (see attached).

However, I have managed to run mvn verify successfully.

My environment is:

1) Windows 10

2) OpenJDK11.05

3) eclipse 2019-12

4) Idempiere 7.1

5) postgres 9.6

thanks

mc

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.

To unsubscribe from this group and stop receiving emails from it, send an email to idem...@googlegroups.com.

[StabilisOne]

After importing projects, our 'wiser' IDE may have made some changes to the workspace, so you can discard them. Mark all projects and by clicking on the selected area with the right mouse button selects the 'Replace With > HEAD Revision' on drop down menu.

[Chuck Boecking]

The abstract bean error also shows when you try to materialize using maven on a freshly clone repo.

Chuck

[mc tan]

Hi,

I have done the replace with > HEAD revision  but I cant seem to get rid of the Java errors. I have tried a 'Clean and rebuild' multiple times.

Anything else I am missing?

mc

[mc tan]

HI Chuck, yes this is a freshly cloned repo.

I followed the guide to do a mvn verify on my cloned source.

mc

[Heng Sin Low]

are you using linux ? if yes, you can also give this a try - https://github.com/hengsin/idempiere-dev-setup

otherwise, try clean all and full rebuild.

--

You received this message because you are subscribed to the Google Groups "iDempiere" group.

To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/8e6e21f9-93f4-492e-948c-9f09241f1938%40googlegroups.com.

[mc tan]

I am using windows.
I have been trying 'cleaning the project and rebuilding all'a few times. Sometimes it works but when i close eclipse and launch it again, the errors reappear. Now i cannot get rid of the java errors.

Am trying to reproduce the problem, will update again once i can find a pattern why this is happening.

[Chuck Boecking]

Something has changed on the internet. The simple act of (a) cloning and (b) maven verify fails on core 7.1, core 6.2, Logilite 6.2. I cannot get anything to build on a simple linux server.

[Carlos Antonio Ruiz Gomez]

Hi Chuck, 7.1 and master are running fine with mvn verify.

6.2 is broken AFAIK and unmaintained but you can check the changes that
were done to the pom.xml

Regards,

Carlos Ruiz



El 3/03/20 a las 12:37, Chuck Boecking escribió:

> Something has changed on the internet. The simple act of (a) cloning
> and (b) maven verify fails on core 7.1, core 6.2, Logilite 6.2. I
> cannot get anything to build on a simple linux server.

> --

[Chuck Boecking]

Hi Carlos,

I will check and report back. I tried the 7.1 branch unsuccessfully Monday evening; however, I will try again.

Chuck

[Chuck Boecking]

I performed the following on an ubuntu 18.04 server with openjdk 11.0.6:

• git clone ... idempiere71
  
• cd idempiere71
• git checkout release-7.1
• git status - just to make sure on release-7.1 branch/workingDir
  
• mvn verify -U
• ... this failed in the way previously described
  
• cd ..
• git clone ... idempieremaster
• cd idempieremaster
  
• git status - just to make sure on master branch/workingDir
  
• mvn verify -U
• ... this failed in the way previously described

This is a task that I have performed many many times. It just stared failing 4 days ago.

I hope this helps!

Chuck

[Ricardo Alexsander Santana]

Hi Chuck, I just tried here with a docker container and the build was successful.

You can reproduce my steps with docker:

docker run -ti adoptopenjdk:11-jdk-hotspot /bin/bash
apt-get update
apt-get install git
curl -o maven.tgz http://ftp.unicamp.br/pub/apache/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz
tar zxvf maven.tgz
export PATH=/apache-maven-3.6.3/bin/:$PATH
git clone https://github.com/idempiere/idempiere.git
cd idempiere/
git checkout release-7.1
git log

## Last Commit
## commit 2c3425c9cce44c6d8eb445e51616dab35834a4fc (HEAD -> release-7.1, origin/release-7.1)
## Author: Carlos Ruiz <car...@gmail.com>
## Date:   Wed Mar 4 17:16:26 2020 +0100
## IDEMPIERE-4191 Process to migrate storage provider (FHCA-1165)

mvn verify -U

[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  13:54 min
[INFO] Finished at: 2020-03-04T18:13:39Z
[INFO] ------------------------------------------------------------------------

Regards,

--
Ricardo Alexsander Santana
ralex...@gmail.com

--

You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/7104374c-3927-4fc1-bea2-a37f6960041d%40googlegroups.com.

[Heng Sin Low]

I try with fresh checkout of both 7.1 and master branch and it is working fine here.

Perhaps it is maven version ? what's your maven version (mvn --version) ?

--

You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/7104374c-3927-4fc1-bea2-a37f6960041d%40googlegroups.com.

[Chuck Boecking]

Ubuntu 18.04 is Maven 3.6.0.

I will try Ricardo's example using 3.6.3 and report back.

Regards,


Chuck Boecking
512.850.6068 (office and cell)
ch...@chuboe.com
ChuckBoecking.com
chuck.boecking (skype)

@ChuckBoecking

http://www.linkedin.com/pub/chuck-boecking/10/970/17b

You received this message because you are subscribed to a topic in the Google Groups "iDempiere" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/idempiere/sDfQPpZyg4c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to idempiere+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/CAC%3D6jXHit6Kk_iOUSASwTX3t5Yiv7fpDC%3D9cyh80LA4p96TLxQ%40mail.gmail.com.

[Synped Dev]

https://wiki.idempiere.org/en/Setting_up_Eclipse

Workspace settings

• In eclipse, navigate to Window > Preferences > General > Workspace
• set "Text file encoding" to "UTF-8" (if default is different)
• set "New text file line delimiter" to "Unix" (if default is different)
• navigate to Window > Preferences > Java > Compiler
• set Java > Compiler > Compiler compliance level to "11"

 

[Chuck Boecking]

I think it may have been particular server I was on. It was on an aws server, and sometimes the IP's are blocked from previous use. Here is what I found after creating a new server:

• master branch successfully built (with both maven 3.6.0 and 3.6.3)
  
• release-7.1 successfully built (with both maven 3.6.0 and 3.6.3)
• release-6.2 failed to build (with both maven 3.6.0 and 3.6.3)
  
• logilite-6.2 successfully built (with both maven 3.6.0 and 3.6.3)

Thank you to everyone who took the time to reply!

Regards,


Chuck Boecking
512.850.6068 (office and cell)
ch...@chuboe.com
ChuckBoecking.com
chuck.boecking (skype)

@ChuckBoecking

http://www.linkedin.com/pub/chuck-boecking/10/970/17b

[mc tan]

I have done all those, but it still didnt work.

I have also redone everything (uninstall eclipse, reinstall eclipse, redo mvn verify and reimport the project to eclipse).

Question: since these are java specific error, do I need to include all the classes in the build path?

[Carlos Antonio Ruiz Gomez]

Hi mctan,

You must be doing something wrong in the middle - or have a wrong prerequisite - or maybe your .m2 folder is bad.

As it seems it works for everybody except you, I would recommend you to explain step by step what you're doing with information about input, output, versions, etc.

When files are too big, you can upload them to one of the online "paste" services and share here just the link.

Regards,

Carlos Ruiz

El 6/03/20 a las 8:20, mc tan escribió:

[THIRUPATHI ENAGURTHI]

Dear McTan,

I am also experienced with lot of issues in idempiere repo and official document.

If you are using Linux OS, simple purge/remove all eclipse, database, idempiere folder in git ..and just simply follow this

https://github.com/hengsin/idempiere-dev-setup    ...@hengsin did ALL in one repo..

Regards,

Roy

--

You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/94e9102c-d0f3-4daa-8e3d-fedc9d48cd4b%40googlegroups.com.

[mc tan]

HI Carlos,

I have managed to get it working. I wiped out everything again and started afresh, this time making sure I read the guide slowly and properly.

There were 2 places where I think I might have made a mistake (in case someone has the same issue as me):

1) the version of the Git Client; I had git client 2.16 earlier (I installed Sourcetree initially, i think 2.16 was defaulted). I then reinstalled Git Client latest version 2.25

2) the workspace. I could have pointed it to the wrong location.

Thank you everyone for all your input and help

mc.

[StabilisOne]

Using that is such a topic... My psgsql remote data base migrated from 5.1 do not cooperate with perfectly built iD 7.1 within Eclipse 2019-12. BUT - Locally, fresh imported DB seed of iD DO COOPERATE and enable to develop Jetty without any problems. 

I am afraid there are some operations behind my control  using  forbidden date operation: "timestamp with time zone - integer", during setup the Jetty.  I have no idea why it subtracts some dates in the background, that cause few exceptions.

Context My OS Ubuntu 18:04 has psgql 9.6 default, and remote data base as well, so shouldn't be conflicted.

Appreciate help, advises regarding my migration or hidden, background sql queries. 

[Carlos Antonio Ruiz Gomez]

Probably the same described here?
https://groups.google.com/d/msg/idempiere/DeqZmqTU7Sk/__j-Nil5DwAJ




El 7/03/20 a las 14:38, StabilisOne escribió:

[mc tan]

Hi,

Anyone knows why I need to redo 'reload target' in order for me to get rid of the java errors (java errors recur everytime I launch eclipse - clean and rebuild does not work).

mc

[StabilisOne]

Checked and not confirmed - source dmp was made in Ubuntu 16.04 with pg 9.6 installed for  iD 5.1. 

Simultaneously fresh DB seed after pg_dump uses expression "FUNCTION" not "PROCEDURE" and it is working with my iD 7.1 built in Eclipse.

I am afraid that HousKeeping 7.1 performs forbidden psql operations from queries  predefined in java code. It regards only algebraic expression with days:

Created <= statement_timestamp() - 7

(Created+7) < statement_timestamp()

Created <= statement_timestamp() - 2

r.DateLastAction+s.TimeoutDays < SysDate

addmonths do not return any PSQLException

There are two other errors included in log 

 - first regards Scheduler.fillParameter DatePromised = DatePromised (DatePromised) java.lang.String - Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff] [96] 

 - second regards my plugin - it is not included in org.adempiere.base_7.1.0.qualifier

[StabilisOne]

Found and corrected sql queries in 'whereclause' column of 'adempiere.ad_housekeeping' table. Your java class is ok.

They had nor CAST neither INTERVAL operators.

but still can not find source of the following sql queries, that makes errors:

• DELETE FROM C_AcctProcessorLog WHERE C_AcctProcessor_ID=1000002 AND (Created+7) < statement_timestamp() 

• Scheduler.fillParameter: DatePromised = DatePromised (DatePromised) java.lang.String - Timestamp format must be yyyy-mm-dd hh:mm:ss

• DELETE FROM AD_Note WHERE AD_BroadcastMessage_ID IS NULL AND AD_Client_ID=0 AND (Created+7) < statement_timestamp()
• DELETE FROM AD_WorkflowProcessorLog WHERE AD_WorkflowProcessor_ID=100 AND (Created+7) < statement_timestamp()
• SELECT * FROM R_Request r WHERE r.DueType='5' AND r.Processed='N' AND AD_Client_ID=? AND EXISTS (SELECT * FROM R_RequestType rt WHERE r.R_RequestType_ID=rt.R_RequestType_ID AND (r.DateNextAction+rt.DueDateTolerance)
• DELETE FROM R_RequestProcessorLog WHERE R_RequestProcessor_ID=1000002 AND (Created+7) < statement_timestamp()
• DB.executeUpdate: DELETE FROM C_AcctProcessorLog WHERE C_AcctProcessor_ID=1000002 AND (Created+7) < statement_timestamp() 

   

W dniu niedziela, 8 marca 2020 14:46:49 UTC+1 użytkownik Carlos Antonio Ruiz Gomez napisał:

[Carlos Antonio Ruiz Gomez]

Did you check the link provided?  There are not wrong SQL queries - is an import database problem.

El 9/03/20 a las 17:17, StabilisOne escribió:

--

[StabilisOne]

After changes in HouseKeeping tab there is no errors regarding sql queries get from  'whereclause' column.

But if could tell me where can I find thoss export 'procedures' (mentioned in shiju01 issue) I would try to experiment with it.