Skip to content

Repackage 3rd party libraries to avoid collisions with SUT libraries #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 0 comments
Closed

Repackage 3rd party libraries to avoid collisions with SUT libraries #35

GoogleCodeExporter opened this issue Apr 6, 2015 · 0 comments
Labels
auto-migrated Priority-High Project-JvmConnector Target-1.0 Type-Defect

Comments

@GoogleCodeExporter
Copy link 

SUT might use the same library classes as the JVM connector, so they are
renamed and repackaged in order to avoid the collisions with the SUT ones.
The problem occurs if the library versions are different.

Please see also issue33.

Original issue reported on code.google.com by [email protected] on 11 Feb 2010 at 2:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-High Project-JvmConnector Target-1.0 Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter