Ticket #24 (new enhancement)
Opened 5 years ago
link between jcReport and eclipse (and more)
| Reported by: | amandel | Owned by: | jCoderZ |
|---|---|---|---|
| Priority: | minor | Milestone: | unscheduled |
| Component: | jCoderZ-report | Version: | trunk |
| Keywords: | Cc: |
Description
copied from elder wiki
Targeting Problem
There is still a gap when coming from a jCoderZ report to get a easy integration of the findings into the IDE (Eclipse). You could integrate local findbugs/checkstyle but there will always be differences regarding configuration, number of tools or version of the tools used. I would like to see the findings as the other stuff as markers within Eclipse.
There might be the need for markers to code that could not be put in the actual code. Like a TODO that is not in a comment of the code. Remove the one place for the source ore separate the information. I still stick to the point that all information should be put into the source file... (a bit a contradiction, but we will see how to handle this). These markers should be shared across the whole development team. Code review process could use this markers and also team communication about specific code should be possible.
Possible Solution snippets
- Use Eclipse Markers a plugin could update the markers. I currently see no solution without a plugin.
- Use a central repository to store the data
- Possibly live online update via a server component could be achieved vi a jabber grout chat read by a eclipse plugin and filled by the component changing the entries (or a other use of the XMPP protocol)
- Store Data in CVS/Subversion or Jira?? To have a version history can be helpfully but also pain. It could be stored as subversion property to the files but this would limit it do be used with´subversion only (could be a .XXX file for others too)
- Feed in information from CC (how to detect changes in existing findings)
Comments and edits are welcome!!!
