Vaadin add-on maven-metadata.xml not available

[GoogleCodeExporter]

Vaadin add-on maven-metadata.xml not available

[GoogleCodeExporter]

And if you try to build the whole project, errors rise while trying to download 
vaadin dependencies.

Original comment by [email protected] on 16 Dec 2014 at 8:59

[GoogleCodeExporter]

Error stack begin like this :

[DEBUG] Using connector AsyncRepositoryConnector with priority 100 for 
http://maven.vaadin.com/vaadin-addons
Downloading: 
http://maven.vaadin.com/vaadin-addons/org/vaadin/addon/confirmdialog/2.0.4/confi
rmdialog-2.0.4.pom
[DEBUG] onThrowable
java.net.ConnectException: null to 
http://maven.vaadin.com/vaadin-addons/org/vaadin/addon/confirmdialog/2.0.4/confi
rmdialog-2.0.4.pom
    at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:95)
    at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:381)
    at org.jboss.netty.channel.DefaultChannelFuture.addListener(DefaultChannelFuture.java:148)

Original comment by [email protected] on 16 Dec 2014 at 9:00

[GoogleCodeExporter]

Seems like Vaadin repository is not working very well...
And the version (7.0.1) you're using is a bit old. The last one taht can be 
download is 7.3.6

Original comment by [email protected] on 16 Dec 2014 at 9:12

[GoogleCodeExporter]

Hello jngerbaux, 

Thanks for updating me of this Vaddin issue. I have not try to build the 
project recently, so it could be true. One of down side of external 
dependencies on a company maven repo I guess. If you have a fix, please do send 
a patch.

Thanks!
Zemian

Original comment by saltnlight5 on 16 Dec 2014 at 11:47

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi,


Finally got the project compiling. 
I first try to download confirmdialog 2.0.4 but there's style were errors.

Then I found a Maven conflict. You specify this in the main pom of myshedule 
application:
<build>
... 
    <distributionManagement>
        <repository>
       <id>local-m2-repo</id>
        <url>file:///${user.home}/.m2/repository</url>
            <uniqueVersion>true</uniqueVersion>
    </repository>
     </distributionManagement>
...
</build>

It think this command overides the main maven user settings for your 
application. Aside putting files in an unautorised place, maven was downloading 
files at this location but seems to be unable to find them back...

As soon as I've removed this command everything went right. I really think it's 
better to respect basic users settings.

I also notice that you create a .myshedule3 directory always in the main user 
directory. Not really fair as this directory is not always available the way it 
is suppose to be. Why working out of the web app directories ? or in specific 
DB tables ?

I'm also missing information on how to setup jobs...
Anyway it works. Thanks.

Original comment by [email protected] on 17 Dec 2014 at 2:34