javafx-maven-plugin seems to ignore finalName parameter

[Uwe]

I want the javafx-maven-plugin to create a jar file but without the version
number in the file name.
So I added 
${project.artifactId}
to the configuration section but the plugin seems to ignore that.
What is wrong?



--
View this message in context: 
http://maven.40175.n5.nabble.com/javafx-maven-plugin-seems-to-ignore-finalName-parameter-tp5907231.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

[Uwe Barthel]

Hi Karl Heinz,

> Are you asking some PR in particular ?
https://issues.apache.org/jira/browse/MNG-3092 - 
https://github.com/apache/maven/pull/70

-- barthel


> On 12 Jun 2016, at 21:52, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
> 
> Hi Uwe,
> 
> On 6/12/16 9:40 PM, Uwe Barthel wrote:
>> Hi Karl Heinz,
>> 
>> did you merge any of the open github.com PRs into it?
> 
> I didn't but there have been PR's which have been merged...
> 
> So please consult the issue tracker which shows which PR's have made it 
> into...
> 
> Are you asking some PR in particular ?
> 
> Kind regards
> Karl Heinz Marbaise
> 
>> 
>> -- barthel
>> 
>> 
>>> On 11 Jun 2016, at 22:21, Karl Heinz Marbaise <khmarba...@gmx.de> wrote:
>>> 
>>> Hi to all Maven users,
>>> 
>>> is someone of you willing to do some testing on the current state of 
>>> development for the upcoming Maven 3.4.0 release?
>>> 
>>> Please be aware of this *** This is not an official release ***
>>> 
>>> I have created downloadable packages which are available from here:
>>> 
>>> Windows: https://s.apache.org/fawM,
>>> Linux: https://s.apache.org/RQ3C
>>> 
>>> 
>>> Every kind of feedback is helpful.
>>> 
>>> This is only a current state of development (Git hash: 
>>> 644ac9c40ad41bf61e3b099918af33b8eb950621) to get some feedback from the 
>>> community...
>>> 
>>> The current list of changes can be seen in the issue tracker:
>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.4.0
>>> 
>>> 
>>> Kind regards
>>> Karl Heinz Marbaise
>>> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing

[Uwe Barthel]

Hi Karl Heinz,

did you merge any of the open github.com PRs into it?

-- barthel


> On 11 Jun 2016, at 22:21, Karl Heinz Marbaise  wrote:
> 
> Hi to all Maven users,
> 
> is someone of you willing to do some testing on the current state of 
> development for the upcoming Maven 3.4.0 release?
> 
> Please be aware of this *** This is not an official release ***
> 
> I have created downloadable packages which are available from here:
> 
> Windows: https://s.apache.org/fawM,
> Linux: https://s.apache.org/RQ3C
> 
> 
> Every kind of feedback is helpful.
> 
> This is only a current state of development (Git hash: 
> 644ac9c40ad41bf61e3b099918af33b8eb950621) to get some feedback from the 
> community...
> 
> The current list of changes can be seen in the issue tracker:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.4.0
> 
> 
> Kind regards
> Karl Heinz Marbaise
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

[Uwe Barthel]

I tried:
'mvn clean' removes the lib/ and target/ folder.
'mvn package' puts the libs into lib/ again.

I delete all libs in lib/ folder but let the lib/ folder itself and the target 
folder untouched.
‘mvn package’ works as expected.

-- 
bart...@x-reizend.de


