You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by ks...@apache.org on 2002/08/15 00:51:09 UTC
cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
kschrader 2002/08/14 15:51:09
Modified: . project.xml
Removed: . project-b5.xml
Log:
Upgrading to Maven Beta 5.
Revision Changes Path
1.47 +39 -24 jakarta-turbine-fulcrum/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-fulcrum/project.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- project.xml 14 Aug 2002 14:12:00 -0000 1.46
+++ project.xml 14 Aug 2002 22:51:08 -0000 1.47
@@ -89,12 +89,13 @@
</developers>
<dependencies>
<dependency>
- <id>bsf</id>
- <version>2.2</version>
+ <id>activation</id>
+ <version>1.0.2</version>
+ <url>http://java.sun.com/products/javabeans/glasgow/jaf.html</url>
</dependency>
<dependency>
- <id>commons-codec</id>
- <version>1.0-dev</version>
+ <id>bsf</id>
+ <version>2.2</version>
</dependency>
<dependency>
<id>commons-collections</id>
@@ -102,6 +103,10 @@
<url>http://jakarta.apache.org/commons/collections.html</url>
</dependency>
<dependency>
+ <id>commons-codec</id>
+ <version>1.0-dev</version>
+ </dependency>
+ <dependency>
<id>commons-configuration</id>
<version>1.0-dev</version>
<url>http://jakarta.apache.org/commons/</url>
@@ -120,17 +125,21 @@
<url>http://jakarta.apache.org/commons/</url>
</dependency>
<dependency>
+ <id>commons-logging</id>
+ <version>1.0</version>
+ <url>http://jakarta.apache.org/commons/</url>
+ </dependency>
+ <dependency>
<id>commons-pool</id>
<version>1.0</version>
</dependency>
<dependency>
<id>commons-util</id>
- <version>1.0-rc3-dev</version>
+ <version>SNAPSHOT</version>
</dependency>
<dependency>
<id>cryptix</id>
<version>3.2.0</version>
- <jar>cryptix32.jar</jar>
</dependency>
<dependency>
<id>dom4j</id>
@@ -138,11 +147,6 @@
<url>http://www.dom4j.org/</url>
</dependency>
<dependency>
- <id>jaf</id>
- <version>1.0.2</version>
- <jar>activation-1.0.2.jar</jar>
- </dependency>
- <dependency>
<id>jdbc</id>
<version>2.0</version>
</dependency>
@@ -151,11 +155,15 @@
<version>1.2.1</version>
</dependency>
<dependency>
+ <id>junit</id>
+ <version>3.7</version>
+ </dependency>
+ <dependency>
<id>log4j</id>
- <version>1.2.6</version>
+ <version>1.2.4</version>
</dependency>
<dependency>
- <id>mail</id>
+ <id>javamail</id>
<version>1.2</version>
<url>http://java.sun.com/products/javamail/</url>
</dependency>
@@ -166,16 +174,16 @@
</dependency>
<dependency>
<id>servletapi</id>
- <version>2.3</version>
+ <version>2.2</version>
</dependency>
<dependency>
<id>stratum</id>
- <version>1.0-b3-dev</version>
+ <version>1.0-b2-dev</version>
<url>http://jakarta.apache.org/turbine/stratum/</url>
</dependency>
<dependency>
<id>torque</id>
- <version>3.0-b4-dev-20020730</version>
+ <version>SNAPSHOT</version>
<url>http://jakarta.apache.org/turbine/torque/</url>
</dependency>
<dependency>
@@ -185,7 +193,7 @@
</dependency>
<dependency>
<id>velocity-dvsl</id>
- <version>0.44</version>
+ <version>0.45</version>
<url>http://jakarta.apache.org/velocity/dvsl/</url>
</dependency>
<dependency>
@@ -198,15 +206,16 @@
<version>2.1.0</version>
</dependency>
<dependency>
- <id>xml-xerces</id>
+ <id>xerces</id>
+ <type>required</type>
<version>2.0.2</version>
<jar>xercesImpl-2.0.2.jar</jar>
<url>http://xml.apache.org/xerces2-j/index.html</url>
</dependency>
<dependency>
<id>xml-apis</id>
+ <type>required</type>
<version>2.0.2</version>
- <jar>xmlParserAPIs-2.0.2.jar</jar>
<url>http://xml.apache.org/xerces2-j/index.html</url>
</dependency>
<dependency>
@@ -216,13 +225,19 @@
</dependencies>
<build>
<nagEmailAddress>turbine-dev@jakarta.apache.org</nagEmailAddress>
- <sourceDirectory>src/java</sourceDirectory>
+ <sourceDirectory>target/src</sourceDirectory>
<unitTestSourceDirectory>src/test</unitTestSourceDirectory>
<aspectSourceDirectories/>
- <unitTestPatterns>
- <unitTestPattern>include = **/*Test*.java</unitTestPattern>
- </unitTestPatterns>
- <jarResources/>
+
+ <unitTest>
+ <includes>
+ <include>**/*Test*.java</include>
+ </includes>
+ <excludes>
+ <exclude>**/XmlRpcTest.java</exclude>
+ </excludes>
+ </unitTest>
+
<jars/>
</build>
</project>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Daniel Rall <dl...@finemaltcoding.com>.
It's the most widely used version number interpretation I've come
across. With your internal scheme, there's no way to differentiate
alpha from beta from release candidate.
Henning Schmiedehausen <hp...@intermeta.de> writes:
> Well,
>
> that's one way of version number interpretation...
>
> We internally use the x.y.z as "beta versions", x.y as Release Versions.
> Regards
> Henning
>
>
>
> On Tue, 2002-08-20 at 00:08, Daniel Rall wrote:
> > "Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
> >
> > > turbine-2.2-b2.jar ---> turbine-2.2.2.jar
> > > fulcrum-3.0-b2.jar ---> fulcrum-3.0.2.jar
> > > torque-3.0-b4.jar ---> torque-3.0.4.jar
> > > maven-1.0-beta-5.jar ---> maven-1.0.5.jar
> >
> > 2.2 b2 != 2.2.2
> > etc.
> >
> > The third numeric is a bug fix revision of the 2.2 release. A beta is
> > a pre-release.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Well,
that's one way of version number interpretation...
We internally use the x.y.z as "beta versions", x.y as Release Versions.
Regards
Henning
On Tue, 2002-08-20 at 00:08, Daniel Rall wrote:
> "Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
>
> > turbine-2.2-b2.jar ---> turbine-2.2.2.jar
> > fulcrum-3.0-b2.jar ---> fulcrum-3.0.2.jar
> > torque-3.0-b4.jar ---> torque-3.0.4.jar
> > maven-1.0-beta-5.jar ---> maven-1.0.5.jar
>
> 2.2 b2 != 2.2.2
> etc.
>
> The third numeric is a bug fix revision of the 2.2 release. A beta is
> a pre-release.
> --
>
> Daniel Rall <dl...@finemaltcoding.com>
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
> turbine-2.2-b2.jar ---> turbine-2.2.2.jar
> fulcrum-3.0-b2.jar ---> fulcrum-3.0.2.jar
> torque-3.0-b4.jar ---> torque-3.0.4.jar
> maven-1.0-beta-5.jar ---> maven-1.0.5.jar
2.2 b2 != 2.2.2
etc.
The third numeric is a bug fix revision of the 2.2 release. A beta is
a pre-release.
--
Daniel Rall <dl...@finemaltcoding.com>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Kurt Schrader <ks...@karmalab.org> writes:
>On Thu, 15 Aug 2002, Henning P. Schmiedehausen wrote:
>> Kurt Schrader <ks...@karmalab.org> writes:
>>
>> >What is the point of using the jar as originally named, other than to just
>> >to make things ambiguous like they used to be?
>>
>> To find out which version was pulled from a project into maven?
>The jar is named cryptix-3.2.0.jar, thus the version is 3.2.0.
[...]
>Not as useful as being able to go to the crytix website, find out that
>3.2.0 is the newest version, and just adding it to your project.xml to use
Please do this. Go to http://www.cryptix.org/products/cryptix31/index.html,
get the cryptix32-20001002-r3.2.0.zip archive and tell me the name of
the .jar inside this archive.
You might actually do the things you suggest. Or take a look outside
our little jakarta pond.
If I get a release version with a reasonable naming scheme (no, I
don't consider "activation.jar" and "mail.jar" a reasonable naming
scheme), I will use it. No matter if it fits the "-x.y.z.jar" scheme
or not. cryptix32.jar is "the 3.2.0 release of cryptix". To me, this
is good enough. I don't go for 100% solutions.
BTW neither Turbine, Fulcrum, Torque nor Maven do adhere to the
"-x.y.z.jar" naming scheme. Oh, wait, I know, what we do. We will
simply rename
turbine-2.2-b2.jar ---> turbine-2.2.2.jar
fulcrum-3.0-b2.jar ---> fulcrum-3.0.2.jar
torque-3.0-b4.jar ---> torque-3.0.4.jar
maven-1.0-beta-5.jar ---> maven-1.0.5.jar
when we put them into the repository. It makes naming much easier and
keeping the old names will only help people that already have
downloaded the other jars.
How is this for confusion?
To me, this discussion is over. I won't and don't discuss political
(aka "everything must be named equal") and ideological (aka "everyone
has to use maven") reasons. In our internal repository, we will keep
the vendor-original naming scheme except where it is not useful
(e.g. mail.jar / activation.jar).
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Kurt Schrader <ks...@karmalab.org>.
On Thu, 15 Aug 2002, Henning P. Schmiedehausen wrote:
> Kurt Schrader <ks...@karmalab.org> writes:
>
> >What is the point of using the jar as originally named, other than to just
> >to make things ambiguous like they used to be?
>
> To find out which version was pulled from a project into maven?
The jar is named cryptix-3.2.0.jar, thus the version is 3.2.0.
How is this not more clear than cryptix32.jar?
> The whole maven stuff starts turning from a build tool into an
> ideology. This seems to be a bad turn for me.
We're trying to standardize and correct the errors of the past.
Standardized naming is a _good_ thing.
> To find out that the foo-1.2.jar distributed with a non-maven
> application is the same as the javafoo-1.2.jar from maven or that the
> bar32.jar from that application is the same as the bar-3.2.0.jar from
> maven is very very useful.
Not as useful as being able to go to the crytix website, find out that
3.2.0 is the newest version, and just adding it to your project.xml to use
it immediately. Have to key that information to the name of the jar in
the distribution is a pain.
> Hey, I have a better idea. Let's make MD5 sums over all of our jars and
> just call them maven-used-1219328038a4e5.jar
Come on now. JavaMail 1.2 and 1.3 both come with mail.jar. Do we want
them both to have a <jar> element with mail.jar in it? Or should we
rename them to javamail-1.2.jar and javamail-1.3.jar and run with it?
That's the problem that we're trying to solve. Adding in jars that don't
fit the pattern doesn't help anyone except for those that already have the
jars downloaded and know their original names.
-Kurt
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Kurt Schrader <ks...@karmalab.org> writes:
>What is the point of using the jar as originally named, other than to just
>to make things ambiguous like they used to be?
To find out which version was pulled from a project into maven? Oh
come on, give me a break, this is one of the most ridiciulous
arguments I've ever read.
The whole maven stuff starts turning from a build tool into an
ideology. This seems to be a bad turn for me.
There are and always will be projects that don't use maven. There will
be maven projects that interact with non-maven-projects. To find out
that the foo-1.2.jar distributed with a non-maven application is the
same as the javafoo-1.2.jar from maven or that the bar32.jar from that
application is the same as the bar-3.2.0.jar from maven is very very
useful.
Hey, I have a better idea. Let's make MD5 sums over all of our jars and
just call them maven-used-1219328038a4e5.jar What's in a name?
Really pissed
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Kurt Schrader <ks...@karmalab.org>.
On Thu, 15 Aug 2002, Henning P. Schmiedehausen wrote:
> Kurt Schrader <ks...@karmalab.org> writes:
>
> >> The jar is called cryptix32.jar. This is their release version. The id tag
> >> is "cryptix" and we need the "jar" reference.
>
> >No, we don't. The jar is up in the repo as cryptix-3.2.0.jar
> >I thought that we were trying to enforce a standard of jar naming here.
>
> Because someone renamed it. Jason and I clashed on the maven list about this
> and he specifically said, that he would consider
>
> <dependency>
> <id>cryptix</id>
> <version>3.2.0</version>
> <jar>cryptix32.jar</jar>
> </dependency>
>
> as acceptable because it needs no jar renaming and keeps the versions
> and id's clean.
It doesn't require any jar renaming as is, the jar is just pulled down
from the maven repo and used as cryptix-3.2.0.jar. We renamed many jars
in order to standardize them.
What is the point of using the jar as originally named, other than to just
to make things ambiguous like they used to be?
-Kurt
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
Kurt Schrader <ks...@karmalab.org> writes:
>> The jar is called cryptix32.jar. This is their release version. The id tag
>> is "cryptix" and we need the "jar" reference.
>No, we don't. The jar is up in the repo as cryptix-3.2.0.jar
>I thought that we were trying to enforce a standard of jar naming here.
Because someone renamed it. Jason and I clashed on the maven list about this
and he specifically said, that he would consider
<dependency>
<id>cryptix</id>
<version>3.2.0</version>
<jar>cryptix32.jar</jar>
</dependency>
as acceptable because it needs no jar renaming and keeps the versions
and id's clean.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Kurt Schrader <ks...@karmalab.org>.
On Thu, 15 Aug 2002, Henning P. Schmiedehausen wrote:
> kschrader@apache.org writes:
>
> > + <id>activation</id>
> > + <version>1.0.2</version>
> > + <url>http://java.sun.com/products/javabeans/glasgow/jaf.html</url>
>
> > - <id>jaf</id>
> > - <version>1.0.2</version>
> > - <jar>activation-1.0.2.jar</jar>
> > - </dependency>
>
> There was consent, that we call this jaf and keep the jar reference.
Think that Jason already fixed it.
> > <id>cryptix</id>
> > <version>3.2.0</version>
> > - <jar>cryptix32.jar</jar>
> > </dependency>
>
> The jar is called cryptix32.jar. This is their release version. The id tag
> is "cryptix" and we need the "jar" reference.
No, we don't. The jar is up in the repo as cryptix-3.2.0.jar
I thought that we were trying to enforce a standard of jar naming here.
> > + <dependency>
> > <id>log4j</id>
> > - <version>1.2.6</version>
> > + <version>1.2.4</version>
> > </dependency>
>
> Why this? We have a 1.2.6 release?
Will fix.
> > <dependency>
> > - <id>mail</id>
> > + <id>javamail</id>
> > <version>1.2</version>
> > <url>http://java.sun.com/products/javamail/</url>
> > </dependency>
>
> The jar is called "mail-1.2.jar". If you call it javamail, please keep
> a <jar> reference.
Actually it's called mail.jar, so mail-1.2 is just as arbitrary as
javamail-1.2, except that javamail is more descriptive.
> > @@ -166,16 +174,16 @@
> > </dependency>
> > <dependency>
> > <id>servletapi</id>
> > - <version>2.3</version>
> > + <version>2.2</version>
> > </dependency>
>
> We're already on 2.3
We're not using any of the features of it, why would we create a
dependency on it and shut out those using the older version?
> > <dependency>
> > <id>stratum</id>
> > - <version>1.0-b3-dev</version>
> > + <version>1.0-b2-dev</version>
> > <url>http://jakarta.apache.org/turbine/stratum/</url>
> > </dependency>
>
> We're already on b3.
Will fix.
-Kurt
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 8/15/02 1:21 AM, "Henning P. Schmiedehausen" <hp...@intermeta.de> wrote:
>> <dependency>
>> - <id>mail</id>
>> + <id>javamail</id>
>> <version>1.2</version>
>> <url>http://java.sun.com/products/javamail/</url>
>> </dependency>
>
> The jar is called "mail-1.2.jar". If you call it javamail, please keep
> a <jar> reference.
There is a 1.3 of javamail ...
http://java.sun.com/products/javamail/
-jon
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: cvs commit: jakarta-turbine-fulcrum project.xml project-b5.xml
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
kschrader@apache.org writes:
> + <id>activation</id>
> + <version>1.0.2</version>
> + <url>http://java.sun.com/products/javabeans/glasgow/jaf.html</url>
> - <id>jaf</id>
> - <version>1.0.2</version>
> - <jar>activation-1.0.2.jar</jar>
> - </dependency>
There was consent, that we call this jaf and keep the jar reference.
> <id>cryptix</id>
> <version>3.2.0</version>
> - <jar>cryptix32.jar</jar>
> </dependency>
The jar is called cryptix32.jar. This is their release version. The id tag
is "cryptix" and we need the "jar" reference.
> + <dependency>
> <id>log4j</id>
> - <version>1.2.6</version>
> + <version>1.2.4</version>
> </dependency>
Why this? We have a 1.2.6 release?
> <dependency>
> - <id>mail</id>
> + <id>javamail</id>
> <version>1.2</version>
> <url>http://java.sun.com/products/javamail/</url>
> </dependency>
The jar is called "mail-1.2.jar". If you call it javamail, please keep
a <jar> reference.
> @@ -166,16 +174,16 @@
> </dependency>
> <dependency>
> <id>servletapi</id>
> - <version>2.3</version>
> + <version>2.2</version>
> </dependency>
We're already on 2.3
> <dependency>
> <id>stratum</id>
> - <version>1.0-b3-dev</version>
> + <version>1.0-b2-dev</version>
> <url>http://jakarta.apache.org/turbine/stratum/</url>
> </dependency>
We're already on b3.
-1 on all this. Kurt, you're going backwards. Please fix this up!
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>