ect's version, it automatically inherits from its parent. Just take
${main.version} out.
On 11/21/06, Los Morales <[EMAIL PROTECTED]> wrote:
Hi,
I'm a bit frustrated on how Maven cycles through its
dependency. Currently
I have a project consisting of multiple sub projects2 l
Hi,
Im a bit frustrated on how Maven cycles through its dependency. Currently
I have a project consisting of multiple sub projects2 levels deep. Heres
a hierarchy:
-->main
--> sub1
--> sub1sub1
--> sub1sub2
--> sub2
The main project has a POM looking like this:
http://mav
Christian Goetze wrote:
The trouble is that you need a -reference- to the parent's version in the
children, and that reference does not seem to resolve any ${...}
substitutions, so it needs to be hard coded.
Hmm... Was this the intended design or could this be fixed up in later
revisions? J
Hi,
I would like to know how to chain a series of maven goals together (much
like Ant's dependency function). For example, I want to do this with one
command: mvn clean; mvn compile; mvn install; mvn package; mvn install.
How do I go about accomplishing this (if its possible). Thanks in ad
PROTECTED]>
Reply-To: "Maven Users List"
To: Maven Users List
Subject: Re: Confused about Maven 2 Eclipse plugin
Date: Thu, 12 Oct 2006 23:12:28 -0400
Look at external tools. You can launch lifecycle and goals from there.
Los Morales wrote:
I'm currently using Eclipse 3.2 and
I'm currently using Eclipse 3.2 and Maven 2 plugin version 0.0.9. When I
enable Maven 2 and right-click on my main project, there are only 2 options
for me in the popup menu: 1) Update Source Folders and 2) Add Dependency...
Where are the lifecycle phases or custom goals? Seems like the Net
Hi,
I'm fairly new to Maven 2 and I've just begun to use Mevenide for NetBeans 6
(Dev). When I run my compile phase, maven is complaining about the source
level for Java being at 1.3 instead of 6: "generics are not supported in
-source 1.3"
I'm not sure why the source is set to 1.3 when al
the multiproject plugin. With
Maven, you can define subprojects (each subproject is defined by a
project.xml), although a very high granularity (i.e. a project per package)
is descouraged.
Maven is also considered as a "wrapper" around Ant. All you need to do when
you want to use Ant, is to define
Hi,
I'm new to maven and would like to know if there is a way of creating one
main project.xml that calls other project.xml files to do the work. For
example, suppose I have 3 projects set up--P1, P2 and P3. P1 is designated
as the main project file. Running P1 initializes itself, calls P2 t