You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@continuum.apache.org by Brett Porter <br...@apache.org> on 2006/08/10 05:40:42 UTC
Re: svn commit: r430090 - /maven/continuum/trunk/continuum-webapp/pom.xml
Hi,
I know I caught the reason from you guys on IRC this morning, apparently
plexus.xml wasn't working - but I'd like to get to the bottom of it.
Are you sure this entirely works? What about if you have
non-components.xml descriptor elements like load-on-start?
I may have made a mistake when applying it to continuum, but plexus.xml
is definitely working in MRM, and that is what the xwork integration
attempts to use to configure everything so I'm not sure this is going to
do everything you need.
Cheers,
Brett
On 10/08/2006 2:36 AM, evenisse@apache.org wrote:
> Author: evenisse
> Date: Wed Aug 9 09:36:28 2006
> New Revision: 430090
>
> URL: http://svn.apache.org/viewvc?rev=430090&view=rev
> Log:
> The merged component descriptor must be in components.xml instead of plexus.xml
>
> Modified:
> maven/continuum/trunk/continuum-webapp/pom.xml
>
> Modified: maven/continuum/trunk/continuum-webapp/pom.xml
> URL: http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/pom.xml?rev=430090&r1=430089&r2=430090&view=diff
> ==============================================================================
> --- maven/continuum/trunk/continuum-webapp/pom.xml (original)
> +++ maven/continuum/trunk/continuum-webapp/pom.xml Wed Aug 9 09:36:28 2006
> @@ -53,7 +53,7 @@
> <execution>
> <id>merge</id>
> <configuration>
> - <output>${project.build.outputDirectory}/META-INF/plexus/plexus.xml</output>
> + <output>${project.build.outputDirectory}/META-INF/plexus/components.xml</output>
> <descriptors>
> <descriptor>${project.build.directory}/generated-resources/plexus/plexus.xml</descriptor>
> <descriptor>src/main/plexus/plexus.xml</descriptor>
>
>
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
Re: svn commit: r430090 - /maven/continuum/trunk/continuum-webapp/pom.xml
Posted by Brett Porter <br...@apache.org>.
On 11/08/2006 7:52 AM, Jesse McConnell wrote:
> one possible difference I have noticed is that the jdo store is not
> loading up until it is first accessed, which is a different behavior
> then before, which make senses if its load-on-start...
Right. It also means that no builds will occur until someone hits a
webpage, which is not correct.
So I think it needs to be fixed.
> I am not sure what to say here, you can easily replicate our situation
> by changing that pom back to the plexus.xml and simply try and start
> up continuum with the jetty webapp, the CNFE stack traces pour out.
I wasn't having that problem, but I'll try again today.
- Brett
Re: svn commit: r430090 - /maven/continuum/trunk/continuum-webapp/pom.xml
Posted by Jesse McConnell <je...@gmail.com>.
> I know I caught the reason from you guys on IRC this morning, apparently
> plexus.xml wasn't working - but I'd like to get to the bottom of it.
correct, the specific error when using the plexus.xml was that when
the actions where being loaded we were getting ClassNotFoundExceptions
on the action classes themselves, so the xwork -> plexus.xml mapping
was working, but when the o.a.m.c.w.a classes (not their webwork
hints) were being loaded it couldn't find them (and the are in the
same artifact as the plexus.xml!)
> Are you sure this entirely works? What about if you have
> non-components.xml descriptor elements like load-on-start?
so far everything I have been doing with the UI has been working fine
one possible difference I have noticed is that the jdo store is not
loading up until it is first accessed, which is a different behavior
then before, which make senses if its load-on-start...
> I may have made a mistake when applying it to continuum, but plexus.xml
> is definitely working in MRM, and that is what the xwork integration
> attempts to use to configure everything so I'm not sure this is going to
> do everything you need.
I am not sure what to say here, you can easily replicate our situation
by changing that pom back to the plexus.xml and simply try and start
up continuum with the jetty webapp, the CNFE stack traces pour out.
jesse
> On 10/08/2006 2:36 AM, evenisse@apache.org wrote:
> > Author: evenisse
> > Date: Wed Aug 9 09:36:28 2006
> > New Revision: 430090
> >
> > URL: http://svn.apache.org/viewvc?rev=430090&view=rev
> > Log:
> > The merged component descriptor must be in components.xml instead of plexus.xml
> >
> > Modified:
> > maven/continuum/trunk/continuum-webapp/pom.xml
> >
> > Modified: maven/continuum/trunk/continuum-webapp/pom.xml
> > URL: http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/pom.xml?rev=430090&r1=430089&r2=430090&view=diff
> > ==============================================================================
> > --- maven/continuum/trunk/continuum-webapp/pom.xml (original)
> > +++ maven/continuum/trunk/continuum-webapp/pom.xml Wed Aug 9 09:36:28 2006
> > @@ -53,7 +53,7 @@
> > <execution>
> > <id>merge</id>
> > <configuration>
> > - <output>${project.build.outputDirectory}/META-INF/plexus/plexus.xml</output>
> > + <output>${project.build.outputDirectory}/META-INF/plexus/components.xml</output>
> > <descriptors>
> > <descriptor>${project.build.directory}/generated-resources/plexus/plexus.xml</descriptor>
> > <descriptor>src/main/plexus/plexus.xml</descriptor>
> >
> >
>
>
> --
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
>
--
jesse mcconnell
jesse.mcconnell@gmail.com