> If I think of further documentation improvements should I add them to the
> same ticket, or create separate ones.
IMO it depends if the are related or not. Also, working with several
smaller tickets is easier than one huge one. When it comes to
documentation it's hard to give a good guideline, b
Wanted to add a "plug" for the versions-maven-plugin
org.codehaus.mojo
versions-maven-plugin
1.2
the goal "versions:display-plugin-updates" will let you know if any
plugins that you are referencing have more recent versions
versions:display-dependency-updates
and
versions:display-property
Done!
http://jira.codehaus.org/browse/MANIMALSNIFFER-21
If I think of further documentation improvements should I add them to
the same ticket, or create separate ones.
Cheers, Eric
On 2011-10-11 12:31 AM, Anders Hammar wrote:
I believe Stephen answered (1) for me quite elegantly. It would h
OK, 1.7 works much better - thanks.
Finally now that I have it working I can understand better what it does
and how it is useful.
Thank you to everyone who helped, and for being patient with me.
Cheers, Eric
On 2011-10-11 6:25 AM, Stephen Connolly wrote:
Well first off, try upgrading the ve
Well first off, try upgrading the version of
animal-sniffer-maven-plugin to latest...
The signatures (and their site) were generated when 1.3 was the latest...
1.7 has a number of important fixes, but without regenerating the
signatures it is hard to get the site updated to say the version of
ani
So, if what I want is to avoid calling any Java 6 methods I would use
org.codehaus.mojo
animal-sniffer-maven-plugin
1.3
check-java16
test
check
org.codehaus.mojo.signature
java16
1.0
When I run this I gets tons of error messages that gives me the
impression something is not configur
> I believe Stephen answered (1) for me quite elegantly. It would help
> tremendously if his explanation were documented on the introduction page.
> I'm not sure if sniffer solves (2) which really was my original intent
> because I had already solved (1) by other means.
Eric, if you file a ticket
The following is probably too late to be useful.
In my foggy memory, my sense is that the exception error message for
the class format error identifies a class name. Under normal
conditions, it's not terribly hard to map a class name to a jar.
Personally, I use grep, because ZIP files (JAR files b
OK, that page is really clear and helps a lot. Thanks.
Unfortunately I do not see any easy way to navigate there from the
sniffer site. That would be a very valuable link to add under the
examples section.
Cheers, Eric
On 2011-10-10 1:54 PM, Stephen Connolly wrote:
When you are on a Mac you
On 10 October 2011 22:02, Eric Kolotyluk wrote:
>
>
> On 2011-10-10 1:41 PM, Wayne Fay wrote:
>>>
>>> OK, I still clearly do not understand how sniffer is supposed to work,
>>> and
>>> it does not look like am going to any time soon, even after all these
>>> explanations.
>>
>> A signature is like
On 2011-10-10 1:41 PM, Wayne Fay wrote:
OK, I still clearly do not understand how sniffer is supposed to work, and
it does not look like am going to any time soon, even after all these
explanations.
A signature is like:
char java.lang.String.charAt(int)
Animal sniffer compares the Java code y
nd of match.
Here's the list of available signatures: http://mojo.codehaus.org/signatures/
-Robert
> Date: Mon, 10 Oct 2011 13:49:53 -0700
> From: eric.koloty...@gmail.com
> To: users@maven.apache.org
> Subject: Re: Managing Different Java Versions
>
> Fair enough. At t
When you are on a Mac you cannot compile with a 1.5 JDK...
Have a look at
http://mojo.codehaus.org/signatures/java15/
On 10 October 2011 21:49, Eric Kolotyluk wrote:
> Fair enough. At the time I actually thought I was compiling against 1.5, but
> in fact I still had not finished setting up Maven
Fair enough. At the time I actually thought I was compiling against 1.5,
but in fact I still had not finished setting up Maven properly to do
that, and it was still compiling with 1.6.
- Eric
On 2011-10-10 1:30 PM, Ansgar Konermann wrote:
Am 10.10.2011 22:15, schrieb Eric Kolotyluk:
I am not
On 2011-10-10 1:28 PM, Stephen Connolly wrote:
On 10 October 2011 21:15, Eric Kolotyluk wrote:
OK, I still clearly do not understand how sniffer is supposed to work, and
it does not look like am going to any time soon, even after all these
explanations.
As it is, I am making better progress
> OK, I still clearly do not understand how sniffer is supposed to work, and
> it does not look like am going to any time soon, even after all these
> explanations.
A signature is like:
char java.lang.String.charAt(int)
Animal sniffer compares the Java code you are writing against the
published s
Am 10.10.2011 22:15, schrieb Eric Kolotyluk:
> I am not really sure why no-one recommended this to me in the first
> place as it effective and simple to understand.
Maybe you led the crowd into the wrong direction by claiming: "I am
almost complete reworking things to run on a Java 5 run-time, and
On 10 October 2011 21:15, Eric Kolotyluk wrote:
> OK, I still clearly do not understand how sniffer is supposed to work, and
> it does not look like am going to any time soon, even after all these
> explanations.
>
> As it is, I am making better progress now just by specifying the Java 5
> compile
OK, I still clearly do not understand how sniffer is supposed to work,
and it does not look like am going to any time soon, even after all
these explanations.
As it is, I am making better progress now just by specifying the Java 5
compiler in my maven-compiler-plugin. It complains right away w
> The problem is I cannot figure out the intent of how the sniffer is supposed
> to work - in particular if it will even help with my particular problem. As
> far as I can tell the Hibernate folks have not set up the necessary
> signatures for the sniffer to tell me what I need to know.
You should
At the moment I do not know how to create and submit such patches. If I
did I might be so inclined.
At the moment, however, I am trying to complete a very time critical
project and just need to get things working. I am hope that in 2012,
when I am not working 60 hour weeks, I will be able to l
>> My usual modus operandi is to go looking at a live example of the use
>> of something if I am unclear as to how to use it. This can be an
>> interesting easter-egg hunt.
>
> And I am not even sure where to start the hunt.
Go to Github and search for the plugin name...
https://github.com/search?
That would be greatly appreciated...
Cheers, Eric
On 2011-10-09 4:35 PM, Stephen Connolly wrote:
in fairness i think i wrote most of the docs. Kohsuke's original docs were
less than minimal. most of the docs were written while on public transport
on a shitty little netbook.
i don't currently h
On 2011-10-09 3:14 PM, Benson Margulies wrote:
If you have to support 1.5, the easiest thing to do is eschew the use
of 1.6 features. Just set the compiler plugin options for source and
target of 1.5.
Yes, I have already done that part.
After you do that, you might still want the sniffer, si
What surprised me the most is people complaining about open source
docs, but then very rarely supply any patches for improving them. As
they surely do put time into figuring out how to use the software (and
to write mail complaining), they would be the very best candidates for
fixing the existing d
On Sun, Oct 9, 2011 at 7:35 PM, Stephen Connolly
wrote:
> in fairness i think i wrote most of the docs. Kohsuke's original docs were
> less than minimal. most of the docs were written while on public transport
> on a shitty little netbook.
Well, little did I know. Having met KK's work before, I j
in fairness i think i wrote most of the docs. Kohsuke's original docs were
less than minimal. most of the docs were written while on public transport
on a shitty little netbook.
i don't currently have the time to prettify the docs further, and when i
have time i want to sort out the versions-maven
If you have to support 1.5, the easiest thing to do is eschew the use
of 1.6 features. Just set the compiler plugin options for source and
target of 1.5.
After you do that, you might still want the sniffer, since this does
not stop you from accidentally coding calls to methods introduced in
1.6.
On 9 October 2011 17:08, Eric Kolotyluk wrote:
> Thanks for the info Brett. The rest of my response is not directed at you,
> I just need to vent after trying to understand animal-sniffer.
>
> The documentation for the animal-sniffer-maven-plugin is terrible - in
> particular the examples are aby
Thanks for the info Brett. The rest of my response is not directed at
you, I just need to vent after trying to understand animal-sniffer.
The documentation for the animal-sniffer-maven-plugin is terrible - in
particular the examples are abysmal. How are people supposed to learn
how to use it -
On 09/10/2011, at 11:25 AM, Eric Kolotyluk wrote:
> I've been using Maven for about 6 months now so I am still a big green.
>
> Recently I discovered that my project needs to be compatible with client code
> that requires Java 5, because it needs to run on OS 10.5 32-bit Intel.
> Unfortunately
31 matches
Mail list logo