repo to all my projects -- just
something I've gotten used to. I do agree, though, that it would be
convenient to have those in the central repo. If someone can point me
to the directions on how to make that happen, I'll see if I can track
down the person inside Sun that can take care of it on our side. From
the looks of central, it appears we used to do that, but stopped. No
idea, but maybe we'll find out.
On Oct 21, 2009, at 5:29 PM, Dan Allen wrote:
Thanks Jason.
Hmm, so for people using Weld from central, should they be required
to add the
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(a)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 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(a)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
Jason Lee, SCJP
President, Oklahoma City Java Users Group
Senior Java Developer, Sun Microsystems