On Tue, Jul 16, 2013 at 10:07 AM, Arnaud Héritier aherit...@gmail.comwrote:
Hi,
Java 6 EOL was in feb and Maven and its plugins are always compatible
Oracle Java 6 was EOL'd.
IBM Java 6 was, and is not due to be for a few more years. They even
*extended* 1.5's life for a year. Sept this
Michael's point about omiting the trailing .0 is valid, and introducing it
now does not follow the established convention.
Is it going to be cleaned up?
-Chris
On Tue, Jul 16, 2013 at 6:42 AM, Arnaud Héritier aherit...@gmail.comwrote:
lol
On Mon, Jul 15, 2013 at 10:40 PM, Hervé BOUTEMY
:
https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewform
Replies :
https://docs.google.com/forms/d/1Jqxq2KgSricwS7YV7pmWvHA8m7_TE7c8JhusugPmGW4/viewanalytics
On Tue, Jul 16, 2013 at 8:06 AM, Chris Graham chrisgw...@gmail.com
wrote:
On Tue, Jul 16, 2013 at 10:07
On Tue, Jul 16, 2013 at 6:26 PM, Lennart Jörelid
lennart.jore...@gmail.comwrote:
This is not (or should not be) an entirely technical question - support for
various versions of JDK may be the simpler criterion to discuss, but I feel
the more relevant question is
Do we first and foremost see
because the comments apply across all of
them anyway.
Fred.
On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham chrisgw...@gmail.com
wrote:
Hi Arnaud.
You need to at least add an OTHER (ie non oracle) entry as well. You
you can track Oracle java 6 and Non-Oracle java 6.
-Chris
can run
on it
due to basics that are missing there.
I didn't distinguish vendors because the comments apply across all
of
them anyway.
Fred.
On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham
chrisgw...@gmail.com
wrote:
Hi Arnaud
that are missing there.
I didn't distinguish vendors because the comments apply across
all
of
them anyway.
Fred.
On Tue, Jul 16, 2013 at 9:29 AM, Chris Graham
chrisgw...@gmail.com
wrote:
Hi Arnaud.
You need to at least add an OTHER (ie non oracle) entry
:
Chris, we can add this right to the apache nexus and it will be synced
to Central. No need to do a one-off upload. Do you have a list of the
exact files that are missing?
On Thu, Jul 11, 2013 at 1:57 AM, Chris Graham chrisgw...@gmail.com
wrote:
ok, cool. I will go and have a look. Thanks
Hi All.
I'm mavenizing a non-maven project, and it is currently using
jakarta-regexp-1.5.jar which is not in Central, but 1.4 is in Central.
The other release can all be found here:
http://archive.apache.org/dist/jakarta/regexp/
How can we get OS resources such as this into Central?
(Yes, I
...@gmail.com wrote:
On 11 July 2013 13:45, Chris Graham chrisgw...@gmail.com wrote:
Hi All.
I'm mavenizing a non-maven project, and it is currently using
jakarta-regexp-1.5.jar which is not in Central, but 1.4 is in Central.
The other release can all be found here:
http
ok, cool. I will go and have a look. Thanks!
-Chris
On Thu, Jul 11, 2013 at 3:51 PM, Barrie Treloar baerr...@gmail.com wrote:
On 11 July 2013 14:44, Chris Graham chrisgw...@gmail.com wrote:
For an existing, actively developed project, yes.
However, in this case, it's been archived
Hi All.
The full path is:
http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/components-fragment.xml
Can someone please explain to me how this file is used (and why it's not
under the META-INF/plexus dir [at the very least]) ?
I'm struggling to see how it is
plexus-maven-plugin merge the content
I agree that's not the usual place :-)
2013/7/9 Chris Graham chrisgw...@gmail.com:
Hi All.
The full path is:
http://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/src/main/components-fragment.xml
Can someone please explain to me how
/maven-**release-manager/pom.xmlhttp://svn.apache.org/repos/asf/maven/release/trunk/maven-release-manager/pom.xml
plexus-maven-plugin merge the content
I agree that's not the usual place :-)
2013/7/9 Chris Graham chrisgw...@gmail.com:
Hi All.
The full path is:
http://svn.apache.org/repos
In this instance, these files are derived files, so does it matter?
If you re-run the build, the same files should be generated in the same way, so
you get a consistent build.
That is different issue to differences between different releases.
It is also a separate issue to whether the file
On Mon, Jul 8, 2013 at 5:31 AM, sebb seb...@gmail.com wrote:
On 7 July 2013 13:45, Chris Graham chrisgw...@gmail.com wrote:
In this instance, these files are derived files, so does it matter?
I already said that this particular file is probably not an issue.
I think that you missed my
What is in (parenthesis) is a full sentence in it's own right.
Given the personal abuse that I have received recently, and I am aware of
others as well who also have.
I certainly would like the responsibilities highlighted.
Because as they say, with great power comes great responsibility. :-)
It took me a few hours to get that together and I don't have the time right
now to make more revisions, so please just hack away
On 3 July 2013 12:27, Chris Graham chrisgw...@gmail.com wrote:
What is in (parenthesis) is a full sentence in it's own right.
Given the personal abuse that I
On Mon, Jul 1, 2013 at 4:20 AM, sebb seb...@gmail.com wrote:
Reminder: all this thread is just about is adding the following lines
to vote e-mails:
SVN Tag:
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.9.1/
On Mon, Jul 1, 2013 at 7:14 PM, sebb seb...@gmail.com wrote:
On 1 July 2013 07:18, Chris Graham chrisgw...@gmail.com wrote:
On Mon, Jul 1, 2013 at 4:20 AM, sebb seb...@gmail.com wrote:
Reminder: all this thread is just about is adding the following lines
to vote e-mails:
SVN Tag
On Fri, Jun 28, 2013 at 8:35 PM, sebb seb...@gmail.com wrote:
The re-use of tags is a side-issue to this thread, though I'm glad to
see some support for using immutable tags, whatever route is chosen
Please start a new thread to continue that discussion.
We had that discussion, as already
On Fri, Jun 28, 2013 at 9:04 PM, Fred Cooke fred.co...@gmail.com wrote:
In terms of current SVN usage, the SVN mv command is probably a good
choice, as already discussed. You could argue that a cp would be better,
but this creates wholesale duplication, which is never good.
The SVN SCM
Moreover, the discussion is very SVN/GIT centric. The release plugin and
continuum (as far as I know) are the primary users of the SCM api. The
entire scm api is an abstraction layer that is very cvs/svn centric (for
historical reasons) but an abstraction layer all the same, and abstraction
layers
:
On 26 June 2013 01:04, Chris Graham chrisgw...@gmail.com wrote:
-1
Except then the poms will point to the wrong place.
Depends how the poms are updated.
On Wed, Jun 26, 2013 at 10:01 AM, Gary Gregory
garydgreg...@gmail.comwrote:
On Tue, Jun 25, 2013 at 7:14 PM, sebb seb...@gmail.com
This appears to be a variant of the Do we reuse version numbers?
discussion of recent times.
That was resolved.
Can we please not rehash this?
-Chris
On Wed, Jun 26, 2013 at 2:52 AM, sebb seb...@gmail.com wrote:
The mission of the ASF is to release software as source, and to ensure
that the
-1
Except then the poms will point to the wrong place.
On Wed, Jun 26, 2013 at 10:01 AM, Gary Gregory garydgreg...@gmail.comwrote:
On Tue, Jun 25, 2013 at 7:14 PM, sebb seb...@gmail.com wrote:
It would be a lot better to use RC1 RC2 etc initially, and copy the
successful tag to the GA
You havn't done this much have you?
mvn release:perform can be rerun and if you clean it the checkout will
always be into a clean location ./target/checkout/ by default.
On Wed, Jun 26, 2013 at 10:11 AM, sebb seb...@gmail.com wrote:
On 26 June 2013 00:34, Chris Graham chrisgw...@gmail.com
On Wed, Jun 26, 2013 at 10:36 AM, sebb seb...@gmail.com wrote:
However there is also the possibility that vital files are missing
from the source archive.
For that to be detected, a comparison with the SVN tag is needed.
How? Given the source archive is built from the checked out tag?
Use the exec plugin?
-Chris
Sent from my iPhone
On 03/06/2013, at 7:32 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Hi guys,
is there any maven github plugin (or any plan)? the goal would be to get
what we have with gem for instance in ruby world to be able to clone a repo
from
Um, did I miss something, but what is a unreleased (ie for it to be pulled,
then it has to be right?) artifact doing in central to start with?
-Chris
On Tue, Jun 4, 2013 at 3:32 AM, Robert Scholte rfscho...@apache.org wrote:
All nice ideas, but let's go back to a real usecase:
Let's assume
a justification, for this it's just my opinion overriding one of
Maven's core principals.
Stagnation wins.
Fred.
but I may miss some git-fu once again...
Regards,
Hervé
Le samedi 1 juin 2013 20:47:36 Chris Graham a écrit :
but as I see, there seems to be a consensus around a 2-sided rule
. Doing so is the behaviour of a (bad quality) grad
student, not a software development professional!
On Mon, Jun 3, 2013 at 2:31 AM, Chris Graham chrisgw...@gmail.com wrote:
Fred,
We are talking more process here. Not the specifics of an individual SCM,
not everything is in git. We
Le samedi 1 juin 2013 20:47:36 Chris Graham a écrit :
but as I see, there seems to be a consensus around a 2-sided
rule:
- don't reuse version number for pre-releases (RC, etc)
- reuse version number for actual releases
Not sure how I feel about that.
alpha/beta
but as I see, there seems to be a consensus around a 2-sided rule:
- don't reuse version number for pre-releases (RC, etc)
- reuse version number for actual releases
Not sure how I feel about that.
alpha/beta/RCx etc, they are all still valid version nos, so I think that
the no re-spin rule
:-) I use a 4 digit no, but I have special requirements. X.Y.Z.N-SNAPSHOT
etc.
-Chris
On Sat, Jun 1, 2013 at 4:50 PM, Mirko Friedenhagen
mfriedenha...@gmail.comwrote:
And btw. even SNAPSHOTs are nowadays deployed with a timestamp and so more
easily identifiable. I like James approach
Hi James,
What you're talking about here is semantic versioning, and I think that it
a totally different discussion to what we are talking about here.
You've used the example of licencing being wrong. Which should have been
caught, but we are all (mostly) human. :-)
I see this as no different
, I would recommend offering different approaches to
core/plugins/whatever: let's not complicate things.
So, to that end,
-1 (ie respin) for all
(non binding)
-Chris
On Thu, May 30, 2013 at 5:11 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Thursday, 30 May 2013, Chris
.
-Chris
On Thu, May 30, 2013 at 7:55 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 30 May 2013 10:30, Chris Graham chrisgw...@gmail.com wrote:
Thank you Stephen for taking the time to explain.
To me, the key critical bits are:
1. The full normal tag is created
was, quite
literally, very sad. This seems like an opportunity to fix the situation.
I'm baffled by some of the things being said, though.
On Thu, May 30, 2013 at 12:26 PM, Chris Graham chrisgw...@gmail.com
wrote:
One more thing to consider:
It's a huge change; as if you do not delete
, the tag is not a
release.
The only release is the src.tar.gz in the dist folder or the archives.
Tags and binaries are simply a convenience for users.
Whether that is something that is important to the Maven community is a
different question though.
On 30 May 2013 11:26, Chris Graham
, 2013 at 1:58 PM, Chris Graham chrisgw...@gmail.com wrote:
No, by their own rules, if the vote passed, then it's 'valid' release.
That fact that we have more than one release of anything means that we
sometimes get it wrong.
-Chris
On Thu, May 30, 2013 at 8:38 PM, Fred Cooke fred.co
Careful there Stephen, we are talking process here, not the specifics of
the git implementation.
-Chris
On Fri, May 31, 2013 at 6:11 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Thursday, 30 May 2013, Wayne Fay wrote:
On Thu, May 30, 2013 at 4:55 AM, Stephen Connolly ...
What do we currently do for plugins?
What do we currently do for core?
Is there in difference in the approach taken?
We call for a vot for vX.Y.Z of arbitrary plugin (plugins's [recently at
least] do not appear to go throught he beta/RC phases).
Can someone please spell out a sequence of events
Done. issue created.
MNG-5476 http://jira.codehaus.org/browse/MNG-5476 covers it.
-Chris
On Wed, May 8, 2013 at 9:36 AM, Chris Graham chrisgw...@gmail.com wrote:
WIll do, ta.
-Chris
On Tue, May 7, 2013 at 11:42 PM, Stuart McCulloch mccu...@gmail.comwrote:
On 7 May 2013, at 09:00
be the simplest of
test cases.
-Chris
On Tue, May 7, 2013 at 10:17 PM, Stuart McCulloch mccu...@gmail.com wrote:
On 6 May 2013, at 23:49, Chris Graham wrote:
Looking at that issue, if the issue was meant to deal with the example
given, ie, and array of strings, then the issue is most certainly
WIll do, ta.
-Chris
On Tue, May 7, 2013 at 11:42 PM, Stuart McCulloch mccu...@gmail.com wrote:
On 7 May 2013, at 09:00, Chris Graham wrote:
I agree, the way that I have to enter the pom under 2.0.9 is now
correctly
reflected by 3.x.
However, the second part of the issue that I found
Hey All.
I'm not sure if I've found a regression issue with Maven 3.0.x (tried with
all versions beta-1 onwards to 3.0.5) or not. V3.x behaves differently to
2.09, 2.0.11 and 2.2.1.
I've written a plugin for WebSphere Message Broker; basically it's a
wrapper for the underlying mqsicreatebar
2013 23:06:49 Chris Graham a écrit :
Hey All.
I'm not sure if I've found a regression issue with Maven 3.0.x (tried
with
all versions beta-1 onwards to 3.0.5) or not. V3.x behaves differently to
2.09, 2.0.11 and 2.2.1.
I've written a plugin for WebSphere Message Broker; basically it's
Regards,
Hervé
Le lundi 6 mai 2013 23:06:49 Chris Graham a écrit :
Hey All.
I'm not sure if I've found a regression issue with Maven 3.0.x (tried
with
all versions beta-1 onwards to 3.0.5) or not. V3.x behaves differently
to
2.09, 2.0.11 and 2.2.1.
I've written a plugin
: '-DmsgSets=VALUE'
However, maven 3.x does not enforce the @required.
IMHO, it should.
-Chris
PS: Sadly, msgSets/ does not work either under 2.0.9. I needs to be
msgSets
msgSet/
/msgSets
etc
On Tue, May 7, 2013 at 1:49 PM, Chris Graham chrisgw...@gmail.com wrote:
Looking at that issue
What I can add: is that when I was developing archetypes a few years back, the
archetypes I developed did appear in that file. (my memory may be wrong), but I
do not ever remember adding them manually to the file.
Ate there hooks in install/deploy or the archetype plugin to do that?
Just a
:-)
My SCM work on the jazz provider were applied by Oliver. :-)
But yes, I need to find the time to do some meaningful work.
-Chris
On Wed, Mar 20, 2013 at 3:28 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
I don't feel 100% confident on the workings of DOXIA to commit this
Are we removing the disributions (which I didn't that the apache rules
allowed for???) Or just saying that it's not longer supported.
I thought that it was the latter.
-Chris
On Fri, Mar 8, 2013 at 9:43 AM, Benson Margulies bimargul...@gmail.comwrote:
Can someone who knows how splash
Ok, cool. no worries.
-Chris
On Fri, Mar 8, 2013 at 9:50 AM, Benson Margulies bimargul...@gmail.comwrote:
We remove them from the main dist area, leaving them on the archives.
That's the formal policy
On Thu, Mar 7, 2013 at 5:47 PM, Chris Graham chrisgw...@gmail.com wrote:
Are we
+1. Non binding.
Sent from my iPhone
On 03/03/2013, at 2:18 AM, Benson Margulies bimargul...@gmail.com wrote:
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
Ta muchly! To all.
-Chris
Sent from my iPhone
On 23/02/2013, at 6:54 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On Friday, 22 February 2013, Chris Graham wrote:
Hi all.
For a multi module project, eg a root, with three modules A, B and C.
C
Ta muchly! To all.
-Chris
Sent from my iPhone
On 23/02/2013, at 6:54 PM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
On Friday, 22 February 2013, Chris Graham wrote:
Hi all.
For a multi module project, eg a root, with three modules A, B and C. C is
dependent upon A and B
Hi all.
For a multi module project, eg a root, with three modules A, B and C. C is
dependent upon A and B.
I'll written a plugin that performs the packaging of C (actually, it's a
WebSphere Message Broker BAR file).
I have two issues in finding artifacts.
1. Currently I need install to be
He he.
He's not here yet.
-Chris
Sent from my iPhone
On 15/02/2013, at 6:25 PM, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Aah, and I was already wondering wether down-under 72h meant something
different :-).
Regards Mirko
--
Sent from my mobile
On Feb 15, 2013 12:40 AM,
that was part of the sub-release and would contain SNAPSHOT versions for all
others. So if you did a full build of the tag, the exact same output should
be produced.
Hopefully this explains the reasons a little more.
Chris
Von: Chris Graham [chrisgw
If I understand what you've written correctly, you wish to build/release
only parts of your project.
If that is the case, then I a'd advise you to split the projects to in two
separate ones, each with their own trunk etc.
That way when you check out from a tag, you'll be building everything
+1
If you want to trim it a bit, I'd remove the reference to the repo mgr.
Good practice, yes. Needed, no.
-Chris
Sent from my iPhone
On 12/02/2013, at 4:26 PM, Manfred Moser manf...@mosabuam.com wrote:
This is similar to what I've used to describe it to people in the past:
Apache Maven
Sent from my iPhone
On 07/02/2013, at 6:59 PM, Baptiste MATHUS m...@batmat.net wrote:
Le 7 févr. 2013 04:54, Chris Graham chrisgw...@gmail.com a écrit :
Hey All.
Regarding the discussions around upgrading to a minimum of Java 1.6.
Whilst I understand the desire for developers to play
at 10:46 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 7 February 2013 08:58, Chris Graham chrisgw...@gmail.com wrote:
Sent from my iPhone
On 07/02/2013, at 6:59 PM, Baptiste MATHUS m...@batmat.net wrote:
Le 7 févr. 2013 04:54, Chris Graham chrisgw...@gmail.com
Hi Nigel.
On Thu, Feb 7, 2013 at 11:00 PM, Nigel Magnay nigel.mag...@gmail.comwrote:
I am running Maven inside of Jenkins inside of WebSphere on AIX. I am
currently hosting Jenkins under WAS 6.1 on AIX 5.3. Whilst AIX 5.3 is
nearing (or may have reached it's EOS), WAS 6.1's EOS dates
On Fri, Feb 8, 2013 at 11:27 AM, Jesse Glick jgl...@cloudbees.com wrote:
On 02/06/2013 05:23 PM, Mark Struberg wrote:
What are the big features and possibilities we gain from 1.6?
The largest in this context would probably be:
- annotation processors
I'm really vague on this, but wasn't
Hey All.
Regarding the discussions around upgrading to a minimum of Java 1.6.
Whilst I understand the desire for developers to play with something shiny
and new, I do find that the current 1.5 based Maven is more than sufficient
for our needs.
I lot of responses about the upgrade are normally
Hey All.
I've been upgrading our old Java 1.4 builds (using m-c-p 2.3.1 to Java 1.6
using 3.0), and I'm wondering if I've run across a regression issue or not.
The project that I was building generates some source (EJB stubs etc) and
it also appears that the devs have also checked that code in
Which is a change in behaviour.
The question is: Is this a desired change ?
-Chris
On Tue, Jan 22, 2013 at 12:03 AM, Anders Hammar and...@hammar.net wrote:
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
Hey Mirko.
Fair enough. :-)
-Chris
On Tue, Jan 22, 2013 at 10:06 AM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
Hello Chris,
I would desire such a change even if it was unplanned ;-).
Regards Mirko
On Mon, Jan 21, 2013 at 11:54 PM, Chris Graham chrisgw...@gmail.com
wrote
weren't
published.
On 14/01/2013, at 3:52 PM, Chris Graham chrisgw...@gmail.com wrote:
Hi all.
I've just noticed an inconsistency in the versions being shown on the
apache web site:
http://maven.apache.org/**plugins/index.htmlhttp://maven.apache.org/plugins/index.html
shows the m-i-p at 2.4
Yes, be really careful with shading and similar XML stuff, the IBM JRE has
a lot of XML processing in it built in, and it can clash.
-Chris
On Mon, Jan 14, 2013 at 6:39 AM, Benson Margulies bimargul...@gmail.comwrote:
Well, you could scan for the JRE's builtin SPI file and pass the class
Hi all.
I've just noticed an inconsistency in the versions being shown on the
apache web site:
http://maven.apache.org/plugins/index.html
shows the m-i-p at 2.4
whereas, if you follow the link on that page for the m-i-p, it leads to:
http://maven.apache.org/plugins/maven-install-plugin/
+1 for the old placement.
The first time I saw it, it threw me as I though that all of the content had
been lost.
-Chris
Sent from my iPhone
On 01/01/2013, at 10:42 PM, Anders Hammar and...@hammar.net wrote:
+1
I think we should keep the old left-hand menu, like what we've done over at
I got lost (in other work) and this thread a long time ago.
Can someone please remind me just why we are changing the logging at all?
-Chris
On Sun, Dec 9, 2012 at 5:52 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
2012/12/9 Olivier Lamy ol...@apache.org:
Perso I'm fine using
I'd like to know how it is implemented and what happens when it is run on a
terminal that does not support it.
-Chris
Sent from my iPhone
On 08/12/2012, at 8:54 AM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
+1 from me
On Friday, 7 December 2012, Jesse McConnell wrote:
I
it
-
Arnaud
Le 8 déc. 2012 à 11:03, Chris Graham chrisgw...@gmail.com a écrit :
I'd like to know how it is implemented and what happens when it is run on a
terminal that does not support it.
-Chris
Sent from my iPhone
On 08/12/2012, at 8:54 AM, Stephen Connolly stephen.alan.conno...@gmail.com
...@zenior.no
wrote:
Seriously this sounds like something you'd want to configure i.
MAVEN_OPTS, so I'd be inclined to do color by default in 2012, soon
2013.
K
Den 8. des. 2012 kl. 11:14 skrev Chris Graham chrisgw...@gmail.com:
Which is what I thought.
+1 to off by default then.
Sent from
Thanks guys! I appreciate it!
On Fri, Nov 23, 2012 at 8:03 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Hervé Boutemy, Robert Scholte, Olivier Lamy
+1 (non binding): Chris Graham, Tamás Cservenák, Tony Chemit,
I will continue
+1 (non binding)
-Chris
PS: thanks!
Sent from my iPhone
On 20/11/2012, at 9:09 AM, Olivier Lamy ol...@apache.org wrote:
Hi,
Last release is from feb 2007.
We fixed 7 issues: http://s.apache.org/RAR-PLUGIN-2.3
Staging repo: https://repository.apache.org/content/repositories/maven-048/
No worries. Thanks.
-Chris
Sent from my iPhone
On 17/11/2012, at 12:51 AM, Olivier Lamy ol...@apache.org wrote:
My bad I missed that.
After compiler plugin I will release it.
2012/11/16 Chris Graham chrisgw...@gmail.com:
I would like to ask that the 2.3-SNAPSHOT version of the RAR plugin
I prefer classname based, as it is, by definition, definative.
If you're concerned about details getting lost, then might I suggest that
you route that logging output to a separate file? trace.log works for me
(and give a -D to allow users to change that as well).
-Chris
On Fri, Nov 16, 2012
I would like to ask that the 2.3-SNAPSHOT version of the RAR plugin is
released. I've tested it and I'm happy with it.
Thanks,
-Chris
On Mon, Oct 15, 2012 at 11:35 AM, Chris Graham chrisgw...@gmail.com wrote:
Hi All.
I've managed to download, build and successfully test the new 2.3
, Benson Margulies bimargul...@gmail.com wrote:
On Fri, Nov 16, 2012 at 7:03 AM, Chris Graham chrisgw...@gmail.com wrote:
I prefer classname based, as it is, by definition, definative.
If you're concerned about details getting lost, then might I suggest that
you route that logging output
AM, Olivier Lamy ol...@apache.org wrote:
2012/11/16 Jason van Zyl ja...@tesla.io:
On Nov 16, 2012, at 7:30 AM, Benson Margulies bimargul...@gmail.com wrote:
On Fri, Nov 16, 2012 at 7:03 AM, Chris Graham chrisgw...@gmail.com wrote:
I prefer classname based, as it is, by definition, definative
If you're doing down this way, I would strongly recommend the ability not
only to log specific packages, but to be able to set their logging level as
well.
For example, from WebSphere:
Wow! Mind numbing and generally thankless work. But important.
So let me rectify that! Thanks!
-Chris
On Fri, Nov 9, 2012 at 7:53 AM, Robert Scholte rfscho...@apache.org wrote:
Nice job!
It takes some time to do the administration, see if issues are still
valid, etc. but it's really worth
Your key is being refused (for a variety of reasons). That's been the case for
me when I've been prompted for passwords when using keys. Good luck in finding
out why. :-)
-Chris
Sent from my iPhone
On 07/11/2012, at 9:34 AM, Mark Hobson markhob...@gmail.com wrote:
Hi,
I'm trying to
Hi.
I think that I'm missing the point here.
Isn't all of the information that you mention below included in the pom,
and rewritten by the release plugin at release time?
Have I missed something?
-Chris
On Tue, Oct 30, 2012 at 7:31 AM, Karl Pietrzak kap4...@gmail.com wrote:
Hi all!
*WHAT*
1.9 or 1.8.1?
It doesn't appear to be a major change.
-Chris
Sent from my iPhone
On 27/10/2012, at 11:31 PM, Mark Hobson markhob...@gmail.com wrote:
On 26 October 2012 21:14, Olivier Lamy ol...@apache.org wrote:
2012/10/26 Mark Hobson markhob...@gmail.com:
Any objections before I start a
Hi All.
I've managed to download, build and successfully test the new 2.3-SNAPSHOT
of the maven-rar-plugin.
I'm happy with it.
If we could release it, then that would be good.
Thanks,
-Chris
On Sat, Aug 4, 2012 at 10:19 AM, Chris Graham chrisgw...@gmail.com wrote:
:-(
I'm off for two
-
Am 28.09.2012 07:50, schrieb Chris Graham:
Yes, thanks. You've send me back to the drawing board...
On 28/09/2012, at 12:23 AM, Sascha Vogt sascha.v...@gmail.com wrote:
First of all, thank you very much for the explanation. I wasn't aware of
that up to know. Will definitely look
Really?
A plugin can not/should not use another plugin as a dep?
So how is the archiver used? Extended?
-Chris, who is puzzled.
Sent from my iPhone
On 27/09/2012, at 11:07 PM, Jörg Schaible joerg.schai...@scalaris.com wrote:
Hi Sascha,
Sascha Vogt wrote:
Hi all,
I currently have a
Yes, thanks. You've send me back to the drawing board...
-Chris
Sent from my iPhone
On 28/09/2012, at 12:23 AM, Sascha Vogt sascha.v...@gmail.com wrote:
First of all, thank you very much for the explanation. I wasn't aware of
that up to know. Will definitely look into a different solution.
If that is the only reason for the release and it can be fixed in an earlier
release, then I see no reason not too.
This is also in line with the general
Maven ethos of not forcing people to upgrade.
-Chris
Sent from my iPhone
On 24/09/2012, at 6:44 AM, Kristian Rosenvold
+1
Sent from my iPhone
On 25/09/2012, at 6:06 AM, Dennis Lundberg denn...@apache.org wrote:
Hi Kristian
I hate to be the one hitting the brakes on everything Git, but...
...I really think we shouldn't move our release component to Git until
we have ironed out any possible problems
:
Greetings,
On Mon, Sep 24, 2012 at 8:57 PM, Chris Graham chrisgw...@gmail.com wrote:
+1
On 25/09/2012, at 6:06 AM, Dennis Lundberg denn...@apache.org wrote:
I hate to be the one hitting the brakes on everything Git, but...
...I really think we shouldn't move our release component to Git
Sent from my iPhone
On 25/09/2012, at 12:21 PM, Jesse Farinacci jie...@gmail.com wrote:
Greetings,
On Mon, Sep 24, 2012 at 8:57 PM, Chris Graham chrisgw...@gmail.com wrote:
+1
On 25/09/2012, at 6:06 AM, Dennis Lundberg denn...@apache.org wrote:
I hate to be the one hitting the brakes
Sent from my iPhone
On 21/09/2012, at 11: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 anything other than CVS using the tag but that could
just be ignorance on everyones part ;-)
:-)
Humorous yes. True too. The recommendation is one CC SCM admin per 20 devs.
And anders is right. Only the larger organizations can afford that overhead.
But, come audit time, it generally saves them too. :-) Or a PIR of a failure...
-Chris
Sent from my iPhone
On 21/09/2012, at 11:34 PM,
101 - 200 of 315 matches
Mail list logo
