Hi Mirko!
Julien, there is a little cleaning up I would like to do with JWebUnit
before we release 2.1 (and close some more of the open feature requests),
but may we tentatively mark 1 Dec as the 2.1 release date?
Does Maven deal with updating the SF site? What about uploading changes? Is
there any particular Maven commands used for releasing/updating new releases
of JWebUnit?
Cheers
Jevon
On Tue, Nov 18, 2008 at 10:33 PM, Julien HENRY <[EMAIL PROTECTED]> wrote:
> Hi Mirko,
>
> You are now a member of JWebUnit team! Welcome!
>
> Please send us one or two patches this way Jevon or I will be able to
> "validate" you coding style. Then I will give you commit rights on the trunk
> and you will be able to commit directly in SVN.
>
> Regards,
>
> Julien
>
> P.S. : Jevon, I let you decide when you want a new release. It could be a
> rc or a beta if you don't feel confident, or directly the 2.1.
>
>
>
> ----- Message d'origine ----
> De : Mirko Friedenhagen <[EMAIL PROTECTED]>
> À : JWebUnit Development mail list <
> [email protected]>
> Envoyé le : Lundi, 17 Novembre 2008, 21h03mn 24s
> Objet : Re: [JWebUnit-development] Re : Re : Standard formatting for IDEs,
> templates for files
>
> Am 17.11.2008 um 13:59 schrieb Julien HENRY:
> > I suggest using 4-spaces everywhere: XML, Java, HTML (in JUnit tests).
> >
> ACK
>
> > Another discussion is the line length. SUN convention is 80 line
> > length but it seems very short for me, especially for XML/HTML files
> > where I really dislike word-wrapping. What's your opinion about this?
> > I'm personnaly in favor for 120 in Java source and no limit in XML/
> > HTML.
>
> I prefer 120 characters as well :-)
>
> > You can of course include Eclipse configuration file (I think latest
> > Maven eclipse plugin have the ability to automatically configure
> > Eclipse coding style). See
> http://maven.apache.org/plugins/maven-eclipse-plugin/examples/load-code-styles.html
> >
> > According to me, encoding in source files should be UTF-8, without
> > any non ASCII char. Only some JUnit tests should contains different
> > encodings to validate everything works fine for localized Web pages.
>
> Good.
>
> > I you plan to contribute to JWebUnit, I can add you to the project
> > team list. Is it ok for you?
>
> I would be happy about this. Right now I have a branch in a Mercurial-
> Repo (http://friedenhagen.net/hg.cgi/jwebunit/mirkos/).
>
> Regards
> Mirko
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> JWebUnit-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jwebunit-development
>
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> JWebUnit-development mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jwebunit-development
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
JWebUnit-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jwebunit-development
