Re: Summary of ApacheCon-Eu conference Why ofbiz-extra

2012-11-28 Thread olivier Heintz
The mains important point are :
- This is one way to facilitate Contribution to OFBiz  *AND* Quality
enhancement
- Share contribution, even if it's not for all ofbiz user, even if it
not follow all current bests practices,  can help
- We need to have a clear definition of what are the Quality criteria
fro Apache-OFBiz
- We need to have a clear process for contribution evaluation and status
and life process

The main comment done by the attendees :
- It's very important to have a addon repository in Apache-OFBiz

The next steps should be :
- to write 1,2 or 3 wiki pages for OFBiz choices (writing in a consensus
way);
- to give visibility on new help integration
- to give visibility on functional (or user-interface) test solution
adopt by OFBiz
- to start a process on addon manager evaluation
- to start to give visibility to ofbiz-extra




Le 27/11/2012 11:28, olivier Heintz a écrit :
 ApacheCon-Eu presentation is now available,
 http://archive.apachecon.com/eu2012/presentations/07-Wednesday/PR-Community/aceu-2012-ofbizextra-addons_what-constrains-for-each-repository.pdf


 I propose below a short summary (only the main points) to be able to
 start community discussion.

 I will do a second mail for comments about this presentation.

 Agenda :
 ==
 - Why to use OFBiz-extra rather than to include it in Apache-OFBiz?
 - the ofbizextra-addons Goals
 - Rules and Constraints by Repository
 - Process to change
 - Conclusions

 Why to use OFBiz-extra rather than to include it in Apache-OFBiz?
 =
 - Slim-down process in Apache-OFBiz project
 - Several technologies for the same function
 Ex : jasperReport, Birt, …
 - Licence
 Ex : GPL
 - Personal decision versus Apache-OFBiz PMC decision
 - Work in progress
 - OOTB solutions for dedicated Business

 ofbizextra-addons Goals
 ===
 - Facilitate and simplify :
 * Contribution to OFBiz
 * Using / Testing added functions
 * Community and/or OFBiz-committer validation
 - Increase :
 * Quality and use of Best Practice
 * OFBiz functionalities without weighing down kernel
 * Propose OOTB dedicated solutions for users

 Rules and Constraints by Repository
 ===
 - 3 repository
 - ofbiz-extra-addons-dev
 * This project is open for all contributors who want to create or
 maintain apache-ofbiz addons.
 * This project has no quality or best practice control, each contributor
 should try to do the best he can.
 * When a user uses an existing addon in this repository, he should
 assume risks, but but in many cases it will help him.
 - ofbiz-extra-addons-incubator
 * This project is open for all Apache-OFBiz addons that should become :
 + part of ofbiz addons labeled Quality repository (ofbizextra-addons),
 + or part of Apache ofbiz project.
 * Addons of this project are in a Quality, Best Practice evaluation and
 enhancement.
 * There is, at least, one organization / person that is involved to
 solve bugs or to offer support services for this addon.
 - ofbiz-extra-addons
 * Repository of the addons labeled Quality
 * In the future, a similar repository can be created as an Apache-OFBiz
 sub-project (for addons with Apache2 licence)
 * There is, at least, one organization / person that is committed to
 offer support services for this addon.
 * Addons
 + Have a complete user help
 + are included in a Continuous Integration Job :
 = Installation test
 = Unit test : Junit
 = Functional test : Selenium

 Addon Quality status page
 (http://code.google.com/a/apache-extras.org/p/ofbiz-extra-addons-incubator/wiki/modelAddonQuality)
 =
 - Update history
 * contributor, date, version, indicator, description
 * reviewer, date, version, indicator, description
 - Base Files
 * add-on.xml, date, version, status, indicator
 * maintainer in add-on.xml, date, version, status, indicator
 * ivy.xml, date, version, status, indicator
 * addon help (English), date, version, status, indicator
 * jenkins job, date, version, status, indicator
 - User Help File
 * writing, date, version, status, indicator
 * review and test, date, version, status, indicator
 - Details
 * Entity - Field
 + Entity, FieldName, Label, Field Description, version, indicator
 * Service
 + ServiceName, description, Junit, version, indicator
 * Portlet
 + PortletName, help, SeedData, parameters, security, selenium, version
 indicator

 Conditions to be in Incubator
 ==
 - The minimum is :
 * add-on.xml and ivy.xml correct
 * a jenkins job for install testing
 * addon help wiki page finished
 * Quality status wiki page created with all boxes
 * One review for User Help section
 - Authorized to commit only for
 * Addon maintainer

 Condition to return to dev
 
 - More than 5 consecutive weeks with only failing install test jobs
 - No answer for user help questions
 * Answers can be an assistance proposal
 * and If the user help is not completed
 - No answer from the maintainer
 * It's possible to change the addon 

Re: 15 minutes to discover addons and addon manager

2012-11-28 Thread Jacques Le Roux
From: olivier Heintz olivier.hei...@neogia.org
 Le 25/11/2012 19:00, Jacques Le Roux a écrit :
 I did not follow this tuto only the one below
 I had already diff installed and a patchDos.bat:
 todos %1
 patch -N -p0  %1

 Creating the recommended bat files worked, thanks!

 When viewing the (long) result from 
 svn di framework\common\config\CommonUiLabels.xml  dropit.txt
 I see encoding issues in dropit.txt, even when changing encoding in Scite to 
 all possible values, normal? I guess it's an issues related to the platform?
 it's not a know issue, can you send the dropit.txt file

I will try to do it again, as its name says it: I dropped this file ;)

