)
Can't reproduce it in GEP 2.2. So close it
Distribution of configuration failed when attempting to deploy using
Geronimo 2.0 adapter
---
Key: GERONIMODEVTOOLS-174
URL
Geronimo 2.0.x branch does not build with tests
---
Key: GERONIMO-4527
URL: https://issues.apache.org/jira/browse/GERONIMO-4527
Project: Geronimo
Issue Type: Bug
Security Level: public
be an easily reviewable set of
changes if anyone cared to see what was changed to fix the build.
Geronimo 2.0.x branch does not build with tests
---
Key: GERONIMO-4527
URL: https://issues.apache.org/jira/browse/GERONIMO-4527
/deployment/EjbRefBuilder.java
Sendingpom.xml
Transmitting file data
Committed revision 740608.
Geronimo 2.0.x branch does not build with tests
---
Key: GERONIMO-4527
URL: https://issues.apache.org/jira
to OpenEJB 3.0.1-SNAPSHOT? The
branches/2.0 builds fine without any changes...
Geronimo 2.0.x branch does not build with tests
---
Key: GERONIMO-4527
URL: https://issues.apache.org/jira/browse/GERONIMO-4527
for release - including removing
dependencies on beta versions.
When I moved it to point it at OpenEJB 3.0 (rather than 3.0-beta-1), the build
stopped working.
If you switch away from the beta version, does the build still work for you?
Geronimo 2.0.x branch does not build with tests
as the name of the bug implies the branch
does not build as it. But it only does not build if you locally updated to
openejb 3.0.
Geronimo 2.0.x branch does not build with tests
---
Key: GERONIMO-4527
URL: https
-SNAPSHOT). These changes include the new snapshot version of OpenEJB
rather than the unbuildable 3.0 version.
was:Because of a number of changes that have occurred in dependencies of
Geronimo it will no longer build.
Summary: Geronimo 2.0.x branch does not build after updating OpenEJB
of configuration failed when attempting to deploy using
Geronimo 2.0 adapter
---
Key: GERONIMODEVTOOLS-174
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-174
[
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn updated GERONIMO-3450:
---
Fix Version/s: (was: 2.0.x)
2.0.1
Unable to Run Pluto 1.1 on Geronimo 2.0
Hello, Geronimo-devs.
We, The Japan Apache Geronimo Users Group , are proud to announce that we've
completed all the Geronimo 2.0 documents translation. Now it's on the Geronimo
Wiki.
http://cwiki.apache.org/GMOxDOC20ja/documentation.html
Everything was done on a voluntary basis, so
Outstanding!
Regards,
Alan
On May 28, 2008, at 8:43 AM, 石田 剛 wrote:
Hello, Geronimo-devs.
We, The Japan Apache Geronimo Users Group , are proud to announce
that we've completed all the Geronimo 2.0 documents translation. Now
it's on the Geronimo Wiki.
http://cwiki.apache.org
Excellent ... thank you!
Joe
石田 剛 wrote:
Hello, Geronimo-devs.
We, The Japan Apache Geronimo Users Group , are proud to announce that
we've completed all the Geronimo 2.0 documents translation. Now it's on
the Geronimo Wiki.
http://cwiki.apache.org/GMOxDOC20ja/documentation.html
servers).
In the web console, the connection pools are limited to using the standard
connection pool. Is there another way to specify the connection pool class
and its properties?
Thanks
Xav
--
View this message in context:
http://www.nabble.com/Oracle-10g-RAC---Geronimo-2.0
Hi
I opened a JIRA and attached an initial patch for a new portlet for
displaying information regarding the different ejb containers and the
ejbs deployed in them. The JIRA is
http://issues.apache.org/jira/browse/GERONIMO-3811. Currently to after
changing the properties like pool size etc the
--
View this message in context: http://www.nabble.com/
Geronimo-2.0%3A-
customize-EJB-Container-settings-tp15072400s134p15072400.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
--
View this message in context: http://www.nabble.com/Geronimo
On Jan 31, 2008, at 7:36 AM, Manu George wrote:
Hi,
What does the community think about having a portlet in the admin
console for configuring openejb related stuff as well as displaying
the different containers etc deployed in Geronimo. I think this may
improve the usability of Geronimo. If
[
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh resolved GERONIMO-3450.
-
Resolution: Invalid
See Ramesh's comment.
Unable to Run Pluto 1.1 on Geronimo 2.0
[
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay D. McHugh closed GERONIMO-3450.
---
Unable to Run Pluto 1.1 on Geronimo 2.0
http://www.nabble.com/file/p14623694/jaxws-calculator-ejb.zip
jaxws-calculator-ejb.zip
When trying to deploy the ejb web services (see attached code) to geronimo
2.0, the following exception was thrown:
...
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447
)
2.1
2.0.x
Unable to Run Pluto 1.1 on Geronimo 2.0
---
Key: GERONIMO-3450
URL: https://issues.apache.org/jira/browse/GERONIMO-3450
Project: Geronimo
Issue Type: Bug
Just in case someone is interested in doing Java EE 5 app development using
Eclipse + WTP and looking for some instructions, here is some:
http://cwiki.apache.org/confluence/display/GMOxSBOX/Java+EE+5.0+App+Development+on+Geronimo+simplified+using+Eclipse
Hernan,
Request you to move this page to
You wanted a new location, you got it ;-)
There is a new section on the cwiki for presentations
(http://cwiki.apache.org/geronimo)
Shiva, here is the direct link to your material
http://cwiki.apache.org/geronimo/java-ee-50-app-development-on-geronimo-simplified-using-eclipse.html
I'll be
Wow, that's really quick. Thanks Hernan!
- Shiva
On 9/7/07, Hernan Cunico [EMAIL PROTECTED] wrote:
You wanted a new location, you got it ;-)
There is a new section on the cwiki for presentations (
http://cwiki.apache.org/geronimo)
Shiva, here is the direct link to your material
On 9/7/07, Shiva Kumar H R [EMAIL PROTECTED] wrote:
Just in case someone is interested in doing Java EE 5 app development using
Eclipse + WTP and looking for some instructions, here is some:
I hope the presentation is also under AL 2.0 :o)
Vamsi
On 9/8/07, Jacek Laskowski [EMAIL PROTECTED] wrote:
On 9/7/07, Shiva Kumar H R [EMAIL PROTECTED] wrote:
Just in case someone is interested in doing Java EE 5 app development
using
Eclipse + WTP and looking for some instructions, here
Pluto 1.1 on Geronimo 2.0
---
Key: GERONIMO-3450
URL: https://issues.apache.org/jira/browse/GERONIMO-3450
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues
[
https://issues.apache.org/jira/browse/GERONIMO-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh B updated GERONIMO-3450:
---
Attachment: geronimo.log
The log of error generated
Unable to Run Pluto 1.1 on Geronimo 2.0
on Geronimo 2.0
---
Key: GERONIMO-3450
URL: https://issues.apache.org/jira/browse/GERONIMO-3450
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Fix Version/s: 2.1.x
Assignee: Tim McConnell
Distribution of configuration failed when attempting to deploy using
Geronimo 2.0 adapter
---
Key: GERONIMODEVTOOLS-174
for the help.
Regards,
Ramesh B.
Unable to Run Pluto 1.1 on Geronimo 2.0
---
Key: GERONIMO-3450
URL: https://issues.apache.org/jira/browse/GERONIMO-3450
Project: Geronimo
Issue Type: Bug
Security
Unable to Run Pluto 1.1 on Geronimo 2.0
---
Key: GERONIMO-3450
URL: https://issues.apache.org/jira/browse/GERONIMO-3450
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues
PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I built from
src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so
that it
downloads a
fresh
from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts
from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
: Thursday, August 23, 2007 12:15 PM
Subject: Re: [Fwd: Re: building geronimo-2.0-rc1]
Problem occurs when there is a space in the M2REPO directory, in this case
C:\Documents And Settings\ Work around is to use an M2REPO dir without
any spaces in it. We will still have to investigate the cause
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I
:
I am not exactly building from geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I built from
src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar
:
I am not exactly building from geronimo-2.0-src.zip,
but
from
branches\2.0.0. If that still counts as if I built
from
src
zip... I
have
not run into this problem. I have tried after
removing
jspc-compiler-tomcat6-2.0
not exactly building from
geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I
built from
src
zip... I
have
not run into this problem. I have tried after
removing
jspc
).toURI() instead of
URI.create(uri).
Thanks,
Raymond
- Original Message -
*From:* Vamsavardhana Reddy [EMAIL PROTECTED]
*To:* dev@geronimo.apache.org
*Sent:* Thursday, August 23, 2007 12:15 PM
*Subject:* Re: [Fwd: Re: building geronimo-2.0-rc1]
Problem occurs when
(The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I built from
src
zip... I
have
not run into this problem
geronimo-2.0-src.zip, but
from
branches\2.0.0. If that still counts as if I built from
src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so
that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita Kulshreshtha [EMAIL
On Aug 18, 2007, at 11:59 PM, Rodrigo Rodrigues da Silva wrote:
Donald,
thanks for your help, but it didn't work out. If it were the
problem, wouldn't have worked on windows before, I guess. Well,
about Linux distros I've tested on ubuntu feisty and debian etch.
none worked.
I'm
On 8/9/07, * David Jencks* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http
* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org
with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0
unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have
I'm still not seeing this problem
My setup is -
SLES10 w/ Sun 1.5.0_11 and Geronimo 2.0
WinXP w/ Sun 1.5.0_11 and Geronimo 2.0
Both machines are on the same subnet and do not have IPv6 configured or
enabled on the Ethernet adapters.
From SLES, the following works:
deploy -host
PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo-2.0
modules to a
2.0 server. This is an unacceptable security exposure and as
such we have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan
will create a news item on our web page.
At this point we need to discuss how to move forward
command line will allow a user to deploy modules to a
2.0 server. This is an unacceptable security exposure and as
such we have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan
will create a news item on our web page.
At this point we
to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have
. This
is an unacceptable security exposure and as such we have abandoned the
release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
GERONIMO-3404 was opened for this.
At this point we need to discuss how to move forward with a 2.0
unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have
have not been so lucky. I have tried branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip
from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I
in the
command line deployer where a null user / password on the deployer
command line will allow a user to deploy modules to a 2.0 server. This
is an unacceptable security exposure and as such we have abandoned the
release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue
lucky. I have tried branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
exposure and as such we have abandoned the
release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
GERONIMO-3404 was opened for this.
At this point we need to discuss how to move forward with a 2.0 release.
I
not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads a
fresh.
--vamsi
On 8/9/07, Anita
branches/2.0.0 also. I
have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without
any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts
* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'd recommend trying with the about to be released unless someone
finds a major problem 2.0 release you can find here
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo
://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
http://people.apache.org/%7Ehogstrom/geronimo-2.0-rc1/geronimo-2.0/org/
apache/geronimo/assemblies/geronimo-tomcat6-jee5/2.0/
You won't have this exact problem because the
JaasLoginServiceRemotingServer gbean isn't in the latest version
My belated but very enthusiastic +1.
Joe
Matt Hogstrom wrote:
I have put together the release and its been a long journey to get here.
If you have comments please put them on the corresponding [DISCUSS] thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo
Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.0
Vote will conclude on 0700 ET on Saturday August 11th.
Binaries and source artifacts are at
http://people.apache.org/~hogstrom/geronimo-2.0-rc1
Files are being uploaded as of the time of this writing.
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my
the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0 release.
I think we should delete the tags/2.0.0 entry and replace it with a
text file that notes
today one of the Geronimo committers discovered a bug in the
command line deployer where a null user / password on the deployer
command line will allow a user to deploy modules to a 2.0 server.
This is an unacceptable security exposure and as such we have
abandoned the release of Geronimo 2.0
.
This is an unacceptable security exposure and as such we have
abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0 release.
I think we should
+1 for option 2
abandoned the
release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
GERONIMO-3404 was opened for this.
At this point we need to discuss how to move forward with a 2.0 release.
I think we should delete the tags
On Aug 13, 2007, at 4:59 PM, Matt Hogstrom wrote:
2. Take the tags/2.0.0 to create a branches/2.0.1
This would mean that we need to update branches/2.0 to 2.0.2-
SNAPSHOT
Copy the existing tag over and apply the security fixes. Repsin
and release.
+1 for option 2
Best wishes,
Paul
command line will allow a user to deploy modules to a 2.0 server. This
is an unacceptable security exposure and as such we have abandoned the
release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need
exposure and as such we have
abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0 release.
I think we should delete the tags/2.0.0 entry
and as such we have abandoned the
release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0 release.
I think we should delete the tags/2.0.0 entry and replace
On Aug 13, 2007, at 4:59 PM, Matt Hogstrom wrote:
2. Take the tags/2.0.0 to create a branches/2.0.1
This would mean that we need to update branches/2.0 to 2.0.2-
SNAPSHOT
Copy the existing tag over and apply the security fixes. Repsin
and release.
Personally, I vote for option 2.
.
This is an unacceptable security exposure and as such we have
abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0
release.
I
of the Geronimo committers discovered a bug in
the command line deployer where a null user / password on the
deployer command line will allow a user to deploy modules to a 2.0
server. This is an unacceptable security exposure and as such we
have abandoned the release of Geronimo 2.0.
Donald Woods
line will allow a user to deploy modules to a 2.0 server.
This is an unacceptable security exposure and as such we have
abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need
line deployer where a null user / password on the
deployer command line will allow a user to deploy modules to a 2.0
server. This is an unacceptable security exposure and as such we
have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan
to deploy modules to a 2.0 server.
This is an unacceptable security exposure and as such we have
abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward
to deploy modules to a 2.0
server. This is an unacceptable security exposure and as such we
have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan
will create a news item on our web page.
At this point we need to discuss how to move forward
On Aug 13, 2007, at 9:27 PM, David Jencks wrote:
I think I've fixed GERONIMO-3404 and GERONIMO-3406 in trunk, rev
565599. It might be a good idea for this to get a review before we
port it to branches/2.0 and possibly branches/2.0.x.
I'm looking things over now... May take me a bit...
[EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so
modules to a 2.0
server. This is an unacceptable security exposure and as such we
have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan will
create a news item on our web page.
At this point we need to discuss how to move forward
. This is an unacceptable security exposure and as such we
have abandoned the release of Geronimo 2.0.
Donald Woods is going to open a JIRA for this issue and Hernan
will create a news item on our web page.
At this point we need to discuss how to move forward with a 2.0
release.
I think we
comments please put them on the corresponding [DISCUSS]
thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.0
Vote will conclude on 0700 ET on Saturday August 11th.
Binaries and source artifacts are at http://people.apache.org/
~hogstrom/geronimo-2.0-rc1
a long journey to get
here.
If you have comments please put them on the corresponding [DISCUSS]
thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.0
Vote will conclude on 0700 ET on Saturday August 11th.
Binaries and source artifacts are at http
On Aug 9, 2007, at 7:22 AM, Anita Kulshreshtha wrote:
Is anyone else seeing this in geronimo-welcome.. I am building from
http://people.apache.org/~hogstrom/geronimo-2.0-rc1/geronimo-2.0-
src.zip
I haven't as I haven't built on a Windows system. Perhaps someone
else can chime in?
Forgot my +1 (perhaps implied)
On Aug 8, 2007, at 3:56 AM, Matt Hogstrom wrote:
I have put together the release and its been a long journey to get
here.
If you have comments please put them on the corresponding [DISCUSS]
thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do
+1
Vamsi
On 8/8/07, Matt Hogstrom [EMAIL PROTECTED] wrote:
I have put together the release and its been a long journey to get here.
If you have comments please put them on the corresponding [DISCUSS]
thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo
+1
-Donald
Matt Hogstrom wrote:
I have put together the release and its been a long journey to get here.
If you have comments please put them on the corresponding [DISCUSS] thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.0
Vote will conclude on 0700
PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src
zip... I
have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it
downloads
(perhaps implied)
On Aug 8, 2007, at 3:56 AM, Matt Hogstrom wrote:
I have put together the release and its been a long journey to get
here.
If you have comments please put them on the corresponding [DISCUSS]
thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release
and its been a long journey to get
here.
If you have comments please put them on the corresponding [DISCUSS]
thread.
[ ] +1 Release Geronimo 2.0
[ ] 0 No opinion
[ ] -1 Do not release Geronimo 2.0
Vote will conclude on 0700 ET on Saturday August 11th.
Binaries and source
org.codehaus.mojo.jspc and ant from .m2 repo without any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src zip... I
have
I am not exactly building from geronimo-2.0-src.zip, but from
branches\2.0.0. If that still counts as if I built from src zip... I have
not run into this problem. I have tried after removing
jspc-compiler-tomcat6-2.0-alpha-1.jar from my M2REPO so that it downloads a
fresh.
--vamsi
On 8/9/07
I have not been so lucky. I have tried branches/2.0.0 also. I have
tried deleting org.codehaus.mojo.jspc and ant from .m2 repo without any
success (The trunk builds fine).
Thanks
Anita
--- Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I am not exactly building from geronimo-2.0-src.zip
1 - 100 of 329 matches
Mail list logo