> On 11 Mar 2016, at 06:05, David Karr <davidmichaelk...@gmail.com> wrote:
> 
> Ok. Could you remove the jars and then run it again?
> 
> On Thu, Mar 10, 2016, 20:58 Uwe Barthel <bart...@x-reizend.de> wrote:
> 
>> Hi David,
>> 
>> I use your pom.xml (but removed parent and org.opendaylight dependencies)
>> and it works well with:
>> 
>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> 2015-11-10T17:41:47+01:00)
>> Maven home: /usr/local/Cellar/maven/3.3.9/libexec
>> Java version: 1.8.0_31, vendor: Oracle Corporation
>> Java home:
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: “mac"
>> 
>> $ ls -1 libs/
>> antlr4-runtime-4.0.jar
>> mapdb-1.0.4.jar
>> 
>> --
>> bart...@x-reizend.de
>> 
>> 
>>> On 11 Mar 2016, at 01:03, David M. Karr <davidmichaelk...@gmail.com>
>> wrote:
>>> 
>>> On 03/10/2016 03:54 PM, Mark Eggers wrote:
>>>> David,
>>>> 
>>>> I just upgraded to 3.3.9, and ran the following on one of my projects
>>>> (twice):
>>>> 
>>>> mvn clean package
>>>> 
>>>> In both cases the JAR files were copied to my output directory and
>>>> included in both the zip and tar.gz files.
>>>> 
>>>> I guess a little more information is needed??
>>> 
>>> Ok.  Following this is the entire pom.xml file in question.  Two of the
>> artifacts aren't on MavenCentral, but the example could easily be
>> simplified to not specify those.
>>> 
>>> --
>>> 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/xsd/maven-4.0.0.xsd;>
>>> 4.0.0
>>> 
>>> 
>>>   com.cisco.yangide
>>>   com.cisco.yangide.parent
>>>   1.1.1-SNAPSHOT
>>>   ../..
>>> 
>>> 
>>> com.cisco.yangide.core
>>> eclipse-plugin
>>> 1.1.1-SNAPSHOT
>>> 
>>>   src
>>>   
>>>   
>>>   org.apache.maven.plugins
>>>   maven-clean-plugin
>>>   
>>>   
>>>   
>>>   libs
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   org.apache.maven.plugins
>>> maven-dependency-plugin
>>>   2.10
>>>   
>>>   
>>>   copy
>>>   prepare-package
>>>   
>>>   copy
>>>   
>>>   
>>> libs
>>>   
>>>   
>>> org.antlr
>>> antlr4-runtime
>>>   4.0
>>>   jar
>>> true
>>> antlr4-runtime-4.0.jar
>>>   
>>>   
>>> org.mapdb
>>> mapdb
>>>   1.0.4
>>>   jar
>>> true
>>> mapdb-1.0.4.jar
>>>   
>>>   
>>> org.opendaylight.yangtools
>>> yang-model-api
>>>   0.6.1
>>>   jar
>>> true
>>> yang-model-api-0.6.1.jar
>>>   
>>>   
>>> org.opendaylight.yangtools
>>> yang-parser-impl
>>>   0.6.1
>>>   jar
>>> true
>>> yang-parser-impl-0.6.1.jar
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>> 
>>> 
>>> --
>>>> 
>>>&

Re: Why isn't maven-dependency-plugin copying my artifacts anymore?

[Uwe Barthel]

Hi David,

I use your pom.xml (but removed parent and org.opendaylight dependencies) and 
it works well with:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_31, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.3", arch: "x86_64", family: “mac"

$ ls -1 libs/
antlr4-runtime-4.0.jar
mapdb-1.0.4.jar

-- 
bart...@x-reizend.de


> On 11 Mar 2016, at 01:03, David M. Karr  wrote:
> 
> On 03/10/2016 03:54 PM, Mark Eggers wrote:
>> David,
>> 
>> I just upgraded to 3.3.9, and ran the following on one of my projects
>> (twice):
>> 
>> mvn clean package
>> 
>> In both cases the JAR files were copied to my output directory and
>> included in both the zip and tar.gz files.
>> 
>> I guess a little more information is needed??
> 
> Ok.  Following this is the entire pom.xml file in question.  Two of the 
> artifacts aren't on MavenCentral, but the example could easily be simplified 
> to not specify those.
> 
> --
> 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/xsd/maven-4.0.0.xsd;>
>  4.0.0
> 
>  
>com.cisco.yangide
>com.cisco.yangide.parent
>1.1.1-SNAPSHOT
>../..
>  
> 
>  com.cisco.yangide.core
>  eclipse-plugin
>  1.1.1-SNAPSHOT
>  
>src
>
>
>org.apache.maven.plugins
>maven-clean-plugin
>
>
>
>libs
>
>
>
>
>
>org.apache.maven.plugins
> maven-dependency-plugin
>2.10
>
>
>copy
>prepare-package
>
>copy
>
>
> libs
>
>
> org.antlr
> antlr4-runtime
>4.0
>jar
> true
> antlr4-runtime-4.0.jar
>
>
> org.mapdb
> mapdb
>1.0.4
>jar
> true
> mapdb-1.0.4.jar
>
>
> org.opendaylight.yangtools
> yang-model-api
>0.6.1
>jar
> true
> yang-model-api-0.6.1.jar
>
>
> org.opendaylight.yangtools
> yang-parser-impl
>0.6.1
>jar
> true
> yang-parser-impl-0.6.1.jar
>
>
>
>
>
>
>
>  
> 
> --
>> 
>> . . . just my two cents
>> /mde/
>> 
>> On 3/10/2016 3:44 PM, David M. Karr wrote:
>>> On 03/10/2016 03:36 PM, Mark Eggers wrote:
 David,
 
 If you're providing a list of dependencies, then yes you'll use the copy
 instead of copy-dependencies.
 
 See the following for that information:
 
 https://maven.apache.org/plugins/maven-dependency-plugin/index.html
 
 Also, I notice that you don't have outputDirectory specified. If you
 don't, the dependencies will be copied to
 ${project.build.directory}/dependency.
