Re: [Jamwiki-devel] Starting with jamwiki hacking / IDE warnings

[<jam...@li...>]

Hi Thomas,

Warning fixes are very much appreciated, so long as they're not just 
"@SuppressWarnings" annotations, which have the side-effect of hiding 
useful messages.  See http://jamwiki.org/wiki/en/How_to_Help#Programmers 
for the steps needed to get Subversion access to begin committing fixes 
and creating a branch for the two features you've mentioned.  I don't 
use Eclipse, so it's possible that IDE will report a number of warnings 
that I wouldn't see otherwise.

As to switching to Git, if enough people want to do so then I'm not 
opposed to the idea.  My main issue with Git (vs Subversion) is that 
with Git it's much easier to screw up your repository in a way that is 
difficult to undo, such as with funky merges or rebases, while with 
Subversion you can always just undo the problem commit.  We use Git at 
work, and have had to put a number of processes in place to ensure that 
people don't do anything that's unexpected and thus cause a lot of work 
for the repository owner to fix.  If there are enough active JAMWiki 
developers with Git knowledge who can fix any such issues then I'm happy 
to switch, but if the responsibility is mostly on me to deal with any 
SCM problems then I'd prefer to continue using Subversion.

Again, any thoughts that anyone else has on Git vs. Subversion are 
welcome - I don't want to stand in the way of people using their 
preferred SCM tool, but I also don't want to be the only with 
responsibility for resolving Git-related issues.

Ryan


On 2/23/2013 11:08 AM, jam...@li... wrote:
> Hi,
>
> I want to learn more about java web development and thus thought I could work
> on my issues with jamwiki:
>
> - I'd like to have diffs in the RecentChanges RSS feed
> - I'd like to have email notifications for watched pages
>
> I already opened three issues about eclipse errors in the jira. Do you also
> accept patches to get the number of warnings down? I normally try to keep the
> number of warnings near to zero in java projects.
>
> In eclipse I currently have around 268, mostly:
>
> - ... is a raw type. References to generic type ... should be parameterized
> - The import ... is never used
> - The serializable class ... does not declare a static final serialVersionUID
> field of type long
> - The static ... from the type ... should be accessed in a static way
>
> Such cleanup work is also a good way to learn more about the codebase.
>
> By the way: Did I already ask whether you might consider switching to Git? :-)
>
> A nice ironic blogpost on Git: http://svenpet.com/2013/02/21/dont-use-git
>
> Regards,
>
> Thomas Koch, http://www.koch.ro
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Jamwiki-devel mailing list
> Jam...@li...
> https://lists.sourceforge.net/lists/listinfo/jamwiki-devel
>