Craig McClanahan craigmcc at apache.org writes:
Someone had asked earlier about how Commons projects accomplished this goal
before Maven. The answer was a convention for using Ant build.xml scripts
that referenced a series of build.properties files containing definitions
for things like what
David Blevins david.blevins at visi.com writes:
Only passively reading the thread, but from some of the comments and
your commit message it looks like you just need JDK 1.3 compiled
versions of those specs.
Yes, that's it.
I'd be happy to apply your pom changes in the geronimo tree and
This is an interesting 'request to developers':
http://www.jpackage.org/jpprequest.php
with some reasons for why putting in the external binaries is a pain
for redistributing.
Hen
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Jan 10, 2007, at 2:39 AM, Joerg Heinicke wrote:
David Blevins david.blevins at visi.com writes:
Only passively reading the thread, but from some of the comments and
your commit message it looks like you just need JDK 1.3 compiled
versions of those specs.
Yes, that's it.
Cool.
I'd
On Jan 8, 2007, at 2:21 PM, Joerg Heinicke wrote:
David Blevins david.blevins at visi.com writes:
If someone needs JDK 1.3 versions of any spec jar, I'd be happy to
help. OpenJPA had a similar request recently (JDK 1.3 version of JTA
1.1) and I made sure to do the final release of that spec
Simon Kitching skitching at apache.org writes:
When using maven, only the first run needs to download the jars ... So, no
need
for internet access at build time.
For ant ... This can be run *once* to download the jars, but is not part of
the
main build task, so there is no need for
On Jan 7, 2007, at 6:28 PM, Phil Steitz wrote:
I see
the geronimo spec jars were added with the comment that they had been
recompiled for JDK 1.3. If that is necessary, its probably better
to first
ask geronimo to produce *different* artifacts that satisfy this, or
at least
to rename
On 1/8/07, Joerg Heinicke [EMAIL PROTECTED] wrote:
Simon Kitching skitching at apache.org writes:
When using maven, only the first run needs to download the jars ... So,
no need
for internet access at build time.
For ant ... This can be run *once* to download the jars, but is not part
of
David Blevins david.blevins at visi.com writes:
If someone needs JDK 1.3 versions of any spec jar, I'd be happy to
help. OpenJPA had a similar request recently (JDK 1.3 version of JTA
1.1) and I made sure to do the final release of that spec with JDK 1.3.
What exactly do you have in mind
Craig McClanahan craigmcc at apache.org writes:
Storing JAR files in your source repository (or pretty much any other
scenario where you check in things that have been generated, instead of
rebuilding them) has the following negative impacts:
* Bypasses the normal mechanisms people use to
On 1/8/07, Joerg Heinicke [EMAIL PROTECTED] wrote:
Craig McClanahan craigmcc at apache.org writes:
Storing JAR files in your source repository (or pretty much any other
scenario where you check in things that have been generated, instead of
rebuilding them) has the following negative
Simon Kitching skitching at apache.org writes:
For a start, if every project were to do this, the impact on the
Apache SVN repository would be huge.
Cocoon (maintenance branch 2.1) has currently 111 jars with about 40 MB in its
repository (+ the one for the environment [2]), we are regularly
On 1/7/07, Joerg Heinicke [EMAIL PROTECTED] wrote:
Simon Kitching skitching at apache.org writes:
For a start, if every project were to do this, the impact on the
Apache SVN repository would be huge.
Cocoon (maintenance branch 2.1) has currently 111 jars with about 40 MB in
its
repository
Martin Cooper martinc at apache.org writes:
In general I don't like the need for internet access on build time.
This is a red herring. One way or another, you're going to have to get the
jars from the network, whether it's getting them from SVN, or having Maven
or Ant retrieve them. And in
--- Martin Cooper [EMAIL PROTECTED] wrote:
[SNIP]
This is a red herring. One way or another, you're
going to have to get the
jars from the network, whether it's getting them
from SVN, or having Maven
or Ant retrieve them. And in all of those three
cases, once you have them on
your local
On Sun, 2007-01-07 at 17:08 +, Joerg Heinicke wrote:
Martin Cooper martinc at apache.org writes:
In general I don't like the need for internet access on build time.
This is a red herring. One way or another, you're going to have to get the
jars from the network, whether it's
On 1/7/07, Joerg Heinicke [EMAIL PROTECTED] wrote:
Martin Cooper martinc at apache.org writes:
In general I don't like the need for internet access on build time.
This is a red herring. One way or another, you're going to have to get
the
jars from the network, whether it's getting them
Hi,
I noticed (due to a recent commit message) that commons-transaction has
jarfiles checked in to svn, eg
http://svn.apache.org/repos/asf/jakarta/commons/proper/transaction/trunk/lib/
What's the general policy on this? Sorry if this has been discussed
before; I don't remember it.
Personally, I
On 1/6/07, Simon Kitching [EMAIL PROTECTED] wrote:
Hi,
I noticed (due to a recent commit message) that commons-transaction has
jarfiles checked in to svn, eg
http://svn.apache.org/repos/asf/jakarta/commons/proper/transaction/trunk/lib/
What's the general policy on this? Sorry if this has
19 matches
Mail list logo
