Hi Igor,

Thanks for your reply and pointing out those links. I wasn't aware of that
project. Will bring it to my team. Our issue is actually just a part of a
bigger on-going discussion about developer onboarding for our project. It
seems like we have very similar goals.

I'll will look trough the Developer Guide to see how to get it running.

Thanks,
Andrii

On Tue, Oct 4, 2011 at 1:36 PM, Igor Fedorenko <[email protected]> wrote:

> It is possible to implement automatic add/remove module projects using
> existing m2e APIs, and in fact this was one of the features of our
> recently opensourced Onboarding work [1]. Our goal was to help teams
> manage consistent development environments for all team members and that
> included consistent Eclipse installation, configuration and workspace.
>
> The part that deals with child modules is relatively small, have a look
> at [2] and [3] if you are interested.
>
> [1] 
> https://github.com/sonatype/**onboarding<https://github.com/sonatype/onboarding>
> [2] https://github.com/sonatype/**onboarding/blob/master/**
> onboarding-m2e/com.sonatype.**s2.project.core/src/main/java/**
> com/sonatype/s2/project/core/**internal/**ModulesAddRemoveMavenProjectCh**
> angedListener.java<https://github.com/sonatype/onboarding/blob/master/onboarding-m2e/com.sonatype.s2.project.core/src/main/java/com/sonatype/s2/project/core/internal/ModulesAddRemoveMavenProjectChangedListener.java>
> [3] https://github.com/sonatype/**onboarding/blob/master/**
> onboarding-m2e/com.sonatype.**s2.project.core/src/main/java/**
> com/sonatype/s2/project/core/**internal/ModulesAddRemoveJob.**java<https://github.com/sonatype/onboarding/blob/master/onboarding-m2e/com.sonatype.s2.project.core/src/main/java/com/sonatype/s2/project/core/internal/ModulesAddRemoveJob.java>
>
> --
> Regards,
> Igor
>
>
> On 11-10-04 5:39 AM, Java Questions wrote:
>
>> Hi all,
>>
>> I'm new to m2e, so my question might sound strange. I would appreciate
>> if you point me to some documentation in that case.
>>
>> We have dozens of sub-projects in our 3-level pom tree and people keep
>> adding and removing some of them on a bi-weekly basis. The problem is
>> further complicated by a fact that not all newly added projects result
>> in compile-time error when they are missing. The could end up not being
>> dropped into OSGi container since people forget to import them properly
>> and Eclipse for some reason doesn't know about their existence
>> automatically.
>>
>> Currently, people have to watch some mailing list and whenever there is
>> such an event, they have to go and either manually invoke import wizard
>> for the very root pom and add missing projects or manually remove some
>> of the not needed ones. Moving/renaming is a combination of
>> removing/adding.
>>
>> That all is very error prone and we would like to automate/simplify the
>> process somehow.
>>
>> Ideally, we would like to have the following workflow:
>> 1) sync
>> 2) fire Eclipse
>> 3) Some hook to trigger which would analyze developer's workspace
>> against latest pom tree (the very root pom is fixed and known)
>> 4) There should be some button somewhere which would be:
>> - green, if everything is all-right
>> - red, if not
>> Clicking it should automatically remove not needed projects (and update
>> Eclipse internals) and add the new ones (some sort of invoking import
>> wizard in a silent mode).
>>
>> Is it possible with the existing functionality? Or would we have to
>> somehow extend m2e?
>>
>> Any help would be very appreciated!
>>
>>
>> ______________________________**_________________
>> m2e-users mailing list
>> [email protected]
>> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users>
>>
> ______________________________**_________________
> m2e-users mailing list
> [email protected]
> https://dev.eclipse.org/**mailman/listinfo/m2e-users<https://dev.eclipse.org/mailman/listinfo/m2e-users>
>
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to