Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-2223

Create optaplanner-ide-config module (artifact) to avoid paths that go outside the directory

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None

      We want to be get the optaplanner IDE configuration file from the maven repository,
      because optaplanner-quickstarts, optaweb-* and maybe the optaplanner-examples in a distribution assembly, can have need it of without having the optaplanner repo itself checked out.

      Refactor to this structure:

      /pom.xml (optaplanner-parent) which has new/edited <modules> entry:
             <module>build/optaplanner-ide-config</>
               <module>build/optaplanner-build-parent</>
    /optaplanner-bom/pom.xml // UNCHANGED
    /build/optaplanner-ide-config/pom.xml // NEW
                    extends optaplanner-parent
                   similar to how quarkus does it, see quarkus repo, directory independent-projects/ide-config/pom.xml
    /build/optaplanner-build-parent/pom.xml
                    formatter plugin with dependency on optaplanner-ide-config
                   similar to how quarkus does it, see quarkus repo, directory build-parent/pom.xml
    /optaplanner-core/pom.xml
    ...

      Also get rid of all occurrences of 

      <format.directory>

      , such as:

        <properties>
    <format.directory>${project.basedir}/../../ide-configuration</format.directory>
  </properties>

              cchianel Christopher Chianelli (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: