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 <luckbr1...@gmail.com> > wrote: > > On Sun, May 8, 2011 at 8:04 PM, Nirmal Fernando <nirmal070...@gmail.com> > wrote: > >> Hi, > >> > >> On Mon, May 9, 2011 at 6:44 AM, Luciano Resende <luckbr1...@gmail.com> > >> 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/
