Sounds like this tool can take care of updating the repository refs to whatever JDF wants,
so yeah, I think it would be good to have them in the project quickstarts.
On Oct 31, 2014, at 2:03 PM, Rob Cernich <rcernich(a)redhat.com> wrote:
So does that mean we can/should put the repository definitions back
into the quickstart poms?
We’re switching back :-/
On 31 Oct 2014, at 15:48, Keith Babo <kbabo(a)redhat.com> wrote:
Hey - this caught me a bit by surprise. I thought that the JDF approach was to
externalize repository definitions from the pom.xml and reference them via an external
settings.xml. I ask because we have traditionally included repo definitions in SY
quickstarts.
thanks,
keith
On Oct 31, 2014, at 9:56 AM, Rafael Benevides <benevides(a)redhat.com> 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
<{a8aabf3a-4467-4e37-9bc5-48b1d7b494a2}_LATAM_RedHat.jpg>
Better technology. Faster innovation. Powered by community collaboration.
See how it works at
www.redhat.com
<linkedin.png> <youtube.png>