Reputation
473
Top tag
Next privilege 500 Rep.
Access review queues
Badges
3 17
Impact
~17k people reached

  • 0 posts edited
  • 0 helpful flags
  • 80 votes cast
Jan
29
comment Where to store standalone.xml and other files so it is acessible in my CI server?
nice to know, thanks!
Jan
29
comment Where to store standalone.xml and other files so it is acessible in my CI server?
I am going this path, except for the encryption because it is a experimental project and I am the only one with access. Nothing serious is stored there. If I store the test env files in their own repo, where would I store the production ones? (In the same repo, but encrypted?)
Jan
29
accepted Where to store standalone.xml and other files so it is acessible in my CI server?
Jan
29
comment Where to store standalone.xml and other files so it is acessible in my CI server?
I am not able to store anything in the CI Server, because it is a hosted solution that builds VMs for each build. But I get the overall idea, which seems very interesting :)
Jan
28
asked Where to store standalone.xml and other files so it is acessible in my CI server?
Dec
26
awarded  Popular Question
Oct
30
accepted Should I unit test my subclasses or my abstract parent class?
Oct
28
comment Should I unit test my subclasses or my abstract parent class?
Yes, they are different (the types and content are different). Technically speaking, I would be able to mock this class or have a simple implementation only for testing purposes with empty implementations. I do not like this approach. But the fact that I do not "need" to think to have passing tests in new implementations makes me feel weird and also makes me question about how confident I am in this test (of course, if I change the base class on purpose, the tests fail, which is a proof that I can trust them)
Oct
28
comment Should I unit test my subclasses or my abstract parent class?
I read somewhere that one shouldn't use inheritance on tests, I am looking for the source to read it carefully
Oct
28
asked Should I unit test my subclasses or my abstract parent class?
Oct
28
comment Can I check the existence of an annotation in an unit test?
The idea of this annotation is that it tells the container that the bean could be removed. It is unfortunately hard to test this behavior :(
Oct
27
comment Can I check the existence of an annotation in an unit test?
Hi! This is interesting, how would you check the behavior of the @remove annotation, for instance?
Oct
26
accepted Can I check the existence of an annotation in an unit test?
Oct
26
asked Can I check the existence of an annotation in an unit test?
Sep
23
awarded  Popular Question
Aug
21
awarded  Autobiographer
Aug
3
comment Should I, and if so how do I, learn to favour upfront design with abstraction over retrospective removal of repetition?
+1 "You're doing it wrong if you ever tell your boss something like, "It works, but I need a couple more days for refactoring.""
Jun
16
accepted Why is a architecture with anemic models the JavaEE standard?
Jun
5
comment Git(flow) workflow for web development
It seems pretty complex. What I would do in your case is: learn about the original git flow and try to use it, add the complexity as needed. You might find out that it fits your necessities. For instance, you might not need the testing branch (it has no development running into it, you are just using it because the code is under test. You could use tags for that. In my case, development is everything that is "testable". Every programmer that is working on a feature has his/her own branch
May
29
comment verify a defect is a production defect or not
Agree completely. And do not forget that if the defect exists in production, data manipulation may be necessary (updating wrong data generated by the defect)