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=node&node=5790403&i=0>
For additional commands, e-mail: [hidden email]
</user/SendEmail.jtp?type=node&node=5790403&i=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_code&node=5790393&code=ZXVnZW4ucmFiaWlAZ21haWwuY29tfDU3OTAzOTN8MTA1NjEzNjg3MA==>.
NAML
<http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=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.
