simple-openid dependency broken for 0.9.4

[GoogleCodeExporter]

.../samples/simple-openid $ mvn jetty:run (as instructed by README)

[INFO] Failed to resolve artifact.

Missing:
----------
1) org.openid4java:openid4java:jar:0.9.4

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.openid4java -
DartifactId=openid4java \
          -Dversion=0.9.4 -Dpackaging=jar -Dfile=/path/to/file

  Path to dependency:
        1) org.openid4java:simple-openid:war:0.9.4
        2) org.openid4java:openid4java:jar:0.9.4

----------
1 required artifact is missing.

for artifact:
  org.openid4java:simple-openid:war:0.9.4

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

Original issue reported on code.google.com by Johnny.B...@gmail.com on 18 Oct 2007 at 6:44

[GoogleCodeExporter]

Sutra, can you please have a look at this? I'm not sure what's required to have 
maven resolve the dependencies for simple-openid. Thanks!

Original comment by Johnny.B...@gmail.com on 18 Oct 2007 at 6:45

[GoogleCodeExporter]

version 0.9.4 of openid4java doesn't exists currently (only 0.9.4.339 from my
repository).

Ths svn version is 0.9.5-SNAPSHOT. I'm doing update, not yet committed.

Original comment by david.bernard.31 on 18 Oct 2007 at 7:04

[GoogleCodeExporter]

I committed the change.
before running "mvn jetty:run" in simple-openid, you need to go to maven2 dir 
and run
"mvn install".

Original comment by david.bernard.31 on 18 Oct 2007 at 7:08

[GoogleCodeExporter]

I ran a "mvn install", which downloaded some POMs and JARs. Back to the simple-
openid folder, I get the same error, for org.openid4java:openid4java:jar:0.9.5-
SNAPSHOT.

Original comment by Johnny.B...@gmail.com on 18 Oct 2007 at 7:29

[GoogleCodeExporter]

what have you in 
$HOME/.m2/repository/org/openid4java/openid4java/0.9.5-SNAPSHOT ?

svn update
cd maven2
mvn clean install #end by "BUILD SUCCESSFULL" ?

Original comment by david.bernard.31 on 18 Oct 2007 at 7:38

[GoogleCodeExporter]

Thanks I got it working.

When is the 'mvn install' step required? We should document it within 
simple-openid.

Original comment by Johnny.B...@gmail.com on 18 Oct 2007 at 9:22

[GoogleCodeExporter]

mvn install is required after fresh svn checkout, svn update or change in the 
source,
to place the jar in a shared area, from where other project like samples could 
pick
the jar.

I'll update the doc tomorrow.

Original comment by david.bernard.31 on 18 Oct 2007 at 9:28

[GoogleCodeExporter]

Thanks a lot, looks great and works with ant 1.6.5 as well!

The patch is surprinsingly light :) If we're going to use ivy for other parts 
of the 
project, the dependencies / configuration will be handled through the ivy.xml 
file, 
correct? (And the stuff under tools/ivy/ won't have to be touched on a regular 
basis.)

Original comment by Johnny.B...@gmail.com on 19 Oct 2007 at 5:52

[GoogleCodeExporter]

It take some time to read/understand ivy documentation. I forgot the evering is 
(need
?) configurable ant syndrome. 

* right the tools/ivy won't have to be touched except to upgrade version or 
improve
settings (I'm a newbee in ivy).
* the patch need to be completed every test's dependencies aren't define with 
ivy
(jetty isn't include)
* conversion to ivy need to read and understand better the ivy concept and
configuration (and configuration concept ;) ).
* I didn't found how to exclude useless transitive dependencies with ivy

Because project could be build with maven, I think it's possible to build it 
with ivy
and then remove the lib directory from svn.

May be a vote (on the mailing list) could be done about directory layout, 
convention,
builder (ant+jar, ant+ivy, maven2, one or two, which is the main). 

an interesting read : ivy/maven compaison 
http://ant.apache.org/ivy/m2comparison.html

Original comment by david.bernard.31 on 19 Oct 2007 at 7:41

• Changed state: Fixed

[GoogleCodeExporter]

Oups, I didn't update the doc, the issue isn't fixed

Original comment by david.bernard.31 on 19 Oct 2007 at 7:43

• Changed state: Started

[GoogleCodeExporter]

The 'ant clean' target should delete the lib/test/ folder; is there a way to 
reference the ivy configuration from there, as opposed to manually having to 
put the 
"lib/test/" path in the clean target?

Original comment by Johnny.B...@gmail.com on 19 Oct 2007 at 8:22

[GoogleCodeExporter]

may be, I don't know. I saw some information about cleaning with ivy but I don't
remember.
Later this week-end I'll try to use the maven antlib instead of ivy antlib for 
test
dependency (to doc is less confuse).

Original comment by david.bernard.31 on 19 Oct 2007 at 8:29

[GoogleCodeExporter]

Okay, as long as that does not add a dependency to maven itself for the ant 
users 
who don't have maven installed. That is: 'ant jar/clean/test' should keep 
working 
seamlesly out of the box.

Original comment by Johnny.B...@gmail.com on 20 Oct 2007 at 5:39

[GoogleCodeExporter]

Original comment by david.bernard.31 on 27 Oct 2007 at 9:23

• Changed state: Fixed