Hi Eric,
Just skip the tests:
mvn -DskipTest install
Even with right connection settings the tests wont pass because they depend on various datasets various magja contributors have accumulated ;-)
I only run the tests inside Eclipse and even that only the tests I'm currently interested at particular time. Bippo/Soluvas Jenkins CI builds also skip tests.
Btw I'm not the only contributor. For further stuff please use the magja googlegroups.
Hendy
Hendy,
I was wanting to email you because this isn't really a issue with the project as a whole…more or less a problem i am having. I am basically unable to get he soap connection to work when i do my own compile. If i do your sonatype repository my connection works just fine (properties file is in local /resources folder).
I do have my magenta-api.properties file in both my local code AND the projects /src/main/resources folder. I am running the basic maven build lifecycle to creat the javadoc and the sources jars.
mvn process-resources
mvn compile
mvn test
mvn package
mvn install
I have also cloned your repository to my local computer and i can't get the tests to connect eather. Your readme talks about a magja-consloe but i don't see that shell file. I can go look at history and get the magja-console script but when i run that maven says i don't have a profile named console. I just was wanting to know what i was doing wrong.
Thanks for your hard work. This connector s the best one i have seen and i am glad someone is working so hard on this project!
Eric
Is your project using Maven?
Because if not, you'll need other dependencies like Axis2, guava etc.
Better use Maven so you'll get all the transitive dependencies.
Hendy
Is your project using Maven?
Because if not, you'll need other dependencies like Axis2, guava etc.m
there seems to be at least 2 mistakes:
1. You're using m2e, but you also used mvn eclipse:eclipse which should not be used.
2. I see that your project (not magja) lists magja as a Library dependency,which is wrong. You should put magja as a dependench on your project's pom.xml. Then magja should be listed *inside* Maven dependencies of your project. Not as a sibling of Maven dependencies as depicted on your screenshot.
Hendy