date:20070805

[OT] Mini-interview with Emmanuel Venisse of Maven and Continuum

2007-08-05 Thread Brett Porter

Hi all,

I thought I might post this in case anyone was interested in getting
to know Emmanuel a bit better: http://www.devzuz.org/?q=node/12

Emmanuel is a long term committer to Maven, who has done a bunch of
stuff and is always busy. It was great fun talking to him.

I hope you find it interesting - I'm hoping to post more of these on
the site in the future, along with some other things that are
generally useful to Maven users but which wouldn't normally be put on
the project site.

Cheers,
Brett

-- 
Brett Porter
Blog: http://www.devzuz.org/blogs/bporter/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: how to specify multiple descriptors on the command-line

2007-08-05 Thread Maria Odea Ching


Hi Lara,

I don't think it's possible to specify the descriptors from the command 
line as it seems to be not supported by the assembly plugin.
Maybe you could try using profiles [1] to separate the different types 
of descriptors (e.g. different plugin config in each profile) for what 
you want to do?


HTH,
Deng

[1] 
http://maven.apache.org/guides/introduction/introduction-to-profiles.html



Lara Brian wrote:

Hi Deng,
Thanks for the reply. Your suggestion (to place the descriptors in the pom)
worked. Thanks a lot. But is there a way to just specify from command line?
The reason i need this is, i have few assembly descriptors (for various
sources, javadocs and few for binaries). I have a plugin that checks for
conflicitng versions in dependencies. I need to run that plugin only for
binaries and not for others. If i specify all the descriptors in the POM i
cannot differentiate one from the other.

I could run individual descriptor by -Ddescriptor option but not descriptors
with -Ddescriptors option. I tried the full path as you specified and still
no luck.

Thanks a lot for any help.
 


Maria Odea Ching-2 wrote:
  

Hi,

Try configuring these descriptors in the pom (shown below) instead of 
setting it at the command-line. Also, I think the path to the 
descriptors should be included instead of just the descriptor filename.



  
maven-assembly-plugin

  
path/to/cmp-server.xml
path/to/cmp-client.xml
  

  



HTH,
Deng

Lara Brian wrote:


Hi All,
How to specify multiple descriptors on the command line when invoking
assebly plugin? What is the separator for the descriptors. I tried
comma/colan but ended up unsuccessful.

I tried,
mvn package assembly:assembly -Ddescriptors=cmp-server.xml,cmp-client.xml
-Dmaven.test.skip=true

but getting,
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error reading assemblies: No assembly descriptors found.

[INFO]


thanks a lot.
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Maven dependency versions

2007-08-05 Thread Dave Hoffer

It is critical that an artifact with version a.b.c.0 never change
irregardless of what repository it is located in.  A released artifact
is static, that is, it is never updated.

It sounds like you want to use SNAPSHOTS which are non-released
development artifact versions.  SNAPSHOTS can be updated.  Maven will
check remote repositories and download newer versions (SNAPSHOTS and
releases) as configured.

-Dave

