You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Scott T Weaver <sc...@binary-designs.net> on 2005/08/17 22:55:31 UTC
j2:portal.genapp overwriting existing project.xml
Is this supposed to happen? If so I really don't think this is such a great
idea as it destroys your existing portal project's descriptor. Are their
any work-arounds to fix this?
Regards,
-Scott
RE: j2:portal.genapp overwriting existing project.xml
Posted by Scott T Weaver <sc...@binary-designs.net>.
Ate,
I found out how to recreate this! It only happens after I re-install
(initMavenPlugin) the plugin. What must be happening is if the file last
modified on the portlet.xml in the maven plugin is after the one in your
project, it is copied over the top of it. Can we exclude the portlet.xml
from the genapp process? Or possibly put a check in place to not copy over
an existing portlet.xml regardless of timestamp?
Regards,
Scott
> -----Original Message-----
> From: Ate Douma [mailto:ate@douma.nu]
> Sent: Wednesday, August 17, 2005 5:09 PM
> To: Jetspeed Developers List
> Subject: Re: j2:portal.genapp overwriting existing project.xml
>
> Scott T Weaver wrote:
> > Is this supposed to happen? If so I really don't think this is such a
> great
> > idea as it destroys your existing portal project's descriptor. Are
> their
> > any work-arounds to fix this?
> Scott,
>
> This is *not* supposed to happen. And I just tested it out again and can't
> reproduce it here.
> Very weird this can happen...
>
> The project.xml (and the other, inherited maven project files for that
> matter) is created with
> the j2:portal.conf.project goal (as invoked from j2:portal.genapp).
> If you look at that goal, you'll see both project.xml and project-info.xml
> are copied
> using attribute overwrite="false".
> So, if those files are not available they will be created but should
> _never_ be updated. If that is
> happening nonetheless, I guess something must be wrong with maven, ant or
> the plugin itself...
>
>
>
> >
> >
> >
> >
> >
> > Regards,
> >
> > -Scott
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: j2:portal.genapp overwriting existing project.xml
Posted by Scott T Weaver <sc...@binary-designs.net>.
Actually, I just had this happen again. Can't figure out why.
-Scott
> -----Original Message-----
> From: Scott T Weaver [mailto:scotts-jetspeed-list@binary-designs.net]
> Sent: Thursday, August 18, 2005 9:45 AM
> To: 'Jetspeed Developers List'
> Subject: RE: j2:portal.genapp overwriting existing project.xml
>
> Hi Ate,
>
> Now I can't either maybe I'm going crazy. Anyways, don't worry about it.
>
> -Scott
>
> > -----Original Message-----
> > From: Ate Douma [mailto:ate@douma.nu]
> > Sent: Wednesday, August 17, 2005 5:09 PM
> > To: Jetspeed Developers List
> > Subject: Re: j2:portal.genapp overwriting existing project.xml
> >
> > Scott T Weaver wrote:
> > > Is this supposed to happen? If so I really don't think this is such a
> > great
> > > idea as it destroys your existing portal project's descriptor. Are
> > their
> > > any work-arounds to fix this?
> > Scott,
> >
> > This is *not* supposed to happen. And I just tested it out again and
> can't
> > reproduce it here.
> > Very weird this can happen...
> >
> > The project.xml (and the other, inherited maven project files for that
> > matter) is created with
> > the j2:portal.conf.project goal (as invoked from j2:portal.genapp).
> > If you look at that goal, you'll see both project.xml and project-
> info.xml
> > are copied
> > using attribute overwrite="false".
> > So, if those files are not available they will be created but should
> > _never_ be updated. If that is
> > happening nonetheless, I guess something must be wrong with maven, ant
> or
> > the plugin itself...
> >
> >
> >
> > >
> > >
> > >
> > >
> > >
> > > Regards,
> > >
> > > -Scott
> > >
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
RE: j2:portal.genapp overwriting existing project.xml
Posted by Scott T Weaver <sc...@binary-designs.net>.
Hi Ate,
Now I can't either maybe I'm going crazy. Anyways, don't worry about it.
-Scott
> -----Original Message-----
> From: Ate Douma [mailto:ate@douma.nu]
> Sent: Wednesday, August 17, 2005 5:09 PM
> To: Jetspeed Developers List
> Subject: Re: j2:portal.genapp overwriting existing project.xml
>
> Scott T Weaver wrote:
> > Is this supposed to happen? If so I really don't think this is such a
> great
> > idea as it destroys your existing portal project's descriptor. Are
> their
> > any work-arounds to fix this?
> Scott,
>
> This is *not* supposed to happen. And I just tested it out again and can't
> reproduce it here.
> Very weird this can happen...
>
> The project.xml (and the other, inherited maven project files for that
> matter) is created with
> the j2:portal.conf.project goal (as invoked from j2:portal.genapp).
> If you look at that goal, you'll see both project.xml and project-info.xml
> are copied
> using attribute overwrite="false".
> So, if those files are not available they will be created but should
> _never_ be updated. If that is
> happening nonetheless, I guess something must be wrong with maven, ant or
> the plugin itself...
>
>
>
> >
> >
> >
> >
> >
> > Regards,
> >
> > -Scott
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: j2:portal.genapp overwriting existing project.xml
Posted by Ate Douma <at...@douma.nu>.
Scott T Weaver wrote:
> Is this supposed to happen? If so I really don't think this is such a great
> idea as it destroys your existing portal project's descriptor. Are their
> any work-arounds to fix this?
Scott,
This is *not* supposed to happen. And I just tested it out again and can't reproduce it here.
Very weird this can happen...
The project.xml (and the other, inherited maven project files for that matter) is created with
the j2:portal.conf.project goal (as invoked from j2:portal.genapp).
If you look at that goal, you'll see both project.xml and project-info.xml are copied
using attribute overwrite="false".
So, if those files are not available they will be created but should _never_ be updated. If that is
happening nonetheless, I guess something must be wrong with maven, ant or the plugin itself...
>
>
>
>
>
> Regards,
>
> -Scott
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org