does dmca push us further toward distributed rev control?

[Chris H.]

Please install the Maven plugin for Eclipse. It is available from the usual menu item in Eclipse under "Maven Integration for Eclipse". I have updated the pom.xml and added back the .classpath and .project files. I was able to build and run Forge fine from within Eclipse without using any Maven speific commands i.e. the Maven integration is transparent. you will notice the dependencies look different because that is what we actually use for the release builds. If there are any issues, let me know.

http://eclipse.org/m2e/

I haven't run into so many dead links in a long while...

This may be better:

http://marketplace.eclipse.org/content/ ... on-eclipse

`
I followed Braids instructions in the getting started wiki. The instructions for adding EGit is the same for Maven Integration for Eclipse. I installed both at the same time.

[Braids]

I was able to follow the Create and Register Your Public-Private Key Pair instructions and they were helpful. A few additions follow . . . 5 . . . 8 . . . 17 . . .

i have implemented the spirit of your three suggestions. please note the document has moved to the slightlymagic wiki at http://www.slightlymagic.net/wiki/Forge:How_to_Get_Started_Developing_Forge. slightlymagic's markup capability uses the same as wikipedia (mediawiki). thus it is superior to the {markdown} used by gitorious's wikis. i replaced the page on gitorious with a detour link.

[Rob Cashwalker]

I just installed a fresh copy of Eclipse Indigo on my work computer. I installed EGit and m2e.
I pulled a fresh clone of ForgeGIT.

The automatic behind-the-scenes build in Eclipse fails, the dependencies for google collections is missing.

[Braids]

@Braids.
Clone the Git Repository
In the very helpful guide, you may want to include something about using the "passphrase" as the password if prompted after step 12 or so.

please check the section here http://www.slightlymagic.net/wiki/Forge:How_to_Get_Started_Developing_Forge#Clone_the_Git_Repository and let me know if my text is correct and in the right place.

[Braids]

I'm having a hard time getting my local clone to update to the latest repository.

I have some pending changes to the Quest mode to support the standard cardpool stuff. It's pretty much done, but before I commit I always do an update, to make sure nothing new would interfere, and if it did, I would get an obvious indication of where the conflict was.
I did a Pull operation, from the main repository and it notified me that there were conflicts. I went into synchronize mode, and started checking each change listed to use the Merge function... Now my local repository shows lots of files as being changed, even though my changes were only in a few specific files.
I might just as well start a fresh clone

isn't that supposed to happen? merging a file creates a new incarnation of that file, which you are partially responsible for having created. am i right?

[Braids]

I followed the Clone the Git Repository instructions. In step 8 should we add our Passphrase as the password to the Clone Git Respository window?

no, never. this is the misstep Rob warned us about. the username must be git and the password blank. i updated the guide to say that.

If we do not it looks like we get a window asking for our password as was mentioned in an earlier message.

yes, i believe that is when you enter your passphrase.

if the passphrase is too much of a bother, you can create a key without one, but i cannot officially recommend it for security reasons.

[Chris H.]

please note the document has moved to the slightlymagic wiki at http://www.slightlymagic.net/wiki/Forge:How_to_Get_Started_Developing_Forge. slightlymagic's markup capability uses the same as wikipedia (mediawiki). thus it is superior to the {markdown} used by gitorious's wikis. i replaced the page on gitorious with a detour link.

`
Looks good. I would change it to beta rather than alpha. The instructions are fairly complete. There may be a need to add a few more words but for the most part I think that it is close to being finished.

Good work.

[Braids]

Import the Cloned Repository

1. I have one cardforge repository named cardforge without the "-master". I assume that this is the master as there is only one repository listed.

the "-master" is a minor text bug. an older version of the guide suggested the user change the cloned repository's directory name to suffix "-master". now, only advanced users are suggested to do so. i just fixed the text's examples to include both "cardforge" and "cardforge-master".

6. Clicking finish results in a project named ForgeGIT [cardforge master] appearing in Eclipse's Package Explorer view. This will take some time, so be patient.

. . . About ten minutes have gone by and Eclipse is still Updating indexes. Not sure if something is wrong or not. I can give it more time . . . It finally finished and everything looks OK at this time. The Import the Cloned Repository took longer that expected.

i just added a note about the import taking a long time and that the user should see the new ForgeGIT project once it finishes.

[Braids]

Please install the Maven plugin for Eclipse. It is available from the usual menu item in Eclipse under "Maven Integration for Eclipse". I have updated the pom.xml and added back the .classpath and .project files. I was able to build and run Forge fine from within Eclipse without using any Maven speific commands i.e. the Maven integration is transparent. you will notice the dependencies look different because that is what we actually use for the release builds. If there are any issues, let me know.

. . . I haven't run into so many dead links in a long while . . .

you can find maven in the default sites from eclipse. well, at least for eclipse indigo you can.

From http://www.slightlymagic.net/wiki/Forge:How_to_Get_Started_Developing_Forge#Install_Eclipse_Software_Items_.28Any_OS.29:
2. Next to Work with:, choose --All Available Sites--. Wait for a bit as the list in the center populates.
3. Open the Collaboration category by clicking the plus sign or triangle to the left of it.
4. Place check marks next to Eclipse EGit and m2e - Maven Integration for Eclipse only. There are lots of goodies in this list if you are into software development, but let us keep it simple.

