Yes as Nuwan mentioned, it is possible to create a project with a different name than the label. In that case, you can create a label with "MARKETING_STORE" and create a project with "internal". But for this, in the setup command, you need to specify both label and the project (setup -n internal -l MARKETING_STORE). In beta, if -n <project-name> is not specified, label name will be considered as the project, that is the reason you got this issue.
Anyway, these commands have been slightly changed in the master branch. Once the next release is done we'll update them all together to match to the next release. Thanks! On Fri, Jun 29, 2018 at 9:22 AM, Malintha Amarasinghe <[email protected]> wrote: > Hi, > > Looks like there have been some edits to the screenshots. I reverted the > docs to a previous version that has the correct screenshots for the moment. > > We will be doing some edits anyway after today's release. We'll review the > full doc again and fix if anything is missing. > > Thanks! > > On Fri, Jun 29, 2018 at 8:55 AM, Dinusha Senanayaka <[email protected]> > wrote: > >> Malintha, can you please fix the label name to be consistent in the >> sample. In the publisher, label is given as "MRKETING_STORE", but in setup >> and build commands label is used as "Internal" which is kind of confusing. >> Better if we an keep label as "MRKETING_STORE" for all the places. >> >> Regards, >> Dinusha >> >> On Fri, Jun 29, 2018 at 8:22 AM Malintha Amarasinghe <[email protected]> >> wrote: >> >>> Thanks for reporting this Iloshini. I have fixed the documentation. >>> >>> Thanks! >>> >>> >>> On Thu, Jun 28, 2018 at 10:38 PM, Iloshini Karunarathne < >>> [email protected]> wrote: >>> >>>> Hi All, >>>> >>>> There is an issue when building the micro-gateway distribution by using >>>> the command, *micro-gw build -l internal* in the documentation [1]. >>>> Found that the source files haven't built and the target folder is empty. >>>> >>>> As per the source code, the command should be *micro-gw build -n >>>> internal *and able to successfully build the micro-gateway >>>> distribution using this command. >>>> >>>> This issue occurs when using the APIM Micro Gateway *Beta release* and >>>> IMHO it will be better if we can update the documentation [1] accordingly. >>>> >>>> >>>> [1]. https://docs.wso2.com/display/AM2xx/Configuring+the+API >>>> +Microgateway >>>> >>>> Thanks, >>>> Iloshini >>>> >>>> Regards, >>>> >>>> *Iloshini Karunarathne* >>>> >>>> *Software Engineer | Support Team* >>>> *WSO2* >>>> >>>> Email : [email protected] >>>> Mobile : +94719821300 >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "WSO2 Documentation Group" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/a/wso2.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Malintha Amarasinghe >>> *WSO2, Inc. - lean | enterprise | middleware* >>> http://wso2.com/ >>> >>> Mobile : +94 712383306 >>> >> >> >> -- >> Dinusha Dilrukshi >> Technical Lead >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94764069991 >> Blog: http://dinushasblog.blogspot.com/ >> > > > > -- > Malintha Amarasinghe > *WSO2, Inc. - lean | enterprise | middleware* > http://wso2.com/ > > Mobile : +94 712383306 > -- Malintha Amarasinghe *WSO2, Inc. - lean | enterprise | middleware* http://wso2.com/ Mobile : +94 712383306
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
