Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-18876

Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • 4.5.1.AM1
    • 4.3.0.Alpha1
    • build
    • None
    • Workaround Exists
    • Hide

      1. Rollback to previous revision and release to local maven repository
      2. Sometimes it is possible to use multiple target platform with
      -Dtpc.targetKind=multiple

      Show
      1. Rollback to previous revision and release to local maven repository 2. Sometimes it is possible to use multiple target platform with -Dtpc.targetKind=multiple

      Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.

      So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus.

      Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.

            nivologd@gmail.com Denis Golovin (Inactive)
            nivologd@gmail.com Denis Golovin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: