+1, twice. (nb)
The list of examples on the plugin's site's index page isn't complete. I'll
fix that on trunk.
/Anders
On Thu, Nov 22, 2012 at 10:00 AM, Olivier Lamy ol...@apache.org wrote:
2 * +1
2012/11/20 Arnaud HERITIER aherit...@apache.org:
Hi,
Sorry for the long delay since the
I fixed a few non-working internal links as well.
/Anders
On Thu, Nov 22, 2012 at 5:04 PM, Arnaud Héritier aherit...@gmail.comwrote:
I didn't see it. Thx.
Arnaud
On Thu, Nov 22, 2012 at 1:32 PM, Anders Hammar and...@hammar.net wrote:
+1, twice. (nb)
The list of examples
This has been fixed on trunk:
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml?view=markup
/Anders
On Tue, Nov 20, 2012 at 9:06 PM, Manfred Moser manf...@mosabuam.com wrote:
Hi all!
Just a question out of curiosity for the
The Maven dev list is not the appropriate mailing list for this question. I
would try the Nexus user list or the tycho user list.
/Anders
On Mon, Nov 19, 2012 at 9:12 AM, kai.zimmermann
kai.zimmerm...@robotron.dewrote:
Hi guys,
I'm looking for a better solution for a problem, I solved it
+1 (non-binding)
tested with jdk 1.6 javac.
/Anders
On Sun, Nov 18, 2012 at 1:27 PM, Robert Scholte rfscho...@apache.orgwrote:
+1
Op Sat, 17 Nov 2012 12:26:09 +0100 schreef Hervé BOUTEMY
herve.bout...@free.fr:
+1
Regards,
Hervé
Le vendredi 16 novembre 2012 00:36:20 Olivier Lamy
I'm confused here. org.apache.maven.plugins:maven-ejb3-plugin doesn't
exist! I didn't even know there was an ejb3 packaging type.
/Anders
On Fri, Nov 16, 2012 at 9:29 PM, Karl Heinz Marbaise khmarba...@gmx.dewrote:
Hi,
now coming up with an other question (related to MNG-5245):
I'm
A very big +1 for 6-8 weeks release cycles for core!
/Anders
On Tue, Nov 13, 2012 at 9:25 PM, Jason van Zyl ja...@tesla.io wrote:
I have put together a simple roadmap using JIRA macros in Confluence to
try and communicate to users what we're planning to do.
Changes looks good for me.
Thanks for having a look!
One specific thing I'm not sure about is the maven-security artifactId. Is
it good, or should we maybe use maven-crypto. maven-security could in the
future contain more than the crypto things.
Most of the large changes has been done Karin
much noise around it but the initial discussion. Haven't been involved so
it's just the view of a bystander.
/Anders
2012/11/12 Anders Hammar and...@hammar.net:
I'm done. Please go ahead and release it!
/Anders
On Mon, Nov 12, 2012 at 8:22 AM, Anders Hammar and...@hammar.net
wrote
Ok. I'll see to that she signs a cla.
/Anders (mobile)
Den 13 nov 2012 17:28 skrev Stephen Connolly
stephen.alan.conno...@gmail.com:
On 13 November 2012 15:04, Olivier Lamy ol...@apache.org wrote:
2012/11/13 Anders Hammar and...@hammar.net:
Changes looks good for me.
Thanks
I'm done. Please go ahead and release it!
/Anders
On Mon, Nov 12, 2012 at 8:22 AM, Anders Hammar and...@hammar.net wrote:
Give me some hours, I think there's at least one JIRA ticket that I want
to close as fixed.
/Anders
On Mon, Nov 12, 2012 at 1:03 AM, Olivier Lamy ol...@apache.org
-
From: Anders Hammar and...@hammar.net
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Monday, November 12, 2012 8:22 AM
Subject: Re: Maven Compiler 3.0 plugin release
G ive me some hours, I think there's at least one JIRA ticket that I want
to
close as fixed
If I speed things up on MNG-5356, would anyone object to get that into
3.1.0 as well?
/Anders
On Sun, Nov 11, 2012 at 5:58 AM, Jason van Zyl ja...@tesla.io wrote:
I have more cycles now, so I'd like to propose a tentative release
schedule for the core and get some changes pushed out.
3.1.0
Here's my suggestion:
We keep the current state where we have the new logging API (slf4j) and the
System.out style implementation. Then we (Olivier?) create a JIRA ticket
for moving to a different logging implementation using a more flexible
logging framework. Then we discuss the benefits of
Give me some hours, I think there's at least one JIRA ticket that I want to
close as fixed.
/Anders
On Mon, Nov 12, 2012 at 1:03 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Some improvements has been made for compiler plugin.
Thanks to all folks who participate !
So now the compiler will
Thanks Olivier! It should be rocking now, hopefully.
/Anders
On Thu, Nov 8, 2012 at 3:34 PM, Olivier Lamy ol...@apache.org wrote:
done
2012/11/8 Anders Hammar and...@hammar.net:
I've sent a pull requests which, IMHO, cleans things up in the javac
part.
Mainly I've focused on having
as there is a new snapshot of plexus-compiler deployed.
/Anders
On Mon, Oct 29, 2012 at 11:09 PM, Anders Hammar and...@hammar.net wrote:
I've added comments to the pull request itself.
/Anders
On Sun, Oct 28, 2012 at 10:42 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
So have a look at those changes
/10/19 Anders Hammar and...@hammar.net:
Changing the version number to 2.0 is not good enough to make
incompatible changes, due to the working of dependency resolution.
Sure it is, out of a configuration management perspective. Out of a
Maven dep resolution perspective it might not be optimal
It's just a few lines of code - what could go wrong? :-)
There's no IT for this. Have you tested it with your problematic use
case? (was it site:run?)
All the existing ITs pass on Java 1.6.0_31 on MacOS 10.7.
I don't see any errors in the code. The only thing I'm thinking about
is if
What platform and where to you get that?
I don't get that with 3.0.4 on Mac OS 10.7 and Apple Java 1.6. Two of
the its fail though.
[ERROR] The following builds failed:
[ERROR] * purge-local-repository-reresolve/pom.xml
[ERROR] * purge-local-repository-version-range/pom.xml
/Anders
On Tue,
Cool!
/Anders
On Wed, Oct 24, 2012 at 10:02 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I like. Pictures make the team feel more human and concrete.
-Stephen
On 24 October 2012 08:56, Kristian Rosenvold
kristian.rosenv...@gmail.comwrote:
I just hacked together a quick
What platform and where to you get that?
I don't get that with 3.0.4 on Mac OS 10.7 and Apple Java 1.6. Two of
the its fail though.
MacOSX Mountain Lion and Java 1.6 from apple. The same error below
also happens when I try the analyze-report report plugin with the
2.6-SNAPSHOT.
Strange
As long as the failing ITs have corresponding JIRAs I think this is good.
/Anders
On Thu, Oct 25, 2012 at 7:15 AM, Paul Gier pg...@redhat.com wrote:
You're right, the maven dependency tree API ran into the same issue.
Since using the plugin annotation for automatic resolution didn't make
the
Just a question regarding plexus-compiler: Is it known to be used by
anything but the m-compiler-p? As we're bumping to v2.0, how about
breaking backwards compatibility? I'm thinking that we should change
the signature of Compiler.compile so that it doesn't just return a
list of messages, but
Changing the version number to 2.0 is not good enough to make
incompatible changes, due to the working of dependency resolution.
Sure it is, out of a configuration management perspective. Out of a
Maven dep resolution perspective it might not be optimal. Preserving
backwards compatibility is
Any specific reason we're not configuring the memory for this CI job?
It has never run successfully; can we disable it?
/Anders
-- Forwarded message --
From: Apache Jenkins Server jenk...@builds.apache.org
Date: Sat, Oct 13, 2012 at 12:37 AM
Subject: Build failed in Jenkins:
In the context of Maven, is there any added value in pluging having a
separated logging environment? If there is no added value, then merged
logging is the way to go.
Could one possible case be a plugin which embeds some framework
which uses slf4j to log to it's own log file(s)? And in this
If all logging from the embedded framework gets directed to the Maven
output console, it could get messy. I'm thinking something like how
the surefire plugin works where the user is directed to the surefire
reports for further problem info (stacktraces etc.)
those would be the cases where the
be a good place to start and then add
more advanced possibilities if needed. Keep it simple.
/Anders
On Oct 12, 2012, at 8:12 AM, Anders Hammar and...@hammar.net wrote:
In the context of Maven, is there any added value in pluging having a
separated logging environment? If there is no added
seem to
recall that a couple of it's failed due to this).
I say we do the 3.1 release off git ;) Move both.
Kristian
2012/10/10 Anders Hammar and...@hammar.net:
I see no reason they need to be migrate at the same time.
/Anders
On Wed, Oct 10, 2012 at 7:53 PM, Jason van Zyl ja...@tesla.io
Are we then also saying that we merge the maven-2 source into this git
repo as well (if we convert that to git)?
/Anders
On Thu, Oct 11, 2012 at 10:01 AM, Arnaud Héritier aherit...@gmail.com wrote:
As far as it is always possible (and easy) to do (and to setup on CI side
as it will be the
Just to get this clear in my head:
When you're talking about slf4j dependency in a plugin, are you
talking about dependency to slf4j-api or an slf4j impl?
/Anders
On Thu, Oct 11, 2012 at 10:16 AM, ceki c...@qos.ch wrote:
On 11.10.2012 08:37, Mark Struberg wrote:
Hi Mark,
Hi Ceki, thanks for
A plugin declaring a dependency on slf4j-api without declaring a
dependency on an implementation does not makes sense imo. It follows
that the term declaring a dependency on slf4j means a dependency on
both slf4j-api as well as a binding, aka implementation.
If the get the slf4j logger
We should clarify that this is for Maven 3.1+, not Maven 3.0.x or Maven 2.
/Anders
On Thu, Oct 11, 2012 at 4:11 PM, Jason van Zyl ja...@tesla.io wrote:
That's fine, users don't seem to mind.
I pretty much have a zero turn around for writing docs using the system I
have so that's I'm going
+1
The correct url for the staged site is:
http://maven.apache.org/plugins/maven-source-plugin-2.2.1/
I found a few non-working links in the site. I've filed MSOURCES-63
for that and will take care of them for the next release.
/Anders
On Wed, Oct 10, 2012 at 7:32 AM, Stephane Nicoll
It looks like you don't create account in JIRA any longer, but it is
driven from Xircles.
/Anders
On Wed, Oct 10, 2012 at 10:25 AM, Luca Tagliani l.tagli...@cbt.it wrote:
But I can't see a way to create a Jira account...
Not from xircles neither from Jira itself
BR
Luca
--
View this
I see no reason they need to be migrate at the same time.
/Anders
On Wed, Oct 10, 2012 at 7:53 PM, Jason van Zyl ja...@tesla.io wrote:
So in chatting with Kristian it appears the the core is ready to flip, while
the integration tests need some work. Can we flip the core and work on the
core
of it's failed due to this).
I say we do the 3.1 release off git ;) Move both.
Kristian
2012/10/10 Anders Hammar and...@hammar.net:
I see no reason they need to be migrate at the same time.
/Anders
On Wed, Oct 10, 2012 at 7:53 PM, Jason van Zyl ja...@tesla.io wrote:
So in chatting
How come not v2.2.1?
/Anders
On Tue, Oct 9, 2012 at 11:20 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
I'd like to release Maven Sources Plugin 2.3.
We fix 1 blocking issue which prevent some users to upgrade:
http://jira.codehaus.org/browse/MSOURCES-62
Staging repository:
Didn't catch the pun, but to clarify: This release only includes a bug
fix. Why are we not doing a bug fix release (thus, 2.2.1) but a minor
release?
/Anders
On Tue, Oct 9, 2012 at 12:10 PM, Arnaud Héritier aherit...@gmail.com wrote:
Not false :-)
On Tue, Oct 9, 2012 at 11:55 AM, Anders
in a bug fix release).
/Anders
/Anders
On Tue, Oct 9, 2012 at 12:10 PM, Arnaud Héritier aherit...@gmail.com wrote:
Not false :-)
On Tue, Oct 9, 2012 at 11:55 AM, Anders Hammar and...@hammar.net wrote:
How come not v2.2.1?
/Anders
On Tue, Oct 9, 2012 at 11:20 AM, Olivier Lamy ol
a
couple of those.
/Anders
On Thu, Oct 4, 2012 at 8:15 AM, Kristian Rosenvold
kristian.rosenv...@zenior.no wrote:
As long as we have a real and uncontroversial 3.1 change I'm happy
about investing in a new version number ;)
Kristian
Den 3. okt. 2012 kl. 21:58 skrev Anders Hammar and...@hammar.net
When using Maven in enterprise environments I often find in annoying
that encrypting passwords is a hassle to set up. I would like to have
the possibility to simplify this by, for example, re-using some
existing solution. I've created MNG-5356 to track this.
Looking at the code though, the
That will probably require to bump core version to 3.1 :-)
Right, I'd like to get this into the planned 3.1 release.
Thanks for bringing this up. :-)
For the ITs, I think it would be good if we bumped the version of core
to 3.1-SNAPSHOT as we then can correctly specify what versions these
new
I've filed MNG-5352 to monitor an upgrade in core to this new version of Sisu.
/Anders
On Thu, Sep 27, 2012 at 9:18 PM, Stuart McCulloch mccu...@gmail.com wrote:
Hi folks,
Just wanted to give an update regarding the status of
http://eclipse.org/sisu/ as it's been a while(!) since we started
+1 non-binding
Tested with Maven core.
/Anders
PS: Are we to use the fluido skin for all plugins?
On Tue, Sep 25, 2012 at 2:37 PM, Olivier Lamy ol...@apache.org wrote:
+1
2012/9/24 Kristian Rosenvold kristian.rosenv...@gmail.com:
Hi,
We solved 6 issues:
I have not seen anything other than CVS using the tag but that could
just be ignorance on everyones part ;-)
ClearCase uses it. But it's ok to ignore that scm...:-)
/Anders
Also I don't think that using tag to convey a git branch is a good
plan... put perhaps setting it for the
Unfortunately it's a fair amount of larger organizations that use it.
So it can't be ignored in reality IMHO.
/Anders
On Fri, Sep 21, 2012 at 3:11 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 21 September 2012 13:59, Anders Hammar and...@hammar.net wrote:
I have not seen
Isn't it a little bit of overkill to do a release for this? Why not
just simply replace that page on the site? Keep it simple...
/Anders
On Wed, Sep 19, 2012 at 7:58 PM, Benson Margulies bimargul...@gmail.com wrote:
A typical thing for people to do is to google for maven-foo, find the
But this reminds me of another ancient peeve: the process of making
the release tends to make the SCM page point at the release tag, not
the trunk. I wish it were otherwise.
Yes, this is true and there was some user complaining about this not
too long ago. He used that link and checked out
No one is objecting on 3.1 so I'll bump the version on trunk.
/Anders
On Sat, Sep 15, 2012 at 11:30 AM, Olivier Lamy ol...@apache.org wrote:
Ping
--
Olivier
Le 10 sept. 2012 09:02, Olivier Lamy ol...@apache.org a écrit :
Le 9 sept. 2012 15:44, Jason van Zyl ja...@tesla.io a écrit :
I
First of all I think we should remove Brian as assignee. I doubt he's
going to work on it.
/Anders
On Sun, Sep 16, 2012 at 8:09 PM, Benson Margulies bimargul...@gmail.com wrote:
https://jira.codehaus.org/browse/MNG-3283
Anyone got an idea for how we could organize ourselves to find and
deal
features. If I'm
doing the next release (which I've announced) I'll bump the version
number when the tests are in place. The next release is still a few
weeks off, so there should be plenty of time for that.
Kristian
2012/9/16 Anders Hammar and...@hammar.net:
No one is objecting on 3.1 so I'll
I *think* this issue was mentioned by someone on this mailing list not
too long ago.
Please create a small project that reproduces this. Then create a jira
and attach it. Then that project could be used as an IT. If you could
create it as an IT (with a verify script) that would be even better.
Yes, Snapshot is not good. PointInTime?
/Anders
On Fri, Sep 14, 2012 at 3:03 PM, Mark Struberg strub...@yahoo.de wrote:
Hi!
If anyone has a better name for the 'DirectorySnapshotScanner' I would be
happy to rename it.
What it makes: it takes a snapshot capture of a directory structure and
Should MINDEXER-60 really have a fix version as it is won't fix? It
could trick people just browsing the list of tickets associated with
this relaese to think this has been introduced.
/Anders
On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák ta...@cservenak.net wrote:
Howdy,
there are a
Yes, if we start having stuff spread out in different repos there
should be some other way that Google to find things.
/Anders
On Wed, Sep 12, 2012 at 12:43 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
In the maven projects menu heading on maven.apache.org we expose a
plugins
, Sep 12, 2012 at 11:34 AM, Anders Hammar and...@hammar.net wrote:
Should MINDEXER-60 really have a fix version as it is won't fix? It
could trick people just browsing the list of tickets associated with
this relaese to think this has been introduced.
/Anders
On Wed, Sep 12, 2012 at 11:27 AM
But it would be nice to allow the end user the ability to swap out the
logging implementation if they want.
Yes, that would be very good. I know there's been questions on the
mailing list how to tweak the logging (don't remember exactly what the
wanted to do). So having something that would
I'm fairly sure this didn't work in Maven 2.x. It was one of the
unsolvable Maven 2.x bugs which was fixed in Maven 3. The workaround
would be to use an older released version of the plugin. Don't think
running a build twice is/was a workable workaround as I can't see how
that would work in a
Anyone -1 of bumping to v3.1 for core?
/Anders
On Sat, Sep 8, 2012 at 9:39 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
+1 on bump to 3.1
On Friday, 7 September 2012, Anders Hammar wrote:
I know. But there wasn't much visible change in v3.0 either. And I'm
thinking
in mind, that with the 3.1 we would make the pom-parser more
strict meaning:
- don't warn but fail for plugins without versions
- don't warn but fail for duplicate dependency entries
(there are probably more...)
Robert
Op Sun, 09 Sep 2012 12:31:06 +0200 schreef Anders Hammar
and...@hammar.net
I'll join. :-)
1. Use slf4j-api as our primary facade/api for loggin in Maven. I'm in
favor, because it's much more common and popular than plexus.
Me too. And I'm even arguing we should try to switch to slf4j in core.
Sure, no real technical advantage, but I believe it's easier for other
Maybe this even should bump the version to v3.1?
/Anders
On Fri, Sep 7, 2012 at 5:37 PM, Olivier Lamy ol...@apache.org wrote:
Maybe I miss something but we don't have any associated jira entry for
reference in release notes neither core it test.
Do you have a bit of time for that ?
Thanks
, 2012 at 10:03 PM, Jason van Zyl ja...@tesla.io wrote:
There are no visible user changes, so I don't think so. There aren't even any
changes to integrators unless they want to use take advantage of the changes.
On Sep 7, 2012, at 4:01 PM, Anders Hammar wrote:
Maybe this even should bump
Hi Andreas,
The best way to handle this suggested improvement is to file a JIRA
ticket [1]. You're very welcome to discuss it here at the dev list,
but it always good to keep track of suggested changes in JIRA. Also,
important comments etc should be added to the ticket as well. This is
for future
What you talk about here is something that BuildContext should
provide, if we stay with that. There's a scanner for changes and a
deleteScanner.
The really tricky thing is when one source file has more than one
output/target file (like inner classes). The plugin needs some way of
knowing what
For voting period the candidate files can be committed to the correct
tree here https://dist.apache.org/repos/dist/dev/ (instead of scp to
people.a.o)
This would be for the RCs as well?
Then once the vote has passed releasing is simple copy from
https://dist.apache.org/repos/dist/dev/ to
This would be for the RCs as well?
Sure I will update the procedure as well.
Ok, I'm not sure I see the point. The RCs will never be released and
the whole point of this storage is for released stuff, right? The only
point would be to keep things in dev/ as an archive. Not sure there's
much
+1 (non-binding)
But I don't have the hard-core git knowledge to help out in the move.
Would probably do more harm than good. :-)
/Anders
On Wed, Sep 5, 2012 at 2:19 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
The hosting bit is defined in context of apache, there is not much we
It's up now. The last build with these changes failed though, but it's
when jaring one of the modules. I can't trigger a manual build so I
can't tell if it was a hiccup or what.
/Anders
On Mon, Sep 3, 2012 at 3:13 AM, Jason van Zyl ja...@tesla.io wrote:
I just committed support for JSR330
1) Yes. :-)
2) I also quite surprisingly noticed this as well while converting a
plugin to use BuildContext and making it m2e compatible. IMO it would
be great if DefailtBuildContext could be improved so that will detect
changes. However, there might be some good reason this hasn't been
What kind of privs should I have in (Codehaus) JIRA for the Maven
projects there (as a committer)? I should be be able to edit tickets,
right? Well, I don't... Is there something that needs to be fixed
manually by someone?
/Anders
Doing some reading in the developer section, I see that the example
svnignores ([1]) doesn't really match what seems to be applied to svn.
Is there a recommended value for the svn:ignore property? I'd be happy
to update [1] with that.
Currently it has an example of:
target
*~
*.log
.classpath
to add you in the maven developers group.
what is your identifier ?
Arnaud
On Fri, Aug 31, 2012 at 2:05 PM, Anders Hammar and...@hammar.net wrote:
What kind of privs should I have in (Codehaus) JIRA for the Maven
projects there (as a committer)? I should be be able to edit tickets,
right? Well
Just to verify:
The idea is to set this property on the root folder of any Maven
project, right? Not on all sub-folders as well? The document says on
the directory.
/Anders
On Fri, Aug 31, 2012 at 2:42 PM, Olivier Lamy ol...@apache.org wrote:
2012/8/31 Anders Hammar and...@hammar.net:
Doing
-style.txt
- Original Message -
From: Anders Hammar and...@hammar.net
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Friday, August 31, 2012 2:51 PM
Subject: Re: svn:ignore
Just to verify:
The idea is to set this property on the root folder of any Maven
project, right
I already started tweaking the m-compiler-plugin and found quite scary
issues. There is e.g. MCOMPILER-21 (open since 2005) which prevents
incremental build and would kick in in your scenario.
This is interesting. I've looked a bit at Mojo's JAXB plugin in the
context of detecting stale
LieGrue,
strub
- Original Message -
From: Anders Hammar and...@hammar.net
To: Maven Developers List dev@maven.apache.org
Cc:
Sent: Monday, August 27, 2012 9:57 AM
Subject: Re: improving incremental builds
I already started tweaking the m-compiler-plugin and found quite scary
My take:
For people using an older version of a plugin, it's sometimes easier
to use the doc for that specific version. You will not be confused by
new features that aren't available in the version you're using etc.
BUT, that requires us to clearly publish links to each and every
version so they
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 created ;-)
Welcome Anders!
Glad to see our first “graduate” of the
störa denna överföring...Stort tack
From: herve.bout...@free.fr
To: dev@maven.apache.org
Subject: Re: Welcome Anders Hammar as a committer
Date: Tue, 21 Aug 2012 00:28:33 +0200
Welcome Anders!
Le lundi 20 août 2012 22:31:03 Anders Hammar a écrit :
Thanks Stephen!
Happy to be onboard
After hanging around for some time I thought that I might as well try
out for the Maven dev team.
I guess most of you already know me from the mailing list, JIRA,
and/or Codehaus Mojo. Working with Maven-based dev infrastructure in
my profession I tend to try fixing all defects I run into in my
But you were not talking about an adapter solution, were you?
/Anders (mobile)
Den 6 aug 2012 16.28 skrev Jesse Glick jgl...@cloudbees.com:
On 08/03/2012 09:15 AM, Anders Hammar wrote:
What's the benefit of this approach rather than just having the user
adding the dependencies directly
PM, Jesse Glick jgl...@cloudbees.com wrote:
On 08/02/2012 04:58 AM, Anders Hammar wrote:
not have a dependency on some library in the plugin itself but rely on it
being declared as a dependency in the Maven project where the plugin is
bound. That made it
totally controllable by the project
What I have done in a customer specific plugin, is to not have a
dependency on some library in the plugin itself but rely on it being
declared as a dependency in the Maven project where the plugin is
bound. That made it totally controllable by the project. I don't
remember the exact could, and my
, Jochen Wiedmann
jochen.wiedm...@gmail.com wrote:
On Thu, Aug 2, 2012 at 10:58 AM, Anders Hammar and...@hammar.net wrote:
What I have done in a customer specific plugin, is to not have a
dependency on some library in the plugin itself but rely on it being
declared as a dependency in the Maven
This would be a normal war project, i.e. a Maven project with the
war package type. Then put the html files in the right location.
More info here:
http://maven.apache.org/plugins/maven-war-plugin/usage.html
/Anders
On Thu, Aug 2, 2012 at 7:01 PM, ajoo007 asgar...@gmail.com wrote:
Hi Guys,
I
There is also a bigger problem if someone behind a MRM tries to use
the plugin before available. At least Nexus has a not found cache with
a default ttl of 24 hours. So that would then in effect block access
to it for about a day even when available at central (unless the admin
clears the nfc).
Yes, although it's not good practice. One project should only produce
one main artifact.
To have the maven-war-plugin create an additional jar artifact with
the java classes, have a look at this config parameter:
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#attachClasses
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 maven-war-plugin create an additional jar artifact with
the java classes, have
I've filed MNG-5280 with a patch. Appreciate any input.
/Anders
On Fri, May 25, 2012 at 10:16 AM, Brett Porter br...@apache.org wrote:
Hi,
The issues list wasn't getting mail since Codehaus upgraded JIRA
(https://jira.codehaus.org/browse/HAUS-2232). I've now fixed it, but you
might want
And he has attached strange jars to a bunch of jira tickets. Should
maybe be cleaned up as well.
/Anders
On Wed, May 23, 2012 at 7:43 PM, Mark Hobson markhob...@gmail.com wrote:
Hi,
This guy looks like spam if anyone wants to delete him?
+1 (non-binding)
Thanks Olivier!
/Anders
On Mon, May 21, 2012 at 4:16 PM, LeClaire Garvin
garvin.lecla...@gmail.com wrote:
+1 non-binding
Regards,
Garvin LeClaire
garvin.lecla...@gmail.com
On May 21, 2012, at 9:51 AM, Olivier Lamy wrote:
Hi,
I'd like to release Apache Maven
I'd appreciate spinning a release of this. When staged I can test on
my real corporate use cases. Should be very similar to my test on the
snapshot though, so I don't expect any issues.
/Anders
On Wed, May 2, 2012 at 2:17 PM, Anders Hammar and...@hammar.net wrote:
It's not that easy
, Anders Hammar and...@hammar.net wrote:
I would argue that those are broken projects. You should pretty much
always
use mrm if you are using invoker for testing a maven plugin. There are
cases where you might use invoker for something else, in which case you
should not be specifying
for the corporate use case as well. I also verified the
code and everything seems ok.
On Wed, May 2, 2012 at 2:08 PM, Olivier Lamy ol...@apache.org wrote:
Hi,
AFAIK no rush :-)
So take the time to test your various use cases.
2012/5/2 Anders Hammar and...@hammar.net:
If no settings specified, the maven
...@gmail.com:
On 26 April 2012 13:57, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
On 26 April 2012 13:40, Anders Hammar and...@hammar.net wrote:
I would argue that those are broken projects. You should pretty much
always
use mrm if you are using invoker for testing a maven plugin
The problem I have with using the mrm-maven-plugin is that it would
then require the pom to be updated.
Here's a scenario:
In an environment with no direct access to central but an internal MRM
is used, which is configured in settings.xml. I download some open
source project that uses the
I would argue that those are broken projects. You should pretty much always
use mrm if you are using invoker for testing a maven plugin. There are
cases where you might use invoker for something else, in which case you
should not be specifying a custom settings.xml.
I might be wrong, but this
401 - 500 of 568 matches
Mail list logo
