<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Martin,<br>
<br>
Right now, the latest tag in the repo should be jtreg4.1-b08. It
seems to be it would be good if your build could reflect that.
There should be enough hooks in the build script to allow you to
set the version.<br>
<br>
-- Jon<br>
<br>
On 01/20/2014 09:54 AM, Martijn Verburg wrote:<br>
</div>
<blockquote
cite="mid:CAP7YuASGQtyyQf=iD5z8e01AMz_k2NN=kUBhCB14SkaAa3A8rw@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Jonathan,
<div><br>
</div>
<div>Thanks for the info. In that case I'll change the build to
produce a 4.2.0-SNAPSHOT following the traditional model. I
guess we can then work on the build script to allow it to
produce formal releases (such as 4.2.0) to Maven central.</div>
<div><br>
</div>
<div>I don't have permission to raise an issue directly in JBUG
for this, are you able to or does it still need to go through
the bugs.sun... method?</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra">
<br clear="all">
<div>Cheers,<br>
Martijn</div>
<br>
<br>
<div class="gmail_quote">On 20 January 2014 17:47, Jonathan
Gibbons <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jonathan.gibbons@oracle.com" target="_blank">jonathan.gibbons@oracle.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 01/18/2014 05:29 AM, Martijn Verburg wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
<a moz-do-not-send="true"
href="https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/"
target="_blank">https://adopt-openjdk.ci.cloudbees.com/job/jtreg/lastSuccessfulBuild/artifact/</a>
now produces a Maven compatible 5.0.0-SNAPSHOT version of
jtreg.<br>
<br>
This was to make the download and install for the Virtual
Machines we're producing for the build-farm as well as
making jtreg Maven repo compatible.<br>
<br>
IIRC jtreg was last released as version 4.3? Hopefully
5.0.0 is the next logical number.<br>
<br>
Probably needs a conversation about how to deal with
versioning and if jtreg can be uploaded to Maven Central
or not (any legal barriers?).<br>
<br>
Cheers,<br>
Martijn<br>
</blockquote>
<br>
Martijn,<br>
<br>
jtreg has never been 4.3. I think you're confusing it with
the version of JTHarness that it uses.<br>
<br>
For a while now, jtreg has been using jtreg 4.1 bNN where NN
is a small interger, currently 08. This was more significant
when we (Oracle) were producing binary builds. Now that we
are no longer doing that, I think we will start advancing
the jtreg number in a more conventional fashion.<br>
<br>
I had hoped to combine the advance to 4.2 with a major
update to the jtreg documentation, but that seems to be
never quite high enough priority to have anything happen :-(<br>
<br>
-- Jon<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>