Changes between Version 4 and Version 5 of GROUP_DEPLOYMENT_PACKAGES

Timestamp:

07/27/09 16:03:40 (16 years ago)

Author:

deyan

Comment:

--

GROUP_DEPLOYMENT_PACKAGES

@@ -1 @@
-About the installers for the different OSes and links with their tickets:
-
-    * include assembly plugin fixing steps in the design.
-    * write the steps in which zip distribution in hudson will be created.
-    * think about making sophie installer under different OSes. Research different libaries and write down the results. 
-
-
 == Zip Package ==
 Generation of the zip package includes fixing the assembly maven plugin:
@@ -13 +6 @@
  * file sets tags have to be added with the scripts that are used for running the application.
  * two module sets have to be created - for the jars needed for the corresponding edition and for the launcher module. The outputDirectory tag should point to the path where jars have to be located (in modules folder).
+ * the unused dependencies(or at least part of them) should be removed to lower the size of the distribution and to be the correct module dependencies(without transitive ones). In this way there can be real enable/disable of plugins, because they are hardly connected with pom.xml dependencies.
  
 Research has been made and the result is that the workable goal is
@@ -24 +18 @@
 RPM:
  * There is maven plugin which can generate rpm package of our build: http://mojo.codehaus.org/rpm-maven-plugin/ and there is very useful example with the configuration needed: http://mojo.codehaus.org/rpm-maven-plugin/example1.html. It has to be integrated in our project(in plugins/pluginManagement section).
- * The deb packages are more complicated to be done automatically(because maven plugin about this is now under development). But there is a way to convert RPM package to DEB (http://www.howtoforge.com/converting_rpm_to_deb_with_alien). This can be done manually with script but may be hudson cannot generate deb packages automatically (there is possibility for running a script after hudson assembly goal).
+ * The deb packages are more complicated to be done automatically(because maven plugin about this is now under development). But there is a way to convert RPM package to DEB (http://www.howtoforge.com/converting_rpm_to_deb_with_alien). This can be done manually with script but may be hudson cannot generate deb packages automatically (there is possibility for running a script after hudson assembly goal). 
 
 == Hudson Zip Distribution ==