-Original Message-
From: Morgovsky, Alexander (US - Glen Mills)
[mailto:[EMAIL PROTECTED] 
Sent: Sunday, August 05, 2007 4:26 PM
To: users@maven.apache.org
Subject: Maven dependency versions

If I have an artifact of version a.b.c.0 in my local repository, and
someone uploads a newer artifact with version a.b.c.0 to the remote
repository, will my dependent project check if there is a newer version
of artifact a.b.c.0 in all of the repositories compared to that in my
local repository, or will it find the older artifact in the local
repository and not look for the newer one in the remote repository?
Thanks. 


This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law.  If you are not the intended recipient, you should
delete this message. 


Any disclosure, copying, or distribution of this message, or the taking
of any action based on it, is strictly prohibited. [v.E.1]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Overriding artifact name in the repository

2007-08-05 Thread Ronn . Chinowutthichai

Hi there,

Pom.xml allows you to override final name of the artifact that gets 
generated. However, this final name doesn't get carried through when you 
deploy to the repository.

I.e., if you have

/myproject/common/library/pom.xml

and say you override final name as myproject-common-library, 
myproject-common-library-1.1.jar gets generated.

That is fine and good, however, when I deploy this library to the 
repository, the actual file name that resides in the repository is 
library-1.1.jar

Is there anything I have missed?

Is there a way to override the artifact name that gets deployed into the 
repository?


Cheers,
rOnn c.
##
DISCLAIMER:
This email and any attachment may contain confidential information.
If you are not the intended recipient you are not authorized to copy
or disclose all or any part of it without the prior written consent
of Toyota.

Opinions expressed in this email and any attachments are those of the
sender and not necessarily the opinions of Toyota.
Please scan this email and any attachment(s) for viruses.
Toyota does not accept any responsibility for problems caused by
viruses, whether it is Toyota's fault or not.
##

Re: Maven dependency versions

2007-08-05 Thread Wayne Fay

If its a SNAPSHOT, then it will look. Otherwise, it will not.

In this case, it sounds like it is not a SNAPSHOT, therefore it will
not look for updates. For Maven to work properly, released versions
must *not* change. If you have files that can/will change, you must
call them SNAPSHOTs.

Wayne

On 8/5/07, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]> wrote:
> If I have an artifact of version a.b.c.0 in my local repository, and
> someone uploads a newer artifact with version a.b.c.0 to the remote
> repository, will my dependent project check if there is a newer version
> of artifact a.b.c.0 in all of the repositories compared to that in my
> local repository, or will it find the older artifact in the local
> repository and not look for the newer one in the remote repository?
> Thanks.
>
>
> This message (including any attachments) contains confidential information 
> intended for a specific individual and purpose, and is protected by law.  If 
> you are not the intended recipient, you should delete this message.
>
>
> Any disclosure, copying, or distribution of this message, or the taking of 
> any action based on it, is strictly prohibited. [v.E.1]
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Maven dependency versions

2007-08-05 Thread Morgovsky, Alexander $US - Glen Mills$

If I have an artifact of version a.b.c.0 in my local repository, and
someone uploads a newer artifact with version a.b.c.0 to the remote
repository, will my dependent project check if there is a newer version
of artifact a.b.c.0 in all of the repositories compared to that in my
local repository, or will it find the older artifact in the local
repository and not look for the newer one in the remote repository?
Thanks. 


This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited. [v.E.1]

Re: eclipse-plugin generates weird classpath entries

2007-08-05 Thread noon


Are they transitive Maven dependencies? If they are, you can exclude them out
in your pom.xml. 

To see which dependency brings these transitive dependencies, try maven -X
and study the dependency tree which maven prints to console.
-- 
View this message in context: 
http://www.nabble.com/eclipse-plugin-generates-weird-classpath-entries-tf4214170s177.html#a12007519
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Building EAR with ATG modules using Maven 2

2007-08-05 Thread mukundh

Hi,

We are currently stuck with the approach of building an EAR file using the
ATG modules to be deployed i n JBoss.

We have defined the following plugins
PMD, JUnit

Now for packaging the ear, ATG provides a assember utility called
runassember.bat which identfies the ATG dependent modules and package a
standalone ear. Hence we are trying to leverage this rather than writing the
whole packaging ourselves.

Our current problem is how to tell Maven that the Runassembler.bat will be
responsible for building the EAR. We are typically looking at something
like this

maven compile
maven pmd:pmd
maven test

Now after this we wanted to understand how we can effectively call the
runassembler so that Maven delegates the building of ear to the runassember.

Please find the extract of the POM.xml

junit
junit
3.8.1
test

lib
assembler
1.0

lib
dss
1.0

lib
dps
1.0

org.apache.maven.scm
maven-scm-provider-svn
1.0-alpha-4

scm:svn:https://...>
scm:svn://...
..

org.apache.maven.plugins
maven-compiler-plugin

1.5
1.5

org.apache.maven.plugins
maven-pmd-plugin

1.5
html
true
utf-8
100

bin
bin/classes
${pom.artifactId}-${pom.version}
bin/test-classes
src
src/main/scripts
src

src/main/resources

src/test/resources

true
org.apache.maven.plugins
maven-scm-plugin

D:\ATG\ATG2006.3

SInce this is very urgent, any help would be highly appreceiated

Thanks in advance.
-Mukundh

--
View this message in context:
http://www.nabble.com/Building-EAR-with-ATG-modules-using-Maven-2-tf4219783s177.html#a12004580
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Database lifecycle in Maven

2007-08-05 Thread Geoffrey De Smet

