Javascript support

[Minto van der Sluis]

Hi Folks,

What's the best way to handle javascript using Maven? I have searched
the ML archive but it seems all projects have sort of died

I have looked at javascript-maven-pluging [1]. But:
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared

Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin

Same goes for the maven-js-plugin [3] :
- functionality limited to compression
- the still some very limited svn activity,

Is there a better way to work with javascript files, or have I been
spoiled by the maven java functionality?

Regards,

Minto 'misl' van der Sluis

[1] http://mojo.codehaus.org/javascript-maven-tools
[2] http://www.dev.abiss.gr/mvn-jstools
[3] http://ossi.mobilvox.com/maven-js-plugin

BTW is not my intention to insult anyone. I really do appreciate all
effort people have put into this, but my impression is javascript
support has been scattered and it seems sort of aborted or at least
neglected :-(

[David Hoffer]

I've used GWT w/ maven.

-Dave

Post by Minto van der Sluis
Hi Folks,
What's the best way to handle javascript using Maven? I have searched the
ML archive but it seems all projects have sort of died
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared
Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin
- functionality limited to compression
- the still some very limited svn activity,
Is there a better way to work with javascript files, or have I been spoiled
by the maven java functionality?
Regards,
Minto 'misl' van der Sluis
[1] http://mojo.codehaus.org/javascript-maven-tools
[2] http://www.dev.abiss.gr/mvn-jstools
[3] http://ossi.mobilvox.com/maven-js-plugin
BTW is not my intention to insult anyone. I really do appreciate all effort
people have put into this, but my impression is javascript support has been
scattered and it seems sort of aborted or at least neglected :-(
---------------------------------------------------------------------

[Minto van der Sluis]

Hi Martin,

I am not looking for a particular javascript library, I am looking for a
kind of dependency management as there exists for java projects. Both
javascript-maven-plugin as maven-jstools-plugin seem to be capable of
doing that.

On my current project I inherited a javascript mess where 3rd party
dependencies are copied somewhere into src/main/resources or
src/main/webapp/js. It's even worse, some js files have both 3rd party
and custom code. So it's hard to see what's custom and what's 3rd party.

To bring order into that chaos I was hoping for a maven javascript
plugin to help out.

Regards,

Minto 'misl' van der Sluis

The Javascript Library du jour (for any supported framework) changes
with the political climate
2 years ago everyone used Dojo
last year everyone converted all their Dojo code to Flex
this year its JQuery
personally i dont put Dojo on my resume anymore as someone would say
thats OLD!
so if you fork a branch to develop JQuery scripts (and you notice
someone sawing the branch you're on)
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig.
Diese Nachricht dient lediglich dem Austausch von Informationen und
entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten
Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den
Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

Date: Mon, 21 Sep 2009 06:33:37 -0600
Subject: Re: Javascript support
I've used GWT w/ maven.
-Dave
On Mon, Sep 21, 2009 at 6:26 AM, Minto van der Sluis

Post by Minto van der Sluis
Hi Folks,
What's the best way to handle javascript using Maven? I have

searched the

Post by Minto van der Sluis
ML archive but it seems all projects have sort of died
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared
Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin
- functionality limited to compression
- the still some very limited svn activity,
Is there a better way to work with javascript files, or have I

been spoiled

Post by Minto van der Sluis
by the maven java functionality?
Regards,
Minto 'misl' van der Sluis
[1] http://mojo.codehaus.org/javascript-maven-tools
[2] http://www.dev.abiss.gr/mvn-jstools
[3] http://ossi.mobilvox.com/maven-js-plugin
BTW is not my intention to insult anyone. I really do appreciate

all effort

Post by Minto van der Sluis
people have put into this, but my impression is javascript support

has been

Post by Minto van der Sluis
scattered and it seems sort of aborted or at least neglected :-(
---------------------------------------------------------------------

------------------------------------------------------------------------
Hotmail: Free, trusted and rich email service. Get it now.
<http://clk.atdmt.com/GBL/go/171222984/direct/01/>

[nicolas de loof]

I created the javascript-maven-pluging two years agoI didn't work on it
anymore for a while as I don't use it @work and have no more time left to
work on it

Patch are welcome if you'd like to support & improve it ;)

Post by Minto van der Sluis
Hi Folks,
What's the best way to handle javascript using Maven? I have searched the
ML archive but it seems all projects have sort of died
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared
Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin
- functionality limited to compression
- the still some very limited svn activity,
Is there a better way to work with javascript files, or have I been spoiled
by the maven java functionality?
Regards,
Minto 'misl' van der Sluis
[1] http://mojo.codehaus.org/javascript-maven-tools
[2] http://www.dev.abiss.gr/mvn-jstools
[3] http://ossi.mobilvox.com/maven-js-plugin
BTW is not my intention to insult anyone. I really do appreciate all effort
people have put into this, but my impression is javascript support has been
scattered and it seems sort of aborted or at least neglected :-(
---------------------------------------------------------------------

[Manos Batsis]

Post by Minto van der Sluis
What's the best way to handle javascript using Maven? I have searched
the ML archive but it seems all projects have sort of died
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared
Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin
- functionality limited to compression
- the still some very limited svn activity,

None of the above projects are dead AFAIK. None of them tries to provide
everything plus the kitchen sink but they work. People use them together
since their overlap is rather minimal.

IMHO, their development is under hibernation due to luck of
interest/suggestions/involvement from plugin users.

hth,

Manos

[nicolas de loof]

Same feedback from me. I got few users requesting status for the plugin (as
you do) and no contribution / proposal / support request in the plugin

Seems there is few maven user to build JS apps.

Post by Manos Batsis
None of the above projects are dead AFAIK. None of them tries to provide
everything plus the kitchen sink but they work. People use them together
since their overlap is rather minimal.
IMHO, their development is under hibernation due to luck of
interest/suggestions/involvement from plugin users.
hth,
Manos
---------------------------------------------------------------------

[Adam]

Same for me with the maven-js-plugin. We have in the works more
features to implement but, I have much less time than I did when I
started on it. Also, there hasn't been much requested as has been
mentioned so anything we have come up for new features has just been
the result of brainstorming instead of requested features.

Adam

On Mon, Sep 21, 2009 at 10:32 AM, nicolas de loof

Post by nicolas de loof
Same feedback from me. I got few users requesting status for the plugin (as
you do) and no contribution / proposal / support request in the plugin
Seems there is few maven user to build JS apps.

Post by Manos Batsis
None of the above projects are dead AFAIK. None of them tries to provide
everything plus the kitchen sink but they work. People use them together
since their overlap is rather minimal.
IMHO, their development is under hibernation due to luck of
interest/suggestions/involvement from plugin users.
hth,
Manos
---------------------------------------------------------------------

[Minto van der Sluis]

Oeps, it seems I stepped on some to toes, sorry guys
... and that I am spoiled ;-)

A different look gives the following results:

javascript-maven-plugin
19 open issues/ total unknown (to me)
mailing list: (archive can't be found)
commiters: 4 (olamy,ndeloof,bentman,trygvis)
# commits in 2009: 16 (svn log | grep " 2009-" | wc -l)

maven jstools plugin:
Bugs
<http://sourceforge.net/tracker/?atid=994821&group_id=205730&func=browse>
- 1 open/2 total
Feature Requests
<http://sourceforge.net/tracker/?atid=994824&group_id=205730&func=browse>
- 1 open/1 total
Patches
<http://sourceforge.net/tracker/?atid=994823&group_id=205730&func=browse>
- 0 open/0 total
Support Requests
<http://sourceforge.net/tracker/?atid=994822&group_id=205730&func=browse>
- 0 open/0 total
mailing list (users): 6 messages over 2 years
commiters: not sure, my guess is only 1 (mbatsis)
# commits in 2009: 0? (I have no cvs client)

maven-js-plugin
Bugs
<http://sourceforge.net/tracker/?atid=972557&group_id=200202&func=browse>
- 0 open/2 total
Feature Requests
<http://sourceforge.net/tracker/?atid=972560&group_id=200202&func=browse>
- 0 open/4 total
Patches
<http://sourceforge.net/tracker/?atid=972559&group_id=200202&func=browse>
- 0 open/0 total
Support Requests
<http://sourceforge.net/tracker/?atid=972558&group_id=200202&func=browse>
- 0 open/1 total
mailing list (dev): 14 messages over 3 years
commiters: 1 (mvaaltemus)
# commits in 2009: 9 (svn log | grep " 2009-" | wc -l)

With these figures javascript-maven-plugin seems the most active one to me.

A quick comparison of features gives:

javascript-maven maven-jstools maven-js
js packaging x x -
dep. mgnt compile-time runtime -
compress x - x
jsunit x - -
jsdoc x x -
jslint x x -
reporting x x -

Is this a proper feature comparison?

Lack of users has IMHO multiple causes:
1) Javascript source management is an afterthough on many project. They
include it as resources in their WAR project. (I've seen the mess ;-)
2) The road for javascript dependency management is not as clear as for
java.
3) Lack of javascript dependencies in the maven repositories (search for
javascript gives 9-16 results [1], [2] and [3])

Regards,

Minto 'misl' van der Sluis

[1] http://search.mvnsearch.org/query.action?cat=jar&q=javascript
[2] http://javarepo.xoocode.org/search?q=javascript
[3] http://mvnrepository.com/search.html?query=javascript

PS. David, GWT is not an option for existing javascript files is it?

PS. Nicolas, 19 open issues in Jira, so there is some community feedback
for your project.

Post by Minto van der Sluis
Hi Folks,
What's the best way to handle javascript using Maven? I have searched
the ML archive but it seems all projects have sort of died
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared
Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin
- functionality limited to compression
- the still some very limited svn activity,
Is there a better way to work with javascript files, or have I been
spoiled by the maven java functionality?
Regards,
Minto 'misl' van der Sluis
[1] http://mojo.codehaus.org/javascript-maven-tools
[2] http://www.dev.abiss.gr/mvn-jstools
[3] http://ossi.mobilvox.com/maven-js-plugin
BTW is not my intention to insult anyone. I really do appreciate all
effort people have put into this, but my impression is javascript
support has been scattered and it seems sort of aborted or at least
neglected :-(
---------------------------------------------------------------------

[Manos Batsis]

Post by Minto van der Sluis
Oeps, it seems I stepped on some to toes, sorry guys
... and that I am spoiled ;-)

Aren't we all ;-)

Post by Minto van der Sluis
1) Javascript source management is an afterthough on many project. They
include it as resources in their WAR project. (I've seen the mess ;-)
2) The road for javascript dependency management is not as clear as for
java.

Bingo. jstools is not only a maven plugin; it is also used as a
classpath-like mechanism for resolving js resources at runtime (i.e.
when processing an HTTP request) within WAR projects.

In short, one can build a JS project with Maven as described in
js-packaging [1], in which case the project artifact is a JAR. A WAR
project can pool that jar as usual by adding it in the dependencies
section within the POM.

The jstools should also be added as a dependency to the WAR, making the
JavascriptDependencyFilter [2] available to the web application. The
filter is responsible for resolving js or other static resources and
produce proper responses to HTTP requests.

In other words jstools provides runtime dep management (for war
projects) and relies on maven conventions for build time.

[1] http://dev.abiss.gr/mvn-jstools/js-packaging.html
[2]
http://dev.abiss.gr/mvn-jstools/apidocs/gr/abiss/mvn/plugins/jstools/web/JavascriptDependencyFilter.html

hth,

Manos

[Minto van der Sluis]

Hi Manos,

JavascriptDependencyFilter is a nice feature and a technical showcase,
but I would not allow a feature like that to be activated in projects I
control.

With this feature I have no absolute control over my deliverables. As
far as I can tell there is no garantee that 2 installations are exactly
identical. It even introduces a runtime dependency on the maven
repository which might not be available on all occasions.

Regards,

Minto 'misl' van der Sluis

Post by Manos Batsis

Post by Minto van der Sluis
Oeps, it seems I stepped on some to toes, sorry guys
... and that I am spoiled ;-)

Aren't we all ;-)

Post by Minto van der Sluis
1) Javascript source management is an afterthough on many project.
They include it as resources in their WAR project. (I've seen the
mess ;-)
2) The road for javascript dependency management is not as clear as
for java.

