While compiling the geronimo-kernel module, do you run it with "mvn install", so that the geronimo-kernel jar file could be installed to the local repository. Or geronimo-boilerplate module could not package the latest jar file. Wish it helps !
2009/10/11 Quintin Beukes <[email protected]> > I eventually settled on copying the geronimo-kernel JAR to an > extracted assembly. > > When I check the boilerplate/target/contents/lib/geronimo-kernel JAR, > it DOES have my code, in fact, that's the one I copied into my > extracted assembly. > > But I looked throughout the documentation, and tried reading the POMs > but can't find a way to build it other than a complete "mvn clean > install", which takes ages. > > I also tried doing a a -Dstage=assembly, which didn't help either. > > Would still like to know of a way to construct a clean assembly after > making change to the kernel. > > Quintin Beukes > > > > On Sun, Oct 11, 2009 at 1:25 PM, Quintin Beukes <[email protected]> > wrote: > > I'm doing something wrong, or there is another step. > > > > I rebuild the boilerplate config, and check in it's target/ directory > > inside the boilerplate car archive. My changed class is there, with > > the changes. > > > > Then I "cd {buildroot}/assemblies/geronimo-jetty7-javaee" and do "mvn > > install". It builds the assembly, but the ZIP it builds doesn't > > contain the boilerplate I just build. > > > > Quintin Beukes > > > > > > > > On Fri, Oct 9, 2009 at 7:06 PM, David Jencks <[email protected]> > wrote: > >> > >> On Oct 9, 2009, at 7:55 AM, Quintin Beukes wrote: > >> > >>> Hey, > >>> > >>> Assume I change a .java file in the framework/modules/geronimo-kernel > >>> project, how can I easily only build what was changed and reassemble > >>> the zip for installing+running? > >> > >> There a few modules that are not put into the geronimo repository > structure > >> -- geronimo-kernel, geronimo-system, and a few others. For these you > have > >> to rebuild the framework/configs/geronimo-boilerplate config before > >> rebuilding the assembly you want. > >> > >> Also, if you change anything related to a GBeanInfo -- for instance > >> attributes, operations, constructor parameters -- you have to rebuild > any > >> configs that might use that gbean. > >> > >> Otherwise, if you change code you can just rebuild the module and > rebuild > >> the assembly. Or, if you want to live dangerously, you can just copy > the > >> new jar over the old one in the geronimo repo. > >> > >> thanks > >> david jencks > >> > >>> > >>> Quintin Beukes > >> > >> > > > -- Ivan
