[
http://issues.ops4j.org/browse/PAXURL-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038#action_14038
]
Toni Menzel commented on PAXURL-94:
-----------------------------------
So this needs an API change, right ?
Well we are close before Pax Runner 1.7 and Exam 2.0.
You think we should include this change?
I mean, the public API of a Pax URL Handler is.. the url string format. if you
ask me.
Pax URL API is defined by that. Everything else is usually internal api.
If so, Pax URL 1.2.6-SNAPSHOT will be released as 1.3.0 without a problem.
> CLONE -Fix typo on method
> org.ops4j.pax.url.commons.handler.ConnectionFactory#createConection
> ---------------------------------------------------------------------------------------------
>
> Key: PAXURL-94
> URL: http://issues.ops4j.org/browse/PAXURL-94
> Project: Pax URL
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Fix For: 2.0.0
>
>
> This commit does this already
> https://github.com/ops4j/org.ops4j.pax.url/commit/593fca640f81a450ac7e3ee8ef3c0f457611ae9d
> (see PAXURL-91). BUT, although internally this commit changes the contracts
> --> should be done in 2.0. It requires at least a new release of pax-runner
> too (and pax-eam too I'm afraid)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
