Hi All,
Responses inline.
On Wed, Feb 11, 2015 at 7:35 AM, Allison, Timothy B. <[email protected]>
wrote:
> I'm working behind a proxy and getting a new proxy error ("proxy
> unacknowledged") with r1658847 on tika-server package.
>
That seems odd... Would adding another pluginRepository cause that?
>
> -----Original Message-----
> From: Nick Burch [mailto:[email protected]]
> Sent: Wednesday, February 11, 2015 6:18 AM
> To: [email protected]
> Subject: Re: svn commit: r1658847 - /tika/trunk/tika-server/pom.xml
>
> On Wed, 11 Feb 2015, [email protected] wrote:
> > + <pluginRepositories>
> > + <pluginRepository>
> > + <id>miredot</id>
> > + <name>MireDot Releases</name>
> > + <url>http://nexus.qmino.com/content/repositories/miredot</url>
> > + </pluginRepository>
> > + </pluginRepositories>
>
> I'm not sure we're allowed to have other repositories defined in our poms?
> We're certainly strongly encouraged not to, as part of the Maven Central
> sync rules:
>
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html#FAQ_and_common_mistakes
>
I see your point. But, Miredot (and its parent company, qmino) is fairly
established. Maybe we can reach out to the company and see if they could
publish to Central? Since it's not OSS, I'm not sure if/how that would work.
> Is there an alternative?
>
As in an alternate documentation generating service? There is Apiary, but
the generated docs wouldn't be Apache hosted. Miredot still seems to be the
best -- formatting, usability, etc.
>
> Nick
>
