Use the static method getLogger instead of using a static logger variable. The logger is created as needed inside the getLogger method.
2)http://kenai.com/jira/browse/HENGSIN-3, properties file wrongly created
Patch accepted.
3) http://kenai.com/jira/browse/HENGSIN-4, Cannot connect to http://localhost:8080/admin/adempiereMonitor
Always set default level for root logger in CLogMgt initialization.
4) http://kenai.com/jira/browse/HENGSIN-5, Build fails by default requiring directory lib/plugins
Modify utils_dev/build.xml to ensure the existence of the lib/plugins folder.
5) Module refactoring
* Remove client bundle dependency from the zkwebui bundle. Common UI code of the 2 bundle is moved into the new uibase bundle.
* Remove client bundle dependency from server side bundle. The swing specific jasper report code is moved into the new JasperReportsClient bundle.
* Move most swing code that is still in the base bundle into the client bundle. Many swing client specific code in Env.java (base bundle) is move into the AEnv.java (client bundle).
* Default handlers for 2Pack is moved into the new pipoHandlers bundle. All loading of 2pack handler is now done using the equinox extension mechanism.
6) Extension point
* Added process, form and modelvalidator extension point base on the existing work done by Jorg Viola in the osgi1 branch.
7) The pipo bundle is move from plugins/pipo to /pipo ( relative to the workspace ) due to ant4eclipse have problem building the bundle using the previous layout.
8) New workflow editor and rendering implementation using netbeans visual library. The implementation is shared the by swing and zk client.
* Converted serverApps and webStore to OSGi war bundle
* Now both webui and webstore OSGi war bundle can be launch from eclipse, next to be converted is the admin and adempiere server monitor web application.
This is a slightly large commit affecting the core functionality of shipments
so I'm happy for all eyeballs I can get on this code. I've tested as thorough
one person can do.
If there are no undiscovered bugs this doesn't change current functionality unless
you change the new setting of "Delivery Policy" available on Client Info and
Organization Info.
See also http://www.adempiere.com/index.php/Delivery_Policy
Link to SF Tracker: http://sourceforge.net/support/tracker.php?aid=3004020
This fix also fixes bug 3017049 - Direct print doesn't work with JasperReports.
There is unfortunately some duplication of code that would look nicer with
inheritance but that can be next step, now at least it works and this is a crucial
function for organizations that use Jasper Reports for invoices etc.
Link to SF Tracker: http://sourceforge.net/support/tracker.php?aid=2973199
r12588
Steps to release -> generate complete model for new version (official tables) part 5/5
***** Please note: trunk may have build problems till this series of commits are completed
***** Each merge is taking about 1/2 an hour and each commit 1/4 an hour !!! I LUV SVN
Regards,
Tony
r12587
Steps to release -> generate complete model for new version (official tables) part 4/5
***** Please note: trunk may have build problems till this series of commits are completed
***** Each merge is taking about 1/2 an hour and each commit 1/4 an hour !!! I LUV SVN
Regards,
Tony
r12586
Steps to release -> generate complete model for new version (official tables) part 3/5
***** Please note: trunk may have build problems till this series of commits are completed
***** Each merge is taking about 1/2 an hour and each commit 1/4 an hour !!! I LUV SVN
Regards,
Tony
r12585
Steps to release -> generate complete model for new version (official tables) part 2/5
***** Please note: trunk may have build problems till this series of commits are completed
***** Each merge is taking about 1/2 an hour to complete !!!
Regards,
Tony
r12582
Steps to release -> generate complete model for new version (libero tables)
r12583
Steps to release -> generate complete model for new version (libero tables)
Regards,
Tony
r12577
Run sequence check before release
r12578
Steps to release - change sources to point new version
r12579
Steps to release -> Create migration scripts to update version information in ad_system table
r12580
Steps to release -> Create migration scripts to update version information in ad_system table
r12581
Steps to release -> Change and compile new Launch4j
Regards,
Tony