I am not an expert on the Maven side, but on the Groovy side, it looks
like as part of upgrading Groovy from 2.x to 4.0.x, that the
dependency went from the "groovy-all" dependency which includes
"groovy-template" (and other modules) to just the core "groovy"
module:
https://github.com/apache/mave
Looks good.
A small bit of feedback. I tried using it on a project (Groovy) with
an "all" artifact that has no jar - just references other jars. Even
when I specified "pom" it tried to look for the jar
artifact. Despite the error stacktrace it continued and still seemed
to produce the correct res
OK, cool. Is the jline3 integration likely before the final?
Cheers, Paul.
On Fri, Apr 21, 2017 at 8:05 AM, Manfred Moser wrote:
> This is a snapshot (=development) build - so no.
>
> Manfred
>
> Paul King wrote on 2017-04-20 14:30:
>
>> Nice Jason. Is it available
Nice Jason. Is it available via sdkman?
Cheers, Paul.
On Thu, Apr 20, 2017 at 4:08 PM, Jason Dillon wrote:
> Folks, just a quick not that I’ve updated Maven Shell for the latest release,
> can be found with the latest SNAPSHOT:
>
> https://oss.sonatype.org/content/repositories/snapshots/com/pla
You will have to make your own assessment but most new projects I see in my
customer base are moving over to gradle. It offers the same convention over
configuration advantages of Maven but with some flexibility if you need it,
plus a whole swag of benefits that are gradle specific. The dependency
I would also recommend gradle for your circumstances. If you were thinking
of using ant, all the ant tasks are available for your in gradle but it has
maven's style of convention over configuration for the part's like building
Java code which have a well-defined lifecycle.
Cheers, Paul.
On Thu, M
So would you describe the Aether Ant Tasks as almost a drop in
replacement for the (dependency resolution part of the) Maven Ant
Tasks?
Thanks, Paul.
On Tue, Sep 20, 2011 at 10:23 AM, Jason van Zyl wrote:
> The resolution logic for Maven 3.x is done by Aether, so you may want to look
> at the A
Codehaus have been upgrading servers over the past few weeks.
On Thu, Aug 18, 2011 at 7:51 AM, Siegfried Goeschl
wrote:
> Hi John,
>
> if you mean something like
>
> [INFO] [site:deploy {execution: default-deploy}]
> https://dav.codehaus.org/mojo/webtest-maven-plugin - Session: Opened
> Aug 17, 2
OK, thanks, in my scenario I can't assume that Maven 2/3 will be installed
and there typically won't be a pom file either. I guess I'll await 2.2.2
(or more specifically a new m.a.t release) with hopefully a fix for:
http://jira.codehaus.org/browse/MANTTASKS-213
I'll look at a hacked solution in t
Thanks Stephen, where can I find out more info about "forking Maven 3"?
To give some context, I am trying to resolve this bug in the Groovy jira
(2.1.3 still has this problem):
http://jira.codehaus.org/browse/GROOVY-4562
My guess is that we may be hitting:
http://jira.codehaus.org/browse/MNG-4738
Hi,
I was trying to find where in a snapshot repo or source repository
the latest version of the maven ant tasks reside?
Thanks, Paul.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-ma
Hi,
I couldn't find any info regarding the status of the ant maven tasks
wrt to the 2.0.5 release. Are the ant tasks still at 2.0.4?
Cheers, Paul.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
12 matches
Mail list logo
