Please see comments inline -
On 6/11/06, David Jencks <[EMAIL PROTECTED]> wrote:
On Jun 7, 2006, at 1:03 PM, Prasad Kashyap wrote:
Attention Maven Committers !
I really wish we had a maven committer too involved with the m2
migration effort. There are atleast 3 maven JIRAs that we desperate
On Jun 7, 2006, at 1:03 PM, Prasad Kashyap wrote:Attention Maven Committers !I really wish we had a maven committer too involved with the m2migration effort. There are atleast 3 maven JIRAs that we desperatelyneed. Hopefully, then you could empathize with our pain and help usget those JIRAs resolve
Attention Maven Committers !
I really wish we had a maven committer too involved with the m2
migration effort. There are atleast 3 maven JIRAs that we desperately
need. Hopefully, then you could empathize with our pain and help us
get those JIRAs resolved :-)
Here are some of them to begin with
I have already linked GERONIMO-2066, GERONIMO-2067, and
GERONIMO-2082 to GERONIMO-2071. I am going to link GERONIMO-1740 also.
Yes, for any new work we can create subtasks.
Thnaks
Anita
--- Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On 6/6/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
>
On 6/6/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Now that we have something like a baseline of M2 in the trunk, can we
please go back to creating subtasks under Geronimo-2071 for any
current work that we are doing. This will help us prevent duplication.
Thanks Prasad! I thought it was me wh
Now that we have something like a baseline of M2 in the trunk, can we
please go back to creating subtasks under Geronimo-2071 for any
current work that we are doing. This will help us prevent duplication.
Cheers
Prasad
On 6/2/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
David J,
These a
David J,
These are the results with rev 411279 and PluginBootstrap2. I will
submit the patch in the morning. Just thought you would like to know..
Thanks
Anita
PSHOT\upgrade-cli-1.2-SNAPSHOT.car
INFO]
INFO]
INFO]
INFO
David J,
I have been working with rev 409296, and openejb 2659. Today I
updated to rev 411279. There have been changes in o.a.g.kernel that
affect PackageBuilder, MavenConfigStore, and MavenAttributeStore. I
need to incorporate these changes into m2 plugin and retest everything.
:( I am assumin
Thanx Jeff. What do you think about
http://jira.codehaus.org/browse/MJSPC-3. ? Can we expect that anytime
soon ? If so, then I'd rather wait to make a run thro' the pom.xml of
all the apps just once.
Cheers
Prasad
On 6/1/06, Jeff Genender <[EMAIL PROTECTED]> wrote:
Prasad,
If you really need t
Prasad,
If you really need to use the jspc plugin now, please use version 1.4.3.
It does not fork the compile.
Jeff
Prasad Kashyap wrote:
> The migration of applications to M2 has been kinda held up by the
> following 2 maven jiras
>
> http://jira.codehaus.org/browse/MJSPC-2 (to fix jspc plugi
The migration of applications to M2 has been kinda held up by the
following 2 maven jiras
http://jira.codehaus.org/browse/MJSPC-2 (to fix jspc plugin)
http://jira.codehaus.org/browse/MWAR-45 (to fix jar'ing classes to web-inf/lib).
I have submitted a patch for the latter (maven-war-plugin, mwar-
Thanx Jeff. Please see comments inline -
Cheers
Prasad
On 5/31/06, Jeff Genender <[EMAIL PROTECTED]> wrote:
Prasad,
I can fix #1. I need to dig up some old code from the 1.4.3 version. I
converted to a forked version because it really lightened the amount of
code in the plugin. But I have he
inline..
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> I found some more modules that have not yet been migrated. Jetty,
> jetty-builder and upgrade come to mind. Think they are a few more. I
> have patches for some.
The patch dt May 29th to G-1740 includes 'upgrade'! Since then I
have bake
Prasad,
I can fix #1. I need to dig up some old code from the 1.4.3 version. I
converted to a forked version because it really lightened the amount of
code in the plugin. But I have heard of this being an issue, so I may
fatten the plugin up a little bit and force a call to javac once again.
Co
Thanx Anita. Yep. I had tried that too. In fact, I had removed
everything from the parent pom and invoked the jspc plugin only in the
uddi-db pom. Even then, the other plugins get executed twice.
The jspc mojo is bound to the generate-sources phase by default. I
didn't change that. It then execut
Prasad,
Thanks! More inline..
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> I have all the applications migrated to M2 now. But I have a problem
> using the jspc-maven-plugin to precompile the JSPs. I hope Jeff can
> help me here.
>
> The jspc-maven-plugin is configured in the parent pom a
I found some more modules that have not yet been migrated. Jetty,
jetty-builder and upgrade come to mind. Think they are a few more. I
have patches for some.
It would be nice if we can commit the others from Anita's patch(es) so
that we have something to keep building upon. I guess we agreed upon
I have all the applications migrated to M2 now. But I have a problem
using the jspc-maven-plugin to precompile the JSPs. I hope Jeff can
help me here.
The jspc-maven-plugin is configured in the parent pom and executed by
the pom in each application. Please find attached the parent pom (goes
in ge
Snapshots are not uploaded on public repos.
But they are available at
http://people.apache.org/maven-snapshot-repository/org/apache/geronimo/specs/geronimo-j2ee_1.4_spec/1.1-SNAPSHOT/
Cheers,
Guillaume Nodet
anita kulshreshtha wrote:
I wish it was true! Prasad has agreed ;) to take car
Jacek,
Thanks! More inline..
--- Jacek Laskowski <[EMAIL PROTECTED]> wrote:
> On 5/29/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
>
> > Please ignore this patch. The earlier patch should work. The
> > problem is the parent pom.xml. It creates conflicts. It will be
> easier
> > if t
On 5/29/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
Please ignore this patch. The earlier patch should work. The
problem is the parent pom.xml. It creates conflicts. It will be easier
if this was deleted and the new pom.xml was added. The problem
mentioned below was caused by wrong ger
Prasad,
Please ignore this patch. The earlier patch should work. The
problem is the parent pom.xml. It creates conflicts. It will be easier
if this was deleted and the new pom.xml was added. The problem
mentioned below was caused by wrong geronimoVersion! I am running a
full build, i.e moduels,
inline..
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> Thank you John.
>
> Anita, the asm dependency in axis-builder/pom.xml needs
> element.
This is because your version of parent pom.xml does not have an asm
dependency element in dependency management section. Isn't this
something that
Thank you John.
Anita, the asm dependency in axis-builder/pom.xml needs
element. Before you regenerate the patch the next time, can you please
set your svn as per John's instructions in the wiki page ?
Cheers
Prasad
On 5/25/06, John Sisson <[EMAIL PROTECTED]> wrote:
I am guessing this is beca
I am guessing this is because the svn:eol-style is property is not set
to native for the pom.xml file and that the patch was originally created
on a *NIX box?
Can *everyone* please check that you have svn set up as discussed in the
document :
http://wiki.apache.org/geronimo/GettingSourceCode
Did you forget to attach the patch or did you mean you were going to attach it ?
Here's the latest top level pom.xml with the version changes.
Cheers
Prasad
On 5/25/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote:
I am attaching a patch for 1.2. I finally built 'modules' with M1 on
the tru
I am attaching a patch for 1.2. I finally built 'modules' with M1 on
the trunk(The PluginInstallerTest failed). This patch builds, but I had
to skip tests. See pom.xml in modules. Jetty module can not find needed
jars. What version changes were made recently?
Thanks
Anita
--- Prasad Kashyap <
I was able to apply the same patch on linux. Wonder why not on windows ?
Cheers
Prasad
On 5/25/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:
Anita,
I'm unable to apply your modules.patch using TortoiseSVN on XP.
I first get a pop-up which says, "{g_path}/modules/tomcat/pom.xml has
no URL." It
Anita,
I'm unable to apply your modules.patch using TortoiseSVN on XP.
I first get a pop-up which says, "{g_path}/modules/tomcat/pom.xml has
no URL." It then tries to retrieve version 0 of file. That fails and
it says, "patching not possible"
Am I doing anything wrong here ?
Cheers
Prasad
On
inline..
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> Anita, that is okay with me.
>
> So we shall continue to use the old JIRA G-851.
>
> You now seem to have a uber patch, one each for the modules and
> configs. This, I believe, will contain the different patches that we
> submitted for th
Anita, that is okay with me.
So we shall continue to use the old JIRA G-851.
You now seem to have a uber patch, one each for the modules and
configs. This, I believe, will contain the different patches that we
submitted for the individual modules and configs.
You may attach those modules.patch
inline..
--- Prasad Kashyap <[EMAIL PROTECTED]> wrote:
> Now that we have a new 1.2 trunk, we can go ahead migrating the build
> to m2 (again).
>
> A recap:
>
> 1. The build in the old trunk was migrated to m2. It can be found
> here
> http://svn.apache.org/viewvc/geronimo/branches/
Now that we have a new 1.2 trunk, we can go ahead migrating the build
to m2 (again).
A recap:
1. The build in the old trunk was migrated to m2. It can be found here
http://svn.apache.org/viewvc/geronimo/branches/dead-1.2/
2. The old migration JIRA was under the JIRA G-851.
http://is
33 matches
Mail list logo
