search

jhickman / gxt-uibinder

Automatically exported from code.google.com/p/gxt-uibinder
0 stars 0 forks source link

Change gwt-customuibinder dependency in the pom #26

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Modify the Maven pom dependency to gwt-customuibinder to not use a system path

Original issue reported on code.google.com by jus...@jhickman.com on 20 Apr 2011 at 1:45

GoogleCodeExporter commented 9 years ago 
Changing to 1.0.0 release

Original comment by jus...@jhickman.com on 10 May 2011 at 6:07

GoogleCodeExporter commented 9 years ago

Original comment by jus...@jhickman.com on 11 May 2011 at 3:15

GoogleCodeExporter commented 9 years ago 
The dependency scope now is 'provided'. Please just remove the scope element, 
so Maven can resolve this dependency from repository, too.

Original comment by chrisb0...@gmail.com on 29 Jul 2011 at 9:53

GoogleCodeExporter commented 9 years ago 
I'm not sure if I know what you're saying here.  You are asking for 
gwt-customuibinder to use the default scope?  

It's scoped as 'provided' so that it doesn't come up as a transitive 
dependency.  This dependency is only needed at compile time and not required as 
a server-side library. 

This is the same reason why  com.google.gwt:gwt-user is added with 'provided' 
scope.

Original comment by jus...@jhickman.com on 29 Jul 2011 at 1:04

GoogleCodeExporter commented 9 years ago 
Hmm.... that's why I did set gxt-uibinder's dependency scope to 'provided' in 
MY pom. I would now expect maven to pull in all the stuff gxt-uibinder needs. 
Instead, I have to manually provide the dependency to gwt-customuibinder.

According to this page 
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism
.html, had gwt-customuibinder's scope been 'compile' in YOUR pom, it would have 
worked as expected...

Original comment by chrisb0...@gmail.com on 31 Jul 2011 at 12:14