Apache (; ) is the collective term for several culturally related groups of Native Americans in the United States originally from the Southwest United States. [http://en.wikipedia.org/wiki/Apache]
Ive look in Google (Google is Your best friend), and found that this issue is quite common...
Workaround:
Try to download my components with either Firefox (Linux, Windows) or Opera(Linux, Windows), or Safari (MAC) or Konqueror (Linux) it will work.
One more time, Internet Explorer do not correctly handle gzip response. IE has bugs (gee, what a surprise) that make it ignore compression on certain types. So that zip file you got is actually just a .zip in a .gz file, if you gunzip it first it becomes a valid zip.
I've correct the issue by avoiding compression on all response content, correct a misconfiguration in the browser pattern recognition I've also update the article: mod_deflate accordingly
Happy downloading!
I found this time a new way to deploy Maven artefacts using the Oracle Weblogic Ant API!
If you remember my previous post, there is many ways to deploy your war/ear to Oracle Weblogic
And now using the official ANT API of Oracle, by far the MOST stable of all!
Read more: Auto deployment of Maven artifacts to Oracle Weblogic
![]()
Got this email from Cyprian Sniegota, he did develop a Maven Archetype for easing development of Joomla extensions. His archetype currently support the creation of a skeleton for components, modules, plugins and templates.
I noticed some time ago that you described combination of Joomla! and Maven. Few weeks ago i wrote joomla-maven-plugin with skeleton projects (sources: bitbucket.org/deviapps) based on php-maven.org work.
Here is short description http://deviapps.com/create-joomla-extension-with-maven and 5 min video (in Polish so far) http://www.youtube.com/watch?v=aE8w9EZciTg
I hope you will be interested.
Thanks to him for having written this project. I will also try to Maven-ize what Joomla has done with Ant in the future (I prefer now crystal clear software lifecycle )

I was getting mad because jetty was refusing to redeploy my static files (xhtml, css) in Eclipse until I find the reason
The Jetty Web Server provides a HTTP server and Servlet container capable of serving static and dynamic contend either from a standalone or embedded instantiations.
Jetty buffers static content for webapps such as html files, css files, images etc and uses memory mapped files to do this if the NIO connectors are being used. The problem is that on Windows, memory mapping a file causes the file to be locked, so that the file cannot be updated or replaced. This means that effectively you have to stop Jetty in order to update a file.
To fix this, add a line with
org.mortbay.jetty maven-jetty-plugin 6.1.5 ... src/main/resources/webdefault.xml
The default webdefault.xml file is found in the lib/jetty.jar at org/mortbay/jetty/webapp/webdefault.xml. Extract it to a convenient disk location and edit it to change useFileMappedBuffer to false:
useFileMappedBuffer false
Copy the changed file into src/main/resources/ of your project.
The problem is explained more in Jetty's documentation.
I was fighting today against the maven-release-plugin of maven, solving complicated errors in a row. As I am convince I made all possible errors, I think it is worse to compile my findings here to help others :-)
This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform.
My approach to speed up things is always to define a small project (in a sandbox SVN root) that is compiling and running in 10 seconds to make some test before trying to make it run on our bigger Innoveo Skye(tm) product (35 modules)
I always have 2 projects prepared:
For the reader that can not wait here is the running command line from TeamCity to be put in Build Runner Goals
release:clean release:prepare release:perform -Dusername=xxxxxxx -Dpassword=yyyyyy
Read more: I was fighting today against Apache Maven release plugin with multi modules projects
In this small post I will show you how to deploy automatically some artifacts of your build into
Weblogic 10.3 by using the weblogic-maven-plugin
This plugin will support various tasks within the Weblogic 8.1 and 9.x environment. Such tasks as deploy, undeploy,clientgen,servicegen, and appc are supported as well as many others. The plugin uses exposed API's that are subject to change but have been tested in 8.1 SP 4-6 and 9.0 - 9.2 MP3. There are two versions of the plugin to support the two environments based on differences in the JDK. The 9.x version is currently being refactored to support the standard JSR supported deployment interface
Read more: Apache Maven BEA Weblogic 10.3 remote deployment
Continuous build with Apache Maven
- Details
- Category: Apache Maven
- Published on Thursday, 10 April 2008 00:00
- Written by Administrator
- Hits: 7381
Maven is a software tool for Java project management and build automation created by Jason van Zyl in 2002. It is similar in functionality to the Apache Ant tool (and to a lesser extent, PHP's PEAR and Perl's CPAN), but has a simpler build configuration model, based on an XML format. Maven is hosted by the Apache Software Foundation, where it was formerly part of the Jakarta Project.
Maven uses a construct known as a Project Object Model (POM) to describe the software project
being built, its dependencies on other external modules and components, and the build order.
It comes with pre-defined targets for performing certain well defined tasks such as compilation
of code and its packaging.A key feature of Maven is that it is network-ready. The core engine can dynamically download
plug-ins from a repository, the same repository that provides access to many versions of different
Open Source Java projects, from Apache and other organizations and developers. This repository
and its reorganized successor, the Maven 2 repository, strives to be the de facto distribution
mechanism for Java applications, but its adoption has been slow. Maven provides built in support
not just for retrieving files from this repository, but to upload artifacts at the end of the build.
A local cache of downloaded artifacts acts as the primary means of synchronizing the output of
projects on a local system.Maven is based on a plugin-based architecture that allows it to make use of any application
controllable through standard input. Theoretically, this would allow anyone to write plugins to
interface with build tools (compilers, unit test tools, etc.) for any other language. from WikiPediaIntroduction to m2eclipse
- Details
- Category: Apache Maven
- Published on Wednesday, 06 May 2009 00:00
- Written by Administrator
- Hits: 7598
The Eclipse IDE is the most widely used IDE for Java development today. At the same time, Apache Maven continues to mature, and has grown to be the industry standard for creating extensible and reliable enterprise builds. While it is certainly possible to develop applications in Eclipse and use Maven as a command-line build tool, most developers expect the IDE to know how to invoke and interact with the build tool they are using.
Enter m2eclipse. The m2eclipse project provides support for Maven within the Eclipse IDE. It is a plugin which helps bridge the gaps between Maven and Eclipse. Using m2eclipse you can develop a large multi-module project with nested Maven modules and have this hierarchical structure reflected in your Eclipse IDE. Using m2eclipse, you can launch and manage your project's Maven build using editors, and your IDE will become aware of both the local and remote Maven repositories allowing you to quickly search for and locate any artifact made available in the Maven repository. m2eclipse will also change the way you create projects with a novel and easy-to-use interface for creating projects from Maven Archetypes.
In this article, we will explore the features m2eclipse provides and help you start using an Eclipse plugin which provides real Maven integration for the best IDE platform available. After reading this article you should have enough information to install the m2eclipse plugin and start creating or importing existing Maven projects into your Eclipse workspace. You will also have an idea of some of the features provided the plugin. read more at ServerSide
M2Eclipse Maven FAQ
- Details
- Category: Apache Maven
- Published on Friday, 17 July 2009 00:00
- Written by Administrator
- Hits: 10384
These things have disturbed us (The developer Team at Innoveo.com) a lot in the past months. We did solve them recently, and I would like to publish them now here to help more people
Someone create a new maven module, after updating from SVN the module is not visible as a separate project.
Scenario:
- User A checks out a maven project from SVN using "Checkout as Maven Project". All modules are now listed as separate projects in Eclipse
- User B creates a new module in the project, and checks it into SVN
- User A updates project
- New module does not show up as a separate project.
Solution:
- Work around found by selecting the parent project
- Do Import -> Maven.
- Select then the same name template and most modules should be grayed out because of name conflicts. But you should see the missing module in the list
- Tick the one (new) module and import it.
In SVN perspective, when I choose "Checkout as Maven Project" on maven projectA, I get an exception saying that maven.123457896 can not be renamed
Scenario:
This error occur sometime, especially if you ever kill eclipse during a previous maven checkout (as sometimes it seems to hang forever). In fact the error message can be misleading,as M2Eclipse can not renamed maven.1234567896 to projectA as it may partially exist on disk.
Solution:
- Stop eclipse
- Go to the workspace location {workpsace_loc}
- Delete the directory maven.1234567896 or any directory starting with maven.xxxxxxxx
- Delete also the temporary created Maven project {workpsace_loc}\projectA directory you were trying to checkout if it exist.
- Restart eclipse, and in SVN perspective, on maven project A, retry and select "Checkout as maven project"
.classpath or .project are not committed in SVN, how to add them?
Scenario:
You may have add a svn:ignore on some directories, or some someone may have committed a recursive svn:ignore properties on some module in the hierarchy. While we should never commit any .classpath to SVN, there is some rare case where it is still needed. For example if you ever add special runtime server libraries that may not be coming from Maven Dependencies.
Solution:
Even if there is a svn:ignore on a maven module, or if a module has applied svn:ignore properties to all its child, you can always put a file under version control by doing the following
- Go in SVN perspective
- Drill down to the Maven module location or directory in which you would like to add a file
- Right click New... then choose File,
- A pop up will open letting you choose a file on disk
- Don’t forget to Enter a commit comment
Maven Surefire runs multiple times our test case when using goal site
This is neither a bug or an issue of Maven, it look like even to be a feature!
Some reporting plugin are modifying (instrumentation) the java byte code of test cases like with Cobertura (goal: cobertura:cobertura).
The Cobertura tool is a free and easy to use source code test coverage analyses. It helps you to discover where your source-code lacks in test coverage.
In some rare case scenario (multi threaded test cases for example), it may be worth to run the code twice as instrumentation may modify behaviors and outcome of tests. So to resume, maven Surefire run them once, then Cobertura one more time but instrumented. One solution among other to escape this is to use Maven profiles, and to rely on another build that do not use reporting to run tests without instrumentation.
More to come ..
Maven dependencies graph plugin in TeamCity and Eclipse
- Details
- Category: Apache Maven
- Published on Thursday, 27 August 2009 00:00
- Written by Administrator
- Hits: 11931
How to add dependencies graph to multi module projects. With this Maven plugin, you’ll be able to visualize Maven modules interdependencies and dependencies in any scope (compile, text, provided, system, runtime)
depgraph:depgraph Can be used to draw a dependency graph from the project, the mojo is executed in. It traverses all dependencies and creates a graph using Graphviz. It draws a dependency graph just for your project. For a simple POM with no sub modules, it draws a graph of all dependencies (including transitive ones) below it. For a POM with sub modules, goes into each leaf POM and generates a separate graph for it.
Here is an example of output on the plugin itself
Read more: Maven dependencies graph plugin in TeamCity and Eclipse
Privacy Statement | Copyright Notice | Licenses
© 1999-2012 Waltercedric.com. Designed by Cédric Walter. Sitemap
Reproduction without explicit permission is prohibited. All Rights Reserved. All photos remain copyright © their rightful owners. No copyright infringement is intended.
Disclaimer: The editor(s) reserve the right to edit any comments that are found to be abusive, offensive, contain profanity, serves as spam, is largely self-promotional, or displaying attempts to harbour irrelevant text links for any purpose.