On 17 Jun 07, at 10:43 PM 17 Jun 07, Brett Porter wrote:
+1
A niggle I would like to see corrected: the source distributions
from the assembly (in the repository), and the one in the second
directory are different. The one in the assembly looks wrong (still
refers to 2.0.7-SNAPSHOT). May
+1
A niggle I would like to see corrected: the source distributions from
the assembly (in the repository), and the one in the second directory
are different. The one in the assembly looks wrong (still refers to
2.0.7-SNAPSHOT). Maybe they should be removed from the staging repo
this time
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
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 18/06/20
On 18/06/2007, at 12:28 PM, Jason van Zyl wrote:
I find this description completely incomprehensible but doesn't it
say don't specify a phase and that's it's for a single project?
Bad grammar. My fault - I wrote it, so I'll fix it now.
attached will work too, but single is more appropriat
On 17 Jun 07, at 7:09 PM 17 Jun 07, [EMAIL PROTECTED] wrote:
Author: brett
Date: Sun Jun 17 19:09:03 2007
New Revision: 548167
URL: http://svn.apache.org/viewvc?view=rev&rev=548167
Log:
attach the assembly (and it's signatures) properly
Modified:
maven/components/branches/maven-2.0.x/mave
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 ca
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 i
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 t
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 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: http://p
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 u
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 fi
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:25 PM 17 Jun 07, Brett Porter wrote:
On 17/06/2007, at 8:43 AM, Jason van Zyl (JIRA) wrote:
[ http://jira.codehaus.org/browse/MNG-2943?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2943.
-
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 17/06/2007, at 8:43 AM, Jason van Zyl (JIRA) wrote:
[ http://jira.codehaus.org/browse/MNG-2943?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2943.
--
Resolution: Fixed
One bundle will be used, and no o
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
P
On 18/06/2007, at 2:07 AM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Sun Jun 17 09:06:59 2007
New Revision: 548054
URL: http://svn.apache.org/viewvc?view=rev&rev=548054
Log:
o rolling back again, i didn't erase the tag and the release plugin
doesn't check first ...
You should just
+1
still works
On 6/17/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
The release notes are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=10500&styleName=Html&version=13138
The tag is here:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/
Staging re
Hi,
The release notes are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?
projectId=10500&styleName=Html&version=13138
The tag is here:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/
Staging repository:
http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repos
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 devel
Kenney Westerhof wrote:
[snip]
>>> The meaning of depMgt is different, applied to either local deps or
>>> transitive deps, and it's not consistent.
>>>
>>> This somewhat describes the situation:
>>> - depMgt for artifact X is used to provide defaults for direct
>>> dependencies of artifact X,
>>
23 matches
Mail list logo
