1
0
-1

We recently upgraded from Transact Fluent API 5.1.x to Transact SDK 18.5.1.  We have on the order of ~80 fluent services and, under our previous IntelliJ development environment, each fluent service had its own ant-based build file which allowed us to build and deploy individual services.  Under the new 18.5.x model, it appears that the focus has shifted to deploying all fluent services as one global service package.

Is this the intention or did I just miss how to configure single service builds?

    CommentAdd your comment...

    2 answers

    1.  
      2
      1
      0

      Hi Thorston,

      I had the same concern when we first started using Transact SDK 18.x.

      I found that in the 'build.properties' file there is the ability to specify a single service to be the focus of the 'build'.

      This section of the file can be modified to target a single service:

      # Service Name (enable building single service instead of all services in "src" folder)
      #svc.name=serviceA
      #svc.name=serviceB
      svc.name=serviceC
      #svc.name=serviceD

      In the above case 'serviceC' will be the target of the Ant build task, such as package or deploy.

      If you comment out all the individual services, so that "Service Name" is not set, then all services in the 'src' folder will be built.

      You need to be concious of which service your are working with, and I found this change of mind set a bit hard to get used to. I'm slowly getting used to it.


      Hope that helps.

      Thanks

      Mark

        CommentAdd your comment...
      1.  
        1
        0
        -1

        Thanks, Mark, I had missed that entirely.

          CommentAdd your comment...