[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578160#action_12578160
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-294:
--
Oh! sorry
+1
++Vamsi
On Thu, Mar 13, 2008 at 4:33 AM, David Jencks [EMAIL PROTECTED]
wrote:
Hi,
(dependent on genesis 1.4 take 5 release vote passing).
A user recently reported a bug in the servlet spec jar, see
https://issues.apache.org/jira/browse/GERONIMO-3896
Tomcat has accepted the
[
https://issues.apache.org/jira/browse/GERONIMO-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3898.
--
Resolution: Fixed
branches 2.1 rev 636646, trunk rev 636647 make the gbean actually work.
[
https://issues.apache.org/jira/browse/GERONIMO-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578177#action_12578177
]
syvalta commented on GERONIMO-3898:
---
I would prefer having geronimo-internal classes
Set svn properties on newly added files
---
Key: GERONIMODEVTOOLS-296
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-296
Project: Geronimo-Devtools
Issue Type: Sub-task
Components:
Thanks Jarek. I had totally missed out setting this configuration!! and all
new files I have added in GEP don't have the required svn properties set. I
have created GERONIMODEVTOOLS-296 for this and will fix it up. In fact it's
only now I am realizing that, in the files I have committed !-- $Rev$
+1
to anything that makes life easier :)
++Vamsi
On Thu, Mar 13, 2008 at 5:04 AM, David Jencks [EMAIL PROTECTED]
wrote:
IIUC we have a coding standard of a 4 space indent for all files
(documented at http://cwiki.apache.org/GMOxDEV/coding-
standards.html). This can make working with maven
Geronimo Revision: 636647 built with tests included
See the full build-0300.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/build-0300.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080313
[INFO] BUILD SUCCESSFUL
[INFO
[
https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578208#action_12578208
]
Ralf Baumhof commented on GERONIMO-3907:
I have just upgraded my geronimo 2.1
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R closed GERONIMODEVTOOLS-296.
Resolution: Fixed
Completed: At revision: 636723
Set svn
NPE in org.apache.geronimo.security.SubjectId.hashCode() caused by incorrect
JAVA_HOME or JRE_HOME
--
Key: GERONIMO-3913
URL:
On Mar 11, 2008, at 11:53 AM, Joe Bohn wrote:
I think it's about time we got a 2.1.1 release out. The main
motivation is to deliver a fix for the PortletSecurityException when
using https on the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855
). but there are a lot of
+1
-Donald
David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files
(documented at http://cwiki.apache.org/GMOxDEV/coding-standards.html).
This can make working with maven difficult because its files and xml
output generatiion use 2 space indent for xml and .vm
On Mar 12, 2008, at 7:34 PM, David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files
(documented at http://cwiki.apache.org/GMOxDEV/coding-
standards.html). This can make working with maven difficult because
its files and xml output generatiion use 2 space
+1 Thanks for pulling in the GERONIMO-3896 patch.
-Donald
David Jencks wrote:
Hi,
(dependent on genesis 1.4 take 5 release vote passing).
A user recently reported a bug in the servlet spec jar,
see https://issues.apache.org/jira/browse/GERONIMO-3896
Tomcat has accepted the proposed
+1 to only changing the .xml and .vm indents to 2 spaces.
-Donald
Donald Woods wrote:
+1
-Donald
David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files
(documented at
http://cwiki.apache.org/GMOxDEV/coding-standards.html). This can make
working with maven
Hi Eric,
I'm confused about this new samples branch.
Is it your intention to release these migration samples independently of
the other samples (this seems to contradict your earlier affirmation on
the discussion thread that we should release them concurrently and
mirror the Geronimo
Use of hidden classes
-
Key: GERONIMO-3914
URL: https://issues.apache.org/jira/browse/GERONIMO-3914
Project: Geronimo
Issue Type: Sub-task
Security Level: public (Regular issues)
Components: core
Ooops, I think I forgot to update that when I upgraded :-( Hopefully
this type of problem will go away soon when I finish the dependency
muck for gshell plugins... which will be soon.
--jason
On Mar 13, 2008, at 12:31 AM, Jason Warner wrote:
Donald,
It looks good to me. Thanks!
On
-1. I don't think there is any value in making the indent for xml or
any other files different than the normal indent for all other files.
--jason
On Mar 13, 2008, at 6:34 AM, David Jencks wrote:
IIUC we have a coding standard of a 4 space indent for all files
(documented at
+1
Jarek
On Wed, Mar 12, 2008 at 7:03 PM, David Jencks [EMAIL PROTECTED] wrote:
Hi,
(dependent on genesis 1.4 take 5 release vote passing).
A user recently reported a bug in the servlet spec jar, see
https://issues.apache.org/jira/browse/GERONIMO-3896
Tomcat has accepted the
Joe,
I am trying to back-port the migration samples relevant for the older
branches of the server into the svn repository.
I started by cleaning up the ones intended for the 1.0 version of the server
yesterday, and am working my way up from there, as all of them have not yet
been verified or
+1
Jay
David Jencks wrote:
Hi,
(dependent on genesis 1.4 take 5 release vote passing).
A user recently reported a bug in the servlet spec jar, see
https://issues.apache.org/jira/browse/GERONIMO-3896
Tomcat has accepted the proposed fix in their trunk.
While working to upgrade to
On Mar 13, 2008, at 7:21 AM, Jason Dillon wrote:
-1. I don't think there is any value in making the indent for xml
or any other files different than the normal indent for all other
files.
Let me give a couple of examples where the 4-space indent causes a
lot of pain and will continue
[
https://issues.apache.org/jira/browse/GERONIMO-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578351#action_12578351
]
Jarek Gawor commented on GERONIMO-3833:
---
Viet,
Wouldn't it be better to let the
[
https://issues.apache.org/jira/browse/GERONIMO-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578356#action_12578356
]
David Jencks commented on GERONIMO-3907:
Have you tried entityManager.flush()?
Upgrade Monitoring and Debugview plugins to use Dojo instead of Dojolegacy
--
Key: GERONIMO-3915
URL: https://issues.apache.org/jira/browse/GERONIMO-3915
Project: Geronimo
[
https://issues.apache.org/jira/browse/GERONIMO-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578383#action_12578383
]
Joseph Leong commented on GERONIMO-3856:
Progress:
1) Working on it...
2)
Can we also upgrade to aspectj-1.5.3?
-Donald
Gianny Damour wrote:
Hi,
A problem has been identified with WADI 2.0-M8 used by Geronimo 2.1
causing the failure of clustered applications when a specific node (the
node hosting the singleton partition rebalancing service) is killed (a
normal
[
https://issues.apache.org/jira/browse/GERONIMO-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-3909.
---
Resolution: Fixed
Fix Version/s: 2.2
Add sort priority order to
[
https://issues.apache.org/jira/browse/GERONIMO-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578408#action_12578408
]
Joseph Leong commented on GERONIMO-3856:
Progress:
1) Javascript check added
[
https://issues.apache.org/jira/browse/GERONIMO-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578415#action_12578415
]
David Jencks commented on GERONIMO-3898:
Documented at
Many of the sample wiki entries include *.zip files in addition to
references to the svn repo. These *.zip files include some snapshot of
the source as well as the javadocs, xrefs, ears/wars, and in some cases
even wiki html (I think including the wiki content in a zip is a bad
idea ... it
proxy connection does not capture the successful connection events
--
Key: GERONIMO-3916
URL: https://issues.apache.org/jira/browse/GERONIMO-3916
Project: Geronimo
Issue Type:
The archetype needs to be documented in the wiki for 2.1+ if we intend
to encourage its use. I assume that is still the case (please speak-up
otherwise). BTW, I'm not sure what it would mean to release the
archetype. It produces a jar but I'm not sure what it would be used
for. Anybody
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what happens with
this branch. We don't have the other 1.0 samples (were there any?)
checked in.
- geronimo/samples/branches/2.0
This includes the samples for
response future does not complete if a connection is closed before the response
is received
---
Key: GERONIMO-3917
URL: https://issues.apache.org/jira/browse/GERONIMO-3917
Joe Bohn wrote:
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what happens with
this branch. We don't have the other 1.0 samples (were there any?)
checked in.
- geronimo/samples/branches/2.0
This includes
On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:
The archetype needs to be documented in the wiki for 2.1+ if we
intend to encourage its use. I assume that is still the case
(please speak-up otherwise). BTW, I'm not sure what it would mean
to release the archetype. It produces a jar
David Jencks wrote:
On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:
The archetype needs to be documented in the wiki for 2.1+ if we intend
to encourage its use. I assume that is still the case (please
speak-up otherwise). BTW, I'm not sure what it would mean to release
the archetype. It
On Mar 13, 2008, at 11:41 AM, Joe Bohn wrote:
David Jencks wrote:
On Mar 13, 2008, at 11:17 AM, Joe Bohn wrote:
The archetype needs to be documented in the wiki for 2.1+ if we
intend to encourage its use. I assume that is still the case
(please speak-up otherwise). BTW, I'm not sure
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples concurrent with each Geronimo release. This
is important because the jsp
We have never yet released artifacts for samples apart from those that
were released as part of a server release via plugins in 2.0.x
(jsp-examples, servlet-examples, and ldap-sample-app). Since these
samples weren't included in the server svn they were not released as
part of the 2.1
On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an
effort to release the samples concurrent with each Geronimo
I'd like to see us keep a branches/2.0 and branches/2.1 around, so
people can continue to add and enhance the samples if they wish
-Donald
Joe Bohn wrote:
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what
Upgrade to WADI 2.0-M9
--
Key: GERONIMO-3918
URL: https://issues.apache.org/jira/browse/GERONIMO-3918
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components:
[
https://issues.apache.org/jira/browse/GERONIMO-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-3918.
--
Resolution: Fixed
applied as Rev636841 in branches/2.1
Upgrade to WADI 2.0-M9
[
https://issues.apache.org/jira/browse/GERONIMO-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3918:
---
Affects Version/s: (was: 2.2)
Fix Version/s: (was: 2.2)
Upgrade to WADI
Joe Bohn wrote:
Many of the sample wiki entries include *.zip files in addition to
references to the svn repo. These *.zip files include some snapshot of
the source as well as the javadocs, xrefs, ears/wars, and in some cases
even wiki html (I think including the wiki content in a zip is a
Donald,
I don't understand. How are you building the code? The automatic
builds are always done with a clean repo and we don't see builds
failing with any missing dependency error.
Jarek
On Thu, Mar 13, 2008 at 3:21 PM, [EMAIL PROTECTED] wrote:
Author: dwoods
Date: Thu Mar 13 12:21:46 2008
I'm starting with a clean local repo and only running mvn install from
under the testsuite subdir, as to run a clean BVT based on the
artifacts in the hosted repos
I believe the daily build script always runs the testsuite after the
server builds completes, right? So the local repo is
Joe Bohn wrote:
We have the following branches in samples:
- geronimo/samples/branches/1.0
Newly added for the migration samples. We'll see what happens with
this branch. We don't have the other 1.0 samples (were there any?)
checked in.
There were some samples apps for 1.0 scattered all
On Thu, Mar 13, 2008 at 1:47 PM, Joe Bohn [EMAIL PROTECTED] wrote:
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples
I wasn't sure which thread to put this in, so I'll throw it in here. So
far, it seems that when we've been discussing samples, we're lumping the
sample applications and the migration samples in together. Is this
something we want to do? In my mind, they aren't really the same and
shouldn't
Migration samples should definitively not go into svn because the source
environment, the start point for those apps is intended to be a different
platform, not Geronimo. There would be no point in keeping them into svn and
adding them as a part of the release process.
However there are a
User wouldn't have to build anything if each sample was a plug-in
Other thought, why not create a samples assembly which would create a
zip/tar of the binaries that could be downloaded and extracted by a user
to their location of choice. A similar source and repo zipfile could be
created
On Thu, Mar 13, 2008 at 3:44 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Migration samples should definitively not go into svn because the source
environment, the start point for those apps is intended to be a different
platform, not Geronimo. There would be no point in keeping them into svn
On Thu, Mar 13, 2008 at 2:44 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Migration samples should definitively not go into svn because the source
environment, the start point for those apps is intended to be a different
platform, not Geronimo. There would be no point in keeping them into svn
Ok, but still, this is weird. geronimo-deploy-jsr88 already gets
geronimo-common through geronimo-system module.
Also, just running testsuites (testsuites checked out from svn) and
relying on other components to be pulled in (from remote repos) seems
bad. There is a great chance that the
Well, from the wiki - Geronimo documentation, there are 3main sets of samples,
well actually 3 now.
1- Migration samples
2- Sample applicaitons
3- Tutorials
1- Migration samples. These should not be in svn unless we plan to maintain and
test sample applications that are intended for JBoss,
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Well, from the wiki - Geronimo documentation, there are 3main sets of
samples, well actually 3 now.
1- Migration samples
2- Sample applicaitons
3- Tutorials
1- Migration samples. These should not be in svn unless we
Donald Woods wrote:
User wouldn't have to build anything if each sample was a plug-in
That would be true if the value in a sample just in running it.
However, I think most users want to dig into the source, make minor
changes and tweak it as a way to jump start their own development.
Erik B. Craig wrote:
On Thu, Mar 13, 2008 at 2:44 PM, Hernan Cunico [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Migration samples should definitively not go into svn because the
source environment, the start point for those apps is intended to be
a different platform, not
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Well, from the wiki - Geronimo documentation, there are 3main sets of
samples, well actually 3 now.
1- Migration samples
2- Sample
[
https://issues.apache.org/jira/browse/GERONIMO-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3916:
--
Attachment: GERONIMO-3916.patch
A suggested fix...
proxy connection does not capture the
Joe Bohn wrote:
Donald Woods wrote:
User wouldn't have to build anything if each sample was a plug-in
That would be true if the value in a sample just in running it. However,
I think most users want to dig into the source, make minor changes and
tweak it as a way to jump start their
Geronimo Revision: 636812 built with tests included
See the full build-1400.log file at
http://geronimo.apache.org/maven/server/binaries/2.1/20080313/build-1400.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/2.1/20080313
[INFO] BUILD SUCCESSFUL
[INFO
Erik B. Craig wrote:
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Well, from the wiki - Geronimo documentation, there are
On Thu, Mar 13, 2008 at 3:32 PM, Hernan Cunico [EMAIL PROTECTED] wrote:
Erik B. Craig wrote:
On Thu, Mar 13, 2008 at 3:08 PM, Jason Warner [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Thu, Mar 13, 2008 at 4:01 PM, Hernan Cunico [EMAIL PROTECTED]
mailto:[EMAIL
Ok, so here is the list of things that I think were mentioned for
inclusion in a 2.1.1 release (those that were not already complete when
this discussion began).
Am I missing anything from the required list or are there items that
should move up from the Optional list (or down from required)?
Geronimo Revision: 636841 built with tests included
See the full build-1500.log file at
http://geronimo.apache.org/maven/server/binaries/trunk/20080313/build-1500.log
Download the binaries from
http://geronimo.apache.org/maven/server/binaries/trunk/20080313
[INFO] BUILD SUCCESSFUL
[INFO
Plus this change shouldn't affect any of the information geronimo
uses when installing plugins etc. Please show the error you get.
thanks
david jencks
On Mar 13, 2008, at 12:54 PM, Jarek Gawor wrote:
Ok, but still, this is weird. geronimo-deploy-jsr88 already gets
geronimo-common through
On Mar 13, 2008, at 2:08 PM, Joe Bohn wrote:
Ok, so here is the list of things that I think were mentioned for
inclusion in a 2.1.1 release (those that were not already complete
when this discussion began).
Am I missing anything from the required list or are there items
that should move
I would like add to the *Required* having a little bit more complete v2.1
documentation.
There are still a lot of topics to cover (from scratch) and to verify carried
over content from previous releases.
Cheers!
Hernan
Joe Bohn wrote:
Ok, so here is the list of things that I think were
As I noted in a previous thread the current NOTICE files generated by
the apache-jar-resource-bundle 1.3 are not consistent with apache
policy. After some discussion on legal-discuss I've come up with a
bundle that no one seems to be able to find anything seriously wrong
with: we're
[exec] [INFO] [INFO]
[exec] [INFO] [INFO] Building Geronimo TestSuite :: CORBA
TestSuite :: Marshal EAR
[exec] [INFO] [INFO]task-segment: [install]
[exec] [INFO] [INFO]
[
https://issues.apache.org/jira/browse/GERONIMO-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated GERONIMO-3917:
--
Attachment: GERONIMO-3917.patch
I am attaching one suggested fix. The gist of the idea is,
-0
I find 2 space indenting difficult to read. I'm sure that I'm
misunderstanding something so take my reply with a grain of salt.
On Mar 13, 2008, at 8:28 AM, David Jencks wrote:
On Mar 13, 2008, at 7:21 AM, Jason Dillon wrote:
-1. I don't think there is any value in making the indent
David,
I deployed a new snapshot, can you give that a try and make sure it's all
OK?
- I can't get a blank line in between the project name and the notice
Fixed
- I can't configure projectName in a suitable place so it shows up in
the generated NOTICE.
In the configuration for the
David Jencks wrote:
On Mar 13, 2008, at 11:47 AM, Joe Bohn wrote:
Joe Bohn wrote:
David Jencks wrote:
On Mar 12, 2008, at 7:12 AM, Joe Bohn wrote:
Donald Woods wrote:
Joe Bohn wrote:
2) When to release the samples? I think we should make an effort
to release the samples concurrent
GEP 2.1.0 JAXB Refactoring Tasklist
---
Key: GERONIMODEVTOOLS-297
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-297
Project: Geronimo-Devtools
Issue Type: Bug
Components:
Plugin: org.apache.geronimo.runtime.common
--
Key: GERONIMODEVTOOLS-298
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-298
Project: Geronimo-Devtools
Issue Type: Sub-task
Plugin: org.apache.geronimo.runtime.v11
---
Key: GERONIMODEVTOOLS-299
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-299
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter:
Plugin: org.apache.geronimo.runtime.v21
---
Key: GERONIMODEVTOOLS-301
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-301
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter:
Plugin: org.apache.geronimo.runtime.v20
---
Key: GERONIMODEVTOOLS-300
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-300
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter:
Plugin: org.apache.geronimo.st.core
---
Key: GERONIMODEVTOOLS-302
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-302
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim
Plugin: org.apache.geronimo.st.v20.core
---
Key: GERONIMODEVTOOLS-304
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-304
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter:
Plugin: org.apache.geronimo.st.v21.core
---
Key: GERONIMODEVTOOLS-305
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-305
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter:
Plugin: org.apache.geronimo.st.v11.core
---
Key: GERONIMODEVTOOLS-303
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-303
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
At Axis2, we are trying to push out a 1.4 Release soon. Planning an RC1 this
weekend/monday.
So questions, What's the plan to upgrade to JAXWS 2.1? I believe the cxf folks
are already at JAXWS 2.1.
Could we please upgrade both (if not
Plugin: org.apache.geronimo.st.ui
-
Key: GERONIMODEVTOOLS-306
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-306
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim
Plugin: org.apache.geronimo.st.v20.ui
-
Key: GERONIMODEVTOOLS-308
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-308
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim
Plugin: org.apache.geronimo.st.v11.ui
-
Key: GERONIMODEVTOOLS-307
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-307
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim
Plugin: org.apache.geronimo.st.v21.ui
-
Key: GERONIMODEVTOOLS-309
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-309
Project: Geronimo-Devtools
Issue Type: Sub-task
Reporter: Tim
Plugin: org.apache.geronimo.deployment.v11.jaxbmodel
Key: GERONIMODEVTOOLS-310
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-310
Project: Geronimo-Devtools
Issue Type:
Plugin: org.apache.geronimo.deployment.v21.jaxbmodel
Key: GERONIMODEVTOOLS-311
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-311
Project: Geronimo-Devtools
Issue Type:
Seems like this would be causing the dependency problem you saw:
'org.apache.geronimo.framework:geronimo-system:pom:2.1.1-SNAPSHOT:runtime'
is invalid. It will be ignored for artifact resolution. Reason: Failed
to validate POM for project
Jarek
On Thu, Mar 13, 2008 at 8:03 PM, Donald
Reimplement fixGeronimo*Schema() functions inside GeronimRuntime classes using
JAXB
---
Key: GERONIMODEVTOOLS-312
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12578584#action_12578584
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-295:
--
Some good
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R closed GERONIMODEVTOOLS-294.
Delete existing EMF plug-ins
1 - 100 of 114 matches
Mail list logo
