On Wed, Dec 14, 2011 at 6:26 PM, Tom Masterson kd7...@gmail.com wrote:
We have several artifacts that we want to copy to remote servers via
scp/ssh. I have looked at the wagon plugin but the documentation seems to
have issues.
DO NOT try to use the Wagon plugin. It is *not* a tool for
On Wed, Dec 14, 2011 at 3:17 PM, scabbage guans...@gmail.com wrote:
I have a multi-module project with a parent pom and several sub-modules. In
one of the module, I have a dependency that has a transitive dependency of
spring (2.0.6). How do I go about having the rest of my project using Spring
Hello,
I can not figer out, how to get this working...
I would like to refer a config-file resource from a parent pom directory, but
when I insert this code to my child pom file:
build
resources
resource
[INFO] skip non existing resourceDirectory
C:\Users\myname\workspace\parent\child\${project.parent.basedir}\src\main\config
For some reason I do not know, this property is not replaced with the
expected value. Any ideas?
Yea, don't do this. If you need a resource from one project to use in
So if I don't use the wagon plugin do you have a sugestion as to what I
should use? I am not finding anything else out there when I do a google
search.
Tom
On Thu, 15 Dec 2011, Benson Margulies wrote:
On Wed, Dec 14, 2011 at 6:26 PM, Tom Masterson kd7...@gmail.com wrote:
We have several
Hello,
If you talk about http://mojo.codehaus.org/wagon-maven-plugin.
If wagon (ssh etc.) are missing, you must add those in the
dependencies section of the plugin.
Maybe you are using m3 so those are not included anymore in distribution.
2011/12/15 Tom Masterson kd7...@gmail.com:
So if I don't
Although it is not fully reliable, what works for me is to use the
maven-exec-plugin to directly invoke ssh/scp command. The issue is
mainly that you cannot be sure that ssh or scp is installed on the
computer maven is running on. But, in all likelyhood:
* Linux: usually ssh/scp is installed
Yes we are using Maven 3.0.3.
Tom
On Thu, 15 Dec 2011, Olivier Lamy wrote:
Hello,
If you talk about http://mojo.codehaus.org/wagon-maven-plugin.
If wagon (ssh etc.) are missing, you must add those in the
dependencies section of the plugin.
Maybe you are using m3 so those are not included
ship-maven-plugin
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 15 Dec 2011 17:09, Tom Masterson kd7...@gmail.com wrote:
So if I don't use the wagon plugin do you have
Olivier,
the wagon plugin will only copy things if the directory hierarchies
look like a repo.
On Thu, Dec 15, 2011 at 12:15 PM, Olivier Lamy ol...@apache.org wrote:
Hello,
If you talk about http://mojo.codehaus.org/wagon-maven-plugin.
If wagon (ssh etc.) are missing, you must add those in
I am creating an executable shaded JAR using Maven 2 using the following
plugin config:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-shade-plugin/artifactId
version1.5/version
executions
Sorry for misunderstanding, I was talking more about wagon api which
can copy files even if the target is not a maven repo.
But http://mojo.codehaus.org/wagon-maven-plugin/upload-mojo.html
doesn't look to be limited to only maven repo target
see sample
The problem is that after executing mvn clean package, the uber-JAR does
not include anything under my test folder (./src/test/java/org/myAddress/*).
How can I configure the shade plugin to include those test files?
This is how things are supposed to work. Test files are not included
in
Hi Barrie Treloar,
You suggestions looks good to me, I tried your suggestion.
And yes this is not working only XSD generated import statements in Module
2. I have one DAO module too which is also generating some JAR file. And
that is also imported in Module2 but that import statements doesn't
The MainTestClass is a Java class that executes TestNG tests when the JAR is
launched. So they are test files. I can understand why they would be
included by default, but is there no way to request that they are added?
--
View this message in context:
Ship-maven-plugin won't work because we need to work with snapshots. What
we are doing more specifically is putting a version from the build server
to as many as four test servers for the use of a variety of teams and
testing. Looks like I may have to roll my onw here.
Tom
On Thu, 15 Dec
Ignore the last message I missed a parameter.
Tom
On Thu, 15 Dec 2011, Stephen Connolly wrote:
ship-maven-plugin
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense words
and other nonsense are a direct result of using swype to type on the screen
On 15
Hi friends,
i found these types of error or exceptions.
please help me ro solve it.
C:\Users\Ashishmvn install
Exception in thread main java.lang.UnsupportedClassVersionError:
org/apache/ma
ven/cli/MavenCli (Unsupported major.minor version 49.0)
at
Maven needs à minimum 1.5 jdk to run
Jeff
Le jeudi 15 décembre 2011, ashishmemod ashishme...@gmail.com a écrit :
Hi friends,
i found these types of error or exceptions.
please help me ro solve it.
C:\Users\Ashishmvn install
Exception in thread main
On Thu, Dec 15, 2011 at 1:32 PM, Olivier Lamy ol...@apache.org wrote:
Sorry for misunderstanding, I was talking more about wagon api which
can copy files even if the target is not a maven repo.
But http://mojo.codehaus.org/wagon-maven-plugin/upload-mojo.html
doesn't look to be limited to only
Hi
You need to use Java 5 or newer to run the latest versions of Maven.
On 2011-12-15 09:04, ashishmemod wrote:
Hi friends,
i found these types of error or exceptions.
please help me ro solve it.
C:\Users\Ashishmvn install
Exception in thread main
So release:prepare does a compile first and then (modifies the pom and)
creates the tag. That makes sense, but...
the problem is we have some artifacts that take a *long* time (up to an
hour) to build. During that time developers may check in more changes that
they don't expect to be part of
You can skip the building of the snapshot by changing the goals in the prepare
phase. This will then jump you right to tag creation, checkout of the tag and
building of the tag during the perform phase.
-Original Message-
From: Phillip Hellewell [mailto:ssh...@gmail.com]
Sent:
Maybe I didn't fully get every steps of your release
but usually you should branch your code and release
from there.
Unless you have total control on your branch/trunk, even then
the best approach should be to branch. We branch on first beta
or code/feature freeze.
On , Phillip Hellewell
On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
tthies...@avaya.com wrote:
You can skip the building of the snapshot by changing the goals in the
prepare phase. This will then jump you right to tag creation, checkout of
the tag and building of the tag during the perform phase.
Thanks
On Thu, Dec 15, 2011 at 3:07 PM, pino.silvag...@gmail.com wrote:
Maybe I didn't fully get every steps of your release
but usually you should branch your code and release
from there.
Do you mean branch or tag?
A release is created from a tag, and that is what the release plugin
does for us.
On Fri, Dec 16, 2011 at 5:24 AM, Daivish Shah daivish.s...@gmail.com wrote:
Hi Barrie Treloar,
You suggestions looks good to me, I tried your suggestion.
And yes this is not working only XSD generated import statements in Module
2. I have one DAO module too which is also generating some JAR
Do you mean branch or tag?
A branch.
In a busy environment, the common practice is:
1) use release:branch to make a branch.
2) use release:prepare/perform on the branch
A release is created from a tag, and that is what the release plugin
does for us.
Unless you have total control on
thank you for above reply...
But I installed java 6 with update 24 in my system!!!
So now what is meaning of this exception?
--
View this message in context:
http://maven.40175.n5.nabble.com/Solve-my-exception-for-mvn-installtion-tp5076811p5079295.html
Sent from the Maven - Users mailing
Hi
I am new to maven. I want to maintain a separate POM file for version of
the jar files. This will help in maintaining the versions of jar files. For
eg: if we are using junit.jar, the version of the jar file should be
maintain in the separate POM file. This will help us in changing in only
On Fri, Dec 16, 2011 at 3:12 PM, ashishmemod ashishme...@gmail.com wrote:
thank you for above reply...
But I installed java 6 with update 24 in my system!!!
So now what is meaning of this exception?
You are mixing versions of Java.
You have your IDE using Java 5 or Java 6
and
You have your
On Fri, Dec 16, 2011 at 4:39 PM, Barrie Treloar baerr...@gmail.com wrote:
On Fri, Dec 16, 2011 at 3:12 PM, ashishmemod ashishme...@gmail.com wrote:
thank you for above reply...
But I installed java 6 with update 24 in my system!!!
So now what is meaning of this exception?
You are mixing
http://blog.artifact-software.com/tech/?p=121
On 16/12/2011 12:17 AM, KumarR wrote:
Hi
I am new to maven. I want to maintain a separate POM file for version of
the jar files. This will help in maintaining the versions of jar files. For
eg: if we are using junit.jar, the version of the jar
Using dependencyManagement in the parent to specify the version of
dependencies is also an option. IMHO that's the true Maven way, but
Ron's approach could be an option in some cases. I don't like that
approach though as it will create an incorrect dependency tree
(dependencies will be on the
Hi All
I have the following mojo, but the values are NOT getting set, by maven runtime.
The exception trace is provided below.
Have anyone faced the same problem before?
public class Assembler1PackageMojo extends AbstractMojo {
/**
* The
Thanks for the reply. Below is my POM script
Parent Pom
---
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
parent
Hi Phillip,
Phillip Hellewell wrote:
On Thu, Dec 15, 2011 at 3:05 PM, Thiessen, Todd (Todd)
tthies...@avaya.com wrote:
You can skip the building of the snapshot by changing the goals in the
prepare phase. This will then jump you right to tag creation, checkout
of the tag and building of
37 matches
Mail list logo
