Re: RFC: Maven License Verifier Plugin
Hi Karl! It would be nice to have a plugin, that for each dependency checks the META-INF\manifest.mf for Bundle-License entry or tries to guess the licence type from META-INF\LICENSE.txt or META-INF\license files. It would be nice, if plugin takes care of autodetecting of licences of leave dependencies, which are not under our control, but for which we would like to check the license compatibility. It can warn the user, if the license type is not detected and can, for example, allow you to set the license for a given groupId/artifactId (and make this setting project-wide from parent pom). That would be a dream :) Or is it a reality already? Karl Heinz Marbaise wrote on 04/02/2010 00:15: Hi there, i have started with implementing some parts of a new Maven Plugin. The Maven License Verifier Plugin (MLV for short). I would present you the idea of the plugin and would like to know if someone has some suggestions, idea's, comments etc. The basic idea is to check every dependency which is used (incl. transitive dependencies) of a build (during a mvn ..) and see if all artifacts have licenses which are based on the policy (of a company etc.) are allowed ...that's often a point in companies...Some companies says only allowed is the Apache License (for example)... The Plugin will use a configuration file which defines different categories of Licenses (http://site.supose.org/maven-licenses-verifier-plugin/licenses.html). The default configuration will not break a build it will just warn about artifacts which don't have a license defined or which in a particular category (WARN, INVALID or none of them). About what I'm unsure about is where to define the license.xml file (or multiple of them): Option 1: Use a particular folder: src/main/licenses/ and put one or more files in there which will be automatically be loaded. Option 2: Give a single or multiple locations for license.xml files in the configuration section for the plugin. Option 3: Use an URL to define where to download the license.xml file or may be multiple URL's. This could be usefull in Companies to have central location where maintain such files which can be used for every project in a company...(May be it's possible to store that in a repository manager like Nexus ?) Option 4: Use an Artifact which can be created and stored into a Maven repository ? Of course the plugin is configurable in that way to brake the build if you do ...(e.g. failOnWarning like ?)... The other question is how to behave in a reactor build (Multi Module build): - Just have a single Configuration (e.g. in Root) and put the configuration file(s) there (not sure how to handle this technically)... And what is needed as well is to be able to exclude particular artifacts from being checked (excludes...exclude.).. (I have to check how to implement this but this is an other question)... Kind regards Karl Heinz Marbaise -- With best regards, Dmitry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Implementing an installer, which is maven-based
Hi everybody! I am still not sure, what is the best direction for me to solve the following task. Maybe someone on maillist implemented something similar, or knows the technology/approach, that can simplify things. What ideally I want to achieve is: 1. Create a lightweight installator, that will not contain any maven artifacts (or, if not possible, contain all of them). 2. When end user launches the installator, it is asked for some input, which is saved as .property file. 3. Installator then fetches only the artifacts needed (selected by user + those which are obligatory), and replaces the property file(s) in those artifacts. Finally it creates ready to-use WAR package. If you have an example of above -- give me a link, please. That would be great! Right now I see the only way is to create a temporary maven project and after doing steps (1) and (2) launch maven to complete the packaging. Thanks in advance! Dmitry Katsubo wrote on 30/01/2010 16:34: Hi all! Sorry, that my question seems to have been asked in maven user list http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/%3c2fbbcb49-65d3-4258-906f-e252372e9...@massol.net%3e but I have the situation, similar to that. I hope you can help me, as you might know what are the latest approaches to that. I have some service, packaged as .WAR, which is completely build by maven. However, this .WAR file requires customization: I need to package it in different ways, depending on user input. Basically, user should himself select the components, he would like to add to WAR, and define some simple configuration for these components. After the packaging the installer should optionally launch tomcat (or jetty) and start a WAR application. I need to write the installer, that: 1. Asks user for the list of components (=checkboxes) 2. For each component, asks for the configuration options (then to be saved as .property file) 3. Package everything from steps 1 and 2 into WAR file. Dependences should be fetched from publicly available maven repository. 4. Optionally launch tomcat (or jetty) in a background 5. Maybe execute some other script, depending on choices in 1 (like demo application). Let me know, if there is a universal solution for that. Thanks in advance for any hint. -- With best regards, Dmitry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Implementing an installer, which is maven-based
Hi all! Sorry, that my question seems to have been asked in maven user list http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/%3c2fbbcb49-65d3-4258-906f-e252372e9...@massol.net%3e but I have the situation, similar to that. I hope you can help me, as you might know what are the latest approaches to that. I have some service, packaged as .WAR, which is completely build by maven. However, this .WAR file requires customization: I need to package it in different ways, depending on user input. Basically, user should himself select the components, he would like to add to WAR, and define some simple configuration for these components. After the packaging the installer should optionally launch tomcat (or jetty) and start a WAR application. I need to write the installer, that: 1. Asks user for the list of components (=checkboxes) 2. For each component, asks for the configuration options (then to be saved as .property file) 3. Package everything from steps 1 and 2 into WAR file. Dependences should be fetched from publicly available maven repository. 4. Optionally launch tomcat (or jetty) in a background 5. Maybe execute some other script, depending on choices in 1 (like demo application). Let me know, if there is a universal solution for that. Thanks in advance for any hint. -- With best regards, Dmitry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Implementing an installer, which is maven-based
Stephen Connolly wrote on 01/02/2010 11:50: have you tried izpack-maven-plugin? Hi Stephan! I had a look at IzPack shortly, and as I understood, IzPack creates an installer for your maven project. So, your maven targets artifacts have to be packaged before creating an installation. What I ideally need is: 1. Create a lightweight installator, that will not contain any maven artifacts (or, if not possible, contain all of them). 2. When end user launches the installator, it is asked for some input, which is saved as .property file. 3. Installator then fetches only the artifacts needed (selected by user + those which are obligatory), and replaces the property file(s) in those artifacts. Finally it creates ready to-use WAR package. If you have an example of above -- give me a link, please. That would be great! Right now I see the only way is to create a temporary maven project and after doing steps (1) and (2) launch maven to complete the packaging. -- With best regards, Dmitry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
