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 c
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 do
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 P
We handled this problem by creating a parent POM that all of our
projects inherit from with the following:
maven-compiler-plugin
1.5
1.5
Then in the individual project you add:
parent-artifact-name
com.my.group
1.0
In
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 see
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:
maven-compiler-plugin
1.6
1.6
true
$
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
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
Which version of the assembly plugin are you using? They recently
released a new version of it. I couldn't get rid of the junit folder by
the method you described so I reverted back to the last non-beta
version.
Trevor Spackman
-Original Message-
From: [EMAIL PROTECTED] [m
p to 2.1.2-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 PROTEC
Looks like you need to tell the pom where the scm is...
I have something like this in my pom.
...
scm:svn:http://example.com/artifactId/trunk
...
Trevor Spackman
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007
elopment version for "Project 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
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). Th
13 matches
Mail list logo