Bingo. jstools is not only a maven plugin; it is also used as a
classpath-like mechanism for resolving js resources at runtime (i.e.
when processing an HTTP request) within WAR projects.
In short, one can build a JS project with Maven as described in
js-packaging [1], in which case the project artifact is a JAR. A WAR
project can pool that jar as usual by adding it in the dependencies
section within the POM.
The jstools should also be added as a dependency to the WAR, making
the JavascriptDependencyFilter [2] available to the web application.
The filter is responsible for resolving js or other static resources
and produce proper responses to HTTP requests.
In other words jstools provides runtime dep management (for war
projects) and relies on maven conventions for build time.
[1] http://dev.abiss.gr/mvn-jstools/js-packaging.html
[2]
http://dev.abiss.gr/mvn-jstools/apidocs/gr/abiss/mvn/plugins/jstools/web/JavascriptDependencyFilter.html
hth,
Manos
---------------------------------------------------------------------

[Manos Batsis]

Hi Minto,

Post by Minto van der Sluis
Hi Manos,
JavascriptDependencyFilter is a nice feature and a technical showcase,
but I would not allow a feature like that to be activated in projects I
control.
With this feature I have no absolute control over my deliverables. As
far as I can tell there is no garantee that 2 installations are exactly
identical.

Can you please clarify that or provide an example? I don't get it :-)

