==========================
#opendaylight-meeting: TWS
==========================


Meeting started by alagalah at 18:05:11 UTC.  The full logs are
available at
http://meetings.opendaylight.org/opendaylight-meeting/2015/tws/opendaylight-meeting-tws.2015-01-26-18.05.log.html
.



Meeting summary
---------------

* edwarnicke presenting archetype for new project  (alagalah, 18:05:23)
  * LINK:
    https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype
    (alagalah, 18:06:03)
  * LINK:
    https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype
    the archetype wiki page Ed is talking through  (colindixon,
    18:06:18)
  * Ed walks through using the archeype, he suggests you copy and paste
    the archetype maven command from the wiki  (colindixon, 18:11:08)
  * 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  (colindixon, 18:12:12)
  * edwarnicke suggests that you leave the classPrefix macro alone since
    it does smart things, but feel free to override it if you know
    better  (colindixon, 18:13:11)
  * 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  (colindixon, 18:14:00)
  * running it even automatically loads the features implemented by the
    archetype  (colindixon, 18:15:55)
  * You can load the code into Eclipse, only error at the moment is
    checkstyle, he’s still trying to beat it out  (colindixon, 18:19:22)
  * shows the HelloProvider which has two functions one when it gets
    loaded into the MD-SAL and one when it’s removed  (colindixon,
    18:19:54)
  * edwarnicke pastes in some code to Eclipse to show how to add code
    that calls the hello provider and implementing the provider
    (colindixon, 18:27:15)
  * edwarnicke then builds *everything* because it automagically
    compiles and re-“links” everything without having to worry about the
    order and stuff  (colindixon, 18:27:39)
  * jmedved brings up adding Integration testing to the archetype
    (alagalah, 18:31:45)
  * edwarnicke will work on it  (alagalah, 18:31:58)
  * edwarnicke shows the pom structure for the project to help explain
    how things are working  (colindixon, 18:42:57)
  * 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)  (colindixon, 18:43:40)
  * POM file structure greatly reduced by inclusion of "binding parent"
    POM XML  (alagalah, 18:43:42)
  * now discussing features file  (alagalah, 18:44:48)
  * defines repositories for the features, defines feature for
    hello-api, creates feature for hello-impl. Creates a hello-impl-rest
    which pulls in RESTCONF  (alagalah, 18:45:21)
  * planning on adding a UI feature sub-section  (alagalah, 18:45:44)
  * colindixon asks if we could document how the project archetype used
    to look so folks familiar with the older way can compare/contrast
    (alagalah, 18:47:54)
  * moving to hello-impl pom.xml  (alagalah, 18:49:17)
  * I think rouguhly the old names to new names is model-<name> =>
    <name>-api and <name> => <name>-impl  (colindixon, 18:49:18)
  * Much in this pom.xml is managed in config-parent  (alagalah,
    18:50:11)
  * only the parent and API are defined  (alagalah, 18:50:28)
  * the archetype gives you teh default config file for free, which has
    been a big sticking point in the past  (colindixon, 18:52:06)
  * moving on to the karaf pom file (which pull in the karaf-parent)
    (colindixon, 18:52:27)
  * Due to karaf fixing bugs in 3.0.2, the use of karaf-parent reduces
    some hack arounds required for karaf 3.0.1  (alagalah, 18:53:27)
  * the karaf-parent will be able to allow us to remove hacks as karaf
    fixes bugs and do it in a central place  (colindixon, 18:53:29)
  * SCROLLING CONSIDERED HARMFUL  (colindixon, 18:57:05)
  * right now we load ${karaf.localFeature} at boot in the karaf-parent,
    which works fine if it’s undefined and loads nothing  (colindixon,
    18:58:09)
  * when you define that in your pom file, it will load that *one*
    feature when karaf comes up  (colindixon, 18:59:45)



Meeting ended at 19:05:36 UTC.



People present (lines said)
---------------------------

* colindixon (26)
* alagalah (17)
* tbachman (6)
* regXboi (5)
* odl_meetbot (3)
* hideyuki (2)
* tykeal (1)
* zxiiro (1)



Generated by `MeetBot`_ 0.1.4