Re: Can't Find Scala Archetype

2014-02-11 Thread Eric Kolotyluk
On 2/11/2014 6:54 PM, Barrie Treloar wrote: On 12 February 2014 13:14, Eric Kolotyluk wrote: I am using the Typesafe Eclipse IDE, and for some reason it cannot find the archetype for net.alchim31.maven scala-archetype-simple 1.5 At one time it could, but now it can't, and I have no idea why.

Re: Can't Find Scala Archetype

2014-02-11 Thread Barrie Treloar
On 12 February 2014 13:14, Eric Kolotyluk wrote: > I am using the Typesafe Eclipse IDE, and for some reason it cannot find the > archetype for > > net.alchim31.maven > scala-archetype-simple > 1.5 > > At one time it could, but now it can't, and I have no idea why. The > diagnostics are completely

Can't Find Scala Archetype

2014-02-11 Thread Eric Kolotyluk
I am using the Typesafe Eclipse IDE, and for some reason it cannot find the archetype for net.alchim31.maven scala-archetype-simple 1.5 At one time it could, but now it can't, and I have no idea why. The diagnostics are completely useless in understanding the problem. Can anyone suggest anyt

Re: maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter

2014-02-11 Thread Barrie Treloar
On 12 February 2014 11:43, Ron Wheeler wrote: > I am trying to build a timesaving module that will build tar files to be > installed on a server > I have defined a bunch of dependencies in the pom and want to build 2 tar > files by invoking 2 instances of the plug-in. > In each one I want to speci

Re: Adding dependency management to parent pom causes errors

2014-02-11 Thread Barrie Treloar
On 12 February 2014 11:51, Laird Nelson wrote: > Agreed wholesale. I think the original poster was wondering why this > stanza: [del] You did a good job there so I didn't add any value to the response. > While we're on the subject of best practices in this area, we've also found > that dependen

Re: Adding dependency management to parent pom causes errors

2014-02-11 Thread Laird Nelson
On Tue, Feb 11, 2014 at 4:48 PM, Barrie Treloar wrote: > This is also best practice. > Agreed wholesale. I think the original poster was wondering why this stanza: ...when "wrapped" (replaced, really) thusly: ** ** ...suddenly {handwave handwave} made his dependencies stop {ha

maven-assembly-plugin:2.4 The following patterns were never triggered in this artifact inclusion filter

2014-02-11 Thread Ron Wheeler
I am trying to build a timesaving module that will build tar files to be installed on a server I have defined a bunch of dependencies in the pom and want to build 2 tar files by invoking 2 instances of the plug-in. In each one I want to specify a list of dependencies to be included from the repo

Re: Adding dependency management to parent pom causes errors

2014-02-11 Thread Barrie Treloar
On 12 February 2014 10:17, Laird Nelson wrote: > First, and foremost, it is template information. If a given real > somewhere else omits a piece of information, then that piece > of information is taken (if possible) from the > section. This is also best practice. Appliying DRY principles you

Re: Adding dependency management to parent pom causes errors

2014-02-11 Thread Laird Nelson
On Tue, Feb 11, 2014 at 12:18 AM, geoffh wrote: > In attempting to identify the cause, I started by just adding dependency > management to my parent pom > Simply adding > > > around the dependencies in my parent pom, causes dependencies not be > resolved > I'm not sure why the developers chose

Adding dependency management to parent pom causes errors

2014-02-11 Thread geoffh
I have a Maven project that has a parent pom and 5 child poms In the initial version each pom had specific dependencies declared All the projects completed the 'mvn clean deploy' build with success I wanted to change this to use the dependency management features - where the parent pom declared

Re: Why is dependency:analyze lying to me?

2014-02-11 Thread Paul Benedict
I am so happy someone brought this up. I actually hit this issue several times but never got around to mentioning it. Please submit a JIRA issue! On Tue, Feb 11, 2014 at 3:41 PM, Barrie Treloar wrote: > On 12 February 2014 07:41, laredotornado-3 > wrote: > > Hi, > > > > I'm using Maven 3.1.1 o

Re: Why is dependency:analyze lying to me?

2014-02-11 Thread Barrie Treloar
On 12 February 2014 07:41, laredotornado-3 wrote: > Hi, > > I'm using Maven 3.1.1 on Mac 10.9.1. When I ran "mvn dependency:analyze" on > my project, I got results that included: > > [WARNING] Unused declared dependencies found: > ... > [WARNING]junit:junit:jar:4.11:te

Why is dependency:analyze lying to me?

2014-02-11 Thread laredotornado-3
Hi, I’m using Maven 3.1.1 on Mac 10.9.1. When I ran “mvn dependency:analyze” on my project, I got results that included: [WARNING] Unused declared dependencies found: … [WARNING]junit:junit:jar:4.11:test So I commented out the above junit dependency in my pom (declar

Re: Best practices for Java EE 7 dependencies

2014-02-11 Thread Wayne Fay
>> > Should I better specify the exact dependencies and investigate some >> > more work in POM maintainance? What would this gain me? >> >> You answered your own question, congrats! :) > > Well, if I got you right, you mean it won't gain me anything. Right? I made no such statement. I was simply a

Re: Best practices for Java EE 7 dependencies

2014-02-11 Thread Martin Hoeller
Hi! Thanks for your answers so far. Am Fri, 7 Feb 2014 11:17:22 -0600 schrieb Wayne Fay : > > Should I better specify the exact dependencies and investigate some > > more work in POM maintainance? What would this gain me? > > You answered your own question, congrats! :) Well, if I got you righ