Jacques

 All the rest worked fine :o)

 Jacques

 From: Nicolas Malin malin.nico...@librenberry.net
 Thanks Jacques.

 I test with the last OFBiz trunk with success.

 Do you have the diff program installed properly ?
 http://code.google.com/a/apache-extras.org/p/ofbiz-adm/wiki/admInstallation

 Nicolas

 Le 25/11/2012 11:59, Jacques Le Roux a écrit :
 Thanks Nicolas,

 I give it a try in Windows using for
 $ alias adm=java -jar $(pwd)/addonmanager-20121027.jar
 doskey adm=java -jar addonmanager-20121027.jar $*
 (see http://superuser.com/questions/49170/create-an-alias-in-windows-xp 
 for more)

 It worked well until

 adm install org.ofbizextra-dev.hello-world
 [INFO] addon manager version : 20121027
 [INFO] Add-On Manager for D:\workspace\ofbizClean
 :: loading settings :: file = 
 D:\workspace\ofbizClean\.addons\ivysettings.xml
 :: resolving dependencies :: org.ofbizextra-dev#targetAddon;1.0
  confs: [default]
  found org.ofbizextra-dev#hello-world;0.1.0.0-dev in libraries-dev
  [0.1.0.0-dev] org.ofbizextra-dev#hello-world;latest.integration
 :: resolution report :: resolve 782ms :: artifacts dl 0ms
  
 -
  |  |modules||   artifacts 
   |
  |   conf   | number| search|dwnlded|evicted|| 
 number|dwnlded|
  
 -
  |  default |   1   |   1   |   0   |   0   ||   1   |   0 
   |
  
 -
 :: retrieving :: org.ofbizextra-dev#targetAddon
  confs: [default]
  0 artifacts copied, 1 already retrieved (0kB/16ms)
 The dependencies will be installed in this order:
 hello-world0.1.0.0-dev
 Add-on hello-world registered
 [INFO] Add-on hello-world unregistered
 org.ofbizextra.addonmanager.core.patch.PatchException: Patch failed for 
 File : framework\common\config\CommonUiLabels.xml
  at 
 org.ofbizextra.addonmanager.core.registry.RegisteredAddOn.applyPatchs(RegisteredAddOn.java:353)
  at 
 org.ofbizextra.addonmanager.core.registry.Registry.installAddOn(Registry.java:211)
  at 
 org.ofbizextra.addonmanager.core.command.InstallAddOnCommand.doExecute(InstallAddOnCommand.java:54)
  at 
 org.ofbizextra.addonmanager.core.AddOnManager.executeCommand(AddOnManager.java:407)
  at org.ofbizextra.addonmanager.cli.Cli.runCommand(Cli.java:119)
  at org.ofbizextra.addonmanager.cli.Cli.main(Cli.java:305)
 org.ofbizextra.addonmanager.core.AddOnManagerException: Installation 
 failed for : org.ofbizextra-dev.hello-world
  at 
 org.ofbizextra.addonmanager.core.command.InstallAddOnCommand.doExecute(InstallAddOnCommand.java:98)
  at 
 org.ofbizextra.addonmanager.core.AddOnManager.executeCommand(AddOnManager.java:407)
  at org.ofbizextra.addonmanager.cli.Cli.runCommand(Cli.java:119)
  at org.ofbizextra.addonmanager.cli.Cli.main(Cli.java:305)
 [ERROR] Installation failed for : org.ofbizextra-dev.hello-world

 Abort signal was received. Shutting down as gracefully as possible ...

 I guess the addon is not upated regarding CommonUiLabels.xml (I added 
 Japaned yesterday)?

 Thanks

 Jacques

 From: Malin Nicolas malin.nico...@librenberry.net
 Hello,

 I put my talk did at ApacheCon Europe on the addons for OFBiz and create
 a discovery scenario for an initiation in less than 15 minutes.

 The Talk :
 http://ofbiz-adm.apache-extras.org.codespot.com/files/ApacheConEurope-2012-addons-presentation-en.pdf
 Discovery scenario :
 http://code.google.com/a/apache-extras.org/p/ofbiz-adm/wiki/DiscoverAddonOn15Minutes

 I open for all feedback

 Nicolas




