RE: Default java source version

2007-07-10 Thread Trevor Spackman
We handled this problem by creating a parent POM that all of our projects inherit from with the following: plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin Then in the

RE: How to use dependency:purge-local-repository

2007-07-10 Thread Trevor Spackman
I don't know if this will help, but I never use the dependency plugin to clean out the local repo... I always just delete the ~/.m2/repository/ folder (or some subfolder in it). HTH, Trevor -Original Message- From: Erez Nahir [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 12:55

RE: New Archetype Plugin

2007-07-10 Thread Trevor Spackman
Whether or not you get a new plugin will depend on how you have your plugins defined in your pom -- if you've specified a specific version (probably a good idea) then you'll never get a newer one. If you don't specify a version, then you'll automatically get the latest version whenever it comes

RE: Default java source version

2007-07-10 Thread Trevor Spackman
Sent to the list... -Original Message- From: Severin Ecker [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 10, 2007 10:59 AM To: Trevor Spackman Subject: Re: Default java source version yes i could do that. thing is, many of my/our projects are unrelated and shouldn't have a common

Which technology stack are you using?

2007-07-06 Thread Trevor Spackman
So here's the question: what are YOU using? There have been a number of posts about what CAN be used, but only a couple of people have mentioned what they DO use. Why do I ask? We recently made the jump from CVS ant to Subversion maven. There have been a few growing pains, but things seem

maven-javadoc-plugin error?

2007-07-03 Thread Trevor Spackman
Hi all, So we decided to up the java version from 1.5 to 1.6 in some of our new projects to take advantage of the new features. Accordingly, I added the following to my pom: build plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration

RE: com/oracle/ojdbc14 where are Oracle driver jars?

2007-05-31 Thread Trevor Spackman
I also am waiting for the appearance of these jars... Trevor -Original Message- From: SiSi'mon [mailto:[EMAIL PROTECTED] Sent: Thursday, May 31, 2007 12:41 PM To: users@maven.apache.org Subject: com/oracle/ojdbc14 where are Oracle driver jars? Does anyone know why there are no jars

RE: how to run svn propset from maven ?

2007-05-11 Thread Trevor Spackman
This is probably off-topic for this particular forum, but all you should have to do is create a pre-commit hook for subversion that will prevent said files from being added. I think that should be much, much easier to enforce than using maven. Trevor Spackman -Original Message

RE: Releasing a branch?

2007-04-26 Thread Trevor Spackman
Name?) it should have been automatically defaulted to 2.0.2.2-SNAPSHOT. You're ready to release again without any pom changes. Trevor Spackman -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, April 26, 2007 10:55 AM To: Maven Users List Subject: Re

RE: Re : Build number and current date

2007-04-26 Thread Trevor Spackman
Looks like you need to tell the pom where the scm is... I have something like this in my pom. project ... scm connectionscm:svn:http://example.com/artifactId/trunk/connection scm ... /project Trevor Spackman -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL

RE: Releasing a branch?

2007-04-26 Thread Trevor Spackman
-SNAPSHOT. Then we merge the bug-fixes back down to the trunk. The one manual step in our process is updating the pom in the trunk to 2.2.0-SNAPSHOT after creating the branch. Is there a better way? Trevor Spackman -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent

Issue with assembly:attached (jar-with-dependencies)?

2007-04-21 Thread Trevor Spackman
I've searched the archive and Jira, but I don't see the answer to this one... Using the 2.2-beta-1 version of assembly:attached (jar-with-dependencies), I don't get the pom.properties or pom.xml files that should be in the META-INF folder for the artifact currently being built (= bad idea).