No one has any ideas?
I'm thinking along the lines that something that wasn't bundled with
maven alpha is now bundled with maven beta. Something that takes
precedence over what's need for customised url handlers to work. Does
anyone know if something has changed in that respect from the alpha to
t
I am using a global settings file (sort of! user level settings. I have
them in my .m2/ folder and not in maven/conf/)
It would have been really nice if I could define something like "network
profiles" and I could activate the proxy settings automatically say on
the basis of IP range. But agai
Thanks all, we know where to go from here!
On Tue, May 4, 2010 at 6:03 PM, Jesse Farinacci wrote:
> Hi Ravi,
>
> On Tue, May 4, 2010 at 7:01 PM, Ravi Luthra wrote:
> >
> > I've heard that locking down the plugin version is a bad practice mostly
> > because of major versions of Maven being relea
> I could put them into pluginManagement, but then all of the projects
> would have to "call-out" all of the executions of the various things,
> which was one of the things I was trying to factor out.
Yes, I meant pluginManagement, sorry about that...
And yes, they'd need to call-out the executio
On 5/7/2010 2:52 PM, Wayne Fay wrote:
>> The problem I'm having is that the factored-out build steps run when I
>> do "mvn install" on the parent-pom to get it into my local repo. These
>> steps don't work and throw errors, when run here.
>>
> Put the common stuff in depMgmt in the parent,
The error suggests that this is an error in the test suite. I think more of
a question for the log4j folks!
M.
-Original Message-
From: Hadzic, Tarik [mailto:hadz...@wusm.wustl.edu]
Sent: 07 May 2010 20:12
To: users@maven.apache.org
Subject: Log2j / Maven problem
I keep getting this on
I keep getting this on trying to install Log4j on my Snow Leopard:
Any ideas?
Thanks,
T
[INFO] An Ant BuildException has occured: The following error occurred while
executing this line:
/Users/tarikhadzic/Downloads/apache-log4j-1.2.16/tests/build.xml:187: Test
org.apache.log4j.CoreTestSuite fai
> The problem I'm having is that the factored-out build steps run when I
> do "mvn install" on the parent-pom to get it into my local repo. These
> steps don't work and throw errors, when run here.
Put the common stuff in depMgmt in the parent, and only declare the
plugins in the build section wh
It seems a good solution to me.
M.
On Fri, 2010-05-07 at 14:30 -0400, Marshall Schor wrote:
> I have a bunch of project that execute some common build steps.
>
> I factored these out into a parent-pom, and change the projects to
> specify this as their parent.
>
> My parent-pom is of package-ty
I have a bunch of project that execute some common build steps.
I factored these out into a parent-pom, and change the projects to
specify this as their parent.
My parent-pom is of package-type "pom".
The problem I'm having is that the factored-out build steps run when I
do "mvn install" on th
Same here,
I don't want to use freestyle jobs to maven as I base my releases to the
m2-release plugin of Hudson (yes I know about the freestyle release plugin,
but it doesn't fit exactly to the needs of a maven release)
I also think that having different versions of maven in development and CI
is
[Joke]
Hey ! Marty McFly should be able to see in the future with its dolorean !
By doing this, you should know when m3 will be released :-)
[/joke]
Joke apart, using Freestyle jobs doesn't allow to use maven oriented plugin
in the builds (like release hudson plugin).
To my part, I won't migrate w
Create a single project that has these dependencies in it ArtifactId
="bunch-of-jars" version =${app.version} set in the parent POM.
Set the project up to create a consolidated single jar file that has all
of the latest crap in it (create jar-with-dependencies)
Make the rest of your POMs depend
One thing you could do is to follow what this line says:
[INFO] For more information, run Maven with the -e switch
Another thing is you could run with the -X switch which will generate lots of
output, probably enough for you to see what's going wrong.
-Marshall Schor
On 5/7/2010 12:27 PM, Rog
Hi,
I am trying to run some tests that are already build as a jar as part of our
integration testing with the surefile plugin. I have followed the guide on
attached tests:
http://maven.apache.org/guides/mini/guide-attached-tests.html
However, my tests are not run. If I extract the jar to /test-c
Currently this occurs:
$ mvn exec:java
-Dexec.mainClass="org.familysearch.digitalarchive.IdisStatusWatcher"
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'exec'.
[INFO]
[INFO] Building mo
> Thanks, but I think that that doesn't answer my question. I just need a
> programmatic way to add jars to the build classpath.
I doubt you'll find many (any?) people on this list who have done this.
IMO you are better off simply deploying all those dependencies to a
corporate repo and using pro
> In Hudson I can currently only set up a Maven2 project - is this also
> working with Maven 3 oder do we have to wait till the maven plugin in
> hudson
> is updated ?
You could try building with M2 on Hudson and use M3 on your
developer's desktops (assuming you're doing nothing weird, it should
m
Thanks, but I think that that doesn't answer my question. I just need a
programmatic way to add jars to the build classpath.
Cheers,
-Alex
On Fri, May 7, 2010 at 1:21 AM, Jemos Infra wrote:
> I think this question was answered recently in the list and involved
> using extensions.
>
> http://mave
Heh, that's old school - you actually have two different machines. I
bet many developers today do their work on a single laptop, which
leads to the constant need to change settings, especially if you work
on multiple projects, some professional, some open source ones. One
solution is, if you can, t
You can always do a freestyle build in Hudson. However, I haven't tested
this with Maven 3.0-beta-1 myself.
/Anders
On Fri, May 7, 2010 at 14:49, MartyMcFly wrote:
>
> Thanks for the answer.
>
> the site functionality problem wouldnt be any concern right now.
>
> Can you say something about mav
Hmmm. I don't quite see the issue. At home I have a settings.xml file that
defines my environment at home, and at work I have a settings.xml file that
defines my environment at work. I can issue the same "mvn " at home or
at work and at home it doesn't go to a proxy and at work it does. I don't
What I've done for my setup is configure maven to take a settings.xml with
no proxy settings configured and pass it explicitly from maven using *mvn -s
your_settings_file.xml* . I'm using Cygwin for this, so I set up a
configuration to alias *mvn* commands to be *mvn -s "wherever your new
settings
Hi,
this is a stopper for me also in order to migrate to maven 3.
as for maven3-beta-1 I tested it in various complex projects and it didn't
have any issues.
2010/5/7 MartyMcFly
>
> Thanks for the answer.
>
> the site functionality problem wouldnt be any concern right now.
>
> Can you say som
Thanks for the answer.
the site functionality problem wouldnt be any concern right now.
Can you say something about maven3-beta-1 and Hudson ? This would be more
important for us.
In Hudson I can currently only set up a Maven2 project - is this also
working with Maven 3 oder do we have to wait
I'm using the features-maven-plugin included in Apache Felix. It in
turn uses "pax-url-mvn" (version 1.1.2) to enable the protocol "mvn:".
This works fine in maven 2.2.1 and also in maven 3.0-alpha-7. However,
with everything else the same, it fails under maven 3.0-beta-1. I get
"java.net.Malfo
I suggest using Maven 3.0-beta-1 right now. It is very stable and lots of
existing bugs in 2.2.1 have been fixed. However, be aware that there is
currently some incompatibilities with the site functionality
(maven-site-plugin).
regarding b), I could point out that m2eclipse is already using Maven
Hello all,
I need some helpful information and hope to find it here :-)
In our company we consider to move from our current horrible build structure
to Maven.
With seeing and hearing several talks from Jason van Zyl et al about Maven3
and its greatness over Maven 2, I was wondering the followin
Gadre,
I think it's assumed that your security configuration will remain stable
"per environment". So at work you will have a settings.xml with proxy
settings and at home a file without proxy settings. Isn't this a one-off
change? Or do you have any particular requirements for which you need to
s
I think this question was answered recently in the list and involved
using extensions.
http://maven.apache.org/guides/mini/guide-using-extensions.html
Regards,
M.
On Thu, 2010-05-06 at 22:29 -0700, Alex Ruiz wrote:
> Greetings,
>
> I know this is not the Maven way, but I need to add a bunch o
Hi,
what's the best way to prevent the usage of a deprecated plugin? Pre M3 we
simply set an unavailable version for the plugin in the pluginMgmt section,
but with M3 we get annoying warnings, because M3 resolves now also the
pluginMgmt elements:
%<
[WARNING]
Are you absolutely positively sure your command-line javac is of the
same minor version as what Maven uses? 1.5 doesn't implement generics
captures so you'd get these kinds of problems if you tried to compile
the same with 1.6 - source is not version compatible even if binary
is.
Kalle
On Thu, M
32 matches
Mail list logo
