I discovered that the problem seems to be with the vaadin facet in eclipse. In a project without that, for example a simple base project which offers the vaadin jars for other projects, then the addons not resolved in this project. In a project with vaadin facets activated it works.
This is really strange because everything works fine exept resolving the addons.
VAADIN_BASE is a simple java project in eclipse with ivy activated.
VAADIN_BASE - ivy.xml[code]
<?xml version="1.0"?>
<!DOCTYPE ivy-module [
]>
<!-- The core server part of Vaadin -->
<dependency org="com.vaadin" name="vaadin-server" rev="&vaadin.version;"
conf="default->default" />
<!-- Vaadin themes -->
<dependency org="com.vaadin" name="vaadin-themes" rev="&vaadin.version;" />
<!-- Precompiled DefaultWidgetSet -->
<dependency org="com.vaadin" name="vaadin-client-compiled"
rev="&vaadin.version;" />
<!-- Vaadin client side, needed for widget set compilation -->
<dependency org="com.vaadin" name="vaadin-client" rev="&vaadin.version;" />
<!-- Compiler for custom widget sets. Should not be deployed -->
<dependency org="com.vaadin" name="vaadin-client-compiler"
rev="&vaadin.version;" conf="widgetset-compile->default" />
</dependencies>
Solved the issue.
From withing Eclipse, go to Window → Preferences
Expand the ‘Ivy’ Tree and select ‘Settings’
Set the “ivy settings path” to the loaction of yorur ivysettings.xml.
I went with ${workspace_loc:proj_name/ivysettings.xml} where proj_name is my project pinting to /proj_name/ivysettings.xml (this is also the same place I have my ivy.xml)
Kenneth Njendu:
Solved the issue.
From withing Eclipse, go to Window → Preferences
Expand the ‘Ivy’ Tree and select ‘Settings’
Set the “ivy settings path” to the loaction of yorur ivysettings.xml.
I went with ${workspace_loc:proj_name/ivysettings.xml} where proj_name is my project pinting to /proj_name/ivysettings.xml (this is also the same place I have my ivy.xml)