As I was surprised by the use case you're describing, I just downloaded a
fresh maven 2.2.1 with default configuration.
Then I created a dumb project with archetype:generate/#15.
Finally, I added the jms dependency:
dependency
groupIdjavax.jms/groupId
artifactIdjms/artifactId
Pleas read
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html. And if
you think something is a bug, file it.
Justin
On Sat, Feb 13, 2010 at 3:45 PM, KARR, DAVID (ATTSI) dk0...@att.com wrote:
-Original Message-
From: KARR, DAVID (ATTSI)
Sent: Saturday, February 13,
Hi,
i've created a new archetype: (the pom.xml)
*groupIdcom.company.maven.archetype/groupId
artifactIdGeneric/artifactId
packagingjar/packaging
version0.0.1/version
nameCompany Generic archetype/name
descriptiondefault archetype for company maven projects/description
parent
Hello,
With the recent release of Checkstyle plugin 2.5, which uses Checkstyle
5.0, the format of the xml config file is not backwards compatible.
I struggled for a bit trying to understand why the checkstyle plugin
reported a Could not find resource:
Problem fixed.
i've used a property in the parent called: classpath.
apparantly this caused errors.
changed it to ctch.classpath and now it works!
great way to create a default project scheme to all the developers.
On Sun, Feb 14, 2010 at 4:07 PM, eyal edri eyal.e...@gmail.com wrote:
Hi,
Hi,
Same case as http://jira.codehaus.org/browse/MCHECKSTYLE-129 ?
2010/2/14 Olivier Dehon odn...@gmail.com:
Hello,
With the recent release of Checkstyle plugin 2.5, which uses Checkstyle
5.0, the format of the xml config file is not backwards compatible.
I struggled for a bit trying to
-Original Message-
From: bmat...@gmail.com [mailto:bmat...@gmail.com] On Behalf Of
Baptiste MATHUS
Sent: Sunday, February 14, 2010 1:11 AM
To: Maven Users List
Subject: Re: Error opening zip file (because it isn't there)
As I was surprised by the use case you're describing, I just
Hi. Is it possible to revert a release after everything's been
completed. The scenario is this: we made a release on Friday, and it
was discovered on Monday that a serious regression took place. We
want to re-release the artifacts in question with a fix.
I see that there's a release:clean goal
eh can you not just type in the older version number while running the release?
afaik, it will accept any verion as the new version (even the previous version)
I think you are looking to make things more complex than they already are..
But then IMHO I wouldn't do that unless you use a maven
On Mon, Feb 15, 2010 at 9:10 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
eh can you not just type in the older version number while running the
release?
afaik, it will accept any verion as the new version (even the previous
version)
I think you are looking to make things
Yes exact same case, even though I was under the impression that if the
xml file was 5.0 compliant, then the http URL was loaded OK.
I'll have to reconfirm that when I get into the office.
-Olivier
On Sun, 2010-02-14 at 20:34 +0100, Olivier Lamy wrote:
Hi,
Same case as
On 15 February 2010 01:10, Ed Hillmann ed.hillm...@gmail.com wrote:
On Mon, Feb 15, 2010 at 9:10 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
eh can you not just type in the older version number while running the
release?
afaik, it will accept any verion as the new version
Hi All,
I'm suck on the Mercurial SCM plugin, my repo's @ *
C:\Mercurial\Clones\project-xyz\*
And it contain's *./project-xyz/pom.xml* and thus gives: *
C:\Mercurial\Clones\project-xyz\project-xyz\pom.xml*
Follwing this blog:
13 matches
Mail list logo
