16:02:56 #startmeeting Java SIG -- https://fedoraproject.org/wiki/SIGs/Java 16:02:56 Meeting started Tue Feb 26 16:02:56 2013 UTC. The chair is sochotni. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:56 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:03:00 #meetingname Java SIG 16:03:00 The meeting name has been set to 'java_sig' 16:03:04 #topic roll-call 16:03:08 .fasinfo sochotni 16:03:09 sochotni: User: sochotni, Name: Stanislav Ochotnicky, email: sochotni@redhat.com, Creation: 2010-04-06, IRC Nick: , Timezone: Europe/Prague, Locale: en, GPG key ID: 71A1677C, Status: active 16:03:12 sochotni: Approved Groups: +gitfedorareview fedorabugs cla_redhat cla_fedora cla_done +packager provenpackager @git-javapackages 16:03:17 .fasinfo jerboaa 16:03:18 .fasinfo msrb 16:03:18 jerboaa: User: jerboaa, Name: None, email: jerboaa@gmail.com, Creation: 2010-06-17, IRC Nick: None, Timezone: None, Locale: None, GPG key ID: None, Status: active 16:03:21 .fasinfo tradej 16:03:21 jerboaa: Approved Groups: cla_fedora cla_done cla_redhat packager fedorabugs @giteclipse-fedorapackager 16:03:24 msrb: User: msrb, Name: Michal Srb, email: msrb@redhat.com, Creation: 2012-12-04, IRC Nick: None, Timezone: UTC, Locale: en, GPG key ID: None, Status: active 16:03:27 msrb: Approved Groups: @gitmaven-rpminstall-plugin fedorabugs packager cla_done cla_fpca 16:03:30 tradej: User: tradej, Name: Tomas Radej, email: tradej@redhat.com, Creation: 2011-08-03, IRC Nick: tradej, Timezone: Europe/Prague, Locale: en, GPG key ID: , Status: active 16:03:34 tradej: Approved Groups: provenpackager cla_fpca cla_done packager fedorabugs 16:03:55 .fasinfo jvanalte 16:03:56 vanaltj: User: jvanalte, Name: Jon VanAlten, email: jon.vanalten@redhat.com, Creation: 2011-05-19, IRC Nick: vanaltj, Timezone: UTC, Locale: en, GPG key ID: , Status: active 16:03:59 vanaltj: Approved Groups: packager fedorabugs cla_fpca cla_done 16:04:15 .fasinfo akurtakov 16:04:20 akurtakov: User: akurtakov, Name: Alexander Kurtakov, email: akurtako@redhat.com, Creation: 2008-10-01, IRC Nick: akurtakov, Timezone: Europe/Sofia, Locale: en, GPG key ID: , Status: active 16:04:23 akurtakov: Approved Groups: @giteclipse-packagekit cla_fedora cla_done cla_redhat fedorabugs +packager provenpackager @git-javapackages @giteclipse-fedorapackager 16:04:42 .fasinfo neugens 16:04:43 neugens: User: neugens, Name: Mario Torre, email: neugens@redhat.com, Creation: 2007-03-20, IRC Nick: neugens, Timezone: UTC, Locale: en, GPG key ID: 80F240CF, Status: active 16:04:46 neugens: Approved Groups: cla_fedora cla_fpca cla_done packager fedorabugs 16:05:22 few more minutes I guess 16:05:35 .fasinfo rgrunber 16:05:36 rgrunber: User: rgrunber, Name: Roland Grunberg, email: rgrunber@redhat.com, Creation: 2009-07-23, IRC Nick: rgrunber, Timezone: America/Toronto, Locale: en, GPG key ID: , Status: active 16:05:39 rgrunber: Approved Groups: @giteclipse-packagekit cla_fedora cla_done cla_redhat packager fedorabugs @giteclipse-fedorapackager 16:06:01 .fasinfo mizdebsk 16:06:02 mizdebsk: User: mizdebsk, Name: Mikolaj Izdebski, email: mizdebsk@redhat.com, Creation: 2012-04-02, IRC Nick: mizdebsk, Timezone: Europe/Prague, Locale: en, GPG key ID: , Status: active 16:06:06 mizdebsk: Approved Groups: @gitmaven-rpminstall-plugin provenpackager git-javapackages cla_fpca cla_done packager fedorabugs @gitjava-deptools 16:06:27 kdaniel incoming I'd guess... 16:07:27 ok, let's start without him 16:07:36 #topic New guidelines & XMvn packaging 16:07:42 #link https://fedoraproject.org/wiki/User:Msrb/JavaPackagingDraft 16:07:58 hopefully this will be less drastic then last meeting? 16:08:07 #chair akurtakov 16:08:07 Current chairs: akurtakov sochotni 16:08:15 I might need to leave a bit earlier 16:08:21 so just in case... 16:10:05 anyway, so I don't see any additions to https://fedoraproject.org/wiki/Meeting:Java_SIG_2013-02-26 16:10:38 I have a question 16:10:44 neugens: shoot 16:11:10 sochotni, with JavaFX being open sourced more and more 16:11:15 I will need to package it in fedora 16:11:29 the current build system uses ant but upstream is moving to gradle 16:11:40 I didn't find any guidelines or help though in our documentation 16:12:10 neugens: Noone created gradle guidelines or macros 16:12:27 it's one hell of an abomination TBT 16:12:33 right 16:12:37 but I guess we can't ignore it 16:12:44 or we may want 16:12:56 not sure, in either case I thought it's a good thing to bring up here 16:13:20 neugens: yeah, it is except it doesn't really affect our current guideline situation/switch 16:14:03 neugens: I believe it's close to impossible to support gradle in sensible way as a build tool. It's impossible to automate/standardize 16:14:25 there will most probably never be XMvn4Gradle 16:14:47 that's what I think too - both maven and gradle don't get the basics - aka always online builds 16:14:56 but with maven there are standards 16:15:04 so one can switch to smth sensible 16:15:09 which is impossible with gradle 16:15:19 anyway, I *really* don't want to get into tangents about gradle right now 16:15:27 (upstream maven does support offline mode and custom repos) 16:15:37 we can get back to it after we discuss the guideline changes 16:15:58 ok, but please this is a quite important topic, so let's not forget 16:16:01 neugens: please bring it again in openfloor 16:16:15 akurtakov, sure, thanks! 16:16:18 I see some minor issues in draft.. 16:16:22 i.e https://fedoraproject.org/wiki/User:Msrb/JavaPackagingDraft#Apache_Maven 16:16:28 In Fedora 15 and newer, Maven 3 is used. Packages built using Maven ship with pom.xml files. They SHOULD contain common sections such as the following: 16:16:39 and then they list %mvn_build/%mvn_install macros 16:16:48 which are only available in F19 16:16:56 in sensible way 16:17:26 msrb: can I ask you to fix that up? 16:17:32 we can drop pre Fedora 17 stuff 16:17:44 sochotni, yep 16:17:57 #action msrb fix up Fedora versions in Apache Maven section 16:18:37 I had commented on-list, and the only replies I saw (unless I missed) were from dwalluck 16:18:54 vanaltj: yeah, we had a busy week in Brno (100 guests for devconf) 16:19:14 vanaltj: take it as sort of an excuse from me for not being more proactive there 16:19:18 I heard it was good times :) 16:19:23 no worries. 16:20:17 basically I was pointing out things that I thought might be confusing/conflicting especially for new packagers. 16:21:19 not sure if that's relevant, but I think it would be helpful to reference a java packages review checklist 16:22:07 jerboaa: you mean http://fedoraproject.org/wiki/Java_review_template ? 16:22:12 That's quite out of date 16:22:21 it would give packagers a chance to go through that list before a review even starts 16:22:49 even if it is, I see that popping up in quite some reviews 16:22:53 jerboaa: I'll update fedora-review to reflect these changes after guidelines are updated 16:22:54 ah yeah template should be updated to match whatever new guidelines get approved. 16:22:58 while I agree that guidelines should be detailed I start to be afraid of them becoming too long 16:23:25 akurtakov: we are planning more simplifications later on 16:23:33 ok 16:23:35 just a reference as a sanity check. no inclusion in guideline intended with my comment 16:23:37 but didn't want to mixing stuff 16:23:45 part of the length is that there are currently some supported releases that need one way, but newest release needs new way. 16:24:32 related to that...i.e. documentation for add_maven_depmap should be kept out of guidelines 16:24:48 I will be preparing a documentation for Java packaging on Fedora 16:25:02 and there will also be javapackages-tools documentation 16:25:15 so we'll be able to just link to upstream tooling docs 16:25:22 instead of listing usage in guidelines 16:25:37 but that's not on the table currently 16:25:52 it will lead to shorter guidelines eventually 16:26:47 my comment was supposed to be - let's keep refining the guidelines but not add new stuff (gradle/reviews/etc.) till we manage to reduce it 16:26:58 akurtakov: no argument there 16:27:11 akurtakov: +1 16:27:59 vanaltj: I'll read those mails about concerns again and try to incorporate them in guidelines 16:28:05 or maybe msrb will? :-) 16:28:11 ok. I'm fine with that 16:28:15 cool, thx. 16:28:18 I remember BR: java one 16:29:09 so can I call a vote on it? I believe small fixing up here and there should not be a problem 16:29:20 meaning even after the vote 16:30:05 fine by me 16:30:55 aka vote on the ideas and actual diff announced on list prior to sending to FPC 16:31:14 s/ideas/basic implementation/ 16:31:15 sounds fine. 16:31:20 ok, so voting for: New guidelines as present currently on https://fedoraproject.org/wiki/User:Msrb/JavaPackagingDraft 16:31:47 plus a few tweaks (supporting non-effective poms and few other things) 16:32:04 + incorporating few typo fixes 16:32:45 +1 from me 16:33:04 +1 on guidelines, +1 on non-effective poms, +1 on typo fixes 16:33:12 +1 here. 16:33:15 +1 16:33:23 +1 16:33:41 +1 , sounds good. 16:33:41 +1 16:34:16 so far, +1: 7, -1:0, x:0 16:35:25 #accepted 16:35:31 I guess :-) 16:35:38 I have one more topic... 16:35:42 should be fairly quick 16:35:44 and is related 16:36:02 #topic Lifting FPC/Fesco temporary ban on XMvn conversions 16:36:24 akurtakov: I assume this is fine lift as well? 16:36:31 from your POV 16:36:35 yes 16:36:57 OK, I'll bring it up tomorrow on FESCO meetings 16:37:21 sochotni: let me know if you want me to comment somewhere (trac?) 16:37:30 as I would not be available in the evening 16:37:39 akurtakov: I guess I can just link to meeting log 16:37:46 works fine 16:37:54 OK 16:38:07 akurtakov: though feel free to add a comment to that FPC bug 16:38:37 #agreed ban can be lifted at FESCO/FPC discretion 16:38:57 #topic open floor 16:40:31 neugens: we *could* discuss gradle, but I am not sure what to make of it 16:40:44 yeah 16:40:47 I don't know either 16:40:55 basically just one package needs it currently 16:41:00 I think this needs greater minds than me ;) 16:41:21 neugens: it might make sense to ask gradle maintainers (I believe mgoldmann & gil) 16:41:41 other that that I really try to avoid gradle so I have no useful info 16:42:01 sochotni, ok 16:42:04 sochotni: https://fedorahosted.org/fpc/ticket/257 commented and resolved by me 16:42:17 fedora has pretty new version of gradle packaged and afaik it's working 16:42:39 mizdebsk, seems so 16:42:39 if maintainers are willing they can introduce guideline proposal 16:42:42 neugens: we would need someone to try coming with a way to make gradle work offline in a reasonable way 16:42:50 mizdebsk, on the other end I gave a look at hibernate 16:42:56 which uses gradle afaik 16:43:01 yes it does 16:43:08 it's the only package using gradle 16:43:08 they actually have maven pom in the sources 16:43:24 I don't know if they generated them or recreated just for packaging 16:43:25 neugens: closest example might be ivy - it's free style (more or less) 16:43:27 I gotta run, akurtakov has chair. Please do #endmeeting once your are done :-) 16:43:49 neugens: but it's pretty easy to plug your own resolver 16:44:22 neugens: if anything about gradle ends up on the guidelines such information would be needed 16:44:35 if/when :) 16:44:38 sochotni: sure 16:45:45 akurtakov, sure 16:46:36 neugens: there are some packages in fedora that keep updating the old build systems 16:46:58 in order to not jump on gradle as it's not easy to find a pattern there 16:47:21 akurtakov, if javafx will keep around the ant build 16:47:24 I'll do the same 16:47:31 but I think it's very unlikely 16:47:48 once they finish the gradle experiments they will probably just keep this only 16:47:50 neugens: I mean upstream don't keep it but we keep it in fedora packages 16:48:06 right but I don't think I have the amount of cycles for that 16:48:18 (although I may have to end up with no alternatives) 16:48:28 neugens: best approach for now might be starting gradle page on fedora wiki 16:48:43 and communicate with others using gradle to document some basic usages 16:49:11 till things get easier to apply to random gradle package 16:49:32 * tradej doesn't know anything about gradle, thus leaves. see you later, guys! 16:50:03 neugens: we do smth similar for tycho as it's in heavy development upstream and hence not smth we can easily make guidelines for now http://fedoraproject.org/wiki/Tycho 16:50:59 neugens: sounds good ? 16:51:22 akurtakov, yeah 16:51:51 neugens: if there is anything ask on the mailing list 16:51:52 I will do more experiments and contact the gradle maintainers 16:51:58 and start the page 16:52:22 I doubt we cna standardize but we may come with at least some best effort guidelines 16:53:06 for me existing documentation is more important than being official 16:53:27 aka better to have unoffical docs than none :) 16:53:44 done with gradle? 16:54:36 seems so, yes 16:54:52 if I have further questions I'll ask in list or during next meetings 16:55:09 anything else ? 16:55:24 or the meeting is going to its end? 16:57:04 #endmeeting