>
> I do not agree on this one, and that's the meaning of the coding style
>
Wouldn't you rather have the compiler catch the error as opposed to
manually introspecting the code each time?
The Apache Maven team is pleased to announce the release of the Apache Maven
SCM Publish Plugin, version 1.1
This plugin is a utility plugin to allow publishing Maven website to any
supported SCM. The primary goal was to have an utility plugin to allow Apache
projects to publish Maven websites
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Benson Margulies, Hervé Boutemy
+1 (non binding):
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr...@maven
here is my +1
Le dimanche 18 mai 2014 22:54:12 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 3 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12730&styleName=H
> tml&version=20027
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavi
Hello,
I was wondering if you could shed any light on a problem I am having.
I have a multi-module project in which one of the modules produces both a
jar and an rpm. I am wondering is there a way to deploy both artefacts to
nexus using the Maven Release Plugin. Currently, the rpm is created
right, sorry by the noise, I didn't look well at the stacktrace to find which
method
was used
at
com.jayway.maven.plugins.android.phase_prebuild.ClasspathModifierLifecyclePartici
pant.afterProjectsRead(ClasspathModifierLifecycleParticipant.java:78)
now I understand, thank you
Hervé
Le mercred
Thank you!
Maciej
2014-05-21 16:32 GMT+02:00 Jason Pyeron :
> > -Original Message-
> > From: Maciek Karas
> > Sent: Wednesday, May 21, 2014 6:47
> >
> > Hi.
> >
> > I found bug or at least missing feature in maven ear plugin.
> > I tried to
> > submit it in JIRA http://jira.codehaus.org/
> -Original Message-
> From: Maciek Karas
> Sent: Wednesday, May 21, 2014 6:47
>
> Hi.
>
> I found bug or at least missing feature in maven ear plugin.
> I tried to
> submit it in JIRA http://jira.codehaus.org/browse/MEAR but I
> don't have account there.
To create an account http:/
For why it fixes it you may want to take a look at the detailed documentation
Benjamin wrote while working on Maven 3:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Class+Loading
Extensions A and B in the diagrams are your case exactly. The
PlexusWagonProvider in Aether injects t
Hi.
I found bug or at least missing feature in maven ear plugin. I tried to
submit it in JIRA http://jira.codehaus.org/browse/MEAR but I don't have
account there. I have explained every detail at stackoverflow:
http://stackoverflow.com/questions/23734249/maven-ear-plugin-project-property-lookup-fa
I am absolutely certain that all project build extensions are loaded by
the time participant#afterProjectsRead is called, and this is the
callback used in William's example. Setting correct TCCL makes his
example work.
You are correct, however, that participant#afterSessionStart is invoked
before
If you restore TCCL to its original value, this is the correct way to
scope component lookup to the current project. This is what Maven does
during the build.
--
Regards,
Igor
On 2014-05-21, 4:33, William Ferguson wrote:
Thanks Igor. That fixes it :-)
Is there any fallout that I should be awar
Github user cstamas closed the pull request at:
https://github.com/apache/maven/pull/10
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Thanks Igor. That fixes it :-)
Is there any fallout that I should be aware of from setting the
Thread#contextClassloader to MaveProject#classReam at that point in the
lifecycle?
William
On Wed, May 21, 2014 at 11:20 AM, Igor Fedorenko wrote:
> MavenLifecycleParticipant comes from a build exten
14 matches
Mail list logo
