Collectible Card Game Headquarters

Braids wrote:yes, that's where i got started, too. if anyone finds any errors in the pre-alpha Getting Started Guide https://www.gitorious.org/cardforge/pages/Getting_Started_Guide regarding key generation, please edit it or let me know! thanks.

`
I will try this out today.

Braids wrote:the new getting started guide https://www.gitorious.org/cardforge/pages/Getting_Started_Guide is now ready for alpha test. using it, i was able to push a change to the repo on gitorious.

because gitorious's wiki doesn't handle concurrent editing very well, please do not edit the document. instead, please post your comments here.

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

5. Please note that you should go to your dashboard and click on the Edit Details button. Enter a full name in the text box which is located above the E-mail text box. The name and e-mail address that you add to the Comment field should match the contents of these two text boxes.

8. You will notice that the key is being saved to your ~/Users/youraccount/.ssh/ folder.

17. Click the Save button in your web browser to save your public SSH key. Go to your dashboard on Gitorious. Click on Manage SSH Keys. You should see Your SSH Keys with a green colored check mark under the Ready? column.

@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.

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

Rob Cashwalker wrote: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

I think what you want to do is Pull from the Master to your clone. This should update your local files, and merge any changes (and tell you to manually merge any conflicts it can't resolve). Then you want to Push back to the Master. I'm not sure if Sync is actually doing the same thing it does in SVN, which would cause you to have "changed" files that don't actually have any changes in them.

I gotta say that SVN was a whole lot simpler....

Rob Cashwalker wrote:I gotta say that SVN was a whole lot simpler....

Yeah, there really is no comparison. But, at least we have a safehouse.

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.

Thank you Dave.

I am not fully up to speed yet, working on the getting started guide with Braids and taking this one step at a time.

On another rev control issue, where should we put the artifacts of the release process -

Releases - go to ftp.cardforge.org per Rob
Site Reports - used to be in google SVN
Daily Builds - this would be great

While Rob will graciously host the releases, I want to be conscience of the bandwidth that the Site and dailybuilds may take. Any ideas? I researched uploads into Git, but it does not look as robust as the SVN support was.

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?

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

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.

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.


EDIT:

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.

I clicked on Manage SSH Keys and there is a green colored check-mark in the Ready? column.



It finally finished and everything looks OK at this time. The Import the Cloned Repository took longer that expected.

cardforge.org is now on an unlimited bandwidth server. It's a little sluggish sometimes, but that's the price of dirt-cheap unlimited hosting...

you can put the site reports onto cardforge.org as well

jendave wrote: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

jendave wrote: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.

`
Were you referring to this:


`