[weld-dev] missing artifacts in central

Shane Bryzak sbryzak at redhat.com
Wed Oct 21 21:34:15 EDT 2009


It was quite easy to set up - instructions are here: 
http://nexus.sonatype.org/oss-repository-hosting.html

Shane

On 22/10/09 08:29, Dan Allen wrote:
> Thanks Jason.
>
> Hmm, so for people using Weld from central, should they be required to 
> add the java.net <http://java.net> 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.
>
> 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.
>
> -Dan
>
> On Wed, Oct 21, 2009 at 6:26 PM, Jason Lee <jason at steeplesoft.com 
> <mailto:jason at steeplesoft.com>> wrote:
>
>     That artifact is deployed here:
>
>     http://download.java.net/maven/2/javax/faces/jsf-api/2.0/
>
>     Note the version AND the repo. AFAIK, all Sun artifacts are
>     deployed to the java.net <http://java.net> repo.
>
>     On Oct 21, 2009, at 5:14 PM, Dan Allen wrote:
>
>>     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.
>>
>>     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.
>>
>>     -Dan
>>
>>     Missing:
>>     ----------
>>     1) javax.faces:jsf-api:jar:2.0.0-RC
>>
>>      Try downloading the file manually from the project website.
>>
>>      Then, install it using the command:
>>         mvn install:install-file -DgroupId=javax.faces
>>     -DartifactId=jsf-api -Dversion=2.0.0-RC -Dpackaging=jar
>>     -Dfile=/path/to/file
>>
>>      Alternatively, if you host your own repository you can deploy
>>     the file there:
>>         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]
>>
>>      Path to dependency:
>>         1) org.example:helloworld:war:0.0.1-SNAPSHOT
>>         2) javax.faces:jsf-api:jar:2.0.0-RC
>>
>>     ----------
>>     1 required artifact is missing.
>>
>>     for artifact:
>>      org.example:helloworld:war:0.0.1-SNAPSHOT
>>
>>     from the specified remote repositories:
>>      central (http://repo1.maven.org/maven2)
>>
>>     -Dan
>>
>>     -- 
>>     Dan Allen
>>     Senior Software Engineer, Red Hat | Author of Seam in Action
>>     Registered Linux User #231597
>>
>>     http://mojavelinux.com
>>     http://mojavelinux.com/seaminaction
>>     http://www.google.com/profiles/dan.j.allen
>>     _______________________________________________
>>     weld-dev mailing list
>>     weld-dev at lists.jboss.org <mailto:weld-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/weld-dev
>
>     Jason Lee, SCJP
>     President, Oklahoma City Java Users Group
>     Senior Java Developer, Sun Microsystems
>     http://blogs.steeplesoft.com
>
>
>
>
> -- 
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20091022/7ecf0fc7/attachment.html 


More information about the weld-dev mailing list