How to get started?

[jendave]

I have created a new page in the wiki describing full Maven/Git/Eclipse integration.
http://www.slightlymagic.net/wiki/Forge ... ntegration

Please take a look. It is still a little rough.

Dave

[Braids]

I have created a new page in the wiki describing full Maven/Git/Eclipse integration.
http://www.slightlymagic.net/wiki/Forge ... ntegration

Please take a look. It is still a little rough.

Dave

what if i have already right-clicked pom.xml, and have run it as a maven build successfully? do i still need to go through your document?

[Chris H.]

I deleted my git project and started over. I already have the performed the Create and Register Your Public-Private Key Pair previously.

I was not able to select a SCM. I installed the connectors from the m2e Marketplace. I then re-started.

I redid the previous steps inoder to checkout Forge from Git and setup up a Maven project in Eclipse. I get a Problem Occurred dialog and no project:

`

[Chris H.]

I deleted the Eclipse folder, the project folder, the git folder and the workspace folder. I installed Eclipse and the needed additional files. I used the Clone the Git Repository and the Import the Cloned Repository instructions rather than new Import Maven Project instructions.

Towards the end of the Import the Cloned Repository instructions I saw something new. A window came up with a list of connectors that Eclipse wanted to install. Granted, they were only SVN subversive connectors. I added them for the heck of it. It should not be needed with Git.

I did not go through the Import Maven Project configuration instructions. Yet I have all of the Maven goals listed and named correctly. I am only missing the 1 Run on Server menu item.

I have the full list of build dependencies. Looks like I some how got really close to getting it all set up ... not quite sure how I did it though.

[jendave]

Chris - when you select the Team menu item do you get a list of Git commands like the screenshot? I have a theory on the error you are getting - it is likely that my setup assumes a git executable is installed and in the path. This is different from the Git connector. Oh well, my doc will work in some setups, but not all.

[Chris H.]

Chris - when you select the Team menu item do you get a list of Git commands like the screenshot?

`
Yep, mine matches yours line by line. But I believe that all/most of those menu items were there before I saw and tried to follow your wiki.

And my Run As and my Debug As are now fully populated, except they are missing the 1 Run on Server menu item. Before your wiki my Run As and my Debug As were not populated.

[Chris H.]

Ran a local build with this as the goal:

Code: Select all

-U -B clean -P osx,windows-linux install

`
and get the following error:

[ERROR] Failed to execute goal com.akathist.maven.plugins.launch4j:launch4j-maven-plugin:1.3.3:launch4j (l4j-gui) on project forge: Failed to build the executable; please verify your configuration. net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@2c59109c -> [Help 1]

`
I also get a dialog pointing out that with the Lion OS installed I can't open the application windres because PowerPC apps are no longer supported. Looks like I may have to revert back to Snow Leopard.

[jendave]

Ran a local build with this as the goal:

Code: Select all

-U -B clean -P osx,windows-linux install

`
and get the following error:

[ERROR] Failed to execute goal com.akathist.maven.plugins.launch4j:launch4j-maven-plugin:1.3.3:launch4j (l4j-gui) on project forge: Failed to build the executable; please verify your configuration. net.sf.launch4j.ExecException: Exec failed(2): [Ljava.lang.String;@2c59109c -> [Help 1]

`
I also get a dialog pointing out that with the Lion OS installed I can't open the application windres because PowerPC apps are no longer supported. Looks like I may have to revert back to Snow Leopard.

The launch4j jars both standalone and Maven run a native executable on each platform. It sounds like the executable is not compatible with Lion. I have not yet upgraded so I cannot see it myself.

[Chris H.]

I cloned the last Snow Leopard backup on my Time Machine to an extra 500 GB HD. I verified that I can build the archives. This will take care of this issue for the moment.

I can continue to keep Lion on my interior boot HD. I can reboot to the Snow Leopard HD when I need to do the next build and release.

[jendave]

I cloned the last Snow Leopard backup on my Time Machine to an extra 500 GB HD. I verified that I can build the archives. This will take care of this issue for the moment.

I can continue to keep Lion on my interior boot HD. I can reboot to the Snow Leopard HD when I need to do the next build and release.

That is good news. To bad you have to dual boot though. Once I upgrade (may be awhile since I usually wait until the first maintenance release) I'll see if I can debug it.

[Chris H.]

That is good news. To bad you have to dual boot though. Once I upgrade (may be awhile since I usually wait until the first maintenance release) I'll see if I can debug it.

`
The rumor mills have suggested that Apple might weaken their requirements and allow Snow Leopard to be run from Lion via a virtualization app such as Parallels or Fusion. But I do not want to pay for the server version of Snow Leopard to do this.

There have been a few reports that VirtualBox can handle this now...

[jendave]

That is good news. To bad you have to dual boot though. Once I upgrade (may be awhile since I usually wait until the first maintenance release) I'll see if I can debug it.

`
The rumor mills have suggested that Apple might weaken their requirements and allow Snow Leopard to be run from Lion via a virtualization app such as Parallels or Fusion. But I do not want to pay for the server version of Snow Leopard to do this.

There have been a few reports that VirtualBox can handle this now...

From your error message, windres appears to be built against PowerPC and not Intel, so I will try to find/compile a new version.

[Chris H.]

From your error message, windres appears to be built against PowerPC and not Intel, so I will try to find/compile a new version.

`
No need to rush.

[jeffwadsworth]

Within Eclipse: I don't know who fixed the right-click on ForgeGit [cardforge master] and select Run As Java Application, but thanks. This makes things so much easier.

[Chris H.]

Within Eclipse: I don't know who fixed the right-click on ForgeGit [cardforge master] and select Run As Java Application, but thanks. This makes things so much easier.

`
I was also missing the Run As Java Application menu command. Installing the Maven connectors seems to have taken care of this.

I added a brief section to the wiki explaining the maven commands. Most people will not need to use these commands. But it is nice to know what their purpose is even if you do not touch them.