You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David H. DeWolf" <dd...@apache.org> on 2004/04/02 05:36:46 UTC
pluto-api-1.0.1 ???
The recent changes to the dependencies that increased the portlet-api
dependency version to 1.0.1 seem strange to me. I'm curious why we're
updating the portlet-api version when nothing has changed? Additionally,
I'm not sure we should update the version of portlet-api when it is
actually a specification that we don't directly control.
I realize that these changes were a result of an issue that was
reported, but I wonder if the correct fix was instead to revert the
portlet-api "sub-project" version to 1.0 (while maintaining the
increased version for pluto and it's other subprojects).
If we do decide that the portlet-api version should be incremented as
well - we need to get the 1.0.1 jar published to ibiblio so that people
doing using pluto for the first time don't have their builds break.
David
RE: pluto-api-1.0.1 ???
Posted by Xavier Saint-Denis <xs...@free.fr>.
I'm a little bit confused to have introduced the modification regarding the
portlet-api version in the differents project.xml
Sorry
Xavier
-----Message d'origine-----
De : Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
Envoyé : vendredi 2 avril 2004 16:09
À : pluto-dev@jakarta.apache.org
Objet : RE: pluto-api-1.0.1 ???
David H. DeWolf wrote:
>
> I'm sorry! It would help if I looked at the updated version
> instead of a stale on! My bad.
>
No problem :)
Carsten
RE: pluto-api-1.0.1 ???
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
David H. DeWolf wrote:
>
> I'm sorry! It would help if I looked at the updated version
> instead of a stale on! My bad.
>
No problem :)
Carsten
Re: pluto-api-1.0.1 ???
Posted by "David H. DeWolf" <dd...@apache.org>.
Carsten Ziegeler wrote:
> David H. DeWolf wrote:
>
>>Thanks Carsten!
>>
>>I noticed that you updated the dependency versions but not
>>the portlet-api subproject pom (we should be able to override
>>just that subproject's currentVersion and not effect the
>>others). Was this an oversight?
>
> I changed this as well: I set the currentVersion to 1.0 for the api.
> It's in the api/project.xml. Or do you mean something different?
I'm sorry! It would help if I looked at the updated version instead of a
stale on! My bad.
>
>
>>Or do you think that the api
>>should maintain the version that coresponds to the rest of pluto?
>
> No, I agree 1.0 is better.
>
>
>>I do remember the discussion in which we decided to keep all
>>the versions the same - but I'm wondering now if we weren't
>>thinking about the ramifications of updating the portlet-api
>>version at that time.
>
> Yes, I thought the same :) but I agree that 1.0 for the api is better.
>
> Carsten
>
>
>>Thanks for clarifying for me!
>>
>>David
>>
>>Carsten Ziegeler wrote:
>>
>>>I just reverted to version 1.0 for the portlet-api.
>>>Sorry for the confusion.
>>>
>>>Carsten
>>>
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>>>>Sent: Friday, April 02, 2004 8:34 AM
>>>>To: pluto-dev@jakarta.apache.org
>>>>Subject: RE: pluto-api-1.0.1 ???
>>>>
>>>>Good question :)
>>>>
>>>>I thought we said a time ago that all sub projects of pluto
>>
>>have the
>>
>>>>same version number. That's why I changed it to
>>>>1.0.1 for everything we have including the portlet-api.
>>>>Now, I agree that this might not make sense as we don't
>>
>>change the api
>>
>>>>at all.
>>>>
>>>>So, if noone is against it, I will revert the changes and use the
>>>>fixed version 1.0 for the portlet-api and 1.0.1 for the rest of the
>>>>project.
>>>>
>>>>Thanks
>>>>Carsten
>>>>
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>From: David H. DeWolf [mailto:ddewolf@apache.org]
>>>>>Sent: Friday, April 02, 2004 5:37 AM
>>>>>To: pluto dev
>>>>>Subject: pluto-api-1.0.1 ???
>>>>>
>>>>>The recent changes to the dependencies that increased the
>>>>
>>>>portlet-api
>>>>
>>>>
>>>>>dependency version to 1.0.1 seem strange to me.
>>>>>I'm curious why we're updating the portlet-api version
>>
>>when nothing
>>
>>>>>has changed? Additionally, I'm not sure we should update
>>>>
>>>>the version
>>>>
>>>>
>>>>>of portlet-api when it is actually a specification that we don't
>>>>>directly control.
>>>>>
>>>>>I realize that these changes were a result of an issue that was
>>>>>reported, but I wonder if the correct fix was instead to
>>
>>revert the
>>
>>>>>portlet-api "sub-project" version to 1.0 (while maintaining the
>>>>>increased version for pluto and it's other subprojects).
>>>>>
>>>>>If we do decide that the portlet-api version should be
>>>>
>>>>incremented as
>>>>
>>>>
>>>>>well - we need to get the 1.0.1 jar published to ibiblio so that
>>>>>people doing using pluto for the first time don't have
>>
>>their builds
>>
>>>>>break.
>>>>>
>>>>>David
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
RE: pluto-api-1.0.1 ???
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
David H. DeWolf wrote:
>
> Thanks Carsten!
>
> I noticed that you updated the dependency versions but not
> the portlet-api subproject pom (we should be able to override
> just that subproject's currentVersion and not effect the
> others). Was this an oversight?
I changed this as well: I set the currentVersion to 1.0 for the api.
It's in the api/project.xml. Or do you mean something different?
> Or do you think that the api
> should maintain the version that coresponds to the rest of pluto?
No, I agree 1.0 is better.
>
> I do remember the discussion in which we decided to keep all
> the versions the same - but I'm wondering now if we weren't
> thinking about the ramifications of updating the portlet-api
> version at that time.
Yes, I thought the same :) but I agree that 1.0 for the api is better.
Carsten
>
> Thanks for clarifying for me!
>
> David
>
> Carsten Ziegeler wrote:
> > I just reverted to version 1.0 for the portlet-api.
> > Sorry for the confusion.
> >
> > Carsten
> >
> >
> >
> >>-----Original Message-----
> >>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> >>Sent: Friday, April 02, 2004 8:34 AM
> >>To: pluto-dev@jakarta.apache.org
> >>Subject: RE: pluto-api-1.0.1 ???
> >>
> >>Good question :)
> >>
> >>I thought we said a time ago that all sub projects of pluto
> have the
> >>same version number. That's why I changed it to
> >>1.0.1 for everything we have including the portlet-api.
> >>Now, I agree that this might not make sense as we don't
> change the api
> >>at all.
> >>
> >>So, if noone is against it, I will revert the changes and use the
> >>fixed version 1.0 for the portlet-api and 1.0.1 for the rest of the
> >>project.
> >>
> >>Thanks
> >>Carsten
> >>
> >>
> >>>-----Original Message-----
> >>>From: David H. DeWolf [mailto:ddewolf@apache.org]
> >>>Sent: Friday, April 02, 2004 5:37 AM
> >>>To: pluto dev
> >>>Subject: pluto-api-1.0.1 ???
> >>>
> >>>The recent changes to the dependencies that increased the
> >>
> >>portlet-api
> >>
> >>>dependency version to 1.0.1 seem strange to me.
> >>>I'm curious why we're updating the portlet-api version
> when nothing
> >>>has changed? Additionally, I'm not sure we should update
> >>
> >>the version
> >>
> >>>of portlet-api when it is actually a specification that we don't
> >>>directly control.
> >>>
> >>>I realize that these changes were a result of an issue that was
> >>>reported, but I wonder if the correct fix was instead to
> revert the
> >>>portlet-api "sub-project" version to 1.0 (while maintaining the
> >>>increased version for pluto and it's other subprojects).
> >>>
> >>>If we do decide that the portlet-api version should be
> >>
> >>incremented as
> >>
> >>>well - we need to get the 1.0.1 jar published to ibiblio so that
> >>>people doing using pluto for the first time don't have
> their builds
> >>>break.
> >>>
> >>>David
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>
Re: pluto-api-1.0.1 ???
Posted by "David H. DeWolf" <dd...@apache.org>.
Thanks Carsten!
I noticed that you updated the dependency versions but not the
portlet-api subproject pom (we should be able to override just that
subproject's currentVersion and not effect the others). Was this an
oversight? Or do you think that the api should maintain the version that
coresponds to the rest of pluto?
I do remember the discussion in which we decided to keep all the
versions the same - but I'm wondering now if we weren't thinking about
the ramifications of updating the portlet-api version at that time.
Thanks for clarifying for me!
David
Carsten Ziegeler wrote:
> I just reverted to version 1.0 for the portlet-api.
> Sorry for the confusion.
>
> Carsten
>
>
>
>>-----Original Message-----
>>From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
>>Sent: Friday, April 02, 2004 8:34 AM
>>To: pluto-dev@jakarta.apache.org
>>Subject: RE: pluto-api-1.0.1 ???
>>
>>Good question :)
>>
>>I thought we said a time ago that all sub projects of pluto
>>have the same version number. That's why I changed it to
>>1.0.1 for everything we have including the portlet-api.
>>Now, I agree that this might not make sense as we don't
>>change the api at all.
>>
>>So, if noone is against it, I will revert the changes and use
>>the fixed version 1.0 for the portlet-api and 1.0.1 for the
>>rest of the project.
>>
>>Thanks
>>Carsten
>>
>>
>>>-----Original Message-----
>>>From: David H. DeWolf [mailto:ddewolf@apache.org]
>>>Sent: Friday, April 02, 2004 5:37 AM
>>>To: pluto dev
>>>Subject: pluto-api-1.0.1 ???
>>>
>>>The recent changes to the dependencies that increased the
>>
>>portlet-api
>>
>>>dependency version to 1.0.1 seem strange to me.
>>>I'm curious why we're updating the portlet-api version when nothing
>>>has changed? Additionally, I'm not sure we should update
>>
>>the version
>>
>>>of portlet-api when it is actually a specification that we don't
>>>directly control.
>>>
>>>I realize that these changes were a result of an issue that was
>>>reported, but I wonder if the correct fix was instead to revert the
>>>portlet-api "sub-project" version to 1.0 (while maintaining the
>>>increased version for pluto and it's other subprojects).
>>>
>>>If we do decide that the portlet-api version should be
>>
>>incremented as
>>
>>>well - we need to get the 1.0.1 jar published to ibiblio so that
>>>people doing using pluto for the first time don't have their builds
>>>break.
>>>
>>>David
>>>
>>>
>>
>>
>
>
RE: pluto-api-1.0.1 ???
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
I just reverted to version 1.0 for the portlet-api.
Sorry for the confusion.
Carsten
> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> Sent: Friday, April 02, 2004 8:34 AM
> To: pluto-dev@jakarta.apache.org
> Subject: RE: pluto-api-1.0.1 ???
>
> Good question :)
>
> I thought we said a time ago that all sub projects of pluto
> have the same version number. That's why I changed it to
> 1.0.1 for everything we have including the portlet-api.
> Now, I agree that this might not make sense as we don't
> change the api at all.
>
> So, if noone is against it, I will revert the changes and use
> the fixed version 1.0 for the portlet-api and 1.0.1 for the
> rest of the project.
>
> Thanks
> Carsten
>
> > -----Original Message-----
> > From: David H. DeWolf [mailto:ddewolf@apache.org]
> > Sent: Friday, April 02, 2004 5:37 AM
> > To: pluto dev
> > Subject: pluto-api-1.0.1 ???
> >
> > The recent changes to the dependencies that increased the
> portlet-api
> > dependency version to 1.0.1 seem strange to me.
> > I'm curious why we're updating the portlet-api version when nothing
> > has changed? Additionally, I'm not sure we should update
> the version
> > of portlet-api when it is actually a specification that we don't
> > directly control.
> >
> > I realize that these changes were a result of an issue that was
> > reported, but I wonder if the correct fix was instead to revert the
> > portlet-api "sub-project" version to 1.0 (while maintaining the
> > increased version for pluto and it's other subprojects).
> >
> > If we do decide that the portlet-api version should be
> incremented as
> > well - we need to get the 1.0.1 jar published to ibiblio so that
> > people doing using pluto for the first time don't have their builds
> > break.
> >
> > David
> >
> >
>
>
RE: pluto-api-1.0.1 ???
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Good question :)
I thought we said a time ago that all sub projects of pluto have
the same version number. That's why I changed it to 1.0.1 for
everything we have including the portlet-api.
Now, I agree that this might not make sense as we don't change
the api at all.
So, if noone is against it, I will revert the changes and use
the fixed version 1.0 for the portlet-api and 1.0.1 for the
rest of the project.
Thanks
Carsten
> -----Original Message-----
> From: David H. DeWolf [mailto:ddewolf@apache.org]
> Sent: Friday, April 02, 2004 5:37 AM
> To: pluto dev
> Subject: pluto-api-1.0.1 ???
>
> The recent changes to the dependencies that increased the
> portlet-api dependency version to 1.0.1 seem strange to me.
> I'm curious why we're updating the portlet-api version when
> nothing has changed? Additionally, I'm not sure we should
> update the version of portlet-api when it is actually a
> specification that we don't directly control.
>
> I realize that these changes were a result of an issue that
> was reported, but I wonder if the correct fix was instead to
> revert the portlet-api "sub-project" version to 1.0 (while
> maintaining the increased version for pluto and it's other
> subprojects).
>
> If we do decide that the portlet-api version should be
> incremented as well - we need to get the 1.0.1 jar published
> to ibiblio so that people doing using pluto for the first
> time don't have their builds break.
>
> David
>
>