Re: [Jcrbrowser-developers] JCR Browser as an RCP application
Brought to you by:
sandro_boehme
From: Ketan P. <ket...@gm...> - 2007-05-16 13:14:28
|
Sandro B=F6hme wrote: > Hello Ketan, >=20 > thank you very much for the contribution of the RCP capabilities! It > will add a big benefit to the JCR Browser project. I remember at least > one guy who activly asked for this feature. In order to commit and > release it I would first like to discuss some things: We're actively using JCRBrowser in our project, and having an eclipse instance running to use a couple of views on a JCR was too expensive. So the RCP application. > o Are really all plug-ins listed in the JCRBrowser.product file needed?= I will have to look into the package that I'd sent attached on the bugzilla. Most plugins are part of the RCP, and provide for basic infrastructure for the application. Are there any other specific plugins that you are talking about, which you think should not be needed ? The multiple versions of swt are relevant when I'm exporting the product for multiple OSs. I'm right now able to create windows, mac, linux and vista versions of JCRBrowser from one product file after installing the RCP delta pack. See http://wbeaton.blogspot.com/2006/04/targetting-different-version-of-rcp.h= tml and http://wiki.eclipse.org/index.php/RCP_FAQ#What_is_the_recommended_target_= platform_setup.3F__Or:_How_can_I_build_and_run_my_RCP_app_against_a_diffe= rent_version_of_the_Eclipse_base.3F > o Can I simply rename the *.java0000644 files to usual Java files or is= > there a special reason why they use this naming pattern? Oops, I think that there's some issue with the tarball that was attached to the bug entry. I'm unable to do a clean untar of the attachment. I'll attach another entry to the same bug. > o I have no problem with keeping the package name to > "com.thoughtworks.jcrbrowser.rcp". I would just prefer to use > "org.visualcontent.rcp" if I maintain this module in long term. Please > tell me in case you have any interest in maintaining this module and > what you think about the package name. > o To ensure the users know what license is used please add the Apache2 > license headers (or a compatible license) to the source files and the > license file to the plug-in root folder. I think it would look like > hijacking of this plug-in if I would do that ;-). Thanks. I'll want to talk to ThoughtWorks on renaming the package names. I do not think this should be a problem, since ThoughtWorks has a lot of open-source projects. As far as licensing is concerned, I'll add the relevant Apache 2 Headers to the source code, in my next attachment to the tarball. > o And finally can I do something for you? Like adding a link to your > blog or networking tool to the release info containing that feature? It= > will be published at the Sourceforge project page and in the Jackrabbit= > mailing list. You can add a link to my blog: http://ketan.padegaonkar.name/ > Thanks again, Thanks to you too :) > Sandro --=20 Ketan Padegaonkar I blog... therefore I am... http://ketan.padegaonkar.name/ If bankers can count, how come they have eight windows and only four tellers? |