Isn't this sort of a catch-22?
People are saying I don't get maven, it's too complex.
Now it's time for them to give something back and document it?
How do you propose they do that? Start at the source and pore through
it to explain it? Saying that is sort of a cop-out, IMO.
I think that the
http://docs.codehaus.org/display/MAVEN/Java+5+Annotations+for+Plugins
On 9/13/07, Kyle.Bober [EMAIL PROTECTED] wrote:
I have been using Maven for quite sometime and this is the first JDK6 project
POM I have created. I am running into a compilation issue using the
compiler:compile goal... This
Is this bug *ever* going to be fixed? It's been like this for many months...
Larry
On 7/24/07, Mac-Systems [EMAIL PROTECTED] wrote:
Dennis Lundberg schrieb:
That is odd. Version 2.1 of the plugin does not use Cobertura 1.9.
That has just recently been added to the 2.2-SNAPSHOT version,
Am I the only one that finds it profoundly ironic that a testing tool
is broken? The cobbler's children have no shoes?
Larry
On 7/24/07, Dennis Lundberg [EMAIL PROTECTED] wrote:
Mac-Systems wrote:
I tested 2.0 with an -U (force update)
Again it is broken like shown below.
Then you would
] wrote:
So runtime seems very similar to the compile scope type. Could somebody
please explain the difference?
The Maven documentation seems to imply something about transitive
dependencies, but I don't understand what it's trying to say.
Thanks.
Larry Meadors-2 wrote:
I'd assume that it's
I'd assume that it's there so that you can run your app from the IDE -
that's the behavior I'd expect.
Larry
On 5/16/07, lightbulb432 [EMAIL PROTECTED] wrote:
Why are dependencies with a scope of runtime added to Eclipse's .classpath
file? I thought the point of runtime is that it's not a
I am trying to use the build number plug-in:
http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html
I changed my pom to use
${project.artifactId}-${project.version}-r${buildNumber} as the final
name, and it works great for all of the files built, but for the pom,
it messes up
On 1/4/07, mraible [EMAIL PROTECTED] wrote:
Is Maven like Ant in that properties are immutable? If so, can I hook into
the lifecycle sooner and set this dao.framework property from the local
pom.xml?
I was thinking the same thing - it sure is acting like that is the case, no?
Larry
I know that for the iBATIS project, we are just starting to use maven,
so are just getting ready to start publishing it.
Larry
On 11/27/06, Javier Leyba [EMAIL PROTECTED] wrote:
Hi
I'm trying to use maven with my projects but I found every jar file I
need is totally older in maven
your
dependency jars. That's what you wanted, right?
Paul
Larry Meadors-2 wrote:
Thanks, Paul - I added that as a file named assembly.xml in the
directory with my pom.xml in it.
I then added this to my pom (in the build/plugins section):
===
plugin
directory for me.
Thanks for your help, people.
Larry
On 11/20/06, Barrie Treloar [EMAIL PROTECTED] wrote:
On 11/21/06, Larry Meadors [EMAIL PROTECTED] wrote:
Hi, I am using maven for the first time, so I apologize if this is a
retarded question, but I can't find it anywhere in the docs.
I
Hi, I am using maven for the first time, so I apologize if this is a
retarded question, but I can't find it anywhere in the docs.
I have an app that is a command line app. I want to create an assembly
that has my jar, along with the other jars that are listed as
dependencies on it.
I tried the
/dependencySets
/assembly
Paul
Larry Meadors-2 wrote:
Hi, I am using maven for the first time, so I apologize if this is a
retarded question, but I can't find it anywhere in the docs.
I have an app that is a command line app. I want to create an assembly
that has my jar, along with the other
13 matches
Mail list logo
