My thanks to the committers for the continuous bug fixes and new features!

On 09/10/2017 17:24, Jonathan Gallimore wrote:
That's awesome, thank you for the feedback so far!

Jon

On Mon, Oct 9, 2017 at 4:22 PM, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk> wrote:

Hi Jon,

That is good as I wanted to test the 7.0.4 with my development setup.  So
I downloaded the apache-tomee-7.0.4-plus.tar.gz and i am running it on my
local machine in place of 7.0.3.

It has started up fine and no problems so far.  I will just keep working
and report back if there are any issues

Matthew


On 09/10/2017 17:14, Jonathan Gallimore wrote:

Hi

That's the staging repo for the vote - if the vote passes, its those
binaries that will be promoted as version 7.0.4. Snapshots won't be
deployed here (they'll go to here:
https://repository.apache.org/content/groups/snapshots/ I believe). I
think
there is an issue with the buildbot job that deploys these, so if you're
waiting on a snapshot, let us know and I can deploy one manually.

Jon

On Mon, Oct 9, 2017 at 4:07 PM, Matthew Broadhead <
matthew.broadh...@nbmlaw.co.uk> wrote:

are the dist builds still at https://dist.apache.org/repos/
dist/dev/tomee/staging-1107/tomee-7.0.4/?


On 09/10/2017 14:58, Mark Struberg wrote:

Hi folks!
Sorry for the delay!
Running the new 7.0.4 attempt with a few customer projects now.
Will ping back once I know more.

txs and LieGrue,
strub

Am 08.10.2017 um 16:43 schrieb Romain Manni-Bucau <
rmannibu...@gmail.com

:
It is http://repository.apache.org/snapshots/
(openejb.deployer.snapshot.repository
system property) but there is not yet a 8 snapshot


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <
https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>

2017-10-08 16:26 GMT+02:00 Alex The Rocker <alex.m3...@gmail.com>:

Hi Romain,

But how to find the repo for TomEE 8.0.0 based testing?

Best regards,
Alexandre


2017-10-08 16:20 GMT+02:00 Romain Manni-Bucau <rmannibu...@gmail.com
:
Hi Alex,
you can set as system property (through surefire)
openejb.deployer.repository=<the
repo>


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/

rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>
2017-10-08 14:07 GMT+02:00 Alex The Rocker <alex.m3...@gmail.com>:

Hi Romain,

Thank you very much for your answer:I  was able to run my Arquilian
test by adding the following line into my projet's pom.xml:

      <repositories>
          <repository>
              <id>my-tomee704repo</id>
              <name>TomEE704 repo</name>
              <url>https://repository.apache.org/content/
repositories/orgapachetomee-1107/</url>
          </repository>
      </repositories>

(and by the way my feedback on TomEE 7.0.4 is still +1)

Question: in the general case, how one can tell which is the
appropriate repository URL to use Arquilian which a TomEE+ version
which isn't yet officialized?

For example, if I want to try TomEE+ 8.0.0, the above repository
does't allow to resolve dependencies on:
                  <dependency>
                      <groupId>org.apache.tomee</groupId>
                      <artifactId>arquillian-tomee-e
mbedded</artifactId>
                      <version>8.0.0</version> <!--Current version
-->
                  </dependency>

So what's the "rule of thumb"? (and can it be documented somewhere
on
tomee.apache.org?)

Best regards,
Alexandre



2017-10-08 10:51 GMT+02:00 Romain Manni-Bucau <
rmannibu...@gmail.com

:
@Alex: did you add this repo https://repository.apache.org/
content/repositories/orgapachetomee-1107/ ?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/

rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>
2017-10-08 10:48 GMT+02:00 Alex The Rocker <alex.m3...@gmail.com>:

Hello,

I am starting to use Arquilian, in particular in order to check
the
impact of TomEE+ version changes on our REST services (annotations
sometimes change, such as the introduction of @JohnzonIgnore in
TomEE
+ 7.x).