Post by Minto van der Sluis
It even introduces a runtime dependency on the maven
repository which might not be available on all occasions.

Not at all. The filter only pulls js files from JARs already within the
WAR classpath.

Cheers,

Manos

[Sluis, M. van der (Minto)]

Hi Manos,

It seems I misunderstood the functionality. I thought .js files were
pulled from outside the delivered EAR/WAR file straight from the maven
repository.

In this case the part you didn't get does not apply anymore. The same
counts for my objections.

Regards,

Minto

-----Oorspronkelijk bericht-----
Van: Manos Batsis [mailto:***@geekologue.com]
Verzonden: dinsdag 22 september 2009 11:18
Aan: Maven Users List
Onderwerp: Re: Javascript support


Hi Minto,

Post by Minto van der Sluis
Hi Manos,
JavascriptDependencyFilter is a nice feature and a technical showcase,
but I would not allow a feature like that to be activated in projects
I control.
With this feature I have no absolute control over my deliverables. As
far as I can tell there is no garantee that 2 installations are
exactly identical.

Can you please clarify that or provide an example? I don't get it :-)

Post by Minto van der Sluis
It even introduces a runtime dependency on the maven
repository which might not be available on all occasions.

Not at all. The filter only pulls js files from JARs already within the
WAR classpath.

