[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1413) introduce continuous integration that test parts with limited classpaths

[Tom Baeyens (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBPM-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12423625#action_12423625 ] 

Tom Baeyens commented on JBPM-1413:
-----------------------------------

[13:49] <porcherg> tomb: i'm trying to do JBPM-1413
[13:50] <porcherg> (limited claspath for tests)
[13:50] <porcherg> but the compile classpath in maven is always included in tests
[13:51] <porcherg> I see 2 solutions:
[13:52] <porcherg> - create a profile in pvm module which compiles only the minimal set of classes (without dependencies), and then run the basic features tests
[13:52] <porcherg> - create a separate module for these tests
[13:53] <porcherg> this module only depends on the pvm core module, and contains only one test classe which launches the BasicFeaturesTest
[14:14] <tomb> porcherg:
[14:15] <tomb> first option you specified is not an option
[14:15] <tomb> sometimes classes need to be compiled with a bigger classpath
[14:15] <tomb> then what is necessary at runtime
[14:15] <tomb> so probably creating a separate module is our only option
[14:16] <tomb> note that all the classes and tests should stay in the core module
[14:16] <tomb> i only want the module to contain/overwrite the test classpath and the set of tests that are included
[14:17] <tomb> so just a pom in the module should be sufficient
[14:17] <tomb> can you check if that is possible ?
[14:17] <tomb> i'll see if i can double check your findings on profiles
[14:29] <porcherg> tomb: i had the same conclusion about the first solution

> introduce continuous integration that test parts with limited classpaths
> ------------------------------------------------------------------------
>
>                 Key: JBPM-1413
>                 URL: https://jira.jboss.org/jira/browse/JBPM-1413
>             Project: JBoss jBPM
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: PVM
>            Reporter: Tom Baeyens
>            Assignee: Guillaume Porcher
>            Priority: Critical
>
> This should guard against introduction of unexpected dependencies.  To compile the PVM, a big classpath is needed as it includes many integrations and options.  But the core essence should still be usable without any external dependencies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira