Hi all,
i have created a war maven project and if i start in using maven-jetty
plugin, everything works fine.
but if i tried to deploy the war project to tomcat. there is an error in the
calalina.log
Dec 23, 2009 1:43:22 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Eng
Thanks Wandy,
yeah I removed proxy information from setting.xml
and blown up the "org" (org.apache.maven.maven-parent) directory from the
local repo...but with no luck.
On Tue, Dec 22, 2009 at 2:25 AM, Wendy Smoak wrote:
> On Mon, Dec 21, 2009 at 2:46 AM, amaresh mourya
>
I'm no Maven expert myself, but putting the WTKX files in the resources
directory seems like a good idea. Cross-posting to the Maven user list in case
anyone has any suggestions!
Greg
On Dec 22, 2009, at 8:02 PM, Michael Bushe wrote:
> I posted this HOWTO on developing with Pivot using Maven an
A parent pom which I thought was setting source/target for all modules
was not. This was masked by the fact that some of the other modules
have their own settings of source/target. So, what I thought was the
eclipse plugin enforcing the old policy of maven plugins running under
1.4 was really just
On Mon, Dec 21, 2009 at 12:25 PM, Benson Margulies
wrote:
> While I read the doc, it didn't seem applicable. Now that you tell me
> that there's no special trickery going on that tries to force 1.4 on
> mojo projects, I'm off to revisit all the poms to see there's
> something I missed.
Can you po
I'ld suggest putting the source plugin in a release or full build profile.
That way your release manager or continuous build system and create the
source jar and developers can optionally include it if you want.
2009/12/16 Anders Hammar
> Sorry, I was a little bit too quite there. Didn't really
I need help figuring out how to reference external properties in a child/module
pom file.
I have tried using filters, properties-maven-plugin - all the same - the
properties propagate to children project resources but do not resolve in the
pom files themselves, thus causing pom validation errors
The nexus FAQ shows the link syntax:
http://nexus.sonatype.org/nexus-faq.html#25
--Brian (mobile)
On Dec 22, 2009, at 12:37 PM, Johannes Schneider
wrote:
Hi,
at the moment I am creating a page for a project of mine.
And because not everybody out there uses maven (don't understand
why),
This is the link you're looking for:
http://nexus.sonatype.org/nexus-faq.html#25
However, this only works if the snapshot is hosted in Nexus powered
repository.
/Anders
On Tue, Dec 22, 2009 at 18:44, Hayes, Peter wrote:
> This works:
>
>
> http://nexus.cedarsoft.com/service/local/artifact/mave
You should always pin down the version of all plugins used. You do that
through the use of the pluginManagement section. In your case I believe
v2.4.2 is defined through the pluginManagement section of Maven's super pom.
However, that version will change whenever you change version of Maven,
which
What we are doing is using the maven repository as a binary artifact
repository... SVN for source code...
They needed somewhere to keep their binary artifacts we have RPMs of our
Java modules that get installed into the stuff they build... and we already
have a geo-redundant maven repository..
They do not want to install java on their machine!
I did warn that they are java-phobes...
-Stephen
(I have toyed with using GCJ to compile a cli tool for them and package that
up as an RPM for them to install... but I'm convinced that some BASH
scripting should be able to do it all)
2009/12/22
Previous versions of the m2eclipse plugin used to allow settings.xml not
to exist and use defaults. Now it errors out if the file is not
present. So the question becomes, what is in a starter settings.xml,
what are the default settings? Is there a way to generate a default
version of this file (
Why not the maven-cli-plugin[1]? This seems fairly close. Or are the
shell-bigots too bigoted to drop into a subshell? :-)
[1] http://wiki.github.com/mrdon/maven-cli-plugin
-Jesse
On Tue, Dec 22, 2009 at 9:56 AM, Stephen Connolly
wrote:
> Hi there,
>
> we have some Java-phobes...
>
> We want to
On 12/22/2009 06:44 PM, Hayes, Peter wrote:
> This works:
>
> http://nexus.cedarsoft.com/service/local/artifact/maven/redirect?r=snapshots&g=com.cedarsoft&a=serialization&v=1.0.0-beta2-SNAPSHOT
Thanks a lot!
Sincerly,
Johannes
>
> There is some documentation out there on this though I'm una
This works:
http://nexus.cedarsoft.com/service/local/artifact/maven/redirect?r=snapshots&g=com.cedarsoft&a=serialization&v=1.0.0-beta2-SNAPSHOT
There is some documentation out there on this though I'm unable to pull it at
the moment.
These are the parameters:
r = repository name (cannot be a g
I'm trying to build the test goal of a project. Something in my setup
(not sure what, I'm using m2eclipse with all the default settings) is
translating that to using surefire-2.4.2 but apparently this plugin is
no good.
301 Moved Permanently
Moved Permanently
The document has moved http://down
Hi,
at the moment I am creating a page for a project of mine.
And because not everybody out there uses maven (don't understand why), I
want to provide a link to the latest artifact for manual download.
Of course that is not possible since every snapshot artifact has the
build date prepended.
How
I believe that the behavior you see is correct. Maybe not what you want
though...:-)
If you explain why you sometimes would like to add more jars wee could
suggest a different solution.
/Anders
On Tue, Dec 22, 2009 at 16:12, Rebholz Paul wrote:
> > Hi all!
> >
> > We have a project producing an
Or use the excludes config of the surefire plugin to exclude those tests in an
incubating phase, then when they grow up to be proper tests remove the name
from the surefire plugin config.
See
http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html
Ben
On 22 Dec
> Hi all!
>
> We have a project producing an ear artifact. The contents of the ear
> file are configured with the maven-ear-plugin. In profiles we want to
> be able to flexibly add more artifacts to the ear file as shown in the
> example below. Our tests so far revealed a different behaviour than
I'm lovin this solution (looks like I forgotten the KISS principle this case
... :-))
Thanks
Frédéric
On Tue, Dec 22, 2009 at 3:46 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Don't have your tests end in Test or TestCase or start with Test. That way
> you can keep them in sr
Hi there,
we have some Java-phobes...
We want to use the Maven Repository to share binary artifacts across
teams...
Has anyone got any BASH scripts which replicate Maven / ANT Tasks / Mercury?
At the moment the best I have is:
repo_dir=$(echo "${groupId}" | sed -n -e
"s:\.:/:gp")/${artifactId}
Don't have your tests end in Test or TestCase or start with Test. That way
you can keep them in src/test/java and they will be compiled, but surefire
will not execute them
2009/12/22 Frederic Camblor
> Hi all !
>
> I'm facing a problem which looks simple but I've not succeeded resolving it
> yet
amit,
You can use the same Nick suggestion using two execution tags to same plugin
tag. Try this:
org.codehaus.mojo
buildnumber-maven-plugin
0.9.6
generate-buildnumber
validate
Sorry I neglected to include both versions of projectD. File updated.
http://old.nabble.com/file/p26889403/omitted_dependency_example.zip
omitted_dependency_example.zip
Anders Hammar wrote:
>
> I tried your example, but it doesn't work. It's complaining about
> test.projects:projectD:jar:1.0
Hi all !
I'm facing a problem which looks simple but I've not succeeded resolving it
yet :-)
I'd like to create "incubation tests" in my project.
"incubation tests" are :
- part of tests hierarchy, but dissociated with test classes (that is to
say, I will locate them in something like src/incuba
Thanks Nick. This works to me. Now I have two variables: a build number and a
human readable current date. I only modified your suggestion setting up a
new name for the variables in each execution using "buildNumberPropertyName"
tag:
org.codehaus.mojo
buildnumber-
> My question is: what is the reason that the maven compiler plugin does not
> recompile the Client.java in the scenario described above? It only
> recompiles it if the Client.class is deleted, i.e. by calling "mvn clean
> compile".
That's the way javac works (and maven-compiler-plugin just invokes
I created a minimal example maven project with the following directory
structure:
C:\SAMPLE.PRJ1
| pom.xml
|
\---src
\---main
\---java
\---sample
Client.java
Library.java
with the content of files Library.java and Client.java as
I am out of the office until 31.12.2010.
In urgent cases please contact Wotan von Klass, phone: +49 (0) 6227 385 38
33, e-mail: wotan.vonkl...@icw.de.
Ich bin bis 31.12.2010 außer Haus.
In dringenden Fällen wenden Sie sich bitte an Wotan von Klass, Tel.: +49
(0) 6227 385 38 33, E-Mail: wotan
I work in a sandbox network and have similar issues.
What I do:
1) Internet Connected Host
1.1) Create pom contain all dependencies and plugins used.
1.2) mvn -s settings.xml clean install site
1.3) find, grep -v, sort -u, echo, cat sort -u, echo (obtain list of group
id's downloaded)
1.4) rsync l
I tried your example, but it doesn't work. It's complaining about
test.projects:projectD:jar:1.0.0-SNAPSHOT missing.
/Anders
On Thu, Dec 17, 2009 at 20:23, egroesbeck wrote:
>
> No problem:
>
> http://old.nabble.com/file/p26833532/omitted_dependency_example.zip
> omitted_dependency_example.zip
Something which might work for you.
parent
| -- src/main/filters
| -- pom.xml (pomP)
| -- module-a
| -- src/main/resources
| -- pom.xml (pomA)
| -- module-b
| -- src/main/resources
| -- pom.xml (pomB)
pomP
${relpath-to-parent}\src\main\filters\${env}-filter.p
I don't see it as maven issue, I see it as a source control management or
people issue.
Getting a clear understanding of how version numbers will be increased, how
people should be using source control, once you know that maven can do what
ever you need it to do.
Issues you'll need to think about
Hi,
Apache Pivot uses maven-ant-tasks to get it's ant build products into a
maven repo. This works if the classpath has maven-ant-tasks version 2.0.10
but does not work with maven-ant-tasks 2.1 on the classpath. The error
using 2.1 is:
maven-install:
[artifact:install] An error has occurred wh
36 matches
Mail list logo