[Building Sakai] tool version mismatch problem

[Steve Swinsburg]

Hi,

It's not really necessary, no. Some tools look at master/pom.xml to get the version of APIs etc, but AFAIK no other tool directly depends on Polls. The main reason it is there is to support the core-deploy pom which deploys binary versions of certain tools.

I have verified my assumption for you:

[swinsborg:~/dev/sakai/src/2.8.x]$ grep -r "sakai.polls.version" *
core-deploy/pom.xml:                    <version>${sakai.polls.version}</version>
master/pom.xml:				<sakai.polls.version>1.4.5</sakai.polls.version>
master/pom.xml:                		<version>${sakai.polls.version}</version>
was/ear/pom.xml:            		<version>${sakai.polls.version}</version>
[eyemac:~/dev/sakai/src/2.8.x]$  

So as you can see, the version is not used anywhere else (ignore 'was' since you are on Tomcat).

Since you are upgrading the version of a tool that is deployed via binary, you have two options:

1. Build your own version from source.

So that core-deploy doesn't keep deploying the old 1.4.5 version, edit the core-deploy pom to take out any references to the polls stuff. i.e. the bit in clean.targets and the dependency block. Then you can safely build and deploy whatever version you want.

2. Edit the master version and leave core-deploy to continue deploy binaries. 

This will NOT work for snapshots since they may not exist in the repository and may only work up until 2.9.x since the model may changing at some point in the future.

I recommend option 1.

Note that the same goes for any tool listed in the core-deploy pom, remove it from the pom, check for dependencies across the code base, then drop in the new the source.

cheers,
Steve



On 20/06/2013, at 3:52 PM, Sanghyun Jeon <euksa99 at gmail.com> wrote:

> My question is: Do the versions have to be the same between the tool's pom.xml and the master's pom.xml? And if they do need to match, then do I match the tool's to the master's or the master's to the tool's?
> In other words, I did as follows:
> master/pom.xml should be changed into:
> <sakai.resetpass.version>2.8.7-SNAPSHOT</sakai.resetpass.version>
> since tool's version is 2.8.7-SNAPSHOT
> Sometimes, I need to upgrade my tool, so that I need to change master's pom.xml for this purpose....
> However, I would like to have your confirmation....
> 
> S
> 
> 
> On Tue, Jun 18, 2013 at 2:03 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> Hi,
> 
> Which version of Sakai is this, the branch or a release like 2.8.3 for example?
> 
> Cheers,
> Steve
> 
> Sent from my iPad
> 
> On 18/06/2013, at 4:40, Sanghyun Jeon <euksa99 at gmail.com> wrote:
> 
> > Hello,
> >
> > There are some mismatch version problems I would like to resolve.
> >
> > for example,
> > master/pom.xml shows:
> > <sakai.resetpass.version>2.8.6</sakai.resetpass.version>
> >
> > However,
> > reset-password/pom.xml says:
> >        <parent>
> >                 <groupId>org.sakaiproject.purepoms</groupId>
> >         <artifactId>sakai-standard-tool</artifactId>
> >                 <version>2.8.6</version>
> >         </parent>
> >         <name>Reset Password and Account Validator</name>
> >         <groupId>org.sakaiproject.reset-pass</groupId>
> >         <artifactId>reset-pass</artifactId>
> >     <version>2.8.7-SNAPSHOT</version>
> >         <packaging>pom</packaging>
> >
> >
> > When I do maven build under base, tomcat/shared/lib has
> > sakai-reset-pass-help-2.8.6.jar
> >
> > However, when I do maven build under reset-password, because I modify some files under reset password folder, I got
> > sakai-reset-pass-help-2.8.7-SNAPSHOT.jar under tomcat/shared/lib
> >
> > I changed master/pom.xml into
> > <sakai.resetpass.version>2.8.7-SNAPSHOT</sakai.resetpass.version>
> > so that I don't have to build reset password separately.
> >
> > My question is
> > there are many similar version mismatch cases for sakai 2.8. Should I modify all of them based on each tool's pom.xml?
> >
> > S
> > _______________________________________________
> > sakai-dev mailing list
> > sakai-dev at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >
> > TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130620/4208e613/attachment.html