Allright, let's go then : I'll push 1.5.3 to sonatype and open a ticket so
that they sync automatically.
On minor issue : I already pushed 1.5.4-SNAPSHOT in order to test the build.
I don't know if it's usable in Stripes app, but as you said it wasn't
stable, I guess it's not ! Otoh, it's a SNAPSHOT release so it's not really
a major issue. SNAPSHOTs are broken sometimes, if you don't like it, then
use RELEASE versions :P
Continuous Integration : it's basically about triggering builds when a
commit is made. The C.I. tool scans the repo, checkouts if it finds some
changes, and runs a build. It usually sends emails when builds fail, and
many reports.
The C.I. tool can run any build, it basically kicks a command, so it could
be ant or maven.
The advantage with maven is that when the build passes (no compile/test
failures), the artifacts can be deployed automatically to some repo
(sonatype) and made avilable to users directly.
One main thing to notice : C.I. is good when trunk is "stable". If the build
always fail, then C.I. is of no use. Otherwise it's really a good practice.
We heavily use it at work, and honestly I couldn't do without now.
For big projects, with inter-team dependencies, it's really a must have.
For us in Stripes, it would avoid the burden of pushing the snapshots, ands
provide a good indicator that the build has been broken.
I'll try to setup something so that you can see how it works.
Cheers
Remi
2010/9/23 Ben Gunter <[email protected]>
> It'd be fine with me if you want to release 1.5.3 that way. I was thinking
> that would probably be a good idea. As for your question about continuous
> integration, we have nothing of the sort set up, and I don't know anything
> about all that.
>
>
> On Thu, Sep 23, 2010 at 9:36 AM, VANKEISBELCK Remi <[email protected]> wrote:
>
>> Should work on OSX and all Sun JDK platforms.
>>
>> Ben, I see people pushing for a 1.5.3 central release in jira :
>> http://www.stripesframework.org/jira/browse/STS-738
>>
>> I know you prefer to wait for 1.5.4-SNAPSHOT, but do you want to try out
>> our new maven build with 1.5.3 ?
>>
>> Could be a good way to test that everything works on a stable codebase. I
>> can use the 1.5.x freshly created poms on the 1.5.3 tag (I guess file
>> structure is the same), deploy to sonatype, and see if they actually sync
>> with central...
>>
>> What do you think ? That could kickstart the process.
>>
>> Cheers
>>
>> Remi
>>
>> PS : what about continuous integration ? do we have any kind of OSS
>> account in some forge somewhere for that (bamboo, cruise control,
>> you-name-it) ? If yes then it might be good to plug the maven build on it,
>> then we would never have to even think about those deployment issues...
>>
>>
>> 2010/9/23 Ben Gunter <[email protected]>
>>
>>> 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
>>>> >>
>>>>
>>>
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