>>> Actually, I was specifying that individually on each artifactItem, but
>>> it's definitely an improvement to only specify that once.  In any case,
>>> it still makes no difference.  It's not writing the artifacts, whether I
>>> use "copy" or "copy-dependencies", or whether I say to write them to
>>> "libs" or "${project.build.directory}/libs". It ("copy", to be specific)
>>> did it the first time I ran this, but never since then.
>>> 
>>> I'm using Maven 3.3.9, with JDK 1.8.0_60.
>>> 
 See the following for that information:
 
 https://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html
 
 . . . just my two cents
 /mde/
 
 On 3/10/2016 3:22 PM, David M. Karr wrote:
> Thanks, but replacing my "manual" copy goal with "copy-dependencies" and
> implicit dependency declarations made no difference.  No error at this
> phase, it just doesn't do anything.
> 
> On 03/10/2016 02:57 PM, Mark Eggers wrote:
>> David,
>> 
>> On 3/10/2016 2:31 PM, David M. Karr wrote:
>>> Several days ago, on the advice of someone on another list, I
>>> configured
>>> the use of the "maven-dependency-plugin" in my POM so that the build
>>> would copy some dependencies into a local folder, not inside the
>>> target
>>> folder.
>>> 
>>> 

Range resolution does not work as docuented? was: Range resolution changed from 2.1?

[Uwe Schäfer]

On 11/17/2010 07:36 PM, uwe schaefer wrote:

Hello,

i am sorry, but i am really puzzled about this. the way i get it, 
(Snapshots aside) maven, from 2.2 on, does no longer work as documented 
here:


http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution

can someone please confirm this and point me to the right document?
currently, we cannot update from 2.1 due to this problem, and we don´t 
know what to change.


It is the same for a bunch of archetype POMs existing, the one from 
Apache Wicket being one of them.


thanks, uwe

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Range resolution changed from 2.1?

[uwe schaefer]

Hi

citing a mail from the wicket-user list, as it has nothing to do with 
the artifact resolved:



 All is fine as long as I specify a certain version, e.g. 1.4.13
 But using a version range does not work, e.g. [1.4.10,1.5)

well, that´s just spooky!

i tried to reproduce this and while maven 2.1 interprets [1.4.10,1.5) as 
we would expect and chooses 1.5-SNAP, maven 2.2.1 as well as 3.0

cannot cope with such a range.

modifing the range to have the same depth like
[1.4,1.5) now works again in 2.2.1 and 3.0, but for some weird reason 
(smell like char comparision instead of numbers?) it now chooses 1.4.9.


if that 1.5 snapshot should be in or out probably is a matter of 
discussion with the maven folks:

[MNG-4751] - Snapshot version not resolved for version range



was there a change in the supposed range resolution i am not aware of?

thanks, uwe

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Range resolution changed from 2.1?

[uwe schaefer]

On 11/17/2010 07:22 PM, Mark Derricutt wrote:

Hi Mark,


AFAIK the changes to range resolution were reverted, tho I've never
used mixed level numbers, we use [1.3.19,2.0.0) - always to the three
levels.


in the case looked at, even those do not work as expected

1.4.9  1.4.10

not to mention that 1.5-SNAPSHOT is no longer looked at, too.

2.1 worked with mixed levels as well (even though that change would be 
bareable from my pov), that´s why i am wondering.


cu uwe

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

optional jars and surefire

[uwe schaefer]

hi

