Thanks, I have some question on how to proceed: - I am thinking about creating a seperate project, if that's okay. - Are there any naming / coding conventions used? - Is there a master pom that I should extend? Or are there Maven standards used, e.g. reports and stuff? - Is it okay if I only create it for Java 5, or should I also support Java 4?
JAMon has a default admin jsp's available, but I am thinking about replacing those with the Wicket way, so just normal html with Java. Nino, if the project skeleton is there I'll let this list know so it can be setup in bamboo. Do the build emails go to a seperate mailing list, or do you just configure the individuals in bamboo? Lars On Tue, Feb 26, 2008 at 9:01 AM, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]> wrote: > Hi Lars > > its also possible setting your future project up with bamboo, so that it > will be built into the wicketstuff for the wicketstuff maven repo. > Getting rights for bamboo also happens here.. > > > regards Nino > > > > lars vonk wrote: > > Hello, > > > > I would like to contribute JAMon monitoring in Wicket I have build for > > my current project to the wicketstuff project. > > According to > http://wicketstuff.org/confluence/display/STUFFWEB/Home#Home-HowdoIapplyforSubversioncommitaccess%3F > > I need to apply for commit rights here. What would be the next step? > > > > Thanks in advance, > > > > Lars Vonk > > > > > > > > -- > Nino Martinez Wael > Java Specialist @ Jayway DK > http://www.jayway.dk > +45 2936 7684 > >
