Ok, trying a different browser (Safari) solved this. Not sure what firefox
is sending to trigger a json answer.
/Anders
On Wed, Apr 10, 2013 at 9:26 AM, Anders Hammar and...@hammar.net wrote:
I get a json answer. Not the UI I was expecting...:-)
/Anders
On Wed, Apr 10, 2013 at 9:16 AM
Looking into this...
/Anders
On Tue, Mar 19, 2013 at 8:36 PM, Stuart McCulloch mccu...@gmail.com wrote:
Misconfigured job? The maven assembly is unpacked to
f:\ws\m3-its\apache-maven-3-SNAPSHOT but the maven.home used in the
following test step is
Fixed.
/Anders
On Tue, Mar 19, 2013 at 9:11 PM, Anders Hammar and...@hammar.net wrote:
Looking into this...
/Anders
On Tue, Mar 19, 2013 at 8:36 PM, Stuart McCulloch mccu...@gmail.comwrote:
Misconfigured job? The maven assembly is unpacked to
f:\ws\m3-its\apache-maven-3-SNAPSHOT
Personally I would like us to stick with the initial discussion of shipping
3.1 with the slf4j usage (and slf4j-simple). That's what we've discussed
and talked about for some time so it would be great to get that out of the
door. The we could discuss the next step. Basically, and generally, I'd
It should be in the same staged repo as the compiler plugin. See that VOTE
thread.
/Anders
On Fri, Mar 8, 2013 at 8:58 AM, Jörg Schaible
joerg.schai...@scalaris.comwrote:
Hi,
this artifact is missing in central:
org.apache.maven.shared:maven-shared-incremental:jar:1.1
+1 (non-binding)
/Anders
On Fri, Mar 1, 2013 at 11:56 PM, Benson Margulies bimargul...@gmail.comwrote:
Hi,
We solved some issues:
** Bug
* [MCHANGES-276] - TracDownloader does not set issue key to ticket id
* [MCHANGES-293] - XML Parser error backtraces from, presumably,
+1 (non-binding)
/Anders
On Sat, Mar 2, 2013 at 4:18 PM, Benson Margulies bimargul...@gmail.comwrote:
Based on the sentiment on the discussion thread, I call a formal vote
to end support for Maven 1.x. This is a vote to:
1: Remove maven 1 release materials from the primary distribution
You should post this question to the users list. This list of for
developing Maven itself and the core plugins.
/Anders
On Thu, Feb 28, 2013 at 3:13 PM, jkm123 asur...@virtusa.com wrote:
Hi All,
I am setting up maven project of spring mvc using my id sts.
I created the project using New
+1 on giving people one week from the Jason's initial mail in this thread.
Will the release be a RC or the real deal? We've had this discussion before
and I honestly don't remember what we decided, but I think cutting a RC
first for core is good. So maybe cut a RC now and have us/people test that
Yes, this line is not really true:
Note that *no further development* is planned for the Maven-1.0 branch,
and Maven-1.1 is in maintenance mode, i.e. development is restricted to
support and bug fixes.
/Anders
On Wed, Feb 27, 2013 at 7:33 PM, Benson Margulies bimargul...@gmail.comwrote:
I
Welcome!
Hack on,
/Anders
On Fri, Feb 22, 2013 at 10:51 PM, Tony Chemit che...@codelutin.com wrote:
On Fri, 22 Feb 2013 22:46:51 +0100
Arnaud Héritier aherit...@gmail.com wrote:
Yep, Welcome Andreas ;)
tony.
Welcome Andreas !!!
On Fri, Feb 22, 2013 at 10:42 PM, Olivier Lamy
+1 (non-binding)
Please not that MNG-5402 and MNG-5403 seems to have been backported to this
release as well. The build number (MNG-5402) is reported slightly different
on the 3.0.x branch though (it has a r prefix which is removed in the
3.1.x branch).
/Anders
On Tue, Feb 19, 2013 at 4:28 PM,
Those artifacts have been released (v2.4), so we need to update out poms.
Until then you can do that yourself locally.
/Anders
On Mon, Feb 18, 2013 at 4:35 PM, Francesco Mari mari.france...@gmail.comwrote:
Hi,
I tried to build Maven from scratch. I have the following error when
building
http://jira.codehaus.org/browse/MNG-5430
Looks like Olivier fixed this so try updating from the repo. Btw, you are
using the new git repo and not the old svn repo?
/Anders
On Mon, Feb 18, 2013 at 4:44 PM, Anders Hammar and...@hammar.net wrote:
Those artifacts have been released (v2.4), so we
.**com stephen.alan.conno...@gmail.com:
You miss my point. Give an example of how to configure such a release
profile. Plus how would recompression being on break things? Is the jar
spec that weak?
On Monday, 11 February 2013, Anders Hammar wrote:
Given that people don't do applets any more
*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*
http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2013/2/8 Anders Hammar and...@hammar.net
Apache Maven is not Ant. And not even remotely related.
:-)
On the more serious side: Based on a recent discussion on the mailing list
we should probably get some wording in there that it has infrastructure
dependencies, i.e. requires a repository (manager):
Apache Maven is *the* opinionated
on break things? Is the jar
spec that weak?
On Monday, 11 February 2013, Anders Hammar wrote:
Given that people don't do applets any more, and most app servers
explode
the .wars anyway, speed should be king. I'd give an example of turning
it
on for the release profile though on the project
In general, I think that the default value should be whatever works in most
cases. Then we could have params for tweaking this (for better performance
e.g. in specific cases), but it would be up to the user to do this.
So, in this specific case, I think the default should be to recompress so
that
0
It would have been good to get v1.8 of m-invoker-p in maven-plugins while
we're at it.
/Anders
On Wed, Jan 30, 2013 at 12:40 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Plugins parent 24 and Shared parent 19.
Staging repository:
I see two of these comments:
!-- TODO remove when upgrading parent to 23 --
And we're using maven-parent v23.
/Anders
On Wed, Jan 30, 2013 at 6:38 AM, Kristian Rosenvold
kristian.rosenv...@zenior.no wrote:
+1
Den 30. jan. 2013 kl. 00:41 skrev Olivier Lamy ol...@apache.org:
Hi,
I'd
improve performance with
reducing the number of transfered bytes when downloaded the pom :-)
Perso I won't consider this as blocker as we are talking about a pom
release so any sub project can override values.
2013/1/30 Anders Hammar and...@hammar.net:
I see two of these comments:
!-- TODO
Just want to check what the general opinion is about changing method
signatures of Plexus component interfaces in our plugins for a minor
version release.
In a perfect world it would be awesome to always keep backwards
compatibility and at least never do any changes unless a major version. But
as
PM, Olivier Lamy ol...@apache.org wrote:
+1
And the patch is a signature change on a private method so not a real
issue.
2013/1/29 Anders Hammar and...@hammar.net:
Just want to check what the general opinion is about changing method
signatures of Plexus component interfaces in our plugins
It's defined in the super-POM.
So, the Ant script used Maven Ant tasks to read the POM for building Maven.
That POM inherits from the super-POM, where that repo is defined.
/Anders
On Tue, Jan 22, 2013 at 1:31 PM, Shixiang Wen wsxwin...@yahoo.com.cnwrote:
Hi,
I will try the solution below.
On Mon, Jan 21, 2013 at 1:11 PM, Chris Graham chrisgw...@gmail.com wrote:
Now I know
that this is wrong
Well, I believe you're answering your own question here. :-) You have an
issue in your project that the old version accepted.
/Anders
Are you behind a web proxy? If so, I belive you need to configure this. I
don't personally build Maven with ant, so I don't know how but there should
be a clue somewhere (maybe in build.xml?).
The http://repo1.maven.org/maven2 repo is fine. That's not the problem
here.
/Anders
On Tue, Jan 22,
I agree. I think 2.5.1 of the m-compiler-p is a better choice.
/Anders
On Sat, Jan 19, 2013 at 10:54 AM, Tony Chemit che...@codelutin.com wrote:
On Thu, 17 Jan 2013 21:17:35 +0100
Olivier Lamy ol...@apache.org wrote:
+0.
m-compiler-p to 3.0 is it a real good idea ?
I tried it, and it
/browse/MNG-5403
Project: Maven 2 3
Issue Type: Bug
Components: General
Affects Versions: 3.1.0
Reporter: jieryn
Assignee: Anders Hammar
Priority: Trivial
Fix For: 3.0, 3.1.0
As part of the release
I've always been under the impression that one should use the property
project.basedir instead of just basedir. Is that true or just my own
interpretation?
/Anders
of
memory.
On Dec 16, 2012, at 2:43 PM, Anders Hammar and...@hammar.net
wrote:
The pattern I see is that all jobs that build with JDK 1.5 hangs.
This
includes the windows node.
/Anders
On Sun, Dec 16, 2012 at 7:10 PM, Dennis Lundberg
denn...@apache.org wrote:
On 2012-12-14
a first step would be to have both bars, instead of top bar replacing left
one
I'm not so sure about this. The basic knowledge I have about UI design is
to never have more than one way to initiate an action. I'm thinking that if
we have to both menu bars showing the same items it will confuse
, at 2:43 PM, Anders Hammar and...@hammar.net wrote:
The pattern I see is that all jobs that build with JDK 1.5 hangs. This
includes the windows node.
/Anders
On Sun, Dec 16, 2012 at 7:10 PM, Dennis Lundberg denn...@apache.org
wrote:
On 2012-12-14 00:29, Brett Porter wrote:
On 13
+1
I think we should keep the old left-hand menu, like what we've done over at
Mojo.
/Anders
On Sat, Dec 29, 2012 at 5:09 PM, Jesse Farinacci jie...@gmail.com wrote:
Greetings,
On Fri, Dec 28, 2012 at 11:21 PM, Kristian Rosenvold
kristian.rosenv...@zenior.no wrote:
There was a comment
No, not adding any metadata. But it could always deploy the attached
artifact, without updating the pom. Don't think Nexus will complain about
that.
/Anders
On Fri, Dec 21, 2012 at 12:50 PM, Benson Margulies bimargul...@gmail.comwrote:
On Fri, Dec 21, 2012 at 12:54 AM, Anders Hammar
The site for m-plugin-p is for 3.1, not the latest 3.2 version. Did
something go wrong in the latest release, or did this happen in the cms
switch?
/Anders
, Olivier Lamy ol...@apache.org wrote:
2012/12/20 Anders Hammar and...@hammar.net:
The site for m-plugin-p is for 3.1, not the latest 3.2 version. Did
something go wrong in the latest release, or did this happen in the cms
switch?
must work.
Nobody upgraded that.
So feel free to test it and do
...@apache.org:
2012/12/20 Anders Hammar and...@hammar.net:
Would be happy to do it, but I have to admit that I'm not sure of the
process now. Is the docs [1] correct?
So mvn site-deploy -Preporting on the right version should do it?
I started a bit of documentation here
http
of the maven-plugin-plugin.
Actually, everything under http://maven.apache.org/plugin-tools/ refers
to
3.1 instead of 3.2
Robert
Op Thu, 20 Dec 2012 17:31:35 +0100 schreef Olivier Lamy
ol...@apache.org:
2012/12/20 Anders Hammar and...@hammar.net:
euh I just checked
No, license.excludedGroups is the java system property you specify on
command-line to configure. The name of the parameter itself is what you
configure in the pom.
/Anders
On Fri, Dec 21, 2012 at 2:16 AM, Benson Margulies bimargul...@gmail.comwrote:
@Parameter( property =
You're looking at the wrong place. The xml stuff is listed early in the
build output (before any plugin execution), but what you're looking for is
listed in the beginning of the execution of the plugin in question.
/Anders
On Fri, Dec 21, 2012 at 2:21 AM, Benson Margulies
I see this has been fixed now. Merci!
/Anders
On Thu, Dec 20, 2012 at 10:32 PM, Anders Hammar and...@hammar.net wrote:
Thanks Olivier!
/Anders
On Thu, Dec 20, 2012 at 10:02 PM, Olivier Lamy ol...@apache.org wrote:
oh ok
Apologize my bad I read too fast the acronym from Anders :-)
I
Thanks,Hervé. I have read some maven books and the url link [1]. But
they do not tell us where are the built-in maven properties such as
maven.repo.local and do not tell us if maven3 still support built-in
maven properties like maven1. It is confuing me much!
maven.repo.local is not a built
The pattern I see is that all jobs that build with JDK 1.5 hangs. This
includes the windows node.
/Anders
On Sun, Dec 16, 2012 at 7:10 PM, Dennis Lundberg denn...@apache.org wrote:
On 2012-12-14 00:29, Brett Porter wrote:
On 13/12/2012, at 9:15 PM, Anders Hammar and...@hammar.net wrote
.
Kristian
2012/12/14 Anders Hammar and...@hammar.net:
I see the hanging too... haven't looked into where it gets stuck any
further though. Perhaps it's using an authenticated URL to checkout
additional stuff as part of the bootstrap?
One theory is that it is related to Jave 5 being used
Jenkins has been upgraded to 1.492, which should help
us with the unwanted constant rebuilds in some of our other projects.
Which jobs are hung?
I can only see one: core-integration-testing-maven-3-embedded
On 2012-12-02 20:12, Anders Hammar wrote:
The core-integration-testing-maven-3
Please use the user mailing list for this sort of questions. This list is
for the development of Maven and the core plugins.
/Anders
On Thu, Dec 13, 2012 at 12:46 PM, Urkens Jean-Pierre
jean-pierre.urk...@devoteam.com wrote:
I’m trying to get the generated javadoc on my site. Attached I
I see the hanging too... haven't looked into where it gets stuck any
further though. Perhaps it's using an authenticated URL to checkout
additional stuff as part of the bootstrap?
One theory is that it is related to Jave 5 being used. The JDK 1.6 and 1.7
builds works just fine it seems. The
I'm +1 for logback as the slf4j impl.
/Anders
On Tue, Dec 11, 2012 at 3:32 AM, Jason van Zyl ja...@tesla.io wrote:
Hi,
I looked around a bit more today and I don't think SLF4J Simple is viable
long term, I don't want to patch it anymore as I would have to do a day's
work to make changes
(for 3.1.0) ? What do we do ?
Arnaud
On Sun, Dec 9, 2012 at 10:53 PM, Anders Hammar
and...@hammar.net wrote:
Not sure where to get into this thread, but I'd just like
to add my
perspective on this topic.
For this first release I would prefer it to not include any
designed to or just switch
to Logback. I think I gave it a best effort but I don't want to patch SLF4J
Simple anymore.
On Dec 9, 2012, at 4:53 PM, Anders Hammar and...@hammar.net wrote:
Not sure where to get into this thread, but I'd just like to add my
perspective on this topic
In this context we could push the slf4j introduction to a 3.1 branch
and release 3.0.5 now.
I'm -1 on that. I think the new architectural changes (injection and slf4j)
makes a good package for v3.1. Introducing injections and bug fixes in
3.0.5 should probably argue for a 3.0.6 release for
Yet another example of why overriding the default finalName is a bad idea.
/Anders
On Sun, Dec 9, 2012 at 7:56 PM, Robert Scholte rfscho...@apache.org wrote:
sounds good enough for me.
this is a clear example why you can generate a release-pom.xml
I'll see if I will add a check when
Not sure where to get into this thread, but I'd just like to add my
perspective on this topic.
For this first release I would prefer it to not include any of the more
advanced slf4j implementations, like a few others have already also stated.
Using simple would give us a good start on this new
, 7 December 2012, Mark Struberg wrote:
basically all stuff which integrates maven does *funky
logging
stuff*...
- Original Message -
From: Anders Hammar and...@hammar.net
To: Maven Developers List
dev@maven.apache.org
Cc:
Sent: Friday, December 7, 2012 7:25 AM
It's been fixed. See ticket.
/Anders (mobile)
Den 7 dec 2012 22:46 skrev Mirko Friedenhagen mfriedenha...@gmail.com:
Hello,
artifactory choked on
https://issues.sonatype.org/browse/MVNCENTRAL-271, probably central
wants maven to fix this and sync again. However there is not issue
tracker
I'm interested to help working on adding a metadata to enable slf4j
visibility
from a plugin: by default, slf4j is not visible, plugins are expected to
use
plugin-api's Log. But if the plugin wants to use core's slf4j, he would be
able to add an annotation in the goal requiring shared core
Lennart,
Your attachments are missing.
/Anders
On Thu, Dec 6, 2012 at 11:49 PM, Lennart Jörelid
lennart.jore...@gmail.comwrote:
Hello all,
I have a few reactors where two separate parent poms exist; one parent is
used exclusively for reactor projects [with packagingpom/packaging] and
the
When displaying mvn -version I got :
Apache Maven 3.1.0 (rNON-CANONICAL_2012-12-03_20-03_jvanzyl; 2012-12-04
05:03:32+0100)
Maven home: /opt/maven
I don't understand the revision, Any clue about it ?
MNG-5402
Working on it. Not a show stopper though in my opinion.
/Anders
thanks,
Is the site updated? It says it was published Nov 15 and some info doesn't
seem to be up-to-date (m-war-p says v2.3 for default lifecycle bindings).
/Anders
On Tue, Dec 4, 2012 at 5:10 AM, Jason van Zyl ja...@tesla.io wrote:
Hi,
Here is a link to Jira with 42 issues resolved:
This git repo at Github mirrors the old Git repo. Is it possible to change
that to the new git repo, or should it be removed all together?
/Anders
The core-integration-testing-maven-3 jobs has started to hang since
yesterday morning (whatever timezone the CI is showing). I have no clue how
to figure out why.
/Anders
-testing-maven-3-embedded
On 2012-12-02 20:12, Anders Hammar wrote:
The core-integration-testing-maven-3 jobs has started to hang since
yesterday morning (whatever timezone the CI is showing). I have no clue
how
to figure out why.
/Anders
--
Dennis Lundberg
The Windows node is one, but I believe I saw the same problem on some other
node as well.
/Anders (mobile)
Den 2 dec 2012 22:37 skrev Dennis Lundberg denn...@apache.org:
On 2012-12-02 22:01, Anders Hammar wrote:
It's the core-integration-testing-maven-3 job that hangs. I've aborted
The Windows node is one, but I believe I saw the same problem on some
other node as well.
The same problem on the solaris node as well.
/Anders
/Anders (mobile)
Den 2 dec 2012 22:37 skrev Dennis Lundberg denn...@apache.org:
On 2012-12-02 22:01, Anders Hammar wrote:
It's the core
The core-integration-testing-maven-3 jobs has started to hang since
yesterday morning (whatever timezone the CI is showing). I have no clue how
to figure out why.
I've disabled the core-integration-testing-maven-3 job for now. We're
just blocking other build jobs as it is now.
As I pointed
In any case doing a choice nowadays for 3.1.0 won't prevent us to change it
in the future. I really hope that the ability to switch from a logger
implementation to another won't require several days of developments or I
really missed something about it.
Well, very likely it would affect the
Great. And from the JIRAs I take it that the default m-war-p has been
changed (downgraded to 2.2?).
/Anders
On Fri, Nov 30, 2012 at 9:00 AM, Jason van Zyl ja...@tesla.io wrote:
Just and update on the 3.1.0 saga.
I'm going to fix the NPE in the MavenCli[1] now, and I'm going to chat
with
I'll send a separate thread about the logging options after chatting with
Simon.
I filed MNG-5394 [1] about creating a page on the site where we could
document on how logging should be done in a plugin. This doesn't have to be
done before we release 3.1.0 though as it's a site task.
/Anders
A question from a git rookie:
If we're applying a proper git patch, then the submitted by row shouldn't
be required in the commit message as git will handle this. Right?
/Anders
On Fri, Nov 30, 2012 at 9:04 AM, Olivier Lamy ol...@apache.org wrote:
In the future could we avoid those non
I'll work on the core-integration-testing-maven-3-xxx ones.
/Anders
On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy ol...@apache.org wrote:
I have switched only 2 jenkins jobs:
* https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
*
, Anders Hammar and...@hammar.net wrote:
I'll work on the core-integration-testing-maven-3-xxx ones.
/Anders
On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy ol...@apache.org wrote:
I have switched only 2 jenkins jobs:
* https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
*
https
and I
didn't break any special stuff in there. This job still fails on some ITs
though. Also, the job activates a non-existing profile '
core-integration-testing-maven-3' which should be corrected/removed.
/Anders
On Fri, Nov 30, 2012 at 9:45 AM, Anders Hammar and...@hammar.net wrote:
I'll
Ah, thanks for clarifying. I'll leave it as is then.
/Anders (mobile)
Den 30 nov 2012 20:24 skrev Dennis Lundberg denn...@apache.org:
On 2012-11-30 12:52, Anders Hammar wrote:
* Git doesn't seem to be available on the ubuntu-ARM nodes that the jdk
1.7 job is running on. Kind of surprised
Will the svn repo go read only once we switch, to prevent mistakes?
/Anders
On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
The repos are located at:
https://git-wip-us.apache.org/repos/asf/maven.git
+1 (non-binding)
Did some smaller text fixes to the two new doc pages and re-published. But
links to these pages are missing from the site.
/Anders
On Mon, Nov 26, 2012 at 7:24 AM, Jason van Zyl ja...@tesla.io wrote:
Hi,
Here is a link to Jira with 30 issues resolved:
Should we fix this in all applicable archetypes, and not just this one?
It's in the quickstart as well, and probably others.
/Anders
On Wed, Nov 28, 2012 at 9:44 AM, Olivier Lamy ol...@apache.org wrote:
ok I will re spin the release due to this old blocker issue :P
2012/11/27 Ansgar
-0
The created sample IT has a few minor issues IMO. I've fixed this in
r1414609. Your call if you have the energy to re-spin for this or leave it
to the next release.
/Anders
On Wed, Nov 28, 2012 at 9:54 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release the archetype for
Testing I now noticed this output:
[WARNING]
Goal prefix is specified as: 'archtst-maven-plugin'. Maven currently
expects it to be 'archtst'.
I never configure goalPrefix, do we need that? As it is now, using the
artifactId isn't really correct.
/Anders
On Wed, Nov 28, 2012 at 11:03 AM,
I don't think we should have http://maven.apache.org as the default. People
go with defaults Maybe http://foo.bar.org? Or just skip it.
/Anders
On Wed, Nov 28, 2012 at 1:24 PM, Brett Porter br...@apache.org wrote:
What about making it an archetype parameter? e.g.
Nope, I'm +1 with everything else. I'll file a ticket for the warning and
fix it.
/Anders
On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy ol...@apache.org wrote:
Perso, I won't consider that as blocker.
Any other troubles ?
2012/11/28 Anders Hammar and...@hammar.net:
Testing I now
28, 2012 at 2:32 PM, Anders Hammar and...@hammar.net wrote:
Nope, I'm +1 with everything else. I'll file a ticket for the warning and
fix it.
/Anders
On Wed, Nov 28, 2012 at 1:59 PM, Olivier Lamy ol...@apache.org wrote:
Perso, I won't consider that as blocker.
Any other troubles
I see we have different formats of the versions in the MARCHETYPES project
in JIRA. I see 5, 1.1 and maven-archetype-plugin-1.2 for example.
If I fix a ticket, what should I set the fix versions as? Are we going to
keep separate release flows for each component or are we going to release
them all
Ok, separate releases it is then. I'll do some cleaning in the JIRA project.
/Anders
On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy ol...@apache.org wrote:
2012/11/28 Anders Hammar and...@hammar.net:
I see we have different formats of the versions in the MARCHETYPES
project
in JIRA. I see
Btw, anyone against changing 5 to parent-5 to remove some confusion
with the older 1.1 etc?
/Anders
On Wed, Nov 28, 2012 at 9:14 PM, Anders Hammar and...@hammar.net wrote:
Ok, separate releases it is then. I'll do some cleaning in the JIRA
project.
/Anders
On Wed, Nov 28, 2012 at 9:12
. There is currently only 14 closed ticket, and those that will
loose a fix version could get back-tracked if it would turn out to be of
interest (which I doubt). Anyone against?
/Anders
On Wed, Nov 28, 2012 at 9:12 PM, Olivier Lamy ol...@apache.org wrote:
2012/11/28 Anders Hammar
does not have any kind of
license header.
/Anders
/Anders
On Wed, Nov 28, 2012 at 2:32 PM, Anders Hammar and...@hammar.net
wrote:
Nope, I'm +1 with everything else. I'll file a ticket for the warning
and
fix it.
/Anders
On Wed, Nov 28, 2012 at 1:59 PM, Olivier
How do I interpret the Final Memory reported by Maven? 66M/188M for
example, what does each of the figures mean?
/Anders
So the second figure isn't affected by Maven?
/Anders
On Tue, Nov 27, 2012 at 9:44 AM, Olivier Lamy ol...@apache.org wrote:
2012/11/27 Anders Hammar and...@hammar.net:
How do I interpret the Final Memory reported by Maven? 66M/188M for
example, what does each of the figures mean
+1 for removing it! Or at least change it to something that strongly
suggest updating it.
/Anders
On Tue, Nov 27, 2012 at 9:45 PM, Olivier Lamy ol...@apache.org wrote:
2012/11/27 Robert Scholte rfscho...@apache.org:
Hi Olivier,
looks like a very nice and useful archetype.
the
As we had some issues with an earlier staged Maven version (was it 3.0.4?)
and releasing (something with nginx in front of nexus), it would be great
if we could verify that we don't release something with an similar issue.
So, anyone doing a release the coming days please use the staged 3.1.0!
-1
MNG-5381 is not fixed. Let's follow up in that ticket.
/Anders
On Sun, Nov 25, 2012 at 7:37 PM, Benson Margulies bimargul...@gmail.comwrote:
Jason, this email is missing the specific link to the buildable source
bundle which is part of the current release vote template. Since
Apache
How would you attach an artifact with a DIFFERENT artifactId than the
project? It doesn't make sense.
I would vote for doing changes that make it impossible to use the plugin as
I-would-like-to-create-any-file-the-way-i-used-to-with-Ant solution. I
think that the possibilities to alter the final
How would you attach an artifact with a DIFFERENT artifactId than the
project? It doesn't make sense.
This is *already* a feature of the plugin. I didn't invent it, I'm
just trying to clean up how your configure it.
Why would you try to clean up how to configure something that doesn't
with a different
artifactId, but rather that we're using the model object (Artifact). I
would hope that it will throw an exception if the artifactId isn't the same
as the project's.
/Anders
On Sun, Nov 25, 2012 at 2:06 PM, Anders Hammar and...@hammar.net wrote:
How would you attach an artifact
this feature, let alone
the naked MavenProject API.
On Sun, Nov 25, 2012 at 2:06 PM, Anders Hammar and...@hammar.net
wrote:
How would you attach an artifact with a DIFFERENT artifactId than
the
project? It doesn't make sense.
This is *already* a feature of the plugin. I didn't
doing something
similar, not making a claim that it's right or wrong to do so.)
Anders Hammar and...@hammar.net wrote:
How would you attach an artifact with a DIFFERENT artifactId than the
project? It doesn't make sense.
I would vote for doing changes that make it impossible to use
+1 (non-binding)
/Anders
On Sat, Nov 24, 2012 at 10:13 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
+1 (non-binding) tested with two personal projects and the trunk of
the extra-enforcer-rules from codehaus.
Regards Mirko
On Fri, Nov 23, 2012 at 7:04 PM, Robert Scholte
Not sure I follow. I work on core just fine in Eclipse with m2e. No need
for it to understand build.xml, it uses the pom.
/Anders
On Sat, Nov 24, 2012 at 11:38 PM, Benson Margulies bimargul...@gmail.comwrote:
When i import the trunk into intellij, the plexus annotations are
missing. And
MVNCENTRAL-266 filed.
/Anders (mobile)
Den 23 nov 2012 14:22 skrev Benson Margulies bimargul...@gmail.com:
A user claims it's trashed. How is it maintained?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
301 - 400 of 568 matches
Mail list logo
