Hello,
in which way resolve maven inherited dependencys.
E.G. module1.v1 - depends module2.v1 and module3.v1
module2.v1 - depends module3.v2
Which version of module3 is used and give maven a error or at least a
warning?
Yours Rüdiger
--
View this message in context:
Karl Heinz Marbaise wrote:
...
first: Have you defined scm section in your root pom ?
Yes, each module and the parent has its own scm section.
If we remove the modules section from the parent we can
release the modules and the parent in single steps.
Karl Heinz Marbaise wrote:
we
Karl Heinz Marbaise wrote:
...
If you do an mvn release:perform ...aren't you asked for the release
version etc. during the process ?
...
I'm asked for the release version for all modules but only asked for the new
SNAPSHOT version for the parent module.
Karl Heinz Marbaise wrote:
Hello,
we are using svn:externals to add our modules into the parent directory.
We can build, test, deploy ... but we can't create a release. The release is
only
created for the parent (which is only a pom module). There are no tags in
subversion
and no artifacts released to the repository.
I have been noticing that Maven is redownloading some SNAPSHOTs every day,
despite the fact that the files have not changed. I ran my build using mvn
-X clean package and I can see that an HTTP 304 is being returned
(verified on the server), yet the file is downloaded anyway. Is there some
Hi
I have a class that uses the method setXIncludeAware(boolean) from
javax.xml.parsers.SAXParserFactory (jdk1.5)
The class compiles in eclipse.
But when I run maven, maven does not compile the class, it says that this
method does not exists.
I tried in others machines, but the error is alwalys
java:compile
again:
maven.compile.source=1.5
maven.compile.target=1.5
Doug
Minds Work wrote:
Hi
I have a class that uses the method setXIncludeAware(boolean) from
javax.xml.parsers.SAXParserFactory ( jdk1.5)
The class compiles in eclipse.
But when I run maven, maven does not compile
Hi
I Have a project that extends from other project.xml ( the parent project),
but I want to ignore some dependencies of the parent project, is there a way
to do this???
[]s
Freddy
Work [mailto:[EMAIL PROTECTED]
Envoyé : lundi 31 octobre 2005 19:16
À : Maven Users List
Objet : can a goal executing in a project execute goals in
other projects?
Is there a way (without using the exec ant task...) to make a
goal call another goal but execute it in other project
It works,
Thank you
[]s
Freddy
On 11/1/05, Dion Gillard [EMAIL PROTECTED] wrote:
Couldn't you make it a system property:
${systemScope.put('name', varFromTstamp)}
On 11/2/05, Minds Work [EMAIL PROTECTED] wrote:
Thanks, it works,
I have another related question
I want to known
[maven 1.0.x]
Can I pass arguments to a goal when I execute maven goal? And with the
attaingoal tag?
[]s
Freddy
Is there a way (without using the exec ant task...) to make a goal call
another goal but execute it in other project?
Example, I execute the goal myGoal in project Foo, and the goal myGoal
execute the jar goal in project Bar?
[]s
Freddy
12 matches
Mail list logo