Re: loading ofbiz with upstart

2012-11-28 Thread Jacques Le Roux
Did you look at 
rc.ofbiz
rc.ofbiz.for.debian
rc.ofbiz.for.ubuntu
in tools dir ?

Jacques

From: Gintare Ragaisiene gintare.ragaisi...@gmail.com
 Hi
 
 I want my ofbiz start when the system (OS Ubuntu 10.04) starts. So I'm
 using Upstart and I placed /etc/init/ofbiz.conf with content
 
 # /etc/init/ofbiz.conf
 
 description OFBiz server
 author Gintare Ragaisiene
 
 start on filesystem
 stop on runlevel [06]
 
 expect fork
 respawn
 
 script
ant start
 end script
 
 
 After did reboot, and when I'm checking status:
 
 initctl status ofbiz
 ofbiz start/running, process 2198
 
 But in my link http://uniquemades.com:8080/unique/control/main I see
 nothing.
 I have checked this link is working well when I just type ant start on
 console.
 
 Thank you



Re: Change http port for production

2012-11-28 Thread Deepak Agarwal
Change in framework/base/config/ofbiz-containers.xml

On Wed, Nov 28, 2012 at 9:17 PM, Gintare Ragaisiene 
gintare.ragaisi...@gmail.com wrote:

 Hi

 I trieing to set up 80 http port instead 8080 with no success. Changes have
 been applied to :

 ../ofbiz/framework/webapp/config/url.properties

 # HTTP Port (Not Secure port)
 #port.http=8080
 port.http=80
 force.http.host=

 .../ofbiz/framework/catalina/ofbiz-component.xml

 property name=http-connector value=connector
 !-- see
 http://jakarta.apache.org/tomcat/tomcat-5.5-doc/config/http.html for
 reference --
 property name=allowTrace value=false/
 property name=emptySessionPath value=false/
 .
 property name=maxThreads value=100/
 property name=minSpareThreads value=4/
 property name=port value=80/
 property name=restrictedUserAgents value=/
 ...
 property name=threadPriority value=java.lang.Thread#NORM_PRIORITY/
 /property



 Thank you,
 Gintare




-- 
Thanks,
Deepak Agarwal,

Mobile: +91 9501190044


Re: Summary of ApacheCon-Eu conference Why ofbiz-extra

2012-11-28 Thread Jacques Le Roux
From: olivier Heintz olivier.hei...@neogia.org
 ApacheCon-Eu presentation is now available,
 http://archive.apachecon.com/eu2012/presentations/07-Wednesday/PR-Community/aceu-2012-ofbizextra-addons_what-constrains-for-each-repository.pdf
 
 
 I propose below a short summary (only the main points) to be able to
 start community discussion.
 
 I will do a second mail for comments about this presentation.
 
 Agenda :
 ==
 - Why to use OFBiz-extra rather than to include it in Apache-OFBiz?
 - the ofbizextra-addons Goals
 - Rules and Constraints by Repository
 - Process to change
 - Conclusions
 
 Why to use OFBiz-extra rather than to include it in Apache-OFBiz?
 =
 - Slim-down process in Apache-OFBiz project
 - Several technologies for the same function
 Ex : jasperReport, Birt, …
 - Licence
 Ex : GPL
 - Personal decision versus Apache-OFBiz PMC decision
 - Work in progress
 - OOTB solutions for dedicated Business

