Menu
▾
▴
braid-devel — Developer's mailing list, used for all discussions about the Braid project.
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
(2) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Gary T. <ga...@we...> - 2008-04-15 02:20:37
|
Very cool Ryan! I'm looking forward to putting a bow on those plugins for the 1.8 release of Mirth. On Sun, Apr 13, 2008 at 4:06 PM, Bloom, Ryan <Rya...@mi...> wrote: > I have finally committed the Mirth plugins to the Braid repository. I'm > sorry this took me so long, but I forgot for a while, and I was trying > to get the build system better. I am going to reconfigure the build > systems for the plugins a little between today and tomorrow. I am going > to consolidate the configuration of the build system so that you can > configure the build once and be able to build all of the plugins. I am > also going to move the build scripts to the top-level build.xml so that > the plugins can be built with a single command. > > Ryan > > Ryan Bloom > Director of Open Source Initiatives -- Healthcare > > Misys plc > 8529 Six Forks Road, Raleigh, North Carolina 27615 > > T (919) 329-1061 > M (919) 559-9433 > E rya...@mi... > www.misys.com > > > > This email and any attachments have been scanned for known viruses using > multiple scanners. We believe that this email and any attachments are virus > free, however the recipient must take full responsibility for virus > checking. > This email message is intended for the named recipient only. It may be > privileged and/or confidential. If you are not the named recipient of this > email please notify us immediately and do not copy it or use it for any > purpose, nor disclose its contents to any other person. > |
|
From: Bloom, R. <Rya...@mi...> - 2008-04-13 23:07:32
|
I have finally committed the Mirth plugins to the Braid repository. I'm sorry this took me so long, but I forgot for a while, and I was trying to get the build system better. I am going to reconfigure the build systems for the plugins a little between today and tomorrow. I am going to consolidate the configuration of the build system so that you can configure the build once and be able to build all of the plugins. I am also going to move the build scripts to the top-level build.xml so that the plugins can be built with a single command. Ryan Ryan Bloom Director of Open Source Initiatives -- Healthcare Misys plc 8529 Six Forks Road, Raleigh, North Carolina 27615 T (919) 329-1061 M (919) 559-9433 E rya...@mi... www.misys.com This email and any attachments have been scanned for known viruses using multiple scanners. We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. |
|
From: Bloom, R. <Rya...@mi...> - 2008-04-01 12:58:48
|
I got the new build system up to the same state as the old systems last night (took way too long, but I haven't had a lot of time. I would like to delete the old build systems soon. To use the new build system, at the root directory, run "ant build" -- build the code "ant dist" -- build two jars in build/dist My next step is to add a task to run the unit tests, and then add in the code from WebReach to create Mirth channels. Comments? Ryan Ryan Bloom Director of Open Source Initiatives -- Healthcare Misys plc 8529 Six Forks Road, Raleigh, North Carolina 27615 T (919) 329-1061 M (919) 559-9433 E rya...@mi... www.misys.com This email and any attachments have been scanned for known viruses using multiple scanners. We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. |
|
From: Bloom, R. <Rya...@mi...> - 2008-02-28 16:07:25
|
Now that I am back from HIMSS, I wanted to take a few seconds and go through the projects that we need to tackle in the braid project. There are four initial projects that I see, and I am going to go after the first two this week. After these first four are done, we will need to decide what features we want to continue to add to the project. The first three tasks are: 1) Simplify the build system, and provide more functionality in the build system 2) Re-factor the code to use net.sf.braid package space. (this will break other code, but that can't be helped easily). 3) Fix all of the unit tests. 4) Create a project web site I am going to work on 1 and 2 first. The second project will impact code that WebReach is going to contribute soon, but that should be easy to resolve when the contribution is made. Ryan Ryan Bloom Director of Open Source Initiatives -- Healthcare Misys plc 8529 Six Forks Road, Raleigh, North Carolina 27615 T (919) 329-1061 M (919) 559-9433 E rya...@mi... www.misys.com This email and any attachments have been scanned for known viruses using multiple scanners. We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. |
|
From: Bloom, R. <Rya...@mi...> - 2008-02-21 22:02:54
|
The code is committed. This is a test to validate that e-mail is working. Ryan Bloom Director of Open Source Initiatives -- Healthcare Misys plc 8529 Six Forks Road, Raleigh, North Carolina 27615 T (919) 329-1061 M (919) 559-9433 E rya...@mi... www.misys.com This email and any attachments have been scanned for known viruses using multiple scanners. We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. |
