Versions Compared

Old Version 14

changes.mady.by.user Glen Mazza

Saved on

compared with

New Version 15

changes.mady.by.user Glen Mazza

Saved on

Key

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

...

  1. Explicitly on the command line. When running eclipse:eclipse, add -Declipse.workspace=/home/dkulp/working/workspace
  2. Update your Maven ~/.m2/settings.xml to have a active profile that always sets these 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. .h2

How Does This All Work, Anyway?

If you are wondering about how all this manages to make Eclipse, Maven, Checkstyle, and PMD
cooperate, see Connecting Maven, Eclipse, Checkstyle, and PMD.