This particular assembly descriptor is a one-time case for the assembly
plugin only. It's not the one that Brian was talking about, since that
one will have to be much more generalized to handle the variability of
other projects. In this case, I know that the build directory for the
assembly pl
On Sat, Jun 13, 2009 at 7:40 AM, Barrie Treloar wrote:
> On Sat, Jun 13, 2009 at 7:21 AM, Barrie Treloar wrote:
>> On Sat, Jun 13, 2009 at 12:04 AM, John Casey wrote:
>>> Is this still happening with maven-assembly-plugin 2.2-beta-4?
>>
>> It was 2.2-beta-2, I'll check -4
>
> 2.2-beta-4 behaves cor
On Sat, Jun 13, 2009 at 7:21 AM, Barrie Treloar wrote:
> On Sat, Jun 13, 2009 at 12:04 AM, John Casey wrote:
>> Is this still happening with maven-assembly-plugin 2.2-beta-4?
>
> It was 2.2-beta-2, I'll check -4
2.2-beta-4 behaves correctly.
---
On Sat, Jun 13, 2009 at 12:04 AM, John Casey wrote:
> Is this still happening with maven-assembly-plugin 2.2-beta-4?
It was 2.2-beta-2, I'll check -4
> Barrie Treloar wrote:
>>
>> On Fri, Jun 12, 2009 at 12:11 AM, John Casey
>> wrote:
>>>
>>> I had to include these files for the recent maven-asse
Hi John,
Yes I did a similar thing in Doxia.
Cheers,
Vincent
2009/6/12 John Casey :
> Is this still happening with maven-assembly-plugin 2.2-beta-4?
>
> Barrie Treloar wrote:
>>
>> On Fri, Jun 12, 2009 at 12:11 AM, John Casey
>> wrote:
>>>
>>> I had to include these files for the recent maven-a
Is this still happening with maven-assembly-plugin 2.2-beta-4?
Barrie Treloar wrote:
On Fri, Jun 12, 2009 at 12:11 AM, John Casey wrote:
I had to include these files for the recent maven-assembly-plugin release.
It was fairly simple, just take a look at this:
http://svn.apache.org/repos/asf/ma
On Fri, Jun 12, 2009 at 12:11 AM, John Casey wrote:
> I had to include these files for the recent maven-assembly-plugin release.
> It was fairly simple, just take a look at this:
>
> http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/main/assembly/source-release.xml
Be a
On Jun 11, 2009, at 9:56 AM, David Jencks wrote:
On Jun 11, 2009, at 4:52 AM, Brian Fox wrote:
On Thu, Jun 11, 2009 at 4:22 AM, David
Jencks wrote:
On Jun 10, 2009, at 6:59 PM, Brian Fox wrote:
Update:
The new assembly plugin and the regex in the source bundle seem
to be
working great
Well, I'm not sure what to say about that. I guess I could say if it's
not on the release docs, it's not policy? It's a little frustrating to
constantly chase a standard that isn't documented and which there are
many opinions of. I'll solve this particular problem of the source
release for now. I h
On Jun 11, 2009, at 4:52 AM, Brian Fox wrote:
On Thu, Jun 11, 2009 at 4:22 AM, David
Jencks wrote:
On Jun 10, 2009, at 6:59 PM, Brian Fox wrote:
Update:
The new assembly plugin and the regex in the source bundle seem to
be
working great. I have just one thing to resolve that I had
prev
I had to include these files for the recent maven-assembly-plugin
release. It was fairly simple, just take a look at this:
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/main/assembly/source-release.xml
-john
Brian Fox wrote:
Update:
The new assembly plugin and
On Thu, Jun 11, 2009 at 4:22 AM, David Jencks wrote:
>
> On Jun 10, 2009, at 6:59 PM, Brian Fox wrote:
>
>> Update:
>> The new assembly plugin and the regex in the source bundle seem to be
>> working great. I have just one thing to resolve that I had previously
>> overlooked: The source archive mus
On Jun 10, 2009, at 6:59 PM, Brian Fox wrote:
Update:
The new assembly plugin and the regex in the source bundle seem to be
working great. I have just one thing to resolve that I had previously
overlooked: The source archive must also contain license and notice
files, even if svn doesn't.
I d
Update:
The new assembly plugin and the regex in the source bundle seem to be
working great. I have just one thing to resolve that I had previously
overlooked: The source archive must also contain license and notice
files, even if svn doesn't. I need to understand better the default
resource bundle
Just to bring the thread back up in light of the recent discussions of
plugin releases:
John has taken over the assembly release that contains the fix I put in for
the ASF stuff. I've been travelling a lot the past two weeks and haven't
progressed much on the poms. Tomorrow or monday I should have
On Wed, May 27, 2009 at 12:25 PM, John Casey wrote:
>
>
> Brian Fox wrote:
>
>> On Tue, May 26, 2009 at 10:18 PM, Brett Porter wrote:
>>
>> On 26/05/2009, at 11:11 PM, Brian Fox wrote:
>>>
>>> We're fixing the directoryscanner to allow regular expressions in
>>> addition
>>>
to the ant sy
Brian Fox wrote:
On Tue, May 26, 2009 at 10:18 PM, Brett Porter wrote:
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in addition
to the ant syntax.
Cool, but that's another release in the chain, right?
It's already to go,
On Tue, May 26, 2009 at 10:18 PM, Brett Porter wrote:
>
> On 26/05/2009, at 11:11 PM, Brian Fox wrote:
>
> We're fixing the directoryscanner to allow regular expressions in addition
>> to the ant syntax.
>>
>
> Cool, but that's another release in the chain, right?
>
It's already to go, John is
On 27/05/2009, at 3:18 PM, Brett Porter wrote:
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in
addition
to the ant syntax.
Cool, but that's another release in the chain, right?
Then we can do (?!.*/src/.*).*/target/.*
Ew
On 26/05/2009, at 11:11 PM, Brian Fox wrote:
We're fixing the directoryscanner to allow regular expressions in
addition
to the ant syntax.
Cool, but that's another release in the chain, right?
Then we can do (?!.*/src/.*).*/target/.*
Ew :)
What if the build directory isn't target? (unl
We're fixing the directoryscanner to allow regular expressions in addition
to the ant syntax. Then we can do (?!.*/src/.*).*/target/.*
On Mon, May 25, 2009 at 6:58 PM, Brett Porter wrote:
> How about an option true
> that uses the list of build directories from all projects in the reactor an
>
How about an option trueexcludeBuildDirectories> that uses the list of build directories from
all projects in the reactor an applies that to the fileset excludes?
It could be either descriptor-wide, or per-fileset I guess.
Short of that, I'd say to get it off the ground to tell projects they
Introducing the configurability in the descriptor itself requires more
changes to the assembly code than I think we should tackle right now. I also
think we should strive to build a descriptor that works for all projects to
the extent possible. That said, I'll make a property in the plugin config t
Brian Fox wrote:
On Mon, May 18, 2009 at 8:57 AM, Ate Douma wrote:
Brian Fox wrote:
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has
On Mon, May 18, 2009 at 8:57 AM, Ate Douma wrote:
> Brian Fox wrote:
>
>> It's been a little slow going, but here's an update of where I'm at:
>> I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
>> renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has been
>>
On 18/05/2009, at 10:57 PM, Ate Douma wrote:
The current descriptor produces tar.gz and zip, does anyone have
strong
feelings if this is ok or should we go with only one of them? (and
which
one?)
Why drop .bz2 in the first place?
We have been using .bz2, .tar.gz and .zip based distro rel
Brian Fox wrote:
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has been
added to 2.2-beta-4 (MASSEMBLY-406). I created a custom descriptor
It's been a little slow going, but here's an update of where I'm at:
I branched assembly 2.2-beta-4-SNAPSHOT[1] from the 2.2-beta-3 tag and
renamed the trunk to 2.2-beta-5. The runOnlyOnExecutionRoot flag has been
added to 2.2-beta-4 (MASSEMBLY-406). I created a custom descriptor bundle[2]
to be us
My plan is to implement the packaging in the maven pom and then later
promote it to the apache pom once any kinks are worked out.
--Brian (mobile)
On May 8, 2009, at 8:17 PM, David Jencks wrote:
Could I ask what's going to happen after you get the assembly plugin
improved? Will there be
Could I ask what's going to happen after you get the assembly plugin
improved? Will there be an apache 7 pom or, how else would we get
this new functionality?
thanks
david jencks
On May 7, 2009, at 8:13 PM, Brian E. Fox wrote:
I just need to finish the ITs.
--Brian (mobile)
On May 7, 2
I just need to finish the ITs.
--Brian (mobile)
On May 7, 2009, at 10:45 PM, Stephane Nicoll
wrote:
On Tue, May 5, 2009 at 3:21 AM, Brett Porter wrote:
On 05/05/2009, at 11:01 AM, Brian Fox wrote:
To make this happen relatively quickly, I'll take finish my patch by
adding tests, and
On Tue, May 5, 2009 at 3:21 AM, Brett Porter wrote:
>
> On 05/05/2009, at 11:01 AM, Brian Fox wrote:
>
> To make this happen relatively quickly, I'll take finish my patch by
>> adding tests, and then stage a release of the assembly plugin 2.2-beta-3.1
>> by applying only this patch to the existi
- Ursprüngliche Mail
Von: Brian Fox
An: dev@maven.apache.org
Gesendet: Dienstag, den 5. Mai 2009, 03:01:25 Uhr
Betreff: Update on ASF Release requirements
There have been a few threads spawned on various ASF lists lately about the
release process at the ASF and Maven projects and oth
t: Dienstag, den 5. Mai 2009, 03:01:25 Uhr
> Betreff: Update on ASF Release requirements
>
> There have been a few threads spawned on various ASF lists lately about the
> release process at the ASF and Maven projects and other Apache projects that
> use
> Maven being complian
On 05/05/2009, at 11:01 AM, Brian Fox wrote:
To make this happen relatively quickly, I'll take finish my patch by
adding tests, and then stage a release of the assembly plugin 2.2-
beta-3.1 by applying only this patch to the existing beta-3 tag so
we can cut a release without a bunch of han
There have been a few threads spawned on various ASF lists lately about
the release process at the ASF and Maven projects and other Apache
projects that use Maven being compliant.
A documentation patch for the release page at
http://www.apache.org/dev/release.html is pending, but it's close en
36 matches
Mail list logo
