For the Bean Validation TCK, I compared the content that gets downloaded
from the JBoss maven repo to the 1.0.3 content provided from Oracle and
they were identical. Not sure what that means for final JEE6
certification, but I don't see how they can tell from the logs which set
of artifacts were
The BVAL and JCDI builds have now been updated to allow extracting
Geronimo assemblies into the target directory for automated testing.
mvn test -Pincontainer,geronimo-assembly -DassemblyId=tomcat7-javaee6
Note, that the assemblyIds are different from the ones defined in the
parent server POM,
On Jul 21, 2010, at 12:04 AM, Jarek Gawor wrote:
Ok, it sounds like more people prefer to move these tcks into a public
svn location.
So I guess we should create a
https://svn.apache.org/repos/asf/geronimo/tck repo and move the tcks
over. There should be no problem with moving the
On Jul 21, 2010, at 12:04 AM, Jarek Gawor wrote:
Ok, it sounds like more people prefer to move these tcks into a public
svn location.
So I guess we should create a
https://svn.apache.org/repos/asf/geronimo/tck repo and move the tcks
over. There should be no problem with moving the
On 7/21/10 12:04 AM, Jarek Gawor wrote:
Ok, it sounds like more people prefer to move these tcks into a public
svn location.
So I guess we should create a
https://svn.apache.org/repos/asf/geronimo/tck repo and move the tcks
over. There should be no problem with moving the following
porting modules live. The JCDI and Bean Validation TCKs are public Apache
licensed, so we could move the porting modules for those two TCKs into our
public svn.
The part of my brain that finds esthetic pleasure in filling cabinets likes
everything all organized in the one VM
On Jul 20, 2010, at 3:05 AM, David Jencks wrote:
On Jul 19, 2010, at 10:37 PM, Jarek Gawor wrote:
My main concern is that if we move the JCDI and Bean Validation
porting code to public svn location then we will effectively have two
mailing lists for discussing tck issues, two jira places
Ok, it sounds like more people prefer to move these tcks into a public
svn location.
So I guess we should create a
https://svn.apache.org/repos/asf/geronimo/tck repo and move the tcks
over. There should be no problem with moving the following modules
(since it's all Apache licensed stuff):
1)
Currently we have these setup in the private svn where the Java EE TCK porting
modules live. The JCDI and Bean Validation TCKs are public Apache licensed, so
we could move the porting modules for those two TCKs into our public svn.
The part of my brain that finds esthetic pleasure in filling
AM, David Blevins david.blev...@visi.com wrote:
Currently we have these setup in the private svn where the Java EE TCK
porting modules live. The JCDI and Bean Validation TCKs are public Apache
licensed, so we could move the porting modules for those two TCKs into our
public svn.
The part
10 matches
Mail list logo
