Skip to content

Conversation

@JordanTerri
Copy link

I made some choices regarding names of projects but there's nothing final, everything can be renamed.
I know that the big problem is to keep traces of the modification history, and to my opinion, everything is fine. Though github may not display full history on files that has been moved, but as said here, the problem comes from GitHub not git: #72 (comment) : full history is always available by doing git log --follow <thefile> (and your favorite IDE usually does the "--follow").

* creating a jsip folder for parent pom with modules
* creating clean java project structure with maven
* moving source code to new structure
* moving unit tests to new structure
* compilation and build ok
* fix few unit tests that crashes
* adding tools as project of their own

* adding missed unit test on sdp on jain-sip-ri
* moving examples classes to an examples project
* moving TCK to test suite component

* moving testcases from RI to test-suite component to avoid circular
dependencies, and also because it's most suited for them to be there in
my opinion

* cleaning examples and pom files
* removing a failing case in unit test

* fixing pom.xml for build
* removing unnecessay dependency
* fixing tck test
* fixing dependencies for tck build
* fixing dependencies on sniffer
* moving old build files to archive folder
@vladimirralev
Copy link
Collaborator

Thanks. I am a litle busy right now. Will try to review this soon.

@DeveloperTK
Copy link

bump

@JordanTerri
Copy link
Author

Hello,
I hope people will find time to review :)

@DerGuteMoritz
Copy link

Thanks for this! FWIW, the build instructions given in the README are now outdated and should probably be adjusted to match the changes introduced by this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants