[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696274#comment-14696274
]
Chris Graham commented on MPIR-234:
---
"So the question becomes what do we put on the Source
[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696261#comment-14696261
]
Chris Graham commented on MPIR-234:
---
"it's a general contract that should be enforcer for
[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14696247#comment-14696247
]
Chris Graham commented on MPIR-234:
---
I see a general drift towards a Git centric discussio
Hi Lukas: nice to se that it has catched your interest :)
Yes, DOXIA-436 is the ideal, where we completely remove any Xhtml intermediate
The idea here is less ambitious: just avoid extending XhtmlParser, since the
source is not Xhtml/Xml
But of course, don't hesitate to help!
Regards,
Hervé
see related https://issues.apache.org/jira/browse/DOXIA-436
Greetings! :)
-Lukas
Am 12.08.2015 um 23:54 schrieb herve.bout...@free.fr:
now that you told it, I'd seriously prefer change Doxia Markdown parser to use
an XhtmlParser instance internally instead of extending XhtmlParser while
com
IMHO, what is not clear in your explanations is that scm url is not the url of
the repo
scm url is "scm:provider:provider-specific content"
our git scm url is currently weak, since it does not define path in repo: then
just add it, in a location perfectly disctinct from repo url inside the scm
Hi,
I vaguely remember a discussion [1] regarding a too low RTO of 60s which
was increased to a very high value ([2])
Cheers
--
Olivier
[1] http://markmail.org/message/yqlofeoah6bcxb4i
[2] https://issues.apache.org/jira/browse/WAGON-365
On 13 August 2015 at 21:08, Kristian Rosenvold wrote:
> W
We are discussing (in https://issues.apache.org/jira/browse/MNG-5869)
what appears to be a situation where an intermediate proxy sends an
incorrect content-length and the download seems to wait indefinitely
for the complete payload to await. Is there no timeout configured for
a default "get" reques
GitHub user edwardmlyte opened a pull request:
https://github.com/apache/maven-plugins/pull/59
Updated docs URL for shade plugin
Updated due to codehaus repo closing
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/edwardmlyte/mave
[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694875#comment-14694875
]
Hervé Boutemy commented on MPIR-234:
notice that this is what I already did in MPIR-290:
10 matches
Mail list logo