Skip to content

Conversation

@owolabileg
Copy link
Contributor

I am suppressing the code which adds the bootclasspath attribute to the generated agent's manifest.mf file. First, @Databean's experience (see his comments in #60) shows that the agent doesn't really need it. Second, according to this sun official document, that attribute is completely optional. Third, this is causing some unnecessary warnings to be generated in windows.

@pdaian, @Databean, @seriousamlqz, please review

@Databean
Copy link
Contributor

Databean commented Sep 8, 2014

I may have been unclear in my previous comment; my experience was that only the boot-classpath was used for the agent jar, and not the system classpath. I was unable to get it working without the boot classpath.

@owolabileg
Copy link
Contributor Author

Thanks a lot @Databean !

"I was unable to get it working without the boot classpath" - can you please clarify?

We are able to build agents and run them in Windows and Linux, even after removing the boot classpath, so I am not sure what you meant.

Thanks again.

@traiansf
Copy link

traiansf commented Sep 8, 2014

For Rv-Predict we've noticed that if our libraries are not in the bootclasspath and if the program uses multiple classloaders, then the agent might not be able to access those libraries.

pdaian added a commit that referenced this pull request Sep 10, 2014
@pdaian pdaian merged commit 6ee43f1 into master Sep 10, 2014
@owolabileg owolabileg deleted the removeBootClassPath branch September 12, 2014 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants