Details

    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Run a non-profile build first, and then run -Prelease.

      Show
      Run a non-profile build first, and then run -Prelease.

      Description

      I had a chance to look in more detail at the error that I was getting with the jBPM builds. It only happens when running -Prelease (-Psoa, -Pdistro) and it only happens if this is the very first build for a version.

      To reproduce it, change -SNAPSHOT in the pom.xml files to something that does not exist, e.g. -FOO. Then run `mvn -Prelease -Dmaven.test.skip=true install`. You will see that the javadoc phase in "jBPM3 - Core" tries to use modules that aren't yet available (it fails trying to find org.jbpm.jbpm3:jbpm-jpdl:pom:3.2.10-FOO).

      I noticed this because we want to change the SOA build in MEAD to just use the jBPM release, and then we can remove the SOA profile. MEAD has its own repository, and has no access to any other repository. So, whan I tried to build jBPM -Prelease in MEAD, it failed.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                aguizar Alejandro Guizar
                Reporter:
                jcoleman Julian Coleman
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours, 17 minutes
                  2h 17m