licensetemplates project not in correct place in svn and has a wrong name or artifactId

[GoogleCodeExporter]

licensetemplates is defined on the top level in the repo, while it is maven 
dependent, and thus 
should be in the java part of svn; furthermore it is intended for checkstyle 
(it even has the same 
groupId), so that should be a hint that it belongs there. Furthermore, the 
artifactId differs from the 
name of the svn directory, which is surprising too and should be changed.

Once the name is set correctly, we also need to add the project name to the 
issue list-of-projects.

This is critical, since the most critical releases depend on checkstyle, which 
depends on this.

Original issue reported on code.google.com by jandockx on 25 Jul 2008 at 11:12

[GoogleCodeExporter]

In fact, I don't agree.  Since ppwcode also encompasses ruby scripts, shell 
scripts, 
xml files... and can even encompass .NET code, I think it is not java specific. 


Checkstyle may check only java code, but the license template is more generic 
to any 
type of ppwcode project, and every project must carry the (or a) template 
prescribed 
by google code.

The only argument that could be valid is that there is a pom file in the 
project, 
but that file should normally not in the way for any other script that wants to 
check whether a valid license is each file.

Original comment by Tom.Mah...@gmail.com on 26 Jul 2008 at 3:56

[GoogleCodeExporter]

So, this would result in using Maven also for non-Java projects? We could try 
that on svn_spider.

Original comment by jandockx on 27 Jul 2008 at 9:25

[GoogleCodeExporter]

See also Issue111

Original comment by jandockx on 27 Jul 2008 at 9:32

[GoogleCodeExporter]

See Issue109

Original comment by jandockx on 27 Jul 2008 at 9:44

[GoogleCodeExporter]

This should not hold back a first release.

Original comment by jandockx on 28 Jul 2008 at 9:36

• Added labels: Priority-Medium
• Removed labels: Priority-Critical