You can subscribe to this list here.
2008 |
Jan
(12) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|
From: Scot P. F. <fl...@mi...> - 2008-04-23 14:00:08
|
All: I hit a snag recently while fixing our documentation to reflect some of the latest changes to Keros. This has yielded 3 additional feature requests in addition to the 1 for documentation changes. The crux of the problem is related to Ant 1.7.0 and earlier - one cannot utilize scriptdef's without the "-lib" command line option (you end up with a class not defined exception). As Keros will do automatic downloads - the downloads are strewn all over ~/.keros directory. Trying to document where to find those jar files as part of the "-lib" option was terribly cumbersome. Therefore, the following feature requests have been opened: * 1949700 (http://sourceforge.net/tracker/index.php?func=detail&aid=1949700&group_id=214037&atid=1028081) * 1949704 (http://sourceforge.net/tracker/index.php?func=detail&aid=1949704&group_id=214037&atid=1028081) * 1949708 (http://sourceforge.net/tracker/index.php?func=detail&aid=1949708&group_id=214037&atid=1028081) These feature requests will be addressed in the order listed above - and must be resolved before 0.2 is released. If anyone has any questions, please review the above links first. Then send out an email to the list so it can be discussed... Sorry for the delay - but this is important to resolve first. I'd rather take longer on the release and it be easily usable for Ant users. /*Many thanks to Phillip "oh voice of reason" Rhodes for working with me through this issue :)*/ -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-04-20 16:09:29
|
All: I am almost ready to release 0.2. The time to complete a build for Keros has dramatically improved - on a dual PIII 800 it takes approximate 40 seconds... I've changed the test and build XMLs dramatically... Additionally, we now have 2 XML files: keros.xml (reusable macros) and keros-build.xml (for building)... -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-04-11 11:01:42
|
All: Sorry for such slow development at Keros :( I just...finally...completed some functionality to download complete third party apps and install them. So, no longer will Keros distribute things such as Find Bugs, Bean Shell, etc. This functionality was completed in Feature Request #1875352 (http://sourceforge.net/tracker/index.php?func=detail&aid=1875352&group_id=214037&atid=1028081) - and was a real pain to figure out. Eventually some of the downloads will disappear when we introduce Ivy... Unfortunately, Ivy won't be introduced till the 0.3 time frame. Anyway, just wanted to give y'all a "heads up" - and to know I am still working on Keros ;) Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-20 16:29:18
|
All: As I have been gearing up for the merge with Open Qabal's build process, I've discovered some features that were needed (and some bugs too). I've added quite a few things that will require documentation as well... Therefore, I think it is more likely that the next release will contain all this new functionality and the release after that be the OQ build process merge. I'd like to isolate these initial releases so as not to introduce too much thereby creating a more brittle release. Besides, I will need to do documentation to support these new features and am more apt to complete this with less to document ;) Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-17 16:18:33
|
All: There are currently 3 bugs opened at Keros. They are more or less "low hanging fruit" - meaning I can knock it out pretty quickly. Ideally I'd like to have no bugs and integration with OQ for the 0.2 release. Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-17 14:51:45
|
All: I just got all JPlate Environment bugs/feature requests moved over to Keros... Now I can start looking at OQ integration. -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-16 20:31:12
|
All: I am in the process of moving over all the JPlate Environment bugs/Feature requests to Keros. Its a manual process and there are many to copy :( I should have it done by tomorrow... Then I will be concentrating on the OQ build process merge... Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-15 17:59:44
|
All: I released 0.1 yesterday and within hours we had 4 downloads... I am pleased :) Anyway, I am starting in on the 0.2 release. I have managed to fix some feature requests I recently opened... Minor nits mostly but things I wanted to fix: for example consistent Keros based namespaces and project naming in the Ant scripts. My next big task is going to move all JPlate Environment bugs/feature requests over to Keros. Then I will be moving on to merge Open Qabal's build process with Keros. Ideally, 0.2 will simply be the minor fixed feature requests mentioned above along with the OQ merge. As I am not sure how much work will be involved with this merge, I cannot speculate as to the duration until completion. However, do note that I deleted the JPlate Environment. This translates to my source tree at JPlate is now broken and one cannot build from source any longer. I clearly have a real need to get Keros in working order so I can fix JPlate ;) Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-14 19:42:24
|
All: Keros 0.1 is ready for release. Tomorrow I will be releasing it... Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-14 18:03:11
|
All: Just to let you know, I just fixed two feature requests: * 1866060 * 1866062 Both deal with removing references to JPlate from Keros (one in code and one in the documentation). I just closed both feature requests as being fixed. I do see, however, that the name of the releases is off (it comes out something like keros-trunk-0.1.YYY). I need to figure out whats wrong and then I think 0.1 can be released. Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-14 15:24:50
|
All: I should be done with 0.1 shortly. I am going to remove all the test code I have checked in and start to use Ant Unit. My intention is to clean up some of the "assert" related code in place, and use Ant Unit where appropriate. In summary, 0.1 should be released this week minus all test code. For 0.2, I will concentrate on introducing Ant Unit as well as a bug and maybe a few feature requests. Shortly thereafter I will look at merging in Open Qabal's build process - perhaps for a 0.3 release. Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-13 18:49:18
|
All: Please check out this bug created against Ant. This will make Keros much much more portable and as a project more easily supported by a tool like Ivy. The crux of this bug/feature is that it allows one to import files from a classpath resource. The neat thing is that Keros could conceivably be distributed as a whole in one jar file :) Anyway, take a peak and give me your thoughts... PS: Phillip, sorry for duping this email to you...the developer list was bouncing back all my emails... I did a cut and paste below... This is really good progress. Is there any technical issue to enable remote ant build file by http or whatever? The goal is to enable to start writting a build just referencing a remote build file (may be cached in a temp that would be used if remote unavailable) and to share build among several project easily... jonathan doklovic-2 wrote: > > > > I added a bug to the bug database and attached a patch that adds the > > same classpath functionality as taskdef to the import task. > > > > http://issues.apache.org/bugzilla/show_bug.cgi?id=44214 > > > > - Jonathan > > > > On Fri, 2008-01-11 at 09:40 -0800, kermitt wrote: > >> >> In a previous post I suggest this: >> >> >> >> I wish Ant import would support URL + jar like that : >> >> >> >> <project ...> >> >> <import url="http://repo/build.jar!common-build.xml"/> >> >> </project> >> >> >> >> As ivy became a sub project, it would make sense to have a closer >> >> integration like : >> >> >> >> <project ...> >> >> <import url="ivy://settings.xml:org/module/artifact@MyResolver" /> >> >> <!-- >> >> would locate the settings.xml file and seek a build-common.xml file using >> >> MyResolver resolver. >> >> --> >> >> </project> >> >> >> >> we could imagine deeper integration : >> >> >> >> <project ...> >> >> <import url="ivy://settings.xml:org/module/artifact@MyResolver" >> >> ivyFile="${basedir]/ivy.xml"/> >> >> <!-- >> >> configure ivy / read the ivy file >> >> would map each ivy configuration to a path ( path could use a lazy >> >> resolve >> >> proxy: resolve only when it get used) >> >> would import resolved artifcat as an ant build file >> >> >> >> --> >> >> </project> >> >> >> >> jonathan doklovic-2 wrote: >> >>> >> > >>> >> > Hi, >>> >> > >>> >> > I know there's not currently a way to do this, but I think it would be >>> >> > very helpful to be able to use the import task to import a file from a >>> >> > jar. >>> >> > >>> >> > This way, when I have a handful of projects, all with common targets, I >>> >> > can put the common.xml build file in a jar and have each project depend >>> >> > on that jar. >>> >> > >>> >> > Combined with something like ivy, I think this would be a pretty good >>> >> > way to share common targets among multiple projects that may not have >>> >> > anything to do with each other. >>> >> > >>> >> > Any thoughts? >>> >> > >>> >> > Any way to do this now? >>> >> > >>> >> > - Jonathan -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-13 18:40:01
|
From me - please disregard -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-11 14:21:42
|
Vamsee: One thing we need bad is the use of Ant Unit for unit testing. I have "rolled my own" unit test cases...but its far from standard. It works...but again...not standard... If you are interested, here is the link: http://ant.apache.org/antlibs/antunit One reason I mention this is that by writing the unit test cases, this will certainly familiarize you with all the Ant code... Its up to you - no pressure... Just let me know if you are interested... Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros |
From: Scot P. F. <fl...@mi...> - 2008-01-09 16:46:48
|
All: Just a note to let y'all know that the code from the JPlate Environment has all been checked into Keros and builds fine. Some things I have done thus far follows: * Set up two mailing lists: one for announcements and one for developers. * Created bug/feature request categories and groups. * I fixed one bug where I had a bad revision start for Subversion. This deals with generating HTML from Subversion logs. Not really important but doing a full build failed. * Opened two feature requests: o Change all programmatic references to anything JPlate related o Change all documentation references to anything JPlate related My main priority right now is to make what is currently in Subversion be reflective of Keros only. Once this is completed I will be performing the following: * 0.1 release * Move over bugs/feature requests as they currently exist in JPlate for the Environment. These artifacts will still require attention in Keros. * Merge the Open Qabal build process into Keros. I will then do a 0.2 release. This is a huge priority for me...so expect to see most of my time spent on Keros. I'll work as quickly as I can...but the above, I believe, is the way to go now... Vamsee, just keep reading over the documentation and "come up to speed." We can worry about assigning you some bugs/feature requests later... If you have any question let me know... And, if y'all don't mind - let's please use the mailing list so we have a running archive of correspondence. Additionally, I will try to get together some additional documentation on how I'd like us to check stuff in... Its mostly administrative related...but if done correctly will aid in our generated HTML docs... We can discuss this later... I think we may want to solicit some QA people...but for now we can do it ourselves. Flossy -- Scot P. Floess 27 Lake Royale Louisburg, NC 27549 252-478-8087 (Home) 919-754-4592 (Work) Chief Architect JPlate http://sourceforge.net/projects/jplate Chief Architect JavaPIM http://sourceforge.net/projects/javapim Architect Keros http://sourceforge.net/projects/keros QA Engineer OpenQabal http://openqabal.dev.java.net |