Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Hosting corporate m2e marketplace


I do not believe it makes sense to make the url user configurable. It
will be inconvenient, to say the least, to require all corporate users
to manually enter discovery catalog url.

I agree. But possibly the ui should be updated so that the field doesn't look editable.
 
I think it is better to
make this configuration part of eclipse distribution, so when eclipse
installed from your corporate update site talks to your corporate
discovery catalog.

You mean by creating a custom Eclipse feature?
Unfortunately it doesn't look like possible subclassing the default discovery code providing a different path...

/Anders

Also, as was discussed in [1], it is possible that m2e marketplace and
"standard" eclipse marketplace catalogs will merge at some point in the
future. So m2e discovery marketplace may disappear altogether.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=346703

--
Regards,
Igor


On 11-08-03 10:32 AM, Anders Hammar wrote:
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 <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> 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
       <igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
       <mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>> 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
       m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
       <mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>


       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
       m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
       https://dev.eclipse.org/__mailman/listinfo/m2e-users
       <https://dev.eclipse.org/mailman/listinfo/m2e-users>

   _________________________________________________
   m2e-users mailing list
   m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
   https://dev.eclipse.org/__mailman/listinfo/m2e-users
   <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


Back to the top