How to properly update the idempiere development environment with changes from the upstream repository?

57 views
Skip to first unread message

Andreas Sumerauer

unread,
Jul 17, 2020, 4:23:54 AM7/17/20
to iDempiere
Hi community,

I have now several times killed my idempiere development environment simply by pulling the changes from the upstream repository.
It just won't compile afterwards and I had to start again with a complete fresh clone. (I have not yet done that this time though)

This time I found that org.adempiere.ui.zk and org.idempiere.webservices won't build.
It seems like eclipse has trouble finding some exported class path entries.
After running project context menu > maven > update project
all lines beginning with
 <classpathentry exported="true" ...
are removed from the classpath.
(The projects also won't build when the lines are still there)

What are the recommended steps to update the local repository?
What am I doing wrong?

Thanks!

Andreas

Heng Sin Low

unread,
Jul 17, 2020, 4:48:14 AM7/17/20
to idem...@googlegroups.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/1ff2d360-b8a7-4b9e-b121-ea63f633957bo%40googlegroups.com.

Andreas Sumerauer

unread,
Jul 17, 2020, 5:43:58 AM7/17/20
to iDempiere
Thanks Hengsin for the fast reply,

I don't believe that my problem is with the git workflow. Instead I suspect it is maven related.

Here is what I do:

git checkout master
git pull upstream master


After that eclipse shows these errors:
Project 'org.adempiere.ui.zk' is missing required library: 'lib/ckez.jar'
Project 'org.adempiere.ui.zk' is missing required library: 'lib/daisydiff.jar'
Project 'org.adempiere.ui.zk' is missing required library: 'lib/owasp-java-html-sanitizer.jar'
Project 'org.idempiere.webservices' is missing required library: 'lib/idempiere-xmlbeans.jar'

When I try to rebuild the workplace I obviously get a heap of follow up errors.

Are there any steps that need to be taken after running git pull ... and before rebuilding the workspace?
This problem occurs when pulling the changes from upstream into my feature branch and also when I pull them into master without any  custom modifications.
As already said: using a fresh clone works just fine.

Andreas






Am Freitag, 17. Juli 2020 10:48:14 UTC+2 schrieb hengsin:
On Fri, Jul 17, 2020 at 4:23 PM Andreas Sumerauer <reua...@gmail.com> wrote:
Hi community,

I have now several times killed my idempiere development environment simply by pulling the changes from the upstream repository.
It just won't compile afterwards and I had to start again with a complete fresh clone. (I have not yet done that this time though)

This time I found that org.adempiere.ui.zk and org.idempiere.webservices won't build.
It seems like eclipse has trouble finding some exported class path entries.
After running project context menu > maven > update project
all lines beginning with
 <classpathentry exported="true" ...
are removed from the classpath.
(The projects also won't build when the lines are still there)

What are the recommended steps to update the local repository?
What am I doing wrong?

Thanks!

Andreas

--
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.

Heng Sin Low

unread,
Jul 17, 2020, 6:19:09 AM7/17/20
to idem...@googlegroups.com
that's what I usually do as  well and I've not encountered similar issues thus far.

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/e85f707f-5d18-4cb6-846d-feb17b90033do%40googlegroups.com.

Diego Ruiz

unread,
Jul 17, 2020, 6:53:18 AM7/17/20
to iDempiere
Hi Andreas,

It happens to me sometimes as well. Last time I experienced this issue was after a commit from Hiep that modified some platform files.

In such cases running
- mvn clean verify
- refreshing the maven files
- reloading the target platform

in that order, solves the issue for me.

Best Regards,
Diego Ruiz

Andreas Sumerauer

unread,
Jul 17, 2020, 7:03:54 AM7/17/20
to iDempiere
Thanks Hengsin for the update.

Since my local repository was corrupted anyway I have now done some experiments:

- git pull upstream master -> this is where the errors show up
- mvn verify

then in eclipse:
- Project > uncheck Build Automatically
- reload Target platform
- Project explorer > select all maven projects, then rightclick > Maven > Update Project
- Project > check Build Automatically

It seems like that did the trick. I do not really know what I have done and maybe not all of the steps were required.
Still I am happy to be able to continue working without having to restart from a fresh clone.

If anybody has an Idea of what might have caused the hickup I will be happy to know.

I also think I need an introduction into maven and the maven eclipse plugin. Are there any good resources available?
I really do not want to know all the ins and outs of the system.
I just need a little bit of background to better understand what is happening under the hood.

Thanks!

Andreas

Andreas Sumerauer

unread,
Jul 17, 2020, 7:16:00 AM7/17/20
to iDempiere
Thanks Diego,

Good to know that the error was not on my side. It seems like I found almost the same solution that your recommended while You were writing your answer.
I will surely include the mvn clean step when it happens again.
From what you write it looks like my update project step is not required.

Maybe somebody knowledgeable can add this fix to the docs. (wiki > download the code > keeping up to date)
I would do it but since I am not familiar with maven I would rather not add my half baked wisdom to the wiki.

Thanks!

Andreas
Reply all
Reply to author
Forward
0 new messages