Interesting. I updated maven using homebrew and it is working now. I was using 3.0.3 before.
I will use NetBeans then. It will be good to get it working with Eclipse because it is fairly popular. I just need to experiment a little more. Thanks! Travis On Sat, Jun 8, 2013 at 4:40 PM, Martin Desruisseaux < [email protected]> wrote: > Le 08/06/13 22:25, Travis L Pinney a écrit : > > Thanks for fixing that. I was able to build everything from command line. >> > > Cool :-) > > > Eclipse can run maven plugins. I am trying to figure out how to have it >> run >> that builder during a Junit run. It can sometimes be picky with >> the configuration. >> > > An alternative is to not run the plugins, and instead copy the "*.utf" > files generated by Maven as if they were ordinary resources. I don't know > how to achieve that with Eclipse however... > > > Also I see you have to do things like this >> >> mvn clean -Dmaven.version=3.0.4 >> mvn test -Dmaven.version=3.0.4 >> >> Is there a reason to have a maven version be explicitly added to the >> command line? >> > > According Maven documentation, a ${maven.version} property is > automatically provided by Maven since 3.0.4. However for a mysterious > reason, it doesn't seem to be the case on the Jenkins machine, so I had to > add them explicitly in the configuration. However I though they would not > be needed on developer's local machine. Plain "mvn clean" or "mvn test" > work for me. Isn't the case for you? > > > Also what text editor or ide do you use for java development? >> > > I use NetBeans, mostly because I'm used to it. There is also Eclipse and > IntelliJ fans around me. NetBeans can open Maven projects natively, but SIS > also contains a "ide-project/NetBeans" directory with everything configured > for those who wish. There is also a "ide-project/eclipse" directory for the > same purpose, but I don't know if it is up-to-date... > > Martin > > >
