NetRexx 3.01 released and available
Locked
12
12
 
|
Not without a modicum of pride the NetRexx Development Team announces the immediate availability of NetRexx 3.01, the first RexxLA release of the language after last year's 3.00, which did not include functional changes. All functional changes and additions in this release are documented in the file releasenotes.txt, included in the package.
It is available for download following the download link on http://www.netrexx.org - or with the following direct links: http://ec2-67-202-36-54.compute-1.amazonaws.com/files/NetRexx-3.01.zip (most bandwidth, specially from the US) http://www.netrexx.org/files/NetRexx-3.01.zip This release is equal to 3.01RC3 which was released a fortnight ago, and is only different in build date, version numbers and additions to the documentation. No problems have been reported for RC3. Do note that the Quick Start Guide is new but considered the replacement of the User's Guide. The Programmer's Guide is incomplete but included to give a glimpse of its direction and because it might help someone even in this rudimentary state. The NetRexx Language Reference 3.01 is an almost unchanged nrl3, renamed for clarity after comments from new users. It still is complete and authoritative. All input on the documentation is welcome and will find its way quickly into new versions. The documents will be updated frequently and a special download location will be reserved for them. We would like to thank everyone who has made this release possible, and please realize that this is only the beginning. Please run with this version as much (and as soon) as possible, and leave comments on this list or as issues on the kenai site tracker. When no major problems occur, we can start the planning for 3.02. Your input on this process is most welcome. best regards, on behalf of the development team, René Vincent Jansen, project manager, RexxLA NetRexx project. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
Re: NetRexx 3.01 released and available
|
|
Looks nice. Great job to all. "The King is dead. Long live the King."
On Thu, Aug 23, 2012 at 4:41 PM, René Jansen <[hidden email]> wrote: Not without a modicum of pride the NetRexx Development Team announces the immediate availability of NetRexx 3.01, the first RexxLA release of the language after last year's 3.00, which did not include functional changes. All functional changes and additions in this release are documented in the file releasenotes.txt, included in the package. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
One teeny wrinkle in an otherwise sterling delivery: the CompileFromString.nrx sample in the package doesn't; it comes back with the following error:
Program CompileFromString.nrx
2 +++ translator=RxTranslator() -- construct translator +++ ^^^^^^^^^^^^
+++ Error: The method 'RxTranslator()' cannot be found in class 'CompileFromString' or a superclass Compilation of 'CompileFromString.nrx' failed [one error]
By changing the import from: import COM.ibm.netrexx. to:
import org.netrexx.process. Regards, Alan.
On 23 August 2012 14:04, Jason Martin <[hidden email]> wrote: -- Looks nice. Great job to all. "The King is dead. Long live the King." Can't tweet, won't tweet! _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/
Alan
-- Needs more cowbell. |
Re: NetRexx 3.01 released and available
|
|
In reply to this post by rvjansen
Wow! Congrats to the team! As soon as I can find some time, I'll have a go
at it! Houston we have lift off... :-) Michael -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of René Jansen Sent: Thursday, August 23, 2012 22:41 To: IBM Netrexx Subject: [Ibm-netrexx] NetRexx 3.01 released and available Not without a modicum of pride the NetRexx Development Team announces the immediate availability of NetRexx 3.01, the first RexxLA release of the language after last year's 3.00, which did not include functional changes. All functional changes and additions in this release are documented in the file releasenotes.txt, included in the package. <snip/> best regards, on behalf of the development team, René Vincent Jansen, project manager, RexxLA NetRexx project. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by alansam
Alan,
thanks for finding this out and reporting it. I will look into it, and I am sure Kermit will too when he finds a computer while unpacking. I can replace the example, but I am worried more about the 'fallback' to the old package name not working well in this case. Added to the test cases. (somewhere today) best regards, René Jansen. On 24 aug. 2012, at 06:17, Alan Sampson <[hidden email]> wrote: One teeny wrinkle in an otherwise sterling delivery: the CompileFromString.nrx sample in the package doesn't; it comes back with the following error: _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
Re: NetRexx 3.01 released and available
|
|
Hi René -
Great job on the 3.01 release. It is much appreciated! I looked at the example program mentioned below (CompileFromString.nrx). It seems to be based on some experimental code I created before we defined the APIs for compiling and interpreting from memory strings (and before we changed package names). See the comments to issue NetRexx-5 for details. Please replace that example with the following examples which use the defined APIs for compiling and interpreting from strings. These will work with "import COM.ibm.netrexx." as well as the newer "import org.netrexx." statements. --------------------------Compile example:---------------------------------- import org.netrexx. /* NetRexx compile from string example */ programstring = "say 'hello there via NetRexxC'" NetRexxC.main("myprogram",programstring) --------------------------Interpret example:---------------------------------- import org.netrexx. /* NetRexx interpret from memory string example */ programstring="say 'hello from an interpreted memory string' " NetRexxA().interpret("myprogram",programstring) --------------------------------------------------------------------------------------- -- Kermit On 8/23/2012 10:48 PM, René Jansen
wrote:
Alan, _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Rene,
First, thank you for all your efforts! I'm still trying to recreate the NetRexx build process without much luck. As you know from my recent JIRA, I haven't been able to make it work with Eclipse. Could you please explain exactly what the steps are? After the download from SVN, exactly what is done? Is Ant used, or did you use a different method? I couldn't find any description of the build process. If missed it, could you point me to it? I'll follow your process (outside of Eclipse) to try to determine what the problem is. Thanks again. Bill _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Hi Bill,
just did a build on a clean Linux on the Raspberry - svn co, cd to trunk, make. Make uses ant and does not do anything on itself anymore. So you can just use the ant command line that is after the all: target in make. The ant command line escapes my memory. The build process is documented, for the moment, in build.xml - there is a dependency problem that is deftly solved in build.xml, not by me by the way. The kenai wiki might say some words about the build process but I doubt that it has more than this email. So not to be lazy, the command lines are: java -jar ant/ant-launcher.jar compile java -jar ant/ant-launcher.jar jars Which, as I correctly remembered, is documented here: http://kenai.com/projects/netrexx/pages/NrxSetup best regards, René. On 25 aug. 2012, at 02:08, Bill Fenlason <[hidden email]> wrote: > Rene, > > First, thank you for all your efforts! > > I'm still trying to recreate the NetRexx build process without much luck. As you know from my recent JIRA, I haven't been able to make it work with Eclipse. > > Could you please explain exactly what the steps are? > > After the download from SVN, exactly what is done? Is Ant used, or did you use a different method? > > I couldn't find any description of the build process. If missed it, could you point me to it? > > I'll follow your process (outside of Eclipse) to try to determine what the problem is. > > Thanks again. > > Bill > > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
I tested the build on Win7 from the command line and from Antelope in
jEdit this morning with no problems. Have not had time to try with Linux yet. The following scripts which I added to the after3.01 branch and probably should have added to trunk simplify the process from the command line (just say "build clean" and "build" in the trunk directory) build.bat: ---------------------------------------------------------------------------------------- @rem start for NetRexx Ant build @echo off java -jar ant\ant-launcher.jar %1 %2 %3 %4 %5 %6 %7 %8 %9 ---------------------------------------------------------------------------------------- build.sh: ---------------------------------------------------------------------------------------- #!/bin/sh # BASH script to execute NetRexx Ant build # ----------------------------------------------------------------- # Reminder: to make this executable: chmod 751 build.sh # ----------------------------------------------------------------- java -jar ant/ant-launcher.jar $* --------------------------------------------------------------------------------------- Unfortunately I am not yet an Eclipse user (hope to rectify that soon) so I have not tested the build there. The Eclipse problem may have to do with the current directory when running the build. -- Kermit On 8/24/2012 2:18 PM, René Jansen wrote: > Hi Bill, > > just did a build on a clean Linux on the Raspberry - svn co, cd to trunk, make. > > Make uses ant and does not do anything on itself anymore. So you can just use the ant command line that is after the all: target in make. The ant command line escapes my memory. > > The build process is documented, for the moment, in build.xml - there is a dependency problem that is deftly solved in build.xml, not by me by the way. > > The kenai wiki might say some words about the build process but I doubt that it has more than this email. > > So not to be lazy, the command lines are: > > java -jar ant/ant-launcher.jar compile > java -jar ant/ant-launcher.jar jars > > > Which, as I correctly remembered, is documented here: http://kenai.com/projects/netrexx/pages/NrxSetup > > best regards, > > René. > > On 25 aug. 2012, at 02:08, Bill Fenlason <[hidden email]> wrote: > >> Rene, >> >> First, thank you for all your efforts! >> >> I'm still trying to recreate the NetRexx build process without much luck. As you know from my recent JIRA, I haven't been able to make it work with Eclipse. >> >> Could you please explain exactly what the steps are? >> >> After the download from SVN, exactly what is done? Is Ant used, or did you use a different method? >> >> I couldn't find any description of the build process. If missed it, could you point me to it? >> >> I'll follow your process (outside of Eclipse) to try to determine what the problem is. >> >> Thanks again. >> >> Bill >> >> >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >> > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by rvjansen
I missed the wiki, thanks for the pointer.
For those of us that use Eclipse, being able to use the extensive SVN support and a simple one click build will be useful - I'll try to do that. When set up correctly, one click netrexx compiles trigger the java compile, and project builds are done automatically. On 8/24/2012 8:18 PM, René Jansen wrote: > Hi Bill, > > just did a build on a clean Linux on the Raspberry - svn co, cd to trunk, make. > > Make uses ant and does not do anything on itself anymore. So you can just use the ant command line that is after the all: target in make. The ant command line escapes my memory. > > The build process is documented, for the moment, in build.xml - there is a dependency problem that is deftly solved in build.xml, not by me by the way. > > The kenai wiki might say some words about the build process but I doubt that it has more than this email. > > So not to be lazy, the command lines are: > > java -jar ant/ant-launcher.jar compile > java -jar ant/ant-launcher.jar jars > > > Which, as I correctly remembered, is documented here: http://kenai.com/projects/netrexx/pages/NrxSetup > > best regards, > > René. > > On 25 aug. 2012, at 02:08, Bill Fenlason <[hidden email]> wrote: > >> Rene, >> >> First, thank you for all your efforts! >> >> I'm still trying to recreate the NetRexx build process without much luck. As you know from my recent JIRA, I haven't been able to make it work with Eclipse. >> >> Could you please explain exactly what the steps are? >> >> After the download from SVN, exactly what is done? Is Ant used, or did you use a different method? >> >> I couldn't find any description of the build process. If missed it, could you point me to it? >> >> I'll follow your process (outside of Eclipse) to try to determine what the problem is. >> >> Thanks again. >> >> Bill >> >> >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >> > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2197 / Virus Database: 2437/5221 - Release Date: 08/24/12 > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by Kermit Kiser
Kermit,
The build works successfully from the command line on my system - I've posted details in the JIRA issue. I thought that ant-launcher was part of ant, but now I suspect it is not? I could not find the source for it. Is it in SVN? For Eclipse, a standard ant build.xml file and normal ant invocation are probably required. Is there some reason that is difficult? I suspect that the ant-launcher is doing something that should be done in the build file? Bill PS let me know if there is anything I can do to help you with Eclipse. On 8/24/2012 8:45 PM, Kermit Kiser wrote: > I tested the build on Win7 from the command line and from Antelope in > jEdit this morning with no problems. Have not had time to try with > Linux yet. The following scripts which I added to the after3.01 branch > and probably should have added to trunk simplify the process from the > command line (just say "build clean" and "build" in the trunk directory) > > build.bat: > ---------------------------------------------------------------------------------------- > > @rem start for NetRexx Ant build > @echo off > java -jar ant\ant-launcher.jar %1 %2 %3 %4 %5 %6 %7 %8 %9 > ---------------------------------------------------------------------------------------- > > > build.sh: > ---------------------------------------------------------------------------------------- > > #!/bin/sh > # BASH script to execute NetRexx Ant build > # ----------------------------------------------------------------- > # Reminder: to make this executable: chmod 751 build.sh > # ----------------------------------------------------------------- > > java -jar ant/ant-launcher.jar $* > --------------------------------------------------------------------------------------- > > > Unfortunately I am not yet an Eclipse user (hope to rectify that soon) > so I have not tested the build there. The Eclipse problem may have to > do with the current directory when running the build. > > -- Kermit > > > On 8/24/2012 2:18 PM, René Jansen wrote: >> Hi Bill, >> >> just did a build on a clean Linux on the Raspberry - svn co, cd to >> trunk, make. >> >> Make uses ant and does not do anything on itself anymore. So you can >> just use the ant command line that is after the all: target in make. >> The ant command line escapes my memory. >> >> The build process is documented, for the moment, in build.xml - there >> is a dependency problem that is deftly solved in build.xml, not by me >> by the way. >> >> The kenai wiki might say some words about the build process but I >> doubt that it has more than this email. >> >> So not to be lazy, the command lines are: >> >> java -jar ant/ant-launcher.jar compile >> java -jar ant/ant-launcher.jar jars >> >> >> Which, as I correctly remembered, is documented here: >> http://kenai.com/projects/netrexx/pages/NrxSetup >> >> best regards, >> >> René. >> On 25 aug. 2012, at 02:08, Bill Fenlason <[hidden email]> wrote: >> >>> Rene, >>> >>> First, thank you for all your efforts! >>> >>> I'm still trying to recreate the NetRexx build process without much >>> luck. As you know from my recent JIRA, I haven't been able to make >>> it work with Eclipse. >>> >>> Could you please explain exactly what the steps are? >>> >>> After the download from SVN, exactly what is done? Is Ant used, or >>> did you use a different method? >>> >>> I couldn't find any description of the build process. If missed it, >>> could you point me to it? >>> >>> I'll follow your process (outside of Eclipse) to try to determine >>> what the problem is. >>> >>> Thanks again. >>> >>> Bill >>> >>> >>> _______________________________________________ >>> Ibm-netrexx mailing list >>> [hidden email] >>> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >>> >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >> >> >> > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2197 / Virus Database: 2437/5221 - Release Date: 08/24/12 > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
When I run a command line "dist" build, which is the default, I get an
error because "javadoc.exe" can not be found. Is this a known problem? _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by billfen
Hi Bill -
Some of what I say here is my opinion but it is probably valid as I designed part of the current build process. I think ant-launcher.jar is part of Ant. We included that jar and the ant.jar with the source distribution for various reasons. One is so that building NetRexx only requires a JDK and not an Ant installation. (With ecj now included it may not even require the JDK. I have not tried that.) Another is that Ant plays some odd tricks with classpath while it is starting which means that it will favor it's own obsolete copy of the ant-netrexx.jar task and may require that NetRexxC.jar be copied to the Ant installation's lib directory. Our customized build.xml setup allows us to use a "bootstrap" NetRexx compiler for the first part of the build process then switch to the newly built compiler in order to compile and run the diagnostic tests. (By the way, if René reads this - the current bootstrap compiler in the distribution is at the RC1 level - it probably should be switched to the final version.) Thanks for the help offer. I am learning Eclipse in my spare time and have no intelligent questions yet. -- Kermit On 8/24/2012 8:09 PM, Bill Fenlason wrote: > Kermit, > > The build works successfully from the command line on my system - I've > posted details in the JIRA issue. I thought that ant-launcher was > part of ant, but now I suspect it is not? I could not find the source > for it. Is it in SVN? > > For Eclipse, a standard ant build.xml file and normal ant invocation > are probably required. Is there some reason that is difficult? > > I suspect that the ant-launcher is doing something that should be done > in the build file? > > Bill > > PS let me know if there is anything I can do to help you with Eclipse. > > > On 8/24/2012 8:45 PM, Kermit Kiser wrote: >> I tested the build on Win7 from the command line and from Antelope in >> jEdit this morning with no problems. Have not had time to try with >> Linux yet. The following scripts which I added to the after3.01 >> branch and probably should have added to trunk simplify the process >> from the command line (just say "build clean" and "build" in the >> trunk directory) >> >> build.bat: >> ---------------------------------------------------------------------------------------- >> >> @rem start for NetRexx Ant build >> @echo off >> java -jar ant\ant-launcher.jar %1 %2 %3 %4 %5 %6 %7 %8 %9 >> ---------------------------------------------------------------------------------------- >> >> >> build.sh: >> ---------------------------------------------------------------------------------------- >> >> #!/bin/sh >> # BASH script to execute NetRexx Ant build >> # ----------------------------------------------------------------- >> # Reminder: to make this executable: chmod 751 build.sh >> # ----------------------------------------------------------------- >> >> java -jar ant/ant-launcher.jar $* >> --------------------------------------------------------------------------------------- >> >> >> Unfortunately I am not yet an Eclipse user (hope to rectify that >> soon) so I have not tested the build there. The Eclipse problem may >> have to do with the current directory when running the build. >> >> -- Kermit >> >> >> On 8/24/2012 2:18 PM, René Jansen wrote: >>> Hi Bill, >>> >>> just did a build on a clean Linux on the Raspberry - svn co, cd to >>> trunk, make. >>> >>> Make uses ant and does not do anything on itself anymore. So you can >>> just use the ant command line that is after the all: target in make. >>> The ant command line escapes my memory. >>> >>> The build process is documented, for the moment, in build.xml - >>> there is a dependency problem that is deftly solved in build.xml, >>> not by me by the way. >>> >>> The kenai wiki might say some words about the build process but I >>> doubt that it has more than this email. >>> >>> So not to be lazy, the command lines are: >>> >>> java -jar ant/ant-launcher.jar compile >>> java -jar ant/ant-launcher.jar jars >>> >>> >>> Which, as I correctly remembered, is documented here: >>> http://kenai.com/projects/netrexx/pages/NrxSetup >>> >>> best regards, >>> >>> René. >>> On 25 aug. 2012, at 02:08, Bill Fenlason <[hidden email]> wrote: >>> >>>> Rene, >>>> >>>> First, thank you for all your efforts! >>>> >>>> I'm still trying to recreate the NetRexx build process without much >>>> luck. As you know from my recent JIRA, I haven't been able to make >>>> it work with Eclipse. >>>> >>>> Could you please explain exactly what the steps are? >>>> >>>> After the download from SVN, exactly what is done? Is Ant used, or >>>> did you use a different method? >>>> >>>> I couldn't find any description of the build process. If missed >>>> it, could you point me to it? >>>> >>>> I'll follow your process (outside of Eclipse) to try to determine >>>> what the problem is. >>>> >>>> Thanks again. >>>> >>>> Bill >>>> >>>> >>>> _______________________________________________ >>>> Ibm-netrexx mailing list >>>> [hidden email] >>>> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >>>> >>> _______________________________________________ >>> Ibm-netrexx mailing list >>> [hidden email] >>> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >>> >>> >>> >> >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ >> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.2197 / Virus Database: 2437/5221 - Release Date: >> 08/24/12 >> >> >> > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by billfen
"javadoc.exe" is included with the JDK. You may need to copy it to the
bin directory of the Java install (jre) running the build. You can also just run a "jars" build which will build the NetRexx jars but will not try to create the javadocs. -- Kermit On 8/24/2012 8:48 PM, Bill Fenlason wrote: > When I run a command line "dist" build, which is the default, I get an > error because "javadoc.exe" can not be found. Is this a known problem? > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Then again, what is Eclipse using for javadoc generation nowadays?
If we are including its java compiler we could include its javadoc tool as well - Saludos / Kind regards, David Requena NOTE: The opinions expressed here represent the opinions of the authors and do not necessarily represent the opinions of those who hold other opinions. -----Original Message----- From: Kermit Kiser <[hidden email]> Sender: [hidden email] Date: Fri, 24 Aug 2012 23:29:06 To: IBM Netrexx<[hidden email]> Reply-To: IBM Netrexx <[hidden email]> Subject: Re: [Ibm-netrexx] Build process "javadoc.exe" is included with the JDK. You may need to copy it to the bin directory of the Java install (jre) running the build. You can also just run a "jars" build which will build the NetRexx jars but will not try to create the javadocs. -- Kermit On 8/24/2012 8:48 PM, Bill Fenlason wrote: > When I run a command line "dist" build, which is the default, I get an > error because "javadoc.exe" can not be found. Is this a known problem? > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by Kermit Kiser
Having to copy things from the JDK into the JRE doesn't sound right to
me. Can the path be set either explicitly or implicitly in the build.xml file? The javadoc.exe file is in the JDK \bin directory. It seems to me that since the JDK must be located for the tools jar, no file copying should be necessary? Ant is distributed with Eclipse, including the NetRexx ant task - it looks as if the custom ant processing for NetRexx may be problematic. Eclipse allow custom builds so perhaps there is a work around, but that may take some effort. Custom ant tasks can be specified relatively easily, so I'll see if that does the trick. It's unfortunate that the standard ant, netrexx task and build.xml approach could not be used. I verified that ant-launcher is indeed part of ant, and that it produces the "unable to locate tools.jar" message. When I get this all straightened out I'll write up a simple "Eclipse setup for NetRexx development" readme. Bill On 8/25/2012 5:29 AM, Kermit Kiser wrote: > "javadoc.exe" is included with the JDK. You may need to copy it to the > bin directory of the Java install (jre) running the build. > > You can also just run a "jars" build which will build the NetRexx jars > but will not try to create the javadocs. > > -- Kermit > > On 8/24/2012 8:48 PM, Bill Fenlason wrote: >> When I run a command line "dist" build, which is the default, I get >> an error because "javadoc.exe" can not be found. Is this a known >> problem? _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by David Requena
Eclipse uses Main Menu-> Project-> Generate JavaDoc which brings up a
wizard. It must be configured to point to the javadoc.exe file in the JDK via browse and click. After that it processes java files in the src directory by one click and puts the output in a \doc (or other) directory. (but the NetRexx project is not organized that way - I'm checking for a workaround). On 8/25/2012 6:35 AM, David Requena wrote: > Then again, what is Eclipse using for javadoc generation nowadays? > > If we are including its java compiler we could include its javadoc tool as well > > - > Saludos / Kind regards, > David Requena > > NOTE: The opinions expressed here represent the opinions > of the authors and do not necessarily represent the opinions > of those who hold other opinions. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by billfen
Problem solved - needed to fix the ant class path. One click builds.
I'll provide a simple Eclipse setup guide. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
Great, many thanks Bill
- Saludos / Kind regards, David Requena NOTE: The opinions expressed here represent the opinions of the authors and do not necessarily represent the opinions of those who hold other opinions. -----Original Message----- From: Bill Fenlason <[hidden email]> Sender: [hidden email] Date: Sat, 25 Aug 2012 08:40:26 To: IBM Netrexx<[hidden email]> Reply-To: IBM Netrexx <[hidden email]> Subject: Re: [Ibm-netrexx] Build process Problem solved - needed to fix the ant class path. One click builds. I'll provide a simple Eclipse setup guide. _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
|
|
In reply to this post by billfen
Good point Bill. I don't really know how Ant finds the javadoc module. I
have been assuming that it needed to be in the system path like java.exe or in the Java bin directory for the active Java VM but that was just a wild guess. Oddly, it seemed to work for me but that may be "dumb luck". Do you know how it actually works? -- Kermit On 8/25/2012 12:40 AM, Bill Fenlason wrote: > Having to copy things from the JDK into the JRE doesn't sound right to > me. Can the path be set either explicitly or implicitly in the > build.xml file? The javadoc.exe file is in the JDK \bin directory. It > seems to me that since the JDK must be located for the tools jar, no > file copying should be necessary? > > Ant is distributed with Eclipse, including the NetRexx ant task - it > looks as if the custom ant processing for NetRexx may be problematic. > Eclipse allow custom builds so perhaps there is a work around, but > that may take some effort. Custom ant tasks can be specified > relatively easily, so I'll see if that does the trick. It's > unfortunate that the standard ant, netrexx task and build.xml approach > could not be used. > > I verified that ant-launcher is indeed part of ant, and that it > produces the "unable to locate tools.jar" message. > > When I get this all straightened out I'll write up a simple "Eclipse > setup for NetRexx development" readme. > > Bill > > On 8/25/2012 5:29 AM, Kermit Kiser wrote: >> "javadoc.exe" is included with the JDK. You may need to copy it to >> the bin directory of the Java install (jre) running the build. >> >> You can also just run a "jars" build which will build the NetRexx >> jars but will not try to create the javadocs. >> >> -- Kermit >> >> On 8/24/2012 8:48 PM, Bill Fenlason wrote: >>> When I run a command line "dist" build, which is the default, I get >>> an error because "javadoc.exe" can not be found. Is this a known >>> problem? > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ > > > _______________________________________________ Ibm-netrexx mailing list [hidden email] Online Archive : http://ibm-netrexx.215625.n3.nabble.com/ |
«
Return to ibm-netrexx
|
1 view|%1 views
| Free forum by Nabble | Edit this page |