Hi all!
I would like to bring the binary build package of Maven 2.0.5 built by
Michael Koch to your attention. I just installed it on Ubuntu Edgy and ran
my builds and all works fine.
http://gnu.wildebeest.org/diary-man-di/?p=35
I can recommend using it.
Manfred
--
View this message in
of their project.
Please help us to spread the word.
Thanks
manfred
--
Manfred Moser
Founder Vancouver Island Java User Group
http://www.mosabuam.com/vijug
http://twitter.com/mosabua
http://www.linkedin.com/in/manfredmoser
Hi All,
Hugo, Ricardo and myself have just released a new set of components
for working with Maven and Android.
If you are interested in Android and Maven please join us on the Maven
Android Developers mailing list. at
http://groups.google.com/group/maven-android-developers
We hope to see you
Hi All,
Hugo, Ricardo and myself have just released a new set of components
for working with Maven and Android.
If you are interested in Android and Maven please join us on the Maven
Android Developers mailing list. at
http://groups.google.com/group/maven-android-developers
We hope to see you
Just a quick heads up that thanks to a combined community effort the
android jar files are now available in maven central.
http://www.simpligility.com/2010/06/android-artifacts-hit-maven-
central/
manfred
-
To unsubscribe,
Hi all!
Thanks for the great release. I thought I let you know that the new beta-2
release works like a charm for Android projects using the Maven Android
Plugin.
On to trying the new site plugin next ..
manfred
http://www.simpligility.com
Well.. can we get that patch applied and a new release of the maven 3 site
plugin as well then.
manfred
PS: beta 2 works on all my projects..
Hi,
Let's go for merge ! (with last spice version 1.3.3-SNAPSHOT or
released version to have a fix for SPICE-34).
Herve : regarding site plugin
On 01/11/2010, at 1:54 PM, Jason van Zyl wrote:
Doesn't change the fact it's a hack, generally not useful and is
generally not going to get used.
I don't disagree, but given it was just yesterday, I think Dennis should
get to finish what he's doing.
Dennis, are you committed to
Works fine on a multi module Android project with plain library, Android
application and instrumentation test modules.
manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
Works for me for building and working with
- Maven Android Plugin
- Maven Android SDK Deplouer
- a JasperServer war project
- ksaop2-android project
- Maven Android Plugin Samples project (4 android project including a
scala one)
manfred
http://www.simpligility.com
Hi,
we're aiming at a
I find it somewhat bewildering that there is no post of the vote or the
results on the dev and users mailing lists I can see. Nor does the web
site seem to be updated.
http://maven.apache.org/team-list.html
I would have expected more transparency from Apache.
manfred
Jeff,
I believe this
Hm... sure Jason had and still has lots of influence. But so does Linus
and so do other BDFL's. Imho the Maven project has tons of good people
involved in the community around the core and the plugins. Jason is one of
them and there are MANY others. There should be cooperation and open
On 22 June 2011 23:20, Benson Margulies bimargul...@gmail.com wrote:
I wrote a program for the job, it reads my gmail and matches it
against the PMC membership. Unfortunately, not all of us vote from
email addresses that match our Apache Member IDs. Would people be
willing to use their
Hi!
I am not a web designer either but from a mere content point of view this
page is already way too busy.
The developer and plugin developer stuff can be removed or reduced to one
link each. The environment tooling links are not necessary on the front
page. The section Maven and Maven users
Also .. from what I understand Maven and core plugins depend on a whole
bunch of other libraries that are not in Maven and/or not in Apache so as
long as there is license compatibilitys I am sure the Maven devs can work
with upstream projects like Aether just like others like commons* or
whatever
+1 (non-binding)
We have started to use Aether in the upcoming Maven Android Plugin and it
already fixes a bunch of issues related to inclusion of native
dependencies.
And as a user I am concerned that Maven needs to keep moving forward asap
to avoid more mindshare loss on cutting edge/power
+1 (non binding)
Manfred
On Thu, August 18, 2011 7:08 am, Ralph Goers wrote:
+1 (binding)
Ralph
On Aug 18, 2011, at 2:23 AM, Arnaud Héritier wrote:
Hi all,
Thus as decided with Mark and Kristian I relaunch a new vote with a
better
scope about what we are voting for.
Next releases
On 11-09-06 08:03 PM, Jesse Farinacci wrote:
Greetings,
On Tue, Sep 6, 2011 at 10:48 PM, Kasturi Kumthekar
kasturi.kumthe...@gmail.com wrote:
http://pragmaticjava.blogspot.com/2011/08/customizing-mavens-lifecycle.html
I find it almost pathological to enforce both Java 1.6 and Maven
2.0.10.
On 11-09-17 09:00 AM, Jason Pyeron wrote:
Is the metadata in the revision? Only export the revision. Defense, Healthcare,
life safety, large organizations, all of these type of organizations have rules,
we are trying to make Maven more adaptable so it can be used there on projectes
where the
On 11-09-17 08:55 PM, Jason Pyeron wrote:
-Original Message-
From: Manfred Moser
Sent: Saturday, September 17, 2011 23:38
To: dev@maven.apache.org
Subject: Re: Request for review and comment
http://jira.codehaus.org/browse/MNG-5167
On 11-09-17 09:00 AM, Jason Pyeron wrote
+1 (non-binding)
manfred
On Thu, November 10, 2011 1:11 pm, Anders Hammar wrote:
+1 (non-binding)
/Anders
On Thu, Nov 10, 2011 at 20:35, Wayne Fay wayne...@gmail.com wrote:
I propose to upgrade to:
* aether 1.13
* sisu 2.3.0
[+1] I'm in favor of this upgrade and the other upgrade when
Good idea. Maven definitely needs a new look including a good log. How
about using something like 99designs.com in addition and if we find a
winner via it just raise the needed money..
manfred
On 11-11-22 11:53 AM, Olivier Lamy wrote:
Hi,
What do you think about asking the community for a
Are you kidding ;-) It is a huge step forward.
On 11-11-22 12:51 PM, Simone Tripodi wrote:
hey, don't you like the fluido-skin as new maven site skin? :)
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On
+1 (non-binding)
works for Hudson, ksoap2-android, the android-maven-plugin and a bunch
of other stuff.
manfred
On 11-11-25 01:17 AM, Olivier Lamy wrote:
Hello,
I'd like to release Apache Maven 3.0.4.
We fixed 31 issues.
See release notes:
Hi!
It was great seeing that others have the same problem with complex
objects for Maven configuration and the generated documentation.
For the android maven plugin
http://code.google.com/p/maven-android-plugin/
I have derived a bit of a standard on how we deal with this and we have
For a full working example mapping Maven to a different life cycle with
a whole bunch of different tasks look at the code of the android maven
plugin..
manfred
On 12-01-03 08:43 AM, Vincent Latombe wrote:
Hello Carson,
you can achieve what you need by defining a new packaging, as described
+1 non-binding
would love to use fluido 1.1
manfred
On 12-01-06 12:50 PM, Simone Tripodi wrote:
Hi all guys,
I am here to propose the Maven Skins version 6, that includes
* Maven Application Skin 1.0 * Maven Default Skin 1.1 * Maven Classic
Skin 1.1 * Maven Stylus Skin 1.4 * Maven Fluido
I would love for those changes to go out..
On 12-01-16 12:42 PM, John Casey wrote:
I'm eager to get a release that has some of the fixes already on
trunk, particularly those related to aggregating javadocs using
dependencies.
Does anyone have any objection to me calling a vote to release
On 12-02-22 08:11 PM, Chas Emerick wrote:
I am working on a Clojure facade for Aether,[1] and would like to clarify some
semantics. Though I'm working with Aether, I think this question is generally
applicable for all Maven tools…but let me know if I should simply bounce to the
Aether ML.
On 12-02-23 04:37 AM, Chas Emerick wrote:
On Feb 23, 2012, at 1:01 AM, Chris Graham wrote:
Remember that 'deploy' still calls 'install'.
Very true for `mvn`. Not true in Aether; this would seem to be a userland tool
convention, and not a fundamental characteristic of the 'deploy' operation.
He is talking about the notion of a install and deploy operating as
implemented by the deploy and install plugins. He is porting them to
Coljure for usage with Clojure build tools like Leiningen and it using
the same library Maven is using for it - Aether.
manfred
On 12-02-23 05:24 AM,
Jos,
I agree with you in the sense that any open source project that cares
about a wide user base should try to provide packages of its software
that are useful to as many people as possible.
Therefore e.g. the Jenkins effort to offer all sorts of installs is
laudible imho.
However for
On Tue, March 20, 2012 7:19 am, Stanislav Ochotnicky wrote:
I would *really* like for maven to produce RPMs as alternative dist
output, but I understand your position. I had a quick look into
rpm-maven-plugin and I believe a reasonable RPM output could be achieved
by using it in with
This is all really great. Now we just need sensibly designed deb like. I
believe Tim did something like that in the past which could be the start
for it
http://discursive.com/2011/04/21/installing-maven-3-from-a-binary-deb-on-ubuntu/
manfred
On 12-03-22 08:43 AM, Stanislav Ochotnicky wrote:
Your Java home points to a JRE .. Maven is a Java development tool and
therefore needs the JDK.
On Tue, April 24, 2012 12:57 am, copyto27 wrote:
Hi john
I tried all you told me, but i continue with the same error
the result of the mvn -version command
PS C:\ mvn -version
Apache Maven
We have implemented a Java 5 annotation for configuration parameters
(PullParameter) in the Android Maven Plugin that might be worth looking
at. We are still phasing them out across the system but a good place to
look at the usage is the ProguardMojo
Its great to see this teamwork happening from the outside. Keep it up!
manfred
On Wed, May 9, 2012 12:47 pm, Jason van Zyl wrote:
The only thing I might suggest is that you create a hybrid scanner that
can deal with the old and new. It looks like you've already looked at [1],
but the hybrid
Correct and it has a large user base and more. I already sent an email to
Shane suggesting to cooperate. It would be great to have somebody of his
experience with the android maven plugin and we could e.g. pull in a few
things like the LintMojo..
manfred
On Thu, May 24, 2012 2:30 am, Emmanuel
Hi!
The Android Maven Plugin is currently considering implementing a code
style and we are probably going to use the Maven codestyle from here
http://maven.apache.org/developers/conventions/code.html
We are planning to enforce the style as part of the build and are
therefore wondering if a
]
Regards,
Hervé
[1] http://svn.apache.org/viewvc/maven/pom/tags/maven-
parent-21/pom.xml?view=markup
[2] http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-
mojo.html#configLocation
Le lundi 28 mai 2012 10:59:51 Manfred Moser a écrit :
Hi!
The Android Maven Plugin
On Wed, June 13, 2012 12:17 pm, Shane Isbell wrote:
Hi all,
I'm working on an android provider for surefire. Generally, I have things
working but have encountered a specific problem. The unit tests are
running
remotely on a device (not the build machine). For the surefire xml report,
I need
While it might be possible it is a bad idea that will cause your problems
most likely... why do you want to do that?
manfred
On Fri, July 6, 2012 12:18 pm, Anders Hammar wrote:
Yes, although it's not good practice. One project should only produce
one main artifact.
To have the
Hi!
Some users of the Android Maven plugin are having trouble with the
compilation because the android.jar that includes all classes from harmony
is on the classpath together with the Oracle JDK.
When method signatures between the two differ e.g. like mentioned here
://maven.apache.org/guides/mini/guide-using-toolchains.html
[2]
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerId
[3] http://plexus.codehaus.org/plexus-components/plexus-compiler/
Op Fri, 06 Jul 2012 23:13:11 +0200 schreef Manfred Moser
manf...@mosabuam.com:
Hi!
Some
:59:51 Manfred Moser a écrit :
Hi!
The Android Maven Plugin is currently considering implementing a code
style and we are probably going to use the Maven codestyle from here
http://maven.apache.org/developers/conventions/code.html
We are planning to enforce the style as part of the build
Congrats Anders!
On Mon, August 20, 2012 1:31 pm, Anders Hammar wrote:
Thanks Stephen!
Happy to be onboard!
/Anders
On Mon, Aug 20, 2012 at 10:19 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I am probably jumping the gun by an hour or two... however the account
has
been
This is one of the caveat that I have when training people Maven usage and
plugin configuration. The documentation is always the newest and it is
actually hard to find old sites and the respective documentation.
The example I always use is the compiler plugin defaulting to language
level 1.3 with
It at least was possible to write a plugin in Groovy without annotations
though. See
http://www.sonatype.com/books/mcookbook/reference/writing-plugins-alternative-sect-writing-groovy.html
Not sure what happened..
manfred
On Thu, August 23, 2012 1:18 pm, Hervé BOUTEMY wrote:
Groovy isn't
I will document this in the Nexus book. Should be available with the next
release of it..
manfred
On Tue, August 28, 2012 2:37 am, Kristian Rosenvold wrote:
Thanks a lot ;) There is no end to how much time someone (=me) can waste
on this. I will update the docs on the core IT's about this;
+1 non binding
In terms of learning more about git, there are a LOT of free resources
available including books and other documentation as well as things like
live office hours at github and so on.
GitHub is also open sourcing all their training material so there will be
more as well.. and lots
On Wed, September 12, 2012 6:06 pm, Chris Graham wrote:
On Wed, Sep 12, 2012 at 9:46 PM, Anders Hammar and...@hammar.net wrote:
I fully agree with you and I'm actually of the opinion that the Java
community has a responsibility to provide enough reasons for those on
older Java platforms to
On Thu, September 13, 2012 6:52 am, Mark H. Wood wrote:
On Wed, Sep 12, 2012 at 09:04:09PM -0700, Manfred Moser wrote:
I think that the cost is only so high because companies keep waiting
until
it is too painful. If you constantly keep upgrading a bit here and there
and stay up to date
On Thu, September 13, 2012 7:05 pm, Chris Graham wrote:
On Thu, Sep 13, 2012 at 2:04 PM, Manfred Moser manf...@mosabuam.com
wrote:
I think that the cost is only so high because companies keep waiting
until
it is too painful. If you constantly keep upgrading a bit here and there
and stay up
On Tue, November 13, 2012 12:38 pm, Jason van Zyl wrote:
This is a long-standing issue, but I think a document and standard has
emerged that I think is reasonable. How do people feel about trying to
adhere to:
http://semver.org
and moving toward using this as our standard versioning
Manfred Moser
manf...@mosabuam.com:
On Tue, November 13, 2012 12:38 pm, Jason van Zyl wrote:
This is a long-standing issue, but I think a document and standard has
emerged that I think is reasonable. How do people feel about trying to
adhere to:
http://semver.org
and moving toward using
some plugines like release or versions need to try to guess which is the
next
one: nothing that belong to core IMHO
Regards,
Hervé
Le mardi 13 novembre 2012 14:28:18 Manfred Moser a écrit :
True... separate, but closely related. If we state that semver is the
recommended practice (and I
contributors for their awesome work.
Tim Hepner https://github.com/mithepner
Aleksander Pyszny http://www.alan-systems.com/en
Tom Bollwitt https://github.com/tlbollwitt
Nic Strong http://www.codepoets.co.nz
Manfred Moser http://www.simpligility.com
Documentation, issue tracker and more can be found
Hi all!
Just a question out of curiosity for the 3.1 release. Are you planning to
update some of the plugin version set in the super pom to newer versions?
E.g the compiler plugin to 2.5.1 would be nice for Java 7 users from what
I know..
manfred
, Manfred Moser manf...@mosabuam.com
wrote:
Hi all!
Just a question out of curiosity for the 3.1 release. Are you planning
to
update some of the plugin version set in the super pom to newer
versions?
E.g the compiler plugin to 2.5.1 would be nice for Java 7 users from
what
I know..
manfred
Great to see it is not only me that finds that weird and gets annoyed by it.
Getting rid of it sound like a great idea.
manfred
On Tue, November 27, 2012 12:50 pm, Anders Hammar wrote:
+1 for removing it! Or at least change it to something that strongly
suggest updating it.
/Anders
On
On Fri, November 30, 2012 12:33 pm, Mark Struberg wrote:
I don't believe it's valid to just let everyone do whatever they want.
Well, I think this is the fundamental point we disagree on.
Maven is not only a build system but also a container which runs user
specific stuff. And a container
://github.com/tptak
Stéphane Nicolas https://github.com/stephanenicolas
Jonas Alves http://jonasalves.wordpress.com/
Manfred Moser http://www.simpligility.com
Documentation, issue tracker and more can be found on the plugin website at
http://code.google.com/p/maven-android-plugin/
For a primer to use
Totally agree... if people really need to build for older Java runtimes
they still can.. but if Oracle thinks they dont want to support JDK 1.7
without getting paid why would the Maven project do it ;-)
For now 1.6 seems just fine and I would even say a jump to 1.7 in the next
year or three
This is similar to what I've used to describe it to people in the past:
Apache Maven is a build management and automation system that defines a
standard build lifecycle as well a plug-in mechanism to perform activities
using project configuration during specific lifecycle phases of the build
On 27 Feb 2013, at 19:34, Benson Margulies bimargul...@gmail.com wrote:
I think it's long overtime for us to officially disclaim support for
Maven 1.
I completely agree. In fact .. while I would suggest to do this asap and
then make the same call for Maven 2. I wonder who would actually be
Hi Alex,
I wrote that advice. The reasons is that depending on your package
structure and number of different team needing different staging profiles
I can become hard to maintain all the repository targets and profiles
matching correctly. We have certainly found that to be the case with OSSRH
This page is completely out of date. Nowadays you would use a repository
manager like Nexus and have most of the issue taken care of..
manfred
Hi all,
Many projects still don't use maven that for me is the best build
tool, but have several problems with security, a summary in
it isn't, just saying that I don't know it is... yet
If we agree on this then I will roll in all the changes, figure
out
what's
wrong with JDK8 and then we release it. The ITs pass and we'll
just
have
to
help people adapt their plugins. I talked to Manfred Moser who
works
I will have a go at it with the android maven plugin and fix what I can..
manfred
+1 Look forward to giving this a harsh bashing and a shaking!
Jason van Zyl wrote:
If no one objects I'm going to roll a release of 3.1.0-alpha-1 over
the weekend. There are plugins that don't work but I
+1 from me (non binding whatsoever but anyway)
I tested it with the build for the android maven plugin and ksoap2-android
and a few other projects.
Apart from the expected problems with shade, site and dependency plugin
the android maven plugin also fails with this due to accessing Aether
Thats fine.. it was just very quiet.
Thanks Stephen.
manfred
I am still poking around with it... when I am happy that I trust it I will
vote... AFAIR we are not running with the strict 72h anyways given the
scope of this change in terms of moving APIs
On 3 April 2013 16:58, Manfred Moser
You would be earning a lot of brownie points I am sure! There are a bunch
of open questions around this and the perception that the archetype system
is pretty much dead on stackoverflow and other places. This could fix a
lot of those concerns..
manfred
Currently, maven-archetype-plugin ignores
bit to far?
/Anders
On Thu, Apr 18, 2013 at 6:41 PM, Manfred Moser
manf...@simpligility.comwrote:
You would be earning a lot of brownie points I am sure! There are a
bunch
of open questions around this and the perception that the archetype
system
is pretty much dead on stackoverflow
Hi all!
The spdy protocol (http://en.wikipedia.org/wiki/SPDY) is getting more and
more tracking and giving some good performance benefits virtually for
free. I was wondering if anybody knows if the http libraries used by Maven
for the various requests (wagon and others) already support spdy or if
Awesome! Congrats to everyone involved.
I am looking forward to adapting the Android Maven Plugin and releasing a
new version asap!
Manfred
+1: Arnaud, Hervé, Brian, Baptiste, Mirko
Vote passes. I will roll out the release later today.
On Jun 4, 2013, at 12:13 PM, Brian Fox
The sentence
The switch in the core from Sonatype Aether
{{{http://eclipse.org/aether}Eclipse Aether}}.
is missing a to
Feel free to reference the Android Maven Plugin breaking with 3.1. We plan
to upgrade the plugin to work with 3.1 (currently ongoing in
I added the Android Maven Pugin to
https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
Do you have any issue tracking reference to link to?
On fixing the issue: I had a very quick look at your poms, and IIUC,
you're
using much Aether API directly from your plugin code.
and maven-
dependency-tree component, which provides compatibility layer between
both
Aether versions. I didn't look precisely into your plugin code, I don't
know
if this strategy can fit.
Regards,
Hervé
Le jeudi 6 juin 2013 14:17:17 Manfred Moser a écrit :
The sentence
The switch
AWESOME!!! Thanks for getting this out the door.
manfred
I will send out the vote result and do the release over the weekend.
On Jun 30, 2013, at 3:00 PM, Jason van Zyl ja...@tesla.io wrote:
Here are the release bits for 3.1.0:
Release notes:
Hi!
With the 3.1.1 release of Maven coming up hopefully soon I would like to
move forward with the plugin testing harness using it as well. Jason fixed
it to work with 3.0 and requested the repo to be moved from svn to git so
he can release 2.2 over a month ago.
It seems like nothing happen on
Manfred
if there is a problem is on the Apache side you should be able to make the
change wheres the hangup
I am not a committer so I have no way to do anything. Maybe I should
become one..
manfred
-
To unsubscribe, e-mail:
Seemingly it does.. a release together with the 3.1.1 release of Maven
would be great.
manfred
I will if it takes 60 days to create a Git repo.
On Sep 19, 2013, at 4:47 PM, Olivier Lamy ol...@apache.org wrote:
Maybe can be release from svn.
On 13 September 2013 14:05, Manfred Moser manf
If I was choosing to write a technical book I would choose asciidoc.
Agreed.. in fact asciidoc is the default markup tool at OReilly. I use it
for all the books as Sonatype including Maven: The Complete Reference and
Maven by Example..
AsciiDoc is the technically superior product that may well
True... but we already did the same when moving from Maven 3.0.5 to 3.1.0,
which is not a drop in replacement... so it would be consistent ;-)
manfred
Well, I don't see the difference, but if I put it this way:
I would be -1 to release Maven 3.1.2 requiring Java 1.6.
One shouldn't bump
://semver.org/ for descriptions of the words I used.
On Mon, Oct 7, 2013 at 9:01 PM, Manfred Moser manf...@simpligility.com
wrote:
True... but we already did the same when moving from Maven 3.0.5 to
3.1.0,
which is not a drop in replacement... so it would be consistent ;-)
manfred
Well, I don't see
Hi!
I have a fork of plugin-testing that works for 3.1.1 at
https://github.com/mosabua/plugin-testing/tree/maven311
It works fine and we currently use it for the android maven plugin master
branch that is migrating to 3.1.1. Could someone please apply the patches
back to the repo and release
have commit
access to shout at if your patches are being ignored ;-)
IOW self starters wanted ;-)
On Wednesday, 16 October 2013, Manfred Moser wrote:
Hi!
I have a fork of plugin-testing that works for 3.1.1 at
https://github.com/mosabua/plugin-testing/tree/maven311
It works fine and we
Benoit Billington wrote:
I'm facing this problem too.
Android has created a new format for its libraries called Android
Archive
(.aar)
This format described here:
http://tools.android.com/tech-docs/new-build-system/aar-format contains
a
/classes.jar
How would I be able to add that
@Manfred We cannot extract the jar into target/classes because the compile
phase will not pick anything from target/classes but use that as output
only. (I didn't check that but It makes sense :) )
@Jorg I cannot let the user set the dependency jar in the pom.
1° the extracted path is
are in the school, only a bunch of mentors who have
commit
access to shout at if your patches are being ignored ;-)
IOW self starters wanted ;-)
On Wednesday, 16 October 2013, Manfred Moser wrote:
Hi!
I have a fork of plugin-testing that works for 3.1.1 at
https://github.com/mosabua/plugin-testing
As you probably noted I cut the 3.8.0 release of the Android Maven Plugin
and announced it on the users list.
It should be of note to you that we now require Maven 3.1.1+ for
developers and users. I have added a prerea and an enforce plugin setup.
As part of getting the build to work I needed a
By separating consumption and production metadata formats, we'll be
able to evolve production format more aggressively. For example, it
would be nice to have Tycho-specific configuration markup inside build
section. This is not currently possible because all poms must be
compatible with the
On Sunday, 24 November 2013, Manfred Moser wrote:
By separating consumption and production metadata formats, we'll
be
able to evolve production format more aggressively. For example, it
would be nice to have Tycho-specific configuration markup inside
build
section
Any objections I stage maven-plugin-testing sometime this week?
None at all. In fact I could move to it from my fork in the android maven
plugin once its out..
manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
+1 for me. Works with the android maven plugin build using Maven 3.1.1
Thanks
Manfred
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=18839
There are still a couple of issues left in JIRA:
Thanks for the release... Android Maven Plugin is using it now in master ;-)
I emailed vote results couple of days before. Not sure what happened.
I just resent the email. Let me know if you still don't see it.
--
Regards,
Igor
On 12/11/2013, 12:06, Hervé BOUTEMY wrote:
the artifacts
What a splendid idea! This is by far my favourite. Trailed by the Moose
maybe.
We could use a symbolized interpretation of a Raven along the lines of
stencil version might work for small versions with the full
colour at 200px+
On Thursday, 19 December 2013, Paul Benedict wrote:
I like the Raven idea -- especially if you can color the bird with the
Apache feathers look.
On Thu, Dec 19, 2013 at 12:13 PM, Manfred Moser
manf
the gradient used in the Apache feather, though I
think
the solid colour might have more strength.
I'll see if I can find another one to try tracing
On 19 December 2013 20:35, Manfred Moser manf...@simpligility.com wrote:
Thats what I had in mind. Just a stylized version that is simplified
On Dec 20, 2013, at 1:01 PM, Manfred Moser manf...@simpligility.com
wrote:
I would move the Raven closer to the word Maven but otherwise this looks
good imho. Of course I am not sure if everyone would recognize it as a
raven ..
Thats my problem
. doesnt look like a raven to me at all
1 - 100 of 321 matches
Mail list logo
