It was fixed in Maven 3.2.3 and not present in 3.1.x. If we add
<repository> element we need to make sure people are using right Maven
version.
Karel
On Mon, Aug 25, 2014 at 2:50 PM, Rafael Benevides
<benevides(a)redhat.com> 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 ?
Anyone else have any objections/comments on this $subject ?
Thanks
--
Rafael Benevides | Senior Software Engineer
JBoss Developer
M: +55-61-9269-6576
Better technology. Faster innovation. Powered by community
collaboration.
See how it works at
www.redhat.com