18:05:11 <alagalah> #startmeeting TWS
18:05:11 <odl_meetbot> Meeting started Mon Jan 26 18:05:11 2015 UTC.  The chair is alagalah. Information about MeetBot at http://ci.openstack.org/meetbot.html.
18:05:11 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:05:11 <odl_meetbot> The meeting name has been set to 'tws'
18:05:23 <alagalah> #topic edwarnicke presenting archetype for new project
18:05:35 <colindixon> link?
18:05:42 <colindixon> I’ll grab it
18:06:03 <alagalah> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype
18:06:10 <colindixon> #undo
18:06:18 <colindixon> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype the archetype wiki page Ed is talking through
18:07:03 * colindixon wonders, can only chairs unod?
18:10:09 <tykeal> colindixon: yes
18:11:08 <colindixon> #info Ed walks through using the archeype, he suggests you copy and paste the archetype maven command from the wiki
18:12:12 <colindixon> #info fill in what it asks for, the key plces are a group ID, artifact ID, and version (version should likely be overridden with a three number -SNAPSHOT version
18:13:11 <colindixon> #info edwarnicke suggests that you leave the classPrefix macro alone since it does smart things, but feel free to override it if you know better
18:14:00 <colindixon> #info edwarnicke notes that it builds/runs out of the box, so you can build and then run from the -karaf directory with <name>-karaf/target/assembly/bin/karaf
18:15:55 <colindixon> #info running it even automatically loads the features implemented by the archetype
18:19:22 <colindixon> #info You can load the code into Eclipse, only error at the moment is checkstyle, he’s still trying to beat it out
18:19:54 <colindixon> #info shows the HelloProvider which has two functions one when it gets loaded into the MD-SAL and one when it’s removed
18:23:12 * regXboi wanders in via phone because webex isn't working
18:24:02 * regXboi wonders what the topic is
18:26:16 <alagalah> regXboi: Ed going through 10:06 alagalah: #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype
18:26:30 <regXboi> alagalah: many thanks
18:26:43 <alagalah> regXboi: After this we will go through the status of the Tutorial project
18:27:15 <colindixon> #info edwarnicke pastes in some code to Eclipse to show how to add code that calls the hello provider and implementing the provider
18:27:39 <colindixon> #info edwarnicke then builds *everything* because it automagically compiles and re-“links” everything without having to worry about the order and stuff
18:31:45 <alagalah> #info jmedved brings up adding Integration testing to the archetype
18:31:58 <alagalah> #info edwarnicke will work on it
18:32:13 * tbachman wanders into the TWS
18:33:43 <regXboi> tbachman: yo!
18:33:49 <tbachman> regXboi: howdy!
18:37:03 * tbachman hears edwarnicke up-arrowing
18:42:57 <colindixon> #info edwarnicke shows the pom structure for the project to help explain how things are working
18:43:40 <colindixon> #info edwarnicke shows the hello-artifact pom file which manages the versions of artifacts that will be exported to other projects (you’ll see how to import in the karaf)
18:43:42 <alagalah> #info POM file structure greatly reduced by inclusion of "binding parent" POM XML
18:44:18 <colindixon> thanks alagalah
18:44:48 <alagalah> #info now discussing features file
18:45:21 <alagalah> #info defines repositories for the features, defines feature for hello-api, creates feature for hello-impl. Creates a hello-impl-rest which pulls in RESTCONF
18:45:44 <alagalah> #info planning on adding a UI feature sub-section
18:47:54 <alagalah> #info colindixon asks if we could document how the project archetype used to look so folks familiar with the older way can compare/contrast
18:49:17 <alagalah> #info moving to hello-impl pom.xml
18:49:18 <colindixon> #info I think rouguhly the old names to new names is model-<name> => <name>-api and <name> => <name>-impl
18:50:11 <alagalah> #info Much in this pom.xml is managed in config-parent
18:50:28 <alagalah> #info only the parent and API are defined
18:52:06 <colindixon> #info the archetype gives you teh default config file for free, which has been a big sticking point in the past
18:52:27 <colindixon> #info moving on to the karaf pom file (which pull in the karaf-parent)
18:53:27 <alagalah> #info Due to karaf fixing bugs in 3.0.2, the use of karaf-parent reduces some hack arounds required for karaf 3.0.1
18:53:29 <colindixon> #info the karaf-parent will be able to allow us to remove hacks as karaf fixes bugs and do it in a central place
18:57:05 <colindixon> #info SCROLLING CONSIDERED HARMFUL
18:57:11 <tbachman> colindixon: LOL
18:58:09 <colindixon> #info right now we load ${karaf.localFeature} at boot in the karaf-parent, which works fine if it’s undefined and loads nothing
18:59:45 <colindixon> #info when you define that in your pom file, it will load that *one* feature when karaf comes up
19:00:02 <colindixon> ok, I need to drop
19:00:08 <colindixon> thanks edwarnicke! this looks awesome!
19:00:16 <hideyuki> 3
19:01:22 * regXboi wanders away for lunch
19:05:02 <tbachman> #endmeeting
19:05:09 <hideyuki> That's great!
19:05:10 <tbachman> anyone still here that’s a chair?
19:05:24 <zxiiro> edwarnicke: Thanks! sounds like a good step forward.
19:05:36 <alagalah> #endmeeting