[
https://issues.apache.org/jira/browse/GERONIMO-4733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan resolved GERONIMO-4733.
Resolution: Fixed
Commit changes to trunk At revision: 794146, 2.1.5 At revision: 794147.
Thanks for
[
https://issues.apache.org/jira/browse/GERONIMO-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin He updated GERONIMO-4743:
-
Component/s: (was: Plugins)
car-maven-plugin
a bug when the assembled server
Previously and in a common way, we do principal-role mapping in a
deployment plan (such as geronimo-web.xml,openejb-jar.xml),
like:
role-mappings
role role-name=user
principal
class=o.a.g.s.r.providers.GeronimoGroupPrincipal name=UserGrp/
/role
...
/role-mappings
But
[
https://issues.apache.org/jira/browse/GERONIMO-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin He closed GERONIMO-4743.
Resolution: Fixed
a bug when the assembled server stops in eclipse
djencks wrote:
Isn't jsf pretty much a struts replacement? I kinda thought struts
and struts 2 were obsolete after jsf came out.
Activemq broker and the apache directory plugin both show using spring
in geronimo, although not as end-user apps.
The reason I add this is that I saw
On Jul 14, 2009, at 11:29 PM, Rodger wrote:
Previously and in a common way, we do principal-role mapping in a
deployment plan (such as geronimo-web.xml,openejb-jar.xml),
like:
role-mappings
role role-name=user
principal
class=o.a.g.s.r.providers.GeronimoGroupPrincipal
On Jul 14, 2009, at 11:40 PM, Forrest_Xia wrote:
djencks wrote:
Isn't jsf pretty much a struts replacement? I kinda thought struts
and struts 2 were obsolete after jsf came out.
Activemq broker and the apache directory plugin both show using
spring
in geronimo, although not as end-user
[
https://issues.apache.org/jira/browse/GERONIMO-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731327#action_12731327
]
David Jencks commented on GERONIMO-4723:
So, apparently this works fine for
Jay -- many thanks for trying out the patch and committing it.
I think the last artifact in our svn repo is the dojo 0.4.3. I can't
find it released anywhere but the source code is in a handy svn repo.
I cooked up a modification of our war-packaging for it that uses the
maven scm plugin
OpenEJB portlet page crushes.
-
Key: GERONIMO-4746
URL: https://issues.apache.org/jira/browse/GERONIMO-4746
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components:
[
https://issues.apache.org/jira/browse/GERONIMO-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kan Ogawa updated GERONIMO-4746:
Attachment: GERONIMO-4746_ScreenShot.png
OpenEJB portlet page crushes.
Geronimo Revision: 794147 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMO-4746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731368#action_12731368
]
Rex Wang commented on GERONIMO-4746:
Should be..
script type=text/javascript
[
https://issues.apache.org/jira/browse/GERONIMO-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731374#action_12731374
]
Han Hong Fang commented on GERONIMO-4621:
-
Hi all,
I verify the patch with
[
https://issues.apache.org/jira/browse/GERONIMO-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Han Hong Fang closed GERONIMO-4621.
---
Exception occurs when export debugviews-console-tomcat plugin
I'd like to try it :-)
-Rex
2009/7/15 David Jencks david_jen...@yahoo.com
Jay -- many thanks for trying out the patch and committing it.
I think the last artifact in our svn repo is the dojo 0.4.3. I can't find
it released anywhere but the source code is in a handy svn repo. I cooked
up a
tried it.
1.
svn co
https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3
mvn clean install
success!
2.
modify the plugins/dojo-legacy stuff
the patch in attachment shows the modification.
build successfully
3.
I did not build the entire server, but just remove the old
On Jul 15, 2009, at 3:50 AM, David Jencks wrote:
Jay -- many thanks for trying out the patch and committing it.
I think the last artifact in our svn repo is the dojo 0.4.3. I
can't find it released anywhere but the source code is in a handy
svn repo. I cooked up a modification of our
agree, the new 1.3.0 also brings some code change to other portlets(see
https://issues.apache.org/jira/browse/GERONIMO-4746), in any case, we need
to learn it.
I'd like to look into it further.
-Rex
2009/7/15 Kevan Miller kevan.mil...@gmail.com
On Jul 15, 2009, at 3:50 AM, David Jencks
On Jul 14, 2009, at 10:59 PM, Joe Bohn wrote:
Sorry ... I think you should just consider the lack of comments to
be silent approval :-).
I was, just giving people a reminder...
I really am fine with it just as it is worded. However, here are
some other thoughts.
- Do we need to
Geronimo Revision: 794246 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715
[INFO] BUILD
[
https://issues.apache.org/jira/browse/GERONIMO-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731544#action_12731544
]
Jarek Gawor commented on GERONIMO-4642:
---
Rahul,
I modified your patch for web
On Jul 15, 2009, at 6:31 AM, Kevan Miller wrote:
On Jul 15, 2009, at 3:50 AM, David Jencks wrote:
Jay -- many thanks for trying out the patch and committing it.
I think the last artifact in our svn repo is the dojo 0.4.3. I
can't find it released anywhere but the source code is in a
On Jul 15, 2009, at 6:27 AM, Rex Wang wrote:
tried it.
1.
svn co
https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3
mvn clean install
success!
2.
modify the plugins/dojo-legacy stuff
the patch in attachment shows the modification.
build successfully
3.
I did not
On Jul 15, 2009, at 12:43 PM, David Jencks wrote:
Of course this would be much much better but I thought that we'd
investigated this and Joe Leong said it would be a lot of work and
no one volunteered to do it?
Right. I don't really know how much work is involved. And nobody
All,
I started thinking about updating branches/2.1 to use the new 6.0.20
Tomcat that we're building.
This would include updating genesis version, and probably a few
additional changes. I'd like to keep changes to a minimum. However,
think it would be good to use the new Tomcat generation
Geronimo Revision: 794340 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090715
[INFO] BUILD
+1 to a 2.1.5 release with Tomcat 6.0.20, which contains several
security fixes.
0 for moving to Genesis 2.0, since we have yet to publish a server
release with it
-Donald
Kevan Miller wrote:
All,
I started thinking about updating branches/2.1 to use the new 6.0.20
Tomcat that we're
On Jul 15, 2009, at 4:59 PM, Donald Woods wrote:
+1 to a 2.1.5 release with Tomcat 6.0.20, which contains several
security fixes.
0 for moving to Genesis 2.0, since we have yet to publish a server
release with it
Ya. I was thinking that we might want it for new Nexus repository
On Jul 15, 2009, at 11:12 AM, David Jencks wrote:
On Jul 15, 2009, at 6:27 AM, Rex Wang wrote:
tried it.
1.
svn co
https://svn.apache.org/repos/asf/geronimo/external/trunk/geronimo-dojo-0.4.3
mvn clean install
success!
2.
modify the plugins/dojo-legacy stuff
the patch in attachment shows
I think the ease of use character of Geronimo is better to be worded in the
general description. The convenient admin console is definitely a bright
spot compared to other open source java application servers.
--
View this message in context:
I don't think only including the dojo.js is OK.. I might make you confusing
on the reference to dojo/0.4/dojo.js stated above, and that ref can be saw
as a sign which represents the project(debug-view) depends on the
dojo-legacy project, which is not saying the jsps only need the dojo.js. eg:
I think the main reason why the new war has the different structure with the
old one is:
in the pom.xml of ext\trunk\geronimo-dojo-0.4.3, only check out the files in
src to target/resource
execution
idcheckout/id
[
https://issues.apache.org/jira/browse/GERONIMO-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan resolved GERONIMO-4589.
Resolution: Fixed
Commit to trunk At revision: 794506, and 2.1.5-SNAPSHOT At revision: 794507.
Thanks
[
https://issues.apache.org/jira/browse/GERONIMO-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731784#action_12731784
]
Han Hong Fang commented on GERONIMO-4718:
-
Hi,
I tried with G2.2 build
a {0} did not get replaced in the last portlet of console --- Apache HTTP
--
Key: GERONIMO-4747
URL: https://issues.apache.org/jira/browse/GERONIMO-4747
Project: Geronimo
[
https://issues.apache.org/jira/browse/GERONIMO-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4747:
--
Attachment: G4747_B21.patch
G4747_trunk.patch
Seems like current resource
I noticed there's a maven resource best practice defined in
genesis-default-flava-2.0.pom.
1, Put normal resource under : ${project.basedir}/ src/main/resources
2, Put the resource that needs filtering under: ${project.basedir}/
src/main/filtered-resources
At the same time, many projects in
[
https://issues.apache.org/jira/browse/GERONIMO-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4747:
--
Patch Info: [Patch Available]
a {0} did not get replaced in the last portlet of console
39 matches
Mail list logo
