No, I never resolved that problem, which was one reason the effort stalled.

On Wed, Sep 22, 2010 at 4:45 PM, Nikolaos Giannopoulos <
[email protected]> wrote:

> Soren,
>
> I take it you use a Mac like me.  This has come up before and here is
> some lengthy discussion and solution options:
>
> http://www.mail-archive.com/[email protected]/msg03858.html
>
> Ben - I thought you had resolved this in the 1.5.x trunk?????
> Unfortunately I can't find any e-mail reply... .
>
> --Nikolaos
>
>
>
> Soren Pedersen wrote:
> > Hi Remi
> >
> > Thanks a lot! It really helps me out.
> >
> > I had the following issue when I ran mvn clean install from project root:
> >
> >
> > stripes\src\net\sourceforge\stripes\tools\SiteStructureTool.java:[20,33]
> > package com.sun.mirror.declaration does not exist
> >
> > I solved it by adding the following dependency to the parent pom:
> >
> >         <dependency>
> >           <groupId>com.sun</groupId>
> >           <artifactId>tools</artifactId>
> >           <version>1.4.2</version>
> >           <scope>system</scope>
> >           <systemPath>${java.home}/../lib/tools.jar</systemPath>
> >         </dependency>
> >
> > Can this be included?
> >
> > I also have an issue with the cargo plugin which I assume is due to a
> > missing plugin repository.  I'll look at it tomorrow.
> >
> > Thanks for a good job :)
> >
> > Regards
> >
> > Søren
> >
> > Den 22/09/2010 kl. 13.24 skrev VANKEISBELCK Remi <[email protected]
> > <mailto:[email protected]>>:
> >
> >> Hi again,
> >>
> >> Ok, now I have almost everything working just like in the ant build.
> >> There's only a small glitch with the tlddocs, but I guess we can live
> >> with that for the moment.
> >>
> >> Ben, could you provide me with the sonatype infos ? I've done some
> >> tests locally with nexus, and it seems to work. Building the full
> >> thing (mvn clean deploy -Prelease) deploys the following artifacts to
> >> the target repo :
> >> * stripes-parent (parent pom)
> >> * stripes (jar)
> >> * stripes-javadocs (jar)
> >> * stripes-src (jar)
> >> * stripes-tlddoc (jar)
> >>
> >> Now if the sonatype repo syncs automatically to central, I think
> >> we're done (or almost).
> >>
> >> Cheers
> >>
> >> Remi
> >>
> >>
> >> 2010/9/22 VANKEISBELCK Remi <[email protected] <mailto:[email protected]>>
> >>
> >>     Hi folks,
> >>
> >>     I have started to mavenize the build on 1.5.x, so that we can
> >>     easier deploy to sonatype and sync with the central repo.
> >>     No worries, I'm not breaking the ant build, you can still
> >>     compile/test/package with ant as before.
> >>     Well, almost : I had to changethe existing pom.xml in stripes/.
> >>     It was use to create the pseudo bundle for maven, so I guess it's
> >>     no big deal for the moment.
> >>
> >>     I thought it would be a piece of cake but the ant build does a
> >>     bit more than a few javacs, so I had to fight a little bit with
> >>     maven plugins (antrun and the like).
> >>
> >>     Anyway, it's a multi module project with the following structure :
> >>     * stripes-parent (dep factorization etc)
> >>       * stripes (core classes, tld)
> >>       * tests (test cases + runner)
> >>       * examples (examples webapp)
> >>
> >>     (I had to do this test module because I didn't want to break the
> >>     ant build. Otherwise it's quite regular.)
> >>
> >>     Which means that running "mvn clean install" in the top-level
> >>     folder will compile, test, package and install the stripes jar as
> >>     well as the examples app in your local repo.
> >>
> >>     Btw, there are test failures, the same than in the ant build.
> >>     I've struggled a little bit to have the exact same tests results
> >>     in ant and maven, because of test cases that have non
> >>     conventional names etc, but in the end, the results of a test run
> >>     are the same (same # of tests and failures).
> >>     This means that for now if you want to build you need to pass
> >>     "-Dmaven.test.skip" to your command line build.
> >>
> >>     To test that everything works fine, you can use the cargo plugin
> >>     in the examples :
> >>     > cd examples/
> >>     > mvn cargo:start -Dtomcat6.home=<path_to_local_tomcat_home>
> >>     (I have the tomcat home in my ~/.m2/settings.xml, but this is up
> >>     to you)
> >>
> >>     This will deploy the examples in your tomcat and start it. Then
> >>     the examples are available at
> >>     http://localhost:8080/stripes-examples
> >>
> >>     The TODO list :
> >>     * Fine-tune stripes manifest (versions etc)
> >>     * Javadoc/tlddoc (I haven't tested it but with tlddoc I doubt
> >>     it's gonna work by magic)
> >>     * Source copy in bugzooky (this "see the source code" feature is
> >>     a build nightmare :P)
> >>     * deploy plugin configuration (I need the sonatype url and
> >>     credentials in order to do this)
> >>     * ?
> >>
> >>     It's a first shot, so don't hesitate to try it out and report any
> >>     issue. It's commited, in branch 1.5.x, rev 1259.
> >>
> >>     Cheers
> >>
> >>     Remi
> >>
>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to