[
https://issues.apache.org/activemq/browse/AMQCPP-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38022
]
Nathan Mittler commented on AMQCPP-58:
--
I've done a bit of clean up to catch various error conditions and clean
[
https://issues.apache.org/activemq/browse/AMQCPP-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38024
]
Nathan Mittler commented on AMQCPP-59:
--
Albert,
I think the issue was your main module. It wasn't destroying
Hi Nathan,
We recently moved the confluence instance.. Something must have gotten
borked. I'll look into it. BUT... I think we are looking into moving
the space on to ASF managed machines.. not sure how long that will
take so, I'll try to get this fix for you ASAP in the mean time.
On
Great - thanks!
On 1/27/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Hi Nathan,
We recently moved the confluence instance.. Something must have gotten
borked. I'll look into it. BUT... I think we are looking into moving
the space on to ASF managed machines.. not sure how long that will
take
This just enables one module... testsuite, same as...
cd testsuite; mvn
To enable mutiupule modules I can see the need for a profile, but for
a single module I really think the cd x; mvn method is better.
* * *
Is anyone using the itests-environment profile?
--jason
[
https://issues.apache.org/activemq/browse/AMQCPP-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38021
]
Nathan Mittler commented on AMQCPP-56:
--
Albert, I think you were trying out trunk while I was in the middle of
Now.I can see following message:
E:\workspace\openejb\openejb3mvn -e eclipse:eclipse
.
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO]
On 1/27/07, Fei Fei [EMAIL PROTECTED] wrote:
E:\workspace\openejb\openejb3mvn -e eclipse:eclipse
.
[INFO]
[INFO] BUILD SUCCESSFUL
Congratulation! I hope your working with Geronimo won't be that hard
any
I observed that a JIRA will show up in Patch Availble only if it is marked
as improvement and Begin RTC review is clicked.
Vamsi
On 1/25/07, Donald Woods [EMAIL PROTECTED] wrote:
Has anyone noticed that the JIRA Project Summary - Patch Available count
is not correct?
Thanks Jacek. That is a good suggestion. Here is what I have come up
with in thinking about a patch:
The server java code has two directory notions: base, used with
ServerInfo.resolve(), and baseServer, used with
ServerInfo.resolveServer(). Base can be set with the oag.home.dir
system
Test
Key: GERONIMO-2782
URL: https://issues.apache.org/jira/browse/GERONIMO-2782
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Reporter: Alan Cabrera
Assigned To: Alan Cabrera
[
https://issues.apache.org/jira/browse/GERONIMO-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Cabrera closed GERONIMO-2782.
--
Resolution: Fixed
Test
Key: GERONIMO-2782
URL:
Ahh, that's right. I wonder if it would be handy to add that state
to all issues so that new people can submit patches and we would have
a way to know when a patch is ready to be picked up by a committer
and applied.
Regards,
Alan
On Jan 27, 2007, at 6:13 AM, Vamsavardhana Reddy wrote:
I think we talked about this offline. OK. You may remove this if you want.
Cheers
Prasad
On 1/27/07, Jason Dillon [EMAIL PROTECTED] wrote:
This just enables one module... testsuite, same as...
cd testsuite; mvn
To enable mutiupule modules I can see the need for a profile, but for
a
No I haven't verified the @EJB injection on Jetty. I believe it is
only on trunk. I was working on getting my M2 build to work. (unable
to resolve dependency o.a.g.specs.geronimo-ejb_3.0_specs//jar)
When I finally gave on M2 build and work on trunk, I hit the
following problem -
Missing:
[
https://issues.apache.org/jira/browse/GERONIMO-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Kashyap updated GERONIMO-1939:
-
Affects Version/s: 2.0
2.0-M2
1.1.1
I reviewed the binaries that Matt has put for review on the following
vote thread -
http://www.nabble.com/-VOTE--2.0-M2-Milestone-ready-for-review-and-JACC-Specs-tf3126768.html
The @EJB injection does not work for Jetty. However, the undeploy of
EJBs now work fine.
These fixes were first put
My initial suspicion turned out to be correct.
The fix in trunk didn't go into M2. Tim McConnell and I verified this
trunk separately. The jetty hack is there in trunk.
The calculator-stateless sample is here for anybody else that wants to try
OK. Now I have verified the @EJB injection jack for Jetty on TRUNK and
have found it to be working.
Cheers
Prasad
On 1/27/07, Prasad Kashyap [EMAIL PROTECTED] wrote:
No I haven't verified the @EJB injection on Jetty. I believe it is
only on trunk. I was working on getting my M2 build to work.
This has been resolved, at least for now. The 'haus folks setup an
automatic redirect from repository.codehaus.org to ibibilo, but
sometimes for an unknown reason, instead of redirecting to the
mirror, some hits would redirect to /, which could cause the
problem below.
I talked to Ben
I think in order to allow multiple instances to work off of the same
installation effectively we need to have a tiered repository support,
so that each instance could include a shared read-only repository
(the system repository), and then a read-write repository (instance
repository),
I've been looking at this recently interms of being able to run
multiple oag instances out of the same filesystem. This means we
need to identify several different points in the filesystem. This is
not exhaustive but really for discussion since Ted brought it up.
One is the location of
Aighty, I'm gonna nuke it.
--jason
On Jan 27, 2007, at 8:49 AM, Prasad Kashyap wrote:
I think we talked about this offline. OK. You may remove this if
you want.
Cheers
Prasad
On 1/27/07, Jason Dillon [EMAIL PROTECTED] wrote:
This just enables one module... testsuite, same as...
cd
Hey Hiram,
Is the resolution on this that we can just add a new header to his file in
our distro?
On 1/19/07, Hiram Chirino [EMAIL PROTECTED] wrote:
Thanks Oren!
On Jan 18, 2007, at 6:49 PM, Oren Ben-Kiki wrote:
On Thu, 2007-01-18 at 18:09 -0500, Hiram Chirino wrote:
...
Yeah the
Hey guys,
I've apparently lost my privileges to change our wiki. Was just trying to
update the AMQCPP 1.1 release page (
http://www.activemq.org/site/activemq-cpp-11-release.html) and was denied.
Thanks,
Nate
AFAIK support for everything needed to do this is already there, all
you need is another module with an additional repository which might
be located by default in var/repository.
Existing command line properties:
-Dorg.apache.geronimo.home.dir=/path/to/geronimo/home speciifies
where the
On Jan 27, 2007, at 5:38 PM, Jason Dillon wrote:
I think in order to allow multiple instances to work off of the
same installation effectively we need to have a tiered repository
support, so that each instance could include a shared read-only
repository (the system repository), and then a
On Jan 27, 2007, at 8:09 PM, David Jencks wrote:
AFAIK support for everything needed to do this is already there,
all you need is another module with an additional repository which
might be located by default in var/repository.
Existing command line properties:
Ya I was just hinting that we should come up with a standard place to
put the instance data tree, which might mean a slight alteration of
the standard tree too... but I'm not really sure, just wanted to put
it out there.
--jason
On Jan 27, 2007, at 6:11 PM, Matt Hogstrom wrote:
On Jan
On Jan 27, 2007, at 1:01 AM, Matt Hogstrom wrote:
All,
I have made the binaries from Geronimo 2.0-M2 available for review at:
http://people.apache.org/~hogstrom/2.0-M2-rc1
In this directory you will find the various assemblies for your
review as well as one massive tar ball that has the
I am noticing that Known Issues and Limitations section still lists some
(atleast one, G-2745) JIRAs that have been addressed. Known Issues and
Limitations and Specific Issues, Features and Improvements fixed in
Version 2.0-M2 sections need review.
Vamsi
31 matches
Mail list logo