[Jaedayr]

I just did

Periodically pull down changes from the server by right clicking the project ForgeGIT in the Package Explorer, choose Team, then Pull.

and have a lot of resources in my local project with a big red X on them. I tried to start Forge and got the following on the Eclipse console.

Code: Select all

Exception in thread "main" java.lang.Error: Unresolved compilation problem:
   Log cannot be resolved

   at forge.Gui_NewGame.main(Gui_NewGame.java:163)

What am I missing? Forge was running yesterday after finishing the Clone process.

[Braids]

I just did

Periodically pull down changes from the server by right clicking the project ForgeGIT in the Package Explorer, choose Team, then Pull.

and have a lot of resources in my local project with a big red X on them. I tried to start Forge and got the following on the Eclipse console.

i think maven hates us. i just did a pull. and i got something similar with the big red X marks. forge started out with over 100 errors in the Problems view. it thought about it for a while, and now the number of errors is down to 18:

Code: Select all

Description   Resource   Path   Location   Type
ArtifactDescriptorException: Failed to read artifact descriptor for com.jhlabs:filters:jar:2.0.235: ArtifactResolutionException: Failure to transfer com.jhlabs:filters:pom:2.0.235 from http://repo1.maven.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact com.jhlabs:filters:pom:2.0.235 from/to central (http://repo1.maven.org/maven2): C:\Documents and Settings\Braids\.m2\repository\com\jhlabs\filters\2.0.235\filters-2.0.235.pom.ahc536ff99f0d2b4a8e (The system cannot find the file specified)   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.beust:jcommander:jar:1.12   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.google.code.jyield:jyield:jar:1.0-SNAPSHOT   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.google.guava:guava:jar:r09   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.googlecode:minlog:jar:1.2   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.miglayout:miglayout:jar:3.7.4   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.mortennobel:java-image-scaling:jar:0.8.5   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact com.thoughtworks.xstream:xstream:jar:1.3.1   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact junit:junit:jar:3.8.1   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact org.beanshell:bsh:jar:2.0b4   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact org.java.net.substance:substance:jar:5.3   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact org.swinglabs:swing-worker:jar:1.1   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact org.swinglabs:swingx:jar:1.6.1   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact org.testng:testng:jar:6.1.1   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact org.yaml:snakeyaml:jar:1.6   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
Missing artifact xpp3:xpp3_min:jar:1.1.4c   pom.xml   /ForgeGIT   line 1   Maven Dependency Problem
The container 'Maven Dependencies' references non existing library 'C:\Documents and Settings\Braids\.m2\repository\com\miglayout\miglayout\3.7.4\miglayout-3.7.4.jar'   ForgeGIT      Build path   Build Path Problem
The project cannot be built until build path errors are resolved   ForgeGIT      Unknown   Java Problem


in the Progress view, it's slowly

Code: Select all

Updating index central|http://repo1.maven.org/maven2: Fetching http://repo1.maven.org/maven2/.index/nexus-maven-repository-index.gz (31%)


Code: Select all

Exception in thread "main" java.lang.Error: Unresolved compilation problem:
   Log cannot be resolved

   at forge.Gui_NewGame.main(Gui_NewGame.java:163)

What am I missing? Forge was running yesterday after finishing the Clone process.

as for this, sorry, i don't know.

[Snacko]

If you have m2e, right click pom.xml and select run as > maven install this will try to build forge and download all the needed dependencies. Maybe select project, right click Maven>update dependencies will download them also.

[Rob Cashwalker]

The only thing I seem to be missing in Maven Dependencies is the google-collections-1.0.jar. If I add it to the build path manually, Forge compiles OK. But I can't figure out how to add it to the maven dependencies...

[jeffwadsworth]

Please install the Maven plugin for Eclipse. It is available from the usual menu item in Eclipse under "Maven Integration for Eclipse". I have updated the pom.xml and added back the .classpath and .project files. I was able to build and run Forge fine from within Eclipse without using any Maven speific commands i.e. the Maven integration is transparent. you will notice the dependencies look different because that is what we actually use for the release builds. If there are any issues, let me know.

. . . I haven't run into so many dead links in a long while . . .

you can find maven in the default sites from eclipse. well, at least for eclipse indigo you can.

From http://www.slightlymagic.net/wiki/Forge:How_to_Get_Started_Developing_Forge#Install_Eclipse_Software_Items_.28Any_OS.29:
2. Next to Work with:, choose --All Available Sites--. Wait for a bit as the list in the center populates.
3. Open the Collaboration category by clicking the plus sign or triangle to the left of it.
4. Place check marks next to Eclipse EGit and m2e - Maven Integration for Eclipse only. There are lots of goodies in this list if you are into software development, but let us keep it simple.

Yeah, you need 3.7...I was using 3.6.

[Chris H.]

Yeah, you need 3.7...I was using 3.6.

`
Until a couple of days ago I was running 3.5.