<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
It was quite easy to set up - instructions are here:
<a class="moz-txt-link-freetext" href="http://nexus.sonatype.org/oss-repository-hosting.html">http://nexus.sonatype.org/oss-repository-hosting.html</a><br>
<br>
Shane<br>
<br>
On 22/10/09 08:29, Dan Allen wrote:
<blockquote
cite="mid:19758da0910211529g684d40beqb102e3d49a4a8c4e@mail.gmail.com"
type="cite">Thanks Jason.<br>
<br>
Hmm, so for people using Weld from central, should they be required to
add the <a moz-do-not-send="true" href="http://java.net">java.net</a>
repo? To better advocate the standard platform, would it be feasible to
have these artifacts pushed to the central repo? JBoss setup a channel
with Sonatype that allows the artifacts to be passed on to central w/o
too much headache.<br>
<br>
Could someone on the Weld team that was involved in getting the
artifacts published to central communicate with Jason about how this
publishing takes place? Perhaps Sun would consider using it.<br>
<br>
-Dan<br>
<br>
<div class="gmail_quote">On Wed, Oct 21, 2009 at 6:26 PM, Jason Lee <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:jason@steeplesoft.com">jason@steeplesoft.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">That artifact is deployed here:
<div><br>
</div>
<div><a moz-do-not-send="true"
href="http://download.java.net/maven/2/javax/faces/jsf-api/2.0/"
target="_blank">http://download.java.net/maven/2/javax/faces/jsf-api/2.0/</a></div>
<div><br>
</div>
<div>Note the version AND the repo. AFAIK, all Sun artifacts are
deployed to the <a moz-do-not-send="true" href="http://java.net"
target="_blank">java.net</a> repo.</div>
<div><br>
<div>
<div>
<div class="h5">
<div>On Oct 21, 2009, at 5:14 PM, Dan Allen wrote:</div>
<br>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">One user is reporting that the JSF 2 artifact is
missing from the central repo, which weld depends on. Therefore, users
must still use the JBoss Maven 2 repository to build a JSF app with
Weld.<br>
<br>
Who is willing to track down how to get this artifact uploaded? I know
how to get something into the JBoss repository, but not central.
Perhaps we need to hound the Mojarra team to publish a JSF 2.0 artifact.<br>
<br>
-Dan<br>
<br>
Missing:<br>
----------<br>
1) javax.faces:jsf-api:jar:2.0.0-RC<br>
<br>
Try downloading the file manually from the project website.<br>
<br>
Then, install it using the command:<br>
mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-api
-Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file<br>
<br>
Alternatively, if you host your own repository you can deploy the file
there:<br>
mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-api
-Dversion=2.0.0-RC -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]<br>
<br>
Path to dependency:<br>
1) org.example:helloworld:war:0.0.1-SNAPSHOT<br>
2) javax.faces:jsf-api:jar:2.0.0-RC<br>
<br>
----------<br>
1 required artifact is missing.<br>
<br>
for artifact:<br>
org.example:helloworld:war:0.0.1-SNAPSHOT<br>
<br>
from the specified remote repositories:<br>
central (<a moz-do-not-send="true" href="http://repo1.maven.org/maven2"
target="_blank">http://repo1.maven.org/maven2</a>)<br>
<br>
-Dan<br clear="all">
<br>
-- <br>
Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br>
<br>
<a moz-do-not-send="true" href="http://mojavelinux.com"
target="_blank">http://mojavelinux.com</a><br>
<a moz-do-not-send="true"
href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a moz-do-not-send="true"
href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>
</div>
</div>
_______________________________________________<br>
weld-dev mailing list<br>
<a moz-do-not-send="true" href="mailto:weld-dev@lists.jboss.org"
target="_blank">weld-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/weld-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/weld-dev</a></blockquote>
</div>
<br>
<font color="#888888">
<div>
<div style=""><span
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<div style="">
<div>
<div style="">
<div style="">
<div>
<div><span style="font-size: medium;"><span style="font-size: 14px;">
<div>Jason Lee, SCJP</div>
<div>President, Oklahoma City Java Users Group</div>
<div>Senior Java Developer, Sun Microsystems</div>
<div><a moz-do-not-send="true" href="http://blogs.steeplesoft.com"
target="_blank">http://blogs.steeplesoft.com</a></div>
</span></span></div>
</div>
</div>
</div>
</div>
</div>
</span></div>
</div>
<br>
</font></div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<br>
<br>
<a moz-do-not-send="true" href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a moz-do-not-send="true" href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a moz-do-not-send="true"
href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
weld-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:weld-dev@lists.jboss.org">weld-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/weld-dev">https://lists.jboss.org/mailman/listinfo/weld-dev</a></pre>
</blockquote>
<br>
</body>
</html>