Ug... this doesn't sound very easy... and would mean a bunch more
"magic" in the build, which I would rather avoid. I'd like to see if
we can speed up the normal build so that its reasonable to just `mvn
install` and in a *reasonable* amount of time have a new build.
For quicker turn aroun
Maybe we could have a maven profile that after the build deploys
whatever got built to whatever running geronimo server it can find?
Another pie-in-the-sky useful sounding feature would be a recursive
build where you specify a depth and maven figures out the
dependencies in geronimo to that
Thanks everyone for your input!
I will make a script in the near future for making some of these points
easier, at least from my perspective.
Don
On 3/9/07, Rakesh Midha <[EMAIL PROTECTED]> wrote:
I find this to be working quicker for me
1. Make changes in geronimo-console-standard (I use ecli
I find this to be working quicker for me
1. Make changes in geronimo-console-standard (I use eclipse for this)
2. go to applications\console
if changes only in java files, use mvn -o
if changes in JSP's also, use mvn -o clean install
3. copy
cp geronimo-console-standard\target\geronimo-
cons
Hi
I have tried building separate modules actually the same way what Don
has followed.Haven't you came a cross to build dependency modules(which
are complaining) while you are trying to build a particular module?After
building all the modules then figure out the target files resides on the
unzippe
Good question and it would be great to see how others tackle this prob.
I spent lots of time trying to figure out the best way too.:-)
Here's one possible solution:
1) You go to the project you made change and run mvn from there.
2) Figure out where the target files reside on the unzipped asse
On Mar 8, 2007, at 8:16 PM, Don Hill wrote:
I know this is probably more of a maven question but after I do a
mvn clean install and I am working on some classes in applications/
console/geronimo-console-standard, what is the process that is
followed to build just this module and then do a 'mv
Hi,
I know this is probably more of a maven question but after I do a mvn clean
install and I am working on some classes in
applications/console/geronimo-console-standard, what is the process that is
followed to build just this module and then do a 'mvn install \ mvn -Ptools
geronimo:start'
I ju
Vamsi,
I'm not sure if this is correct but I think if you want a module (jar)
level dependency that is added to the assembly repo but not included in
the config plan you can do the folllowing:
- add a dependency entry in geronimo-dependency.xml under that module's
src/main/resources/META-INF/
Hi,
I want to know how the following can be achieved in branches\1.1 and trunk builds.
When I build a configuration, I want a certain dependency to be copied
to repository at assembly time. I do not want the build to add
this dependency directly to the configuration that is built. It
is better
Are you referring to the CosNaming.idl or the ServerNamingContext.java?
I am not aware of anything missing from the CosNaming.idl, but the
ServerNamingContext.java is a just a bare-bones impl that allows the
client to perform a lookup. No other methods are supported/implemented
at this time.
I just noticed that the interop module has an implementation of cos
naming, but it doesn't look like it is complete. Are you working on
finishing this? Also, do you have some sample code that binds this
into an orb.
Right now, in openejb we support the OpenORBNaming service and the Sun
o
I just did a fresh get of Geronimo and I have the following build
error. I have done a search of the codeline to find out who depends on
the interoperable name server, but all I can find are references to tmporb*.
Any suggestions?
Thanks
Mark
[mkdir] Created dir:
D:\OpenSource\Apache\geroni
Hi Hari;
EWS build.xml generation is first writen without the knowladge about
geronimo axis module and when it try to acomadate later and get the
build working things get messy (there is a problem of finding the
maven repository in all the machines)
I will have a look at the both build to improve
I have a build related question (in axis module) that could be related
to this JIRA entry.
The EWS code generation currently assumes that the directory structure
for axis looks like geronimo/modules/axis. Geronimo build runs into
problems if I either rename geronimo to, say, trunk (i.e.,
trunk/mod
15 matches
Mail list logo
