Labels

.net (1) *nix (1) administration (1) Android (2) Axis2 (2) best practice (5) big-data (1) business-analysis (1) code re-use (1) continuous-integration (1) Cordova-PhoneGap (1) database (2) defect (1) design (3) Eclipse (7) education (1) groovy (2) https (2) Hudson (4) Java (1) JAX-RS (2) Jersey (3) Jetty (1) localization (1) m2eclipse (2) MapForce (1) Maven (12) MySQL (1) Nexus (4) notes (4) OO (1) Oracle (4) performance (1) Perl (1) PL/SQL (1) podcast (1) PostgreSQL (1) requirement (1) scripting (1) serialization (1) shell (1) SoapUI (1) SQL (1) SSH (2) stored procedure (1) STS (2) Subclipse (1) Subversion (3) TOAD (3) Tomcat (4) UML (2) unit-testing (2) WAMP (1) WAS (3) Windows (3) WP8 (2) WTP (2) XML (4) XSLT (1)

Friday, March 25, 2011

Unable to find resource 'xxxxxxxxxxxx:xxxxx:maven-plugin:x.x.x' in repository central

Although one may think to correct this by adding a <repository> specification in the POM file, a closer look at the error messages, including "A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository" may give another clue.  For plugins, a <pluginRepository> specification is required.

Tuesday, March 15, 2011

Deploy to own Maven repository using SSH

  • Maven command:  mvn deploy:deploy-file -DgroupId=<groupId> -DartifactId=<artifactId> -Dversion=<version> -Dpackaging=<e.g. jar or war, etc.> -Dfile=<path to file>-Durl=<e.g. scpexe://your hostname/full file system path to repo on server> -DrepositoryId=<id of repo in settings.xml>
  • References:  Deployment of artifacts in an external SSH command and Deploy Plugin

Requirements gathering/Analysis

Key challenges:
  • Tracking issues, decisions and rationale
  • Transform ambiguity to concrete rules/processes
  • Explaining process logic concisely
  • Closing any loop-holes in process
Tracking issues:

  • Email - organize by project, subject.  Use tags for content that falls into more than one folder
  • Spreadsheet or similar - columns:  Date issue raised, issue, issue ID, resolution, who is addressing, what is resolution pending on, related documents or emails
Explaining process:
  • use of flowcharts, sequence diagrams or swim lane diagrams.  Use case diagrams to summarize and group according to user role
  • number the steps so that they can be talked to and addition explanation can be associated with a given step