- This topic has 36 replies, 10 voices, and was last updated 14 years, 6 months ago by
.
-
Posts
-
Denis,
Sorry about the delay, please PM it to me (use the PM button under my posts) and attach it there — also include a link back to this thread so I have context for why I’m receiving the attachment (I get a few a day). Thx!
Same problem here.
I am using MyEclipse 7.1.1 (not 7.0.1) and tried everything explained here without any luck :(.
I think that the “deployer” of myeclipse is not taking into consideration provided scope for dependencies… ¿is that possible?
genuinefafa,
Can you hit the pm button below my post and send me a sample project that can help us reproduce this issue at our end.Thank you.
I am currently using the latest myEclipse 7.5 and am also seeing this issue. I have dependencies listed as provided in my pom and they are being deployed to my server.
Was there any resolution to this thread? Thanks!
hubbardr1,
We have not been able to reproduce this issue at our end. Can you create a brand new MyEclipse Web Project, and manually add a few dependencies as “provided” and then deploy it and see if they get deployed or not. If the behavior doesn’t match the other project, the problem might be somewhere else.Hello there!
I found the answer to my question in the @yahoo spam folder :(.
Is this problem still there? or were you able to ‘fix’ it?
– Yes, I can reproduce the problem
– Yes, I can send you the killer “app” private (or not).If you still need it, i’ll make it for you 😉
If you still need it, i’ll make it for you 😉
We would appreciate it if you could help us reproduce this issue at our end. Can you send us a sample project along with the steps to be followed to reproduce this issue?
I found the answer to my question in the @yahoo spam folder :(.
What was the answer that you found?
Anything come of this? I have 7.5 and a simple war project with provided scope still deploys with provided dependencies. I can send the example to whoever wants it. 🙂
It looks like dependencies marked as provided in the pom are honored correctly but provided transitive dependencies are getting pulled into the deployed app incorrectly… At least for jboss. Take hibernate for example, even if you mark in the war’s pom as provided, if another compile dependency has a (transitively) provided dependency on hibernate, hibernate gets package. Transitive provided dependencies should not be included in the deployed war. Maven treats this correctly when you do a package. But myeclipse includes ALL jars that are on the classpath. That is wrong.
Can someone from myeclipse please respond with an update on this? Is there a work around? Do we have something mis-configured? It doesn’t seem to make any difference which of the maven feature sets (myeclipse vs m2eclipse) I have enabled.
