geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anita kulshreshtha <a_kuls...@yahoo.com>
Subject Re: Re-migration to m2 - status and discussion.
Date Mon, 29 May 2006 17:24:25 GMT
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, m2-plugins, openejb and configs (non jetty and
non client). Here are the results - 

Thanks
Anita


er-1.2-SNAPSHOT.car
[INFO]
[INFO]
[INFO]
----------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
----------------------------------------------------------------------------
[INFO] Geronimo ............................................... SUCCESS
[2.516s]
[INFO] Geronimo Modules ....................................... SUCCESS
[0.047s]
[INFO] Geronimo :: Activation ................................. SUCCESS
[3.719s]
[INFO] Geronimo :: Kernel ..................................... SUCCESS
[2:07.969s]
[INFO] Geronimo :: Common ..................................... SUCCESS
[8.390s]
[INFO] Geronimo :: Util ....................................... SUCCESS
[13.719s]
[INFO] Geronimo :: System ..................................... SUCCESS
[8.297s]
[INFO] Geronimo :: Management API ............................. SUCCESS
[3.062s]
[INFO] Geronimo :: J2EE ....................................... SUCCESS
[5.813s]
[INFO] Geronimo :: Core ....................................... SUCCESS
[4.656s]
[INFO] Geronimo :: Security ................................... SUCCESS
[30.297s]
[INFO] Geronimo :: Naming ..................................... SUCCESS
[5.125s]
[INFO] Geronimo :: Web Services ............................... SUCCESS
[3.062s]
[INFO] Geronimo :: Axis ....................................... SUCCESS
[7.547s]
[INFO] Geronimo :: J2EE Schema ................................ SUCCESS
[51.672s]
[INFO] Geronimo :: Deployment ................................. SUCCESS
[6.969s]
[INFO] Geronimo :: Deploy :: Common Config .................... SUCCESS
[1.453s]
[INFO] Geronimo :: Service :: Builder ......................... SUCCESS
[14.828s]
[INFO] Geronimo :: Security :: Builder ........................ SUCCESS
[8.109s]
[INFO] Geronimo :: J2EE :: Builder ............................ SUCCESS
[21.453s]
[INFO] Geronimo :: Naming :: Builder .......................... SUCCESS
[12.954s]
[INFO] Geronimo :: Axis :: Builder ............................ SUCCESS
[20.843s]
[INFO] Geronimo :: Transaction ................................ SUCCESS
[31.938s]
[INFO] Geronimo :: Client ..................................... SUCCESS
[1.625s]
[INFO] Geronimo :: Test :: DDBeans ............................ SUCCESS
[5.532s]
[INFO] Geronimo :: Connector .................................. SUCCESS
[5.734s]
[INFO] Geronimo :: Connector :: Builder ....................... SUCCESS
[13.563s]
[INFO] Geronimo :: Client Builder ............................. SUCCESS
[9.625s]
[INFO] Geronimo :: Configuration Converter .................... SUCCESS
[2.343s]
[INFO] Geronimo :: Web :: Builder ............................. SUCCESS
[10.672s]
[INFO] Geronimo :: Deploy :: JSR-88 ........................... SUCCESS
[7.203s]
[INFO] Geronimo :: Deploy :: CLI Tool ......................... SUCCESS
[4.453s]
[INFO] Geronimo :: Derby ...................................... SUCCESS
[2.266s]
[INFO] Geronimo :: Directory .................................. SUCCESS
[21.281s]
[INFO] Geronimo :: Deploy :: Hot Deployer ..................... SUCCESS
[2.531s]
[INFO] Geronimo :: Installer :: Processing .................... SUCCESS
[1.750s]
[INFO] Geronimo :: JMX Remoting ............................... SUCCESS
[3.500s]
[INFO] Geronimo :: Mail ....................................... SUCCESS
[3.719s]
[INFO] Geronimo :: Scripts .................................... SUCCESS
[8.187s]
[INFO] Geronimo :: Timer ...................................... SUCCESS
[1:16.297s]
[INFO] Geronimo :: Tomcat ..................................... SUCCESS
[49.328s]
[INFO] Geronimo :: Tomcat :: Builder .......................... SUCCESS
[30.079s]
[INFO] Geronimo :: Upgrade .................................... SUCCESS
[4.890s]
[INFO] Geronimo Plugins ....................................... SUCCESS
[0.063s]
[INFO] Geronimo :: Maven2 Packaging Plugin .................... SUCCESS
[10.968s]
[INFO] OpenEJB ................................................ SUCCESS
[0.188s]
[INFO] OpenEJB :: Core ........................................ SUCCESS
[44.312s]
[INFO] OpenEJB :: PK Generation :: Builder .................... SUCCESS
[9.641s]
[INFO] OpenEJB :: Builder ..................................... SUCCESS
[37.937s]
[INFO] Geronimo Configs ....................................... SUCCESS
[0.156s]
[INFO] Geronimo Configuration for performing service deployments 
SUCCESS [5.016s]
[INFO] System Configuration for the J2EE Server ............... SUCCESS
[20.109s]
[INFO] RMI Naming configuration ............................... SUCCESS
[1.547s]
[INFO] Server Configuration for the J2EE Server ............... SUCCESS
[1.813s]
[INFO] Axis Configuration for the J2EE Server ................. SUCCESS
[1.906s]
[INFO] Configuration for performing J2EE deployments .......... SUCCESS
[2.391s]
[INFO] Axis Configuration for performing J2EE deployments ..... SUCCESS
[1.547s]
[INFO] Configuration for Application Client Deployments ....... SUCCESS
[1.531s]
[INFO] System Configuration for the J2EE Client ............... SUCCESS
[0.875s]
[INFO] Directory Configuration ................................ SUCCESS
[1.079s]
[INFO] Hot Deployer ........................................... SUCCESS
[1.234s]
[INFO] Security Configuration for the J2EE server ............. SUCCESS
[3.016s]
[INFO] LDAP Security Realm .................................... SUCCESS
[0.921s]
[INFO] Online Deployer Configuration .......................... SUCCESS
[0.594s]
[INFO] openejb Configuration for performing J2EE deployments .. SUCCESS
[1.266s]
[INFO] Shared Library GBean ................................... SUCCESS
[0.640s]
[INFO] Shutdown Configuration ................................. SUCCESS
[0.625s]
[INFO] Tomcat Configuration for the J2EE Server ............... SUCCESS
[1.954s]
[INFO] Tomcat Deployer Configuration for performing J2EE deployments 
SUCCESS [1.140s]
[INFO] Configuration for no j2ee app clients .................. SUCCESS
[0.953s]
[INFO] Configuration for no EJBs .............................. SUCCESS
[0.937s]
[INFO] Unavailable Web Services deployer ...................... SUCCESS
[0.985s]
[INFO]
----------------------------------------------------------------------------
[INFO]
----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: 13 minutes 45 seconds
[INFO] Finished at: Mon May 29 13:22:33 EDT 2006
[INFO] Final Memory: 32M/63M
[INFO]
----------------------------------------------------------------------------
--- anita kulshreshtha <a_kulshre@yahoo.com> wrote:

