[cle-release-team] Some more pom issues

[Maurer, Christopher Wayne]

Anthony,
I'm running into some slightly confusing issues as I try to release some of the indies.  Some have been smoother than others and we've been able to work through the problems so far.  This one is a little strange.  We're not sure if it's the result of what we've had to do in the master pom, but I'll lay it out for you and maybe you can enlighten us!

So far, I've gotten the same error in the emailtemplateservice and jsf modules.
https://source.sakaiproject.org/svn/emailtemplateservice/branches/emailtemplateservice-0.6.x
And
https://source.sakaiproject.org/svn/jsf/branches/jsf-2.9.x

For ETS, I switched the parent to the released version of master (2.9.0-b01).  When I try to do a regular 'mvn clean install', I get this error:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

Missing:
----------
1) org.sakaiproject.emailtemplateservice:emailtemplateservice-api:jar:0.6.0-b01

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.sakaiproject.emailtemplateservice -DartifactId=emailtemplateservice-api -Dversion=0.6.0-b01 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=org.sakaiproject.emailtemplateservice -DartifactId=emailtemplateservice-api -Dversion=0.6.0-b01 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
  1) org.sakaiproject.emailtemplateservice:emailtemplateservice-impl:jar:0.6-SNAPSHOT
  2) org.sakaiproject.emailtemplateservice:emailtemplateservice-api:jar:0.6.0-b01

----------
1 required artifact is missing.

for artifact:
  org.sakaiproject.emailtemplateservice:emailtemplateservice-impl:jar:0.6-SNAPSHOT


So, I'm wondering if it's "confused" because the versions specified in master are already at 0.6.0-b01 even though it hasn't been released yet.  And maybe something is trying to use that version rather than it's own local project version?  Perhaps we should change the master to only have the updated version for the modules as we've released them.  It's strange since it didn't happen for the other half dozen or so modules that were successful.
Do you see anything obvious in the poms that should be fixed or any other suggestions?

Chris

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20111216/167b21b7/attachment-0006.html