Cheers,

Manos

---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@maven.apache.org
For additional commands, e-mail: users-***@maven.apache.org


=============================DISCLAIMER============================

De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd
voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u
er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de
rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken
aan andere personen dan de geadresseerde. Indien u deze e-mail
abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender
op de hoogte, waarbij u bij deze gevraagd wordt het originele bericht
te vernietigen. Politie Amsterdam-Amstelland is niet verantwoordelijk
voor de inhoud van deze e-mail en wijst iedere aansprakelijkheid af
voor en/of in verband met alle gevolgen en/of schade van een onjuiste
of onvolledige verzending ervan. Tenzij uitdrukkelijk het tegendeel
blijkt, kunnen aan dit bericht geen rechten worden ontleend. Het
gebruik van Internet e-mail brengt zekere risico?s met zich mee.
Daarom wordt iedere aansprakelijkheid voor het gebruik van dit medium
door de Politie Amsterdam-Amstelland van de hand gewezen.

[Manos Batsis]

Post by Sluis, M. van der (Minto)
It seems I misunderstood the functionality. I thought .js files were
pulled from outside the delivered EAR/WAR file straight from the maven
repository.

Truth is I need to make this clearer in the documentation.

To provide an example, suppose you wanted to include the sarissa
javascript library as a dependency in the WAR and make it available
automatically to HTTP clients:


