On Thu, Apr 14, 2011 at 9:02 AM, Simon Nash <[email protected]> wrote: > ant elder wrote: >> >> On Wed, Apr 13, 2011 at 9:59 PM, Simon Nash <[email protected]> wrote: >>> >>> Raymond Feng wrote: >>>> >>>> Maven sometimes need to resolve the artifact to a range of versions or >>>> the >>>> LATEST. I think the versions in the XML will help in such cases. >>>> >>> Thanks for this explanation. Any ideas on how I can get the other >>> versions >>> added back to these files? >>> >> >> I'm not sure I understand whats happened, looking in the central repo >> now the 1.6.2 release is there and the maven-metadata.xml includes the >> old versions but not the 1.6.2 version, see >> http://repo2.maven.org/maven2/org/apache/tuscany/sca/tuscany-assembly/ >> >> I'd guess that most of the releases we do have used that cp command >> approach so this must have happened before for all those other >> releases and no one has complained. >> >> ...ant >> >> > Yes, that's strange as well but in the opposite way; the maven-metadata.xml > there has all the older releases but is missing the newer ones (1.6.1, > 1.6.2, > 2.0-Beta1 and 2.0-Beta2). > > I'm going to go ahead and add the download page for 1.6.2 and send out the > announcement. If anyone reports any problems caused by these > maven-metadata.xml > discrepancies, we can address them at that time. > > Simon > >
I think that's right Simon. I don't have anything technically useful to add here but back in the day I did repeatedly struggle to use Maven to deploy the released artifacts to the right place. At some point (probably when the instructions were updated) I found that some RMs were just copying up the artifacts and no one was complaining. Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
