Re: Maven Site Skinning
Dennis: Yes, you have got this exactly right. I have a skin packaged in a jar and a custom plugin that contains the custom logo creation goal. I create the logo using the plugin at pre-site and reference the skin in my parent pom's site.xml which refers to the generated logo. Thank you for confirming that what I have already done is in fact correct. I was thinking that the mojo should be part of the skin package because the skin and the logo are both related to the look n feel of the project site. The more I think about it the more I agree with you that they should indeed remain seperate. Thanks again for the input. It's greatly appreciated! On Tue, Apr 21, 2009 at 2:43 PM, Dennis Lundberg wrote: > Ryan Connolly wrote: >> Hello: >> I am creating a site skin for my company's project sites and have >> written a MOJO that will generate the site logo based on the project >> name that runs at the pre-site lifecycle phase. My question is this: >> Could my plugin goal somehow be packaged along with the skin so that >> it can be called automatically for any project that uses this skin? >> Currently I have the skin in one project and the single mojo plug-in >> in another project. My hopes are to have them somehow combined as to >> not have to maintain 2 projects that are essentially part of the same >> 'project'. > > If I understand your setup correctly, you should not integrate your > plugin into the skin. Instead you should keep them separate as they do > different things. > > The skin is a bunch of files that defines the look and feel of your > site, packaged together in a jar-file. These files can include a logo, > or in your case you can leave that out of your skin. Just reference the > not-yet-existing logo in your style sheets. > > Then you can have project X, a project that wants your skin and a custom > generated logo. That project will reference your skin in its site.xml. > That project will also include an execution of your logo mojo in its > pom.xml, that will create the logo that is referenced in your skin. Just > make sure that the logo mojo outputs the logo into the correct directory > used for site resources, /src/site/resources/... by default. > >> >> Any help and/or suggestions would be greatly appreciated. >> >> Thanks, >> -Ryan >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- �...@n - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Skinning
Ryan Connolly wrote: > Hello: > I am creating a site skin for my company's project sites and have > written a MOJO that will generate the site logo based on the project > name that runs at the pre-site lifecycle phase. My question is this: > Could my plugin goal somehow be packaged along with the skin so that > it can be called automatically for any project that uses this skin? > Currently I have the skin in one project and the single mojo plug-in > in another project. My hopes are to have them somehow combined as to > not have to maintain 2 projects that are essentially part of the same > 'project'. If I understand your setup correctly, you should not integrate your plugin into the skin. Instead you should keep them separate as they do different things. The skin is a bunch of files that defines the look and feel of your site, packaged together in a jar-file. These files can include a logo, or in your case you can leave that out of your skin. Just reference the not-yet-existing logo in your style sheets. Then you can have project X, a project that wants your skin and a custom generated logo. That project will reference your skin in its site.xml. That project will also include an execution of your logo mojo in its pom.xml, that will create the logo that is referenced in your skin. Just make sure that the logo mojo outputs the logo into the correct directory used for site resources, /src/site/resources/... by default. > > Any help and/or suggestions would be greatly appreciated. > > Thanks, > -Ryan > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Skinning
Hi Jesse: I'm not familiar with ImageMagick... I'm acheiving simple logo creation using Java 2d as I didn't want users to have to have imaging apps installed to run the build. I would love to see what you come up with should you pursue that route would love to know if you can come up with a way for a skin project to include a mojo instead of having to maintain them seperately! On Tue, Apr 21, 2009 at 11:35 AM, wrote: > Hi Ryan, > > On Tue, Apr 21, 2009 at 11:31 AM, Ryan Connolly wrote: >> Jesse: >> >> I would be glad to, however, I feel it still needs some tweaking >> to allow for user configuration... > > I was going to do a project just like this, and incorporate > ImageMagick. My first thought was just to have an open ended parameter > that would be options to pass to ImageMagick. By default the Mojo > would use the project.name as the text, but this would be overridable. > > -jesse > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- �...@n - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Skinning
Hi Ryan, On Tue, Apr 21, 2009 at 11:31 AM, Ryan Connolly wrote: > Jesse: > > I would be glad to, however, I feel it still needs some tweaking > to allow for user configuration... I was going to do a project just like this, and incorporate ImageMagick. My first thought was just to have an open ended parameter that would be options to pass to ImageMagick. By default the Mojo would use the project.name as the text, but this would be overridable. -jesse - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Skinning
Jesse: I would be glad to, however, I feel it still needs some tweaking to allow for user configuration... I'm working on adding color, gradient, background configurations to allow this to work well with other skins/color/style schemes as it currently generates a logo that fits in with the skin I am developing for our company projects. Please let me know what would interest you in regards to project logo generation and I would be glad to look into incorporating your requests. Thanks! On Tue, Apr 21, 2009 at 11:05 AM, wrote: > Hello Ryan, > > On Tue, Apr 21, 2009 at 10:05 AM, Ryan Connolly wrote: >> Hello: >> I am creating a site skin for my company's project sites and have >> written a MOJO that will generate the site logo based on the project >> name that runs at the pre-site lifecycle phase. > > Any chance you can release this Mojo? :-) > > -jesse > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- �...@n - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Site Skinning
Hello Ryan, On Tue, Apr 21, 2009 at 10:05 AM, Ryan Connolly wrote: > Hello: > I am creating a site skin for my company's project sites and have > written a MOJO that will generate the site logo based on the project > name that runs at the pre-site lifecycle phase. Any chance you can release this Mojo? :-) -jesse - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Site Skinning
Hello: I am creating a site skin for my company's project sites and have written a MOJO that will generate the site logo based on the project name that runs at the pre-site lifecycle phase. My question is this: Could my plugin goal somehow be packaged along with the skin so that it can be called automatically for any project that uses this skin? Currently I have the skin in one project and the single mojo plug-in in another project. My hopes are to have them somehow combined as to not have to maintain 2 projects that are essentially part of the same 'project'. Any help and/or suggestions would be greatly appreciated. Thanks, -Ryan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
