The site is on the todo list.
Other then the default reports. Is there anything specific anyone wants to see?
CLI help page
basic api example for crawling
what else ?
On Tue, Jan 18, 2011 at 2:43 PM, Anders Hammar wrote:
> JIRA [1] says http://maven.apache.org/indexer/, but that gives you a
JIRA [1] says http://maven.apache.org/indexer/, but that gives you a page
not found...
/Anders
[1] http://jira.codehaus.org/browse/MINDEXER
On Tue, Jan 18, 2011 at 20:29, Karl Heinz Marbaise wrote:
> Hi,
>
> i've got a question about the Maven Indexer.
>
> I can't find a web site for that ? Doe
Hi,
i've got a question about the Maven Indexer.
I can't find a web site for that ? Does exist a web site about that
where are some informations are summarized etc. ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl H
Applied, thanks.
For future reference, we typically process patches by first attaching them to
JIRA at http://jira.codehaus.org/browse/MNG
Cheers,
Brett
On 18/01/2011, at 9:04 PM, Stanislav Ochotnicky wrote:
> Hi,
>
> ReactorReader used ArtifactUtils in some places, but in others created
> ke
Hi,
ReactorReader used ArtifactUtils in some places, but in others created
keys/versionless keys on its own. This inconsistency could cause
problems in the future. Attached patch fixes this problem.
--
Stanislav Ochotnicky
Associate Software Engineer - Base Operating Systems Brno
PGP: 7B08724
Hi Lukas,
Lukas Theussl wrote:
> Anders Hammar wrote:
>> On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
>>
>>>
>>> Ok, I get it. The xdoc should be written with the same encoding that is
>>> used when it is read to generate the final report, which is
>>> project.build.sourceEncoding (by def
I'll attach to MPLUGIN-180. Please reopen that.
/Anders
On Tue, Jan 18, 2011 at 09:10, Lukas Theussl wrote:
>
>
> Anders Hammar wrote:
>
>> On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
>>
>>
>>> Ok, I get it. The xdoc should be written with the same encoding that is
>>> used when it is
Anders Hammar wrote:
On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
Ok, I get it. The xdoc should be written with the same encoding that is
used when it is read to generate the final report, which is
project.build.sourceEncoding (by default).
No, it shouldn't. The xdoc xml file shou
On Mon, Jan 17, 2011 at 08:48, Lukas Theussl wrote:
>
> Ok, I get it. The xdoc should be written with the same encoding that is
> used when it is read to generate the final report, which is
> project.build.sourceEncoding (by default).
>
>
No, it shouldn't. The xdoc xml file should be written with
