This is the use case which Maven enables especially well, no? ie, update code in container, build it, and then test the impact in AOP. The jars from container are integrated into the AOP build using Maven's local repository. There is no "update the repository step" since it is part of the default build cycle.
-----Original Message----- From: Scott M Stark Sent: Tuesday, May 02, 2006 11:54 AM To: Adrian Brock Cc: Ryan Campbell; QA; jboss-development@lists.sourceforge.net Subject: RE: jboss-head-jdk-matrix Build Failed We have to bootstrap the repository with a snapshot version. This can be a local jbossbuild repository override to avoid having to synch through cvs and then out to the webserver. It's the same problem we will face when developing multiple maven projects with inter-dependencies. Maven just has a natural mechanism for bootstrapping its repository by following the dependency and building the projects as needed by adding a parent project. > -----Original Message----- > From: Adrian Brock > Sent: Tuesday, May 02, 2006 9:31 AM > To: Scott M Stark > Cc: Adrian Brock; Ryan Campbell; QA; > jboss-development@lists.sourceforge.net > Subject: RE: jboss-head-jdk-matrix Build Failed > > The first problem I've come across is that AOP is using the > "container" > project for the metadata repository interfaces. > > There is no binary release of this yet, since it is still > being developed. > > So how doable is this while we are still working on the > AOP/MC integration with still unstable apis? ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
