Closed GoogleCodeExporter closed 9 years ago
Original comment by sujata...@gmail.com
on 15 Sep 2011 at 3:12
Original comment by sujata...@gmail.com
on 16 Apr 2012 at 8:30
I saw you flagged this as Started; nice thing. Do you have an ETA?
thanks
Original comment by jose.lec...@gmail.com
on 17 Apr 2012 at 6:26
Issue fixed. please include the following reference to the repo in your build.
<repositories>
<repository>
<id>resting</id>
<url>http://resting.googlecode.com/svn/trunk/repo</url>
</repository>
</repositories>
Let me know if you face any issues.
Original comment by lpriyapa...@gmail.com
on 18 Apr 2012 at 11:13
Original comment by lpriyapa...@gmail.com
on 18 Apr 2012 at 11:15
Reassigning to Sujata for verification.
Original comment by lpriyapa...@gmail.com
on 18 Apr 2012 at 11:17
so, which areis the groupId, artifactId, versions available?
Original comment by jose.lec...@gmail.com
on 19 Apr 2012 at 1:52
groupid=com.google.resting
artifactId=resting
version=0.7
Right now I have made only the latest release (0.7) available.
Original comment by lpriyapa...@gmail.com
on 20 Apr 2012 at 12:34
so, have you tested it?
it's not working
Original comment by jose.lec...@gmail.com
on 20 Apr 2012 at 5:42
There is a typo in the reference URL.
<repositories>
<repository>
<id>resting</id>
<url>http://resting.googlecode.com/svn/trunk/resting/repo</url>
</repository>
</repositories>
Original comment by lpriyapa...@gmail.com
on 21 Apr 2012 at 11:17
there are files under that location now.
However, the artifactId should be resting-java or resting-android
pls, do at least a minor testing before fix-close the issues or pass the info.
I'm pretty sure that will help to bring more users.
Original comment by jose.lec...@gmail.com
on 23 Apr 2012 at 7:22
hmmm
so you have published a bundle...
Sujata, have you ever tested this? :s
Original comment by jose.lec...@gmail.com
on 23 Apr 2012 at 8:00
Hi Jose,
The status of this issue is *Fixed*, which, by the words of Google Code,
means "*Developer made source code changes, QA should verify". *This
indicates that the fix has been committed by developer, *but not yet tested.
*
Once it is tested, the status will change to *Verified*. It is then the
issue can be considered as tested and closed for the particular build.
Please use a fix only after it has been moved to the state of *Verified*.
Thanks
Sujata
Original comment by sujata...@gmail.com
on 24 Apr 2012 at 6:13
so, do you need help on QA?
The bundle you published seems not to work, since nor the IDE nor the
classloader can reach classes inside your jar. I think you should publish a
real maven built artifact, with its pom file included
Original comment by jose.lec...@gmail.com
on 24 Apr 2012 at 12:49
Original issue reported on code.google.com by
jose.lec...@gmail.com
on 11 Sep 2011 at 4:36