Sounds like good reasons to me.

 ofbizextra-addons Goals
 ===
 - Facilitate and simplify :
 * Contribution to OFBiz
 * Using / Testing added functions
 * Community and/or OFBiz-committer validation
 - Increase :
 * Quality and use of Best Practice
 * OFBiz functionalities without weighing down kernel
 * Propose OOTB dedicated solutions for users

More tests should be done by the community before adopting ofbizextra-addons 
for Apache OFBiz Extras
But from my early tests, and knowing the Neogia community experience with 
addons, I think all these goals qualify.


 Rules and Constraints by Repository
 ===
 - 3 repository

From what I already learned (very few) from addons, these must be svn repos.
It would not be at the ASF because of possible license issues, so where will 
they be? How reliable will they be or should they be? etc.
Also we could have an entry in the ASF repo, under 
https://svn.apache.org/repos/asf/ofbiz if the addons are ASL2 licensed. But 
this would NOT mean, except if we agree otherwise, that the addons there are 
reviewed guaranteed by the OFBiz team. Anyway from an official POV *only 
released products are official*. I mean those here 
http://ofbiz.apache.org/download.html

 - ofbiz-extra-addons-dev
 * This project is open for all contributors who want to create or
 maintain apache-ofbiz addons.
 * This project has no quality or best practice control, each contributor
 should try to do the best he can.
 * When a user uses an existing addon in this repository, he should
 assume risks, but but in many cases it will help him.

+1

 - ofbiz-extra-addons-incubator
 * This project is open for all Apache-OFBiz addons that should become :
 + part of ofbiz addons labeled Quality repository (ofbizextra-addons),
 + or part of Apache ofbiz project.
 * Addons of this project are in a Quality, Best Practice evaluation and
 enhancement.
 * There is, at least, one organization / person that is involved to
 solve bugs or to offer support services for this addon.

I wondered how this would be enforced but ok it's explained below in 
conditions.

 - ofbiz-extra-addons
 * Repository of the addons labeled Quality
 * In the future, a similar repository can be created as an Apache-OFBiz
 sub-project (for addons with Apache2 licence)

Yes, as discussed above IMO. Maybe not in a 1st step, but possibly when things 
will have settled down...

 * There is, at least, one organization / person that is committed to
 offer support services for this addon.
 * Addons
 + Have a complete user help
 + are included in a Continuous Integration Job :
 = Installation test
 = Unit test : Junit
 = Functional test : Selenium

What I fear (even with the conditions below) is the admin work (understand 
paper-work) related with these steps (not real steps since you can choose to 
stay in the dev eternally). I mean how to guarantee things/states related to 
conditions? Who will (officially, think conflicts) do it?
 
 Addon Quality status page
 (http://code.google.com/a/apache-extras.org/p/ofbiz-extra-addons-incubator/wiki/modelAddonQuality)

 =
 - Update history
 * contributor, date, version, indicator, description
 * reviewer, date, version, indicator, description

 - Base Files
 * add-on.xml, date, version, status, indicator
 * maintainer in add-on.xml, date, version, status, indicator
 * ivy.xml, date, version, status, indicator
 * addon help (English), date, version, status, indicator
 * jenkins job, date, version, status, indicator

 - User Help File
 * writing, date, version, status, indicator
 * review and test, date, version, status, indicator

 - Details
 * Entity - Field
 + Entity, FieldName, Label, Field Description, version, indicator
 * Service
 + ServiceName, description, Junit, version, indicator
 * Portlet
 + PortletName, help, SeedData, parameters, security, selenium, version
 indicator

 Conditions to be in Incubator
 ==
 - The minimum is :
 * add-on.xml and ivy.xml correct
 * a jenkins job for 

Re: Summary of ApacheCon-Eu conference Why ofbiz-extra

2012-11-28 Thread dejc

With all of these constraints, what would be the point of using extras projects?

Please consider that these QA, documentation, etc constraints even exist and 
are not enforced for OFBiz itself... and are clearly not considered a priority 
by very many or we'd see more people (committers and non-committer 
contributors) working on it.

-David


