Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change gwt-customuibinder dependency in the pom #26

Closed
GoogleCodeExporter opened this issue Jun 16, 2015 · 5 comments
Closed

Change gwt-customuibinder dependency in the pom #26

GoogleCodeExporter opened this issue Jun 16, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

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
Copy link
Author

Changing to 1.0.0 release

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

  • Changed state: Started
  • Added labels: Milestone-1.0.0
  • Removed labels: Milestone-0.12

@GoogleCodeExporter
Copy link
Author

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

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

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
Copy link
Author

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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant