You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Jörg Schaible <Jo...@Elsag-Solutions.com> on 2003/12/08 18:09:44 UTC
[Jelly-Tags SOAP] patched project.xml to run demo
Hi,
it took some time, but lastly I got the demo of jelly-tags-soap running. The example suffers from the missing jars of Sun on the ibiblio server and was not updated after jelly.jar was separated. I've added a diff below, but the basic question is, what to do with the jars of Sun? I've setup an own repository on my server with the jars from the new j2ee 1.4, but I have no real idea for a general solution (therefore I did not open a JIRA issue). What have other projects done using the Maven dependencies and relying on some jars of Sun?
Regards,
Jörg
$ cvs diff -u project.xml
Index: project.xml
===================================================================
RCS file: /home/cvspublic/jakarta-commons/jelly/jelly-tags/soap/project.xml,v
retrieving revision 1.5
diff -u -r1.5 project.xml
--- project.xml 27 Jan 2003 05:24:15 -0000 1.5
+++ project.xml 8 Dec 2003 17:03:24 -0000
@@ -30,18 +30,42 @@
</dependency>
<dependency>
+ <groupId>commons-jelly</groupId>
+ <artifactId>commons-jelly-tags-log</artifactId>
+ <version>SNAPSHOT</version>
+ </dependency>
+
+ <dependency>
<id>axis</id>
<version>1.0</version>
</dependency>
<dependency>
- <id>jaxrpc</id>
- <version>1.0</version>
+ <groupId>jaxrpc</groupId>
+ <artifactId>jaxrpc-api</artifactId>
+ <version>1.1</version>
+ </dependency>
+ <dependency>
+ <groupId>jaxrpc</groupId>
+ <artifactId>jaxrpc-impl</artifactId>
+ <version>1.1</version>
</dependency>
+ <dependency>
+ <groupId>jaxrpc</groupId>
+ <artifactId>jax-qname</artifactId>
+ <version>1.1</version>
+ </dependency>
+
<dependency>
- <id>saaj</id>
- <version>1.1</version>
+ <groupId>saaj</groupId>
+ <artifactId>saaj-api</artifactId>
+ <version>1.2</version>
+ </dependency>
+ <dependency>
+ <groupId>saaj</groupId>
+ <artifactId>saaj-impl</artifactId>
+ <version>1.2</version>
</dependency>
<!-- START for running demos -->
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Jelly-Tags SOAP] patched project.xml to run demo
Posted by Paul Libbrecht <pa...@activemath.org>.
Joerg,
Are you sure it's the only ones needed. Last week I managed to compile
this taglib and it's quite a hell to get along (outside of j2ee).
Your project.xml update is badly missing URLs on how to get these
dependencies.
In particular, I know no official place to get that evil jax-qname
(which is just one class) nor did I find the version in the
web-services-packs I downloaded...
For all of them, I've put
http://java.sun.com/webservices/webservicespack.html as URL but I am
really no happy with it (it's also a 30 Mb download and an "interactive
installer"... not really the breeze of a maven download).
It would be good to find better URLs.
It would be great to get rid of qname (but I really don't how yet).
Maybe the trick would be to haunt people at Sun so that they do their
things in a more accessible fashion, and even require an open-repository
and maven-controlled project.
Paul
Jörg Schaible wrote:
> Hi,
>
> it took some time, but lastly I got the demo of jelly-tags-soap running. The example suffers from the missing jars of Sun on the ibiblio server and was not updated after jelly.jar was separated. I've added a diff below, but the basic question is, what to do with the jars of Sun? I've setup an own repository on my server with the jars from the new j2ee 1.4, but I have no real idea for a general solution (therefore I did not open a JIRA issue). What have other projects done using the Maven dependencies and relying on some jars of Sun?
>
> Regards,
> Jörg
>
> $ cvs diff -u project.xml
> Index: project.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-commons/jelly/jelly-tags/soap/project.xml,v
> retrieving revision 1.5
> diff -u -r1.5 project.xml
> --- project.xml 27 Jan 2003 05:24:15 -0000 1.5
> +++ project.xml 8 Dec 2003 17:03:24 -0000
> @@ -30,18 +30,42 @@
> </dependency>
>
> <dependency>
> + <groupId>commons-jelly</groupId>
> + <artifactId>commons-jelly-tags-log</artifactId>
> + <version>SNAPSHOT</version>
> + </dependency>
> +
> + <dependency>
> <id>axis</id>
> <version>1.0</version>
> </dependency>
>
> <dependency>
> - <id>jaxrpc</id>
> - <version>1.0</version>
> + <groupId>jaxrpc</groupId>
> + <artifactId>jaxrpc-api</artifactId>
> + <version>1.1</version>
> + </dependency>
> + <dependency>
> + <groupId>jaxrpc</groupId>
> + <artifactId>jaxrpc-impl</artifactId>
> + <version>1.1</version>
> </dependency>
> + <dependency>
> + <groupId>jaxrpc</groupId>
> + <artifactId>jax-qname</artifactId>
> + <version>1.1</version>
> + </dependency>
> +
>
> <dependency>
> - <id>saaj</id>
> - <version>1.1</version>
> + <groupId>saaj</groupId>
> + <artifactId>saaj-api</artifactId>
> + <version>1.2</version>
> + </dependency>
> + <dependency>
> + <groupId>saaj</groupId>
> + <artifactId>saaj-impl</artifactId>
> + <version>1.2</version>
> </dependency>
>
> <!-- START for running demos -->
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Jelly-Tags SOAP] patched project.xml to run demo
Posted by Paul Libbrecht <pa...@activemath.org>.
Cool, way cool,
The issues start with:
- you want to distribute this wonderful directory every developer should
have around (I'm sure you dare send this to me but not put this on the
website).
- you want to debug in more details with respect to version (that can
becomes really tricky with Sun's jar-naming)
- you want to consider distributing your program including these jars...
which means you should document the licenses of the things you distribute.
At that last point, I got once caught: servlet-2.1 license said that I
could not redistribute it with my product if it was later than the last
servler-2.1 release plus 180 days...
Paul
PS: the packs of Sun are very very similar to such heaps! (webservices
sounds to make efforts but it's unfinished)
Martin van den Bemt wrote:
> I have a big download directory where al the sun stuff resides. When a
> dependency is not on ibiblio, most of the time it is concerning jars
> from sun, so I just add the group directory in my local repository (eg
> /opt/mavenjars/jaxrpc and rename the jar to have the "mavenized" version
> number in there (the artifectId).
> That's it :)
> At first it takes some time to get everything into your local
> repository, but before you know it, you just need to update new
> versions..
>
> Mvgr,
> Martin
>
> On Mon, 2003-12-08 at 18:09, Jörg Schaible wrote:
>
>>Hi,
>>
>>it took some time, but lastly I got the demo of jelly-tags-soap running. The example suffers from the missing jars of Sun on the ibiblio server and was not updated after jelly.jar was separated. I've added a diff below, but the basic question is, what to do with the jars of Sun? I've setup an own repository on my server with the jars from the new j2ee 1.4, but I have no real idea for a general solution (therefore I did not open a JIRA issue). What have other projects done using the Maven dependencies and relying on some jars of Sun?
>>
>>Regards,
>>Jörg
>>
>>$ cvs diff -u project.xml
>>Index: project.xml
>>===================================================================
>>RCS file: /home/cvspublic/jakarta-commons/jelly/jelly-tags/soap/project.xml,v
>>retrieving revision 1.5
>>diff -u -r1.5 project.xml
>>--- project.xml 27 Jan 2003 05:24:15 -0000 1.5
>>+++ project.xml 8 Dec 2003 17:03:24 -0000
>>@@ -30,18 +30,42 @@
>> </dependency>
>>
>> <dependency>
>>+ <groupId>commons-jelly</groupId>
>>+ <artifactId>commons-jelly-tags-log</artifactId>
>>+ <version>SNAPSHOT</version>
>>+ </dependency>
>>+
>>+ <dependency>
>> <id>axis</id>
>> <version>1.0</version>
>> </dependency>
>>
>> <dependency>
>>- <id>jaxrpc</id>
>>- <version>1.0</version>
>>+ <groupId>jaxrpc</groupId>
>>+ <artifactId>jaxrpc-api</artifactId>
>>+ <version>1.1</version>
>>+ </dependency>
>>+ <dependency>
>>+ <groupId>jaxrpc</groupId>
>>+ <artifactId>jaxrpc-impl</artifactId>
>>+ <version>1.1</version>
>> </dependency>
>>+ <dependency>
>>+ <groupId>jaxrpc</groupId>
>>+ <artifactId>jax-qname</artifactId>
>>+ <version>1.1</version>
>>+ </dependency>
>>+
>>
>> <dependency>
>>- <id>saaj</id>
>>- <version>1.1</version>
>>+ <groupId>saaj</groupId>
>>+ <artifactId>saaj-api</artifactId>
>>+ <version>1.2</version>
>>+ </dependency>
>>+ <dependency>
>>+ <groupId>saaj</groupId>
>>+ <artifactId>saaj-impl</artifactId>
>>+ <version>1.2</version>
>> </dependency>
>>
>> <!-- START for running demos -->
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [Jelly-Tags SOAP] patched project.xml to run demo
Posted by Martin van den Bemt <ml...@mvdb.net>.
Hi,
I have a big download directory where al the sun stuff resides. When a
dependency is not on ibiblio, most of the time it is concerning jars
from sun, so I just add the group directory in my local repository (eg
/opt/mavenjars/jaxrpc and rename the jar to have the "mavenized" version
number in there (the artifectId).
That's it :)
At first it takes some time to get everything into your local
repository, but before you know it, you just need to update new
versions..
Mvgr,
Martin
On Mon, 2003-12-08 at 18:09, Jörg Schaible wrote:
> Hi,
>
> it took some time, but lastly I got the demo of jelly-tags-soap running. The example suffers from the missing jars of Sun on the ibiblio server and was not updated after jelly.jar was separated. I've added a diff below, but the basic question is, what to do with the jars of Sun? I've setup an own repository on my server with the jars from the new j2ee 1.4, but I have no real idea for a general solution (therefore I did not open a JIRA issue). What have other projects done using the Maven dependencies and relying on some jars of Sun?
>
> Regards,
> Jörg
>
> $ cvs diff -u project.xml
> Index: project.xml
> ===================================================================
> RCS file: /home/cvspublic/jakarta-commons/jelly/jelly-tags/soap/project.xml,v
> retrieving revision 1.5
> diff -u -r1.5 project.xml
> --- project.xml 27 Jan 2003 05:24:15 -0000 1.5
> +++ project.xml 8 Dec 2003 17:03:24 -0000
> @@ -30,18 +30,42 @@
> </dependency>
>
> <dependency>
> + <groupId>commons-jelly</groupId>
> + <artifactId>commons-jelly-tags-log</artifactId>
> + <version>SNAPSHOT</version>
> + </dependency>
> +
> + <dependency>
> <id>axis</id>
> <version>1.0</version>
> </dependency>
>
> <dependency>
> - <id>jaxrpc</id>
> - <version>1.0</version>
> + <groupId>jaxrpc</groupId>
> + <artifactId>jaxrpc-api</artifactId>
> + <version>1.1</version>
> + </dependency>
> + <dependency>
> + <groupId>jaxrpc</groupId>
> + <artifactId>jaxrpc-impl</artifactId>
> + <version>1.1</version>
> </dependency>
> + <dependency>
> + <groupId>jaxrpc</groupId>
> + <artifactId>jax-qname</artifactId>
> + <version>1.1</version>
> + </dependency>
> +
>
> <dependency>
> - <id>saaj</id>
> - <version>1.1</version>
> + <groupId>saaj</groupId>
> + <artifactId>saaj-api</artifactId>
> + <version>1.2</version>
> + </dependency>
> + <dependency>
> + <groupId>saaj</groupId>
> + <artifactId>saaj-impl</artifactId>
> + <version>1.2</version>
> </dependency>
>
> <!-- START for running demos -->
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
--
Martin van den Bemt <ml...@mvdb.net>
mvdb.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org