2008/3/6, Dennis Lundberg <[EMAIL PROTECTED]>: > Vincent Siveton wrote: > > Hi, > > > > 2008/3/6, Brett Porter <[EMAIL PROTECTED]>: > >> Just to understand - does that mean you're going to re-align the > >> versions and leave the JIRA project as one? > >> > > > > Nope. I proposed to create a new jira project for plugin tools (see > MPA-107). > > MPLUGIN will be for the Maven plugin. > > > Will MPLUGIN and plugin tools have different release cycles? If the > answer is no, then we don't need another JIRA project.
Like I said, maven-plugin-tools-javadoc is an independent tool so I guess the answer could be yes. But I am fine to align version and using using MPLUGIN. To be consistent, I think we could also align the goupId (see [1]). Cheers, Vincent [1] http://www.nabble.com/-Discuss--Review-plugin-tools-groupId-and-version-td15601645s177.html > > > > > Cheers, > > > > Vincent > > > >> (maybe the old versions in JIRA could signify which version of the > >> plugin and which of the tools like we did with surefire until the > >> versions were aligned) > >> > >> Thanks, > >> > >> Brett > >> > >> > >> On 07/03/2008, at 9:07 AM, Vincent Siveton wrote: > >> > >> > Thanks Brett. > >> > > >> > Vincent > >> > > >> > 2008/3/6, Brett Porter <[EMAIL PROTECTED]>: > >> >> > >> >> On 07/03/2008, at 3:29 AM, Benjamin Bentmann wrote: > >> >> > >> >>>> * maven-plugin-tools-api-2.2 > >> >>> > >> >>> According to JIRA, the maven-plugin-tools-api-2.2 was released > >> >>> 2006-12-29: > >> >>> > http://jira.codehaus.org/browse/MPLUGIN/component/13118?selected=com.atlassian.jira.plugin.system.project:component-changelog-panel > >> >>> > >> >>> Cleaning up JIRA to get in sync with the POMs and the actual > >> >>> contents of > >> >>> central would be good. > >> >> > >> >> > >> >> This was the reason why all the versions were aligned previously... I > >> >> consolidated the JIRA since it was expected they would all be > >> >> released > >> >> together. > >> >> > >> >> > >> >>> > >> >>> > >> >>>> * maven-plugin-plugin-2.4 > >> >>> > >> >>> Given the fact that the plugin's release cycle has obviously drifted > >> >>> away > >> >>> from the other plugin tools, it might be senseful to move this > >> >>> component > >> >>> into a dedicated JIRA project. > >> >>> > >> >>> > >> >>> Benjamin > >> >>> > >> >>> > >> >>> --------------------------------------------------------------------- > >> >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >>> For additional commands, e-mail: [EMAIL PROTECTED] > >> >>> > >> >> > >> >> > >> >> -- > >> >> Brett Porter > >> >> [EMAIL PROTECTED] > >> >> http://blogs.exist.com/bporter/ > >> >> > >> >> > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> >> For additional commands, e-mail: [EMAIL PROTECTED] > >> >> > >> >> > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > For additional commands, e-mail: [EMAIL PROTECTED] > >> > > >> > >> -- > >> Brett Porter > >> [EMAIL PROTECTED] > >> http://blogs.exist.com/bporter/ > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > > Dennis Lundberg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
