Issue 5809 in pharo: System-CommandLine has poor packaging

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug

New issue 5809 by [hidden email]: System-CommandLine has poor  
packaging
http://code.google.com/p/pharo/issues/detail?id=5809

System-CommandLine package includes tests too (BasicCodeLoaderTest,  
CommandLineArgumentsTest, CommandLineHandlerTest).

The tests should be in separate package.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Workneeded
        Labels: Milestone-2.0

Comment #1 on issue 5809 by [hidden email]: System-CommandLine has  
poor packaging
http://code.google.com/p/pharo/issues/detail?id=5809

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 5809 by [hidden email]: System-CommandLine has  
poor packaging
http://code.google.com/p/pharo/issues/detail?id=5809

no that's not true, the tests are all in

System-CommandLine-Test

which is much better than Test-System-CommandLine. I hope we will change  
that soon for the rest of the system. Maybe I'am wrong but for me tests  
belong to a certain project, thus should live under a clearly identified  
subspace of said project.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 5809 by [hidden email]: System-CommandLine has  
poor packaging
http://code.google.com/p/pharo/issues/detail?id=5809

PackageInfo just made a package System-CommandLine. This needs to be split.
(I *hate* packageInfo!!!)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 5809 by [hidden email]: System-CommandLine  
has poor packaging
http://code.google.com/p/pharo/issues/detail?id=5809

Hi Camillo,

of course System-CommandLine-Test is good package name. The problem is that  
currently you cannot have packages named System-CommandLine and  
System-CommandLine-Test because the second one will then be all included in  
the System-CommandLine package.
Our options are
1) to have packages System-CommandLine-Core and System-CommandLine-Tests
2) to have packages System-CommandLine and System-CommandLineTests

For small packages we prefer the first option.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Integrated

Comment #5 on issue 5809 by [hidden email]: System-CommandLine has  
poor packaging
http://code.google.com/p/pharo/issues/detail?id=5809

I moved it for now into the big Tests* package (even though I don't like it)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker