You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by John Casey <ca...@gmail.com> on 2006/08/31 02:27:09 UTC
notice about recent assembly plugin snapshot
Hi everyone,
I just wanted to send a quick note to let you know that I've made some
modifications to the way the assembly plugin functions. These changes are
likely to break your assemblies if you're using the
moduleSets/moduleSet/sources element.
The sources element used to be derived from fileSet, in that you could
provide directory, outputDirectory, includes, excludes, etc. directly on
that element. This sources element would determine how source-files from
module children and grandchildren of your project were included. In some
recent work, I've noticed that it's sometimes useful to be more flexible
with module source inclusion. So, I've made the sources element a
free-standing class, no longer derived from the fileSet.
So, to replicate this:
<moduleSets>
<moduleSet>
<sources>
<directory>src</directory>
<excludes>
<exclude>**/*.bak</exclude>
<exclude>**/*~</exclude>
</excludes>
</sources>
</moduleSet>
</moduleSets>
you'd need to change it to the following:
<moduleSets>
<moduleSet>
<sources>
<fileSets>
<fileSet>
<directory>src</directory>
<excludes>
<exclude>**/*.bak</exclude>
<exclude>**/*~</exclude>
</excludes>
</fileSet>
</fileSets>
</sources>
</moduleSet>
</moduleSets>
I've deployed this new snapshot for people to try out, but changes like this
and other new features of the moduleSet section are not documented yet. I'm
planning to flesh out the documentation for these new parts soon, and call a
release, as I think we're nearing a good cut-off point, before beginning a
new round of features. I just wanted to make sure I didn't leave people
saying, "WTF? This used to work!" tonight.
-john
Quick availability of maven module to dependent modules in same project
Posted by Denis McCarthy <dm...@annadaletech.com>.
Hi,
I've recently moved from ant to maven2, and all in all I'm really happy
with the move. However, one of the main reasons I decided to move was
maven's superior dependency handling.
My project consists of two web apps with a corresponding
business/dataaccess module that both webapps rely on. Each of the three
apps in question are set up as maven modules, with the two web apps
declaring a dependency on the business module in their respective poms.
I'm using eclipse WTP with maven plugin as the development environment.
This works fine, but with one caveat: it's too slow to deploy new
versions of the business module to rapidly test changes with the
webapps. Currently, when any change is made to the business module our
developers have to run a mvn install on the business module. This runs
all the tests (some of which are quite slow because they are testing the
database). This takes about 3 minutes, which in the context of doing
many such deployments each day is too long. I'd like to set up my
project so that any changes to the business layer are visible to the
webapps as quickly as possible (even not having to run the tests as part
of mvn install would be a big boost)
Does anyone know how I can make changes to a maven module visible to
dependent modules rapidly, without running all the unit tests each time?
I'd consider writing my own plugin if necessary, but I'm sure there is
some existing functionality to allow me to do this.
TIA
Denis
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: notice about recent assembly plugin snapshot
Posted by Vinod Panicker <vi...@gmail.com>.
Hi,
I just noticed that the assembly is including the ".svn" directories
when copying the filesets as well. Is this expected or is it a bug?
Regards,
Vinod.
On 8/31/06, John Casey <ca...@gmail.com> wrote:
> Hi everyone,
>
> I just wanted to send a quick note to let you know that I've made some
> modifications to the way the assembly plugin functions. These changes are
> likely to break your assemblies if you're using the
> moduleSets/moduleSet/sources element.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: notice about recent assembly plugin snapshot
Posted by Brett Porter <br...@gmail.com>.
The standard pattern there is to have a <useDefaultExcludes /> tag
that is by default true. If you turn it off, you have to exclude all
the ones you don't want.
I think it needs to do that, especially if it did in 2.1. Backwards
compat is key.
- Brett
On 14/09/06, John Casey <ca...@gmail.com> wrote:
> I *think* the <sources/> tag was in the 2.1 release. I'm guessing I'll have
> to put support back in for backward compat...but I need to check out when
> this element was added to the model first.
>
> As for the .svn files, I believe this is a shortcoming of the underlying
> scanner implementation's default excludes. I'm a little hesitant to put that
> exclusion in by default, because there's no way to take it back. In other
> words, it may help most people to exclude **/.svn/** by default, but for
> those who *need* that pattern to be included, I don't think it would be
> possible.
>
> -john
>
> On 9/13/06, Brett Porter <br...@gmail.com> wrote:
> >
> > John?
> >
> > On 31/08/06, Brett Porter <br...@gmail.com> wrote:
> > > was this behaviour only in previous snapshots of the current release,
> > > or was it that way in the previous release?
> > >
> > > On 31/08/06, John Casey <ca...@gmail.com> wrote:
> > > > Hi everyone,
> > > >
> > > > I just wanted to send a quick note to let you know that I've made some
> > > > modifications to the way the assembly plugin functions. These changes
> > are
> > > > likely to break your assemblies if you're using the
> > > > moduleSets/moduleSet/sources element.
> > > >
> > > > The sources element used to be derived from fileSet, in that you could
> > > > provide directory, outputDirectory, includes, excludes, etc. directly
> > on
> > > > that element. This sources element would determine how source-files
> > from
> > > > module children and grandchildren of your project were included. In
> > some
> > > > recent work, I've noticed that it's sometimes useful to be more
> > flexible
> > > > with module source inclusion. So, I've made the sources element a
> > > > free-standing class, no longer derived from the fileSet.
> > > >
> > > > So, to replicate this:
> > > >
> > > > <moduleSets>
> > > > <moduleSet>
> > > > <sources>
> > > > <directory>src</directory>
> > > > <excludes>
> > > > <exclude>**/*.bak</exclude>
> > > > <exclude>**/*~</exclude>
> > > > </excludes>
> > > > </sources>
> > > > </moduleSet>
> > > > </moduleSets>
> > > >
> > > > you'd need to change it to the following:
> > > >
> > > >
> > > > <moduleSets>
> > > > <moduleSet>
> > > > <sources>
> > > > <fileSets>
> > > > <fileSet>
> > > > <directory>src</directory>
> > > > <excludes>
> > > > <exclude>**/*.bak</exclude>
> > > > <exclude>**/*~</exclude>
> > > > </excludes>
> > > > </fileSet>
> > > > </fileSets>
> > > > </sources>
> > > > </moduleSet>
> > > > </moduleSets>
> > > >
> > > > I've deployed this new snapshot for people to try out, but changes
> > like this
> > > > and other new features of the moduleSet section are not documented
> > yet. I'm
> > > > planning to flesh out the documentation for these new parts soon, and
> > call a
> > > > release, as I think we're nearing a good cut-off point, before
> > beginning a
> > > > new round of features. I just wanted to make sure I didn't leave
> > people
> > > > saying, "WTF? This used to work!" tonight.
> > > >
> > > > -john
> > > >
> > > >
> > >
> > >
> > > --
> > > Apache Maven - http://maven.apache.org
> > > "Better Builds with Maven" book - http://library.mergere.com/
> > >
> >
> >
> > --
> > Apache Maven - http://maven.apache.org
> > "Better Builds with Maven" book - http://library.mergere.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: notice about recent assembly plugin snapshot
Posted by John Casey <ca...@gmail.com>.
I *think* the <sources/> tag was in the 2.1 release. I'm guessing I'll have
to put support back in for backward compat...but I need to check out when
this element was added to the model first.
As for the .svn files, I believe this is a shortcoming of the underlying
scanner implementation's default excludes. I'm a little hesitant to put that
exclusion in by default, because there's no way to take it back. In other
words, it may help most people to exclude **/.svn/** by default, but for
those who *need* that pattern to be included, I don't think it would be
possible.
-john
On 9/13/06, Brett Porter <br...@gmail.com> wrote:
>
> John?
>
> On 31/08/06, Brett Porter <br...@gmail.com> wrote:
> > was this behaviour only in previous snapshots of the current release,
> > or was it that way in the previous release?
> >
> > On 31/08/06, John Casey <ca...@gmail.com> wrote:
> > > Hi everyone,
> > >
> > > I just wanted to send a quick note to let you know that I've made some
> > > modifications to the way the assembly plugin functions. These changes
> are
> > > likely to break your assemblies if you're using the
> > > moduleSets/moduleSet/sources element.
> > >
> > > The sources element used to be derived from fileSet, in that you could
> > > provide directory, outputDirectory, includes, excludes, etc. directly
> on
> > > that element. This sources element would determine how source-files
> from
> > > module children and grandchildren of your project were included. In
> some
> > > recent work, I've noticed that it's sometimes useful to be more
> flexible
> > > with module source inclusion. So, I've made the sources element a
> > > free-standing class, no longer derived from the fileSet.
> > >
> > > So, to replicate this:
> > >
> > > <moduleSets>
> > > <moduleSet>
> > > <sources>
> > > <directory>src</directory>
> > > <excludes>
> > > <exclude>**/*.bak</exclude>
> > > <exclude>**/*~</exclude>
> > > </excludes>
> > > </sources>
> > > </moduleSet>
> > > </moduleSets>
> > >
> > > you'd need to change it to the following:
> > >
> > >
> > > <moduleSets>
> > > <moduleSet>
> > > <sources>
> > > <fileSets>
> > > <fileSet>
> > > <directory>src</directory>
> > > <excludes>
> > > <exclude>**/*.bak</exclude>
> > > <exclude>**/*~</exclude>
> > > </excludes>
> > > </fileSet>
> > > </fileSets>
> > > </sources>
> > > </moduleSet>
> > > </moduleSets>
> > >
> > > I've deployed this new snapshot for people to try out, but changes
> like this
> > > and other new features of the moduleSet section are not documented
> yet. I'm
> > > planning to flesh out the documentation for these new parts soon, and
> call a
> > > release, as I think we're nearing a good cut-off point, before
> beginning a
> > > new round of features. I just wanted to make sure I didn't leave
> people
> > > saying, "WTF? This used to work!" tonight.
> > >
> > > -john
> > >
> > >
> >
> >
> > --
> > Apache Maven - http://maven.apache.org
> > "Better Builds with Maven" book - http://library.mergere.com/
> >
>
>
> --
> Apache Maven - http://maven.apache.org
> "Better Builds with Maven" book - http://library.mergere.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: notice about recent assembly plugin snapshot
Posted by Brett Porter <br...@gmail.com>.
John?
On 31/08/06, Brett Porter <br...@gmail.com> wrote:
> was this behaviour only in previous snapshots of the current release,
> or was it that way in the previous release?
>
> On 31/08/06, John Casey <ca...@gmail.com> wrote:
> > Hi everyone,
> >
> > I just wanted to send a quick note to let you know that I've made some
> > modifications to the way the assembly plugin functions. These changes are
> > likely to break your assemblies if you're using the
> > moduleSets/moduleSet/sources element.
> >
> > The sources element used to be derived from fileSet, in that you could
> > provide directory, outputDirectory, includes, excludes, etc. directly on
> > that element. This sources element would determine how source-files from
> > module children and grandchildren of your project were included. In some
> > recent work, I've noticed that it's sometimes useful to be more flexible
> > with module source inclusion. So, I've made the sources element a
> > free-standing class, no longer derived from the fileSet.
> >
> > So, to replicate this:
> >
> > <moduleSets>
> > <moduleSet>
> > <sources>
> > <directory>src</directory>
> > <excludes>
> > <exclude>**/*.bak</exclude>
> > <exclude>**/*~</exclude>
> > </excludes>
> > </sources>
> > </moduleSet>
> > </moduleSets>
> >
> > you'd need to change it to the following:
> >
> >
> > <moduleSets>
> > <moduleSet>
> > <sources>
> > <fileSets>
> > <fileSet>
> > <directory>src</directory>
> > <excludes>
> > <exclude>**/*.bak</exclude>
> > <exclude>**/*~</exclude>
> > </excludes>
> > </fileSet>
> > </fileSets>
> > </sources>
> > </moduleSet>
> > </moduleSets>
> >
> > I've deployed this new snapshot for people to try out, but changes like this
> > and other new features of the moduleSet section are not documented yet. I'm
> > planning to flesh out the documentation for these new parts soon, and call a
> > release, as I think we're nearing a good cut-off point, before beginning a
> > new round of features. I just wanted to make sure I didn't leave people
> > saying, "WTF? This used to work!" tonight.
> >
> > -john
> >
> >
>
>
> --
> Apache Maven - http://maven.apache.org
> "Better Builds with Maven" book - http://library.mergere.com/
>
--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: notice about recent assembly plugin snapshot
Posted by Brett Porter <br...@gmail.com>.
was this behaviour only in previous snapshots of the current release,
or was it that way in the previous release?
On 31/08/06, John Casey <ca...@gmail.com> wrote:
> Hi everyone,
>
> I just wanted to send a quick note to let you know that I've made some
> modifications to the way the assembly plugin functions. These changes are
> likely to break your assemblies if you're using the
> moduleSets/moduleSet/sources element.
>
> The sources element used to be derived from fileSet, in that you could
> provide directory, outputDirectory, includes, excludes, etc. directly on
> that element. This sources element would determine how source-files from
> module children and grandchildren of your project were included. In some
> recent work, I've noticed that it's sometimes useful to be more flexible
> with module source inclusion. So, I've made the sources element a
> free-standing class, no longer derived from the fileSet.
>
> So, to replicate this:
>
> <moduleSets>
> <moduleSet>
> <sources>
> <directory>src</directory>
> <excludes>
> <exclude>**/*.bak</exclude>
> <exclude>**/*~</exclude>
> </excludes>
> </sources>
> </moduleSet>
> </moduleSets>
>
> you'd need to change it to the following:
>
>
> <moduleSets>
> <moduleSet>
> <sources>
> <fileSets>
> <fileSet>
> <directory>src</directory>
> <excludes>
> <exclude>**/*.bak</exclude>
> <exclude>**/*~</exclude>
> </excludes>
> </fileSet>
> </fileSets>
> </sources>
> </moduleSet>
> </moduleSets>
>
> I've deployed this new snapshot for people to try out, but changes like this
> and other new features of the moduleSet section are not documented yet. I'm
> planning to flesh out the documentation for these new parts soon, and call a
> release, as I think we're nearing a good cut-off point, before beginning a
> new round of features. I just wanted to make sure I didn't leave people
> saying, "WTF? This used to work!" tonight.
>
> -john
>
>
--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org