Working on productization we want to avoid code (also pom) changing,
but often we have to change some plugin property (tesets, source packing, ...)
being able to change it via external property would be useful.
Should I file a feature request? Under which component?
Thanks,
Matej.
On
Nope no feature request. It would be rejected.
If you regularly need to tweak config of something, it is up to you to
prepare your poms before hand to allow for such tweaking by binding
properties to the configuration elements that you want to tweak and
providing the sensible defaults that you
On 17 December 2013 11:45, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
Nope no feature request. It would be rejected.
Actually It would be nice to have a configuration like this:
profile
iddisable-test/id
activation
property
Cemo wrote:
On 17 December 2013 11:45, Stephen Connolly
stephen.alan.conno...@gmail.com
wrote:
Nope no feature request. It would be rejected.
Actually It would be nice to have a configuration like this:
profile
iddisable-test/id
activation
Hi,
The issue got resolved when i removed the below dependency in pom.xml
dependency
groupIdcom.101tec/groupId
artifactIdzkclient/artifactId
version0.3/version
/dependency
But upon submitting the topology, the storm code is throwing the below
exception:
java.lang.NoClassDefFoundError:
But upon submitting the topology, the storm code is throwing the below
I have no idea what submitting the topology means.
java.lang.NoClassDefFoundError: org/I0Itec/zkclient/serialize/ZkSerializer
at
kafka.javaapi.consumer.ZookeeperConsumerConnector.(ZookeeperConsumerConnector.scala:64)
at
since the value is readonly, it doesn't go to the user-documentation because
user can't do anything: it's pure internal code
for yourself, you can change readonly to false and see user documentation
generated
Regards,
Hervé
Le dimanche 15 décembre 2013 21:15:32 Martin Gainty a écrit :
Have a look at how the maven-javadoc-plugin handles docletartifacts [1]
You'll probably will need to use Aether, which means you should consider
using the Maven Dependency Tree[2] to support Maven 2, Maven 3.0.x and
Maven 3.1.x.
Robert
[1]
Thanks Robert. It is a huge lead.
-D
On Tue, Dec 17, 2013 at 11:58 AM, Robert Scholte rfscho...@apache.orgwrote:
Have a look at how the maven-javadoc-plugin handles docletartifacts [1]
You'll probably will need to use Aether, which means you should consider
using the Maven Dependency
From: herve.bout...@free.fr
To: users@maven.apache.org
Subject: Re: WhatWeSayWeDo != WhatWeDo
Date: Tue, 17 Dec 2013 19:53:28 +0100
since the value is readonly, it doesn't go to the user-documentation because
user can't do anything: it's pure internal code
for yourself, you can
So any work available
On Dec 12, 2013 12:43 PM, Jose Manuel Garcia Maciel/Mexico/IBM
jos...@mx1.ibm.com wrote:
I will be out of the office starting 12/12/2013 and will not return until
01/06/2014.
I will respond to your message when I return. If urgent my phone is in
bluepages
11 matches
Mail list logo
