I got it working by switching
componentConfigurator.configureComponent( wagon, plexusConf,
container.getContainerRealm()
);
for
componentConfigurator.configureComponent( wagon, plexusConf,
(ClassRealm)this.getClass().getClassLoader() );
Thoughts?
-Dan
On Sun, Nov 27, 2016 at 9:34 PM, Dan Tran
I am interested fixing the long waited issue
https://issues.apache.org/jira/browse/WAGON-454 ( since introduction of
Maven 3)
where a wagon user can configure additional wagon provider configuration
at maven settings
It boils down to this line
https://github.com/mojohaus/wagon-maven-plugin/blo
Hi,
it all depends if the introduced escape character is really a good default
and/or if we should have 2 parameters regarding escaping.
I prefer having only 1 parameter and I think that the chosen escape
character is not default enough to mark it as _the_ default.
just my 2 cents
Robert
O
Hi,
On 27/11/16 18:34, Hervé BOUTEMY wrote:
yes, reverting MRESOURCES-223 seems reasonable since it has drawbacks that
were not envisioned IMHO
Yes this is a problem...
So this should be changed...I think of introducing an option to simply
disable escaping...which will keep the behaviour of
look at the begining of the console output: "Building remotely on jenkins-
test-2e6"
looks like some tests: I launched the build and it's now ok, and I just asked
for information on these slaves [1]
Regards,
Hervé
[1] https://lists.apache.org/thread.html/
9b5040d35b9e05e21493184be5b307039bb8f35
yes, reverting MRESOURCES-223 seems reasonable since it has drawbacks that
were not envisioned IMHO
Karl Heinz, since you worked on MRESOURCES-223, what do you think about it?
Regards,
Hervé
Le vendredi 25 novembre 2016, 14:24:15 CET Christian Schulte a écrit :
> Hi,
>
> the maven-resources-p