We have a one-time-use prebuild.sh script to create 2 databases (not the 
tables): a normal one and a test one.

Our integration tests are done in spring, which:
1) Boots hibernate-jpa, which does a hbm2ddl=create to create the tables
2) Fires DBunit to create testdata in that database.
Our normal runs in development for now use hbm2ddl=update.

Maven's lifecycle really isn't used in this process.

With kind regards,
Geoffrey De Smet


Wayne Fay wrote:

This is the second time you've asked, so I figured I'd reply with what
I know, which isn't much.

1) Not that I am aware of.
2) Not that I am aware of. We handle this manually with ant scripts
that run before/after our builds/deploys.

Wayne

On 8/4/07, Victor Bendig <[EMAIL PROTECTED]> wrote:

Hi,

Have a couple of questions around databases and maven,

1. Does Maven create standards for database development?
2. Is there a plugin that handles the lifecycle of the database (create,
drop, etc)

I found a sql-maven-plugin but this forces me to bind sql files to code
phases.  While this might be good when testing, I find it might be heavy if
I bind the install of my project with the database creation.

Any ideas where I can look for this?

Regards,


--
Victor Bendig




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Auto incrementing a build identifier

2007-08-05 Thread Antony Stubbs


That's exactly what M2 needs - would you consider releasing your mojo? I'd
love to try using.
IMO this should be apart of the m2 deploy goal.

The problem with Mavin buildnumber plugin, is that it isn't synced with the
build number repository.


Artamonov, Juri wrote:
> 
>>The thing is that I don't want to generate "new" builds during
> development, overwriting the current snapshot is preferred. But when
> processing a project which will be "publicly" available, I want to be
> able to identify it >(even a snapshot) with an incremented build number,
> but without having to manage the version setting by hand.
> 
> IMHO, this is (I mean let's say snapshot numbering) not yet covered well
> in m2.
> 
> I have requirement also for myself to distunguish two snapshot builds
> and here is what I did...
> 
> 1. I use maestro stuff with continuum and m2. When I do install I have
> files like 1.0-SNPASHOT- in repository. BUILD_NUMBER is
> always inrementing on 1 when new version is installed into repository.
> 2. I wrote the plugin which get latest BUILD_NUMBER from repository and
> do +1 during for example compile phase. Now I know what build version is
> going to be and I put this information into manifest file or war file or
> for example jar file. Now I have information inside of the archive that
> allows me to distinguish two snapshot versions.
> 
> Also you can use
> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/ plugin but
> seems having it working requires a lot of manual work, due missing
> versions on the repositories of the components listed in the
> dependencies.
> 
> Best regards,
>   Juri.
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Friday, September 22, 2006 8:30 PM
> To: users@maven.apache.org
> Subject: Auto incrementing a build identifier
> 
> 
> A question about version numbering in Subversion.
> 
> I am aware of the way subversion handles version information while
> releasing. As I have peeked overhere in the Maven repository:
> 
> https://svn.apache.org/repos/asf/maven/plugins/tags/maven-release-plugin
> -2.0-beta-4/src/main/java/org/apache/maven/plugins/release/versions/Defa
> ultVersionInfo.java
> 
> Now I am wondering about something. My current contract would like a
> build increment value in between two brackets. Which auto increases with
> each build delivered to production. I'd say that hooking into the deploy
> phase would be a good time for such actions. But then I figure that it
> isn't.
> 
> I'd say the initialize phase is the correct one. Since I am not
> processing resources or sources but the POM.xml. The thing is this, can
> I modify the POM then and there and keep the build going or do I need to
> modify the POM. And let the user start another run, just like the
> release plugin does?
> 
> Also, is it possible (by documented API or acceptable convention) to
> detect whether or not a build is running up to or past the deploy phase?
> 
> The thing is that I don't want to generate "new" builds during
> development, overwriting the current snapshot is preferred. But when
> processing a project which will be "publicly" available, I want to be
> able to identify it (even a snapshot) with an incremented build number,
> but without having to manage the version setting by hand.
> 
> Any suggestions are greatly apreciated.
> 
> Kind regards,
> Jeroen Leenarts
> http://blog.leenarts.net
> 
> Download this as a file
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Auto-incrementing-a-build-identifier-tf2319084s177.html#a12003652
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] How to add timestamp of build to properties file using filtering?