i have a project with optional jars. some source files compile against them.
i do not want to force this dependency onto the user, so he can choose 
wether to use a feature requiring these jars.

when i run the surefire tests, the jars are included in the classpath.

is there a way to rerun the surefire tests WITHOUT these jars?

that would ensure the mentioned feature is cleanly separated from the 
rest of the code.


thanks, uwe

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: optional jars and surefire

[Uwe Schäfer]

Anders Hammar schrieb:

You mean like moving that feature to a separate module? :-)
That's the cleanest way you could do this. The 'optional' option is just a
workaround for a bad design, IMO.


as the feature is deeply woven into the regular code, this is 
unfortunately not possible.


cu uwe

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: optional jars and surefire

[Uwe Schäfer]

Johannes Schneider schrieb:


Yes, as Anders told, it is a work around for bad design ;-)


:)


But you could create a test-module. Then move the tests that shall be
run *without* optional modules to that module...


sounds good, i´ll try, thanks.

cu uwe


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: lifecycle phase is restarting over

[Kai Uwe Bachmann]

Hello,

could you post your assembly descriptor and the plugin configuration?
Or try one of the predefined assemblies (e.g. jar-with-dependencies).

Best Regards

Kai Uwe Bachmann
Am 08.03.2007 um 21:35 schrieb Dave Maung:

thanks for answering my question. I did attached goal, however, it  
seems

to failed to asseble

The error that I am getting is

[INFO]
--- 
-

[INFO] Error adding file 'C:\webapps\targe
t\classes' to archive: C:\webapps\target\c
lasses isn't a file.

If I used assembly goal, I was able to assemble without any problem  
except

compile phase executed twice.

Dave

On 3/8/07, Kai Uwe Bachmann [EMAIL PROTECTED] wrote:


Hello,

I think you use the assembly goal of the plugin. When you take a look
at the documentation you will
see that this goal calls the package phase by itself. If you use the
attach goal it wouldn't call an other
goal.

Best Regards

Kai Uwe Bachmann
Am 08.03.2007 um 20:56 schrieb Dave Maung:

 I have the following life cycle set up
 in compile phase, I have some ant task running, and in package  
phase, I

 have assembly plugin  set up.

 The problem is if I execute mvn package, it is calling compile
 lifecycle
 phase twice. Is there way to stop occuring it? I am using Maven  
2.0.5?


 Dave


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: lifecycle phase is restarting over

[Kai Uwe Bachmann]

Hello,

I think you use the assembly goal of the plugin. When you take a look 
at the documentation you will
see that this goal calls the package phase by itself. If you use the 
attach goal it wouldn't call an other

goal.

Best Regards

Kai Uwe Bachmann
Am 08.03.2007 um 20:56 schrieb Dave Maung:


I have the following life cycle set up
in compile phase, I have some ant task running, and in package phase, I
have assembly plugin  set up.

The problem is if I execute mvn package, it is calling compile 
lifecycle

phase twice. Is there way to stop occuring it? I am using Maven 2.0.5?

Dave



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Projectstructure

[Kai Uwe Bachmann]

Hello,

in my opinion you don't have a problem with maven but with Eclipse. 
Have you tried to post your problem to an Eclipse forum ?


Mit freundlichen Grüßen / Best Regards

Kai Uwe Bachmann
Am 15.08.2006 um 20:01 schrieb Kaiser, Hans:


Hello,


it's not required to put the subprojects in the directory of the root
project. You can place them all in separate directories
like Eclipse does and reference to it by relative path. I think you
have a directory structure like
wokspace
|-- myApp
|-- common
...
so you have to create a pom.xml in myApp with
...
modules
   module../common/module
...
/modules
...


no project structure is

workspace
|-- my-app (is also the CVS-module)
 |-- presentation
 |-- common
 |-- web
 |-- pom.xml (the master pom)



I think this will solve your problem.

If common, presentation and web are independent of myApp it could be a
better solution to reference them as dependency
and let maven do the rest



I will try the relative paths by adding the master pom to a subdir.
Anyway, would be a possibility to setup an environment for eclipse, 
with

the given structure?



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Projectstructure

[Kai Uwe Bachmann]

Hello,

it's not required to put the subprojects in the directory of the root 
project. You can place them all in separate directories
like Eclipse does and reference to it by relative path. I think you 
have a directory structure like

