I'm trying to rally support for one of my favorite issues. I would
like Maven to be able to update bad poms and or artifacts from the
remote repo.
What's the use case for this?A developer creates a jar of his
project. However he built it with a 1.5 jdk when it should have been
built wit
I had the same problem using jetty6, spring and log4j. Solved it by setting
a system property specifying Log4J as the logger for commons logging. Here
is my plugin configuration:
org.mortbay.jetty
maven-jetty6-plugin
I agree entirely. When mvn -U is executed, not only should the process
look for new versions of dependencies, but it should also check the
md5s for the jars and poms (and/or timestamps of the files) to see if
something has changed.
Having said that, I can also understand the response "tick a new
v
Nevermind, I figured it out. For some reason I had M2_HOME in my
~/.mavenrc set and pointing to my 2.0.2 installation. Commented that
out and it works just fine now.
Rich
Richard Wallace wrote:
I tried to upgrade from version 2.0.2 to 2.0.3 because I've been
bumping into the problem where t
Is the flag working for profiles? I've got the
following profiles.xml
tomcat-local
tomcat
local
tomcat-local
http://localhost:8080/manager
That I'm using in my pom.xml to configure the tomcat plugin like
o
Try this instead
tomcat-local
-j
---
Justin Fung
[EMAIL PROTECTED]
Sr. Analyst, Business Systems
IT Banking Systems, e-Business
HSBC Bank Canada
http://www.hsbc.ca
p: (604) 643-6605
f: (604) 643-6727
Richard Wallace <
Richard Wallace wrote:
Is the flag working for profiles? I've got the
following profiles.xml
tomcat-local
tomcat
local
tomcat-local
http://localhost:8080/manager
Shouldn't you put a value in the tag? Like
true
- Henry
John has fixed this and will post a new RC shortly.
On 4/5/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
> And yes it hangs in the 2.0.4 RC
>
> -Original Message-
> From: Allison, Bob [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 04, 2006 19:10
> To: Maven Users List
> Subject: RE: [m2.0.
I'm having some trouble with the prepare target of the release plug in. I
have a pom artifact type, and I have several child modules like the example
below. I'm using the eclipse flat directory structure
../module1
../module2
when I perform "mvn release:prepare" I'm prompted for the ve
Henry S. Isidro wrote:
Richard Wallace wrote:
Is the flag working for profiles? I've got the
following profiles.xml
tomcat-local
tomcat
local
tomcat-local
http://localhost:8080/manager
Shouldn't you put a value in the tag
Actually, my "fix" broke a few other tests, so it'll take me a little
longer to put up a new RC/call a new vote. Should be firmly in place
tomorrow.
-john
Brett Porter wrote:
John has fixed this and will post a new RC shortly.
On 4/5/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
And yes it ha
yes it is a bug
http://jira.codehaus.org/browse/MRELEASE-6
-D
On 4/5/06, Todd Nine <[EMAIL PROTECTED]> wrote:
>
> I'm having some trouble with the prepare target of the release plug in. I
> have a pom artifact type, and I have several child modules like the
> example
> below. I'm using the ec
I assumed that your internal repo is not a mirror of ibiblio since it
contains custom artifacts (your custom cobertura plugin). Also because
you're using the same groupId, artifactId and version of cobertura
plugin you have to override central so it won't download that ibiblio's
version of the
Jeff Louw schrieb:
It is working ... but:
The generated launch.jnlp file does not appear to be correct. I think the
problem is the template.vm overrides the information that has already been
provided in the pom.xml ?
How can I setup the template.vm so that a correct launch.jnlp is created ?
A
Hi
I'm able to run jboss:configure run successful
but when i use jboss:start
it is giving the following error:
System cannot find the path specified..
any solutions please.
Hello,
Try using mvn jboss:start -X and search from the debug message, what
path is missing. May the jboss:configure dont make correct configuration
fail.
All the best.
Taavi Sildeberg
raja bangaru wrote:
Hi
I'm able to run jboss:configure run successful
but when i use jboss:start
it is giv
101 - 116 of 116 matches
Mail list logo