You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ron Wheeler <rw...@artifact-software.com> on 2010/11/05 12:56:24 UTC

Best Practice for using maven for web sites

Does anyone have any comments on using Maven to build static web sites.

The graphic artists building our web sites have created massive projects 
full of lots of small graphics projects with various versions of things.

It would seem reasonable to create small projects to create individual 
assets such as Flash animations, Photoshop collages, etc.
If these assets were held in repo with a version, at least we could find 
the "released" assets with a known version.

This would also fit with our Subversion structure a bit better.

The site would then need to be assembled.

Has anyone done this or, conversely, can think of reasons why this would 
be more trouble than it is worth.

Ron

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Best Practice for using maven for web sites

Posted by Dennis Lundberg <de...@apache.org>.
On 2010-11-05 12:56, Ron Wheeler wrote:
> Does anyone have any comments on using Maven to build static web sites.
> 
> The graphic artists building our web sites have created massive projects
> full of lots of small graphics projects with various versions of things.
> 
> It would seem reasonable to create small projects to create individual
> assets such as Flash animations, Photoshop collages, etc.
> If these assets were held in repo with a version, at least we could find
> the "released" assets with a known version.
> 
> This would also fit with our Subversion structure a bit better.
> 
> The site would then need to be assembled.
> 
> Has anyone done this or, conversely, can think of reasons why this would
> be more trouble than it is worth.

You can do that. Make sure that your site asset projects produces a zip
artifact. Then those zip artifacts can be unpacked during the pre-site
phase och the projects that depends of those assets.

> 
> Ron
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Best Practice for using maven for web sites

Posted by Antonio Petrelli <an...@gmail.com>.
2010/11/5 Ron Wheeler <rw...@artifact-software.com>:
>> Why can't you use a CMS?
>
> Not sure what you mean here.
> I need an environment that allows the creation of Flash animations using the
> Adobe tools, etc. which will create artifacts that can be assembled into a
> web site.

So use Adobe tools and a VCS.

> Currently we do this manually in a way that is unacceptably unstructured but
> does work.
>
> I am not sure where a CMs fits into the scheme.

I am not sure why you want to use Maven for this.
At least a CMS lets you publish your final content where you want.
What do you want Maven to do for you?

Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Best Practice for using maven for web sites

Posted by Justin Edelson <ju...@justinedelson.com>.

On 11/5/10 12:22 PM, "Ron Wheeler" <rw...@artifact-software.com> wrote:

>On 05/11/2010 8:07 AM, Antonio Petrelli wrote:
>> 2010/11/5 Ron Wheeler<rw...@artifact-software.com>:
>>> Does anyone have any comments on using Maven to build static web sites.
>>>
>>> The graphic artists building our web sites have created massive
>>>projects
>>> full of lots of small graphics projects with various versions of
>>>things.
>>>
>>> It would seem reasonable to create small projects to create individual
>>> assets such as Flash animations, Photoshop collages, etc.
>>> If these assets were held in repo with a version, at least we could
>>>find the
>>> "released" assets with a known version.
>> Why can't you use a CMS?
>Not sure what you mean here.
>I need an environment that allows the creation of Flash animations using
>the Adobe tools, etc. which will create artifacts that can be assembled
>into a web site.

Ron-
You should look at the flexmojos project for Flash/Flex specifically.
There are some JavaScript plugins as well.

I think you'll run into some cultural problems, but hopefully that won't
be the case for you.

Justin

>Currently we do this manually in a way that is unacceptably unstructured
>but does work.
>
>
>I am not sure where a CMs fits into the scheme.
>
>
>> Antonio
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Best Practice for using maven for web sites

Posted by Ron Wheeler <rw...@artifact-software.com>.
On 05/11/2010 8:07 AM, Antonio Petrelli wrote:
> 2010/11/5 Ron Wheeler<rw...@artifact-software.com>:
>> Does anyone have any comments on using Maven to build static web sites.
>>
>> The graphic artists building our web sites have created massive projects
>> full of lots of small graphics projects with various versions of things.
>>
>> It would seem reasonable to create small projects to create individual
>> assets such as Flash animations, Photoshop collages, etc.
>> If these assets were held in repo with a version, at least we could find the
>> "released" assets with a known version.
> Why can't you use a CMS?
Not sure what you mean here.
I need an environment that allows the creation of Flash animations using 
the Adobe tools, etc. which will create artifacts that can be assembled 
into a web site.
Currently we do this manually in a way that is unacceptably unstructured 
but does work.


I am not sure where a CMs fits into the scheme.


> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


RE: Best Practice for using maven for web sites

Posted by "Yanko, Curtis" <cu...@uhc.com>.
 
+1 ;-)

I can't tell you how many times we get teams trying to turn Subversion
and the build process into a CMS

________________________________

Curt Yanko | Continuous Integration Services | UnitedHealth Group IT 
Making IT Happen, one build at a time, 600 times a day

-----Original Message-----
From: Antonio Petrelli [mailto:antonio.petrelli@gmail.com] 
Sent: Friday, November 05, 2010 8:08 AM
To: Maven Users List
Subject: Re: Best Practice for using maven for web sites

2010/11/5 Ron Wheeler <rw...@artifact-software.com>:
> Does anyone have any comments on using Maven to build static web
sites.
>
> The graphic artists building our web sites have created massive 
> projects full of lots of small graphics projects with various versions
of things.
>
> It would seem reasonable to create small projects to create individual

> assets such as Flash animations, Photoshop collages, etc.
> If these assets were held in repo with a version, at least we could 
> find the "released" assets with a known version.

Why can't you use a CMS?

Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Best Practice for using maven for web sites

Posted by Antonio Petrelli <an...@gmail.com>.
2010/11/5 Ron Wheeler <rw...@artifact-software.com>:
> Does anyone have any comments on using Maven to build static web sites.
>
> The graphic artists building our web sites have created massive projects
> full of lots of small graphics projects with various versions of things.
>
> It would seem reasonable to create small projects to create individual
> assets such as Flash animations, Photoshop collages, etc.
> If these assets were held in repo with a version, at least we could find the
> "released" assets with a known version.

Why can't you use a CMS?

Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org