Actually, I was hoping you had some suggestions, as we haven't entirely
nailed down our strategy either.  :)  Guess we'll keep it tabled for now
and stick with the default minification, but I'll let you know if we
come up with anything clever.  What does your plugin configuration look
like?  Here's what we're using (it's defined in a separate build profile
in the uportal-war/pom.xml):

 

<profile>

   <id>minify</id>

   <activation>

      <property>

         <name>minify</name>

      </property>

   </activation>

   <build>

      <plugins>

         <plugin>

            <groupId>net.sf.alchim</groupId>

            <artifactId>yuicompressor-maven-plugin</artifactId>

            <executions>

               <execution>

                  <goals>

                     <goal>compress</goal>

                  </goals>

               </execution>

            </executions>   

            <configuration>

               <nosuffix>true</nosuffix>

               <jswarn>false</jswarn>

               <preserveStringLiterals>true</preserveStringLiterals>

               <preserveAllSemiColons>true</preserveAllSemiColons>

               <nomunge>true</nomunge>

               <failOnWarning>false</failOnWarning>

 
<sourceDirectory>${basedir}/src/main/webapp/media</sourceDirectory>

 
<outputDirectory>${project.build.directory}/compressed/media</outputDire
ctory>

            </configuration>

         </plugin>

         <plugin>

            <groupId>org.apache.maven.plugins</groupId>

            <artifactId>maven-war-plugin</artifactId>

            <version>2.1-alpha-1</version>

            <configuration>

               <webResources>

                  <resource>

                     <directory>target/compressed</directory>

                     <includes>

                        <include>**/*.js</include>

                        <include>**/*.css</include>

                     </includes>

                  </resource>

               </webResources>

            </configuration>

         </plugin>

      </plugins>

   </build>

</profile>

 

--Chris

 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jen Bourey
Sent: Tuesday, October 07, 2008 9:43 PM
To: [email protected]
Subject: Re: [uportal-dev] Javascript performance issues

 

Hi Chris,

So far, I haven't used the aggregation options.  Last time we went over
these issues, we'd talked about naming files such that they could have a
long-term cache header applied to them.  I haven't thought of a good way
to combine that goal with aggregating files in the build, although I'm
certainly open to any suggestions.

- Jen



On Mon, Oct 6, 2008 at 6:31 AM, Christopher Doyle <[EMAIL PROTECTED]>
wrote:

Great news about the Fluid Reorderer, Jen!  We are using the yui
compressor plugin at Hopkins, and that's definitely something we'd like
to see added back into the project.  There's already a JIRA ticket for
it, too - UP-2159.  Did you use the aggregation options at all?

 

--Chris

 

 

-- 




You are currently subscribed to [email protected] as:
[EMAIL PROTECTED]

To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

-- 
You are currently subscribed to [email protected] as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

Reply via email to