[iot-pmc] [CQ 17875] BeanShell 2.0b4

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=17875





--- Comment #8 from Ilya Binshtok <ilya.binshtok@xxxxxxxxxxxxxxx>  2018-11-01 11:13:11 ---
(In reply to comment #7)
> (In reply to comment #5)
> > 
> > Hello Kai,
> > 
> > Bean Shell is a dependency relevant for building/testing as shown below:
> > 
> > [INFO] +- org.testng:testng:jar:6.9.10:test
> > [INFO] |  +- com.beust:jcommander:jar:1.48:test
> > [INFO] |  \- org.beanshell:bsh:jar:2.0b4:test
> > 
> > As you can see, the Bean Shell 2.0b4 along with jcommander 1.48 is a dependency
> > of the TestNG 6.9.10.  
> > 
> > Note that TestNG 6.9.10 has already been approved in CQ #17874 (PB CQ11325).
> > And  jcommander 1.48 has been approved in CQ #17873 (PB CQ9859)
> > We don't use Bean Shell anywhere else.
> > 
> > 
> > Best regards, 
> > 
> > Ilya
> > 
> 
> You do not need to create individual CQs for test/build-only dependencies.
> Please see [1] for details and then withdraw all the CQs you have created for
> test/build-only dependencies and replace them with a single works-with CQ as
> described in the link. This will save the PMC and the IP team a lot of work.
> 
> You might also find the Project Handbook's IP section [2] to be of particular
> interest.
> 
> Thank you,
> Kai 
> 
> [1]
> https://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies
> [2] https://www.eclipse.org/projects/handbook/#ip
> 

Hi Kai,

Yes, I will do this for assertj-core and BeanShell since those dependencies
have not been approved yet. But Tahu has other test-only dependencies:
* testng 6.9.10
* jcommander 1.48
* junit 4.8.2
that have been approved because I piggy backed them to approved CQs. I assume
that I should not withdraw these approved test-only CQs, right?

Best regards, 

Ilya


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.