Jaroslav Bachorik
|
Posted: October 20, 2010 20:04 by Jaroslav Bachorik
|
|
Greetings to all! Finally I was able to get all the bits together and create a coherent 1.2 release of BTrace. It is synchronized with the updated releases of VisualVM and NetBeans plugins. The main themes for this release are
Along the main line there is a lot of small but important improvements proposed and implemented by Joachim Skeie. For more detailed info about fixed bugs and implemented features check release notes. Enjoy! -JB- |
BTrace 1.2 is out
8 posts
Replies: 7 - Last Post: June 13, 2011 16:51
by: Joseph Pallas
by: Joseph Pallas
showing 1 - 8 of 8
|
Jaroslav Bachorik
|
Posted: April 04, 2011 07:15 by Jaroslav Bachorik
|
There were some troubles with the java.net maven repository related to the site migration. Currently, I am not able to upload the artifacts to the new location  You can generate (and install) your local artifacts by checking out btrace core and executing following code hg up release-1.2 ant -f make/build.xml clean jar create.poms Once I figure out where to publish the 'official' artifacts I'll upload them there. |
|
Jaroslav Bachorik
|
Posted: April 18, 2011 12:28 by Jaroslav Bachorik
|
|
Ok, finally figured out how to access the new java.net maven repository. The 1.2 release artifacts have been uploaded. Info on how to access the repository here |
Joseph Pallas
|
Posted: June 10, 2011 16:29 by Joseph Pallas
|
|
Is it possible that the 1.2 release in the maven repository is somehow different from the 1.2 release on the download page? I just spent some time trying to track down a problem with using the javaagent and I got different behavior depending on which jar file I used. I can't help noticing that the 1.2 release tag in Hg has a newer date than the download files at http://kenai.com/projects/btrace/downloads/directory/releases/release-1.2. |
|
Jaroslav Bachorik
|
Posted: June 13, 2011 10:35 by Jaroslav Bachorik
|
|
I will check it. The file timestamp in kenai is created at the time of the first upload and then it might not get updated when uploading a newer version. However, I will try to compare the archives and fix any discrepancy. Thanks a lot for reporting! Cheers, -JB- |
|
Joseph Pallas
|
Posted: June 13, 2011 16:51 by Joseph Pallas
|
|
It turns out the problem I was having was not due to the files being different (although two of the files apparently are: com/sun/btrace/agent/Client.class and com/sun/btrace/runtime/ClassFilter.class). The problem was actually because of the filename: the maven artifacts have the version number in the name of the jar. So the manifest specifies Boot-Class-Path: btrace-boot.jar while the jar file in the maven repository is actually named btrace-boot-1.2.jar. I don't really know anything about how agents work, nor have I ever used bootclasspath. I was just copying what the btracer script does. In this case, instead of getting some useful error message about a problem with the bootclasspath, I got a security exception from a call to getUnsafe(). That didn't really point me in the right direction, as you can imagine. Once I understood the problem, I was able to use -Xbootclasspath/a:btrace-boot-1.2.jar in my script to make things work. So, I guess a case could be made that the maven version should be different: the filename in the Boot-Class-Path entry of the agent manifest ought to reflect the filename in the repository. joe |
showing 1 - 8 of 8
Replies: 7 - Last Post: June 13, 2011 16:51
by: Joseph Pallas
by: Joseph Pallas