<dependency>
<groupId>gr.abiss.mvn.plugins</groupId>
<artifactId>maven-jstools-plugin</artifactId>
</dependency>
<dependency>
<groupId>gr.abiss.js</groupId>
<artifactId>sarissa</artifactId>
</dependency>

The sarissa script is then available by default (the URL pattern is
configurable) as

http://domain.tld/lib/js/gr/abiss/js/sarissa/sarissa.js

hth,

Manos

[David Hoffer]

I don't think GWT can manage existing JS files. GWT could be used for new
dev and the rest as a static resource which could be used by GWT if desired.

Post by Minto van der Sluis
Oeps, it seems I stepped on some to toes, sorry guys
... and that I am spoiled ;-)
javascript-maven-plugin
19 open issues/ total unknown (to me)
mailing list: (archive can't be found)
commiters: 4 (olamy,ndeloof,bentman,trygvis)
# commits in 2009: 16 (svn log | grep " 2009-" | wc -l)
Bugs <
http://sourceforge.net/tracker/?atid=994821&group_id=205730&func=browse> -
1 open/2 total
Feature Requests <
http://sourceforge.net/tracker/?atid=994824&group_id=205730&func=browse> -
1 open/1 total
Patches <
http://sourceforge.net/tracker/?atid=994823&group_id=205730&func=browse> -
0 open/0 total
Support Requests <
http://sourceforge.net/tracker/?atid=994822&group_id=205730&func=browse> -
0 open/0 total
mailing list (users): 6 messages over 2 years
commiters: not sure, my guess is only 1 (mbatsis)
# commits in 2009: 0? (I have no cvs client)
maven-js-plugin
Bugs <
http://sourceforge.net/tracker/?atid=972557&group_id=200202&func=browse> -
0 open/2 total
Feature Requests <
http://sourceforge.net/tracker/?atid=972560&group_id=200202&func=browse> -
0 open/4 total
Patches <
http://sourceforge.net/tracker/?atid=972559&group_id=200202&func=browse> -
0 open/0 total
Support Requests <
http://sourceforge.net/tracker/?atid=972558&group_id=200202&func=browse> -
0 open/1 total
mailing list (dev): 14 messages over 3 years
commiters: 1 (mvaaltemus)
# commits in 2009: 9 (svn log | grep " 2009-" | wc -l)
With these figures javascript-maven-plugin seems the most active one to me.
javascript-maven maven-jstools maven-js
js packaging x x -
dep. mgnt compile-time runtime -
compress x - x
jsunit x - -
jsdoc x x -
jslint x x -
reporting x x -
Is this a proper feature comparison?
1) Javascript source management is an afterthough on many project. They
include it as resources in their WAR project. (I've seen the mess ;-)
2) The road for javascript dependency management is not as clear as for
java.
3) Lack of javascript dependencies in the maven repositories (search for
javascript gives 9-16 results [1], [2] and [3])
Regards,
Minto 'misl' van der Sluis
[1] http://search.mvnsearch.org/query.action?cat=jar&q=javascript
[2] http://javarepo.xoocode.org/search?q=javascript
[3] http://mvnrepository.com/search.html?query=javascript
PS. David, GWT is not an option for existing javascript files is it?
PS. Nicolas, 19 open issues in Jira, so there is some community feedback
for your project.
Hi Folks,

