2:11 p.m.
Hi all,
I wanted to play with the BV TCK. I've downloaded it, read the instruction,
but the code doesn't compile because of these two dependencies :
<dependency>
<groupId>org.jboss.test-audit</groupId>
<artifactId>jboss-test-audit-api</artifactId>
<version>${jboss.test.audit.version}</version>
</dependency>
<dependency>
<groupId>org.jboss.test-audit</groupId>
<artifactId>jboss-test-audit-impl</artifactId>
<version>${jboss.test.audit.version}</version>
</dependency>
In the pom.xml there are two repositories :
* https://repository.jboss.org/nexus/content/repositories/snapshots/
Nothing in there
* https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/
Needs a user/pwd
I crawled the Maven central but couldn't find anything.
Do you know which repository I should add to have all
the org.jboss.test-audit artifacts ?
Thanks
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org/> |
Twitter<http://twitter.com/agoncal>
| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org/>
| Devoxx France <http://www.devoxx.fr/>
4:53 p.m.
Hi Antonio,
Cool that you're interested in the TCK :)
The mentioned artifacts are in the public JBoss Maven repository [1]. More
information on using that repo can be found at [2]. Note that the TCK has
no new tests for Bean Validation 1.1 yet, we're in the process of adding
these atm.
Besides adding tests we're also considering to generate the audit file used
in the TCK coverage report [3] from the actual spec text [4]. That way the
assertions in the TCK exactly resemble the spec and it also gets very easy
to see which parts of the spec are covered how well by the TCK.
Let us know in case you have any further questions or suggestions, want to
contribute etc.
Happy Christmas,
--Gunnar
[1] https://repository.jboss.org/nexus/content/groups/public-jboss
[2] https://community.jboss.org/wiki/MavenGettingStarted-Users
[3]
http://docs.jboss.org/hibernate/beanvalidation/tck/1.0/reference/html_sin...
[4] https://hibernate.onjira.com/browse/BVAL-349
2012/12/23 Antonio Goncalves <antonio.mailing(a)gmail.com>
Hi all,
I wanted to play with the BV TCK. I've downloaded it, read the
instruction, but the code doesn't compile because of these two dependencies
:
<dependency>
<groupId>org.jboss.test-audit</groupId>
<artifactId>jboss-test-audit-api</artifactId>
<version>${jboss.test.audit.version}</version>
</dependency>
<dependency>
<groupId>org.jboss.test-audit</groupId>
<artifactId>jboss-test-audit-impl</artifactId>
<version>${jboss.test.audit.version}</version>
</dependency>
In the pom.xml there are two repositories :
* https://repository.jboss.org/nexus/content/repositories/snapshots/
Nothing in there
* https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/
Needs a user/pwd
I crawled the Maven central but couldn't find anything.
Do you know which repository I should add to have all
the org.jboss.test-audit artifacts ?
Thanks
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org/> |
Twitter<http://twitter.com/agoncal>
| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org/>
| Devoxx France <http://www.devoxx.fr/>
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
6:37 p.m.
Thanks, just by adding the following repository in the pom.xml works. You
might want to add it to the pom as not everybody declares JBoss Repo in
their settings.xml
<repositories>
<repository>
<id>jboss-public-repository</id>
<name>JBoss Public Repository</name>
<url>https://repository.jboss.org/nexus/content/groups/public-jboss/
</url>
</repository>
</repositories>
Thanks again
2012/12/23 Gunnar Morling <gunnar(a)hibernate.org>
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org/> |
Twitter<http://twitter.com/agoncal>
| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org/>
| Devoxx France <http://www.devoxx.fr/>
7:25 p.m.
Hi Antonio,
It's an ongoing debate whether it's good to put repo information into POMs
or not, see e.g. [1]. The major problem is that users of such a pom.xml as
dependency will get that repo pulled into their own build, which might not
be what they want.
Now I guess there won't be many people using the TCK as dependency, but I
still think it's saver to leave the repo info out of the POM and have users
add it to their settings.xml. With the BV reference implementation we
provide an examplary settings.xml which can be used for building: mvn clean
install -s settings-example.xml. I've created a ticket for the TCK to do
the same [2].
Thanks again for your feedback,
--Gunnar
[1]
http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-p...
[2] https://hibernate.onjira.com/browse/BVTCK-30
2012/12/23 Antonio Goncalves <antonio.mailing(a)gmail.com>
Thanks, just by adding the following repository in the pom.xml works.
You
might want to add it to the pom as not everybody declares JBoss Repo in
their settings.xml
<repositories>
<repository>
<id>jboss-public-repository</id>
<name>JBoss Public Repository</name>
<url>https://repository.jboss.org/nexus/content/groups/public-jboss/
</url>
</repository>
</repositories>
Thanks again
2012/12/23 Gunnar Morling <gunnar(a)hibernate.org>
> https://community.jboss.org/wiki/MavenGettingStarted-Users
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org/> |
Twitter<http://twitter.com/agoncal>
| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org/>
| Devoxx France <http://www.devoxx.fr/>
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
4150
days inactive
4150
days old
beanvalidation-dev@lists.jboss.org
3 comments
2 participants
participants (2)
-
Antonio Goncalves -
Gunnar Morling