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]>
> 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
