Right, I see that now. I never tried editing it, but it looked like an editable field.
Would it make sense to make this configurable to support the described use case? /Anders On Wed, Aug 3, 2011 at 04:23, Igor Fedorenko <[email protected]> wrote: > No, this is a read-only field, the value is hardcoded in the code. > > -- > Regards, > Igor > > > On 11-08-03 1:59 AM, Anders Hammar wrote: > >> I'm confused, isn't the (m2e marketplace) catalog url configurable >> through Preferences->Maven->Discovery? >> >> /Anders >> >> On Mon, Aug 1, 2011 at 17:41, Igor Fedorenko <[email protected] >> <mailto:[email protected]>> wrote: >> >> Do not install org.eclipse.m2e.discovery bundle to completely disable >> m2e marketplace functionality. You will have to create custom Eclipse >> feature to do this. m2e marketplace url is not configurable. >> >> -- >> Regards, >> Igor >> >> >> On 11-08-01 5:10 PM, Julien HENRY wrote: >> >> Hi, >> >> In my company we are hosting our own Eclipse p2 update site. Our >> Eclipse user installations can only access this site. This allow us >> to filter and validate plugins before allowing users to get them. >> >> I'm trying to regenerate our update site with Eclipse 3.7 and m2e >> 1.0. I don't really understand what I can do with plugins coming >> from >> m2e marketplace. Should I also host a corporate m2e marketplace? >> >> Currently I can't even create the update site, because when I try >> to >> include org.eclipse.m2e.feature, I get the following error: >> >> Processing inclusion from feature org.eclipse.m2e.feature: Unable >> to >> find plug-in: org.eclipse.m2e.maven.runtime_** >> __1.0.0.20110607-2117. >> Please check the error log for more details. >> >> Indeed I don't have org.eclipse.m2e.maven.runtime_**__1.0.0 >> anymore, >> because it was updated to 1.0.1 by a patch feature (with a red >> cross): >> >> Embedded Maven Runtime 3.0.3 1.0.1.201106031148 >> org.sonatype.m2e.maven.__**runtime.3.0.3.feature.group SONATYPE >> >> I tried to include the patch feature in my custom update site, but >> still I get the error message complaining that >> org.eclipse.m2e.maven.runtime_**__1.0.0 can not be resolved. >> >> Any suggestion? >> >> Thanks >> >> Julien >> >> ______________________________**___________________ >> m2e-users mailing list >> [email protected] <mailto:[email protected]> >> >> >> https://dev.eclipse.org/__**mailman/listinfo/m2e-users<https://dev.eclipse.org/__mailman/listinfo/m2e-users> >> >> <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<https://dev.eclipse.org/mailman/listinfo/m2e-users> >
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
