Now this is implemented through maven-antrun-plugin and profile which is
activated by presence of requirements.properties file, that references
by name requirements defined in requirements component. All ant scripts
were ported form our PDE based build.
Now I think maven dependencies mechanism can be used for that.
What wee need here are:
1. Maven repository with all dependencies in it: JBoss AS, Seam and etc.
It could be couple repos for community projects and products, first can
be available everywhere, second only on hudson or through VPN.
2. Then integration tests would use dependency declaration and unpack
goal to get it from repo and prepare for integration tests.
It still might require ant but only for configuration, for example to
install rifsaw on JBossTools during preparation for integration tests.
It just an idea, WDYT?
Denis
On 07/28/2010 05:16 AM, Snjezana Peco wrote:
Hi,
I have been working on Maven and Portal tests and would appreciate if
you could give me with some info.
How is Seam 2.2.0.GA defined?
I can find jbosstools.test.seam.2.0.1.GA.home for Seam 2.0.1.GA, but
can't find Seam 2.2.
I would also need definition for EAP 5.0, EAP 5.1, EPP 5.0, EPP 4.3,
JBoss AS 5.1 with GateIn, JBoss AS 5.1 with GateIn Portlet Container,
JBoss Portrlet Bridge 2.0.0 FINAL.
GateIn can be downloaded from
https://www.jboss.org/gatein/downloads.html
GateIn Portlet Container can be downloaded from
http://www.jboss.org/gatein/portletcontainer/downloads.html
JBoss Portlet Bridge from
http://www.jboss.org/portletbridge/downloads.html
Thanks,
Snjeza