Closed GoogleCodeExporter closed 9 years ago
This is actually fairly hard because there are a zillion dependencies.
Original comment by archie.c...@gmail.com
on 28 Jun 2010 at 9:09
I am working on this one this coming week.
Hopefully only a few days away.
Original comment by roger.parkinson35
on 15 Oct 2011 at 8:02
Some progress. I've built a normal (ie not a packager) repo that does what I
need, specifically it lets me run web services over http just fine, with no
security. It is just using the cxf-bundle rather than all the other cxf options
and I haven't bothered with the server dependencies (geronimo, jetty etc) and
all the other stuff in the 'provided' targets that appeared when it was pulled
from maven.
I also have some dangling dependencies. These are dependencies that some of the
dependent products use, but cxf excludes. I figure if I track those down I
never finish. But this might be against the rules for ivyroundup. Please
comment.
There is some confusion around org.apache.ws.commons/XmlSchema. ivyroundup's
current version is 4.3, cxf has org.apache.ws.xmlschema/xmlschema-core-2.0.1
but on the apache website there is no mention of anything other than the 4.3
version ivyroundup already has. It is the same animal, same package names and
classes anyway.
The security stuff looks okay but I don't have the resource to test it.
I took some shortcuts on one or two items. CXF uses a later version of commons
lang and the one in ivyroundup now seems to work fine so I downgraded the
required version. There are comments in the ivy.xml files so they aren't
forgotten.
There are, then, just 13 products needed to add to ivyroundup. Given the
approach I'm taking is this going to work for other people?
Roger
Original comment by roger.parkinson35
on 20 Oct 2011 at 8:24
I'm not a user of Apaache CXF so can't really comment but this sounds
reasonable to me.
Re: dangling dependencies, they're probably OK for now.
Also I added the newer versions of commons-lang 2.6 and 3.0.1.
Original comment by archie.c...@gmail.com
on 20 Oct 2011 at 1:22
I need to do this in installments. Attached are patches for 4 products that cxf
depends on. There are 16 in total (I said 13 earlier, miscounted). I've made
XmlSchema just another, later version of the one already in ivyroundup. On the
Apache website the prefix changes with the new version and the case is lower
(xmlschema) but I figure it is better to keep compatible.
Thanks for sorting out commons lang.
Let me know if you need these as separate issues.
Roger
Original comment by roger.parkinson35
on 31 Oct 2011 at 8:57
Attachments:
These look reasonable. I added XmlSchema added 2.0.1 in r1787.
Do you want to add the others yourself?
Original comment by archie.c...@gmail.com
on 31 Oct 2011 at 2:43
I am happy to do that, but I don't have access do I?
Original comment by roger.parkinson35
on 2 Nov 2011 at 2:00
Oops, you're right... sorry. Maybe we'll make you a committer if this all works
:-)
I will work on the others soon.
Original comment by archie.c...@gmail.com
on 2 Nov 2011 at 2:12
Added the other three in r1789.
Original comment by archie.c...@gmail.com
on 2 Nov 2011 at 2:34
I can see Velocity but none of the others.
This is when I use svn to update my local copy of the repo.
Should I see them there yet?
Original comment by roger.parkinson35
on 3 Nov 2011 at 8:24
They're all there...
http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.velocity/velo
city/1.7/ivy.xml
http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.ws.commons/Xm
lSchema/2.0.1/ivy.xml
http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.apache.xml/xml-secur
ity/1.4.6/ivy.xml
http://ivyroundup.googlecode.com/svn/trunk/repo/modules/org.codehaus.jettison/je
ttison/1.3/ivy.xml
What does your repo/modules.xml look like? It should show this:
<modules>
<timestamp>2011-11-02 14:40:14 UTC</timestamp>
<svnRevision>1789</svnRevision>
...
</modules>
Original comment by archie.c...@gmail.com
on 3 Nov 2011 at 2:03
Sorry for the delay getting back.
When I update from svn I get the stuff in the repo, but not in the src.
So my src/modules/org.apache.velocity/velocity dir is empty even after an
update.
So when I build my repo it makes the repo/modules/org.apache.velocity/velocity,
although if I fetch that dir directly the right stuff is there.
Shouldn't there be entries for these in src?
My repo/modules.xml looks like this after an update:
<modules>
<timestamp>2011-11-10 14:26:07 UTC</timestamp>
<svnRevision>1800</svnRevision>
but after a build (build.xml target=repo) it looks like this:
<modules>
<timestamp>2011-11-12 04:10:10 UTC</timestamp>
<svnRevision>1070</svnRevision>
I definitely updated from svn (a couple of extra times on src to make sure).
Are you sure they got committed to src?
Original comment by roger.parkinson35
on 12 Nov 2011 at 5:01
You should see version 1.7 under src/modules/org.apache.velocity/velocity. If
you don't then there's something wrong with your SVN checkout. Try deleting the
velocity directory and checking it out again. If that doesn't work, delete
everything and re-checkout.
You can see what the SVN tree should look like in your web browser, e.g.:
http://ivyroundup.googlecode.com/svn/trunk/src/modules/org.apache.velocity/velocity/
Original comment by archie.c...@gmail.com
on 13 Nov 2011 at 9:49
I checked everything out again and the missing stuff was, indeed, there.
I have the patch files for the remaining libraries attached.
A couple of the patch files have more than one library in them. Let me know if
you need them split up.
This gets everything needed for a web service using:
<dependency org="org.apache.cxf" name="cxf-bundle" rev="2.4.3"
conf="default->default,security"/>
S straight web service works fine, I haven't tried adding security to it yet
but the libraries resolve okay anyway.
Regards Roger
Original comment by roger.parkinson35
on 25 Nov 2011 at 8:59
Attachments:
Thanks!
Everything worked except (a) files contained tab characaters; and (b) your
forgot to put your name in the copyright messages.
I fixed these glitches and committed everything in r1805.
Original comment by archie.c...@gmail.com
on 25 Nov 2011 at 4:58
Original issue reported on code.google.com by
archie.c...@gmail.com
on 8 Apr 2010 at 8:05