Nabble - CheckStyle

[ checkstyle-Bugs-2155288 ] resource checkstyletask.properties

2008-10-10T01:19:07Z

Bugs item #2155288, was opened at 2008-10-09 17:36
Message generated for change (Comment added) made by marcbeckers
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2155288&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ANT Task
Group: release 4.4
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Marc Beckers (marcbeckers)
Assigned to: Oliver Burn (oburn)
Summary: resource checkstyletask.properties

Initial Comment:
I have written a custom check and put it in a jar. When I run the check in NetBeans with the Checkstyle Beans plugin it all works well, but when I run it with Ant I get the following error:

Could not load definitions from resource checkstyletask.properties. It could not be found.
C:\MyData\LocalSubversionWorkingCopy\bla\trunk\projects\BLA\autobuild.xml:43: Problem: failed to create task or type checkstyle
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

But the file checkstyletask.properties is available in the checkstyle-all-4.4.jar.

What am I doing wrong? Please help me!

Snippet from build.xml:

<target name="checkstyle" depends="init, compile">
<mkdir dir="${build.checkstyle.dir}"/>
<taskdef resource="checkstyletask.properties" classpath="${lib.dir}/autobuild/checkstyle/*.jar"/>
<checkstyle config="${lib.dir}/autobuild/checkstyle/mychecks.xml" failonviolation="false" classpath="${lib.dir}/autobuild/checkstyle/*.jar">
<formatter type="xml" tofile="${build.checkstyle.dir}/checkstyle.xml"/>
<fileset dir="${src.dir}" includes="**/*.java"/>
<classpath path="${build.classes.dir};"/>
</checkstyle>
</target>

----------------------------------------------------------------------

>Comment By: Marc Beckers (marcbeckers)
Date: 2008-10-10 10:19

Message:
I have fixed the problem by adding a path element:

<path id="checkstyle.classpath">
<fileset dir="${lib.dir}/autobuild/checkstyle">
<include name="*.jar"/>
</fileset>
</path>

and changing the taskdef element:

<taskdef resource="checkstyletask.properties"
classpathref="checkstyle.classpath"/>

Apologizes!

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2155288&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[ checkstyle-Bugs-2155288 ] resource checkstyletask.properties

2008-10-09T08:36:53Z

Bugs item #2155288, was opened at 2008-10-09 17:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2155288&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ANT Task
Group: release 4.4
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Marc Beckers (marcbeckers)
Assigned to: Oliver Burn (oburn)
Summary: resource checkstyletask.properties

Initial Comment:
I have written a custom check and put it in a jar. When I run the check in NetBeans with the Checkstyle Beans plugin it all works well, but when I run it with Ant I get the following error:

Could not load definitions from resource checkstyletask.properties. It could not be found.
C:\MyData\LocalSubversionWorkingCopy\bla\trunk\projects\BLA\autobuild.xml:43: Problem: failed to create task or type checkstyle
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.

But the file checkstyletask.properties is available in the checkstyle-all-4.4.jar.

What am I doing wrong? Please help me!

Snippet from build.xml:

<target name="checkstyle" depends="init, compile">
<mkdir dir="${build.checkstyle.dir}"/>
<taskdef resource="checkstyletask.properties" classpath="${lib.dir}/autobuild/checkstyle/*.jar"/>
<checkstyle config="${lib.dir}/autobuild/checkstyle/mychecks.xml" failonviolation="false" classpath="${lib.dir}/autobuild/checkstyle/*.jar">
<formatter type="xml" tofile="${build.checkstyle.dir}/checkstyle.xml"/>
<fileset dir="${src.dir}" includes="**/*.java"/>
<classpath path="${build.classes.dir};"/>
</checkstyle>
</target>

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2155288&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[ checkstyle-Feature Requests-2123015 ] Reports with relative filenames

2008-10-08T14:34:33Z

