IDempiere/FullMeeting20141001

⇐ Table of Contents | Full Meeting Minutes | Full Meeting 2014-10-01

CarlosRuiz: Good Morning
Edwin_Ang: Good night here :)
nmicoud: Bonjour ici :)
CarlosRuiz: I'm and will be in the process of testing the development branch - including next two weeks
Deepak: Is anybody have ever noticed issue like idempiere server management is not getting up
CarlosRuiz: Hi Deepak - any error in console?
CarlosRuiz: nmicoud, about your post in forums - do you mean the zoom on the "import bp" window?
nmicoud: yes
CarlosRuiz: the first field there points to the imported bp
CarlosRuiz: there is no zoom across because the key (i_bpartner_id) is not a foreign key in other tables
Deepak: No Error
nmicoud: ho... i though the zoom across search for windows where c_bpartner_id was used
CarlosRuiz: yep - that's if you zoom across from the bp window
CarlosRuiz: but the i_bpartner has different id
tbayen: Hi everybody :)
CarlosRuiz: Hi tbayen
nmicoud: ok
tbayen: Carlos, did you already care about IDEMPIERE-2180? It seems I made a mistake and hieplq saved my soul with a second patch.
Deepak: Carlos,No error but when brows to /idempiereMonitor,it says could not display page
CarlosRuiz: haven't seen that behavior before Deepak
CarlosRuiz: tbayen, will take a look
CarlosRuiz: :-) you were thinking in java when wrote the shell :-)
Deepak: Carlos, Is any tentative date for releasing idempiere 3.0?
CarlosRuiz: not yet - I'm planning a release probably ending october - not sure if it will be r3 or r2.1
hieplq: hi CarlosRuiz, relate to script, please also look IDEMPIERE-2201
CarlosRuiz: hieplq, did you modify the idempiere_RedHat.sh script - or is it the committed?
hieplq: no. but it's quick. i can do it now
hieplq: i don't know about this action "cp ...". why must do this copy
hieplq: just ignore warning, everything still work nomal
CarlosRuiz: seems like saving a backup of the env
CarlosRuiz: but I see in the redhat script that it changes to IDEMPIERE_HOME directory
CarlosRuiz: su $IDEMPIEREUSER -c "cd $IDEMPIERE_HOME;$IDEMPIERE_HOME/idempiere-server.sh &> $LOGFILE &"
CarlosRuiz: before running the server it does "cd $IDEMPIERE_HOME" - so, it must not complain about that
hieplq: let me check it
CarlosRuiz: or is it the setup which throws the error?
hieplq: hi CarlosRuiz "source $ENVFILE" is called before cd, because warning is display
CarlosRuiz: ah I see
CarlosRuiz: in the debian script there is a cd before that line
hieplq: thanks. i will test in centos and report it late
infoder: Hi
infoder: i get this error in jenkins after building
infoder: Target /var/lib/jenkins/workspace/MSConnect/MyCustom/build-target-platform.target has no containers
infoder: and the build FAILURE
tbayen: Can you have a look at IDEMPIERE-659. It is quite old and I use it for a long time but I realized that it is not in trunk.
tbayen: ?
CarlosRuiz: :-) I haven't integrated my own patch
frankie-figz: Hey guys, how should I go about requesting a plug-in and documenting the blue-print / work related to it ?
tbayen: What do you mean by "requesting"? Who will write the plugin? You?
frankie-figz: Well, initially their is an idea which is documented.
frankie-figz: Then others look at the idea and give feed back
frankie-figz: Come to an agreement and we start working
frankie-figz: I do not have the skill to write it all.. and would be willing to sponsor it
frankie-figz: But I would like the work to be transparent and collaborative
tbayen: Basically for new thoughts to be discussed you can first write a message to the google group forum and let people answer. After you got some feedback you can create a page in the wiki about it. If you are lucky you found some people that join your effort and you can finish the idea. Then you can write your code or pay someone to do it.
tbayen: The forum and the wiki are both free for everyone. Just join them and start whatever you think is the right way. There are no rules to stop you. :-)
frankie-figz: What about creating a new project in the jira.idempiere page called "idempiere-plugins" to be used for new plug-ins and/or suggesting improvements/bugs of existing plugins ?
frankie-figz: The forum and wiki are nice but I feel it may hamper creativity and tracebility
tbayen: In principle that is not a bad idea. But up to now there is no plugin that is of enough interest for the whole community to do that. Most plugins belong to one single programmer and are not collaborative.
tbayen: In my personal opinion if you have an idea for a plugin that is worthful for a broader audience then you can create a jira ticket for that to collect all things about this plugin. That may be a start.
tbayen: What is your plugin idea about?
frankie-figz: It is related to the production of goods
tbayen: A real description for a whole plugin concept and documentation will not fit well in the jira. A wikipage is better for that. JIRA is more for small bugs and issues or to say something like "We need a plugin for foo because of bar and I made a broader description, documentation, time plan and sponsoring offer at wiki.idempiere.org/.... "
frankie-figz: Alrighthy, I'll go for it.
frankie-figz: On a related note, have you looked at the create purchase order from requisition plug in ?
tbayen: I like wiki pages for that because they are "alive". The hurdle for other community members to change and extend things is a bit lower.
tbayen: Said that is is really up to you which way you like. Do whatever you want and tell us on every way you want. Your contribution is welcome! :-)
tbayen: Nope. I am not using production. Sorry.
hieplq: hi tbayen, how i know a new wiki page is created? i don't see any way to setup notify.
CarlosRuiz: hieplq, I setup a news reader with feedly
CarlosRuiz: several indeed - one for main wiki, another for english, another for spanish
tbayen: I use a newsreader. And there is also a page with changes.
hieplq: thanks for share, i will try it.
tbayen: I use the same rss/atom newsreader for trunk changes and jira tickets. (Thanks Carlos for this hint)
CarlosRuiz: castle tip :-)
tbayen: I use not the aggregator webpage you showed me but a rss reader on my android phone. So I am informed everywhere when someone dares to change my wiki pages.
frankie-figz: For a suggestion of improvement of an existing plug-in should I use the wiki page where it was created ?
frankie-figz: or start with a message in the forum ?
frankie-figz: or both for redundancy ?
Edwin_Ang: better you write at wikipage and then announce in the forum
CarlosRuiz: frankie-figz, for that I use the talk page of the wiki page
tbayen: That's not easy to answer. I think the wiki page is not read by many people. Personally I prefer the forum if I want feedback to create a new idea and the wiki if I want to manifest a finished idea for the future. If it is a longer article I would do it always in the wiki and give a link with a tldr in the forum.
frankie-figz: Thanks fellows, I will proceed as suggested
frankie-figz: Have a good one !
CarlosRuiz: Hi mand1nga
mand1nga: Hello :)
mand1nga: greetings from Argentina!
aguerra: Good morning have all !!!
CarlosRuiz: Hi aguerra
CarlosRuiz: I'm going to disconnect for some minutes - ttyl

...

infoder: yes
infoder: i use buckminster
infoder: importtargetdefinition -A '${WORKSPACE}/org.adempiere.mine.feature/build-target-platform.target'
aguerra: Good morning Carlos we are opening operations in Panama and we want to put ourselves to orders. Greetings !!!
CarlosRuiz: Good - I wish you luck there aguerra
aguerra: thk a lot!!!
allgood: hi folks
allgood: how can i access the osgi> prompt of a running idempiere instance?
allgood: just found... with telnet!
hieplq: CarlosRuiz_away, commit of IDEMPIERE-2180 miss ";" at "]; then"
CarlosRuiz_away: ah, my fault
hieplq: @CarlosRuiz, your patch for IDEMPIERE-2201 is working for centos. no warning, backup file is created. please commit it.
CarlosRuiz: thanks hieplq for the test