Re: What packaging for Jira excel reports with maven?
I categorize different usage of Maven into two categories: A) As a build tool B) As a utility tool A) would be for example building a Java web application, i.e. using the full build lifecycle of Maven. B) on the other hand is where you just want to do one specific thing, for example generate Java classes from an xml schema or creating a jar of existing Java classes. So the first question is if your usage would fit into A or B? To narrow things down a little bit, do you want this excel file to be generated as part of the build of your software and then deployed together with that to the repository? If so, it would be A. If you're just trying to find a tool to generate this excel file on demand, we would be in B. My point here is that if you're in category A then Maven is absolutely appropriate. At least if you're building everything else with Maven. But if you're in category B, then Maven is just one of many options you have. I would even go as far as saying that there are simpler solutions, one being a shell script (or Windows batch file) where you just have you Java command with the jar on the classpath and the options to have the excel file generated. Using Maven here would just add an additional dependency (to Maven) which could just complicate things. My two cents, /Anders On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang s...@dod.no wrote: I have access to a Jar-file that contains code that: - Reads an excel file containing a JQL query, the names of the fields from the JQL results to include in excel, as well as the sheets that are to be populated - Talks to Jira, using the Jira REST API, to do the query and extract the results - Exports a new excel file populated with the query results The Jar-file resides in a plexus archive, so I thought that having a small maven project, containing a pom.xml and the template excel spreadshet in src/main/resources/ would be a good match. The idea was that I could: - set the Jar-file containing the excel export code as a dependency - use exec-maven-plugin to run the Jar - have the output of exec-maven-plugin (an excel file) as the build artifact But the idea stopped on that I don't know what packaging should be used for the pom: jar didn't seem appropriate, so I tried pom, but that doesn't do anything (no target directory created). Is maven appropriate for what I'm trying to do? Is there an appropriate packaging to use? Thanks! - Steinar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Scanning for Projects... before
Is it possible running a maven plugin before Scanning for projects... ? -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What packaging for Jira excel reports with maven?
Looks like something that ANT might be good at. Ron On 02/04/2014 6:58 AM, Anders Hammar wrote: I categorize different usage of Maven into two categories: A) As a build tool B) As a utility tool A) would be for example building a Java web application, i.e. using the full build lifecycle of Maven. B) on the other hand is where you just want to do one specific thing, for example generate Java classes from an xml schema or creating a jar of existing Java classes. So the first question is if your usage would fit into A or B? To narrow things down a little bit, do you want this excel file to be generated as part of the build of your software and then deployed together with that to the repository? If so, it would be A. If you're just trying to find a tool to generate this excel file on demand, we would be in B. My point here is that if you're in category A then Maven is absolutely appropriate. At least if you're building everything else with Maven. But if you're in category B, then Maven is just one of many options you have. I would even go as far as saying that there are simpler solutions, one being a shell script (or Windows batch file) where you just have you Java command with the jar on the classpath and the options to have the excel file generated. Using Maven here would just add an additional dependency (to Maven) which could just complicate things. My two cents, /Anders On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang s...@dod.no wrote: I have access to a Jar-file that contains code that: - Reads an excel file containing a JQL query, the names of the fields from the JQL results to include in excel, as well as the sheets that are to be populated - Talks to Jira, using the Jira REST API, to do the query and extract the results - Exports a new excel file populated with the query results The Jar-file resides in a plexus archive, so I thought that having a small maven project, containing a pom.xml and the template excel spreadshet in src/main/resources/ would be a good match. The idea was that I could: - set the Jar-file containing the excel export code as a dependency - use exec-maven-plugin to run the Jar - have the output of exec-maven-plugin (an excel file) as the build artifact But the idea stopped on that I don't know what packaging should be used for the pom: jar didn't seem appropriate, so I tried pom, but that doesn't do anything (no target directory created). Is maven appropriate for what I'm trying to do? Is there an appropriate packaging to use? Thanks! - Steinar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: What packaging for Jira excel reports with maven?
Or ivy if you want dependency resolution On Apr 2, 2014 7:59 AM, Ron Wheeler rwhee...@artifact-software.com wrote: Looks like something that ANT might be good at. Ron On 02/04/2014 6:58 AM, Anders Hammar wrote: I categorize different usage of Maven into two categories: A) As a build tool B) As a utility tool A) would be for example building a Java web application, i.e. using the full build lifecycle of Maven. B) on the other hand is where you just want to do one specific thing, for example generate Java classes from an xml schema or creating a jar of existing Java classes. So the first question is if your usage would fit into A or B? To narrow things down a little bit, do you want this excel file to be generated as part of the build of your software and then deployed together with that to the repository? If so, it would be A. If you're just trying to find a tool to generate this excel file on demand, we would be in B. My point here is that if you're in category A then Maven is absolutely appropriate. At least if you're building everything else with Maven. But if you're in category B, then Maven is just one of many options you have. I would even go as far as saying that there are simpler solutions, one being a shell script (or Windows batch file) where you just have you Java command with the jar on the classpath and the options to have the excel file generated. Using Maven here would just add an additional dependency (to Maven) which could just complicate things. My two cents, /Anders On Tue, Apr 1, 2014 at 2:05 PM, Steinar Bang s...@dod.no wrote: I have access to a Jar-file that contains code that: - Reads an excel file containing a JQL query, the names of the fields from the JQL results to include in excel, as well as the sheets that are to be populated - Talks to Jira, using the Jira REST API, to do the query and extract the results - Exports a new excel file populated with the query results The Jar-file resides in a plexus archive, so I thought that having a small maven project, containing a pom.xml and the template excel spreadshet in src/main/resources/ would be a good match. The idea was that I could: - set the Jar-file containing the excel export code as a dependency - use exec-maven-plugin to run the Jar - have the output of exec-maven-plugin (an excel file) as the build artifact But the idea stopped on that I don't know what packaging should be used for the pom: jar didn't seem appropriate, so I tried pom, but that doesn't do anything (no target directory created). Is maven appropriate for what I'm trying to do? Is there an appropriate packaging to use? Thanks! - Steinar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: DependencyTreeBuilder vs. DependencyGraphBuilder
I haven't had any problems so far. I was just confused by DependencyTreeBuilder's Javadoc. It says that (at least I understood it that way) the dependency graph might differ from the dependency resolution in Maven 3. The same Javadoc references an Issue (MSHARED-167) that was solved two years ago. So I was not sure if differences can still occur or not. According to Hervé's reply, differences can still occur. Cheers, Stefan On Wed, Apr 2, 2014 at 2:49 AM, Martin Gainty mgai...@hotmail.com wrote: Stefan A year ago..Herve says r1469697 maven-dependency-tree is fixed for M3 Is this not the case? Martin Date: Tue, 1 Apr 2014 08:29:20 +0200 Subject: DependencyTreeBuilder vs. DependencyGraphBuilder From: st.fer...@gmail.com To: users@maven.apache.org I'm using the org.apache.maven.shared:dependency-tree library to gather dependency information on my projects. In order to get additional information about version conflicts, I prefer to use DependencyTreeBuilder instead of DependencyGraphBuilder. However, the Javadoc of DependencyTreeBuilder says: Notice that it doesn't fail with Maven 3, but when Maven 2 and Maven 3 don't calculate the same transitive dependency result, the tree calculated with this component is consistent with Maven 2 even if run with Maven 3 (see MSHARED-167) The issue MSHARED-167 [1] was closed in June 2012. So may DependencyTreeBuilder still produce different results than DependencyGraphBuilder or is this not an issue anymore? Cheers, Stefan [1] https://jira.codehaus.org/browse/MSHARED-167 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
Is it possible running a maven plugin before Scanning for projects... ? Probably not. What is your use case? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
I want to delete a directory from local repo before building a multi-module project. I wrote a plugin for that and the directory get deleted indeed, but it gets deleted too late. What I mean: my project Project has a dependency com.test that is not present in local repo. I run mvn clean install. What happens is that maven is scanning for projects and all the dependencies that it needs, downloading them (I guess though artifact resolver) to my local repo. Then my plugin is hooked to the pre-clean phase and it removes the directory .m2/repository/com. Now when Project actually needs dependency com.test for the compile, this dependency is not present (my plugin removed it) and maven fails. Why do I have such a weird case? Imagine I have releases artifacts that actually do not change their version, but do change their contents. Maven will not update my local repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). That is why I first need to remove com.test then kick in the artifact resolver. Thank you, Eugene. -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790400.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
Well, I think maven is the wrong thing to solve this here, since you clearly use maven in a non intended way. In a CI setup, that would be a build task before the maven task would be called. Christian On 02.04.2014 16:09, eugene wrote: I want to delete a directory from local repo before building a multi-module project. I wrote a plugin for that and the directory get deleted indeed, but it gets deleted too late. What I mean: my project Project has a dependency com.test that is not present in local repo. I run mvn clean install. What happens is that maven is scanning for projects and all the dependencies that it needs, downloading them (I guess though artifact resolver) to my local repo. Then my plugin is hooked to the pre-clean phase and it removes the directory .m2/repository/com. Now when Project actually needs dependency com.test for the compile, this dependency is not present (my plugin removed it) and maven fails. Why do I have such a weird case? Imagine I have releases artifacts that actually do not change their version, but do change their contents. Maven will not update my local repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). That is why I first need to remove com.test then kick in the artifact resolver. Thank you, Eugene. -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790400.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
I could not agree more if only I had a choice :) Thx for the comment -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790402.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
Have you tried creating a dependency for you rproject, that does that deleting? If I am not mistaken, dependencies should be downloaded (or attempted to download) for every project in a reactor run. So lets say your project is P and the newly introduced project is M then it would look like: /-+-M (deletes com.test in any of its goals...) | +-P has dependency on com.test and M Christian On 02.04.2014 16:14, eugene wrote: I could not agree more if only I had a choice :) Thx for the comment -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790402.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
Well.. there are a lot of projects like this.. My plugin is actually inside the maven's super pom from maven-model-builder jar And it gets invoked once per project (even if there are multiple modules) I actually wanted a solution that will not trigger any changes in my poms.. On 4/2/14, 5:20 PM, Christian Domsch [via Maven] wrote: Have you tried creating a dependency for you rproject, that does that deleting? If I am not mistaken, dependencies should be downloaded (or attempted to download) for every project in a reactor run. So lets say your project is P and the newly introduced project is M then it would look like: /-+-M (deletes com.test in any of its goals...) | +-P has dependency on com.test and M Christian On 02.04.2014 16:14, eugene wrote: I could not agree more if only I had a choice :) Thx for the comment -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790402.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790403i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790403i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790403.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==. NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790404.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Scanning for Projects... before
And I think here is the problem. As far as I understand maven, what happens with your setup is that maven recognizes the dependency to com.test, then you delete it, after that maven treis to use it e.g. in the compile step which leads to the error. And the reason is that through your setup you call it everytime a project is run in the reactor. What I meant, is that you create a regular project, through dependency mechanisms ensure that it is the very first project to be run (probably multiple ways to achieve that) and so the deletion of com.test is only attempted once. Every other project afterwards should then try to download the plugin because it is not found in the local repo. Maybe may way is flawed as well, since my idea suggests that each project scans the repo uncached. Christian On 02.04.2014 16:25, eugene wrote: Well.. there are a lot of projects like this.. My plugin is actually inside the maven's super pom from maven-model-builder jar And it gets invoked once per project (even if there are multiple modules) I actually wanted a solution that will not trigger any changes in my poms.. On 4/2/14, 5:20 PM, Christian Domsch [via Maven] wrote: Have you tried creating a dependency for you rproject, that does that deleting? If I am not mistaken, dependencies should be downloaded (or attempted to download) for every project in a reactor run. So lets say your project is P and the newly introduced project is M then it would look like: /-+-M (deletes com.test in any of its goals...) | +-P has dependency on com.test and M Christian On 02.04.2014 16:14, eugene wrote: I could not agree more if only I had a choice :) Thx for the comment -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790402.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790403i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790403i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790403.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==. NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790404.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Scanning for Projects... before
Hi Eugene, Imagine I have releases artifacts that actually do not change their version, but do change their contents. Maven will not update my local repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different version string every time something changes; or B) a SNAPSHOT version. This mutability is the entire purpose of snapshots, and what differentiates them from release versions. Regards, Curtis On Wed, Apr 2, 2014 at 9:09 AM, eugene eugen.ra...@gmail.com wrote: I want to delete a directory from local repo before building a multi-module project. I wrote a plugin for that and the directory get deleted indeed, but it gets deleted too late. What I mean: my project Project has a dependency com.test that is not present in local repo. I run mvn clean install. What happens is that maven is scanning for projects and all the dependencies that it needs, downloading them (I guess though artifact resolver) to my local repo. Then my plugin is hooked to the pre-clean phase and it removes the directory .m2/repository/com. Now when Project actually needs dependency com.test for the compile, this dependency is not present (my plugin removed it) and maven fails. Why do I have such a weird case? Imagine I have releases artifacts that actually do not change their version, but do change their contents. Maven will not update my local repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). That is why I first need to remove com.test then kick in the artifact resolver. Thank you, Eugene. -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790400.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[RESULT] [VOTE] Maven Reactor Plugin - Final Release 1.1 (RETIRED) - Take 3
Hi to all, the vote has passed with the following result: +1 (binding): Hervé Boutemy, Stephen Connolly, Oliver Lamy Many thanks for the support. Kind regards Karl-Heinz Marbaise On 3/30/14 6:17 PM, Karl Heinz Marbaise wrote: Hi, We have solved only a single issue (the final retirement issue): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11831version=20210 Based on my mistake, the files are already on final ASF repository: http://repository.apache.org/content/groups/public/ http://repository.apache.org/content/groups/public/org/apache/maven/plugins/maven-reactor-plugin/1.1/maven-reactor-plugin-1.1-source-release.zip Source release checksum(s): maven-reactor-plugin-1.1-source-release.zip sha1: a05d38771ae05f1323e474f9562aea0f2dc59898 Staging site: http://maven.apache.org/plugins-archives/maven-reactor-plugin-LATEST/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl-Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Scanning for Projects... before
I still attempt the deletion only once, that is already implemented inside my plugin and it does not work :( On 4/2/14, 5:32 PM, Christian Domsch [via Maven] wrote: And I think here is the problem. As far as I understand maven, what happens with your setup is that maven recognizes the dependency to com.test, then you delete it, after that maven treis to use it e.g. in the compile step which leads to the error. And the reason is that through your setup you call it everytime a project is run in the reactor. What I meant, is that you create a regular project, through dependency mechanisms ensure that it is the very first project to be run (probably multiple ways to achieve that) and so the deletion of com.test is only attempted once. Every other project afterwards should then try to download the plugin because it is not found in the local repo. Maybe may way is flawed as well, since my idea suggests that each project scans the repo uncached. Christian On 02.04.2014 16:25, eugene wrote: Well.. there are a lot of projects like this.. My plugin is actually inside the maven's super pom from maven-model-builder jar And it gets invoked once per project (even if there are multiple modules) I actually wanted a solution that will not trigger any changes in my poms.. On 4/2/14, 5:20 PM, Christian Domsch [via Maven] wrote: Have you tried creating a dependency for you rproject, that does that deleting? If I am not mistaken, dependencies should be downloaded (or attempted to download) for every project in a reactor run. So lets say your project is P and the newly introduced project is M then it would look like: /-+-M (deletes com.test in any of its goals...) | +-P has dependency on com.test and M Christian On 02.04.2014 16:14, eugene wrote: I could not agree more if only I had a choice :) Thx for the comment -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790402.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790403i=0 For additional commands, e-mail: [hidden email] /user/SendEmail.jtp?type=nodenode=5790403i=1 If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790403.html To unsubscribe from Scanning for Projects... before, click here NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790404.html Sent from the Maven - Users mailing list archive at Nabble.com. If you reply to this email, your message will be added to the discussion below: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790405.html To unsubscribe from Scanning for Projects... before, click here http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5790393code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==. NAML http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://maven.40175.n5.nabble.com/Scanning-for-Projects-before-tp5790393p5790419.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Scanning for Projects... before
repo unless their are snapshots, right? Well snapshot is not an option right now (due to corporate things). It is one of Maven's cardinal assumptions that release versions are immutable. If you need different contents, use either: A) a different As Curtis already mentioned, you are unlikely to find a solution by continuing to head in this direction. Find another approach - most likely one that involves a process running outside of Maven before your build kicks off. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Enforcer plugin
Folks, I've gotten my classifier artifact to build and install in our local repository. Specifying the classifier gets the appropriate artifact, and removing the classifier gets the [other] appropriate artifact. Now I'm a bit paranoid that the artifact with the classifier will leak out into other releases, so I thought I would write an enforcer rule. I thought that the following would work: bannedDependencies excludes excludeorg.mdeggers:*:*:*:*:DEBUG/exclude /excludes /bannedDependencies based on: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html While this certainly blocked the following dependency: dependency groupIdorg.mdeggers/groupId artifactIdSampleBuild/artifactId version1.5/version typewar/type classifierDEBUG/classifier /dependency with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:DEBUG:1.5 It also blocked the following dependency: dependency groupIdorg.mdeggers/groupId artifactIdSampleBuild/artifactId version1.5/version typewar/type /dependency with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:1.5 This I did not expect. The messages are also a bit suspect in that they don't match the pattern given in the documentation. I looked on JIRA and found the following (based on another thread): http://jira.codehaus.org/browse/MENFORCER-74 http://jira.codehaus.org/browse/MENFORCER-75 http://jira.codehaus.org/browse/MENFORCER-72 These are all closed with a 'fixed' designation for release 1.3. I'm using version 1.3.1 However, I briefly looked at the code here: http://svn.apache.org/viewvc/maven/enforcer/tags/enforcer-1.3.1/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BannedDependencies.java?revision=1502671view=markup and classifier does not seem to have made it in. Have I walked through this correctly? If so, is there a fix (other than not using classifiers, or just hoping that a DEBUG classifier doesn't make it into a release)? Thanks, Mark /mde/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Enforcer plugin
On 4/2/2014 5:25 PM, Mark Eggers wrote: Folks, I've gotten my classifier artifact to build and install in our local repository. Specifying the classifier gets the appropriate artifact, and removing the classifier gets the [other] appropriate artifact. Now I'm a bit paranoid that the artifact with the classifier will leak out into other releases, so I thought I would write an enforcer rule. I thought that the following would work: bannedDependencies excludes excludeorg.mdeggers:*:*:*:*:DEBUG/exclude /excludes /bannedDependencies based on: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html While this certainly blocked the following dependency: dependency groupIdorg.mdeggers/groupId artifactIdSampleBuild/artifactId version1.5/version typewar/type classifierDEBUG/classifier /dependency with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:DEBUG:1.5 It also blocked the following dependency: dependency groupIdorg.mdeggers/groupId artifactIdSampleBuild/artifactId version1.5/version typewar/type /dependency with the message: Found Banned Dependency: org.mdeggers:SampleBuild:war:1.5 This I did not expect. The messages are also a bit suspect in that they don't match the pattern given in the documentation. I looked on JIRA and found the following (based on another thread): http://jira.codehaus.org/browse/MENFORCER-74 http://jira.codehaus.org/browse/MENFORCER-75 http://jira.codehaus.org/browse/MENFORCER-72 These are all closed with a 'fixed' designation for release 1.3. I'm using version 1.3.1 However, I briefly looked at the code here: http://svn.apache.org/viewvc/maven/enforcer/tags/enforcer-1.3.1/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/BannedDependencies.java?revision=1502671view=markup and classifier does not seem to have made it in. Have I walked through this correctly? If so, is there a fix (other than not using classifiers, or just hoping that a DEBUG classifier doesn't make it into a release)? Thanks, Mark /mde/ Works with 2.0-SNAPSHOT of the maven enforcer plugin. /mde/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
