Perso I use it as I find it very convenient. Not extra unzip, env var to
change just running ant cli, etc..
What is the problem with? It just works fine.
--
Olivier
On 20 Dec 2014 11:54, "Barrie Treloar" wrote:
> On 20 December 2014 at 10:37, Jason van Zyl wrote:
> >
> > I myself have not used
It's not the repository layout that Google is not honouring. It's the
semantics of the unspecified dependency type in the POMs in that repository.
If the POM syntax were changed to require that deps had a type then Maven
itself could fail the build because it could determine that the inputs were
in
On 20 December 2014 at 10:37, Jason van Zyl wrote:
>
> I myself have not used the bootstrap in 18 months. I use a previously
> built version of Maven. Anyone using it? Anyone care if I remove it?
+1.
It's a complicated setup that can be avoided.
I myself have not used the bootstrap in 18 months. I use a previously built
version of Maven. Anyone using it? Anyone care if I remove it?
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/
Hi!
The Apache Maven Team is pleased to announce the release of 3.2.5
The release notes can be found here:
http://maven.apache.org/docs/3.2.5/release-notes.html
The release can be downloaded from:
http://maven.apache.org/download.cgi
Full list of changes can be viewed in JIRA:
https://jira.code
On 2014-12-19, 17:40, William Ferguson wrote:
I'd love to go the first route, but unfortunately Google is only making the
Android libraries available via a repository that is downloaded (and
updated) via the Android SDK. So they are not visible on Maven Central and
Maven Central obviously couldn'
I'd love to go the first route, but unfortunately Google is only making the
Android libraries available via a repository that is downloaded (and
updated) via the Android SDK. So they are not visible on Maven Central and
Maven Central obviously couldn't vet them.
The second option would work, but I
The Apache Maven team is pleased to announce the release of the
Apache Maven Assembly Plugin, version 2.5.3.
The Assembly Plugin for Maven is primarily intended to allow users to aggregate
the project output along with its dependencies, modules, site documentation,
and other files into a single di
GitHub user kwin opened a pull request:
https://github.com/apache/maven-enforcer/pull/14
MENFORCER-220 pass real MojoExecution into the EnforcerExpressionEvaluator
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kwin/maven-enforc
+1 from me...
Kind regards
Karl Heinz Marbaise
On 12/16/14 12:10 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11124&version=15977
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=proje
Ok, I understand the problem now, but I don't think forcing everything
to explicitly state dependency type is the right solution here.
"Convention over configuration" is one of fundamental Maven principals,
and by convention dependencies are assumed to have type=jar.
I see two possible ways to im
Thanks for the update Robert.
Rgds , Rory
> On 18 Dec 2014, at 21:58, Robert Scholte wrote:
>
> Hi all,
>
> small update: I've fixed MANIMALSNIFFER-49
> I've built Maven from trunk using the latest SNAPSHOT of the
> animalsniffer-maven-plugin and now it succeeds.
> Next I'll search for a co
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67626029
Feeding the tagged sources to the reports is not an issue. Feeding
intermediate build results is. That's like the tagged sources changing with
every build. Everyth
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67625978
irc.codehaus.org #maven-dev
---
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 th
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67625959
Maybe jump in IRC, probably easier to chat.
---
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
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67625232
I don't agree. Why would you not want to build the site from the sources
for the tag of the release you're building?
---
If your project is set up for it, you can reply to
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67625161
Maybe the proper solution would be to control this behaviour based on an
attribute of the lifecycle ? So a lifecycle can be flagged as producing
artifacts or as co
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67622663
It is re-enabling the following workflow in Maven 3.
cmd> mvn release:prepare
cmd> mvn release:perform
Wait until the artifacts are syn
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67621964
I'm not really in favour of this change. This seems entirely wrong to
change the way resolution works for the site plugin.
---
If your project is set up for it, you can re
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67621081
I would need a way to disable workspace resolution mainly for the `site`
lifecycle.
cmd> svn checkout .../tags/maven-3.0
cmd> cd maven-3.0
Up and about after flying to Bangalore. I'll work on the announcement now.
On Dec 17, 2014, at 1:25 PM, Jason van Zyl wrote:
> +1 from Jason, Stephen, and Karl
>
> I'll promote the release, let it trickle out, and do the announcement
> tomorrow.
>
> On Dec 14, 2014, at 7:00 PM, Jason van Zyl
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-67614958
Can you explain why this is needed?
---
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
22 matches
Mail list logo
