Re: [jbossdeveloper] <repository /> definition in pom.xml for Quickstarts and Demos

Np, Max. They will be used just "if required" for dependencies that were not released yet because we want/need that the -develop branch should be buildable for Quickstarts contributors. During the productisation procedures, the only repository allowed will be "maven.repository.redhat.com".

On 4/21/15 03:54, Max Rydahl Andersen wrote: > On 20 Apr 2015, at 20:39, Rafael Benevides wrote: > >> Hi all, >> >> The <repository /> definition in pom.xml was included as part of EAP >> 7 plan: https://mojo.redhat.com/docs/DOC-1020116 > > I noticed this linked to a link that says a repo named > "temp-maven-repo" is in the list of approved repositories ? Is that > really intended ? > > And why is the very global > repository.jboss.org/nexus/content/groups/public allowed in here ? We > are supposed to *not* depend on that repository in any form of > fashion during productisation aren't we ? > > p.s. I think I've asked the above before so i'm sorry if I forgotten > - if there is a good reason I think we should add that in the > comments of the qstools-plugin :) > > /max > >> >> >> On 11/14/14 07:38, Pete Muir wrote: >>>> On 14 Nov 2014, at 10:51, Max Rydahl Andersen >>>> <manderse(a)redhat.com&gt; wrote: >>>> >>>>>>> Can you please review https://mojo.redhat.com/docs/DOC-997344 >>>>>>> <https://mojo.redhat.com/docs/DOC-997344> and confirm if those >>>>>>> ids are ok. If not, do you mind to place the right information >>>>>>> at the document? >>>>>> sorry for late response. >>>>>> >>>>>> Looking at this list the only two repositories I consider valid >>>>>> in production quickstarts >>>>> production quickstarts aren’t actually a thing :-p >>>> What word do we use for it then ? it's not community quickstarts >>>> since they depend on productized bits. >>> Product quickstarts. >>> >>>>>> are: >>>>>> >>>>>> redhat-techpreview-all-repository >>>>>> http://maven.repository.redhat.com/techpreview/all/ >>>>>> <http://maven.repository.redhat.com/techpreview/all/> >>>>>> >>>>>> redhat-earlyaccess-all-repository (for things not GA) >>>>>> https://maven.repository.redhat.com/earlyaccess/all/ >>>>>> <https://maven.repository.redhat.com/earlyaccess/all/> >>>>> These ^^^, plus fusesource, are valid for non-earlyaccess >>>>> quickstarts >>>> So the earlyaccess repo is valid for non-earlyaccess quickstarts ? >>>> seems counterintuitive ? >>> Yes. A quickstart may be in beta, or a product may be in beta. >>> These things are orthogonal. >>> >>>>>> These are I'm surprised we are now letting in: >>>>>> >>>>>> Jboss public repo is not something our productized nor project >>>>>> quickstarts should depend on is it ? Was there not a requirement >>>>>> for quickstarts >>>>>> to *not* rely on this repo that is a big mashup of dependencies >>>>>> and instead only rely on central published artifacts ? >>>>>> jboss-public-repository >>>>>> https://repository.jboss.org/nexus/content/groups/public/ >>>>>> <https://repository.jboss.org/nexus/content/groups/public/> >>>>> This ^^^ is valid only for earlyaccess quickstarts >>>> ...so earlyaccess quickstarts is even earlier than what is in >>>> earlyaccess maven repo ? >>>> >>>> Just trying to do the mapping since this is what we call community >>>> quickstarts on jboss tools end and we keep it clearly separate >>>> from production related stuff >>>> to avoid/reduce confusion. >>> Correct. It’s much closer to what you call early access in JBDS - >>> features that aren’t ready to go in to the product yet. >>> >>>>>> Fuse reposource repo I thought was only being used for old fuse >>>>>> releases ? If that is no longer the case then that is not great >>>>>> since >>>>>> it seem to have a lot of redundancy of artifacts. >>>>>> fuse-public-repository >>>>>> https://repo.fusesource.com/nexus/content/groups/public >>>>>> <https://repo.fusesource.com/nexus/content/groups/public> >>>>> It’s still used for Fuse releases AFAIK. >>>> mkay '/ - i'll try reach Aileen and here what is the plan for it >>>> and what is stopping them from getting into >>>> maven.repository.redhat.com. >>>> >>>>>> This repo I do not understand what is for and should not be >>>>>> exposed anywhere IMO. Only relevant to put in testers own >>>>>> settings.xml is it not ? >>>>>> jboss-developer-staging-repository >>>>>> http://jboss-developer.github.io/temp-maven-repo/ >>>>>> <http://jboss-developer.github.io/temp-maven-repo/> >>>>> Agreed, this one should never appear in a POM. >>>> +1 >>>> >>>> /max >>>> >>>>>> About the ID's correctness/alignment with our tools that is >>>>>> something Fred should be able to verify better than I. >>>>>> >>>>>> /max >>>>>> >>>>>>> Pete/Max, >>>>>>> >>>>>>> Do you know if Fuse maven repository still valid ? >>>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> On 10/31/14 11:56, Rafael Benevides wrote: >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I was thinking about the implementation of the repository >>>>>>>> definition in pom.xml and I want to share my thoughts: >>>>>>>> >>>>>>>> - Create a QSTools CHECKER to mark the lack of <repository /> >>>>>>>> as a guideline violation if MavenCentralChecker is disabled. >>>>>>>> - The violation message will instruct to use the new QSTools >>>>>>>> GOAL that will be created >>>>>>>> >>>>>>>> - Create another QSTools GOAL to setup the repositories. >>>>>>>> - There will be a list of approved repositories and its IDs >>>>>>>> (redhat techpreview, earlyacess, jboss developer temporary, >>>>>>>> etc) >>>>>>>> - QSTools will remove all previous repositories from pom.xml >>>>>>>> and prompt which repositories should be added. >>>>>>>> - This will help Quickstarts and demos to be easily buildable >>>>>>>> from development and production branches and will also allow >>>>>>>> this list to be bulk updated to remove any previous >>>>>>>> development repository definition. >>>>>>>> >>>>>>>> Please, >>>>>>>> >>>>>>>> If you have any feedback on this, feel free to reply. >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Rafael Benevides | Senior Software Engineer* >>>>>>>> JBoss Developer >>>>>>>> M: +55-61-9269-6576 >>>>>>>> >>>>>>>> Red Hat >>>>>>>> >>>>>>>> Better technology. Faster innovation. Powered by community >>>>>>>> collaboration. >>>>>>>> See how it works at www.redhat.com <http://www.redhat.com/> >>>>>>>> <http://www.redhat.com/ <http://www.redhat.com/>> >>>>>>>> >>>>>>>> LinkedIn <http://www.linkedin.com/company/3258288 >>>>>>>> <http://www.linkedin.com/company/3258288>> Youtube >>>>>>>> <https://www.youtube.com/redhatlatam >>>>>>>> <https://www.youtube.com/redhatlatam>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> jbossdeveloper mailing list >>>>>>>> jbossdeveloper(a)lists.jboss.org >>>>>>>> <mailto:jbossdeveloper@lists.jboss.org> >>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>>>>>>> <https://lists.jboss.org/mailman/listinfo/jbossdeveloper> >>>>>>> _______________________________________________ >>>>>>> jbossdeveloper mailing list >>>>>>> jbossdeveloper(a)lists.jboss.org >>>>>>> <mailto:jbossdeveloper@lists.jboss.org> >>>>>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper >>>>>>> <https://lists.jboss.org/mailman/listinfo/jbossdeveloper> >>>>>> >>>>>> /max >>>>>> http://about.me/maxandersen <http://about.me/maxandersen> >>>> >>>> /max >>>> http://about.me/maxandersen > > > /max > http://about.me/maxandersen