The MANIFEST.MF file contains this content:
"Vaadin-Widgetsets: de.steinwedel.messagebox.WidgetSet"
So when I build Widgetset for my Vaadin app, it will look for "de.steinwedel.messagebox.WidgetSet" automatically.
And the compliler fails, with error message:
"Unable to find 'de/steinwedel/messagebox/WidgetSet.gwt.xml' on your classpath"
I searched this WidgetSet file, found it in the source files, but it is not released into the jar file.
Is this the reason why Widgetset compliler fails?
My suggestion:
(1)Release this WidgetSet file to the jar file.
OR
(2)Is this WidgetSet file used anywhere in this add-on?
If not, can you just delete it totally?
And then, delete the Widgetset declaration from the MANIFEST.MF file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks alot for your good feedback, because it helps me to improve the quality of the addon.
I have no idea, why I had added the WidgetSet.gwt.xml to the MANIFEST.MF. Anyhow, I have released V3.0.3 without a WidgetSet declaration inside the MANIFEST.MF.
I would be glad about your feedback, if the new version works for you or not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have no idea, why I had added the WidgetSet.gwt.xml to the MANIFEST.MF
If I remember correctly, The widgeset file was in your add-on since the old 2.x version.
But somehow it was not released into the jar file of 3.x version
And this cause the compiler fails because it need the widgeset but can not found it.
I upgraded to the latest v3.0.3, the Widgetset declaration in the MANIFEST.MF file is gone. And the Widgetset of my Vaadin app can be compiled correctly now.
Thanks very much
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looks like this add-on depends on "vaadin-client-compiler".
And this dependency propagates to my Vaadin app, make my app depends to this compiler too (at the default scope).
Since you have deleted the Widgetset file, I think the add-on will need this compiler no longer.
Am I right?
If I am right, can you please delete this dependency?
I can block this dependency in my app, by setting the dependency scope.
But if you can kindly it from the add-on, my dependency setting file will be a little better looking.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have removed most of the dependencies, because they seems not to be required. I leave the specific version 7.5.5 for vaadin, because I expect, that the conflict manager of ivy and maven will solve the problem correctly, if you refer a newer version of vaadin. If I use a version range, maven will download the pom.xml of all available published vaadin versions. That takes a long time and is not reasonable.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can not build Widgetset
In the latest version(3.0.2):
The MANIFEST.MF file contains this content:
"Vaadin-Widgetsets: de.steinwedel.messagebox.WidgetSet"
So when I build Widgetset for my Vaadin app, it will look for "de.steinwedel.messagebox.WidgetSet" automatically.
And the compliler fails, with error message:
"Unable to find 'de/steinwedel/messagebox/WidgetSet.gwt.xml' on your classpath"
I searched this WidgetSet file, found it in the source files, but it is not released into the jar file.
Is this the reason why Widgetset compliler fails?
My suggestion:
(1)Release this WidgetSet file to the jar file.
OR
(2)Is this WidgetSet file used anywhere in this add-on?
If not, can you just delete it totally?
And then, delete the Widgetset declaration from the MANIFEST.MF file.
Hello LiYing,
thanks alot for your good feedback, because it helps me to improve the quality of the addon.
I have no idea, why I had added the WidgetSet.gwt.xml to the MANIFEST.MF. Anyhow, I have released V3.0.3 without a WidgetSet declaration inside the MANIFEST.MF.
I would be glad about your feedback, if the new version works for you or not.
If I remember correctly, The widgeset file was in your add-on since the old 2.x version.
But somehow it was not released into the jar file of 3.x version
And this cause the compiler fails because it need the widgeset but can not found it.
I upgraded to the latest v3.0.3, the Widgetset declaration in the MANIFEST.MF file is gone. And the Widgetset of my Vaadin app can be compiled correctly now.
Thanks very much
A little more question.
Why this add-on depends on "vaadin-client-compiler"?
I am using this add-on via the dependency management tool Apache Ivy.
(See: http://ant.apache.org/ivy/)
Looks like this add-on depends on "vaadin-client-compiler".
And this dependency propagates to my Vaadin app, make my app depends to this compiler too (at the default scope).
Since you have deleted the Widgetset file, I think the add-on will need this compiler no longer.
Am I right?
If I am right, can you please delete this dependency?
I can block this dependency in my app, by setting the dependency scope.
But if you can kindly it from the add-on, my dependency setting file will be a little better looking.
Thanks.
You are right, the dependency is not required anymore. I g2g remove it in a few minutes.
I have removed most of the dependencies, because they seems not to be required. I leave the specific version 7.5.5 for vaadin, because I expect, that the conflict manager of ivy and maven will solve the problem correctly, if you refer a newer version of vaadin. If I use a version range, maven will download the pom.xml of all available published vaadin versions. That takes a long time and is not reasonable.
I upgraded to the latest v3.0.4. It works OK
Thanks very much.
Happy new year~~~
I am using Vaadin v7.5.10.
But looks like Ivy can fix the conflict of dependency version.
So don't worry, It works fine.
Perfect!
I wish you happy new year, too!