I wasn't able to reproduce the problem. I think I'll just update the
parent to alpha-5, check again, then call the release tomorrow.
- Brett
On 19/06/2007, at 11:39 AM, Jason van Zyl wrote:
On 18 Jun 07, at 5:57 PM 18 Jun 07, Brett Porter wrote:
Jason,
How did you experience this
On 18 Jun 07, at 11:19 PM 18 Jun 07, Brett Porter wrote:
I wasn't able to reproduce the problem. I think I'll just update
the parent to alpha-5, check again, then call the release tomorrow.
When you update I'll try again as well.
- Brett
On 19/06/2007, at 11:39 AM, Jason van Zyl wrote:
On Sunday 17 June 2007 21:51, Brett Porter wrote:
On 18/06/2007, at 11:46 AM, Daniel Kulp wrote:
Technically, if you follow all the latest legal discussions and
stuff, the name of the tgz/zip should be apache-maven-2.0.7 which
would allow
to use an artifactId of apache-maven. We just
On 19/06/2007, at 2:35 AM, Daniel Kulp wrote:
On Sunday 17 June 2007 21:51, Brett Porter wrote:
On 18/06/2007, at 11:46 AM, Daniel Kulp wrote:
Technically, if you follow all the latest legal discussions and
stuff, the name of the tgz/zip should be apache-maven-2.0.7 which
would allow
to use
On Monday 18 June 2007 12:41, Brett Porter wrote:
On 19/06/2007, at 2:35 AM, Daniel Kulp wrote:
1) The project name is officially Apache Maven, not Maven. The
downloads and such should reflect that. (as should the READMEs,
the web
site, etc)
Yes, I agree with that. Sorry, I
Jason,
How did you experience this problem with the RR plugin so I can
verify it is fixed in a later version?
- Brett
On 18/06/2007, at 11:51 AM, Brett Porter wrote:
You're right, it's pinned to alpha-2 but 5 is out.
Jason - how do I reproduce the error if I want to check it?
On 18 Jun 07, at 5:57 PM 18 Jun 07, Brett Porter wrote:
Jason,
How did you experience this problem with the RR plugin so I can
verify it is fixed in a later version?
Try building the embedder module in trunk. That's where it failed for
me.
- Brett
On 18/06/2007, at 11:51 AM, Brett
If you're working on a fix that requires a specific fix and is not
something that is in ongoing, high-flux development then can people
release first and then incorporate.
Two example of late are plexus-utils in trunk, and the Maven parent POM.
Snapshots are for intra-project, high-flux
On 18/06/2007, at 1:52 AM, Jason van Zyl wrote:
If you're working on a fix that requires a specific fix and is not
something that is in ongoing, high-flux development then can people
release first and then incorporate.
Two example of late are plexus-utils in trunk, and the Maven parent
On 17 Jun 07, at 4:24 PM 17 Jun 07, Brett Porter wrote:
On 18/06/2007, at 1:52 AM, Jason van Zyl wrote:
If you're working on a fix that requires a specific fix and is not
something that is in ongoing, high-flux development then can
people release first and then incorporate.
Two example
On 18/06/2007, at 10:28 AM, Jason van Zyl wrote:
It won't work on the assemblies anyway because that's not the name
we use for distribution so the signatures would not be correct.
They have to be taken as they are built with the final name and
those are signed. Something I need to bring
On 17 Jun 07, at 5:59 PM 17 Jun 07, Brett Porter wrote:
On 18/06/2007, at 10:28 AM, Jason van Zyl wrote:
It won't work on the assemblies anyway because that's not the name
we use for distribution so the signatures would not be correct.
They have to be taken as they are built with the
On Sunday 17 June 2007 20:28, Jason van Zyl wrote:
It won't work on the assemblies anyway because that's not the name we
use for distribution so the signatures would not be correct. They
have to be taken as they are built with the final name and those are
signed. Something I need to bring up
On Sunday 17 June 2007 19:24, Brett Porter wrote:
I was going to take care of that very shortly, but wanted to make
sure it was at least correct first. Using v5 was not - the gpg plugin
that was included did not work with the assemblies (as you can see
from your staging repository:
On 18/06/2007, at 11:33 AM, Jason van Zyl wrote:
I think we also have to deal with the asymmetry in that we make the
source assembly from the root, and then do weird wiggling. In Maven
I think we should have the assemblies at the top-level but this
leads other problems with the assembly
On 18/06/2007, at 11:46 AM, Daniel Kulp wrote:
Technically, if you follow all the latest legal discussions and stuff,
the name of the tgz/zip should be apache-maven-2.0.7 which would
allow
to use an artifactId of apache-maven. We just changed over to that
format for CXF. That way
On 6/17/07, Brett Porter [EMAIL PROTECTED] wrote:
I remember pushing for assemblies at the root in the past, but later
agreeing it wasn't best practice because of the lifecycle
inconsistency (the root project must be first in the reactor to
install the pom, but must be last in the reactor if it
On 18/06/2007, at 11:48 AM, Daniel Kulp wrote:
On Sunday 17 June 2007 19:24, Brett Porter wrote:
I was going to take care of that very shortly, but wanted to make
sure it was at least correct first. Using v5 was not - the gpg plugin
that was included did not work with the assemblies (as you
Yeah, I hadn't made it to my second cup of coffee so I didn't
remember we had the @aggregator tag for this purpose, so using
assembly:attached *should* work for this purpose. But I don't think
it properly draws in the modules so it's purely an assembly plugin
feature.
- Brett
On
On 6/17/07, Brett Porter [EMAIL PROTECTED] wrote:
On 18/06/2007, at 11:46 AM, Daniel Kulp wrote:
Technically, if you follow all the latest legal discussions and stuff,
the name of the tgz/zip should be apache-maven-2.0.7 which would
allow
to use an artifactId of apache-maven. We just
20 matches
Mail list logo
