-
1. Re: Backup deployments after jboss-cli DEPLOY command
sfcoy Mar 21, 2015 3:59 AM (in response to garrydias)1 of 1 people found this helpfulMany organisations use something like nexus or artifactory to store versioned copies of jar files, war files, etc in a standard way.
Build tools like Apache Maven and Gradle store the results of their build process in repository managers such as these.
As we always build and release versioned artifacts, we can always grab the previous version and redeploy it.
Subsequently there is no need then for a server based backup process.
-
2. Re: Backup deployments after jboss-cli DEPLOY command
garrydias Mar 24, 2015 12:55 PM (in response to sfcoy)I know these two and I´m using artifactory actually.
My real issue is that my jars can´t carry the version number in their names:
Is a multi-module project containing 15 jars deployed in an wildfly instance and each jar has a jboss-deployment-structure.xml or jboss-all.xml declaring the dependencies between them. If I need to deploy or replace a new module I don´t need to deploy its dependencies with updated dependency declaration in jboss-deployment-structure.xml or jboss-all.xml.
My artifactory issue is that when I perform a mvn release:perform the jar files are stored with the version number in the name.
Maybe I should find a way do deploy to artifactory with {file_name}-{version}.jar and rename it if deploy it as a rollback.