Re: [m2e-users] Best way to have one project looking at a subset of anot

[Stephen Coy <steve@xxxxxxxxxxxxx>]

I work this way all of the time and I do not have any issues with it. As Igor said, there is only one copy of the source in the file system.


On 17/04/2012, at 8:44 AM, KARR, DAVID wrote:

>> -----Original Message-----
>> From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-
>> bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
>> Sent: Monday, April 16, 2012 3:27 PM
>> To: Maven Integration for Eclipse users mailing list; m2e-
>> users@xxxxxxxxxxx
>> Subject: Re: [m2e-users] Best way to have one project looking at a
>> subset of another project
>> 
>> Import as Maven of the aggregator is expected to create separate
>> workspace project for each module. Each module workspace project is
>> expected to have sources folders, dependecies, etc. Not sure why this
>> does not happen for you.
> 
> If your suggestion means to have two copies of the code at the lower-level, once in the top-level project, and once in the separately imported project, then that doesn't do me much good.  That would mean I'd have to change both copies each time I made a change.  I know this, as that's what I was doing before.
> 
> In any case, I guess I've found a reasonable compromise.  I deleted the project that was pointing at the lower level, and I now have just the top-level aggregator.  At least with this I can do "Open Type", and it will find the Java classes in the lower levels.  Where this causes problems is that it won't let me use this project to create a Debug configuration (it's not in the list, perhaps because it doesn't think it's a Java project).  Instead, I simply created a debug configuration from some project, it doesn't matter which one, and then I added source folders to the debug configuration.  I now only have one copy of the source, and I can set breakpoints in the Java code.
> 
>> --
>> Sent from my SGS
>> 
>> "KARR, DAVID" <dk068x@xxxxxxx> wrote:
>> 
>>> I have one m2e project checked out from svn which is an aggregator
>>> project.  It is several layers deep.  Several layers down there are
>>> some projects with src/main/java trees.  I need to have the top-level
>>> aggregator project, but I also need to be able to debug code from the
>>> lower-level directories.  The top-level project doesn't know it has
>>> Java source, so I can't effectively set breakpoints or do "Open Type".
>>> 
>>> While I have this top-level aggregator project, can I create
>> additional
>>> projects that are just pointing at segments of that big project, so
>>> they both have the same files, but the lower-level one knows it's a
>>> Java project, so I can set breakpoints and "Open Type"?
>>> 
>>> It seems like I can just create a new project from an existing
>>> location, being within the first project.
>>> 
>>> Will that work, or will that cause me other problems?
>>> _______________________________________________
>>> m2e-users mailing list
>>> m2e-users@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>> 
>> _______________________________________________
>> m2e-users mailing list
>> m2e-users@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-users
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users