Prasad, could you peek at the patches and help sort out what needs to
get applied to m2migration?
Thanks,
--jason
On Jul 15, 2006, at 4:24 AM, anita kulshreshtha wrote:
Hi Prasad,
I wish I could be of more help and investigate why the config are
not building. These patches used to work until rev 418907 on the
trunk.
I have been unable to build the trunk using 'mvn' after RTC-2161. I
have not had time to investigate it. IIRC this error comes when the
openejb-deployer config is bad.
I will have limited email access for the next 2 weeks.
Cheers
Anita
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Hi Anita,
I applied the pending patch (geronimo-remote-deploy/pom.xml). That
was when I got that error. Are there are more patches to be applied
along with that ?
Cheers
Prasad
On 7/14/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
Would it not be simpler to use the patched version of m-a-p and
just
rename it to geronimo-assembly2-plugin and add it to our code base?
This plugin is more elegant than the ant solution. we can remove
this
code as soon as maven-assembly-plugin is updated. Are there any
problems with using code like this?
BTW, I saw your comments about remote-deploy-* configs. These
are
the pending patches at -
http://issues.apache.org/jira/browse/GERONIMO-2067#action_12415761
I will be offline for next 2 weeks due to preplanned summer
engagements.
Cheers
Anita
--- Jason Dillon <[EMAIL PROTECTED]> wrote:
It looks like the Maven 2 peeps are not going to be able to take
in
our patches to apply to the assembly plugin, which provides
mappers
and some includes/excludes to unpack and a permission related fix
to
files/file element processing.
I believe that those changes will eventually make it in, but for
now
to get around the need Prasad and I talked about using the
dependency
plugin and the antrun plugin to perform the needed "flattening"
of
the schema files for the /schema/* in the assembly.
I've implemented this already for the geronimo-jetty-j2ee
assembly in
the svkmerge/m2migration branch.
It appears to function as expected. I've disabled the remaining
assemblies which have not yet been converted. Once they have
been
converted they will be re-enabled.
Note, we are still using car:installConfigs... but we no longer
need
to have MASSEMBLY-45 or MASSEMBLY-127 applied to a custom 2.2-
SNAPSHOT version of the maven-assembly-plugin to build out
assemblies.
The full conversation is here if anyone is interested:
http://uwyn.com/drone/log/bevinbot/geronimo/20060714
Starts with '19:53 <jdillon> any thoughts on using dependency +
antrun to setup the right bits and then use the 2.1 assembly
plugin?'
--jason
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
