[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589841#action_12589841
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-256:
--
https://bugs
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R reassigned GERONIMODEVTOOLS-272:
Assignee: Tim McConnell (was: Shiva Kumar H R)
> Descrip
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589838#action_12589838
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-254:
--
For referenc
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R reassigned GERONIMODEVTOOLS-254:
Assignee: Tim McConnell (was: Shiva Kumar H R)
> Spaces
Geronimo classpath container not included by default
Key: GERONIMODEVTOOLS-331
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-331
Project: Geronimo-Devtools
Issue Type: Bug
org.apache.geronimo.v21.feature\feature.xml incorrectly includes
org.apache.geronimo.v11.feature
Key: GERONIMODEVTOOLS-330
URL: https://issues.apache.org/jira/browse/
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589820#action_12589820
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-272:
--
Patch has be
Joe Bohn wrote:
David Jencks wrote:
On Apr 16, 2008, at 7:15 AM, Joe Bohn wrote:
David Jencks wrote:
While the original manifestations of GERONIMO-3705 (build doesn't
work with maven 2.0.8) appeared to only apply to maven > 2.0.7,
Bruce Snyder came up with a problem with identical symptoms
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Kirby reopened GERONIMODEVTOOLS-323:
with this change, updatesite.zip doesn't work.
In many cases, the only error
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMODEVTOOLS-272:
-
Fix Version/s: 2.1.0
Assignee: Shiva Kumar H R (was: T
David Jencks wrote:
On Apr 16, 2008, at 7:15 AM, Joe Bohn wrote:
David Jencks wrote:
While the original manifestations of GERONIMO-3705 (build doesn't
work with maven 2.0.8) appeared to only apply to maven > 2.0.7, Bruce
Snyder came up with a problem with identical symptoms using maven
2.0.
Fixed, I added a macro to automatically list all children pages of "Development and
deployment planning".
These pages are now visible from
http://cwiki.apache.org/GMOxDOC21/documentation.html
Sorry it took this long to update this. The original TOC on the front page was
put there as a guidelin
I think there is a major and unacceptable problem with the indexing
of the current 2.1 docs. Some time ago I implemented a little
feature for app-specific log4j configuration and actually wrote up
some instructions on how to use it. Today I wanted to see what I had
written and discovered
On Apr 16, 2008, at 7:15 AM, Joe Bohn wrote:
David Jencks wrote:
While the original manifestations of GERONIMO-3705 (build doesn't
work with maven 2.0.8) appeared to only apply to maven > 2.0.7,
Bruce Snyder came up with a problem with identical symptoms using
maven 2.0.7. I think if the
Kevan Miller wrote:
On Apr 16, 2008, at 2:36 PM, Hernan Cunico wrote:
Erik B. Craig wrote:
I agree that we definitely need to address IP issues around
documentation/the wiki... but isn't there any way to accomplish this
without adding barriers to users editing content?
Can we do something lik
On Apr 16, 2008, at 2:36 PM, Hernan Cunico wrote:
Erik B. Craig wrote:
I agree that we definitely need to address IP issues around
documentation/the wiki... but isn't there any way to accomplish
this without adding barriers to users editing content?
Can we do something like wikipedia does f
Joe Bohn wrote:
RELEASE_NOTES:
1) I've noticed that we actually have 2 RELEASE_NOTES-2.1.txt files in
our source. They are both identical. One is in our root ...
branches/2.1.1/RELEASE-NOTES-2.1.txt. The other is
branches/2.1.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/REL
RELEASE_NOTES:
1) I've noticed that we actually have 2 RELEASE_NOTES-2.1.txt files in
our source. They are both identical. One is in our root ...
branches/2.1.1/RELEASE-NOTES-2.1.txt. The other is
branches/2.1.1/assemblies/geronimo-boilerplate-minimal/src/main/underlay/RELEASE_NOTES-2.1.tx
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589715#action_12589715
]
Ted Kirby commented on GERONIMODEVTOOLS-272:
Can someone put this tri
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated GERONIMODEVTOOLS-266:
---
Attachment: GERONIMODEVTOOLS-259d.patch
patch to add the test for all value
Erik B. Craig wrote:
I agree that we definitely need to address IP issues around
documentation/the wiki... but isn't there any way to accomplish this
without adding barriers to users editing content?
Can we do something like wikipedia does for editing content where there
is a checkbox or a noti
As one of the non-committers who has been active contributing to the
Geronimo Wiki, I echo the preference for a lightweight process. I prefer
the method whereby you can check a box "Grant license to ASF" as you do
with JIRA contributions. However barring this, the proposed process
looks accepta
Rereading this again, I think I might have misinterpreted a bit. To make
sure I understand it now, a user could contribute a single page by providing
a "patch" in a jira without needing to gain contributor status?
On Wed, Apr 16, 2008 at 2:01 PM, Jason Warner <[EMAIL PROTECTED]> wrote:
> I'd be
I'd be more inclined to do something akin to what Erik suggested. I'm
concerned that the process to gain access to editing the wiki would deter
many of the people that add a page here and there that describes something
they've done. A number of our contributions come from people who are just
maki
I agree that we definitely need to address IP issues around
documentation/the wiki... but isn't there any way to accomplish this without
adding barriers to users editing content?
Can we do something like wikipedia does for editing content where there is a
checkbox or a notice or something saying
"Y
Are we breaking new ground here? I'd suspect that the other projects
that are using the Wiki may have already discussed this and may have a
resolution.
Thanks to Miller, Miller and Miller for their awareness of the legal
ramifications; I missed it and its a good point.
On Apr 16, 2008, a
Hey Kevan,
Thanks for bringing this up. Potential IP issues with our documentation is a
reality and I agree we need a process for controlling contributions.
Some comments inline
Kevan Miller wrote:
All,
To properly protect the IP rights of our Wiki-based documentation, we
need to stop allowin
I agree that this should be as light-weight as possible.
There are a couple of suggestions that I would make to the process:
1) Make sure that people are aware of the fact that they can submit an
ICLA at any time (not just after we have voted).
2) We should standardize on the format of the do
I agree that the current situation is bad. I would like to resolve
it by:
- removing all custom svn:ignore properties
- providing some documentation on setting up your global ignores
- making sure that we don't require any non-standard svn:ignore
settings.
Here's why:
- having to set up sv
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: (was: Geronimo-3957-Trunk.patch)
> Updating svn:ignore lists
> -
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: Geronimo-3957-Trunk.sh
Geronimo-3957-210.sh
Attached the
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: (was: Geronimo-3957-210.patch )
> Updating svn:ignore lists
> --
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: (was: Geronimo-3957-20.patch)
> Updating svn:ignore lists
>
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: (was: Geronimo-3957-Trunk.patch)
> Updating svn:ignore lists
> -
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: (was: Geronimo-3957-21.patch)
> Updating svn:ignore lists
>
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: Geronimo-3957-21.sh
Geronimo-3957-20.sh
G
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: Geronimo-3957-210.patch
Geronimo-3957-21.patch
I'd like to see an example in action before I commit myself but so
far I don't see any problems with this. I assume you have already or
will soon verify this doesn't cause problems with the tck :-)
I wonder if a package name with "osgi" in it somewhere would be more
appropriate?
There ar
On Apr 16, 2008, at 2:47 AM, Jacek Laskowski wrote:
On Wed, Apr 16, 2008 at 9:52 AM, <[EMAIL PROTECTED]> wrote:
Author: djencks
Date: Wed Apr 16 00:52:51 2008
New Revision: 648603
URL: http://svn.apache.org/viewvc?rev=648603&view=rev
Log:
GERONIMO-3705 fix build to work with maven 2.0.9
In the past months, I've been working on making the specs jars from Geronimo
working in an OSGi environment.
All these jars have been published and work great :-)
However, lots of these spec jars define factories (stax, saaj for example)
that use the META-INF/services/ discovery mechanism to find a
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R updated GERONIMODEVTOOLS-223:
-
Fix Version/s: 2.1.0
This might be a duplicate of GERONIMODEVTO
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell closed GERONIMODEVTOOLS-246.
--
Resolution: Duplicate
Closing as a duplicate of
https://issues.apach
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell reopened GERONIMODEVTOOLS-246:
> Classpath Container Extension Point
> -
[
https://issues.apache.org/jira/browse/GERONIMO-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589578#action_12589578
]
rustamabd edited comment on GERONIMO-3864 at 4/16/08 7:33 AM:
[
https://issues.apache.org/jira/browse/GERONIMO-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589578#action_12589578
]
Rustam Abdullaev commented on GERONIMO-3864:
Happens for me as well, on ever
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R resolved GERONIMODEVTOOLS-192.
--
Resolution: Fixed
Assignee: Shiva Kumar H R (was: Tim M
David Jencks wrote:
While the original manifestations of GERONIMO-3705 (build doesn't work
with maven 2.0.8) appeared to only apply to maven > 2.0.7, Bruce Snyder
came up with a problem with identical symptoms using maven 2.0.7. I
think if the fix for this issue also fixes the situation he has
Geronimo Revision: 648672 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20080416/build-0800.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.1/20080416
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R resolved GERONIMODEVTOOLS-327.
--
Resolution: Fixed
Assignee: Shiva Kumar H R (was: Kan O
All,
To properly protect the IP rights of our Wiki-based documentation, we
need to stop allowing unrestricted write access to our Wiki. Wiki
contributors should be required to have an ICLA on file with the ASF.
I also think that we need to hold a PMC vote before granting this
access.
I'l
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R resolved GERONIMODEVTOOLS-189.
--
Resolution: Duplicate
Assignee: Shiva Kumar H R (was: T
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R closed GERONIMODEVTOOLS-190.
Resolution: Fixed
Assignee: Shiva Kumar H R (was: Tim McCon
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589553#action_12589553
]
Vasily Zakharov commented on GERONIMO-3957:
---
And the final discussion:
http://
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589551#action_12589551
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-190:
--
This has bee
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589544#action_12589544
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-312:
--
Redundant co
Hi, all,
I've noticed that in many places in Geronimo repository the files and
subdirectories generated by build scripts are put to svn:ignore
properties of the corresponding directories, so that they do not get
in the way when checking a working copy status and preparing a
patch/commit.
However
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589537#action_12589537
]
Vasily Zakharov commented on GERONIMO-3957:
---
The issue has some discussion his
[
https://issues.apache.org/jira/browse/GERONIMO-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasily Zakharov updated GERONIMO-3957:
--
Attachment: SVNPropPatch.java
I've found no reasonable way to create a transferable
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589520#action_12589520
]
Shiva Kumar H R commented on GERONIMODEVTOOLS-256:
--
Also refer t
On Wed, Apr 16, 2008 at 12:13 PM, Shiva Kumar H R <[EMAIL PROTECTED]> wrote:
> Oh! I shld have mentioned that it is available starting from WTP 2.0.1 (and
> we mention WTP 2.0.2 as the pre-req for GEP 2.0.1).
GEP seems to be the source of information about Eclipse and its
ecosystem so this and ot
On Wed, Apr 16, 2008 at 3:18 PM, Jacek Laskowski <[EMAIL PROTECTED]>
wrote:
> On Wed, Apr 16, 2008 at 9:46 AM, <[EMAIL PROTECTED]> wrote:
> > Author: shivahr
> > Date: Wed Apr 16 00:46:53 2008
> > New Revision: 648588
> >
> > URL: http://svn.apache.org/viewvc?rev=648588&view=rev
> > Log:
> >
On Wed, Apr 16, 2008 at 9:46 AM, <[EMAIL PROTECTED]> wrote:
> Author: shivahr
> Date: Wed Apr 16 00:46:53 2008
> New Revision: 648588
>
> URL: http://svn.apache.org/viewvc?rev=648588&view=rev
> Log:
> GERONIMODEVTOOLS-178 Deadlock while stopping Geronimo server from within
> Eclipse - Now fi
On Wed, Apr 16, 2008 at 9:52 AM, <[EMAIL PROTECTED]> wrote:
> Author: djencks
> Date: Wed Apr 16 00:52:51 2008
> New Revision: 648603
>
> URL: http://svn.apache.org/viewvc?rev=648603&view=rev
> Log:
> GERONIMO-3705 fix build to work with maven 2.0.9
> +if (log.isDebugEnabled
While the original manifestations of GERONIMO-3705 (build doesn't
work with maven 2.0.8) appeared to only apply to maven > 2.0.7, Bruce
Snyder came up with a problem with identical symptoms using maven
2.0.7. I think if the fix for this issue also fixes the situation he
has we should apply
[
https://issues.apache.org/jira/browse/GERONIMO-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-3705:
---
Fix Version/s: 2.2
2.1.x
2.1.1
Bruce Snyder reported
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shiva Kumar H R closed GERONIMODEVTOOLS-178.
Fix Version/s: (was: 2.0.0)
2.1.0
This has
[
https://issues.apache.org/jira/browse/GERONIMO-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3440.
--
Resolution: Fixed
Fix Version/s: 2.2
2.1.x
Fixed in trunk before r
[
https://issues.apache.org/jira/browse/GERONIMO-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589450#action_12589450
]
David Jencks commented on GERONIMO-3705:
Fixed in branches/2.1 (2.1.2-SNAPSHOT)
[
https://issues.apache.org/jira/browse/GERONIMO-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589449#action_12589449
]
David Jencks commented on GERONIMO-3440:
Fixed in 2.1 before the 2.1.1 branch in
69 matches
Mail list logo
