Sande,

I think you can do it, after we "inject" the repository definition at the pom.xml sources. I'm not sure if we will be able to do that until 6.4 release. (I'm not aware about the release schedule)

On 10/31/14 14:49, Sande Gilda wrote:

Which reminds me. Should I remove the 3rd paragraph (see below) from this topic [1] in the JBoss EAP 6.4 Development Guide?

This method of configuration is generally not recommended. If you decide to configure repositories in your project POM file, plan carefully and be aware that it can slow down your build and you may even end up with artifacts that are not from the expected repository.

[1] https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Development_Guide/index.html#Configure_the_JBoss_Enterprise_Application_Platform_Maven_Repository_Using_the_Project_POM

On 10/31/2014 12:39 PM, Pete Muir wrote:

We’re switching back :-/

On 31 Oct 2014, at 15:48, Keith Babo <kbabo@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@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>