Feature Requests item #2123015, was opened at 2008-09-22 10:55
Message generated for change (Comment added) made by kajsaanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397081&aid=2123015&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Florian (iflo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Reports with relative filenames

Initial Comment:
Currently a report generated by a command line call contains error messages with absolute filenames:
e.g. "/tmp/checkstyleRun6928601/src/main/java/my/package/Example.java:0:0 something is wrong"

It would be cool if one could specify a directory to which filenames are made relative to. For example this could be done by the user by adding the following two arguments to the command line:
--filenamesRelativeTo /tmp/checkstyleRun6928601/

This should result in error messages with relative filenames:
"src/main/java/my/package/Example.java:0:0 something is wrong" as error message.

----------------------------------------------------------------------

Comment By: Kajsa Anderson (kajsaanderson)
Date: 2008-10-08 16:34

Message:
I use this workaround in my Ant build, between the checkstyle task and the
xslt task that creates the report:


<replace file="${stylereport.dir}/style_report.xml" token="${src}"
value="..." />

But I agree that it would be a nice feature.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397081&aid=2123015&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[ checkstyle-Patches-2151774 ] Update the Maven dependencies.

2008-10-07T08:19:29Z

Patches item #2151774, was opened at 2008-10-07 17:19
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397080&aid=2151774&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Florian (iflo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Update the Maven dependencies.

Initial Comment:
This patch updates the maven dependencies of checkstyle.
It also increases the maven version number from 4.4-SNAPSHOT to 5.0-SNAPSHOT.

off topic: Is there generally any interests in supporting maven as a build tool for your project? I tried to change the pom.xml so that can compile the project with maven. I got the compilation working but 20 out of the 538 unit tests still fail when I execute the tests with maven. If you aren't interested in using maven as build tool I will not look in the matter further.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397080&aid=2151774&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[ checkstyle-Patches-2151706 ] Do not require a file, when the user uses the option "-r".

2008-10-07T07:36:56Z

Patches item #2151706, was opened at 2008-10-07 16:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397080&aid=2151706&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Florian (iflo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Do not require a file, when the user uses the option "-r".

Initial Comment:
The command line version of checkstyle offers a "-r" option. If the directory specified with "-r" is empty, checkstyle will print:
"Must specify files to process" followed by a usage explanation.

I think this is a small bug, because a user who specifies "-r" did not forget to specify which files should be checked.

I have such a case that I have a directory which might contain files to check. I don't want checkstyle to fail if there are no files in that directory.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397080&aid=2151706&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[ checkstyle-Bugs-2127437 ] suppressions dtd

2008-10-06T06:33:18Z

Bugs item #2127437, was opened at 2008-09-24 18:52
Message generated for change (Comment added) made by victormote
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2127437&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
>Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Victor Mote (victormote)
Assigned to: Oliver Burn (oburn)
Summary: suppressions dtd

Initial Comment:
The web site (config.html#Filters) includes the following example of using an "id" to suppress a check:

<suppress id="stringEqual" files="SomeTestCode.java"/>

However, the DTD reference for the "suppressions" document points to a version 1_0, which does not allow the "id" attribute. Perhaps the documentation should provide a reference to version 1_1, which does support this attribute.

----------------------------------------------------------------------

>Comment By: Victor Mote (victormote)
Date: 2008-10-06 07:33

Message:
Hi Oliver:

The page is here:
http://checkstyle.sourceforge.net/config.html#Filters

Search for this text:
"DTD Suppressions 1.0"

or:
"http://www.puppycrawl.com/dtds/suppressions_1_0.dtd"

I hope this helps.

Victor Mote

----------------------------------------------------------------------

Comment By: Oliver Burn (oburn)
Date: 2008-10-05 22:14

Message:
Hi - I cannot find the reference to version 1_0 -- can you please paste the
exact text in so I can find it.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2127437&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

TR: Is the project interested in the following rules ?

2008-10-06T02:11:31Z

Hello,

In the scope of the development of a quality platform project, we are
implementing some checkstyle 4.4 checks to verify the rules of our
development / architecture standards. Now I'm writing the following
email to the list in order to ask if the checkstyle project would be
interested in them.

One of the main feature of these checks is that they are completely
configurable and generic. Indeed, we wanted to have adaptable checks
allowing us to make evolve our quality standards without having to
redevelop the checks, and we also wanted to enable anybody to adapt them
to their precise needs without having to follow our own standards. By
"anybody" we meant the checkstyle users community ;-)

Here follows a description of the checks :

===
1. Type names verification

We use this check to verify that types respect the naming standard which
are in place. For instance we want that all Exceptions end with
"Exception", all interfaces end with "Able", all formbeans start with
"Fb", etc. Instead of writing a check for each rule, we wrote a single
check that can be configured as follows :

a. must the rule be applied to interfaces or to classes ?
b. must the verification occur only if the type is an instance of a
given base type (for instance only to subclasses of
"java.lang.Exception") or must it be always applied (for instance it
must be applied to all interfaces)
c. what is the text that must be be present (for instance "Able",
"Exception")
d. where must it be present (prefix or suffix) ?

===
2. Package root

We use this simple check to verify that all projects use a correct
package root. (for instance, in our organization, all packages must
start with "ch.ge." and packages names should include information about
the department and project they are part of. Thus, packages part of
project "b" of department "a", should be prefixed "ch.ge.a.b.")

===
3. Package dependencies - In a context where we use package names to
represent architecture layers, we needed a rule allowing us to define
what package dependencies (calls from package A to package B) are
forbidden. We develped thus a check enabling us to check that each layer
is correctly isolated from other layers.

In this check, all dependencies are described using regular expressions,
which allows us to extend the verification at will (for instance to add
new layers, or to adapt the check to projects having used another naming
scheme for layers (for legacy projects for instance)).

To give you an idea of what we can do with this rule, as attachement you
can find an example of verifications we are currently doing. This shows
what the check allows us to verify and what we currently cannot verify.
Plea <<checks.pdf>> se note that all these verifications are done by
instanciating the generic rule only 5 times.

The rule can be configured as follows :
a. the package to which the rule must be applied (the layer to be
verified) as a regexp
b. the imports that are forbidden as a regexp
c. a switch to ignore the rule if the checked type is already in a
"forbidden" package (this allows us to have rules that say that "no
class can import a class from package B or its subpackages, unless the
class is from package B or its subpackages"

==
4. Dependency cycles detection - This check aims at detecting dependency
cycles between components. Such cycles are difficult to detect by hand
and impede the maintainablity and evolvability of the code. To represent
components we use regular expressions on packages.

Currently, the check simply outputs cycles as logs "component A ->
component B -> component C -> component A" (for instance). In the
future, I plan to improve it to provide more information to help break
these cycles. Two parameters are available :
a. the regexp allowing to detect components (for instance, if a package
has a subpackage named "api" then it is a component)
b. the regexp specifying the packages which have to be scanned for
cycles (for instance if we want to scan only a given set of components)

If you need any more information feel free to ask :-)

Best regards,

Michel Pawlak

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-user mailing list
Checkstyle-user@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-user

checks.pdf (13K) Download Attachment

From forum: CheckStyle - User

[ checkstyle-Bugs-1435289 ] HTML Comments in JavaDoc cause incorrect parsing

2008-10-05T21:31:02Z

Bugs item #1435289, was opened at 2006-02-21 02:56
Message generated for change (Comment added) made by oburn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=1435289&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core Framework
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Phil Riley (rileypb)
Assigned to: Oliver Burn (oburn)
Summary: HTML Comments in JavaDoc cause incorrect <tag> parsing

Initial Comment:
The following javadoc is incorrectly parsed:

/**
* Create a new Event with the given parameters.
*
* Will accept the parameters:
* <ol>
* <li>latency: optional, ≥ 0, defaults to zero if trigger time is also
omitted.</li>
* <li>trigger time: optional,
≥, defaults to posting time if latency
is also omitted.</li>
* <li>posting time: required.</li>
* </ol>
* 
*
* @param type event type
* @param source event source
* @param target event target(s)
* @param params event parameters
*/

Checkstyle reports the following warning:
"Unclosed HTML tag found: <ol>"

Only removing the " ignore everything in between.

I'd agree that attempting to determine if what is between <>'s is a class
is not the way to go.

----------------------------------------------------------------------

Comment By: Rmy-Christophe Schermesser (rschermesser)
Date: 2008-09-23 02:44

Message:
Hi,

I am willing to fix this issue, but I am not sure whow to fix it.

I have found 2 possible ways to fix it :

- Allow only some specific HTML tags in the javadoc.
- Check if the value between the < > is a Java class or not.

Which way do you prefer ? Or do you have another idea ?

I much prefer the first solution, because the second one is very very slow
...

Thanks in advance

----------------------------------------------------------------------

Comment By: Tobias Scholl (schollt)
Date: 2008-02-04 22:05

Message:
Logged In: YES
user_id=1464585
Originator: NO

Another example:

/**
* @return a {@code List<String>}.
*/
List<String> someMethod() {
return new java.util.ArrayList<String>();
}

"<String>" considered to be an HTML tag and produces the following error:
Unclosed HTML tag found: <String>}.

Possible workaround:
<code>List<String></code>.

However, that (in my opinion) makes the comment less readable in the
source code.

----------------------------------------------------------------------

Comment By: Hendrik Schreiber (hendriks73)
Date: 2006-05-04 01:46

Message:
Logged In: YES
user_id=252726

A similar problem occurs when linking to a method with parametrized
arguments like this:

/**
* {@link #offer(java.util.Collection<Task>)}
*
*
* @param task task
*/

The resulting message is "Unclosed HTML tag found: <Task>)}"

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=1435289&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[ checkstyle-Bugs-2127437 ] suppressions dtd

2008-10-05T21:14:04Z

Bugs item #2127437, was opened at 2008-09-25 10:52
Message generated for change (Comment added) made by oburn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2127437&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Victor Mote (victormote)
>Assigned to: Oliver Burn (oburn)
Summary: suppressions dtd

Initial Comment:
The web site (config.html#Filters) includes the following example of using an "id" to suppress a check:

<suppress id="stringEqual" files="SomeTestCode.java"/>

However, the DTD reference for the "suppressions" document points to a version 1_0, which does not allow the "id" attribute. Perhaps the documentation should provide a reference to version 1_1, which does support this attribute.

----------------------------------------------------------------------

>Comment By: Oliver Burn (oburn)
Date: 2008-10-06 15:14

Message:
Hi - I cannot find the reference to version 1_0 -- can you please paste the
exact text in so I can find it.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397078&aid=2127437&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

Re: [5.0beta01] Unable to instantiate PackageHtml

2008-10-05T21:04:32Z

Correct - the PackageHtml has been replaced by http://checkstyle.sourceforge.net/5.x/config_javadoc.html#JavadocPackage

In SVN I have fix the problem.

On Mon, Oct 6, 2008 at 02:40, Thomas Suckow <tsuckow@...> wrote:

Sun checks has not been updated for 5.0

JavadocPackage replaces PackageHtml

I recommend starting with checkstyle_checks rather than sun_checks

Thomas Suckow

On Fri, Oct 3, 2008 at 12:29 AM, stlecho <stlecho@...> wrote:
>
> Hi,
>
> When using the sun_checks.xml file in the checkstyle Ant target, I'm
> receiving an "Unable to instantiate PackageHtml" error. When removing the
> <module name="PackageHtml"/> definition from sun_checks.xml, the target
> works perfectly.
>
> Is this an issue related to the 5.0beta01 version ?
>
> Regards, Stefan Lecho.
> --
> View this message in context: http://www.nabble.com/-5.0beta01--Unable-to-instantiate-PackageHtml-tp19787589p19787589.html
> Sent from the CheckStyle - User mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> 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=/
> _______________________________________________
> Checkstyle-user mailing list
> Checkstyle-user@...
> https://lists.sourceforge.net/lists/listinfo/checkstyle-user
>

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-user mailing list
Checkstyle-user@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-user

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-user mailing list
Checkstyle-user@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-user

From forum: CheckStyle - User

Re: [5.0beta01] Unable to instantiate PackageHtml

2008-10-05T08:40:57Z

Sun checks has not been updated for 5.0

JavadocPackage replaces PackageHtml

I recommend starting with checkstyle_checks rather than sun_checks

Thomas Suckow

On Fri, Oct 3, 2008 at 12:29 AM, stlecho <stlecho@...> wrote:

>
> Hi,
>
> When using the sun_checks.xml file in the checkstyle Ant target, I'm
> receiving an "Unable to instantiate PackageHtml" error. When removing the
> <module name="PackageHtml"/> definition from sun_checks.xml, the target
> works perfectly.
>
> Is this an issue related to the 5.0beta01 version ?
>
> Regards, Stefan Lecho.
> --
> View this message in context: http://www.nabble.com/-5.0beta01--Unable-to-instantiate-PackageHtml-tp19787589p19787589.html
> Sent from the CheckStyle - User mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> 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=/
> _______________________________________________
> Checkstyle-user mailing list
> Checkstyle-user@...
> https://lists.sourceforge.net/lists/listinfo/checkstyle-user
>

From forum: CheckStyle - User

Re: Extending checkstyle 4.4

2008-10-05T08:04:34Z

Hi Arnaud,

wow, this list looks really impressive. If you're comfortable sharing the the sources under LGPL and including our standard license header in your source files, you might want to contribute your code to our patch tracker, so they could end up in the normal checkstyle distribution. Just make sure that you follow the guidelines in our "contributing" document.

I am not aware of any other place to share checkers.

Cheers,
Lars

On Mon, Sep 29, 2008 at 6:00 PM, Arnaud Roques wrote:

Hello,
Checkstyle is really a great tool to improve code quality, and I've developped some checkers that other people may find usefull. (They have been used with JDK1.4).
If you have some idea to add in this list, please tell me.

From forum: CheckStyle - User

[ checkstyle-Feature Requests-2146528 ] Translation check: Allow checkstyle:off in properties file

2008-10-04T08:12:40Z

Feature Requests item #2146528, was opened at 2008-10-04 17:12
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397081&aid=2146528&group_id=29721

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Check
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: evernat (evernat)
Assigned to: Nobody/Anonymous (nobody)
Summary: Translation check: Allow checkstyle:off in properties file

Initial Comment:
This is a feature enhancement request.
ResourceBundle are chained with parents as said in http://java.sun.com/j2se/1.5.0/docs/api/java/util/ResourceBundle.html#getString(java.lang.String).
For example, messages_fr.properties is chained with messages.properties.
So, all messages are not always in messages_fr.properties and default ones in message.properties are used if it is the case.

The problem is that the translation check of checkstyle (http://checkstyle.sourceforge.net/config_misc.html#Translation) does not like chaining and gives a lot of warnings wich are false positives in this file.
I would like to keep this check as I also have files that I would want to verify for correct translation.

My enhancement request is to be able to write a comment in my particular messages_fr.properties to disable check for this file. The comment could be # CHECKSTYLE:OFF

Thank you

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=397081&aid=2146528&group_id=29721

-------------------------------------------------------------------------
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=/
_______________________________________________
Checkstyle-devel mailing list
Checkstyle-devel@...
https://lists.sourceforge.net/lists/listinfo/checkstyle-devel

From forum: CheckStyle - Dev

[5.0beta01] Unable to instantiate PackageHtml

2008-10-02T14:07:50Z

Hi,

When using the sun_checks.xml file in the checkstyle Ant target, I'm receiving an "Unable to instantiate PackageHtml" error. When removing the <module name="PackageHtml"/> definition from sun_checks.xml, the target works perfectly.

Is this an issue related to the 5.0beta01 version ?

Regards, Stefan Lecho.

From forum: CheckStyle - User