Dependency Versions - Makeover

Stefan Negrea snegrea at redhat.com
Thu Mar 21 21:40:14 UTC 2013


Hello Everybody, 

Just a follow up on the version changes. I created BZ 923458 [1] to keep track of the work and today I pushed the first set of changes to master branch. Please let me know if you see any problems or failures after this set of changes. I will wait for the build to stabilize and only then continue with a new set of changes in master.

During this exercise I came around a few submodules that are not built with the project. Can somebody tell me if the code is still needed or required? If not, we could purge it from the repository ahead of the github migration.
The submodules:
1) etc/augeas-utils
2) etc/apt
3) modules/helpers/inventory-serializer
4) modules/enterprise/server/plugins/alert-scriptlang
5) modules/enterprise/server/plugins/alert-sms
6) modules/enterprise/server/plugins/cloud
7) modules/plugins/ raw-config-test, onewire, lsof, jdbctrace, jira


I am not very concerned about the agent plugins since they could be picked up by the community for development again once we migrate to github. I am more concerned with the rest of unused submodules. So any history or details about them would be more than helpful. 


[1] https://bugzilla.redhat.com/show_bug.cgi?id=923458


Thank you,
Stefan Negrea

----- Original Message -----
> From: "Stefan Negrea" <snegrea at redhat.com>
> To: rhq-devel at lists.fedorahosted.org
> Sent: Monday, March 18, 2013 12:34:55 PM
> Subject: Re: Dependency Versions - Makeover
> 
> 
> 
> Thanks for all the feedback. I will move forward with the proposal
> below since it will make future dependency version
> maintenance/increments very easy. The proposal received no negative
> votes so far :)
> 
> 
> Thank you,
> Stefan Negrea
> 
> ----- Original Message -----
> > From: "Stefan Negrea" <snegrea at redhat.com>
> > To: rhq-devel at lists.fedorahosted.org
> > Sent: Friday, March 15, 2013 11:59:29 AM
> > Subject: Re: Dependency Versions - Makeover
> > 
> > So the plan would be:
> > 
> > 1) Properties with versions in root pom:
> > <jboss-jmx.version>4.2.3.GA</jboss-jmx.version>
> > 
> > 2) Root pom will have dependencies with versions in
> > dependencyManagement section:
> > <dependency>
> >   <groupId>jboss</groupId>
> >   <artifactId>jboss-jmx</artifactId>
> >   <version>${jboss-jmx.version}</version>
> > </dependency>
> > 
> > 3) Root pom will have plugins with versions in pluginManagement
> > section (build/pluginManagement):
> > <plugin>
> >   <groupId>org.codehaus.mojo</groupId>
> >   <artifactId>clirr-maven-plugin</artifactId>
> >   <version>${clirr.version}</version>
> > </plugin>
> > 
> > 4) All submodules would use plugins and dependencies without
> > version:
> > <dependency>
> >   <groupId>antlr</groupId>
> >   <artifactId>antlr</artifactId>
> >   <scope>provided</scope>
> > </dependency>
> > 
> > <plugin>
> >   <groupId>org.codehaus.mojo</groupId>
> >   <artifactId>clirr-maven-plugin</artifactId>
> >   ....
> > </plugin>
> > 
> > 
> > The versions to be extract in properties would be the full name of
> > the dependency/plugin + version. For example:
> > clirr-maven-plugin.version and not the current clirr.version.
> > 
> > I really like this because we will have a single pattern for
> > dependencies. Only one rule to follow.
> > 
> > 
> > 
> > Thank you,
> > Stefan Negrea
> > 
> > 
> > 
> > ----- Original Message -----
> > > From: "John Mazzitelli" <mazz at redhat.com>
> > > To: rhq-devel at lists.fedorahosted.org
> > > Sent: Friday, March 15, 2013 11:39:15 AM
> > > Subject: Re: Dependency Versions - Makeover
> > > 
> > > > So you would rather see all the dependencies declared in the
> > > > dependencyManagement section of the root pom of the project?
> > > > And
> > > > then apply the option 2 from below across all the sub-modules?
> > > > The
> > > > only concern that I have with this option is that we will have
> > > > a
> > > > huge!! section for dependency management. Aside from the huge
> > > > section in the root pom I think it is a cleaner approach.
> > > 
> > > I like the idea of having everything like this defined in one
> > > place
> > > (the root pom). If its large, so be it. The alternative is going
> > > through our large set of poms to adjust things that we need.
> > > _______________________________________________
> > > rhq-devel mailing list
> > > rhq-devel at lists.fedorahosted.org
> > > https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> > > 
> > _______________________________________________
> > rhq-devel mailing list
> > rhq-devel at lists.fedorahosted.org
> > https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> > 
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> 


More information about the rhq-devel mailing list