Page 2 of 2

Re: Eclipse and Maven

PostPosted: 25 Jul 2011, 18:24
by jendave
jendave wrote:
Please send me the jars. Most of the ones that Forge depends on are on in a standard Maven repo (http://mvnrepository.com), but the ones that were not (jyield), I put into a repo I maintain at http://arcane.googlecode.com/svn/trunk/repository. Since my repo is already a part of the current Forge Maven build, all we have to do is add your mantis jars and we should be good.
Nevermind. I found the mantisconnect jar and uploaded to the Arcane remote repo. I also added it to the Maven pom.xml file. Let me know once you add code that uses it. If there are any problems, let me know.

Dave

Re: Eclipse and Maven

PostPosted: 25 Jul 2011, 20:44
by Rob Cashwalker
I had just sent it to you before reading this. The library I'm expecting to use also requires a number of others, so they may need to be worked in as well.

Re: Eclipse and Maven

PostPosted: 28 Jul 2011, 04:43
by Rob Cashwalker
Nevermind... I spent a while trying to execute the mantis library, expecting errors to point me to which libraries it really needed, and I did my best trying out different matches from the Maven-based versions until I got no errors and a successful bug report. Working on actual implementation and GUI now.

Re: Eclipse and Maven

PostPosted: 04 Aug 2011, 14:21
by jendave
I have reorganized the root project directory to make it more Maven friendly. Please do a 'git pull' and 'refresh' the project in Eclipse. You will see that all the main source code is under src/main/java and the test code is under /src/test/java.

Re: Eclipse and Maven

PostPosted: 04 Aug 2011, 22:10
by Braids
jendave wrote:I have reorganized the root project directory to make it more Maven friendly. Please do a 'git pull' and 'refresh' the project in Eclipse. You will see that all the main source code is under src/main/java and the test code is under /src/test/java.
holy Flux!

this is a test . . . of my EGit skills. i see right through you, Dave. :twisted: {UB} :wink:

Re: Eclipse and Maven

PostPosted: 05 Aug 2011, 01:57
by Rob Cashwalker
I now have three nodes with code in them: src/main/java, src/test/java and src. src has conflicts, compared to my local copy, the differences are in the Bug Reporting update I pushed last night. Looks like I have to delete and re-pull again...

Re: Eclipse and Maven

PostPosted: 05 Aug 2011, 02:03
by Braids
Rob Cashwalker wrote:I now have three nodes with code in them: src/main/java, src/test/java and src. src has conflicts, compared to my local copy, the differences are in the Bug Reporting update I pushed last night. Looks like I have to delete and re-pull again...
that should be OK. does src have any java files in it? it shouldn't.

edit: you should be able to move your code from the src folder into the corresponding package within the {src/main/java} folder.
edit 2: the only thing i learned this evening about EGit is that sometimes, if pulling fails, and merging fails, push still might work just fine. sounds dangerous, but it actually was smart enough in a particular case where i had done too many hard resets.
edit 3: oh, and that anything involving EGit and "synchronization" is either a wretched hive of scum and villainy or more powerful than i could possibly imagine. i'm leaning toward the former.

Re: Eclipse and Maven

PostPosted: 05 Aug 2011, 02:32
by Rob Cashwalker
yeah, no actual code, just the two files I had last modified.

I moved them over, did an add, then did a commit, only to find that it thought ALL the files had been changed.

So, yeah, seems like the smartest thing is to dump and run...