What's the mojo project's view of licenses? Feel free to send it to me.
On Fri, Oct 4, 2013 at 7:46 AM, Anders Hammar wrote:
> Nobody? Pleeease! :-)
>
> /Anders
>
>
> On Sat, Sep 28, 2013 at 2:34 PM, Anders Hammar wrote:
>>
>> I'm looking into doing some improvements on the sqlj-maven-plugin and
I want to use the appassembler to make scripts that are part of a much
larger distro that includes the necessary lib dir; I really just need
the script generation.
Any objection to a parameter for the purpose?
-
To unsubscribe fr
Yes, thanks.
On Thu, Mar 27, 2014 at 11:13 AM, Dennis Lundberg wrote:
> Hi Benson,
>
> There is already a parameter "generateRepository" that if set to
> "false" will skip the repository generation (aka the lib dir).
> Is that what you are looking for?
>
>
khmarbaise marked the 'assemble' goal deprecated. Why? It's extremely
useful to set up command-lines -- completely non-daemon, non-jsw
daemons.
Please explain; I for one am willing to continue to maintain the code
of the assemble goal.
-
THanks. In process.
On Sun, Jun 8, 2014 at 5:44 AM, Karl Heinz Marbaise wrote:
> Hi Benson,
>
>
>> khmarbaise marked the 'assemble' goal deprecated. Why? It's extremely
>>
>> useful to set up command-lines -- completely non-daemon, non-jsw
>> daemons.
>
>
> The revision (15651) your are talking a
aus.org/appassembler/appassembler-maven-plugin/assemble-mojo.html#useWildcardClassPath
>
> Will that help?
>
> Kind regards
> Karl-Heinz Marbaise
>
> On 6/7/14 11:17 PM, Benson Margulies (JIRA) wrote:
>>
>> Benson Margulies
>> <https://jira.codehaus.org/
JSW has a lot of stuff in it that is more than just 'generate
scripts'; it has all those other configuration files that come into
play. So I confess to some small skepticism about the idea that it is
possible to generalize the two. However, my lack of imagination
shouldn't stop someone else.
It se
+1
On Jul 12, 2014 9:36 PM, "Karl Heinz Marbaise" wrote:
> Hi,
>
> I'd like to release version 1.8.1 of the appassembler-maven-plugin
>
> The Application Assembler Plugin is a Maven plugin for generating scripts
> for starting java applications. All dependencies and the artifact of the
> project
On Mon, May 4, 2015 at 8:35 AM, jieryn wrote:
> Apache, and Apache Maven, should just purchase the codehaus.org domain
> name and set a permanent redirect to Apache Maven site.
>
Why? Who cares? There's no important relationship between a Maven gid and a
DNS domain name. Codehaus.org contained t
On Mon, May 4, 2015 at 8:40 AM, Benson Margulies
wrote:
>
>
> On Mon, May 4, 2015 at 8:35 AM, jieryn wrote:
>
>> Apache, and Apache Maven, should just purchase the codehaus.org domain
>> name and set a permanent redirect to Apache Maven site.
>>
>
>
redirect to an Apache page
> > (though I'd prefer to redirect to an Apache page that describes the
> Codehaus
> > shutdown and how things were migrated). I'm not sure whether that's
> > something they'd be up for or not.
> >
> > -Keegan
> >
+1
On Mon, May 4, 2015 at 1:08 PM, Robert Scholte
wrote:
> +1
>
> Op Sun, 03 May 2015 21:48:41 +0200 schreef Baptiste Mathus <
> bmat...@batmat.net>:
>
> Hi all,
>>
>> As a followup to previous threads, I guess it's time for us to try and
>> move
>> on.
>> Indeed, the announcement says services
See the integration test in the source.
On Thu, Aug 25, 2011 at 6:11 AM, Stephen More wrote:
> I see that http://jira.codehaus.org/browse/MCOBERTURA-65 is now closed.
>
> So to test it I did:
>
> svn co
> https://svn.codehaus.org/mojo/trunk/mojo/cobertura-maven-plugin/src/it/mcobertura-65
> cd m
On Mon, Aug 29, 2011 at 5:32 PM, Mark Struberg wrote:
> +1
>
> This discussion has also a legal component!
>
> If someone does work and pushes this stuff to the repo on codehaus, then it's
> crystal clear that this is a contribution to codehaus.
> If one just maintains a 'private' fork on github,
I just dealt with a few low-hanging issues here. Anyone else care to
do anything before releasing?
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
On Tue, Oct 9, 2012 at 1:15 PM, Olivier Lamy wrote:
> 2012/10/8 Benson Margulies :
>> As of svn 1.6, there are no longer svn dirs in each subdir. So,
>> copying 'all' does not give the integration tests anything to work
>> with.
> must be 1.7 I think
>>
Greeting and Salutations,
We solved some issues issues:
Release Notes - Mojo Build Number Maven Plugin - Version 1.2
** Bug
* [MBUILDNUM-1] - javasvn issues, not respecting developerConnection
* [MBUILDNUM-2] - Incorrect regexp in items documentation on
create-mojo.html
* [MBUILDN
Could someone familiar with the mojo parent please cast an eye on the
buildnumber-maven-plugin pom and see if you see why I had such trouble
with the site deployment in release:perform?
-
To unsubscribe from this list, please visi
g else went
wrong, so I perhaps stupidly assumed that the convention was to stick
with 2.2.1.
>> I have created the issue https://jira.codehaus.org/browse/WAGON-379.
>> It's fixed (I will push that soon) I'm doing more tests now.
>>
>> 2012/10/11 Benson Margulie
Hi,
The Mojo team is pleased to announce the release of the Maven
BuildNumber Plugin version 1.2.
The buildnumber plugin sets properties to numbers generates from SCM
revisions or other indications.
You can see more about the plugin at:
http://mojo.codehaus.org/rbuildnumbe-maven-plugin/
To get
; Regards Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/
> https://bitbucket.org/mfriedenhagen/
>
>
> On Mon, Oct 15, 2012 at 9:27 PM, Benson Margulies
> wrote:
>> Hi,
>>
>> The Mojo team is pleased to announce t
If I read the core correctly, then the plugin, faced with a missing license for
group.artifact.version
goes looking for
group.artifact.version:properties:third-party
However, you really cannot retroactively deploy an attached artifact
for a project, so this does not allow someone to create t
On Fri, Dec 21, 2012 at 12:54 AM, Anders Hammar wrote:
>
>> However, you really cannot retroactively deploy an attached artifact
>> for a project, ...
>
>
> I think you can, but could differ between mrm. If it's a good thing is a
> different topic.
I don't see how it can work well. There's only o
it complains if redeploy is not enabled.
On Dec 21, 2012, at 8:32 AM, Anders Hammar wrote:
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, B
I need to fix the options for the Maven 2 builds of the
license-maven-plugin; we need an 'install' goal to compensate for the
usual reactor breakage.
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/
odehaus.org/development/codehaus-support.html
>
>> Date: Tue, 1 Jan 2013 20:18:22 +0100
>> From: che...@codelutin.com
>> CC: dev@mojo.codehaus.org
>> Subject: Re: [mojo-dev] How do I get a login on the bamboo server?
>
>>
>> On Tue, 1 Jan 2013 13:37:23 -0500
I'd really like to see a release of the cobertura plugin with the
patch in MCOBERTURA-65. I'll go fork to github if I have to, but
before doing that I wanted to check and see if there was any
likelihood of this happening here.
-
T
OK, I'll take a run at improving on it.
On Wed, Mar 30, 2011 at 5:32 PM, Robert Scholte wrote:
> the patch is missing integration tests, so it requires more work then just
> patching it. If anyone(you?) could provide some IT's I can have a look at
> it.
> It's not only to confirm that it works, b
I've uploaded an enhanced patch with an integration test.
On Wed, Mar 30, 2011 at 5:32 PM, Robert Scholte wrote:
> the patch is missing integration tests, so it requires more work then just
> patching it. If anyone(you?) could provide some IT's I can have a look at
> it.
> It's not only to confir
er words, what's the advantage, to anyone,
of keeping this code at codehaus?
--benson margulies
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
se for better compatibility with the GPL.
> For my contributions, I'm fine with that.
>
> I'm fine with Benson having commit rights if he is keen to maintain it.
>
> - Brett
>
> On 01/04/2011, at 6:53 AM, Benson Margulies wrote:
>
>> Hello Mojo Develo
us than to write extra code to avoid the use of the real API.
On Fri, Apr 1, 2011 at 7:51 AM, Jochen Wiedmann
wrote:
> On 01/04/2011, at 6:53 AM, Benson Margulies wrote:
>
>> I just got bad news from Robert Scholte. There is a longstanding
>> problem of license friction with thi
For what it's worth, I sent email to the cobertura dev list pointing
out my view that their AL versus GPL grant language is ambiguous, and
asking them to consider a statement of the form, "any open source
build tool can call cobertura." I'll pass along any response that I
get.
Lacking that, of cou
Brett will have to write for himself. From my point of view, either a
proper Codehaus / Apache notice (one that claims copyright for
Codehaus and then grants the license) or a BSD license would be fine.
However, Brett likely knows something that I don't.
In both cases, my view is, following Larry
I asked Larry Rosen for some *informal* legal advice. He's written a
book on open source licensing and a legal advisor to the ASF:
--- begin quote
Cobertura's licensing model is nonsense. Distinguishing between "ant
tasks" and "the rest of Cobertura" is meaningless to me. I suppose
this is
al-licensed
it.
--benson
On Fri, Apr 1, 2011 at 4:42 PM, Jochen Wiedmann
wrote:
> On Fri, Apr 1, 2011 at 10:28 PM, Benson Margulies
> wrote:
>
>> As far as I'm concerned, we can take the software under the most
>> liberal license available (AL 1.1) and ignore t
Brett, Larry
On Apr 2, 2011, at 1:17 AM, Brett Porter wrote:
's
>
> On 02/04/2011, at 7:08 AM, Benson Margulies wrote:
>
>> Brett will have to write for himself. From my point of view, either a
>> proper Codehaus / Apache notice (one that claims copyright for
>&
their own 'fork a jvm' verbiage. If they don't accept Larry's view,
then their ant thing is a derived work, and they can't license it AL
at all.
--benson
On Sat, Apr 2, 2011 at 1:17 AM, Brett Porter wrote:
>
> On 02/04/2011, at 7:08 AM, Benson Margulies wrot
One interesting problem here is ossrh. Since you can only have one
parent, people will have to choose between this one and the ossrh
parent. Or you could make two of this. Or you could just make this an
archetype?
On Wed, Apr 6, 2011 at 7:03 AM, Jochen Wiedmann
wrote:
> Hi,
>
> this proposal isn'
;> Subject: Re: [mojo-dev] Cobertura: in codehaus or out
>>
>> On Sat, Apr 2, 2011 at 2:37 PM, Benson Margulies
>> wrote:
>>
>> >> - ALv2 is not compatible with GPLv2 due to the patent terms, making
>> >> that situation a bit weird. BSD would mak
Some dozens of email messages back, we discussed cleaning up the
inappropriate Apache notices.
Brett had suggested using BSD, so I guess I'll do that. is there an
example of a 'Codehaus has copyright, licensed BSD' notice around?
---
There are various patches hanging off of jira that appear complete
(e.g. MCOBERTURA-86). Should I apply some before making a release?
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
I believe that I've swept up all the easy patches for m-c-p.
So, on to a release.
Process? Is there a vote? Is there something written about how to go
about the mechanics?
-
To unsubscribe from this list, please visit:
http
in the section "Call a Vote" : vote success with lazy
> consensus.
> So at least your only +1 wins :-)
>
> /Olivier
>
> 2011/4/12 Benson Margulies :
>> I believe that I've swept up all the easy patches for m-c-p.
>>
>> So, on to a release.
>>
&
Turns out that someone already did this.
On Tue, Apr 12, 2011 at 1:56 PM, Anders Hammar wrote:
> I suggest using the jira-report instead of changes-report. One of the
> improvements I've suggested as part of MOJO-1654.
>
> /Anders
>
> On Tue, Apr 12, 2011 at 19:43, Be
To make sure I've understood olamy's remark, I'm posting a vote thread
after my habits from elsewhere. If this is a foreign and inappropriate
behavior I apologize in advance.
-
To unsubscribe from this list, please visit:
htt
Sorry, I was reading in a meeting and got out of order.
I think I can manage from the page. I can certainly wait a day.
On Tue, Apr 12, 2011 at 2:48 PM, Robert Scholte wrote:
> Nope, this is not how it's done.
> Please read the complete page and follow it step by step.
> But if you could wait on
will do
On Apr 13, 2011, at 1:06 PM, Robert Scholte wrote:
Benson,
I've fixed some stuff, enough for this release.
If you could do me one favor before calling a vote: please check the
checkstyle-report. It contains some errors, which would be nice if most of
them got fixed.
If I noticed correct
checkstyle 5.0 goes ape when faced with '@goal' in a javadoc comment.
(it gets an exception and reports it.)
checkstyle 5.1 is rumored to have an option to disable this. Not only
isn't there a checkstyle plugin that uses 5.1, there doesn't even seem
to be a copy of checkstyle 5.1 itself in central
le-plugin v2.7.
> http://jira.codehaus.org/browse/MOJO-1660
>
> /Anders
>
> On Thu, Apr 14, 2011 at 03:29, Benson Margulies
> wrote:
>
> checkstyle 5.0 goes ape when faced with '@goal' in a javadoc comment.
> (it gets an exception and reports it.)
>
> chec
Attentive watchers of the svn log will note that I tagged 2.5. You
didn't see a vote because I don't (yet) have access to stage the
release to nexus. JIRA opened, hopefully this will be resolved soon.
-
To unsubscribe from this li
codehaus.org/mojo/tags/cobertura-maven-plugin-2.5
[ ] +1
[ ] +0
[ ] -1
The vote is open for 72 hours and will succeed by lazy consensus.
Regards / Cheers /
Benson Margulies
-
To unsubscribe from this list, p
This is pretty awful. I think I'll unwind and try this One More Time.
On Fri, Apr 15, 2011 at 1:54 PM, Benson Margulies wrote:
> I'd like to release version 2.5 of the cobertura-maven-plugin
>
> The cobertura-maven-plugin is a maven plugin that executes the open
> source C
Hello everyone,
I've restaged the release with the site fixed. All the data below is
still accurate.
--benson
On Fri, Apr 15, 2011 at 1:54 PM, Benson Margulies wrote:
> I'd like to release version 2.5 of the cobertura-maven-plugin
>
> The cobertura-maven-plugin is
'm sorry I didn't see that before, but that is quite
> confusing.
> We should really get some generic Mojo guideline in place on how we should
> use this report (MOJO-1654).
>
> /Anders
> On Mon, Apr 18, 2011 at 17:15, Benson Margulies
> wrote:
>>
>> Hello
After plenty of time and no votes, I'm declaring this passed by (very)
lazy consensus.
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
11226&version=16413
Enjoy,
The Mojo team.
Benson Margulies
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
I see that c-m-p 2.5 isn't on central yet. What's the sync schedule
from codehaus to central?
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
MCOBERTURA-145 describes a conflict with maven-project-info-reports.
It seems as if there's some convention that the author of
MCOBERTURA-65 and I didn't understand.
Are any readers of this list sufficiently involved in m-p-i-r to
perhaps save us a lot of reverse-engineering and give us a clue?
S
Thanks.
On Fri, Apr 22, 2011 at 9:24 AM, Benjamin Bentmann
wrote:
> Benson Margulies wrote:
>
>> MCOBERTURA-145 describes a conflict with maven-project-info-reports.
>> It seems as if there's some convention that the author of
>> MCOBERTURA-65 and
MCOBERTURA-145 seems to me to justify a turn of the crank, but not a
move to 2.6. Anyone object?
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Robert,
I understand your point. At the same time, another spin around the
crank (once I've got the fix and some tests) would take me about an
hour, it would clean up the snafu with the JIRA report, and it would
finish delivering the aggregation support, which was sort of the idea
that got me star
Hmm.
Well, one issue here is that I'm not much of a Cobertura expert. I got
into this because coworkers were bemoaning the lack of aggregation.
Some of them there bug reports require a level of Cobertura knowledge
that I just don't have.
I'll revisit the list and see what else I can put a dent in
Hiding in the maven-release-plugin is:
http://svn.apache.org/repos/asf/maven/release/tags/maven-release-2.1/maven-release-plugin/src/it/setup/maven-scm-provider-dummy
I want to use this in a cobertura integration test to fake out release:perform.
Should I:
(a) make a copy
(b) make this a rele
MCOBERTURA-132 complains that user settings of forkMode don't work in
M3. It looks to me as if the reason is that M3 'fixed' something. The
c-m-p lifecycle.xml has a setting of forkMode in it for surefire.
While it looks like a bear to prove it, my hypothesis is that in M3,
this setting wins.
Coul
So, someone asks in a jira for integration test support.
Seems to me that the path to this would be an extra 'check' mojo
called check-integration which had a @execute of integration-test and
another lifecycle for the purpose. Anyone have any other thoughts?
--
om spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
>
> On 23 Apr 2011 16:53, "Benson Margulies" wrote:
>> Hmm.
>>
>> Well, one issue here is that I'm not much of a Cobertura expert. I
I made a new IT.
It 'fails'
[DEBUG] Executing: /bin/sh -c cd
/Users/benson/asf/c-m-p-3/target/it/fork-it &&
/opt/apache-maven-3.0.3/bin/mvn -B -X -D
maven.repo.local=/Users/benson/asf/c-m-p-3/target/local-repo -s
/Users/benson/asf/c-m-p-3/target/it/interpolated-settings.xml clean
verify
[INFO] ..
That was the problem, indeed. I copied the wrong test :-)
On Tue, Apr 26, 2011 at 5:01 AM, Robert Scholte wrote:
> Is this still a problem? I've checked out the code and I see the IT
> succeeds.
> One reason could be a invoker.properties -file which might have a setting
> for the expected buildRe
Is this alive or dead? Should that rather unhelpful maven site be there?
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
in stub that Jason created
> ages ago.
>
> /Anders
>
> On Mon, May 16, 2011 at 15:05, Benson Margulies
> wrote:
>>
>> Is this alive or dead? Should that rather unhelpful maven site be there?
>>
>> --
;s been here for a while know if there is such a process?
> Should we just vote and then (hopefully) go ahead?
>
> /Anders
> On Mon, May 16, 2011 at 15:30, Benson Margulies
> wrote:
>
> Is there a process of deleting abandoned sandbox sites to reduce noise
> and confusion?
>
Someone ran the minimal archetype to set up a plugin for retroweaver,
published the site, and then didn't do anything else. The result is a
confusing (and perhaps embarassing) opportunity to cause confusion and
frustration. Users looking for a maven plugin for retroweaver find
this, and then find t
MCOBERTURA-132 is getting attention, aside from other fixes we did
since 2.5. Another release?
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
To make it 2.5.1 I have to change the fixed-bys. I'll do that and
start the machinery.
On Fri, May 20, 2011 at 12:27 PM, Robert Scholte wrote:
> Looks more like a 2.5.1 to me, but sounds good to me.
>
> -Robert
>
>> Date: Fri, 20 May 2011 11:53:33 -0400
>> From: bimargul...@gmail.com
>> To: dev@m
Oh, very tricky. OK, thanks.
On Fri, May 20, 2011 at 12:32 PM, Robert Scholte wrote:
> I've renamed the version in jira.
>
> -Robert
>
>> Date: Fri, 20 May 2011 12:29:13 -0400
>> From: bimargul...@gmail.com
>> To: dev@mojo.codehaus.org
>> Subject: Re: [mojo-dev] 2.6 of cobertura-m-p?
>>
>> To mak
right this moment I need a nap to compensate for a very late (?early?)
airplane arrival last night. Maybe Sunday I'll turn the crank and post
the vote.
On Fri, May 20, 2011 at 12:39 PM, Olivier Lamy wrote:
> let's go !!
>
> 2011/5/20 Benson Margulies :
>> MCOBERTURA
This vote passes, 6 +1 and nothing else. Someone pass me my machete.
On Tue, May 17, 2011 at 3:38 AM, Olivier Lamy wrote:
> +1
>
> --
> Olivier
>
> Le 16 mai 2011 22:14, "Benson Margulies" a écrit :
>> Someone ran the minimal archetype to set up a plugin for
I want to dispose of the web presence of the maven-retroweaver-plugin,
but I am ignorant of how.
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
To my, having the site say:
svn checkout https://svn.codehaus.org/mojo/tags/cobertura-maven-plugin-2.5
cobertura-maven-plugin
makes no sense. if someone is a developer, they want the trunk. Does
anyone know if m-p-i-p can be made to work that way?
Hi,
I'd like to release version 2.5.1 of the cobertura-maven-plugin
c-m-p is a maven plugin that executes the Cobertura code coverage tool.
We solved 3 issues, one of which was a regression in 2.5 release.
** Bug
* [MCOBERTURA-132] - forkMode is ignored when generating cobertura
reports us
t;> Use webdav to "mount" the server folder. Then remove.
>>
>> The url is the distribution url for sites:
>> https://dav.codehaus.org/mojo/
>>
>> /Anders
>>
>> On Fri, May 20, 2011 at 22:32, Benson Margulies
>> wrot
Something tells me that you've all considered and rejected this before, but ...
What if the site deployment URL was set to include a version number
element, and then part of the release process was to update a
.htaccess to point to the latest release?
Then you could deploy a snapshot site, and pe
rg
>> Subject: Re: [mojo-dev] [VOTE] Release cobertura-maven-plugin version 2.5.1
>>
>> +1
>>
>> 2011/5/20 Benson Margulies :
>> > Hi,
>> >
>> > I'd like to release version 2.5.1 of the cobertura-maven-plugin
>> >
>
l not be rendered on
invocation of mvn clean install site for a multi module project.
** Improvement
* [MCOBERTURA-144] - The JIRA report should only list those issues
fixed in the current release
Enjoy,
The Mojo team.
benson marg
This is all done.
On Fri, May 20, 2011 at 4:28 PM, Benson Margulies wrote:
> This vote passes, 6 +1 and nothing else. Someone pass me my machete.
>
> On Tue, May 17, 2011 at 3:38 AM, Olivier Lamy wrote:
>> +1
>>
>> --
>> Olivier
>>
>> Le 1
At my day job, we put the versions in the deployment URL.
My proposal is then to use .htaccess to map '/foo' to the latest
release '/foo/1.2.3'.
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/mana
has the reverse proxy apache mod install we could also use
it as you say, I used to know how to do that.
>
> /Anders
>
> On Wed, May 25, 2011 at 12:22, Benson Margulies
> wrote:
>>
>> At my day job, we put the versions in the deployment URL.
>>
>>
should not be
redirect to (for example):
http://mojo.codehaus.org/setup-maven-plugin/2.3
as that would then be the url he/she would bookmark. And that's going to
cause confusion when we release 2.4+.
/Anders
On Wed, May 25, 2011 at 12:41, Benson Margulies wrote:
> On Wed, May 25, 2011 at
r easy staging, and when the release is finished, just
>> update the link. Anyone else open to this idea?
>>
>>
>> > Another idea would be to have a directory structure like
>> >
>> > foo-plugin-site/
>> > |-- 1.0
>>
The Groovy community is no longer in a position to maintain the
gmaven-plugin. For building pure groovy projects, they have their own
build tools. For building some groovy along with java, they are
refining a maven-compiler-plugin plugin. That leaves, if I'm not too
confused, just running a groovy
I feel a bit dropped into the middle of this.
Is this thread just about gwt, or is it also about a general plan to
move to git for mojo?
On Tue, May 31, 2011 at 2:00 PM, Kristian Rosenvold
wrote:
> Yes, I can be "someone". I can also initialize the github mirroring.
>
> But "someone else" needs
Consider:
https://builds.apache.org/job/Lucene-Solr-Maven-trunk/lastSuccessfulBuild/artifact/maven_artifacts/*zip*/maven_artifacts.zip/,
complete with trailing slash.
Jenkins answers this with a zip file. Which causes an infinite
recursion in the wagon-maven-plugin, eventually. I'm inclined to
fi
+1
On Jul 8, 2011, at 12:15 PM, "Trygve Laugstøl" wrote:
> Hi,
>
> I'd like to release the unix-maven-plugin with a few changes I've done ofer
> the last year and half since the last release.
>
> The vote is open for 72 hours and will succeed by lazy consensus.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
On Sat, Jul 9, 2011 at 2:08 PM, Stephen Connolly
wrote:
> i see no reason why you cannot deploy the site from trunk after you have
> released... in fact if it is only the site i would be happy fixing in
> target/checkout (so the version is the release version) and pushing from
> there.
This situa
n Plugin
Priority:
Major
Reporter:
Benson M
Title: Message Title
Benson Margulies reopened an issue
Title: Message Title
Benson Margulies updated an issue
Title: Message Title
Benson Margulies closed an issue as Fixed
Title: Message Title
Benson Margulies updated an issue
1 - 100 of 264 matches
Mail list logo
