Re: What packaging for Jira excel reports with maven?

2014-04-02 Thread Anders Hammar
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

Scanning for Projects... before

2014-04-02 Thread eugene
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.

Re: What packaging for Jira excel reports with maven?

2014-04-02 Thread Ron Wheeler
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

Re: What packaging for Jira excel reports with maven?

2014-04-02 Thread Sebastian Otaegui
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

Re: DependencyTreeBuilder vs. DependencyGraphBuilder

2014-04-02 Thread Stefan Ferstl
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.

Re: Scanning for Projects... before

2014-04-02 Thread Wayne Fay
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:

Re: Scanning for Projects... before

2014-04-02 Thread eugene
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.

Re: Scanning for Projects... before

2014-04-02 Thread Christian Domsch
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

Re: Scanning for Projects... before

2014-04-02 Thread eugene
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.

Re: Scanning for Projects... before

2014-04-02 Thread Christian Domsch
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:

Re: Scanning for Projects... before

2014-04-02 Thread eugene
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

Re: Scanning for Projects... before

2014-04-02 Thread Christian Domsch
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

Re: Scanning for Projects... before

2014-04-02 Thread Curtis Rueden
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

[RESULT] [VOTE] Maven Reactor Plugin - Final Release 1.1 (RETIRED) - Take 3

2014-04-02 Thread Karl Heinz Marbaise
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

Re: Scanning for Projects... before

2014-04-02 Thread eugene
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

Re: Scanning for Projects... before

2014-04-02 Thread Wayne Fay
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

Enforcer plugin

2014-04-02 Thread Mark Eggers
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

Re: Enforcer plugin

2014-04-02 Thread Mark Eggers
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