In my team, some of them are using Netbeans and some of them using Eclipse, so in our Subversion repository for each JAVA project we have Netbeans & Eclipse project files.
I do want to keep Netbeans & Eclipse project setting files inside the JAVA project, they are specific to IDEs.
Please help me to maintain only the JAVA source files inside the subversion.
Use a common build infrastructure, like maven. This encapsulates (as good as) all settings inside the maven pom.xml files (source encoding, java version etc.).
Also versioned library dependencies, subprojects are managed in maven.
NetBeans knows maven out-of-the-box, and eclipse has a good maven plugin.
In my experience manual configuration, especially in eclipse, and grown ant scripts, are cumbersome.
Related
I have imported my Tycho project in Eclipse using m2eclipse and I have the following issue: Tycho adds the Java nature to eclipse-plugin projects that don't have any Java code, for example the help plugin. It's not a big deal, but I find it annoying.
Is there any way to disable this?
Tycho doesn't define a separate packaging type for Eclipse plug-ins without code.
So if the Tycho Project Configurator, i.e. the m2eclipse extension for Tycho, wanted to omit the Java nature for eclipse-plugin projects, it could only do so after scanning the entire project for *.java files. And even then it would not be clear if the project does not contain Java code, or simply not yet contain Java code.
So, having the Java nature on all eclipse-plugin projects is a simple and robust choice that makes sense IMHO.
I am working on a java project. The developer who started working on it is pretty firm on using myeclipse and I am pretty firm on using eclipse. Is there a way I can use the project settings that would not conflict with MyEclipse. When I open the project in Eclipse, I see a lot of myeclipse jar files for Java EE and what not. He's not using maven.
You will need to keep your project folders private and only share the source. Both of you cannot use the same project metadata.
Sharing metadata will cause both of you pain. And even more when upgrading to newer versions of eclipse and reading old projects.
Our solution was to switch to maven, and NOT having any metadata in source control repository. The m2e plugin then generates exactly the metadata you need when you import the maven projects in Eclipse.
An added benefit was that suddenly our projects worked with Netbeans and IntelliJ without any extra effort.
I am trying to set up a project, but feel completely overwhelmed with lack of knowledge. In university we used netbeans which resolved project structure gently for us. As community leans towards eclipse I am trying to migrate there, but feel myself like a penguin not able to fly. I can't understand project structure where and what has to be added, do I have to define ANT or MAVEN manually in eclipse can they be integrated? Where to go ? Apache manuals are so complicated, why is that I can program in Java , but don't know the fundamentals, soo depressed, please anyone guide me. I find pieces on web, but seems can't build full picture in my head.
You have a couple of options. Basically, eclipse uses a workspace, which contains one .metadata directory used by the plugins and all of the project folders. Projects can then be things like java projects, PDE projects, PHP projects, etc.
There is maven integration in eclipse which I would use, http://www.eclipse.org/m2e/ It was part of Indigo, which released June 2011.
Set up your java projects in your workspace, and then use m2e to mavenize them, or use m2e to generate the java projects into your workspace.
maven provides a facility to create a new project with the required structure based on the type of project (jar, war, etc.).
You can do this or achieve it directly from Eclipse as suggested by Paul Webster, by installing the m2e plugin.
This structure can then be easily built using maven, as well as developed in Eclipse.
While installing the open-source software like Mahout, I read some notes like
Convert Maven project of Mahout into Eclipse project
What does this mean? What's the difference between a Maven project and Eclipse project?
Install Maven if you haven't already done it.
Enter the command prompt or a shell and navigate to the directory where the Mahout is located (there's a pom.xml file). Type the command:
mvn eclipse:eclipse
which will create project files for Eclipse and open the project in Eclipse.
No conversion is needed. Eclipse supports Maven projects, and vice-versa.
Difference between these two projects yield from the difference of the tools. Eclipse is an IDE and Maven is a build tool. In fact, IDE is a superset of a build tool. That's why Eclipse may use Maven for building. Common properties between the projects relate to how the build is being done and Eclipse has a set of properties aimed to persist the state between programming sessions.
I just created a Web App project from a repository through Eclipse's SVN support. What I would be doing is have an ANT build going and then finally deploy through Tomcat.
I am using Eclipse IDE for Java EE developers on an Ubuntu system.
There are a number of jar files needed
to support my project - like Struts,
Hibernate, etc. etc.
Do I need to
manually download each of them
and put them in the lib folder?
OR
Does Eclipse have a solution to
automatically UPDATE these from the internet? Any plugins to automatically take care of this?
You should consider using Maven for your project. It's VERY well supported in Eclipse, and handles all dependencies (as well as other things, such as releases).
The problem is there's a bit of a learning curve, but if you intend your project to get to a considerable size, I'd say it's very important.
Maven has support for ant builds and most libraries are in the central Maven repository. You just say your project has a dependency on the external project and it will automatically download the dependencies.
http://maven.apache.org/