I would like to upgrade my Eclipse RCP project which was live yesterday, developed using Eclipse RCP 3.6 version(code was like tightly coupled as I didn't use Spring DI), as a future road-map consideration, I'd like to upgrade my project to Eclipse 4. Primary reason for upgrading is to use spring DI & CSS in my RCP application. Can I do spring integration and CSS in my Eclipse RCP 3.6 project or Should I start from creating an RCP 4 Scratch project.
Brainstorming for ideas, actually. Any directions & suggestions would be great.
To answer your first question... it is certainly possible to use Spring DI in Eclipse 3.6, but the current CSS styling for Eclipse RCP UI wasn't introduced until Eclipse 4.
I can't address if you should or should not create an RCP 4 Scratch project. That's a tough decision and it should be made by someone with deep knowledge of your project and its future goals.
As for direction and suggestions...
I have two sources of information for you.
Lars Vogella. His tutorial sites are very well put together, and I consider them a must have for anyone wanting to learn the basics of Eclipse RCP development. Unfortunately, these tutorials may not be detailed enough to help you. It depends on your current level of Eclipse RCP knowledge. http://www.vogella.com/tutorials.html
Eclipse Source. This is a paid service. I've never worked with these guys, but they have been sending me some emails offering several different pricing levels for various levels of support. There web site is well put together and it offers some great information. http://eclipsesource.com/en/eclipse/
Related
I am new eclipse scout. However I do have some experience in EclipseRCP.
I have created an application in eclipse rcp, in which it has four modules which are four plugin projects.
Also I am using hibernate in backend for database communication.Database is Mysql.
Below are my questions.
In eclipse can I create the same modules as my eclipse rcp application. I have seen
only one eclipse project created in different examples. So in mycase, I have four plugin projects. Do I need
to make all these four plugin projects into one scount application?
Can I reuse the hibernate code which I have written in Scout application?
1/ With the Mars version (and before) of Eclipse Scout, an Eclipse Scout Application is very similar to an Eclipse RCP Application. It runs on top of Equinox. You will be able to manage your plugins project the same way. When you create a new project, the IDE prepares some plugins, but you can have more...
2/ Nothing against reusing your Hibernate code in your Scout Application. But you might know that integrating Hibernate in the OSGi world is not so easy and requires some work.
I am developing an standalone GUI for our in-house tool. After it has matured enough, it is supposed to be integrated into Eclipse as a plugin.
I am a newcomer to Java world. I have read about RCP. Is this is correct use case scenario for RCP? If yes, can I use SWT views in a RCP application/plugin?
Is this is correct use case scenario for RCP?
Yes, RCP is a good fit. You can use the same plugin for providing functionality both in Eclipse and in your standalone application.
If yes, can I use SWT views in a RCP application/plugin?
Yes, of course. Until the latest version of RCP (e4) you could only use SWT for GUI (of course, Swing/JavaFX/etc. can be integrated with SWT).
When you develop an Eclipse RCP based application, you in fact develop a number of plug-ins. If you play by a specific set of limited rules, then your plug-in can run unaltered as part of an RCP application and as part of the larger Eclipse IDE.
(One can easily argue that the IDE is "just" a very large RCP application. The IDE is based on the Eclipse Platform of which Eclipse RCP is just a small sub-set...)
I would recommend two books for your project:
"Eclipse Rich Client Platform (2nd Edition)" by Jeff McAffer, Jean-Michel Lemieux, and Chris Aniszczyk - see Amazon.
"Eclipse Plug-ins (3rd Edition)" by Eric Clayberg and Dan Rubel - see Amazon.
Where the first is more or less the bible for RCP based applications, the later gives you a lot of good examples on how to integrate into the IDE. Very advanced as times, but also very good.
I am using Maven to automate a project that is being developed in RAD 7.5.
I've installed m2eclipse in RAD 7.5 , updated ( manually ) maven dependencies , and it builds Maven way within RAD.
My main question : what is the best practice using m2eclipse with RAD?
Should we keep both ( RAD and maven ) settings in the project workspace or remove all RAD settings and stick with Maven only?
Also , I am wondering about m2eclipse dependency management feature. I was hoping that it will update pom.xml with the new dependency when I add it to the classpath and vise versa ( in case we are keeping both configurations ). Is this a correct assumption?
this doesn't seem to happen. Maybe I need to give it another try....
Any suggestions are very much appreciated!
The article "Java EE development using Rational Application Developer 7.5.5 and Maven" (http://www.ibm.com/developerworks/wikis/display/rad/Articles) is OK but the site is wrong.
Since RAD 7.5.5 is based on Eclipse 3.4.2 you need to point here:
http://m2eclipse.sonatype.org/sites/m2e-e34/
My main question : what is the best practice using m2eclipse with RAD? Should we keep both (RAD and maven) settings in the project workspace or remove all RAD settings and stick with Maven only?
I don't work with RAD so I'm not sure my answer will be totally accurate but when working with Eclipse, m2eclipse takes care of the .classpath and the .project files and everything is derived from the pom.xml, not the other way around. I don't think it's different with RAD.
[...] I was hoping that it will update pom.xml with the new dependency when I add it to the classpath and vise versa (in case we are keeping both configurations). Is this a correct assumption?
I don't think so, m2eclipse won't translate a random dependency (that may not be available in any repo) into a maven artifact and add the coordinates to the pom.xml. Edit the pom.xml or use the wizard to add a dependency. As I said above, it works the other way around, things are derived from a pom.xml.
As there seem to be many open issues with m2eclipse (at least 0.10+) and RAD 7.5, I'm thinking of going the manual way in RAD with the eclipse:rad goal:
http://maven.apache.org/plugins/maven-eclipse-plugin/rad-mojo.html
Please to go to http://www.ibm.com/developerworks/wikis/display/rad/Articles
See section Java EE, article "Java EE development using Rational Application Developer 7.5.5 and Maven".
This is a best-practices paper published by Rational Application Developer development team.
Be aware that the comment from Pascal might have performance implications during publishing to WebSphere Application Server or WebSphere Portal Server.
The developerWorks forum for Rational Application Developer contains also quite a number of posts.
The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
I am completelty new to the BB development.
I want to start development of BlackBerry application.
I am confused how to start? And what plugins have to download and from which link?
And bit confused about the JDE plugin <--> Java plugin for Eclipse
Which I have to download for development?
Can any one explaine the above things?
thanks in advance...
JDE and eclipse plugin are same other than, JDE has only debug mode, but the eclipse has both debug and run mode. I am using eclipse for several years, so I feel comfortable in using eclipse. I recommend eclipse because, it is more developer friendly when compared to JDE.
I agree with Karthikeyan that eclipse has a more feature rich environment plus it can incorporate other plugins such as cvs, svn, mysql etc.
Sometimes it can take more configuration to get everything set up right properly. If you want to get your code up and running quickly without any configuration, I would highly recommend using the JDE.
Glen
My company starts a new project next week. We have planned to develop the application with eclipse rcp. The build process should be fully automated, so we're prepared to set up a continuous integration environment (e.g. Continuum). For the build-automation-part I intended to use maven2, because I want use its dependency management.
I have used maven2 for a small old-style java project, but have never set up maven for using it with eclipse rcp.
What's the best way to do this? Basic concepts? Common traps? Are any tutorials or book's around there? The tutorials and informations I found, seemed outdated or incomplete.
PS: The main project will be divided into sub-project's (plug-in's). But I think this is typical for eclipse rcp projects.
You should take a look at Tycho:
the-future-of-maven-osgi-join-the-tycho-users-mailing-list
the-next-generation-of-build-tools-for-eclipse-plugins-and-rcp-applications
Like most Maven questions, this is solved by a link to a plug-in:
"pde-maven-plugin"
Other advice:
use the assembly plug-in to build
the update site
consider using hudson rather than
Continuum
I've been battling maven2/Eclipse RCP integration for some time. The key is not so much getting your setup right: You can get it to work - eventually - by reverse-engineering Eclipse's build process in maven.
In my experience, the hard part is keeping everything up to date. Every time Eclipse revs their libs, you'll find yourself re-writing a bunch of pom files for that newest RCP widget or SWT lib. Naturally, CI helps with this somewhat. The problem is that Eclipse and maven are very particular about the way they do the business of building, and their approaches are quite different. To make matters worse, PDE dev (and Eclipse dev, more generally) is powered by a lot of wizard code, which is sometimes quite opaque as to what's happening behind the scenes.
The question you really need to ask yourself is if it's worth the effort. In my particular case, I believe it has been. (CI is too good to live without.) But the trade-off is that you may find yourself being the "build guy", which can take valuable time away from actual development, which is probably what you enjoy most.
I've got recently the same problem : build eclipse RCP application through continuous integration.
I haven't applied them yet but I've found some interesting articles :
Here's the documentation for Tycho
Building Eclipse Plugins with Maven 2 on eclipse.org
Build Eclipse RCP products using Maven 2 - how hard can it be? from Immo Hüneke's blog
Here's an article about PDE build automation
Here's a shell script to automate JUnit test launch