> Prasad, 
>    Here is yet another modules.patch. I had to add the following
> lines
> to kernel, system, core, connector and security modules to deal with
> the assert statements. I have tried putting these in parent pom in
> pluginManagement and w/o pluginManagement section. But this does not
> seem to get inherited! I am using maven 2.0.4. These used to work
> earlier (in 1.2-dead and 1.1.).
>            <plugin>
>                 <artifactId>maven-compiler-plugin</artifactId>
>                 <configuration>
>                     <source>1.4</source>
>                     <target>1.4</target>
>                 </configuration>
>             </plugin>
> 
> Thanks
> Anita
> --- anita kulshreshtha <a_kulshre@yahoo.com> wrote:
> 
> > Prasad and John,
> >     Thanks! John for looking into this. I am attaching a
> > newmodules.patch which has beed edited using emacs. I have removed
> > ^M.
> > from lines like these (this is an emacs view) :
> > 
> > Index: kernel/pom.xml^M
> >
> ===================================================================^M
> > --- kernel/pom.xml	(revision 0)^M
> > +++ kernel/pom.xml	(revision 0)^M
> > @@ -0,0 +1,89 @@^M
> >    I have checked my original pom.xmls, they do not contain ^M. I
> do
> > not know why the generated lines contain ^M in the patch. This
> patch
> > is
> > built for the new trunk using svn diff ....
> > 
> > Thnaks
> > Anita
> > 
> > --- anita kulshreshtha <a_kulshre@yahoo.com> wrote:
> > 
> > > inline..
> > > 
> > > --- Prasad Kashyap <goyathlay.geronimo@gmail.com> wrote:
> > > 
> > > > Thank you John.
> > > > 
> > > > Anita, the asm dependency in axis-builder/pom.xml needs
> <version>
> > > > 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 should go there?
> > > 
> > > Before you regenerate the patch the next time, can you
> > > > please
> > > > set your svn as per John's instructions in the wiki page ?
> > >    The 'modules' patch I submitted contains the follwing line for
> > > each
> > > pom.xml -
> > > 
> > > Property changes on: scripts\pom.xml
> > >
> ___________________________________________________________________
> > > Name: svn:eol-style
> > >    + native
> > > 
> > >    So I guess, they are being set by my box. There are a lot of
> > files
> > > in svn which need to have their eol-style set. It would be very
> > > helpful
> > > to run the script John talked about. Otherwise the new patches
> are
> > > very
> > > hard to read.
> > > 
> > > Thanks
> > > Anita 
> > > 
> > > > 
> > > > Cheers
> > > > Prasad
> > > > 
> > > > On 5/25/06, John Sisson <jrsisson@gmail.com> wrote:
> > > > > 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#head-4cfe1f3516da2bace5dcb5ed105eaed7c7478afb
> > > > >
> > > > > so that any new files you create will have the correct svn
> > > > properties.
> > > > >
> > > > > I can run the script I put together (
> > > > >
> > > >
> > >
> >
> https://svn.apache.org/repos/asf/geronimo/gbuild/trunk/svnpropset.sh
> > > > >   ) that fixes the svn properties on existing files if you
> > like. 
> > > > Let me
> > > > > know..
> > > > >
> > > > > I recommend that you make a backup of any changes you haven't
> > > > committed
> > > > > first just in case.. (as fixing the line endings can result
> in
> > > > every
> > > > > line in your files being changed, possibly causing merge
> > > issues)..
> > > > >
> > > > > After the svn properties are fixed, the patches may need to
> be
> > > > regenerated.
> > > > >
> > > > > John
> > > > >
> > > > > Prasad Kashyap wrote:
> > > > > > I was able to apply the same patch on linux. Wonder why not
> > on
> > > > windows ?
> > > > > >
> > > > > > Cheers
> > > > > > Prasad
> > > > > >
> > > > > > On 5/25/06, Prasad Kashyap <goyathlay.geronimo@gmail.com>
> > > 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 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 5/25/06, anita kulshreshtha <a_kulshre@yahoo.com>
> wrote:
> > > > > >> > inline..
> > > > > >> >
> > > > > >> > --- Prasad Kashyap <goyathlay.geronimo@gmail.com>
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 the individual modules and configs.
> > > > > >> > >
> > > > > >> > > You may attach those modules.patch and config.patch
to
> > the
> > > > G-851
> > > > > >> > > jira.
> > > > > >> > > I shall attach a similar uber patch for the
> applications
> > > in
> > > > the same
> > > > > >> > > jira.
> > > > > >> >    I will rebuild the patches against the trunk. I
am
> > still
> > > > trying to
> > > > > >> > get an m1 build for the trunk.
> > > > > >> >
> > > > > >> > >
> > > > > >> > > The pom.patch from your G-1740 couldn't be applied
> > because
> > > > the
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Mime
View raw message