Maven

[Palmeta]

Hi I think weupnp is a great job! But there seems to be a problem with maven.

this works!

org.bitlet
weupnp
0.1.2

but...

org.bitlet weupnp 0.1.3

gives missing artifact.

[abahgat]

How are you specifying your dependency? Version 0.1.3 is available on central here, so I would have expected maven to be able to resolve it just like 0.1.2.

[Palmeta]

I add it to my pom.xml as usual and 0.1.2 resolves fine but 0.1.3 is
missing.

            <dependency>

org.bitlet
weupnp
0.1.2

On Tue, Sep 22, 2015 at 4:59 AM, Alessandro Bahgat <[email protected]

wrote:

How are you specifying your dependency? Version 0.1.3 is available on
central here
https://search.maven.org/#artifactdetails%7Corg.bitlet%7Cweupnp%7C0.1.3%7Cjar,
so I would have expected maven to be able to resolve it just like 0.1.2.

—
Reply to this email directly or view it on GitHub
#18 (comment).

Arlindo Bento

[Palmeta]

I also get :
[Fatal Error] :9:3: The element type "p" must be terminated by the matching
end-tag "

".

quite frequently when I try to port foreward my router.

On Tue, Sep 22, 2015 at 8:29 PM, Arlindo Bento [email protected]
wrote:

I add it to my pom.xml as usual and 0.1.2 resolves fine but 0.1.3 is
missing.

            <dependency>

org.bitlet
weupnp
0.1.2

On Tue, Sep 22, 2015 at 4:59 AM, Alessandro Bahgat <
[email protected]> wrote:

How are you specifying your dependency? Version 0.1.3 is available on
central here
https://search.maven.org/#artifactdetails%7Corg.bitlet%7Cweupnp%7C0.1.3%7Cjar,
so I would have expected maven to be able to resolve it just like 0.1.2.

—
Reply to this email directly or view it on GitHub
#18 (comment).

Arlindo Bento

Arlindo Bento

[abahgat]

Hi Palmeta, 0.1.4 is now available, I'm hoping this should work for you.

Regarding the fatal error you reported in the last comment, at which stage does it happen?
Do you have a stacktrace?

[Palmeta]

Ok I'll try it out as soon as I get the chance.
The error happens intermittently. I'm devising a program which at specific
intervals checks the router for a forwarded port and attempts to forward it
again. I think that the router may at sometimes send back an incomplete
message or a malformed one and the xml parser in weupnp throws the
exception. I'l see if I can manage to catch it but it is probably catching
the exception internally and only printing an error message.

On Thu, Oct 8, 2015 at 5:18 AM, Alessandro Bahgat [email protected]
wrote:

Hi Palmeta, 0.1.4 is now available, I'm hoping this should work for you.

Regarding the fatal error you reported in the last comment, at which stage
does it happen?
Do you have a stacktrace?

—
Reply to this email directly or view it on GitHub
#18 (comment).

Arlindo Bento