To contribute/write to the public Kepler SVN repository, you need to apply for an SVN account: https://kepler-project.org/developers/get-involved#request-a-named-svn
Derik On Mar 7, 2012, at 1:55 PM, Bina Philip wrote: > Thanks for all the information Derik and yes your other email was also very > informative and gives me a detailed picture of how exactly the actor I code > can be used by other coders. > > From the instructions in one of the links you mentioned, I have one question. > Let me quote the instruction here > "After you have created a module either manually or using the commands ant > make-suite or ant make-module you will probably want to add them to a version > control system. Currently, the build system only supports > > If you would like to store your module in our version control system at > https://code.kepler-project.org/code/kepler/ and you have write permission, > there is an ant command to add your module automatically. All you have to do > is type the command: > > ant upload -Dmodule=module.name > You will be prompted for your SVN username and password and the module should > upload." > > Now for this set of instructions, I can see I need write permissions to store > my module in the version path mentioned above. How can I obtain these > permissions? Also what does the SVN username and password refer to? I used > the subversion to check out the code from the trunk from the command line but > it did not give me an option to configure any such username and password. > > Kindly let me know. > > Best > > > On Wed, Mar 7, 2012 at 3:41 PM, Derik Barseghian <[email protected]> > wrote: > Hi Bina, > Hopefully I've addressed some of these questions in my last response: > http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2012-March/002183.html > > Other responses inline: > > On Mar 6, 2012, at 9:45 AM, Bina Philip wrote: > > > Hello, > > > > I wanted to know how the over-all process of creating a custom actor would > > work. If I were to make a custom actor in kepler then according to the > > documentation I would have to check out the code in the trunk for kepler > > and then after creating a module for my actor I would have to start coding > > for my actor (like mentioned in the HelloWorld example). If I have some > > additional external jars I need for this actor of mine I just import those > > external jars into my module's build path and start coding for my actor. > > Please correct my understanding if I am incorrect until this point. > > > > That's right. Though it's recommended that 3rd party module developers work > off the last release branch (2.3 currently) rather than trunk. > > > Now after this I had a question from the Users perspective, if there is > > another member in my team who download Kepler to use it (without any source > > code check out etc) and wants to use the actor I just created for Kepler. > > How can he/she use this actor and gain access to this? > > Users that download the released version of kepler (e.g. install from a 2.3.0 > installer) will only be able to get your actor module once you publish it. > They will get download it using the Module Manager from within Kepler. > > > > > I also wanted to know the contents of the kar file does this contain any > > modules within it that have the jars related to that kar? When somebody > > tries to open a kar file in kepler what goes on in the background while the > > workflow runs? How are the jars related to this kar identified from within > > the workflow system? I am trying to see if I can make a custom actor and > > supply my team member with a kar file for the actor, can he/she import this > > kar file in kepler and run this actor (without getting any source code > > checked out and adding any additional jars?) > > > > When you publish your module it's placed in the repository as a zip file, not > a kar file. > E.g.: > https://code.kepler-project.org/code/kepler/releases/released/dataturbine-2.2.0/ > The zip file contains everything your module needs, e.g. the actor code, the > jars it needs, etc. > > In the past we discussed distributing modules as kars, but this didn't get > implemented. Currently a kar typically only contains an actor, a workflow, a > workflow + report design, or a workflow + report design + report instance + > workflow run metadata file. > > > Kindly let me know. > > > > Best > > > > -- > > Regards, > > Bina > > Indiana University Bloomington > > Dept Of Computer Science (Master's). > > Contact:- 812-327-4780 > > > > _______________________________________________ > > Kepler-users mailing list > > [email protected] > > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users > > > > > -- > Regards, > Bina > Indiana University Bloomington > Dept Of Computer Science (Master's). > Contact:- 812-327-4780 > _______________________________________________ Kepler-users mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