On Nov 28, 2012, at 6:02 AM, olivier Heintz olivier.hei...@neogia.org wrote:

 The mains important point are :
 - This is one way to facilitate Contribution to OFBiz  *AND* Quality
 enhancement
 - Share contribution, even if it's not for all ofbiz user, even if it
 not follow all current bests practices,  can help
 - We need to have a clear definition of what are the Quality criteria
 fro Apache-OFBiz
 - We need to have a clear process for contribution evaluation and status
 and life process
 
 The main comment done by the attendees :
 - It's very important to have a addon repository in Apache-OFBiz
 
 The next steps should be :
 - to write 1,2 or 3 wiki pages for OFBiz choices (writing in a consensus
 way);
 - to give visibility on new help integration
 - to give visibility on functional (or user-interface) test solution
 adopt by OFBiz
 - to start a process on addon manager evaluation
 - to start to give visibility to ofbiz-extra
 
 
 
 
 Le 27/11/2012 11:28, olivier Heintz a écrit :
 ApacheCon-Eu presentation is now available,
 http://archive.apachecon.com/eu2012/presentations/07-Wednesday/PR-Community/aceu-2012-ofbizextra-addons_what-constrains-for-each-repository.pdf
 
 
 I propose below a short summary (only the main points) to be able to
 start community discussion.
 
 I will do a second mail for comments about this presentation.
 
 Agenda :
 ==
 - Why to use OFBiz-extra rather than to include it in Apache-OFBiz?
 - the ofbizextra-addons Goals
 - Rules and Constraints by Repository
 - Process to change
 - Conclusions
 
 Why to use OFBiz-extra rather than to include it in Apache-OFBiz?
 =
 - Slim-down process in Apache-OFBiz project
 - Several technologies for the same function
 Ex : jasperReport, Birt, …
 - Licence
 Ex : GPL
 - Personal decision versus Apache-OFBiz PMC decision
 - Work in progress
 - OOTB solutions for dedicated Business
 
 ofbizextra-addons Goals
 ===
 - Facilitate and simplify :
 * Contribution to OFBiz
 * Using / Testing added functions
 * Community and/or OFBiz-committer validation
 - Increase :
 * Quality and use of Best Practice
 * OFBiz functionalities without weighing down kernel
 * Propose OOTB dedicated solutions for users
 
 Rules and Constraints by Repository
 ===
 - 3 repository
 - ofbiz-extra-addons-dev
 * This project is open for all contributors who want to create or
 maintain apache-ofbiz addons.
 * This project has no quality or best practice control, each contributor
 should try to do the best he can.
 * When a user uses an existing addon in this repository, he should
 assume risks, but but in many cases it will help him.
 - ofbiz-extra-addons-incubator
 * This project is open for all Apache-OFBiz addons that should become :
 + part of ofbiz addons labeled Quality repository (ofbizextra-addons),
 + or part of Apache ofbiz project.
 * Addons of this project are in a Quality, Best Practice evaluation and
 enhancement.
 * There is, at least, one organization / person that is involved to
 solve bugs or to offer support services for this addon.
 - ofbiz-extra-addons
 * Repository of the addons labeled Quality
 * In the future, a similar repository can be created as an Apache-OFBiz
 sub-project (for addons with Apache2 licence)
 * There is, at least, one organization / person that is committed to
 offer support services for this addon.
 * Addons
 + Have a complete user help
 + are included in a Continuous Integration Job :
 = Installation test
 = Unit test : Junit
 = Functional test : Selenium
 
 Addon Quality status page
 (http://code.google.com/a/apache-extras.org/p/ofbiz-extra-addons-incubator/wiki/modelAddonQuality)
 =
 - Update history
 * contributor, date, version, indicator, description
 * reviewer, date, version, indicator, description
 - Base Files
 * add-on.xml, date, version, status, indicator
 * maintainer in add-on.xml, date, version, status, indicator
 * ivy.xml, date, version, status, indicator
 * addon help (English), date, version, status, indicator
 * jenkins job, date, version, status, indicator
 - User Help File
 * writing, date, version, status, indicator
 * review and test, date, version, status, indicator
 - Details
 * Entity - Field
 + Entity, FieldName, Label, Field Description, version, indicator
 * Service
 + ServiceName, description, Junit, version, indicator
 * Portlet
 + PortletName, help, SeedData, parameters, security, selenium, version
 indicator
 
 Conditions to be in Incubator
 ==
 - The minimum is :
 * add-on.xml and ivy.xml correct
 * a jenkins job for install testing
 * addon help