search

tony1223 / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

Jetty pulls all jars in maven dependency hierarchy instead of resolved dependencies #45

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Jetty is pulling all jars from maven dependencies instead of resolved
dependencies. I did not notice this until recently when it started pulling
in different versions of struts2 jars and the application initialization
would fail. I had to manually change .classpath file to point to individual
jars rather than having it determined by maven. The same configuration runs
fine with the command mvn:jetty run.

What steps will reproduce the problem?
I am running a war with just 1 change from the standard launch config. 
Added spring-agent.jar as a VM argument. Classpath is also default. (which
lists maven dependencies, which are resolved dependencies)

What is the expected output? What do you see instead?
I expect the project class loader to load only resolved dependencies rather
than all dependencies.

What version of the product are you using? On what operating system?
1) Run Jetty Run 1.1.1
2) Eclipse --3.5 (buildId=M20090917-0800) 
3) Windows vista enterprise edition
4) Jdk 1.5/1.6
5) m2eclipse plugin (http://m2eclipse.sonatype.org/installing-m2eclipse.html) 
6) maven version --2.2.1

Please provide any additional information below.

Please let me know if this information is insufficient or not clear.

Original issue reported on code.google.com by vijaysag...@gmail.com on 24 Mar 2010 at 9:58

GoogleCodeExporter commented 9 years ago 
Currently I know a defect for RJR load all the maven dependency , 
including the "optional" Jar files.

It's not a easy one for some reason.

1.RJR is not count on M2E , so it's hard to get the information here.
  so far I don't find good way to check the dependency.
2.It's hard to trace it all for the detail.

Anyway ,I know it's bothering us , will try to find a solution or a temp 
workaround for it as a top priority.

Hope we could get it in 1.2 or 1.2.1

Original comment by tonylovejava on 9 Mar 2011 at 10:43

GoogleCodeExporter commented 9 years ago

Original comment by tonylovejava on 9 Mar 2011 at 10:44

GoogleCodeExporter commented 9 years ago 
Move this to 1.2.1 milestone.

Original comment by tonylovejava on 11 Mar 2011 at 12:04

GoogleCodeExporter commented 9 years ago 
I have opted to use M2Eclipse and it solves this problem. Thanks for looking 
anyway.

Original comment by vijaysag...@gmail.com on 11 Mar 2011 at 12:30

GoogleCodeExporter commented 9 years ago 
I found I misunderstood this defect , and I couldn't reproduce this one. 
Change to more-info.

Original comment by tonylovejava on 14 Mar 2011 at 1:25

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
This one might be related to  Issue #52  which will fix in 1.2.1

Original comment by tonylovejava on 15 Mar 2011 at 5:39

GoogleCodeExporter commented 9 years ago 
We fix another similar issue in Issue 81.

Original comment by tonylovejava on 1 Jul 2011 at 8:36