I discussed this with my team and they were quite interested. If it really suits our needs and we'll see that it makes sense to work in that direction, we could even contribute back anything we would need to tune to make it work for us.
But I need some additional help from you in order to proceed with the investigation, since my experience with Eclipse plugins is very basic. For now I need to know/do the following things: 1) Be able to run/debug the Onboarding project I looked at https://docs.sonatype.org/display/M2ECLIPSE/Developer+Guide and tried to import the Onboarding project in a similar way. That helped me to get rid of some errors, but I still get tons of them (for instance, for some reason I have problems with resolving/downloading s2-e36.target - could it be because I tried it with e3.7.1?). Do you have somewhere up-to-date wiki somewhere describing how to get started? Every mistake with setup costs a lot of time (when it starts verifying/downloading something it takes a lot of time and then shows an error). 2) Based on the above get it to run locally so that I can demo to my team it based on some of our projects. Any setup/configuration documentation would help here. 3) Understand list of dependencies for it Is that documented somewhere? The problem is that we have a lot of devs and not all of them even use m2e. So, we need a clear list of dependencies so that we start pushing on standardizing them. Thanks, Andrii On Tue, Oct 4, 2011 at 4:20 PM, Java Questions <[email protected] > wrote: > 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
