[jbossts-issues] [JBoss JIRA] (JBTM-1407) Have a build option that builds JTS only against JacORB or IDLJ, but not both.

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750463#comment-12750463 ] 

Tom Jenkinson commented on JBTM-1407:
-------------------------------------

It should be trivial to do that *today* for JDK orb with profiles as you can activate a profile by the presence of a file, e.g. JAVA_HOME/lib/orb.idl. However, JacORB would be in the classpath unless you specifically disabled it with a different profile so its presence would be guaranteed. Now, in the future when AS7-5582 is implemented, the "JDK" orb will be a maven dependency (same as JacORB), i.e. it will be available by default in the classpath.

Lets say we made the change today as a convenience until AS7-5582 is available, the question is do we really want to have unpredictable results in the build. Lets say the user attempts this new default, detection based build but does still expect both a JDK orb and JacORB version but we as can't locate orb.idl (say they are on pi) and just build the JacORB version - what would you expect then, log a warning?
                
> Have a build option that builds JTS only against JacORB or IDLJ, but not both.
> ------------------------------------------------------------------------------
>
>                 Key: JBTM-1407
>                 URL: https://issues.jboss.org/browse/JBTM-1407
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JTS
>    Affects Versions: 4.17.3
>            Reporter: Mark Little
>            Assignee: Gytis Trikleris
>             Fix For: 5.0.0.M2
>
>          Time Spent: 2 days, 5 hours, 50 minutes
>  Remaining Estimate: 2 hours
>
> This boils down to supporting two new profiles:
> ./build.sh -P jts-jacorb
> ./build.sh -P jts-idlj

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira