- The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC.
-
Tags
agile aix ant automation bug tracking convention data dependency injection design pattern eclipse encapsulation eXtreme Programming factory fix gnu/linux gwt html java javafx jsp jvm log mvc osgi parameter object perforce performance pipe refactoring reflection regexp service strange struts subversion TDD tennis tomcat visitor vpn webapp xacml xml xp studio xsltTwitter
- RT @macgirlsweden #XACML engine evaluates the policy & w/ low risk level allows edit but w/ higher level removes edit or hides doc #mmtm12 1 day ago
- RT @johjak #mmtm12 Jeroen starting demo of #xacml policy-based security; risk-adative security. Interesting! #emcworld #documentum 1 day ago
- RT @macgirlsweden #XACML Components being shown #mmtm12 #documentum http://t.co/Va6uqdIq 1 day ago
- RT @turnerkid #mmtm12 reactive dynamic adaptive security model being discussed. Been working with RSA #XACML 1 day ago
- RT @macgirlsweden Argues for a need for dynamic security models - shows off the #XACML engine #mmtm12 #documentum 1 day ago
Tag Archives: ant
Root Cause Analysis
I’ve moved on to a new project recently. It’s quite different from the previous one. Before I worked on a monolythic web application, now we’re using OSGi. As a result, our project consists of a lot of sub-projects (OSGi bundles) … Continue reading
Posted in process
Tagged ant, cause effect diagram, gradle, groovy, osgi, perforce, root cause analysis, subversion
2 Comments
Performance tuning an Ant build
Common advice in the Agile world is to maintain an automated build that runs in under 10 minutes. I doubt anybody would disagree that a faster build is better than a slower one. But how do we keep the build … Continue reading
Using factory classes in Ant tasks
So you have this nice factory class that prevents your client code from knowing the implementation class of the instances it needs to create and that lets it program to an API only. Of course, at some point somebody needs … Continue reading
Automated distribution creation (4)
In this series of posts, I talked about my continuing quest for the fully automated creation of a distribution for our product. I talked about downloading release notes from our issue tracker and how to add those to our NEWS … Continue reading
Posted in Environment
Tagged ant, automation, cms, cruise control, manual, subversion
Leave a comment
Automated distribution creation (3)
In previous posts, I talked about my continuing quest for the fully automated creation of a distribution for our product. First, I talked about downloading release notes from our issue tracker. Then I showed how to add those to our … Continue reading
Automated distribution creation (2)
In my previous post I talked about how I managed to automatically download the release notes from our issue tracker web site. These notes still needed adding to our NEWs file, which describes the changes between releases. There are really … Continue reading
Automated distribution creation
So we have this automated build with CruiseControl. It generates code, compiles, deploys, and tests. It’s saved my skin a gazillion times. It’s really great. But it could be even better. It could also build a complete distribution, making the … Continue reading