Post by Minto van der Sluis
What's the best way to handle javascript using Maven? I have searched the
ML archive but it seems all projects have sort of died
- svn activity is near to none for the last year.
- sources and web-site seem to be out of sync.
- site contains a few dead links ()
- dedicated mailing list archive seem to have disappeared
Jstools plugin does not seems to be in a much better shape.
- last svn activity is 19 months ago.
- less functionality than javascript-maven-plugin
- functionality limited to compression
- the still some very limited svn activity,
Is there a better way to work with javascript files, or have I been
spoiled by the maven java functionality?
Regards,
Minto 'misl' van der Sluis
[1] http://mojo.codehaus.org/javascript-maven-tools
[2] http://www.dev.abiss.gr/mvn-jstools
[3] http://ossi.mobilvox.com/maven-js-plugin
BTW is not my intention to insult anyone. I really do appreciate all
effort people have put into this, but my impression is javascript support
has been scattered and it seems sort of aborted or at least neglected :-(
---------------------------------------------------------------------

---------------------------------------------------------------------

[Neil Chaudhuri]

I have 4 poms:

1) parent, which has common dependencies and configuration shared by children
2) persistence, which packages a jar and is a child of parent
3) services, which packages a war, is a child of parent, and has persistence as a dependency
4) logging, which packages a jar that is a dependency of both persistence and services but is not part of the parent-child relationship shared by the others

I want to use the Maven assembly plugin so that I can build a war file in one command line execution. This means packaging and installing logging, then packaging and installing persistence, then packaging services.

Can you tell me where I should define my assembly plugin configuration? At the parent? Also, what would it look like roughly?

Thanks.

[Luca Li Greci]

Hi Neil,

I usually add a project for the distribution so that I can decouple the
"build logic" from the modules. In the parent I define the assembly plugin
and in this distribution module I write the assembly under
src/resources/assembly.

Using this approach will avoid weird situation where one module (I assume
the persistence) needs to be built before one other (I assume the service)

To write my assembly descriptor I've read
http://www.sonatype.com/books/maven-book/reference/assemblies.html

and I used FileSets and dependencySets.

Best regards

Luca

Post by Neil Chaudhuri
1) parent, which has common dependencies and configuration shared by children
2) persistence, which packages a jar and is a child of parent
3) services, which packages a war, is a child of parent, and has
persistence as a dependency
4) logging, which packages a jar that is a dependency of both persistence
and services but is not part of the parent-child relationship shared by the
others
I want to use the Maven assembly plugin so that I can build a war file in
one command line execution. This means packaging and installing logging,
then packaging and installing persistence, then packaging services.
Can you tell me where I should define my assembly plugin configuration? At
the parent? Also, what would it look like roughly?
Thanks.
---------------------------------------------------------------------

[Neil Chaudhuri]

I have that book, but it isn't clear to me if the assembly plugin actually builds and installs all the components. The way it reads, it seems like you simply describe where existing files live to be included in the assembly. It doesn't seem to actually build the dependencies. Am I wrong on this?

Thanks.

Neil


-----Original Message-----
From: Luca Li Greci [mailto:***@gmail.com]
Sent: Mon 9/21/2009 4:00 PM
To: Maven Users List
Subject: Re: Understanding Assembly Plugin

Hi Neil,

I usually add a project for the distribution so that I can decouple the
"build logic" from the modules. In the parent I define the assembly plugin
and in this distribution module I write the assembly under
src/resources/assembly.

Using this approach will avoid weird situation where one module (I assume
the persistence) needs to be built before one other (I assume the service)

To write my assembly descriptor I've read
http://www.sonatype.com/books/maven-book/reference/assemblies.html

and I used FileSets and dependencySets.

Best regards

Luca

Post by Neil Chaudhuri
1) parent, which has common dependencies and configuration shared by children
2) persistence, which packages a jar and is a child of parent
3) services, which packages a war, is a child of parent, and has
persistence as a dependency
4) logging, which packages a jar that is a dependency of both persistence
and services but is not part of the parent-child relationship shared by the
others
I want to use the Maven assembly plugin so that I can build a war file in
one command line execution. This means packaging and installing logging,
then packaging and installing persistence, then packaging services.
Can you tell me where I should define my assembly plugin configuration? At
the parent? Also, what would it look like roughly?
Thanks.
---------------------------------------------------------------------

[Luca Li Greci]

Post by Neil Chaudhuri
I have that book, but it isn't clear to me if the assembly plugin actually
builds and installs all the components. The way it reads, it seems like you
simply describe where existing files live to be included in the assembly. It
doesn't seem to actually build the dependencies. Am I wrong on this?
Thanks.
Neil

Neil,

