<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
It seems that staging repo is not being used anymore. I asked on
another thread (you were copied) to review this process. <br>
<br>
After the process is reviewed and clarified, we should update "JBoss
Developer Materials Repository Management and Releases" MOJO [1]
with those clarification points.<br>
<br>
Anyway, adding and removing repos from pom.xml files is easy as
running: mvn -U org.jboss.maven.plugins:qstools:repositories<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://mojo.redhat.com/docs/DOC-928619">https://mojo.redhat.com/docs/DOC-928619</a><br>
<br>
<meta charset="utf-8">
<div class="moz-cite-prefix">On 11/27/14 11:25, Sande Gilda wrote:<br>
</div>
<blockquote cite="mid:5477264E.1040306@redhat.com" type="cite">I am
a little confused by this discussion.
<br>
<br>
Are we saying we will add the staging repo [1] to the development
branch POM files only and we then have to strip them from the
product branch POM files? I think it is going to be hard to
maintain different POM file contents in different branches.
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://jboss-developer.github.io/temp-maven-repo">http://jboss-developer.github.io/temp-maven-repo</a>
<br>
<br>
On 11/27/2014 07:15 AM, Rafael Benevides wrote:
<br>
<blockquote type="cite">On 11/27/14 10:04, Julian Coleman wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
<blockquote type="cite">I think that the staging repo is the
answer here for testing purposes.
<br>
</blockquote>
I think that this makes sense too. However, I'm not sure how
we will test
<br>
the final version, as that will need a reference to the public
repository
<br>
and be tested before the public repository contains the
artifacts.
<br>
</blockquote>
We use a different process that we have the final versions
released
<br>
previously having the "-build-x" suffix at the version and place
those
<br>
versions at <a class="moz-txt-link-freetext" href="http://jboss-developer.github.io/temp-maven-repo/">http://jboss-developer.github.io/temp-maven-repo/</a>
repo
<br>
(which is our "staging" repo until we have a nexus server
setup). But I
<br>
know that this process is particular and couldn't fit for every
project.
<br>
Do you see any restrictions to test the final version using the
internal
<br>
repo and having that repo defined in settings.xml ?
<br>
<blockquote type="cite">
<blockquote type="cite">I think so, otherwise we won't achieve
our objectives to have buildable
<br>
sources at github.
<br>
</blockquote>
Will it matter if we reference an internal repository in the
sources?
<br>
(It won't be possible to build them trivially from outside the
Red Hat
<br>
network.)
<br>
</blockquote>
In that case, that's why we used
<br>
<a class="moz-txt-link-freetext" href="http://jboss-developer.github.io/temp-maven-repo/">http://jboss-developer.github.io/temp-maven-repo/</a> as a staging
maven repo.
<br>
<blockquote type="cite">Thanks,
<br>
<br>
J
<br>
<br>
</blockquote>
_______________________________________________
<br>
jbossdeveloper mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jbossdeveloper@lists.jboss.org">jbossdeveloper@lists.jboss.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbossdeveloper">https://lists.jboss.org/mailman/listinfo/jbossdeveloper</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>