wokspace
|-- myApp
|-- common
...
so you have to create a pom.xml in myApp with
...
modules
  module../common/module
   ...
/modules
...

I think this will solve your problem.

If common, presentation and web are independent of myApp it could be a 
better solution to reference them as dependency

and let maven do the rest

Mit freundlichen Grüßen / Best Regards

Kai Uwe Bachmann
Am 15.08.2006 um 13:56 schrieb Kaiser, Hans:


Hello Kai Uwe,



my suggestion is a direcory structure of
myApp
|-- common
|-- presentation
|-- web
In CVS only the module myApp was checked in.
The whole project doesn't exists in the Eclipse workspace,





In Eclipse I've created a new workspace and 3 new projects from the
existing sources. The myApp
contains no sources itself and (only the pom file) so I doesn't create
an Eclipse project for it.
Finally I had only one CVS module with all the sources and no
duplications.


ahh okay, hadn't known something about this option.
To be sure, if we are takling about the same things, I have done
following:
- checked out my-app into the workspace
- added common, presentation and web into eclipse as Projects (with
existing project into workspace)

Now I have no idea how to add the master POM.xml into my workspace.
Could you give me an hint?


The only redundancies I have in my project are the dependencies 
between

the projects. This must be defined
in the maven pom and the Eclipse project because of a bug or missing
feature in the Eclipse plugin. I hope this
lack will be fixed in the next version.

BTW: The maven integration of Netbeans is much better if it could be 
an

alternative for you.


I thought about it, but we are using eclipse





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Projectstructure

[Kai Uwe Bachmann]

Hello,

I have a similar project structure and I realized it as a Maven 
multiproject (see HowTos).
Finaly you wil have 4 pom-files. One in the projects and one in the 
module.


In Eclipse I opened these projects simply by creating new projects from 
existing source, so the module wasn't in the Eclipse workspace.


Mit freundlichen Grüßen / Best Regards

Kai Uwe Bachmann
Am 13.08.2006 um 23:41 schrieb Kaiser, Hans:


Hello list,

I am currently astonished, how maven handles many build problems. It is
pretty fine!
Anyway I have troubles to integrate it into my project structure.

I am using eclipse and I have my eclipse sub-projects all together in a
CVS-module my-app.
Here the CVS structure:
my-app (CVS-module)
   presentation
   common
   web

In eclipse I have following projects:
presentation
common
web


Now I am wondering, how could I add a pom.xml to the given structure?
Does the CVS-module my-app has to be checkout into ecplise-workspace, 
so

the resulting projects in eclipse will be:
my-app
presentation
common
web

What will be the best way to use such project structure in maven?

best regards



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Projectstructure

[Kai Uwe Bachmann]

Hello,

my suggestion is a direcory structure of
myApp
|-- common
|-- presentation
|-- web
In CVS only the module myApp was checked in.
The whole project doesn't exists in the Eclipse workspace,

In Eclipse I've created a new workspace and 3 new projects from the 
existing sources. The myApp
contains no sources itself and (only the pom file) so I doesn't create 
an Eclipse project for it.
Finally I had only one CVS module with all the sources and no 
duplications.
The only redundancies I have in my project are the dependencies between 
the projects. This must be defined
in the maven pom and the Eclipse project because of a bug or missing 
feature in the Eclipse plugin. I hope this

lack will be fixed in the next version.

Mit freundlichen Grüßen / Best Regards

Kai Uwe Bachmann

BTW: The maven integration of Netbeans is much better if it could be an 
alternative for you.


Am 14.08.2006 um 09:57 schrieb Kaiser, Hans:


Hello Kai Uwe,

Thank you for your advice!



I have a similar project structure and I realized it as a Maven
multiproject (see HowTos).
Finaly you wil have 4 pom-files. One in the projects and one in the
module.


fine, this was also my plan, but see project structure

In Eclipse I opened these projects simply by creating new projects 
from

existing source, so the module wasn't in the Eclipse workspace.


I haven't got it, could you explain me, how you get it working with the
master-POM which includes all my modules?
As I can see, I will have to checkout following structure in eclipse:
- presentation
- common
- web
- the whole CVS-module my-app, which itself includes: (pom.xml,
presentation, common, web)

If so, this would be very odd, because of redundant data in the eclipse
workspace.
Could you explain me your approach?

regards



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]