John Casey wrote at Donnerstag, 18. Dezember 2008 01:39:
> Hi everyone,
>
> It's been quite awhile since we released a new version of the Assembly
> Plugin, and there have been some important fixes. Along with the plugin
> itself, its dependencies contain some improvements, and all of it is
> rea
is posted at http://blogs.sonatype.com/people/?p=1065
Thanks,
Oleg
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Did you add the staging repository? That's at:
http://people.apache.org/~jdcasey/stage
It looks like it's just checking repository.sonatype.org.
-john
Jason van Zyl wrote:
I just pulled from the tag to build and try it with Maven 3.x and got:
Just me, or are there some deps not deployed?
Mi
Cool. Nice.
On 18-Dec-08, at 7:26 PM, Arnaud HERITIER wrote:
I improved a little bit the script
We have now only one task in the CI server :
https://ci.sonatype.org/view/Reports/job/Users%20votes%20in%20Jira/
The script needs to have the output directory for reports as a param.
I added HTML ve
I think this is a regression:
http://jira.codehaus.org/browse/MNG-3922
Attached artifacts with classifiers seem to have gotten hosed. Works
in 2.0.8. No worky in 2.0.9.
On 17-Dec-08, at 7:44 PM, Brian E. Fox wrote:
(once again with the right url)
This fixes the NPE reported in the last RC
I improved a little bit the script
We have now only one task in the CI server :
https://ci.sonatype.org/view/Reports/job/Users%20votes%20in%20Jira/
The script needs to have the output directory for reports as a param.
I added HTML versions of reports with link to issues :
http://www.sonatype.org/~
I just pulled from the tag to build and try it with Maven 3.x and got:
Just me, or are there some deps not deployed?
Missing:
--
1) org.apache.maven.shared:maven-common-artifact-filters:jar:1.1
Try downloading the file manually from the project website.
Then, install it using the c
I appreciate that, I was only trying to point out that I don't have the
time right now to drive another release like the last one...it might
kill me. :-)
Jason van Zyl wrote:
In summary I'm saying you were the release manager. Not that it's your
process. If you want to pass on the torch that's
+1
Vincent
2008/12/17, John Casey :
> Hi everyone,
>
> It's been quite awhile since we released a new version of the Assembly
> Plugin, and there have been some important fixes. Along with the plugin
> itself, its dependencies contain some improvements, and all of it is ready
> to be released fo
The solution outlined below is the recommended way to handle this.
Copy/unpack was meant to handle external artifacts.
--Brian (mobile)
On Dec 18, 2008, at 4:28 PM, Jamie Whitehouse > wrote:
I've run into a similar situation and I'll explain how I resolved this
problem. There are two way'
I've run into a similar situation and I'll explain how I resolved this
problem. There are two way's that I've solved this, both of which are
used to inform the reactor of the inter-module dependency:
1) Simply add SomeModuleWAR to your dependency list. This is generally
a good idea to help the re
We've been waiting for several of these fixes for quite a while.
+1
-Trevor
John Casey-5 wrote:
>
> Hi everyone,
>
> It's been quite awhile since we released a new version of the Assembly
> Plugin, and there have been some important fixes. Along with the plugin
> itself, its dependencies c
2008/12/18 Jason van Zyl
> On 18-Dec-08, at 3:02 PM, Stephen Connolly wrote:
>
>> Actually, I'm liking the Nixon name for these mixins
>>
> No chance.
>
So you're saying that chance is not a factor hmm sounds like a done deal
so!
LOL
On 18-Dec-08, at 3:07 PM, Shane Isbell wrote:
On Thu, Dec 18, 2008 at 12:02 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
Actually, I'm liking the Nixon name for these mixins
Sure, why not? We can just call mavenized mixins, Nixons. Now I just
need a
big pen to start
On 18-Dec-08, at 3:02 PM, Stephen Connolly wrote:
Actually, I'm liking the Nixon name for these mixins
No chance.
2008/12/18 Ralph Goers
On Dec 18, 2008, at 9:56 AM, Brian Fox wrote:
It's not just about ignorig the ids. What about the distmgt info that
would be needed to deploy... Or
On Thu, Dec 18, 2008 at 12:02 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Actually, I'm liking the Nixon name for these mixins
Sure, why not? We can just call mavenized mixins, Nixons. Now I just need a
big pen to start blacking out sections of the spec.
Actually, I'm liking the Nixon name for these mixins
2008/12/18 Ralph Goers
>
> On Dec 18, 2008, at 9:56 AM, Brian Fox wrote:
>
> It's not just about ignorig the ids. What about the distmgt info that
>> would be needed to deploy... Or filtering or processing of it? I think it's
>> just better t
Gotta love Iphone autocorrect ;-)
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Thursday, December 18, 2008 1:09 PM
To: Maven Developers List
Subject: Re: Mixins (was Re: POM construction specification)
2008/12/18 Brian Fox
> filtering or proc
On Dec 18, 2008, at 9:56 AM, Brian Fox wrote:
It's not just about ignorig the ids. What about the distmgt info
that would be needed to deploy... Or filtering or processing of it?
I think it's just better to keep processing of the Nixon separate.
Yes, I agree (except with the Nixon name).
On Dec 18, 2008, at 8:34 AM, Jason van Zyl wrote:
On 18-Dec-08, at 1:35 AM, Ralph Goers wrote:
OK - I'm looking forward to seeing this. I understand the
programmatic aspect in the use case you describe with the IDE, but
not with something like the release capability. IIUC this would
all
I've just checked out doxia from trunk and got this error too :(
--
View this message in context:
http://www.nabble.com/Unable-to-find-the-mojo-%27org.apache.maven.doxia%3Adoxia-maven-plugin%3A1.0-beta-1-SNAPSHOT%3Arender-books%27-tp20667787p21078812.html
Sent from the Doxia - dev mailing list a
The Nixon is not crooked, it doesn't need processing.
On Thu, Dec 18, 2008 at 10:08 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> 2008/12/18 Brian Fox
>
> > filtering or processing of it? I think it's just better to keep
> processing
> > of the Nixon separate.
> >
> > --Brian
2008/12/18 Brian Fox
> filtering or processing of it? I think it's just better to keep processing
> of the Nixon separate.
>
> --Brian (mobile)
I don't know that you'll ever get to process the Nixon... the best you can
do is get him to do is resign, but his successor will probably pardon him so
In summary I'm saying you were the release manager. Not that it's your
process. If you want to pass on the torch that's cool. But that
decision is yours. Our process isn't as nearly as good as we might
like to think and someone doing the releases for a couple quarters in
my opinion is a goo
It's not just about ignorig the ids. What about the distmgt info that
would be needed to deploy... Or filtering or processing of it? I think
it's just better to keep processing of the Nixon separate.
--Brian (mobile)
On Dec 18, 2008, at 10:15 AM, Ralph Goers
wrote:
On Dec 18, 2008, a
On 18-Dec-08, at 9:17 AM, Brian E. Fox wrote:
I mentioned an idea in my review that seems to have been overlooked. I
think a regular .pom in the repository shouldn't be able to be used
as a
"mixin".
In my examples it is a normal POM that parses on its own, but I
actually need something n
Two things I definitely want to highlight here:
1. This is not my process. I'm obviously interested in getting Maven
releases out the door, and having them be of the highest quality we can
achieve. This means there is no way I can be the gatekeeper on every
release; I simply don't have that ki
The whole point of choosing sweetheart issues for the 2.1 roadmap was so
that those developers driving certain issues would have a natural
inclination to help push out new milestones. I was hoping this would
help keep 2.1 from bogging down...
Ralph Goers wrote:
On Dec 18, 2008, at 12:42 AM,
On 18-Dec-08, at 3:42 AM, Brett Porter wrote:
Hi,
I did what seems like my bi-annual review of all the unscheduled
issues today, reviewing and scheduling where appropriate. There's 10
left with open questions, and I'm making an early new years
resolution to keep on top of new reports :)
I think mixins are important, but I think in the short term trying to
focus on bring the spec up to what is known to be the behavior right
now is the focus. Once all those tests are done and the spec is
comprehensive with an appendix, has example, and where tests refer to
sections in the PO
On 18-Dec-08, at 1:35 AM, Ralph Goers wrote:
OK - I'm looking forward to seeing this. I understand the
programmatic aspect in the use case you describe with the IDE, but
not with something like the release capability. IIUC this would
allow our organization to create a standard way of doing
On Dec 18, 2008, at 6:17 AM, Brian E. Fox wrote:
I mentioned an idea in my review that seems to have been overlooked. I
think a regular .pom in the repository shouldn't be able to be used
as a
"mixin". We should keep inheritance and mixins separate. The way I
would
do it is with a new packa
I mentioned an idea in my review that seems to have been overlooked. I
think a regular .pom in the repository shouldn't be able to be used as a
"mixin". We should keep inheritance and mixins separate. The way I would
do it is with a new packaging type of mixin that would take another xml
file like
+1
Arnaud
On Thu, Dec 18, 2008 at 9:41 AM, Petar Tahchiev wrote:
>
> I tried it and I like it.
>
> +1 (not binding)
>
> Cheers, Petar.
>
> John Casey-5 wrote:
> >
> > Hi everyone,
> >
> > It's been quite awhile since we released a new version of the Assembly
> > Plugin, and there have been some
The snapshots from the grid are being deployed to
http://repository.sonatype.org so you can just search and download from there.
-Original Message-
From: Abel Muiño [mailto:amu...@gmail.com]
Sent: Thursday, December 18, 2008 4:15 AM
To: dev@maven.apache.org
Subject: Re: Maven 3.x
Great
Great news!
Is it possible to get early access to the artifacts? I see that the build is
ok, but I can't find a download link.
Jason van Zyl-5 wrote:
>
> I'm getting close to eliminating the last of the problems, but the
> grid build is working for and we'll start adding more OS's but things
On 18/12/2008, at 8:07 PM, Ralph Goers wrote:
On Dec 18, 2008, at 12:42 AM, Brett Porter wrote:
Hi,
I did what seems like my bi-annual review of all the unscheduled
issues today, reviewing and scheduling where appropriate. There's
10 left with open questions, and I'm making an early new
On Dec 18, 2008, at 12:42 AM, Brett Porter wrote:
Hi,
I did what seems like my bi-annual review of all the unscheduled
issues today, reviewing and scheduling where appropriate. There's 10
left with open questions, and I'm making an early new years
resolution to keep on top of new reports
Hi,
I did what seems like my bi-annual review of all the unscheduled
issues today, reviewing and scheduling where appropriate. There's 10
left with open questions, and I'm making an early new years resolution
to keep on top of new reports :)
Jason, Shane - as instructed I put all the repo
I tried it and I like it.
+1 (not binding)
Cheers, Petar.
John Casey-5 wrote:
>
> Hi everyone,
>
> It's been quite awhile since we released a new version of the Assembly
> Plugin, and there have been some important fixes. Along with the plugin
> itself, its dependencies contain some improv
41 matches
Mail list logo