The reason for using an assembly is to generate "the final distribution",
this file could include not only the library that you're developing (and 3rd
part dependency) but also scripts (*.bat, *.sh) for the startup purpose, or
spring/application configuration.

In your case, I believe that this chapter should give you the answer you
need
http://www.sonatype.com/books/maven-book/reference/assemblies-set-dist-assemblies.html

Luca

Post by Neil Chaudhuri
-----Original Message-----
Sent: Mon 9/21/2009 4:00 PM
To: Maven Users List
Subject: Re: Understanding Assembly Plugin
Hi Neil,
I usually add a project for the distribution so that I can decouple the
"build logic" from the modules. In the parent I define the assembly plugin
and in this distribution module I write the assembly under
src/resources/assembly.
Using this approach will avoid weird situation where one module (I assume
the persistence) needs to be built before one other (I assume the service)
To write my assembly descriptor I've read
http://www.sonatype.com/books/maven-book/reference/assemblies.html
and I used FileSets and dependencySets.
Best regards
Luca

Post by Neil Chaudhuri
1) parent, which has common dependencies and configuration shared by children
2) persistence, which packages a jar and is a child of parent
3) services, which packages a war, is a child of parent, and has
persistence as a dependency
4) logging, which packages a jar that is a dependency of both persistence
and services but is not part of the parent-child relationship shared by

the

Post by Neil Chaudhuri
others
I want to use the Maven assembly plugin so that I can build a war file in
one command line execution. This means packaging and installing logging,
then packaging and installing persistence, then packaging services.
Can you tell me where I should define my assembly plugin configuration?

At

Post by Neil Chaudhuri
the parent? Also, what would it look like roughly?
Thanks.
---------------------------------------------------------------------

--
Victor Hugo wrote, "The future has many names: For the weak, it means the
unattainable. For the fearful, it means the unknown. For the courageous, it
means opportunity."
---------------------------------------------------------------------

[nicolas de loof]

Post by Minto van der Sluis
PS. Nicolas, 19 open issues in Jira, so there is some community feedback
for your project.

Half of them are Harlan Iverson todo list (also committer in this project)
Some may get fixed quickly, but few of them has patch attached.

By "feedback" I suggested mailing list activity on user or
***@mojo.codehaus.org

I'd be pleased to work more one this project if I got more time ...

Nicolas

[Sluis, M. van der (Minto)]

It seems we all suffer from the same.

A day only has 24 hours and a few of them are required for hibernation.
Why don't we all state that a day has a 100 hours then we would at least
be ably to do 4 times as much ;-)

On the otherhand, we could also try to improve our efficiency, but that
is much harder to achieve.

Misl


-----Oorspronkelijk bericht-----
Van: nicolas de loof [mailto:***@gmail.com]
Verzonden: dinsdag 22 september 2009 14:17
Aan: Maven Users List
Onderwerp: Re: Javascript support

Post by Minto van der Sluis
PS. Nicolas, 19 open issues in Jira, so there is some community
feedback for your project.

Half of them are Harlan Iverson todo list (also committer in this
project) Some may get fixed quickly, but few of them has patch attached.

By "feedback" I suggested mailing list activity on user or
***@mojo.codehaus.org

I'd be pleased to work more one this project if I got more time ...

Nicolas

=============================DISCLAIMER============================

De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd
voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u
er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de
rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken
aan andere personen dan de geadresseerde. Indien u deze e-mail
abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender
op de hoogte, waarbij u bij deze gevraagd wordt het originele bericht
te vernietigen. Politie Amsterdam-Amstelland is niet verantwoordelijk
voor de inhoud van deze e-mail en wijst iedere aansprakelijkheid af
voor en/of in verband met alle gevolgen en/of schade van een onjuiste
of onvolledige verzending ervan. Tenzij uitdrukkelijk het tegendeel
blijkt, kunnen aan dit bericht geen rechten worden ontleend. Het
gebruik van Internet e-mail brengt zekere risico?s met zich mee.
Daarom wordt iedere aansprakelijkheid voor het gebruik van dit medium
door de Politie Amsterdam-Amstelland van de hand gewezen.