I naively tried changing my dependency from 7.0.3 to 7.0.4, but
it's
not being resolved:
                  <dependency>
                      <groupId>org.apache.tomee</groupId>
                      <artifactId>arquillian-tomee-

embedded</artifactId>
                      <version>7.0.4</version> <!--Current version
-->

                  </dependency>
I guess that this is because TomEE 7.0.4 isn't yet officialized.

But yet, I fell that it would be great if I could use the current
TomEE+ 7.0.4 release candidate with Arqulian in order to give

feedback
on this RC before it's final.
What would be the simplest way to setup my pom.xml in order to run
my
Arquilan tests using latest TomEE+ 7.0.4 release candidate, *using

the
embedded adapter* ?
(I guess that using the remote adapter with the RC I downloaded is
an
alternative, but yet I want also the use embedded version).

Best regards,
Alexandre


2017-10-05 19:29 GMT+02:00 Alex The Rocker <alex.m3...@gmail.com
:
Hello Andy,
And thank you very much for your answer. I already voted a +1

based on
my applicative tests which showed no regressions of this TomEE+
7.0.4
vs. TomEE+ 7.0.3.
I can wait for a week for the "final freeze" :)
Best regards,
Alexandre


2017-10-05 19:25 GMT+02:00 Andy Gumbrecht <andy...@gmx.de>:

The vote is open for 'at least' 72 hours, or until we get 3+
binding
votes.
I know that many of the guys are ultra busy with JavaOne at the
moment,

so I
don't expect to get a response until next week.
The review process is basically downloading the binaries and

checking
them
for complete functionality. That includes running apps and testing
everything possible, including the legal headers etc. This
always

takes
time, but we do it to ensure you get a good distribution.
Thanks for your understanding. We still really appreciate your
help
and
votes, which should mean that you have just as thoroughly tested
all
your
environments. The more eyes on, the better!
Andy Gumbrecht.

I'm adding my binding vote, as I have not found any issues:

+1



On 04/10/17 00:42, Alex The Rocker wrote:

Hello Andy
Would you please specific until when this vote for TomEE+ 7.0.4

is
supposed to last?
Best regards,
Alex

2017-09-28 13:37 GMT+02:00 Felipe Jaekel <fkjae...@gmail.com>:

+1
2017-09-26 18:24 GMT-03:00 Andy Gumbrecht <

agumbre...@tomitribe.com>:
Hi Everyone,
I'd kindly like to ask you all to take a look at this build and
place
your
votes for a 7.0.4 release.
The re-roll updates to CXF 3.1.13 and JAXB 2.3.0 (Provided).

I added comments in the previous vote that relate to Java 9,

which is
experimental and requires the following (corrected) flag:
--add-module java.xml.bind

Staging repo:
https://repository.apache.org/content/repositories/

orgapachetomee-1107/
Source zip:
https://repository.apache.org/content/repositories/orgapache
tomee-1107/org/apache/tomee/tomee-project/7.0.4/tomee-
project-7.0.4-source-release.zip

Dist area:
https://dist.apache.org/repos/dist/dev/tomee/staging-1107/

tomee-7.0.4/
Legal:
https://dist.apache.org/repos/dist/dev/tomee/staging-1107/to
mee-7.0.4/legal.zip

Keys:
https://dist.apache.org/repos/dist/release/tomee/KEYS

Changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
ctId=12312320&version=12339959

Green buildbot:
https://ci.apache.org/builders/tomee-trunk-ubuntu-

jvm8/builds/725
https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/839
The RAT report indicates 0 Unknown Licenses.
Please vote:
    +1: Release
    -1 Do not release because ... See below.

If you vote -1 then please create a JIRA ticket here:
https://issues.apache.org/jira/projects/TOMEE - Include as

much
information as possible and, if applicable, a unit test.
The vote will be open for 3 days or the consensus is binding
(At
least 3
binding votes).
Everyone, committer or not, is encouraged to test and vote.
Thank
you
very
much for your time.
Andy Gumbrecht.





Reply via email to