[
https://issues.apache.org/jira/browse/GERONIMO-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610459#action_12610459
]
Sainath Chowdary commented on GERONIMO-4150:
Thank you Jay for your feedback
[
https://issues.apache.org/jira/browse/GERONIMO-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George reassigned GERONIMO-4178:
---
Assignee: (was: Manu T George)
Please verify and commit if appropriate
> Misl
[
https://issues.apache.org/jira/browse/GERONIMO-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn resolved GERONIMO-4182.
Resolution: Fixed
Fix Version/s: 2.2
2.1.x
2.1.2
>
Joe Bohn wrote:
David Jencks wrote:
Can you check if the plugin installer gbean is using the artifact
resolver that knows about the aliases you installed? If it's directly
accessing the repository we need to change it to use the appropriate
artifact resolver (after figuring out which artifact
Artifact aliases are not honored when deploying a plugin that has a dependency
on another plugin with an alias
--
Key: GERONIMO-4182
URL: https://issues.ap
[
https://issues.apache.org/jira/browse/GERONIMO-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bohn resolved GERONIMO-2814.
Resolution: Fixed
Fix Version/s: (was: Wish List)
2.2
Lin Sun wrote:
I agree this should work for certain scenarios when the server doesn't
provide the needed dependency. I suggested this because we had
jasper-deployer specified as scope=provided while we don't have jasper
specified as scope=provided in this sample in 2.1 branch.
Right ... I not
I agree this should work for certain scenarios when the server doesn't
provide the needed dependency. I suggested this because we had
jasper-deployer specified as scope=provided while we don't have jasper
specified as scope=provided in this sample in 2.1 branch.
Lin
On Thu, Jul 3, 2008 at 12:16
Lin Sun wrote:
Hi Joe,
You could try adding
provided
to the org.apache.geronimo.configs/jasper/{version}/car dependency in
the pom.xml. I 've seen a similar error like this before and by
adding the scope fixed it.
Thanks Lin. That does indeed solve (more correctly avoid) the p
Yep yep. It's on my to do list.
On Thu, Jul 3, 2008 at 11:06 AM, Jason Dillon <[EMAIL PROTECTED]> wrote:
> You should make sure that the TCK is happy with this new version ;-)
> --jason
>
>
> On Jul 2, 2008, at 9:35 PM, Jason Warner wrote:
>
> created https://issues.apache.org/jira/browse/GERONI
I'm working on having the debug-views fully converted for dojo 1.1.1
purposes.
-Joseph Leong
On Thu, Jul 3, 2008 at 11:04 AM, Hernan Cunico <[EMAIL PROTECTED]> wrote:
> Donald Woods wrote:
>
>> Shouldn't we put roadmap/release/project management type info in the
>> GMOxPMT space instead? The DE
You should make sure that the TCK is happy with this new version ;-)
--jason
On Jul 2, 2008, at 9:35 PM, Jason Warner wrote:
created https://issues.apache.org/jira/browse/GERONIMO-4181 to track
this issue
On Tue, Jul 1, 2008 at 3:48 PM, Joe Bohn <[EMAIL PROTECTED]>
wrote:
Jason Warner w
Donald Woods wrote:
Shouldn't we put roadmap/release/project management type info in the
GMOxPMT space instead? The DEV space is getting crowded with other
topics and it's hard to find the Roadmap pages
-Donald
Hernan Cunico wrote:
Hi All,
We kinda started to have some discussion some
All,
We have a Geronimo Board report due by July 14th. I created a skeleton
file at
http://cwiki.apache.org/confluence/display/GMOxPMGT/Apache+Geronimo+Board+Report+-+2008-07+-+July
Will start filling it out over the weekend/early next week. Feel free
to update with relevant information.
-
Gianny Damour wrote:
Hello,
I am back from holiday; A quick scan of the mailing lists tells me that
the upgrade to WADI 2.0 is causing classloader clashes.
As identified by Jason W. and Kevan, a Tribes class is loaded by two
distinct classloaders (tomcat6 and wadi-clustering configuration
c
Shrey & myself are working on EAR Plan Creator and hope to complete by July
end.
On Thu, Jul 3, 2008 at 6:16 AM, Donald Woods <[EMAIL PROTECTED]> wrote:
> Items I've seen mentioned so far for 2.2 -
> - Java SE 6 support
> - Derby 10.4.1.3
> - Dojo 1.1.1 (minimal for console usage and plugins f
On Jul 3, 2008, at 5:10 AM, Gianny Damour wrote:
Hello,
I am back from holiday; A quick scan of the mailing lists tells me
that the upgrade to WADI 2.0 is causing classloader clashes.
As identified by Jason W. and Kevan, a Tribes class is loaded by two
distinct classloaders (tomcat6 and
Hi Joe,
You could try adding
provided
to the org.apache.geronimo.configs/jasper/{version}/car dependency in
the pom.xml. I 've seen a similar error like this before and by
adding the scope fixed it.
Thanks,
Lin
On Wed, Jul 2, 2008 at 4:33 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
Jarek Gawor wrote:
Cool, thanks. I updated this page with a list of bugs that I thought
are important for the 2.1.2 release so that we can discuss if they are
actaully required or critical for the release.
Donald & Jarek,
Thanks for starting the list!
Joe
On Wed, Jul 2, 2008 at 7:57 PM, D
[
https://issues.apache.org/jira/browse/GERONIMO-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lin Sun resolved GERONIMO-4180.
---
Resolution: Fixed
Assignee: Lin Sun (was: YunFeng Ma)
Patch committed to daytrader trunk (s
[
https://issues.apache.org/jira/browse/GERONIMO-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu T George updated GERONIMO-4178:
Attachment: G4178-r673642.patch
Captures and throws a DeploymentException if the contain
[
https://issues.apache.org/jira/browse/GERONIMO-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YunFeng Ma updated GERONIMO-4180:
-
Attachment: GERONIMO-4180.patch
The patch provides deployment plan and database script for SQL
Thanks Joseph & Tim for raising and fixing this. This was there on the back
of my mind too but never took time to fix it :(
On Thu, Jul 3, 2008 at 2:41 PM, Tim McConnell <[EMAIL PROTECTED]> wrote:
> Hi Joe, GERONIMODEVTOOLS-332 is fixed. I changed the error message you were
> getting into a warni
Hello,
I am back from holiday; A quick scan of the mailing lists tells me
that the upgrade to WADI 2.0 is causing classloader clashes.
As identified by Jason W. and Kevan, a Tribes class is loaded by two
distinct classloaders (tomcat6 and wadi-clustering configuration
classloaders), which
Hi Joe, GERONIMODEVTOOLS-332 is fixed. I changed the error message you were
getting into a warning message such that you can continue to define a server
runtime. This is now similar to the same warning message when a JRE other than
1.5 is used. There may other errors when defining a 2.1.1 serve
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell resolved GERONIMODEVTOOLS-332.
Resolution: Fixed
Changed the error message to be a warning messa
26 matches
Mail list logo
