On 10 Jul 2013, at 06:05, Baptiste MATHUS bmat...@batmat.net wrote:
If those properties are specific to eclipselink, then I think it's ok and
simpler to just leave them in the persistence.xml even if they're actually
not used when EclipseLink isn't the provider. Then package only one ear.
Well the first thing I would look towards is whether you can use an
application server specific deployment descriptor to tweak the effective
persistence.xml at deployment time.
I am not saying that the above is possible, but if it is, then that is
obviously the way to go as you then can just
Hi Mirko. If you want the compile class path for the pom executing a plugin,
you can do this:
1. Configure the plugin to require compile and runtime dependency resolution:
@Mojo( ... requiresDependencyResolution = ResolutionScope.COMPILE_PLUS_RUNTIME)
2. Specify a parameter configured to
Where does an installer fit in this vision?
It seems to me, having installed thousands of programs as a Windows user
and Linux system administrator, that a lot of the discussion about
deployment issues seem to ignore the role of installers (rpm, msi,
izPack, etc.).
They are specifically
Well if it is an interactive installer then it can do the configuration for
you...
But with a JavaEE application you don't know:
1. What application container they have
2. What database they have
3. Where the application container picks up deployed apps
4. How the user wants the app deployed in
On 10/07/2013 10:06 AM, Stephen Connolly wrote:
Well if it is an interactive installer then it can do the
configuration for you...
It needs to be interactive in some way if you want to handle a variety
of environments.
./configure
make
install
(you hope that you don't end up with something
On 10 July 2013 15:52, Ron Wheeler rwhee...@artifact-software.com wrote:
On 10/07/2013 10:06 AM, Stephen Connolly wrote:
Well if it is an interactive installer then it can do the configuration
for you...
It needs to be interactive in some way if you want to handle a variety
of
I agree with a lot of the JCP description of the deployer role.
I also think that they are oriented to a small portion of the deployment
world.
Most of the time the person doing deployments has a third party product
from a vendor and does not have the source code and does not even have
any
Hi,
The Mojo team is pleased to announce the release of the
appassembler-maven-plugin version 1.4
The Application Assembler Plugin is a Maven plugin for generating scripts
for starting java applications. All dependencies and the artifact of the
project itself are placed in
a generated Maven
There is a beautiful example of the fluido skin used for site generation
including checkstyle report creation out at:
http://maven.apache.org/skins/maven-fluido-skin/checkstyle-aggregate.html
I have been trying to recreate use of fluido with checkstyle to no avail.
So I downloaded the fluido
You are creating the site and THEN running the check style mojo independently.
You should be specifying the check style plugin in your reports section.
On Jul 10, 2013, at 3:26 PM, Spammer Juliano s...@danandlaurajuliano.com
wrote:
There is a beautiful example of the fluido skin used for site
Hello Russel,
thanks, but how do I specify this in Ant-Mojos?
Regards Mirko
--
Sent from my mobile
On Jul 10, 2013 2:37 PM, Russell Gold r...@gold-family.us wrote:
Hi Mirko. If you want the compile class path for the pom executing a
plugin, you can do this:
1. Configure the plugin to
Hi Olivier,
On 09.07.2013 14:27, Olivier Lamy wrote: * [MWAR-267] - Maven WAR
plugin does not copy dependencies of type
bundle into WEB-INF/lib
Thanks for fixing this. It's a great help.
Bye, Thomas.
-
To
Thanks for the feedback, I've managed some success using a reporting tag
in my pom. I've created a HelloWorld project and am following the
guidelines at:
http://maven.apache.org/plugins/maven-checkstyle-plugin/usage.html
I'm able to generate a fluido styled checkstyle report and link to it from
Hi,
If you are running the failsafe plugin for integration tests, and you bind only
the integration-test goal and not the verify goal, you can have test failures
in your build. Is there a way to report them on the project website?
Thanks,
Russ
-
Come read my webnovel, Take a
OK, found it - the maven-surefire-report-plugin seems to does the trick; only…
it is not clear to me if it simply has not been maintained much, or something
is missing from the documentation.
There are goals for selecting reports, but typically you select reports for
websites by specifying
Hi,
After i run the command 'mvn package', then i get the following error message :
Failed to execute goal org.kohsuke:access-modifier-checker:1.4:enforce
(default-enforce) on project javaone-sample: Execution default-enforce of goal
org.kohsuke:access-modifier-checker:1.4:enforce failed:
Hi,
Do you have a repository configured? You're trying to read artifacts from
maven.glassfish.org, which is generally intended for glassfish development. You
should be able to get most of what you want from maven central.
- Russ
On Jul 10, 2013, at 9:46 PM, 邹志勇 zouzhiyong0...@163.com wrote:
Hi all- I'm writing an obfuscator plugin that invokes the ProGuard open
source java obfuscator. There is that was written several years ago, but I
had problems adapting it to into our projects so decided to write a new one
for Maven 3.0. I've been thinking about whether the plugin should run at
I've several projects that were created before we began using maven and
which we've added maven to subsequently. Obviously these projects were not
created with an archetype. Is there a standard folder that is commonly
used in archetypes for holding files such as application configuration files
or
20 matches
Mail list logo
