Versions Compared

Old Version 6

changes.mady.by.user willem jiang

Saved on

compared with

New Version 7

changes.mady.by.user Daniel Kulp

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

That's all there is to it. From eclipse, all the unit tests and system tests should be runnable. However, to build kits/jars and stuff, you still need to use the command line "mvn" stuff.

Importing new projects that depend on CXF projects

With the latest version (2.5) of the maven-eclipse-plugin, when you run "mvn eclipse:eclipse" on a project, if it knows where your workspace is, it will see what projects are already defined and wire them in to the new project instead of pointing at the jars in your ~/.m2/repository dir. Thus, debugging is a lot easier. There are two ways to get it to know where your workspace is:

  1. Explicit on the command line. When running eclipse:eclipse, add -Declipse.workspace=/home/dkulp/working/workspace
  2. Update you ~/.m2/settings.xml to have a active profile that always sets the variables. Thus, whenever the eclipse plugin looks for it, it know where the workspace is. In settings.xml, do:
    Code Block
    

    <activeProfiles>
        <activeProfile>extra</activeProfile>
    </activeProfiles>
    <profiles>
        <profile>
            <id>extra</id>
            <properties>
                <eclipse.workspace>/home/dkulp/working/workspace</eclipse.workspace>
                <eclipse.workspace.dir>/home/dkulp/working/workspace</eclipse.workspace.dir>
            </properties>
        </profile>
    </profiles>
    By doing that, you can pretty much run eclipse:eclipse (or -Psetup.eclipse for cxf projects) at any point and it will always wire the new project to depend on the existing projects.