1133618
> Geronimo 3.0 trunk does not build unless you manually download and install
> geronimo-jaxws_2.2_spec-1.0.jar into your local mave
t build unless you manually download and install
> geronimo-jaxws_2.2_spec-1.0.jar into your local maven repo
> -
>
> Key: GERONIMO-6004
&g
ou manually download and install
> geronimo-jaxws_2.2_spec-1.0.jar into your local maven repo
> -
>
> Key: GERONIMO-6004
>
n a specific dependency to the geronimo-jaxws_2.2_spec-1.0 artifact in
maven.
> Geronimo 3.0 trunk does not build unless you manually download and install
> geronimo-jaxw
ifact in my local maven repository.
> Geronimo 3.0 trunk does not build unless you manually download and install
> geronimo-jaxws_2.2_spec-1.0.jar into your local maven repo
> --
Geronimo 3.0 trunk does not build unless you manually download and install
geronimo-jaxws_2.2_spec-1.0.jar into your local maven repo
-
Key
locution that made this work while back, so its easy to install
plugins you built using maven into the local repo using the
geronimo-plugins.xml catalog maintained by the car-maven-plugin.
> Make it easier for a local maven repo to be a plugin r
r a local maven repo to be a plugin repo
> -
>
> Key: GERONIMO-3335
> URL: https://issues.apache.org/jira/browse/GERONIMO-3335
> Project: Geronimo
> Issue Type: Improvement
can be
installed since there is no geronimo-plugins.xml -
file://~/.m2/repository
Also, what does this feature really buy us? Why not just deploy the
.car that was built and placed in the repo instead?
> Make it easier for a local maven repo to be a plugin r
at
org.apache.geronimo.system.plugin.PluginRepositoryDownloader.getRepositories(PluginRepositoryDownloader.java:98)
> Make it easier for a local maven repo to be a plugin repo
> -
>
> Key: GERONIMO-3335
> URL: https://issues.apache.org/
set up for
other servers and also tested on windows.
Scanning local repos not implemented yet.
> Make it easier for a local maven repo to be a plugin repo
> -
>
> Key: GERONIMO-3335
>
Make it easier for a local maven repo to be a plugin repo
-
Key: GERONIMO-3335
URL: https://issues.apache.org/jira/browse/GERONIMO-3335
Project: Geronimo
Issue Type: Improvement
onimo-packaging-plugin or
car-maven-plugin) since I believe those plugins start a server using
CARs they fetch out of your local Maven repo. (This is assuming
you're trying to build CARs or Geronimo plugins without first building
Geronimo itself, which I think is totally desirable.)
Can we push th
lieve those plugins start a server using
CARs they fetch out of your local Maven repo. (This is assuming
you're trying to build CARs or Geronimo plugins without first building
Geronimo itself, which I think is totally desirable.)
Can we push the Geronimo 1.1 CARs to the Maven 1 repo, and if
pos
Not to pass the buck but we in Geronimo are using Maven I think the way it was intended to be used.
Certainly there are issues that are becoming apparent. Aaron put out a good summary of the
problem that we are experiencing.
I think this is certainly important feedback for the Maven team as w
d mirror capability.
Still, it's extremely unfortunate that your very first build as a
developer is the absolute worst-case scenario. It would be very nice
to have an updated "Maven repo bundle" that a new developer could
download (or check out) and unpack to get all the dependencies
Apologies in advance if this is noisy. I've been using maven for only
a year, so I don't understand all the issues.
Maven will cache artifacts locally and if you have a dependency on a
non-snapshot version of the artifact, it only ever gets downloaded
once. From then on, it assumes that the
On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> > On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> >
> > > And in any case, I believe that much of the problem
> > > is not with maven
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
Perhaps you are misunderstanding my intentions. I am not trying to
blame anybody for the current situation and ask them to do penance.
I'm trying to get them to change what they do for future releases.
What exists now and in the past and who cr
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
>
> > And in any case, I believe that much of the problem
> > is not with maven per se, but with how it is being used.
>
> How exactly?
>
> C
On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
> And in any case, I believe that much of the problem
> is not with maven per se, but with how it is being used.
How exactly?
Cocoon/Geronimo have both hit the same problem. The factor would
On 6/7/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
With respect sir, please direct the Maven ire to the Maven developers
and not the Maven users. We're blaming the messenger by complaining at
Matt for having helped figure out the problem.
I don't really buy that. Just because they have chose
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
And in any case, I believe that much of the problem
is not with maven per se, but with how it is being used.
How exactly?
Cocoon/Geronimo have both hit the same problem. The factor would seem
to be having a lot of components in your build -
On 6/7/06, Joshua Slive <[EMAIL PROTECTED]> wrote:
On 6/6/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Joshua Slive wrote:
>
> > So you not only have your build process tied to apache infrastructure
> > in a non-scalable way
>
> Is this the issue with Maven not handling redirects, or somethin
On 6/6/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Joshua Slive wrote:
> So you not only have your build process tied to apache infrastructure
> in a non-scalable way
Is this the issue with Maven not handling redirects, or something else?
It is the fact that builds of geronimo must downloa
This sounds good as far as it goes. But we still have 5 single points
of failure in our build. I would rather set up a site or zone to host
everything Geronimo needs, point all our builds to that only, and have
it create nightly packages of all the dependencies in the Maven repo
so a first-time
First off, thanks to Matt and the admins for the workaround!
On Tue, Jun 06, 2006 at 11:36:32PM -0400, Matt Hogstrom wrote:
> In general the problem is really people that are getting involved with
> Geronimo for the first time as they start out with an empty repo. The
> developers and others on
Well, to address Joshua's comments the first issue is we know that there is a problem and where it
is. We're talking to the Maven team to ensure that we engineer a solution that fixes the problem
and allows us all to work and still sleep at night.
In general the problem is really people that a
Joshua Slive wrote:
> So you not only have your build process tied to apache infrastructure
> in a non-scalable way
Is this the issue with Maven not handling redirects, or something else?
> but you are essentially doing a DoS attack against the
> infrastructure every time you build. Great.
Is
On 6/6/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
All,
I spent a couple of hours working with the Infra structure team on the build
problems we've been
experiencing. They were really helpful in isolating the problem and effecting
a solution. Joes2
(IRC handle on #asfinfra) was the main con
Yay! Thanks guys!
Matt Hogstrom wrote:
All,
I spent a couple of hours working with the Infra structure team on the
build problems we've been experiencing. They were really helpful in
isolating the problem and effecting a solution. Joes2 (IRC handle on
#asfinfra) was the main contact point
Wow, thank you Matt and Infra!!
On Jun 6, 2006, at 5:14 PM, Matt Hogstrom wrote:
All,
I spent a couple of hours working with the Infra structure team on
the build problems we've been experiencing. They were really
helpful in isolating the problem and effecting a solution. Joes2
(IR
All,
I spent a couple of hours working with the Infra structure team on the build problems we've been
experiencing. They were really helpful in isolating the problem and effecting a solution. Joes2
(IRC handle on #asfinfra) was the main contact point.
The problem is that people.apache.org h
On 6/6/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
There are cheap (< $20/month) hosting plans that allow e.g. 250-1500
GB transfer per month. I'm not sure how the performance is, and I'm
not sure how much transfer we'd actually use, but it might be worth a
try. I'll cover the cost if someone
Matt
Aaron Mulder wrote:
> Is there interest in setting up a Geronimo Maven repo (to avoid load
> and outages affecting the other Maven sites)? Is there someone who
> would take charge of maintaining it (that is, making sure release we
> need from Codehaus, ibiblio, etc. are copi
7;d be interested to hear what the options
are though.
Matt
Aaron Mulder wrote:
Is there interest in setting up a Geronimo Maven repo (to avoid load
and outages affecting the other Maven sites)? Is there someone who
would take charge of maintaining it (that is, making sure release we
need fr
I believe this is key for maven to be successful and reliable for geronimo
builds.
+1
--jason
-Original Message-
From: "Aaron Mulder" <[EMAIL PROTECTED]>
Date: Tue, 6 Jun 2006 10:59:07
To:"Geronimo Dev"
Subject: Geronimo Maven Repo
Is there interest in s
Dain Sundstrom <[EMAIL PROTECTED]>
Date: Tue, 6 Jun 2006 08:50:58
To:dev@geronimo.apache.org
Subject: Re: Geronimo Maven Repo
On Jun 6, 2006, at 7:59 AM, Aaron Mulder wrote:
> Is there interest in setting up a Geronimo Maven repo (to avoid load
> and outages affecting the other Maven
I will help.
--jason
-Original Message-
From: "Aaron Mulder" <[EMAIL PROTECTED]>
Date: Tue, 6 Jun 2006 14:20:02
To:dev@geronimo.apache.org
Subject: Re: Geronimo Maven Repo
On 6/6/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
> Can't we just put it in
Do we have a machine with enough disk space available?
If so, I'll volunteer if it's a recent Linux distro and you can give me
SSH access to it
-Donald
Aaron Mulder wrote:
On 6/6/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
Can't we just put it in our Apache Zone?
Works for me.
On 6/6/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
Can't we just put it in our Apache Zone?
Works for me. Any volunteers to manage it?
Aaron
On Jun 6, 2006, at 7:59 AM, Aaron Mulder wrote:
Is there interest in setting up a Geronimo Maven repo (to avoid load
and outages affecting the other Maven sites)? Is there someone who
would take charge of maintaining it (that is, making sure release we
need from Codehaus, ibiblio, etc. are
Is there interest in setting up a Geronimo Maven repo (to avoid load
and outages affecting the other Maven sites)? Is there someone who
would take charge of maintaining it (that is, making sure release we
need from Codehaus, ibiblio, etc. are copied to the Geronimo repo, and
perhaps creating
we're building and doing continuous builds anyway. Or can we simply
put an HTTP server up and point
to the maven repo used for GBuild anyway?
Matt
Kevan Miller wrote:
> Some of you may have noticed 1.1 build errors last week which were
> caused by the relocation of the Apache maven r
can we simply put an
HTTP server up and point
to the maven repo used for GBuild anyway?
Matt
Kevan Miller wrote:
> Some of you may have noticed 1.1 build errors last week which were
> caused by the relocation of the Apache maven repo from
> 'cvs.apache.org/repository' to '
.
Would it make sense to use the same rsync commands I'm using for my internal repo and have one of
the GBuild machines host this function? We have control of them and it is consistent with the way
we're building and doing continuous builds anyway. Or can we simply put an HTTP server
Kevan Miller <[EMAIL PROTECTED]> wrote:
Some of you may have noticed 1.1 build errors last week which were
caused by the relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'. It's
my understanding from asfinfra that t
build
on a regular (weekly?) basis. It could also be something checked into
Subversion, but I'm afraid this would gather a lot of cruft, so we'd
have to aggressively prune anything in there that was no longer
needed.
I'm pretty iffy on putting a maven repo repro into svn. For on
basis. It could also be something checked into
Subversion, but I'm afraid this would gather a lot of cruft, so we'd
have to aggressively prune anything in there that was no longer
needed.
I'm pretty iffy on putting a maven repo repro into svn. For one, it
becomes incorrect anytime
D]> wrote:
Some of you may have noticed 1.1 build errors last week which were
caused by the relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'. It's
my understanding from asfinfra that the maven repo will be moved to
ome of you may have noticed 1.1 build errors last week which were
caused by the relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'. It's
my understanding from asfinfra that the maven repo will be moved to
yet another locatio
e relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'. It's
my understanding from asfinfra that the maven repo will be moved to
yet another location... And also that asfinfra does not feel that an
apache maven repo will ever
On Wed, May 24, 2006 at 04:05:40AM -0400, Kevan Miller wrote:
> Some of you may have noticed 1.1 build errors last week which were
> caused by the relocation of the Apache maven repo from
> 'cvs.apache.org/repository' to 'people.apache.org/repository'.
I've
Some of you may have noticed 1.1 build errors last week which were
caused by the relocation of the Apache maven repo from
'cvs.apache.org/repository' to 'people.apache.org/repository'. It's
my understanding from asfinfra that the maven repo will be moved to
yet ano
Jacek,
I need the following wars at org.apache.geronimo.geronimo-samples
(or something similar):
geronimo-jsp-examples-tomcat-5.5.15.war
geronimo-servlet-examples-tomcat-5.5.15.war
Thanks
Anita
--- Kevan Miller <[EMAIL PROTECTED]> wrote:
>
> On Apr 11, 2006, at 8:34 AM, Jacek Laskowski wrot
We publish nightly SNAPSHOTS by rsync'n from the continuum install.
I don't know how this factors into the m2 build, but I hope we can
keep the sync from continuum working.
-dain
On Apr 11, 2006, at 5:34 AM, Jacek Laskowski wrote:
Hi,
I'm pretty sure I asked about it before, but can't fi
--- Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On 4/11/06, Kevan Miller <[EMAIL PROTECTED]> wrote:
>
> > FYI --
> http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
I was also under the impression that for ibiblio even you have to
follow these instructions, just like us mortal
On 4/11/06, Kevan Miller <[EMAIL PROTECTED]> wrote:
> FYI -- http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
If I receive it in another email, that won't be very funny ;)
> However, I don't think you want the modules on Ibiblio. Since they're
> snapshots and apt to be changing freq
On Apr 11, 2006, at 8:34 AM, Jacek Laskowski wrote:
Hi,
I'm pretty sure I asked about it before, but can't find the answer.
How can I upload Geronimo jars to Maven1 and Maven2 repositories on
iBiblio. I'd like to use M2-ized version of some already-migrated
modules, but since they're not avail
On 4/11/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
> Jacek,
> Here it is. It was sent to me by you!
> http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
Thanks Anita for the reference, but well, I was asking about the exact
procedure for us, Geronimo committers. I know it inv
Jacek,
Here it is. It was sent to me by you!
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html
Thanks
Anita
--- Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm pretty sure I asked about it before, but can't find the answer.
> How can I upload Geronimo jars to Maven1 an
Hi,
I'm pretty sure I asked about it before, but can't find the answer.
How can I upload Geronimo jars to Maven1 and Maven2 repositories on
iBiblio. I'd like to use M2-ized version of some already-migrated
modules, but since they're not available anywhere, but on my laptop
it's not a viable option
Sachin Patel wrote:
Strange. I have no idea. I just tried on windows, and the scenario
worked. If the zip is in the local repo, it skipped the remote
download. When I deleted the zip from the local repo and reran, it
pulled it down.
- sachin
Thanks for trying it Sachin. It's very
Strange. I have no idea. I just tried on windows, and the scenario
worked. If the zip is in the local repo, it skipped the remote
download. When I deleted the zip from the local repo and reran, it
pulled it down.
- sachin
On Dec 21, 2005, at 10:39 PM, Bill Stoddard wrote:
Sachin P
Sachin Patel (JIRA) wrote:
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-26?page=comments#action_12361088 ]
Sachin Patel commented on GERONIMODEVTOOLS-26:
--
This is incorrect. The current syntax is correct as is. If the zip is not
av
available in the local repo, it will pull it down from cvs.apache.org
Have you tried it? Put the zip in the local maven repo and what what happens.
Bill
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-26?page=all ]
Sachin Patel resolved GERONIMODEVTOOLS-26:
--
Resolution: Invalid
> Eclipse plugin build will always miss geronimo-jetty-j2ee-*.zip in the local
> mave
, it will pull it down from cvs.apache.org
> Eclipse plugin build will always miss geronimo-jetty-j2ee-*.zip in the local
> maven repo
> ---
>
> Key: GERONIMODEVTOOLS-26
>
Eclipse plugin build will always miss geronimo-jetty-j2ee-*.zip in the local
maven repo
---
Key: GERONIMODEVTOOLS-26
URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-26
Project
+1
On Oct 20, 2005, at 1:04 AM, David Jencks wrote:
IIUC the currently recommended-by-maven location for the geronimo
artifacts in a maven repo would be org.apache.geronimo/jars/
rather than geronimo/jars/...
I think we should make this change before 1.0 goes out.
In a related issue
+1
Regards,
Alan
On 10/20/2005 7:23 AM, Matt Hogstrom wrote:
+1 I think any work we can get out of the way incrementally towards M2
is good.
Matt
Jacek Laskowski wrote:
David Jencks wrote:
IIUC the currently recommended-by-maven location for the geronimo
artifacts in a maven repo
+1 I think any work we can get out of the way incrementally towards M2 is good.
Matt
Jacek Laskowski wrote:
David Jencks wrote:
IIUC the currently recommended-by-maven location for the geronimo
artifacts in a maven repo would be org.apache.geronimo/jars/
rather than geronimo/jars
David Jencks wrote:
IIUC the currently recommended-by-maven location for the geronimo
artifacts in a maven repo would be org.apache.geronimo/jars/ rather
than geronimo/jars/...
If Maven2 recommends this approach I'm fine with it. That's a very small
change noone would likely e
On 10/19/05, David Jencks <[EMAIL PROTECTED]> wrote:
> IIUC the currently recommended-by-maven location for the geronimo
> artifacts in a maven repo would be org.apache.geronimo/jars/ rather
> than geronimo/jars/...
>
> I think we should make this change before 1.0 goes
IIUC the currently recommended-by-maven location for the geronimo
artifacts in a maven repo would be org.apache.geronimo/jars/ rather
than geronimo/jars/...
I think we should make this change before 1.0 goes out.
In a related issue, the packaging plugin stores the built
configurations in
On Apr 1, 2005, at 4:59 AM, Hari Kodungallur wrote:
I read through the discussion about the need for a maven repository
containing all the dependency jar files. I totally agree with that
fact. In addition, I have a suggestion.
Most likely users are going to be building from the latest code (tip
I read through the discussion about the need for a maven repository
containing all the dependency jar files. I totally agree with that fact.
In addition, I have a suggestion.
Most likely users are going to be building from the latest code (tip of
the trunk) or a milestone release (tip of a tag/b
On Wed, Mar 30, 2005 at 07:29:58PM -0500, Geir Magnusson Jr. wrote:
>
> On Mar 30, 2005, at 5:09 PM, Dain Sundstrom wrote:
>
> >I don't think we should move our repo just because someone believes
> >there might possibly be a policy against it at Apache.
>
> It's discouraged because it really pu
On Mar 30, 2005, at 7:29 PM, Geir Magnusson Jr. wrote:
The world isn't perfect here. I don't like the "Well, they do it
too!" approach, but we can try to be proactive here, and I'm willing
to try the following argument if the Geronimo PMC supports it :
Because we do distribute 3rd party binarie
On Mar 30, 2005, at 5:09 PM, Dain Sundstrom wrote:
On Mar 30, 2005, at 3:37 AM, Geir Magnusson Jr. wrote:
On Mar 30, 2005, at 5:57 AM, Dirk-Willem van Gulik wrote:
All - For now, we could make a first step by just putting the
geronimo build artifacts on geronimo.apache.org/maven - namely the
spec
Dain Sundstrom wrote:
On Mar 30, 2005, at 3:37 AM, Geir Magnusson Jr. wrote:
On Mar 30, 2005, at 5:57 AM, Dirk-Willem van Gulik wrote:
All - For now, we could make a first step by just putting the geronimo
build artifacts on geronimo.apache.org/maven - namely the spec jars
(for now, more on that
On Mar 30, 2005, at 3:37 AM, Geir Magnusson Jr. wrote:
On Mar 30, 2005, at 5:57 AM, Dirk-Willem van Gulik wrote:
All - For now, we could make a first step by just putting the geronimo
build artifacts on geronimo.apache.org/maven - namely the spec jars
(for now, more on that laster), the geronimo-
On Mar 30, 2005, at 10:44 AM, Jeremy Boynes wrote:
Hiram Chirino wrote:
Maintaining our own repos would also allow us to solve the SNAPSHOT
dependency problem we currently have. We could have a procedure,
that before a release (say the M4 release), we copy the geronimo repo
http://geronimo.apac
Hiram Chirino wrote:
Maintaining our own repos would also allow us to solve the SNAPSHOT
dependency problem we currently have. We could have a procedure, that
before a release (say the M4 release), we copy the geronimo repo
http://geronimo.apache.org/maven to http://geronimo.apache.org/M4/maven
On Mar 30, 2005, at 6:37 AM, Geir Magnusson Jr. wrote:
On Mar 30, 2005, at 5:57 AM, Dirk-Willem van Gulik wrote:
This does not per-see preclde the ASF from allowing non ASF code to be
distributed from ASF environments. However we do try to avoid it as it
dillute our message:. Ideally we want to say
On Mar 30, 2005, at 5:57 AM, Dirk-Willem van Gulik wrote:
This does not per-see preclde the ASF from allowing non ASF code to be
distributed from ASF environments. However we do try to avoid it as it
dillute our message:. Ideally we want to say 'anything you download
from
here is under the ASF lic
On Tue, 29 Mar 2005, Alan D. Cabrera wrote:
> > With the new infrastructure it may be possible to locate this at the
> > ASF in the project's zone. However, as I understand ASF policy they do
> > not allow the standalone distribution of non-ASF code (e.g. a Jetty
> > archive even though it is AL
On Wednesday 30 March 2005 05:20, Alan D. Cabrera wrote:
> Jeremy Boynes wrote:
> > With the new infrastructure it may be possible to locate this at the
> > ASF in the project's zone. However, as I understand ASF policy they do
> > not allow the standalone distribution of non-ASF code (e.g. a Jetty
Dain Sundstrom wrote:
Why not use http://geronimo.apache.org/maven?
As I said:
>>
With the new infrastructure it may be possible to locate this at
the ASF in the project's zone. However, as I understand ASF policy
they do not allow the standalone distribution of non-ASF code (e.g.
a Jetty archive
Jeremy Boynes wrote:
As Alan brought it up, what are the thoughts on a maven repo dedicated
to the artifacts needed to build/distribute Geronimo?
With the new infrastructure it may be possible to locate this at the
ASF in the project's zone. However, as I understand ASF policy they do
310.536.8355, ext. 26
On Mar 29, 2005, at 11:56 AM, Jeremy Boynes wrote:
As Alan brought it up, what are the thoughts on a maven repo dedicated
to the artifacts needed to build/distribute Geronimo?
With the new infrastructure it may be possible to locate this at the
ASF in the project's
As Alan brought it up, what are the thoughts on a maven repo dedicated
to the artifacts needed to build/distribute Geronimo?
With the new infrastructure it may be possible to locate this at the ASF
in the project's zone. However, as I understand ASF policy they do not
allow the stand
Aaron Mulder wrote:
I'm a little confused about the tomcat module -- even though it
isn't included in the normal build (and in fact the tomcat build appears
to fail), there's a geronimo-tomcat-1.0-SNAPSHOT.jar module generated and
uploaded. Well, whatever, it's there, just don't expect it
OpenEJB will depend on new Geronimo modules as a result of the
deployer changes, so I've run a "maven jar:deploy" to upload a full set of
fresh modules to the Maven repo. This was the result of a full build with
itests on Linux / Sun JDK 1.4.2_06, and it includes today
94 matches
Mail list logo
