In addition to what was said by Marc: if you talk about "jacoco:dump", then you can already pass proxy settings using standard Maven environment variable - "MAVEN_OPTS". If not, then please elaborate more on your requirements and setup.
On Thursday, January 19, 2017 at 4:21:45 PM UTC+1, Marc R. Hoffmann wrote: > > Hi, > > some remarks: > > - The JaCoCo remote protocol is plain TCP/IP (not http), so you can't > use a regular http proxy, you need something like SOCKS > - I hope your JaCoCo agents do not run in public internet. The remote > port is completely unprotected, may be used to exploit data or do a DoS > attack. See warning in documentation. > - Poxying TCP/IP connections with SOCKS is typically configured on OS > level. > > Please elaborate more on your setup regarding my points above. > > Thanks, > -marc > > On 2017-01-19 01:11, Abraham Tehrani wrote: > > We have a situation in that in order for our Jenkins infrastructure to > > talk to our system's under test on port 6300 we need to use a proxy. > > This is kind of an enhancement request to have the ability to pass a > > proxy setting to the Maven plugin. > > > > What are your thoughts? > -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/5072221c-c608-4f72-baac-5fd078670fef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
