Hi,
I created the wicketstuff-parent to host shared configuration (like some
dependencies, distribution configuration, build, reporting,...)
I use it with several wicketstuff project : wickectstuff-misc,
wicketstuf-jquery,...
You're free to use/update/complete it (it was created to this purpose: help
other wicketstuff project.
When you use it, you could override
* the license, scm section
* the properties use to define version of depencencies and compiled class
* "wicket.version" (I'll update the pom to use 1.3.1 as default).
* "java.src.version"
* "slf4j.version"
Regards
/davidB
Maurice Marrink wrote:
> Actually there is a wicketstuff parent pom, however it is not required
> that you extend it.
>
> Maurice
>
> On Tue, Feb 26, 2008 at 10:40 AM, Nino Saturnino Martinez Vazquez Wael
> <[EMAIL PROTECTED]> wrote:
>> As a wicketstuff only im not sure how much my sayings count. But i'l
>> tell how I feel anyways:)
>>
>>
>> lars vonk wrote:
>> > 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?
>> >
>> A good question, theres a little difference between naming the projects,
>> some use wicket-contrib-projectname others wicketstuff-projectname.
>>
>> I thin all uses package names like this : org.wicketstuff
>>
>>> - Is there a master pom that I should extend? Or are there Maven
>> > standards used, e.g. reports and stuff?
>> >
>> I dont think we have a wicketstuff parent pom, but some of us use this
>> wicket parent pom:
>>
>> <parent>
>> <groupId>org.apache.wicket</groupId>
>> <artifactId>wicket-jdk15</artifactId>
>> <version>1.3.0</version>
>> <relativePath>../pom.xml</relativePath>
>> </parent>
>>
>>> - Is it okay if I only create it for Java 5, or should I also support Java
4?
>> >
>> >
>> I think you should do what's most productive for you, and then you can
>> always decide if you want to support java 1.4... Etc..
>>
>>> 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.
>> >
>> >
>> Sounds like the way to go..
>>
>>> 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?
>> >
>> >
>> You configure individuals in bamboo, but there are no mail server setup
>> for it...
>>
>>> 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
>> >>
>> >>
>> >>
>> >
>> >
>> >
>>
>> --
>>
>>
>> Nino Martinez Wael
>> Java Specialist @ Jayway DK
>> http://www.jayway.dk
>> +45 2936 7684
>>
>>
