It's synced now. Thanks Olivier!
Am I right to assume that this duplication is not likely to be present in
future and that Apache Maven binaries will be published only on new
path/URL?
Kind regards,
Stevo Slavić.
On Fri, May 24, 2013 at 3:59 PM, Olivier Lamy ol...@apache.org wrote:
ok.
I
Hello,
I have two different web.xml files. One for Developers and another for
Production.
Today I manually rename the file to use in develop enviroment and
production. I would like to know how can I automatize the build using Maven
Profile (or any other plugin). Is that possible?
Thanks in
I have two different web.xml files. One for Developers and another for
Production.
Why? What specifically is different? Can those differences not be
eliminated, to produce one single artifact for all environments?
Wayne
-
To
I believe this is quite reasonable. Developers would like to be able to see a
lot of reports on the code internals. The ability to generate those is one of
Maven's strengths; however, users (which I assume is meant by production)
should generally not be given all that information, especially if
I'm having trouble understanding your use case still, I think - and you are
disregarding the general pattern that child poms are found nested under their
parent; however, from your description, I don't see why this wouldn't work. Can
you make a small sample project that displays the problematic
what I prefer to do is have developers use an on-demand servlet container,
e.g. jetty or tomcat and then configure web.xml overrides for the app when
deployed using e.g. jetty:run or tomcat:run
but YMMV
On 27 May 2013 16:58, Russell Gold r...@gold-family.us wrote:
I believe this is quite
The differences between the web.xml is
context-param
param-namejavax.faces.PROJECT_STAGE/param-name
param-value*Development | Production*/param-value
/context-param
and some error-page tags.
Ivo
On Mon, May 27, 2013 at 1:12 PM, Russell Gold r...@gold-family.us wrote:
OK, *headdesk*. I was
I think my initial idea is somthing like what Russel said. But I don't know
how to do it.
Ivo
On Mon, May 27, 2013 at 2:20 PM, Alberto Ivo alberto...@gmail.com wrote:
The differences between the web.xml is
context-param
param-namejavax.faces.PROJECT_STAGE/param-name
OK, I think I have managed to duplicate the behavior. Is this what you are
seeing?
[ERROR]
[ERROR] The project com.packtpub.maven:obfuscate:1.0
(/Users/russgold/projects/maven-course/sample4/obfuscator/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
Am 2013-05-27 17:20, schrieb Alberto Ivo:
Hello,
I have two different web.xml files. One for Developers and another for
Production.
Today I manually rename the file to use in develop enviroment and
production. I would like to know how can I automatize the build using Maven
Profile (or any
Michael-O, how do you choose what webapp use? Manually?
Ivo
On Mon, May 27, 2013 at 2:33 PM, Michael-O 1983-01...@gmx.net wrote:
Am 2013-05-27 17:20, schrieb Alberto Ivo:
Hello,
I have two different web.xml files. One for Developers and another for
Production.
Today I manually rename
Am 2013-05-27 19:37, schrieb Alberto Ivo:
Michael-O, how do you choose what webapp use? Manually?
Please do NOT top post:
http://en.wikipedia.org/wiki/Posting_style#Choosing_the_proper_posting_style
Choosing for what?
On Mon, May 27, 2013 at 2:33 PM, Michael-O 1983-01...@gmx.net wrote:
The Mojo team is pleased to announce the release of the Maven 2.x Keytool
Plugin version 1.3
A plugin that wraps the keytool program bundled with Oracle's Java SDK. Allows
to
manipulate keystores.
Description
---
This Keytool Plugin has the 17 following goals:
keytool:changeAlias
13 matches
Mail list logo
