Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8199

open tasks aren't parsed anymore

    Details

    • Similar Issues:

      Description

      In the past I used a Freestyle project for my non java project (delphi). There open tasks where successful parsed as a postbuildaction.
      Now I changed the project type to maven 2 project, where the open task parser is configured in the build settings. Now it seems, that the parser is not called, even so I copied the configuration without changes to the new project.

      Is there any logfile where I can exactly determine if the parser wasn't started, or if it skipped the files or if it didn't find the todos because of the given task tags?

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          What do you mean with copied? Did you manually change the XML files?

          Show
          drulli Ulli Hafner added a comment - What do you mean with copied? Did you manually change the XML files?
          Hide
          drulli Ulli Hafner added a comment -

          In the console log of a build the following line should appear:

          [TASKS] Scanning workspace files for tasks...

          Show
          drulli Ulli Hafner added a comment - In the console log of a build the following line should appear: [TASKS] Scanning workspace files for tasks...
          Hide
          drulli Ulli Hafner added a comment -

          Note that the plug-in uses the default maven src folders to determine the files to scan...

          Show
          drulli Ulli Hafner added a comment - Note that the plug-in uses the default maven src folders to determine the files to scan...
          Hide
          drulli Ulli Hafner added a comment -

          BTW: please also have a look at: JENKINS-6127

          Show
          drulli Ulli Hafner added a comment - BTW: please also have a look at: JENKINS-6127
          Hide
          namue namue added a comment -

          With copied I mean: I created a new Job and copied all entries in hudson ui (http://server/hudson/job/dummy/configure) field by field.

          The catalina.out of the tomcat containing my hudson has no entry "[TASKS] Scanning workspace files for tasks...".

          What means default maven src folder? In the configuration I can set the files to scan (I set it to */.pas). The description says this directoey is relative to my workspace. So I think this should work. I do not use a folder named src/main/java but folders like MODULE/source where MODULE is a String, that differs for every module. This foldes are located directly in my workspaceroot.

          Show
          namue namue added a comment - With copied I mean: I created a new Job and copied all entries in hudson ui ( http://server/hudson/job/dummy/configure ) field by field. The catalina.out of the tomcat containing my hudson has no entry " [TASKS] Scanning workspace files for tasks...". What means default maven src folder? In the configuration I can set the files to scan (I set it to * / .pas). The description says this directoey is relative to my workspace. So I think this should work. I do not use a folder named src/main/java but folders like MODULE/source where MODULE is a String, that differs for every module. This foldes are located directly in my workspaceroot.
          Hide
          namue namue added a comment -

          Description of the field was wrong. The parser does not parse files relative to the workspace root but relative to the sourcedirs.

          If the sourcedirs are not inside the pom, because it's no java-project, they can be added with following entry in the pom:

          <plugin>
          <groupId>org.codehaus.mojo</groupId>
          <artifactId>build-helper-maven-plugin</artifactId>
          <version>1.5</version>
          <executions>
          <execution>
          <id>add-source</id>
          <phase>pre-clean</phase>
          <goals>
          <goal>add-source</goal>
          </goals>
          <configuration>
          <sources>
          <source>.</source> // full workspace
          </sources>
          </configuration>
          </execution>
          </executions>
          </plugin>

          Show
          namue namue added a comment - Description of the field was wrong. The parser does not parse files relative to the workspace root but relative to the sourcedirs. If the sourcedirs are not inside the pom, because it's no java-project, they can be added with following entry in the pom: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <version>1.5</version> <executions> <execution> <id>add-source</id> <phase>pre-clean</phase> <goals> <goal>add-source</goal> </goals> <configuration> <sources> <source>.</source> // full workspace </sources> </configuration> </execution> </executions> </plugin>

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              namue namue
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: