Open GoogleCodeExporter opened 9 years ago
Original comment by kkrugler...@transpac.com
on 8 Jul 2014 at 4:31
I added this class as a simple way of checking what we were getting for a given
sitemap URL. OK for renaming it to SiteMapTool but I don't think we need to
provide the recursivity parsing as this can easily be built on top of CC + I'd
rather avoid multiplying the jars we produce, especially for such a small
functionality.
What about building this functionality outside CC and host it as a separate
project e.g. on GitHub?
Original comment by digitalpebble
on 9 Jul 2014 at 8:07
I still think we need this functionality inhouse.
I am playing with sitemap parsing and I return to this tool each time and use
it.
There is a place for a git hub project using netty or whatever Ken suggested
for heavy duty sitemap parsing! - using our library as 3rd party parsing for
sitemap and using something else for the heavy duty networking.
But I still think we need it inhouse.
Maybe we should put it in the "test" folder ?
What is so bad about another jar ?
Original comment by avrah...@gmail.com
on 11 Jul 2014 at 2:48
What is so bad about another jar ?
Having one JAR separate file for such a small functionality does not make sense
+ we want to avoid multiplying them as I explained above.
Original comment by digitalpebble
on 14 Jul 2014 at 1:10
ok.
This is the conclusion of what we will do in this issue:
Just rename the file to the "Tool" suffix instead of "Test".
Please note that this issue will be taken care of after the submission of
issue39
Original comment by avrah...@gmail.com
on 18 Jul 2014 at 7:08
Please note that this issue will be taken care of after the submission of
issue43
And not issue39 as I wrote in the last comment
Original comment by avrah...@gmail.com
on 18 Jul 2014 at 7:20
Original comment by avrah...@gmail.com
on 18 Jul 2014 at 8:05
Original issue reported on code.google.com by
avrah...@gmail.com
on 4 Jul 2014 at 9:36