Good point. It seems JIRA is setup not to allow public signup. Who in Maven
Land can help him?
On Tue, Jan 28, 2014 at 2:37 PM, Omair Majid wrote:
> * Paul Benedict [2014-01-28 15:34]:
> > Your best course is to create a new ticket for the Maven Javadoc plugin,
> > and then attach your patch t
Hi,
It was possible historically, but I think it was disabled due to spamming
issue.
Anyway, the best way to create an account on codehaus is by using xircles:
http://xircles.codehaus.org/signup
This will help you have only one account for jira and possibly the other
services of Codehaus.
HTH
Ch
* Paul Benedict [2014-01-28 15:34]:
> Your best course is to create a new ticket for the Maven Javadoc plugin,
> and then attach your patch to the ticket:
> http://jira.codehaus.org/browse/MJAVADOC
Thanks for the pointer. Filing a bug was my first thought too, but I
don't have an account on jira.
Oliver,
Your best course is to create a new ticket for the Maven Javadoc plugin,
and then attach your patch to the ticket:
http://jira.codehaus.org/browse/MJAVADOC
Paul
On Tue, Jan 28, 2014 at 2:14 PM, Omair Majid wrote:
> Hi,
>
> One of the projects that I am working on has a fairly large ex
Hi,
One of the projects that I am working on has a fairly large exclude list
for javadoc packages. maven-javadoc-plugin requires me to put this in
on line in the pom, which makes it very hard to read. I think it would
be nicer to allow separating the items in the list with newlines and
other white
Thanks for the additional feedback and suggestions. Responses inline below.
Gary
> -Original Message-
> From: Jason van Zyl [mailto:ja...@takari.io]
> Sent: Monday, January 27, 2014 1:14 PM
> To: Maven Developers List
> Subject: Re: SPDX Maven Plugin
>
>
> On Jan 27, 2014, at 3:35 PM, G
Right o, thanks.
On Jan 28, 2014, at 2:35 AM, Kristian Rosenvold
wrote:
> I had a solution for this problem using @Named, but i had trouble getting
> it to work, I probably did something wrong. I'll give it one more shot.
> Just move the issue along if I don't fix it by the time you cut the rel
Hi all,
I created ARCHETYPE-456 yesterday for m-archetype-p to support comparing
directories for integration-testing ignoring the EOL/newline encoding [1].
Currently, I put that code directory in the plugin. But I guess it'd better
be placed alongside already existing IOUtil.contentEquals() method
