Well, there is some example code within the project. And I believe it was
enough to get me started. But beyond that, no I don't think you'll find
anymore docs on it. If you run into trouble, I'll do my best to help since
it seems to be working in my project.
<dependency>
<groupId>org.wicketstuff</groupId>
<artifactId>wicket-contrib-jasperreports</artifactId>
<version>1.4.10-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>jasperreports</groupId>
<artifactId>jasperreports</artifactId>
</exclusion>
<exclusion>
<artifactId>servlet-api</artifactId>
<groupId>javax.servlet</groupId>
</exclusion>
</exclusions>
</dependency>
I exclude jasperreports because I include a specific version and I didn't
want the conflict. I exclude servlet-api because that is provided.
On Wed, Jun 9, 2010 at 10:53 AM, Steven Haines <lyg...@yahoo.com> wrote:
> We're just about to start integrating Jasper with our wicket application
> (with a due date by the end of the week), so I found your positing
> particularly timely!
>
> Do you have any sample code and/or configuration information that shows me
> how to integrate wicket-contrib-jasperreports into my application (Maven)?
>
> Thanks!
> Steve
>
>
>
>
>
> ----- Original Message ----
> From: Michael O'Cleirigh <michael.ocleir...@rivulet.ca>
> To: users@wicket.apache.org
> Sent: Tue, June 8, 2010 9:05:07 AM
> Subject: Re: [wicketstuff/wicket-contrib-jasperpreports] Is anyone
> supporting this?
>
> Hi Charles,
>
> As long as wicketstuff-core builds locally with
> wicket-contrib-jasperreports in the core pom (as a module) you can
> commit the core pom.
>
> I have a hudson instance running that will build and auto deploy into
> the sonatype snapshot repository a 1.4.10-SNAPSHOT version of your
> artifacts.
>
> For an internal work release I need to cut a 1.4.9.1 wicketstuff-core
> release this week. If your changes work in trunk you can backport them
> to the wicket 1.4.9 branch and when I cut the release they will be
> included and deployed into the central maven repository.
>
> Regards,
>
> Mike
>
>
> > Awesome. Thanks.
> >
> > I pushed up my initial set of changes. wicket-contrib-jasperreports now
> > builds as 1.4.10-SNAPSHOT using wicketstuff-core.
> >
> > However, I have not added it to the wicketstuff-core build. I'll try to
> get
> > on that shortly, at least it is no worse off than it was before and now
> at
> > least it building closer to the newer wicketstuff projects.
> >
> > Next up would be actual enhancements to the code. Rodolfo mentioned some
> > additions and I have to refactor some of my code that I wrote as a
> > workaround so that it can be pushed back as well.
> >
> > Thanks for your help! That's one less project that I have to maintain a
> > customized instance of!
> >
> > On Mon, Jun 7, 2010 at 6:05 PM, nino martinez wael<
> > nino.martinez.w...@gmail.com> wrote:
> >
> >
> >> youve been added.
> >>
> >> As for the requirement with core, I think you just need to add the
> >> project to the pom on core, I'd suggest looking at one of the projects
> >> thats already in there (so you can copy and paste)..
> >>
> >> regards Nino
> >>
> >> 2010/6/7 Charles Deal<chuckdea...@gmail.com>:
> >>
> >>> Excellent. sf username: cdeal
> >>>
> >>> First things first then. If I get some patches put into scm other
> people
> >>> will see that it is still a viable project. Then as I get time, I'll
> >>> extract some of my code into some kind of example.
> >>>
> >>> What are the requirements for building with core and who do I contact
> to
> >>>
> >> get
> >>
> >>> this included in the core build process?
> >>>
> >>> On Thu, Jun 3, 2010 at 5:24 PM, nino martinez wael<
> >>> nino.martinez.w...@gmail.com> wrote:
> >>>
> >>>
> >>>> go for commit rights. And for requirements it would be good to have an
> >>>> example project other than that it should just be working :)
> >>>>
> >>>>
> >>>>
> >>>> 2010/6/3 Charles Deal<chuckdea...@gmail.com>:
> >>>>
> >>>>> Is anyone out there maintaining/using this library?
> >>>>>
> >>>>> I am using it and I have a handful of modifications that I'd like to
> >>>>>
> >> push
> >>
> >>>>> back into the source tree. Should I prepare a patch and JIRA issue
> or
> >>>>>
> >>>> shall
> >>>>
> >>>>> I pursue commit access for this library?
> >>>>>
> >>>>> I would also like to get it hooked into the build process. It seems
> >>>>>
> >> like
> >>
> >>>> I
> >>>>
> >>>>> only need to add the wicketstuff-core reference to this pom and have
> >>>>>
> >> the
> >>
> >>>>> wicketstuff-core pom updated to include this module. What else
> needs
> >>>>>
> >> to
> >>
> >>>> be
> >>>>
> >>>>> done? Are there specific requirements for a library to be part of
> the
> >>>>> wicketstuff-core build?
> >>>>>
> >>>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>>> For additional commands, e-mail: users-h...@wicket.apache.org
> >>>>
> >>>>
> >>>>
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
