since mojo-keytool is alway used by keytool-maven-plugin, why not make it part of the plugin ( ie a parent with 2 project, component and plugin)? any changes in the component will likely trigger another release of plugin.
-D On Fri, Jan 27, 2012 at 7:02 AM, Stephen Connolly <[email protected]> wrote: > I think just create a home for it under sub-projects, and from there do > whatever you think will work > > > On 27 January 2012 14:28, Tony Chemit <[email protected]> wrote: >> >> On Fri, 27 Jan 2012 14:03:18 +0000 >> Stephen Connolly <[email protected]> wrote: >> >> > and mock-repository-manager too ;-) >> >> Yes but in my case this is a project with no maven plugin, but some >> compoments used by some others plugins. >> So I can't put this in an existing project. >> >> Do you think I could just do as a regular mojo project is that what you >> mean stephen ? >> >> The idea of this project was to be 'our' maven-share-components. >> >> > >> > On 27 January 2012 14:02, Stephen Connolly >> > <[email protected]>wrote: >> > >> > > I would just copy what has been done for animal-sniffer and extra >> > > enforcer rules >> > > >> > > >> > > On 27 January 2012 13:49, Tony Chemit <[email protected]> wrote: >> > > >> > >> Hi guys, >> > >> >> > >> I'd like to do soon a release of the keytool-m-p and webstart-m-p >> > >> which need a release of the mojo-keytool. >> > >> >> > >> As the mojo-keytool is part of a new project named >> > >> mojo-shared-components [1], I'd like we discuss how to do a first >> > >> (alpha-1 or beta-1) release of this project. >> > >> >> > >> For the moment the project organisation is like this : >> > >> >> > >> >> > >> sandbox/mojo-shared-components >> > >> ├── mojo-keytool (2) >> > >> ├── mojo-shared-components (1) >> > >> └── pom.xml (0) >> > >> >> > >> where (0) is org.codehaus.mojo.shared:mojo-shared-aggregator >> > >> (1) is org.codehaus.mojo.shared:mojo-shared-components >> > >> (2) is org.codehaus.mojo.shared:mojo-keytool >> > >> >> > >> (0) is the aggreator pom for any sub project >> > >> (1) is the share-components parent pom >> > >> (2) is the first real component of the project >> > >> >> > >> Is that seem ok with you ? >> > >> >> > >> About the site, how could we organize it, Should we have a >> > >> common page for the project (a static site) and then for all real >> > >> components (like mojo-keytool) a real generated site. >> > >> >> > >> Any help or idea to realize this is welcome ;) >> > >> >> > >> >> > >> thanks, >> > >> >> > >> tony. >> > >> >> > >> [1] >> > >> https://svn.codehaus.org/mojo/trunk/sandbox/mojo-shared-components >> > >> >> > >> >> > >> ----- >> > >> Tony Chemit >> > >> -------------------- >> > >> tél: +33 (0) 2 40 50 29 28 >> > >> email: [email protected] >> > >> http://www.codelutin.com >> > >> >> > >> --------------------------------------------------------------------- >> > >> To unsubscribe from this list, please visit: >> > >> >> > >> http://xircles.codehaus.org/manage_email >> > >> >> > >> >> > >> >> > > >> >> >> >> -- >> Tony Chemit >> -------------------- >> tél: +33 (0) 2 40 50 29 28 >> email: [email protected] >> http://www.codelutin.com >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
