netrexx code repository
Locked
 
|
To have a successful NetRexx repository, we need a mechanism to resolve dependencies on the library level. Who has the time to look into http://ant.apache.org/ivy/ and have a first scan if this is a suitable tool, or alternatively, we need the more encompassing 'maven' to perform this role?
Please have a look if you are so inclined and report back to me or the list. best regards, René Jansen. _______________________________________________ Ibm-netrexx mailing list [hidden email] |
|
|
More and more, Java open source projects are standardizing on using
maven to handle builds and dependency resolution. I work with maven all the time and having to step backwards to use ant is always a pain. Rick On Wed, Oct 13, 2010 at 9:20 AM, René Jansen <[hidden email]> wrote: > To have a successful NetRexx repository, we need a mechanism to resolve dependencies on the library level. Who has the time to look into http://ant.apache.org/ivy/ and have a first scan if this is a suitable tool, or alternatively, we need the more encompassing 'maven' to perform this role? > > Please have a look if you are so inclined and report back to me or the list. > > best regards, > > René Jansen. > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > > _______________________________________________ Ibm-netrexx mailing list [hidden email] |
|
|
In reply to this post by rvjansen
I have tons of experience with Maven, and would be happy to help in
its use. It's far from perfect, but it does two things pretty well: dependency management, and enforcing a nice project structure. Pat. -- Defy mediocrity. _______________________________________________ Ibm-netrexx mailing list [hidden email] |
Re: netrexx code repository
|
|
In reply to this post by rickmcguire
Hello Rick,
thanks for your insights & experience results... As I never used ANT up to now (I do have my own *build* process due to a lack of knowledge ...) , I will have a look at MAVEN.... It's so great to have you there at ibm-NetRexx as well... Thomas. ======================================================== Am 13.10.2010 15:43, schrieb Rick McGuire: > More and more, Java open source projects are standardizing on using > maven to handle builds and dependency resolution. I work with maven > all the time and having to step backwards to use ant is always a pain. > > Rick > > On Wed, Oct 13, 2010 at 9:20 AM, René Jansen<[hidden email]> wrote: >> To have a successful NetRexx repository, we need a mechanism to resolve dependencies on the library level. Who has the time to look into http://ant.apache.org/ivy/ and have a first scan if this is a suitable tool, or alternatively, we need the more encompassing 'maven' to perform this role? >> >> Please have a look if you are so inclined and report back to me or the list. >> >> best regards, >> >> René Jansen. >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> >> > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > > -- Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com _______________________________________________ Ibm-netrexx mailing list [hidden email]
Tom. (ths@db-123.com)
|
Re: netrexx code repository
|
|
In reply to this post by Patrick Forhan
Hello Pat,
for my most recent ReyC and PP projects, I could need your MAVEN experience, as well ... Could you give me please an URL where I should *read* first the essentials? Thomas. ========================================================= Am 13.10.2010 15:54, schrieb Patrick Forhan: > I have tons of experience with Maven, and would be happy to help in > its use. It's far from perfect, but it does two things pretty well: > dependency management, and enforcing a nice project structure. > > Pat. > -- Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com _______________________________________________ Ibm-netrexx mailing list [hidden email]
Tom. (ths@db-123.com)
|
Re: netrexx code repository
|
|
In reply to this post by Patrick Forhan
Hi Patrick, & all:
Given that Rene makes a decision which tool to use: Would you be willing to act as the Maven administrator? I'm ready to deploy all of my soft as open source, but do not have the time nor knowledge to learn all this new stuff... I'm currently focussing at translating PL/I and COBOL to NetRexx ... Thomas. ========================================================== Am 13.10.2010 15:54, schrieb Patrick Forhan: > I have tons of experience with Maven, and would be happy to help in > its use. It's far from perfect, but it does two things pretty well: > dependency management, and enforcing a nice project structure. > > Pat. > -- Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com _______________________________________________ Ibm-netrexx mailing list [hidden email]
Tom. (ths@db-123.com)
|
|
|
In reply to this post by Thomas.Schneider.Wien
There's quite a few tutorials out there, but I would start with the
source of it all: http://maven.apache.org/ The first couple of paragraphs have a lot of introductory information. Pat. On Wed, Oct 13, 2010 at 10:51 AM, Thomas Schneider <[hidden email]> wrote: > Hello Pat, > for my most recent ReyC and PP projects, I could need your MAVEN > experience, as well ... > > Could you give me please an URL where I should *read* first the essentials? > Thomas. > ========================================================= > Am 13.10.2010 15:54, schrieb Patrick Forhan: >> >> I have tons of experience with Maven, and would be happy to help in >> its use. It's far from perfect, but it does two things pretty well: >> dependency management, and enforcing a nice project structure. >> >> Pat. >> > > > -- > Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > > -- Defy mediocrity. _______________________________________________ Ibm-netrexx mailing list [hidden email] |
|
|
In reply to this post by Patrick Forhan
Hi Patrick,
thanks for your offer, and I have to warn you, I might have to take you up on it. The 'enforcing a nice project structure' part actually is what has me worrying about it. I realise I have to look at it again, also seen Rick's prompt and clear reaction. What I remember is that I was forced into a directory structure and that I could not do 'class in source' directories. Is that still right? [Note to list: I am not starting a discussion about this. Merely stating what my thoughts were a few years ago.) OTOH: what we need it for is when someone downloads some NetRexx set of classes, it can resolve dependencies on class libraries. This would be mostly from authorative sources for the library, and sometimes, if the libraries are originally crafted in NetRexx, from our own repository. My points of reference here are mostly cpan, rpm and macports, who all enable me to download some library and have the dependecies resolved through downloading while building. I image we have to make .pom files available which enable the NetRexx user to do the rest with one easy command. best regards, René Jansen. On 13 okt 2010, at 15:54, Patrick Forhan wrote: > I have tons of experience with Maven, and would be happy to help in > its use. It's far from perfect, but it does two things pretty well: > dependency management, and enforcing a nice project structure. > > Pat. > > -- > Defy mediocrity. > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > _______________________________________________ Ibm-netrexx mailing list [hidden email] |
Re: netrexx code repository
|
|
Well Done, Rene, :-) Greetings to Venetia, by the way.... I'll now continue to work at my stuff for a while, and be quiet again ... Thomas. ============================================ Am 13.10.2010 19:05, schrieb René Jansen: > Hi Patrick, > > thanks for your offer, and I have to warn you, I might have to take you up on it. > The 'enforcing a nice project structure' part actually is what has me worrying about it. I realise I have to look at it again, also seen Rick's prompt and clear reaction. What I remember is that I was forced into a directory structure and that I could not do 'class in source' directories. Is that still right? [Note to list: I am not starting a discussion about this. Merely stating what my thoughts were a few years ago.) > > OTOH: what we need it for is when someone downloads some NetRexx set of classes, it can resolve dependencies on class libraries. This would be mostly from authorative sources for the library, and sometimes, if the libraries are originally crafted in NetRexx, from our own repository. My points of reference here are mostly cpan, rpm and macports, who all enable me to download some library and have the dependecies resolved through downloading while building. I image we have to make .pom files available which enable the NetRexx user to do the rest with one easy command. > > best regards, > > René Jansen. > > > On 13 okt 2010, at 15:54, Patrick Forhan wrote: > >> I have tons of experience with Maven, and would be happy to help in >> its use. It's far from perfect, but it does two things pretty well: >> dependency management, and enforcing a nice project structure. >> >> Pat. >> >> -- >> Defy mediocrity. >> _______________________________________________ >> Ibm-netrexx mailing list >> [hidden email] >> > > _______________________________________________ > Ibm-netrexx mailing list > [hidden email] > > -- Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com _______________________________________________ Ibm-netrexx mailing list [hidden email]
Tom. (ths@db-123.com)
|
|
|
In reply to this post by rvjansen
On Wed, Oct 13, 2010 at 12:05 PM, René Jansen <[hidden email]> wrote:
> thanks for your offer, and I have to warn you, I might have to take > you up on it. The 'enforcing a nice project structure' part actually > is what has me worrying about it. I realise I have to look at it > again, also seen Rick's prompt and clear reaction. What I > remember is that I was forced into a directory structure and that > I could not do 'class in source' directories. Is that still right? [Note > to list: I am not starting a discussion about this. Merely stating > what my thoughts were a few years ago.) Right, you can reconfigure source and output directories, but here is the default layout for a java/jar project: source/input directories: src/main/java src/main/resources src/test/java src/test/resources output directories: target target/classes target/test-classes A general flow for maven in such a project would be to: 1. compile src/main/java to target/classes 2. copy src/main/resources to target/classes 3. compile src/test/java to target/test-classes 4. run unit tests, output to target/surefire-reports 5. build jar, source jar, and test jars, place in target Again, you can change much of this, but with Maven, the more you fight with it, the more you will have to fight with it. It kind of snowballs and will cause annoyances down the line. > ...This would be mostly from authorative sources for the library, > and sometimes, if the libraries are originally crafted in NetRexx, > from our own repository. It is not terrible to set up a repository, but the holy grail (for the users, anyway) is to get your libraries uploaded to Maven Central, http://repo1.maven.org/maven2/ -- this will make the process quite seamless for adding NetRexx to a project. Another important task, though, is compilation. This will generally require a special maven plugin that can essentially execute netrexxc and conform to something similar to the input and output directories above. This is not too tricky, especially if there is a java entry point to do the work. Related to this is a topic of modularity: how do you break up a project? This was discussed a bit earlier in this thread. For example, you will generally get yourself into trouble if you have: src/main/java src/main/netrexx src/main/javafx all in the same module, and are trying to compile them all at once. Unless you have a single compiler that can process all your source at once, this won't work. You will be far happier to make multiple modules, use maven to describe the dependencies, and do one language at a time. Pat. -- Defy mediocrity. _______________________________________________ Ibm-netrexx mailing list [hidden email] |
|
|
If anyone cares, I lightly formatted, corrected, and expanded upon
this email at http://blog.muddyhorse.com/2010/10/quick-maven-primer-for-java-development/ Pat. -- Defy mediocrity. _______________________________________________ Ibm-netrexx mailing list [hidden email] |
Re: netrexx code repository
|
|
In reply to this post by Patrick Forhan
Patrick, thanks for the insight....
I will have to: 1.) read more about maven 2.) re-arrange my own directories (again, third time) to follow your 'default' directory scheme. I will wait for this until Rene did decide whether he wants to use ANT or MAVEN .... Thomas. =========================================================== Am 13.10.2010 20:05, schrieb Patrick Forhan: > On Wed, Oct 13, 2010 at 12:05 PM, René Jansen<[hidden email]> wrote: >> thanks for your offer, and I have to warn you, I might have to take >> you up on it. The 'enforcing a nice project structure' part actually >> is what has me worrying about it. I realise I have to look at it >> again, also seen Rick's prompt and clear reaction. What I >> remember is that I was forced into a directory structure and that >> I could not do 'class in source' directories. Is that still right? [Note >> to list: I am not starting a discussion about this. Merely stating >> what my thoughts were a few years ago.) > Right, you can reconfigure source and output directories, but here is > the default layout for a java/jar project: > > source/input directories: > src/main/java > src/main/resources > src/test/java > src/test/resources > > output directories: > target > target/classes > target/test-classes > > A general flow for maven in such a project would be to: > 1. compile src/main/java to target/classes > 2. copy src/main/resources to target/classes > 3. compile src/test/java to target/test-classes > 4. run unit tests, output to target/surefire-reports > 5. build jar, source jar, and test jars, place in target > > Again, you can change much of this, but with Maven, the more you fight > with it, the more you will have to fight with it. It kind of > snowballs and will cause annoyances down the line. > >> ...This would be mostly from authorative sources for the library, >> and sometimes, if the libraries are originally crafted in NetRexx, >> from our own repository. > It is not terrible to set up a repository, but the holy grail (for the > users, anyway) is to get your libraries uploaded to Maven Central, > http://repo1.maven.org/maven2/ -- this will make the process quite > seamless for adding NetRexx to a project. > > Another important task, though, is compilation. This will generally > require a special maven plugin that can essentially execute netrexxc > and conform to something similar to the input and output directories > above. This is not too tricky, especially if there is a java entry > point to do the work. > > Related to this is a topic of modularity: how do you break up a > project? This was discussed a bit earlier in this thread. For > example, you will generally get yourself into trouble if you have: > src/main/java > src/main/netrexx > src/main/javafx > > all in the same module, and are trying to compile them all at once. > Unless you have a single compiler that can process all your source at > once, this won't work. You will be far happier to make multiple > modules, use maven to describe the dependencies, and do one language > at a time. > > Pat. -- Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com _______________________________________________ Ibm-netrexx mailing list [hidden email]
Tom. (ths@db-123.com)
|
«
Return to ibm-netrexx
|
1 view|%1 views
| Free forum by Nabble | Edit this page |