Wine is a software to allow running Windows applications in Linux, MAC etc. platforms. It is available for installation from package managers like yum (RHEL, CentOS) and apt (Ubuntu). You can find more details on how it works in Wine wiki . But the default Wine package available from package manager does not have support for 32 bit Windows applications. This was the case for me. In Redhat Enterprise Linux 7.3, the wine package did not contain support for 32 bit windows applications. So the only option was to build a separate rpm of wine which will include this support. All the steps are executed on a RHEL 7.3 VM (x86_64). Step 1 Download and run shell script which will make wine 64 and 32 support for RHEL: https://github.com/zma/usefulscripts/blob/master/script/install-wine-i686-centos7.sh It accepts a version no. as CLI parameter e.g. 2.0.3 The script installs wine in /usr/local/ directory by default. We can verify the files that are being copied for wine using "...
Maven is a popular software project management tool. It is used heavily for building you project deliverables. More information about maven can be found here.
Maven works on the dependency concept. It essentially means that every project should identify its required artifacts. These artifacts can be found in repositories. Repository is a central place where you keep all your required jars (or other resources). There is a specific structure required to put your artifacts into the repository. We can not just copy every thing at same place. To identify a resource through dependency mentioned in pom.xml, maven looks for the specific structure. Also ther should be a.POM file at the same location of the artifact.
Normally the artifacts generated by maven build comes with the POM for it. So that, any other project wanting to use this artifact can do that. But if the artifact is created from a build other than maven (e.g. ant, Makefile etc), it will not have the POM generated. So this artifact can not be readily used by maven. We need to use the below command to generate a POM for a 3rd party artifact which does not come with a POM by default.
mvn install:install-file -DgroupId=group-id \
-DartifactId=artifact-id \
-Dversion=version \
-Dpackaging=packaging \
-Dfile=fileToInstall \
-DgeneratePom=true
Here groupId is a string that identifies the product group. artifactId is the string to identify the artifact from its group. version is the artifact version. packaging is the file type of the artifact (e.g. jar). file attribute holds the complete path to the artifact in your local system. generatePom attribute creates the POM for this artifact.
This command will create the required directory structure for your 3rd party artifact and generate a POM for it. The output will be copied to your local repository. Now you can use this dependency in your POM to build your project.
Maven works on the dependency concept. It essentially means that every project should identify its required artifacts. These artifacts can be found in repositories. Repository is a central place where you keep all your required jars (or other resources). There is a specific structure required to put your artifacts into the repository. We can not just copy every thing at same place. To identify a resource through dependency mentioned in pom.xml, maven looks for the specific structure. Also ther should be a
Normally the artifacts generated by maven build comes with the POM for it. So that, any other project wanting to use this artifact can do that. But if the artifact is created from a build other than maven (e.g. ant, Makefile etc), it will not have the POM generated. So this artifact can not be readily used by maven. We need to use the below command to generate a POM for a 3rd party artifact which does not come with a POM by default.
mvn install:install-file -DgroupId=group-id \
-DartifactId=artifact-id \
-Dversion=version \
-Dpackaging=packaging \
-Dfile=fileToInstall \
-DgeneratePom=true
Here groupId is a string that identifies the product group. artifactId is the string to identify the artifact from its group. version is the artifact version. packaging is the file type of the artifact (e.g. jar). file attribute holds the complete path to the artifact in your local system. generatePom attribute creates the POM for this artifact.
This command will create the required directory structure for your 3rd party artifact and generate a POM for it. The output will be copied to your local repository. Now you can use this dependency in your POM to build your project.
Comments
Post a Comment