<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>
10 years, 7 months
JBoss Developer production builds down over holiday period
by Paul Robinson
All,
Given that most of us are away for the next two weeks, we thought it best not to rebuild+publish the JBoss Developer production site every 6 hours, like we currently do. Should something go wrong it is unlikely that we would notice, plus I don’t really want to be on-call to fix it ;-)
I’ll re-enable on January the 5th.
Paul.
--
Paul Robinson
JBoss Developer Team Lead (www.jboss.org)
Free/busy info: https://www.google.com/calendar/embed?src=probinso%40redhat.com&ctz=Europ...
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)
10 years, 11 months
Re: [jbossdeveloper] Fwd: BRMS 6 Quickstarts
by Rafael Benevides
Hi all,
Since this email in March, the BRMS/BPMS Quickstarts become part of
product release since version 6.0.2+
On the latest meeting with Geoffrey and Petr we discussed about the
"owner" of these Quickstarts. As conclusion, we decided to formalize the
donation of them to BRMS/BRPMS team.
I'd like to ask that the person from BPMS/BRMS team that will take
responsibility on them, to join jbossdeveloper(a)lists.jboss.org (
https://lists.jboss.org/mailman/listinfo/jbossdeveloper ) so he can be
aware of the latest discussion about JBoss Developer Materials.
Thanks BRMS/BPMS team for the support that I received during Quickstarts
development.
Rafael
On 3/18/14 09:56, Rafael Benevides wrote:
> Hi all,
>
> After a long development cycle and review and some feedbacks ( Thanks
> Sande, Burr, Geoffrey ), the BRMS Quickstarts (
> https://github.com/jboss-developer/jboss-brms-quickstarts ) are ready!
>
> From now, I think they can be included as part of BRMS distro for 6.1
>
> Feel free to poke it.
>
> Em 06/01/14 11:12, Rafael Benevides escreveu:
>> I opened the following Jiras, so we can discuss over them individually.
>>
>> [JDF-581] Create Beginner BRMS Quicsktart: helloworld-drl
>> [JDF-582] Create an Intermediate BRMS Quickstart: helloworld-stateful
>> [JDF-583] Create an Intermediate BRMS Quickstart: helloworld-brms
>> [JDF-584] Create an Intermediate BRMS Quickstart: decision-table
>> [JDF-585] Create an Advanced BRMS Quickstart: store-dsl
>> [JDF-586] Create an Advanced BRMS Quickstart: helloworld-cep
>> [JDF-587] Create an Advanced BRMS Quickstart: brms-integration
>> [JDF-588] Create an Advanced BRMS Quickstart: brms-planner
>> [JDF-589] Create an Intermediate BPMS Quickstart: brms-bpms
>> [JDF-590] Create an Advanced BPMS Quickstart: brms-bpms-task
>>
>> Em 03/01/14 13:48, Rafael Benevides escreveu:
>>> Hi all,
>>>
>>> Today I talked to Edson Tirelli on #droolsdev so the Drools team can
>>> be aware of this effort by our side.
>>>
>>> I also discovered that they already have their Maven BOMs on
>>> https://github.com/droolsjbpm/droolsjbpm-build-bootstrap . It was
>>> discussed that we could move this repo to
>>> https://github.com/jboss-developer/jboss-brms-boms for BRMS 6.1
>>>
>>> Anyway the JBoss Developer materials uses a little bit different
>>> GAV: org.jboss.bom.brms:jboss-javaee-6.0-with-drools:6.1-redhat-X -
>>> Probably wrapping the existing BRMS BOMs should be better to avoid
>>> too much changes for BRMS 6.1. Don't you agree ? But if we do it, we
>>> will have two BRMS BOMs ( the one provided by Drools and one
>>> provided by JBoss Developer Materials). Any comments on this are
>>> welcome!
>>>
>>> I'm copying them so they can be evolved on the discussion and
>>> provide any feedback. Edson, Mark, feel free also to give any
>>> feedback on the proposed Quickstarts below.
>>>
>>>
>>>
>>> -------- Mensagem original --------
>>> Assunto: BRMS 6 Quickstarts
>>> Data: Mon, 23 Dec 2013 12:49:46 -0200
>>> De: Rafael Benevides <benevides(a)redhat.com>
>>> Empresa: Red Hat
>>> Para: Peter Muir <pmuir(a)redhat.com>, Burr Sutter <bsutter(a)redhat.com>
>>>
>>>
>>>
>>> Hi Pete/Burr
>>>
>>> I'm starting to plan BRMS 6 Quickstarts and besides the BRMS BOM (
>>> https://github.com/jboss-developer/jboss-brms-boms ), I also would
>>> like to included the following quickstarts that I'm planning:
>>>
>>> The idea is to discuss/check if the features covered are OK and also
>>> hear any kind of feedback about the possible uses cases.
>>>
>>> Note: 1- Some of them I didn't think yet about what use cases to
>>> show, but the idea is to focus on the feature.
>>> 2 - I'm not familiar with BPM (last BPM project that I used was jBPM
>>> 3), so it is possible that the features are not well covered, so any
>>> feedback are welcome!
>>>
>>> Basic
>>> helloworld-drl: Basic - A simple helloworld reading a DRL from
>>> Classpath integrated with CDI
>>>
>>> Intermediate
>>> helloworld-stateful: Intermediate - A use case for Stateful session.
>>> Maybe Stock Monitoring
>>> helloworld-brms: Intermediate - The same application reading the DRL
>>> from the BRMS server using the Agent
>>> decision-table: Intermediate - Any use case reading a Decision Table
>>> from BRMS server
>>>
>>> Advanced:
>>> store-dsl: Advanced - A DSL rule using Type Declaration and Functions
>>> helloworld-cep: Advanced: Check for fraudulent credidt card
>>> transaction based on amount paid in a time frame.
>>> brms-integration: Advanced: Use case to show Drools Commands
>>> brms-planner: Advanced: Use case for planning a routing example.
>>>
>>> BPMS:
>>> brms-bpms: Intermediate: Use case for bpms
>>> brms-bpms-task: Advanced: Use case for bpms with Human Tasks
>>>
>>> -
>>> --
>>>
>>> *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>
>>>
>>>
>>
>
11 years
Production and Staging builds disabled
by Paul Robinson
All,
I’ve disabled the Production and Staging CI builds for about 18hours. It should be back on by 10:00 UTC on Thursday. This is to confirm that the bad data, we are seeing, is not being put into the DCP by our CI.
If anyone needs these to run, before then, please let me know.
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)
11 years
Doing a Staging build locally
by Paul Robinson
All,
Is anyone doing a staging build of the site on their local machine? You’d probably be using this command:
rake preview[staging]
We are seeing some odd data appear in the DCP server used by the staging sites. I’m trying to track down where it is coming from.
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)
11 years
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
11 years
