[jbossdeveloper] <repository /> on quickstarts pom.xml

[Max Rydahl Andersen]

On 25 Aug 2014, at 15:26, Geoffrey De Smet wrote:

> +1 We're doing the same in our examples, by adding a bootstrap 
> repository:
> https://github.com/droolsjbpm/optaplanner/blob/master/optaplanner-examples/pom.xml#L23

I assume this is the case, but just want to be sure that pom.xml is not 
used in examples shipped/documented for our products :)

We should never ever in our published product examples require jboss.org 
repositories - only maven.repository.redhat.com ones.

/max


>
> With kind regards,
> Geoffrey De Smet
> OptaPlanner lead
>
> On 25-08-14 15:07, Max Rydahl Andersen wrote:
>> On 25 Aug 2014, at 14:50, Rafael Benevides wrote:
>>
>>> Hi all,
>>>
>>> On a look for a continuous improvement on developer user experience 
>>> and also because we have been constantly asked to support issues 
>>> related to the setup of https://access.redhat.com/maven-repository 
>>> to make the quickstarts work, we want to include the <repository /> 
>>> definition on quickstarts pom.xml
>>>
>>> Actually the Archetypes already have the <repository /> on the 
>>> pom.xml file of the generated project.
>>>
>>> The idea here is to have the <repository /> with the 
>>> https://maven.repository.redhat.com/techpreview/all/ defined on 
>>> every quickstarts's pom.xml file with a comment on top of it saying 
>>> that this approach is not recommended but we included it so users 
>>> can test the quickstarts without further setup and that it's 
>>> recommended to use settings.xml.
>>>
>>> It will bring the following advantages:
>>> - It will make ease to contributors and users
>>> - Simplify the build.
>>> - Simplify the Archetype synch process / No need to inject the repo 
>>> since it will come from the Quickstarts
>>> - We can add a pre-defined comment above the pom.xml repository 
>>> definition to explain that we don't recommend that.
>>> - We can also add this "comment" to QSTools to check/fix it.
>>>
>>> As a roadmap for it:
>>> - We need to document that at the 
>>> https://github.com/jboss-developer/jboss-developer-shared-resources
>>> - We need to update the contributing guides
>>> - We need to update QSTools to do this update on all quickstarts for 
>>> us.
>>>
>>> Max, Is there any restrictions on JBDS side ?
>>
>> No, as long as we keep that comment about its bad practice and don't 
>> start moving it into shared parent pom's we should be fine :)
>>
>>
>> /max
>> http://about.me/maxandersen


/max
http://about.me/maxandersen