<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I can say that only about latest
(2.3.x) releases from top of my head. <br>
<br>
On 08/28/2013 04:25 PM, Jason Porter wrote:<br>
</div>
<blockquote cite="mid:1377699948489.2929774d@Nodemailer" type="cite">
<div>Ah. Are the final artifacts not affected by this?</div>
<div class="mailbox_signature">—<br>
Sent from <a moz-do-not-send="true"
href="https://www.dropbox.com/mailbox">Mailbox</a> for iPhone</div>
<br>
<br>
<div class="gmail_quote">
<p>On Wed, Aug 28, 2013 at 8:24 AM, Marek Novotny <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:mnovotny@redhat.com" target="_blank">mnovotny@redhat.com</a>></span>
wrote:<br>
</p>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="moz-cite-prefix">well, but that involves a
dedicated person, which needs to go through all released
versions and verify that all dependencies come from Maven
Central. I know/suppose that this verification has to be
done before Central sync is setup.<br>
Artifacts in central need to be self contained in Central
repo.<br>
<br>
Old releases certainly are affected by a relation to
repository.jboss.org and in parallel by unique GAV which are
not in Central at all.<br>
<br>
On 08/28/2013 03:53 PM, Jason Porter wrote:<br>
</div>
<blockquote cite="mid:1377697997695.a238f3f5@Nodemailer"
type="cite">
<div>I don't see a reason why we shouldn't sync non final
artifacts. </div>
<div> <br>
</div>
<div>If the artifacts are already in JBoss Nexus instance,
we should be fine to simply sync them to central. We'll
need to remove any instances of the JBoss repo from the
poms and make sure all the other dependencies are in
central too, but that shouldn't take long. </div>
<div class="mailbox_signature">—<br>
Sent from <a moz-do-not-send="true"
href="https://www.dropbox.com/mailbox">Mailbox</a> for
iPhone</div>
<br>
<br>
<div class="gmail_quote">
<p>On Wed, Aug 28, 2013 at 6:25 AM, Marek Novotny <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:mnovotny@redhat.com" target="_blank">mnovotny@redhat.com</a>></span>
wrote:<br>
</p>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<p>I find out that we need to contact Joel Orlina from
sonatype and ask for<br>
the synchronization.<br>
<br>
Do we have any special requirements for that?<br>
<br>
I would let to ask for synchronization of Seam
2.3.1.Final artifacts<br>
only or you have different idea?<br>
<br>
On 07/31/2013 05:25 PM, Jason Porter wrote:<br>
> I can't find it (big surprise, searching through
docspace, right?).<br>
> Paul Gier should be the man to talk to though.<br>
><br>
><br>
> On Wed, Jul 31, 2013 at 7:33 AM, Jason Porter
<<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:lightguard.jp@gmail.com">lightguard.jp@gmail.com</a><br>
> <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:lightguard.jp@gmail.com"><mailto:lightguard.jp@gmail.com></a>>
wrote:<br>
><br>
> IIRC there's a docspace page or some one at
Sonatype we talk to.<br>
> I'll dig a big more. Paul Would also know. <br>
> —<br>
> Sent from Mailbox <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="https://www.dropbox.com/mailbox"><https://www.dropbox.com/mailbox></a>
for iPhone<br>
><br>
><br>
> On Wed, Jul 31, 2013 at 1:20 AM, Marek Novotny<br>
> <<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:mnovotny@redhat.com">mnovotny@redhat.com</a>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mnovotny@redhat.com"><mailto:mnovotny@redhat.com></a>>
wrote:<br>
><br>
> No problem, you asked for Seam3 synchronization,
right? I can<br>
> see it in<br>
> <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://community.jboss.org/wiki/MavenRepositoryCentralSynchronization">https://community.jboss.org/wiki/MavenRepositoryCentralSynchronization</a><br>
> , but there is no link to howto get something in.<br>
><br>
> What is the process to add something to Maven
Central<br>
> synchronization? Could you help me with that?<br>
><br>
> On 07/30/2013 06:49 PM, Jason Porter wrote:<br>
>> I think we should readdress that now that
Seam 2 is using<br>
>> Maven, and we want our builds (and the
customers and<br>
>> community) to be consistent.<br>
>><br>
>><br>
>> On Tue, Jul 30, 2013 at 2:15 AM, Marek
Novotny<br>
>> <<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:mnovotny@redhat.com">mnovotny@redhat.com</a>
<a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:mnovotny@redhat.com"><mailto:mnovotny@redhat.com></a>>
wrote:<br>
>><br>
>> No specific reason, only that it wasn't the
priority for<br>
>> Seam2 to be in Central.<br>
>><br>
>> On 07/29/2013 08:38 PM, Jason Porter wrote:<br>
>>> Is there any reason we're not syncing
these artifacts<br>
>>> (the community bits) to Central?<br>
>>><br>
>>><br>
><br>
><br>
><br>
> -- <br>
> Jason Porter<br>
> <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://en.gravatar.com/lightguardjp">http://en.gravatar.com/lightguardjp</a><br>
<br>
<br>
-- <br>
Marek Novotny<br>
--<br>
WFK and Seam Product Lead<br>
<br>
Red Hat Czech s.r.o.<br>
Purkynova 99<br>
612 45 Brno<br>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a></p>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
</pre>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Marek Novotny
--
WFK and Seam Product Lead
Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
</pre>
</body>
</html>