Hello We are using an open source product in which we found a couple of bugs. We have altered the code and rebuilt locally. We have also reported the issues to the OS project via Jira and submitted our fixes.
While we wait for the issues to be resolve in the GA version of the product we must deploy the locally built(via maven) version to our internal remote repository in order for our developers to use it. Note that the build is of a SNAPSHOT release of the source. We have attempted this in four ways. 1- We copied the artifacts generated by the mvn install for the product from a local repository to the internal remote repository. 2- We did a mvn install of the product on the machine where the internal remote repository is hosted referring to that repository as the local repository. In these 2 cases, when a developer attempts to access the artifacts in the internal remote repository the process fails saying: "[DEBUG] SHA1 not found, trying MD5". There are SHA1 or MD5 files for the artifacts on which this message occurs. After some research we found some posts that indicate these methods were not the way to go so: 3- We attempted to do a mvn deploy of the product by specifying our internal remote repository in the distributionManagement section of the product's main pom. We had to cancel it when it attempted to get the latest build number from the open source project's server which we, of course, do not have access to. 4- We did a deploy-file on an individual artifact but this approach has two problem. First the open source project that we are concerned about is large with many individual jars and poms so we'd rather not have to deploy each one individually. Second when we do this we get a completely different name for the artifact in the internal remote repository that includes a timestamped. As each artifact will have a different timestamp it would be very difficult to keep them all straight in our application's pom. We want to know if it is possible to alter the internal remote repository to make it accessible? We have other projects in our repository that do not have SHA1 files (commons for instance). Can we delete all the meta-data files? If not, given that we do not have access to the build number server, what is the proper way to deploy? We are using Maven 2.0.8. Thanks Tom -- View this message in context: http://www.nabble.com/No-SHA1-for-Locally-Built-Open-Source-Product-tp17064966s177p17064966.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
