[No Operation]

Hi there, glad you read my post, even when the title is:
“Not operational guide” 😉

I just wanna share my way to work with projects.

Rule 1
Create ONE project per web application
Use the wizard (which uses your previous configured defaults) to create the project, and add the content.
This is the project used for test and deployment.
Share it with your repository and check it in.

Rule 2
All external code is referenced by using JARs
This gives you the advantage to have compact projects. People can work on this project without having interferences to other projects.
Update the JARs if required.

Rule 3
Create special developer projects only to extract test cases
Let’s say your web project “elefants” uses a component “grey” which is used as “grey.jar”. You might have the wish/need to debug both together.
Perform the check out for the project “grey”, and add it tou your web project “elefants”.

Rule 4
NEVER CHECK IN those developer projects
Use these modifications only to track the issues down until you have extracted test cases.

Rule 5
Track down your issues and define tests
If some project contains an error, you can define a test to reproduce that error.
If the error is in “grey”, you define a test in the project “grey”.
Since there was also an issue in “elefants”, create also a test in “elefants”.

Rule 6
Resolve your reproducable issues
Solve the issues, perform the builds and updates as needed and verify your projects.

NOP

[Riyad Kalla]

NOP thanks for the guide, hopefully this can help some people getting started with ME.

[Author]

Posts