IDempiere/FullMeeting20150311

From WikiQSS

Table of Contents | Full Meeting Minutes | Full Meeting 2015-03-11

CarlosRuiz: Good Morning
nmicoud: Bonjour
CarlosRuiz: will be checking the peer review queue :-)
CarlosRuiz: .
ocurieles: Good Morning :D
nmicoud: Could you have a rapid look at https://idempiere.atlassian.net/browse/IDEMPIERE-2512 (there is no patch only a possible solution)
CarlosRuiz: nmicoud, that must be happening in other points where SQL is allowed
carlos__: strange my old connection as CarlosRuiz is zombie
carlos__: nmicoud, that must be happening in other points where SQL is allowed
CarlosRuiz: nmicoud, that must be happening in other points where SQL is allowed
carlos__: easier workaround maybe is to use chr(64)
nmicoud: ah i see
CarlosRuiz: can you test it ? @SQL=SELECT 'nmicoud'||chr(64)||'tgi.fr' FROM DUAL
nmicoud: not ATM, (at a meeting) but ASAP
CarlosRuiz: ok, will annotate it in ticket
nmicoud: ok, thanks
ocuriele_: The Cash Plan is used on iDempiere ? or come from ADemDead?
aguerra: Buenos días a todos
aguerra: Hello everybody
CarlosRuiz: Hi Alejandro
CarlosRuiz: ocuriele_, the cash plan is deprecated in iDempiere
CarlosRuiz: ah sorry
CarlosRuiz: cash journal is deprecated in iDempiere - cash plan is a new feature - I think is not present in adempiere
CarlosRuiz: I mean - cash flow -> http://www.adempiere.com/FS02_Cash_Flow
CarlosRuiz: don't know if you're looking for that one?
ocuriele_: Yes @CarlosRuiz, let's me make a review
ocuriele_: Some guide for use two Chart of Accounts
ocuriele_: ?
CarlosRuiz: I don't remember a guide about that - advanced functionality
ocuriele_: mm - I imported the new account Element and I created the new Accounting Schema but the importer don't put the default account
ocuriele_: for this Schema
tbayen: Hi CarlosRuiz I heard about an earthquake in the news. Is everything ok for you?
ocuriele_: http://ecodiario.eleconomista.es/telecomunicaciones-tecnologia/noticias/6543474/03/15/Colombia-hit-by-61-magnitude-earthquake-felt-in-several-cities.html
ocuriele_: :/
CarlosRuiz: thanks tbayen_ and ocuriele_ - everything fine here - it moved a lot the buildings
tbayen_: I hoped that everything is fine with your family. :)
tbayen_: I heard that some airports closed... I hope that Diego will find his way nevertheless.
CarlosRuiz: Bogota airport is working fine
tbayen_: Is he prepared for the big adventure?
CarlosRuiz: yep - bags ready
tbayen_: Di you give him all instructions which iDempiere projects are most urgent to be done? And that he has to convince his new boss to agree with your plans?
CarlosRuiz: hahaha - I can't do that - don't know your priorities
tbayen_: I am sure there will be time to do some sponorings in the sense of the community needs. ;-)
CarlosRuiz: that sounds great
JanThielemann: hey guys, i'm trying to build idempiere 2.1 via jenkins but i always get this error: ERROR: org.eclipse.core.runtime.CoreException: /var/lib/jenkins/workspace/iDempiere2.1/org.adempiere.server-feature/product.ant:23: Java returned: 137
JanThielemann: do you know why? because on the same server i build my 2.0 and theres no problem at all
JanThielemann: im using java 7 and buckminster 4.2
CarlosRuiz: JanThielemann, you can open a user on ci.idempiere.org and check what is different there
CarlosRuiz: ah - I think I have that option disabled - I can create a user for you
tbayen_: The ant script does not write its error messages. I had a similar issue in IDEMPIERE-1618. There is a patch to see the erroro messages. afair you can also see the error log in the logfile of your eclipse installation.
JanThielemann: carlosruiz i already have a user :)
JanThielemann: jthielemann
JanThielemann: i'll check it out
tbayen_: Do you know about error 137? (http://stackoverflow.com/questions/18524574/java-program-terminate-with-java-result-137) That sounds like you have not enough resources or such
JanThielemann: i have this wired behaviour. i change the configuration to use buckminster 3.7 ->build fails. I switch back to 4.2 -> build succeeds. A second build with 4.2 will then fail :/
tbayen_: A rule that I learned long ago is to delete ~/buckminster.output everytime I change something.
tbayen_: This rule solves every single "error:13" for me. Perhaps it applies also to "error:137". ;)
JanThielemann: tbayne: first line of my build: rm -rf ${WORKSPACE}/buckminster.output/ ${WORKSPACE}/buckminster.temp/ ${WORKSPACE}/targetPlatform/
tbayen_: hmmm.... sorry. In german I would say "then my latin is at its end" ;)
JanThielemann: tbayen_: the translation is "I am at my wits end" :)
tbayen_: But that's not so funny. :-D
tbayen_: I gtg. See you later. And CarlosRuiz: say good luck to Diego! :-)
CarlosRuiz: thanks tbayen_
CarlosRuiz: nmicoud, what do you mean "in a process" on IDEMPIERE-2512 ?
nmicoud: when you launch the process from the menu
CarlosRuiz: the default for a parameter?
nmicoud: yes
CarlosRuiz: must do the same - let me test it ...
CarlosRuiz: testing with Recurring Run > Parameter Comment
CarlosRuiz: it worked here
nmicoud: wow
CarlosRuiz: in default from a prm worked also without the chr
nmicoud: mean you use same param in scheduler and process ?
CarlosRuiz: ah - just tested default prm in process
CarlosRuiz: don't understand the case?
nmicoud: try the request email processor ; email adress param : launch it through in a scheduler ; with chr(64) is ok launch it in a process ; with chr(64) is not ok
CarlosRuiz: yes - the scheduler must be doing Env.parseContext - so it requires the chr
CarlosRuiz: and solving the default doesn't require it - but work both ways
nmicoud: means that @SQL=SELECT 'nmicoud'||(chr64)||'tgi.fr' FROM DUAL works for scheduler and process (from menu) ?
CarlosRuiz: yep - in my test it worked as a default from menu (tested with recurring process
nmicoud: that's weird ; need to retest then
mhernandezve: Hi partners!!
orlandocurieles: HI @mhernandezve
orlandocurieles: @CarlosRuiz in the Tree Maintenance i can't see the search box in demo.idempiere.com
orlandocurieles: i need close the form and open again to see correctly
CarlosRuiz: Hi Miguel
CarlosRuiz: yes orlandocurieles - I've seen that bug since some time - also in 2.1
mhernandezve: Hi CarlosRuiz
mhernandezve: Hi orlandocurieles
CarlosRuiz: going out - c u then