Re: GSOC working space
On Thu, May 12, 2011 at 12:44 PM, ant elder wrote: > On Thu, May 12, 2011 at 4:43 AM, Nirmal Fernando > wrote: > > > > > Just wanna get clarified whether what I am doing now is what you have > > expected. > > > > Now, I am creating a whole new Maven project which has no connection to > > Tuscany trunk. > > If you find it easy enough to create a whole new project then that is > fine for the prototype experiments that you're doing presently, for > any code that you want to eventually include in the Tuscany build then > that would need to use the Tuscany parent pom's when it gets added to > the build so it might be easiest starting off using that. Even for > code that you have no intention of adding to the Tuscany build it > might be easiest to start with a Tuscany pom.xml as then you can > inherit all the plugin config for things like the compiler, testing, > etc which will help make things simple. Its easy to start with a > tuscany one, just copy one of the Tuscany pom.xml's to your project, > eg the pom.xml at [1], and in that delete the old 's and > the 's elements, and change the and for > your project name. > > (I've pointed you at one of the Tuscany sample pom.xml's because if > you use a module one then it has requirements on including things like > manifests and legal files that you really don't need to worry about > yet) > > ...ant > > [1] > https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/pom.xml > Thanks Ant, it's really helpful! -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: GSOC working space
On Thu, May 12, 2011 at 4:43 AM, Nirmal Fernando wrote: > > Just wanna get clarified whether what I am doing now is what you have > expected. > > Now, I am creating a whole new Maven project which has no connection to > Tuscany trunk. If you find it easy enough to create a whole new project then that is fine for the prototype experiments that you're doing presently, for any code that you want to eventually include in the Tuscany build then that would need to use the Tuscany parent pom's when it gets added to the build so it might be easiest starting off using that. Even for code that you have no intention of adding to the Tuscany build it might be easiest to start with a Tuscany pom.xml as then you can inherit all the plugin config for things like the compiler, testing, etc which will help make things simple. Its easy to start with a tuscany one, just copy one of the Tuscany pom.xml's to your project, eg the pom.xml at [1], and in that delete the old 's and the 's elements, and change the and for your project name. (I've pointed you at one of the Tuscany sample pom.xml's because if you use a module one then it has requirements on including things like manifests and legal files that you really don't need to worry about yet) ...ant [1] https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/getting-started/helloworld/pom.xml
Fwd: GSOC working space
Hi, On Wed, May 11, 2011 at 10:22 AM, Jean-Sebastien Delfino < jsdelf...@apache.org> wrote: > On Sun, May 8, 2011 at 9:25 PM, Luciano Resende > wrote: > > On Sun, May 8, 2011 at 8:04 PM, Nirmal Fernando > wrote: > >> Hi, > >> > >> On Mon, May 9, 2011 at 6:44 AM, Luciano Resende > >> wrote: > >>> > >>> On Sat, May 7, 2011 at 7:50 AM, Nirmal Fernando < > nirmal070...@gmail.com> > >>> wrote: > >>> > Hi, > >>> > > >>> > I would like to send my initial patch which is a composite diagram > >>> > generator > >>> > prototype using Apache Batik. > >>> > How should I share the project? It's around 3MB including Apache > Batik > >>> > binaries. > >>> > > >>> > Thanks. > >>> > > >>> > >>> Are you using maven to create the project ? the batik dependencies can > >>> be defined as dependencies and thus you won't need to provide the > >>> binaries itself. > >> > >> Not really, it's just a Java project created by Eclipse! > >>> > >>> > > > > Then, it's ok if you just attach it as a zip, but you should start > > migrating it to a maven project. To make things easier, you could try > > merging your new code inside modules/node-manager ... I could try > > helping with that... > > > > > > Looks like good progress already :) > > You can attach it to a JIRA, but we usually don't put dependency JARs in > SVN. > > Also, it'll be easier for others to try your code if you do the following: > - create a Maven module with a pom.xml file declaring your dependencies; > - check that this module builds OK with Maven after you've built the > Tuscany trunk; > - use mvn eclipse:eclipse to generate an Eclipse project from the > declarations in your pom.xml. > > These steps are a little more work than just creating and exporting a > project from Eclipse, but they help: > - share your work with more people in the community, e.g. people not > using Eclipse, like me for example; > - make it easier for others to get in your code, as it'll be in a > predictable Maven folder structure; > - provide a reproducible, command line based, way to build, execute > and test your code; > - eventually integrate your code and tests in the project's automated > builds. > > As a starting point you could copy the structure of an existing > Tuscany Maven module (just the pom.xml and the folder structure), like > node-manager for example. Once that works, add a test case or two > under src/test/java, as it'll help others play with it and understand > how to invoke it. > Just wanna get clarified whether what I am doing now is what you have expected. Now, I am creating a whole new Maven project which has no connection to Tuscany trunk. > > Hope this helps. > -- > Jean-Sebastien > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/ -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: GSOC working space
On Wed, May 11, 2011 at 10:22 AM, Jean-Sebastien Delfino < jsdelf...@apache.org> wrote: > On Sun, May 8, 2011 at 9:25 PM, Luciano Resende > wrote: > > On Sun, May 8, 2011 at 8:04 PM, Nirmal Fernando > wrote: > >> Hi, > >> > >> On Mon, May 9, 2011 at 6:44 AM, Luciano Resende > >> wrote: > >>> > >>> On Sat, May 7, 2011 at 7:50 AM, Nirmal Fernando < > nirmal070...@gmail.com> > >>> wrote: > >>> > Hi, > >>> > > >>> > I would like to send my initial patch which is a composite diagram > >>> > generator > >>> > prototype using Apache Batik. > >>> > How should I share the project? It's around 3MB including Apache > Batik > >>> > binaries. > >>> > > >>> > Thanks. > >>> > > >>> > >>> Are you using maven to create the project ? the batik dependencies can > >>> be defined as dependencies and thus you won't need to provide the > >>> binaries itself. > >> > >> Not really, it's just a Java project created by Eclipse! > >>> > >>> > > > > Then, it's ok if you just attach it as a zip, but you should start > > migrating it to a maven project. To make things easier, you could try > > merging your new code inside modules/node-manager ... I could try > > helping with that... > > > > > > Looks like good progress already :) > > You can attach it to a JIRA, but we usually don't put dependency JARs in > SVN. > > Also, it'll be easier for others to try your code if you do the following: > - create a Maven module with a pom.xml file declaring your dependencies; > - check that this module builds OK with Maven after you've built the > Tuscany trunk; > - use mvn eclipse:eclipse to generate an Eclipse project from the > declarations in your pom.xml. > > These steps are a little more work than just creating and exporting a > project from Eclipse, but they help: > - share your work with more people in the community, e.g. people not > using Eclipse, like me for example; > - make it easier for others to get in your code, as it'll be in a > predictable Maven folder structure; > - provide a reproducible, command line based, way to build, execute > and test your code; > - eventually integrate your code and tests in the project's automated > builds. > > As a starting point you could copy the structure of an existing > Tuscany Maven module (just the pom.xml and the folder structure), like > node-manager for example. Once that works, add a test case or two > under src/test/java, as it'll help others play with it and understand > how to invoke it. > > Hope this helps. > Thanks Jean for the detailed information, I will create a Maven project. > -- > Jean-Sebastien > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: GSOC working space
On Sun, May 8, 2011 at 9:25 PM, Luciano Resende wrote: > On Sun, May 8, 2011 at 8:04 PM, Nirmal Fernando > wrote: >> Hi, >> >> On Mon, May 9, 2011 at 6:44 AM, Luciano Resende >> wrote: >>> >>> On Sat, May 7, 2011 at 7:50 AM, Nirmal Fernando >>> wrote: >>> > Hi, >>> > >>> > I would like to send my initial patch which is a composite diagram >>> > generator >>> > prototype using Apache Batik. >>> > How should I share the project? It's around 3MB including Apache Batik >>> > binaries. >>> > >>> > Thanks. >>> > >>> >>> Are you using maven to create the project ? the batik dependencies can >>> be defined as dependencies and thus you won't need to provide the >>> binaries itself. >> >> Not really, it's just a Java project created by Eclipse! >>> >>> > > Then, it's ok if you just attach it as a zip, but you should start > migrating it to a maven project. To make things easier, you could try > merging your new code inside modules/node-manager ... I could try > helping with that... > > Looks like good progress already :) You can attach it to a JIRA, but we usually don't put dependency JARs in SVN. Also, it'll be easier for others to try your code if you do the following: - create a Maven module with a pom.xml file declaring your dependencies; - check that this module builds OK with Maven after you've built the Tuscany trunk; - use mvn eclipse:eclipse to generate an Eclipse project from the declarations in your pom.xml. These steps are a little more work than just creating and exporting a project from Eclipse, but they help: - share your work with more people in the community, e.g. people not using Eclipse, like me for example; - make it easier for others to get in your code, as it'll be in a predictable Maven folder structure; - provide a reproducible, command line based, way to build, execute and test your code; - eventually integrate your code and tests in the project's automated builds. As a starting point you could copy the structure of an existing Tuscany Maven module (just the pom.xml and the folder structure), like node-manager for example. Once that works, add a test case or two under src/test/java, as it'll help others play with it and understand how to invoke it. Hope this helps. -- Jean-Sebastien
Re: GSOC working space
On Sun, May 8, 2011 at 8:04 PM, Nirmal Fernando wrote: > Hi, > > On Mon, May 9, 2011 at 6:44 AM, Luciano Resende > wrote: >> >> On Sat, May 7, 2011 at 7:50 AM, Nirmal Fernando >> wrote: >> > Hi, >> > >> > I would like to send my initial patch which is a composite diagram >> > generator >> > prototype using Apache Batik. >> > How should I share the project? It's around 3MB including Apache Batik >> > binaries. >> > >> > Thanks. >> > >> >> Are you using maven to create the project ? the batik dependencies can >> be defined as dependencies and thus you won't need to provide the >> binaries itself. > > Not really, it's just a Java project created by Eclipse! >> >> Then, it's ok if you just attach it as a zip, but you should start migrating it to a maven project. To make things easier, you could try merging your new code inside modules/node-manager ... I could try helping with that... -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: GSOC working space
Hi, On Mon, May 9, 2011 at 6:44 AM, Luciano Resende wrote: > On Sat, May 7, 2011 at 7:50 AM, Nirmal Fernando > wrote: > > Hi, > > > > I would like to send my initial patch which is a composite diagram > generator > > prototype using Apache Batik. > > How should I share the project? It's around 3MB including Apache Batik > > binaries. > > > > Thanks. > > > > Are you using maven to create the project ? the batik dependencies can > be defined as dependencies and thus you won't need to provide the > binaries itself. > Not really, it's just a Java project created by Eclipse! > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: GSOC working space
On Sat, May 7, 2011 at 7:50 AM, Nirmal Fernando wrote: > Hi, > > I would like to send my initial patch which is a composite diagram generator > prototype using Apache Batik. > How should I share the project? It's around 3MB including Apache Batik > binaries. > > Thanks. > Are you using maven to create the project ? the batik dependencies can be defined as dependencies and thus you won't need to provide the binaries itself. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: GSOC working space
For now its probably easiest to just zip up the files and attach that to a JIRA, you could use the existing JIRA for your project TUSCANY-3496. ...ant On Sat, May 7, 2011 at 3:50 PM, Nirmal Fernando wrote: > Hi, > > I would like to send my initial patch which is a composite diagram generator > prototype using Apache Batik. > How should I share the project? It's around 3MB including Apache Batik > binaries. > > Thanks. > > On Sat, May 7, 2011 at 1:49 PM, Nirmal Fernando > wrote: >> >> Hi All, >> >> On Sat, May 7, 2011 at 12:46 PM, ant elder wrote: >>> >>> On Tue, May 3, 2011 at 8:29 AM, ant elder wrote: >>> > On Sat, Apr 30, 2011 at 2:56 PM, Florian Moga >>> > wrote: >>> >> Hi, >>> >> We currently have a couple of places where we keep work in progress >>> >> code. It >>> >> would be nice to agree on a location for GSOC projects so we can >>> >> suggest it >>> >> to the students so they will know how to create their patches. >>> >> Options include: >>> >> 1) sca-java-2.x/contrib/ >>> >> 2) sca-java-2.x/trunk/unreleased >>> >> I'd go with contrib/ as it currently has a trunk-like structure with >>> >> modules, samples, etc and contains more experimental code. >>> >> Thanks, >>> >> Florian >>> > >>> > It could be left up to each student to decide. Most of us usually put >>> > things directly in trunk/modules so the students could also do that, >>> > and include it in the build when they feel confident, if they want to >>> > experiment a bit before going to trunk then contrib would be fine, or >>> > create a folder in the sandbox for the project would work too. >>> > >>> >>> and one more option is the SVN collaboration area which is the sandbox >>> to make it easier to work with people who don't yet have Tuscany >>> commit privileges - >>> https://svn.apache.org/repos/asf/tuscany/collaboration/ >> >> I would like to use sandbox for my development work! >> >>> >>> ...ant >> >> >> >> -- >> Best Regards, >> Nirmal >> >> C.S.Nirmal J. Fernando >> Department of Computer Science & Engineering, >> Faculty of Engineering, >> University of Moratuwa, >> Sri Lanka. >> Blog: http://nirmalfdo.blogspot.com/ > > > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. > Blog: http://nirmalfdo.blogspot.com/ >
Re: GSOC working space
Hi, I would like to send my initial patch which is a composite diagram generator prototype using Apache Batik. How should I share the project? It's around 3MB including Apache Batik binaries. Thanks. On Sat, May 7, 2011 at 1:49 PM, Nirmal Fernando wrote: > Hi All, > > On Sat, May 7, 2011 at 12:46 PM, ant elder wrote: > >> On Tue, May 3, 2011 at 8:29 AM, ant elder wrote: >> > On Sat, Apr 30, 2011 at 2:56 PM, Florian Moga >> wrote: >> >> Hi, >> >> We currently have a couple of places where we keep work in progress >> code. It >> >> would be nice to agree on a location for GSOC projects so we can >> suggest it >> >> to the students so they will know how to create their patches. >> >> Options include: >> >> 1) sca-java-2.x/contrib/ >> >> 2) sca-java-2.x/trunk/unreleased >> >> I'd go with contrib/ as it currently has a trunk-like structure with >> >> modules, samples, etc and contains more experimental code. >> >> Thanks, >> >> Florian >> > >> > It could be left up to each student to decide. Most of us usually put >> > things directly in trunk/modules so the students could also do that, >> > and include it in the build when they feel confident, if they want to >> > experiment a bit before going to trunk then contrib would be fine, or >> > create a folder in the sandbox for the project would work too. >> > >> >> and one more option is the SVN collaboration area which is the sandbox >> to make it easier to work with people who don't yet have Tuscany >> commit privileges - >> https://svn.apache.org/repos/asf/tuscany/collaboration/ >> > > I would like to use sandbox for my development work! > > >> >> ...ant >> > > > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. > > Blog: http://nirmalfdo.blogspot.com/ > > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: GSOC working space
Hi All, On Sat, May 7, 2011 at 12:46 PM, ant elder wrote: > On Tue, May 3, 2011 at 8:29 AM, ant elder wrote: > > On Sat, Apr 30, 2011 at 2:56 PM, Florian Moga > wrote: > >> Hi, > >> We currently have a couple of places where we keep work in progress > code. It > >> would be nice to agree on a location for GSOC projects so we can suggest > it > >> to the students so they will know how to create their patches. > >> Options include: > >> 1) sca-java-2.x/contrib/ > >> 2) sca-java-2.x/trunk/unreleased > >> I'd go with contrib/ as it currently has a trunk-like structure with > >> modules, samples, etc and contains more experimental code. > >> Thanks, > >> Florian > > > > It could be left up to each student to decide. Most of us usually put > > things directly in trunk/modules so the students could also do that, > > and include it in the build when they feel confident, if they want to > > experiment a bit before going to trunk then contrib would be fine, or > > create a folder in the sandbox for the project would work too. > > > > and one more option is the SVN collaboration area which is the sandbox > to make it easier to work with people who don't yet have Tuscany > commit privileges - > https://svn.apache.org/repos/asf/tuscany/collaboration/ > I would like to use sandbox for my development work! > > ...ant > -- Best Regards, Nirmal C.S.Nirmal J. Fernando Department of Computer Science & Engineering, Faculty of Engineering, University of Moratuwa, Sri Lanka. Blog: http://nirmalfdo.blogspot.com/
Re: GSOC working space
On Tue, May 3, 2011 at 8:29 AM, ant elder wrote: > On Sat, Apr 30, 2011 at 2:56 PM, Florian Moga wrote: >> Hi, >> We currently have a couple of places where we keep work in progress code. It >> would be nice to agree on a location for GSOC projects so we can suggest it >> to the students so they will know how to create their patches. >> Options include: >> 1) sca-java-2.x/contrib/ >> 2) sca-java-2.x/trunk/unreleased >> I'd go with contrib/ as it currently has a trunk-like structure with >> modules, samples, etc and contains more experimental code. >> Thanks, >> Florian > > It could be left up to each student to decide. Most of us usually put > things directly in trunk/modules so the students could also do that, > and include it in the build when they feel confident, if they want to > experiment a bit before going to trunk then contrib would be fine, or > create a folder in the sandbox for the project would work too. > and one more option is the SVN collaboration area which is the sandbox to make it easier to work with people who don't yet have Tuscany commit privileges - https://svn.apache.org/repos/asf/tuscany/collaboration/ ...ant
Re: GSOC working space
On Sat, Apr 30, 2011 at 2:56 PM, Florian Moga wrote: > Hi, > We currently have a couple of places where we keep work in progress code. It > would be nice to agree on a location for GSOC projects so we can suggest it > to the students so they will know how to create their patches. > Options include: > 1) sca-java-2.x/contrib/ > 2) sca-java-2.x/trunk/unreleased > I'd go with contrib/ as it currently has a trunk-like structure with > modules, samples, etc and contains more experimental code. > Thanks, > Florian It could be left up to each student to decide. Most of us usually put things directly in trunk/modules so the students could also do that, and include it in the build when they feel confident, if they want to experiment a bit before going to trunk then contrib would be fine, or create a folder in the sandbox for the project would work too. ...ant
Re: GSOC working space
On Sat, Apr 30, 2011 at 6:56 AM, Florian Moga wrote: > Hi, > We currently have a couple of places where we keep work in progress code. It > would be nice to agree on a location for GSOC projects so we can suggest it > to the students so they will know how to create their patches. > Options include: > 1) sca-java-2.x/contrib/ > 2) sca-java-2.x/trunk/unreleased > I'd go with contrib/ as it currently has a trunk-like structure with > modules, samples, etc and contains more experimental code. > Thanks, > Florian As long as it's part of the build, I'm fine with it, which means it needs to be inside trunk somewhere. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
GSOC working space
Hi, We currently have a couple of places where we keep work in progress code. It would be nice to agree on a location for GSOC projects so we can suggest it to the students so they will know how to create their patches. Options include: 1) sca-java-2.x/contrib/ 2) sca-java-2.x/trunk/unreleased I'd go with contrib/ as it currently has a trunk-like structure with modules, samples, etc and contains more experimental code. Thanks, Florian
