I will do my best to describe the problems I am experiencing, but this is all fairly new to me, so if there is any more information required, I will do my best to provide it.
I am having two issues and I am unsure as to whether or not they are related or not.
The first problem is one I am experiencing with SVN. I add our branch as an SVN location within Eclipse, I then check out the Domain as well as the project. The project used to check out with a whole lot of Maven dependencies, however it no longer does this and I have to add a user library to my build path containing hundreds of JARS and there are still some missing that I am unable to locate. Also when we start working on a new branch, I am unable to switch my branch, I have to delete the project from my work space and re check it out and re add the user library. This all started after I noticed that when I checked out the project it was not checking out with the latest files in some instances, so I decided to delete my work space and start from scratch.
Then second issue I am having is when I build using Maven, there is a file in my Domain (which has been built successfully), this file is referenced from my project and even though when I open up the file in question it has all the relevant methods I need, I try to build the project and it complains about these methods being missing from the Domain file and hence the build fails.
If anyone has any idea about what might wrong I would appreciate suggestions. I hope this makes sense.
Maven and user libraries are pretty much mutually exclusive. A Maven project is expected to be a self-contained collection of resources where everything needed to produce a product is either buildable from sources in the project or pulled from Maven archives as dependencies.
What it sounds like is that you may be having IDE issues where the Maven dependencies don't automatically connect to the IDE, robbing you of things like the ability to debug at the source level inside dependencies, auto-complete text, and/or get the nice documentation pop-ups. Sometimes in such cases it's necessary to pound the Eclipse enviroment into shape. For example, make sure that your Eclipse project is defined as a "Maven Project"
Even after all this time, occasionally I have to do some random banging on things, so if you need more help, we'll move this thread to the Eclipse forum.
Sometimes the only way things ever got fixed is because people became uncomfortable.
Yes, Tim is right. You want to import the project as a Maven project. If you can build your maven project from command-line, and you are have imported the project as a maven project into eclipse, then you should be able to build the project without any problem. All eclipse does is run the same command-line that you run
If you are unable to build your project from command-line, then there is something wrong with your project, and you need to fix that first before it runs in eclipse.
If you haven't imported the project as a maven project, then you should do so right now. Eclipse doesn;t stop you from creating a normal java project and importing your source files into it. You will create a lot of headaches if you do this
Why is the word "abbreviation" so long? And this ad is so short?