| Not-ba81 | [iDempiereDaily] jenkins built #554 completed (success) http://ci.idempiere.org/job/iDempiereDaily/554/ | 03:26 |
|---|---|---|
| Not-ba81 | [IDEMPIERE] fr.jkrieg updated IDEMPIERE-3531 | 03:42 |
| Not-ba81 | [IDEMPIERE] > not yet, but equinox + eclipse help developer on osgi stuff. > you easy define a launcher, manage plugin, add osgi metadata by editor, without deep knowledge of osgi I personally don't find the OSGi GUI manifest are a massive help. Maybe it's just me, but I think anyone who has to fiddle at the OSGi manifests is probably already savvy enough that they could easily fiddle with the manifest file directly | 03:42 |
| Not-ba81 | (and in fact, would probably prefer to do so). I know as I've been trying to come up to speed with OSGi in iDempiere I found the GUI more of a hinderance than a help - I always skip straight to the "MANIFEST.MF" tab. :) > yes, on group have guy success to move it to Apache Karaf (or something like that) This is good news. I read also somewhere that there may also be licensing considerations for this kind of | 03:42 |
| Not-ba81 | separation. > you can use language script like groovy to handle build process Incidentally, I'm not sure if you're aware, but Gradle is based on Groovy, which is one of the reasons its popular. You can embed script snippets directly in the build files to automate things. I think you could have a Gradle step that automatically deployed the seed database, for example. > i'm not sure about Gradle but Maven/Tycho look | 03:42 |
| Not-ba81 | fit to idempiere. now it's standard build tool for RCP project, supported from eclipse community > from "Gradle and Eclipse RCP - Gradle Summit 2016" i see almost is work-around > and it isn't well support from community: https://github.com/diffplug/gradle-and-eclipse-rcp > when people stop we will fall back buckminster situation Yes, this is a good point. Admittedly attempts to do OSGi/p2 support in Gradle are still | 03:42 |
| Not-ba81 | in their early stages, and there is a risk that it might never take off and we are left in the same position as with Buckminster. I guess one difference is that with Buckminster it was the entire build system that is no longer supported. I think that is unlikely to happen with Gradle, so the worst that might happen is we are left needing to maintain the OSGi/p2- specific plugins. But certainly, this is a good reason | 03:42 |
| Not-ba81 | to choose Tycho over Gradle (at least until the support in Gradle matures, if it ever does). | 03:42 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3531 | 03:42 |
| *** a42niem has joined #idempiere | 05:36 | |
| Not-ba81 | [iDempiere4.1Daily] jenkins built #124 completed (success) http://ci.idempiere.org/job/iDempiere4.1Daily/124/ | 05:51 |
| *** nmicoud has joined #idempiere | 06:07 | |
| *** rhein has joined #idempiere | 06:45 | |
| Not-ba81 | [IDEMPIERE] hengsin updated IDEMPIERE-3531 | 07:09 |
| Not-ba81 | [IDEMPIERE] iDempiere's dependency on eclipse and equinox specific stuff is minimal so it should be straightforward to move it to another OSGi container. As usual with any community driven project, the key here is the availability of a long term maintainer to support one more OSGi runtime. Equinox isn't tied to Eclipse so that's not the key element that would stop you from doing iDempiere development with IntelliJ. | 07:09 |
| Not-ba81 | You can use Equinox outside of Eclipse. For OSGi services metadata maintenance, to reduce the dependency on Eclipse's OSGi support, we need to migrate to use annotation instead. For build, I think we should move to Maven + Tycho first as it is proven and stable ( As buckminster is dead, we need to movve to a stable build system first). If someone/community is interested, Gradle can be started after that as an | 07:09 |
| Not-ba81 | option/experiment and we should only move to it if it is prove to be stable ( not having a stable build system for a while is not an option! ). I guess p2 support is the key issue here since there doesn't seems to be a stable Gradle module for that yet ( Perhaps moving away from p2 could be an option here, for e.g by using https://plugins.gradle.org/plugin/com.diffplug.gradle.p2.asmaven ). | 07:09 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3531 | 07:09 |
| Not-ba81 | [IDEMPIERE] hengsin created IDEMPIERE-3535 Implement font icon theme | 07:13 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3535 | 07:13 |
| Not-ba81 | [IDEMPIERE] hengsin created IDEMPIERE-3536 Dynamic validation not working correctly in Grid View | 07:14 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3536 | 07:14 |
| Not-ba81 | [IDEMPIERE] hengsin created IDEMPIERE-3537 Generic Info Window: Rendering of Search, Table Direct and List columns | 07:23 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3537 | 07:23 |
| *** rhein has quit IRC | 08:37 | |
| Not-ba81 | [IDEMPIERE] carlosruiz_globalqss updated IDEMPIERE-3531 | 09:20 |
| Not-ba81 | [IDEMPIERE] > For build, I think we should move to Maven + Tycho first as it is proven and stable Agree, I think this is the right step at this moment. > I read also somewhere that there may also be licensing considerations for this kind of separation. Yes, we have a licensing issue as in principle GPLv2 (idempiere) is not compatible with the EPL. Contrary to what some FUD spreading people have said in other | 09:20 |
| Not-ba81 | scenarios, I think that's not a big issue because: - is very unlikely that somebody complains about compatibility of two open source licenses in an open source project - if any implementor is really concerned about that then he/she can move to glassfish (GPL) - there are success stories in forums Anyways, moving to another container sounds ok, but in such case I would suggest glassfish for what is said above. But I | 09:20 |
| Not-ba81 | think changing to maven is one project and moving to a different container maybe is a different subproject to be tackled in a different ticket. Last (talking from my ignorance here): instead of moving to another OSGi container, we could move to java 9 modularity (in a different future subproject) - is that possible? worthy? OSGi is very mature compared to java9. But as modularity now is implicit to the language can | 09:20 |
| Not-ba81 | be a better move. WDYT? | 09:20 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3531 | 09:20 |
| *** CarlosRuiz has joined #idempiere | 09:20 | |
| Not-ba81 | [IDEMPIERE] hengsin updated IDEMPIERE-3531 | 12:07 |
| Not-ba81 | [IDEMPIERE] For me, Java 9 modularity is a version 1 release and I think it is usually a good idea to avoid a version 1 release. | 12:07 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3531 | 12:07 |
| Not-ba81 | [IDEMPIERE] hieplq updated IDEMPIERE-3531 | 12:28 |
| Not-ba81 | [IDEMPIERE] licensing compatible will soon official resolve https://www.eclipse.org/org/documents/epl-2.0/faq.php#epl-secondary personal i live well with depend on RCP, and Maven + Tycho is best choose now. it's wide use for RCP so almost issue have already has solution for move to gradle and deploy to any Osgi container. i think that first step is move standard osgi with support from bnd, get rid of RCP after that | 12:28 |
| Not-ba81 | we can parallel support multi build system also Osgi container for move to java 9 module, at least we have to waiting for almost importance library move to it first. and wait to see how it stable, intuitive than Osgi. | 12:28 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3531 | 12:28 |
| *** a42niem has quit IRC | 12:30 | |
| *** CarlosRuiz has quit IRC | 13:20 | |
| *** Gershwin has joined #idempiere | 16:10 | |
| *** nmicoud has quit IRC | 16:25 | |
| Not-ba81 | [iDempiereDaily] jenkins built #556 completed (success) http://ci.idempiere.org/job/iDempiereDaily/556/ | 18:16 |
| Not-ba81 | [iDempiere5.1] jenkins built #1 completed (success) http://ci.idempiere.org/job/iDempiere5.1/1/ | 18:35 |
| Not-ba81 | [iDempiere5.1Daily] jenkins built #1 completed (success) http://ci.idempiere.org/job/iDempiere5.1Daily/1/ | 19:03 |
| *** a42niem has joined #idempiere | 19:29 | |
| Not-ba81 | [IDEMPIERE] hieplq created IDEMPIERE-3538 NPE happen if show dialog at time not yet complete login | 20:09 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3538 | 20:09 |
| *** a42niem has quit IRC | 22:21 | |
| Not-ba81 | [iDempiere] hengsin pushed 1 commit to default [+3/-0/±59] https://bitbucket.org/idempiere/idempiere/commits/ | 22:57 |
| Not-ba81 | [iDempiere] hengsin 332881a - IDEMPIERE-3535 Implement font icon theme | 22:57 |
| Not-ba81 | [IDEMPIERE] hengsin updated IDEMPIERE-3535 Fix Version set to "iDempiere HEAD" | 22:58 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3535 | 22:58 |
| Not-ba81 | [IDEMPIERE] hengsin updated IDEMPIERE-3535 Version set to "5.1" | 22:58 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3535 | 22:58 |
| Not-ba81 | [IDEMPIERE] hengsin updated IDEMPIERE-3535 status set to "In Progress" | 22:58 |
| Not-ba81 | [IDEMPIERE] http://idempiere.atlassian.net/browse/IDEMPIERE-3535 | 22:58 |
| Not-ba81 | [iDempiere] jenkins built #1892 completed (success) http://ci.idempiere.org/job/iDempiere/1892/ | 23:26 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!