David Oren wrote:
What I'd like to suggest is adding the ability to deploy directories --
that is, instead of having to package an application in a war or ear file
and then deploying that file, the deployer will be given the full path where
the application is located. The application will be
The subject says it all ;-)
Jeff
Special request from the Maven team:those doing deployment to java-repository using jar:deploy (this does not affect normal users), please ensure you are using maven-artifact-plugin 1.5.2 or above.If you are using
1.1-beta-2, it comes with the latest version.If you are using 1.0.2, you must
problems getting the UserPrincipal for servlets and struts
--
Key: GERONIMO-1014
URL: http://issues.apache.org/jira/browse/GERONIMO-1014
Project: Geronimo
Type: Bug
Environment: WinXP, Geronimo-M4
[ http://issues.apache.org/jira/browse/GERONIMO-1014?page=all ]
Ludwig Laman updated GERONIMO-1014:
---
Attachment: sampleWebApp.war
attached is a simple war file (taken from the whole servlet/struts application
just to present a simple J2EE security
[
http://issues.apache.org/jira/browse/GERONIMO-1014?page=comments#action_12329532
]
Ludwig Laman commented on GERONIMO-1014:
This is how it goes:
1. Deploy the war.
2. Browse to http://localhost:8080/sampleWebApp
3. Login as system/manager
4.
do you really want to call it v1.0.0?
maybe tack on a -dev or something to indicate it's not a release?
On Sep 15, 2005, at 3:54 PM, [EMAIL PROTECTED] wrote:
Author: sppatel
Date: Thu Sep 15 12:54:49 2005
New Revision: 289302
URL: http://svn.apache.org/viewcvs?rev=289302view=rev
Log:
change
Yeah, good call. For eclipse to be able to load the plugin it needs to
end in a version number. I can bump the versions down.
Geir Magnusson Jr. wrote:
do you really want to call it v1.0.0?
maybe tack on a -dev or something to indicate it's not a release?
On Sep 15, 2005, at 3:54 PM,
Jacek, yes there is an all in one package, but only for the .7 released
versions. The current plugin won't build against .7 as there have been
breaking API changes since then.
Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Geronimo Wiki for
change
To get some discussion going on release schedules... What version should
we have the eclipse plugin at? Currently it stands at 1.0.0.
To give you some background
First off, Eclipse requires a pure version number, so we can't have
1.0.0-dev. If you go to any of the eclipse projects,
OpenEJB as well. The only test I did was ensure XMLBeans ran, and they
were not any errors during generation.
Matt Hogstrom wrote:
Did you do this for Geronimo only or did you test OpenEJB as well?
Sachin Patel wrote:
In 2 of the geronimo schema files the imports' schemaLocation path
are
Ok...I can commit this for you so let me know when we're in sync.
Sachin Patel wrote:
OpenEJB as well. The only test I did was ensure XMLBeans ran, and they
were not any errors during generation.
Matt Hogstrom wrote:
Did you do this for Geronimo only or did you test OpenEJB as well?
Hi there, ...
It has been up to a slow start, but I have finally gotten something
rolling now.
As I have mentioned earlier, I wanted to redo the I/O subsystem, and
this is going quite well. The first milestone I am targeting is to
be able to do client side stream-based invocations; i.e.
This is a great idea. Running the TCK is a huge pain for us and we
have a very small matrix right now (2 version of geronimo * 1
platform * 1 Java VM).
I was chatting with David Blevins about this yesterday, and he
suggested that we make this a full subproject. The subproject could
Cool. Thanks Matt. Would one of the other geronimo committers mind
taking as sec and fixing up geronimo-web.xsd and geronimo-security.xsd?
Thanks.
Matt Hogstrom wrote:
Ok...I can commit this for you so let me know when we're in sync.
Sachin Patel wrote:
OpenEJB as well. The only test I did
On 9/16/05, David Oren [EMAIL PROTECTED] wrote:
What I'd like to suggest is adding the ability to deploy directories --
that is, instead of having to package an application in a war or ear file
and then deploying that file, the deployer will be given the full path where
the application is
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-12?page=comments#action_12329565
]
Miguel A Paraz commented on GERONIMODEVTOOLS-12:
I updated and rebuit. Same thing. The project is empty except for the bean file.
I found that the
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-12?page=comments#action_12329567
]
Sachin Patel commented on GERONIMODEVTOOLS-12:
--
I imported you project, and I was able to deploy.
14:25:28,217 INFO [LocalConfigStore:config-store]
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-12?page=comments#action_12329568
]
Sachin Patel commented on GERONIMODEVTOOLS-12:
--
Also which wtp-I20050914 driver are you on? There were 3 on that day, and one
of them had 118 compile
[
http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-12?page=comments#action_12329569
]
Sachin Patel commented on GERONIMODEVTOOLS-12:
--
Actually there is already a trace statement in WTP that will give us the info
that we need. Enable
Sachin Patel wrote:
I've posted a link to the unstable version of the eclipse plugin
binary on the subproject site.
Jacek, I've posted the build instructions on the wiki. You can get to
it from the subproject site as well. Look forward on getting some
feedback from you.
Thanks! I'm trying
Sachin Patel wrote:
Jacek, yes there is an all in one package, but only for the .7 released
versions. The current plugin won't build against .7 as there have been
breaking API changes since then.
So, is downloading all of the pieces one by one the only way to build
the Eclipse plugin?
The WTP All-in-one pack is only available for the .7 release which is
quite old now.
I've been working with WTP to ensure that all their plugins have been
converted to jars, and this has been recently done for the ones listed
below. Thats why the .7 all in one package no longer works. Plus
Yes. Its the only way to be able to launch it too. So you have to grab
each of the peices anyways.
There will be an all-in-one package for WTP 1.0 so you don't have to.
I'll talk to the WTP team to see if they can make one available for the
next milestone at the end of the month.
Jacek
Brett,
Have the changes been committed that make the Geronimo HEAD work
with 1.1-b2? Last time I noticed, you said we had some POMs that were not
valid I think.
Thanks,
Aaron
On Fri, 16 Sep 2005, Brett Porter wrote:
Special request from the Maven team:
those doing
I believe Dain committed them the other day.Cheers,BrettOn 9/17/05, Aaron Mulder [EMAIL PROTECTED]
wrote:Brett,Have the changes been committed that make the Geronimo HEAD work
with 1.1-b2?Last time I noticed, you said we had some POMs that were notvalid I think.Thanks,AaronOn Fri, 16 Sep 2005,
[
http://issues.apache.org/jira/browse/GERONIMO-1011?page=comments#action_12329604
]
Jeremy Boynes commented on GERONIMO-1011:
-
Fixed in a slightly different way
Sendingmodules/assembly/src/plan/j2ee-jetty-plan.xml
Sending
I committed the patch and have been using 1.1-b2 for about a week now.
-dain
On Sep 16, 2005, at 6:01 PM, Brett Porter wrote:
I believe Dain committed them the other day.
Cheers,
Brett
On 9/17/05, Aaron Mulder [EMAIL PROTECTED] wrote:Brett,
Have the changes been committed that make
Anyone mind if I delete the old M4 QA branch? The correct M4 code is
in tags/v1_0_M4, so this only leads to confusion (including mine
earlier today).
-dain
On 9/17/05, Sachin Patel (JIRA) [EMAIL PROTECTED] wrote:
Actually there is already a trace statement in WTP that will give us the info
that we need. Enable trace for org.eclipse.wst.server.core and rerun and
during publish watch for...
Hi,
Sorry but I could not find how to enable WTP trace.
I would like to help testing.
--
Dorileo
On Wed, 2005-09-14 at 05:45 -0400, Geir Magnusson Jr. wrote:
I'd like to discuss how we might expand our efforts in the area of
testing and QA. Now that we're getting into the habit of J2EE
certified releases, we have a much bigger testing load
31 matches
Mail list logo
