<repository /> definition in pom.xml for Quickstarts and Demos
by Rafael Benevides
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/>
LinkedIn <http://www.linkedin.com/company/3258288> Youtube
<https://www.youtube.com/redhatlatam>
9 years, 1 month
Re: [jbossdeveloper] <repository /> on quickstarts pom.xml
by Pete Muir
On 16 Sep 2014, at 00:27, Max Rydahl Andersen <max.andersen(a)redhat.com> wrote:
> On 9 Sep 2014, at 16:07, Rafael Benevides wrote:
>
>> We also need to check that with JBDS, because it's odd that stacks only
>> uses "redhat-techpreview-all-repository" as additional repository.
>
> because it was the only thing we needed originally.
>
>> Max/Fred,
>>
>> Is there any issues having
>> https://maven.repository.redhat.com/earlyaccess/all/ as declared inside
>> quickstarts pom.xml ?
>
> sorry - but I need to grok when earlyaccess/all is even needed before answering that ? :)
>
> My default position would be that if you need earlyaccess you are expected to be able to understand why you need it.
>
> But i'm not sure if that is true anymore - hence wanting to ask why/when earlyaccess is ever needed ?
> is it for running quickstarts targeting a beta version of EAP ? (meaning no snapshots, but actual all releases in it?)
Right, it’s where we put beta and alpha releases.
>
> If yes, why doesn't /all get split up in /supported and /earlyaccess and /all will serve the combined result ?
Propose this on the wolf list?
>
> Meaning we remove the need to have two different repos always handed around but allow those who want the separation to just use /supported if need be.
>
> i.e. do what maven normally does (use version numbers to separate things) and stop having it be a complex setup for the default case ?
>
> /max
>
>>
>> Em 9/9/14, 9:27, Pete Muir escreveu:
>>> On 9 Sep 2014, at 13:06, Marek Novotny <mnovotny(a)redhat.com> wrote:
>>>
>>>> On 9.9.2014 13:56, Pete Muir wrote:
>>>>> On 9 Sep 2014, at 12:54, Marek Novotny <mnovotny(a)redhat.com> wrote:
>>>>>
>>>>>> On 9.9.2014 13:00, Pete Muir wrote:
>>>>>>> On 9 Sep 2014, at 11:35, Marek Novotny <mnovotny(a)redhat.com> wrote:
>>>>>>>
>>>>>>>> On 8.9.2014 18:48, Pete Muir wrote:
>>>>>>>>>>>>>>> QSTools ticket: https://issues.jboss.org/browse/JDF-762
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> But after placing http://maven.repository.redhat.com/techpreview/all/ at the Quickstarts, I realized that we won't solve the user experience issues without adding - https://maven.repository.redhat.com// and
>>>>>>>>>>>>>>> - http://jboss-developer.github.io/temp-maven-repo/ also
>>>>>>>>>>>>>>> for the -develop branch.
>>>>>>>>>>>>> I’m not sure we need to worry about people using the -develop branch. This is for contributors only, and they can read the instructions normally.
>>>>>>>>>>> So I assume that we need to inject http://maven.repository.redhat.com/techpreview/all/ in pom.xml and make them to add the others in settings.xml
>>>>>>>>> Well, we may want to add earlyaccess too. WDYT?
>>>>>>>>>
>>>>>>>> Why we should have it there for end users? earlyaccess repository is
>>>>>>>> just exceptional resource for public Betas, isn't it? Isn't that
>>>>>>>> confusing to have it there even for traditional GA releases?
>>>>>>> OTOH this is not really the way Maven works. In Maven you tend to mix up all releases, and use version numbers to control what gets pulled in.
>>>>>> Even I agree with your statement, do we have a clean description there
>>>>>> what could end users understand why we have a bunch or repositories
>>>>>> there instead of one? We declared today that you can use our product
>>>>>> maven repository (online techpreview/all or offline zipped repository)
>>>>>> plus Central and then in Quickstarts we use "another" repository.
>>>>>>
>>>>>> I agree that injected repository will help to an end user, but wouldn't
>>>>>> it be simple just as one repository?
>>>>>>
>>>>>> you can easily manage versions in BOM imports etc. but for the learning
>>>>>> purpose it can be confusing. WDYT?
>>>>> Hmm. People are used to adding a second repo for snapshots, which is kinda similar.
>>>>>
>>>> What are our target group of developers for quicksktarts? Newbies or
>>>> experienced devs?
>>>>
>>>> I may see it more like short and simple bootstrap for newbies, but your
>>>> view is probably different.
>>> Agreed on newbies. Hence why we don’t want to make people add/remove repos, but have a sensible default configured for them.
>>>
>>>>
>>>> --
>>>> Marek Novotny
>>>> --
>>>> WFK and Seam Product Lead
>>>>
>>>> Red Hat Czech s.r.o.
>>>> Purkynova 99
>>>> 612 45 Brno
>>>
>>> _______________________________________________
>>> jbossdeveloper mailing list
>>> jbossdeveloper(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>>
>> _______________________________________________
>> jbossdeveloper mailing list
>> jbossdeveloper(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
>
> /max
> http://about.me/maxandersen
9 years, 6 months
Patchy availability Thurs and Fri
by Paul Robinson
All,
My availability will be patchy on Thursday and Friday. We are moving offices, plus I have some teaching and personal matters to attend to.
I’ll keep an eye on email, but response times could be higher.
Paul.
--
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors:Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Paul Hickey (Ireland)
9 years, 7 months
