Re: How to handle Incremental Versions

[amit kumar]

I am using buildnumber plugin now to append timestamp to the builds.
But at continuous integration ( Continuum) I am facing the problem
because in the pom.xml for any dependency I have specified a
particular version say 1.0, but after using the buildnumber plugin the
builds have a different version everytime(varying with time). How to
handle this?




On Jan 21, 2008 12:34 PM, amit kumar <[EMAIL PROTECTED]> wrote:
> Hi,
> If I use buildnumber plugin to have builds with versions in
> incremental fashion, is there any way to handle this changed version
> of the artifact in the pom.xmls of other artifacts which are dependent
> on such a particular module(with incremental versions)
>
> Regards,
> Amit
>

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

How to handle Incremental Versions

[amit kumar]

Hi,
If I use buildnumber plugin to have builds with versions in
incremental fashion, is there any way to handle this changed version
of the artifact in the pom.xmls of other artifacts which are dependent
on such a particular module(with incremental versions)

Regards,
Amit

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

Re: [m2] continuum dashboard integration?

[Wendy Smoak]

On Jan 20, 2008 2:47 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:

> My basic issue is that my continuum does not seem to run more than the 1st
> goal for a project as setup in the "Project Information Tab", "Build
> Definitions" section" of continuum.

The terms 'goal' and 'build definition' are not interchangeable.  A
build definition can have one or more goals defined.

I think you're saying that only the first of your three build
definitions runs, meaning the entire thing (all three goals/phases you
have defined in it) happen, and then nothing else.

What is in the log file at this time?  There should be a reason for
"nothing happens" for the second and third definition.  You might see
something like "No changes, not building".

I thought the determination of "have any changes happened" was done
per build definition, but maybe it's per project (or broken.)

What happens if you check the 'Always Build' checkbox on all three
build definitions?

-- 
Wendy

Re: EJB WebSphere dependencies

[Siarhei Dudzin]

Try to setup a remote repository like Artifactory. We use one and have not
problems so far...

Regards,
Siarhei

On 1/16/08, Marcus Müller <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I'm currently trying to use Maven2 for creating an EAR file which
> contains among some utitlity-JARs an EJB-project using EJB 2.1 and
> containing one message driven bean.
>
> I have problems there compiling the project as the EJB-implementation
> should be used from a WebSphere 6.0 server. So what I did is to put the
> j2ee.jar from WebSphere into my local Maven2 repository. But when I
> compile with like "mvn install" I get the following error messages:
>
> Downloading: http://repo1.maven.org/maven2/websphere/j2ee/1/j2ee-1.pom
> [WARNING] Unable to get resource from repository central
> (http://repo1.maven.org/maven2)
> [INFO] [compiler:compile]
> [INFO] Compiling 1 source file to D:\projects\ProjectEJB\target\classes
> [INFO]
>
> 
> [ERROR] BUILD FAILURE
> [INFO]
>
> 
> [INFO] Compilation failure
> MDBBean.java:[143,44] cannot resolve symbol
> symbol  : method createConnection (java.lang.String,java.lang.String)
> location: interface javax.jms.ConnectionFactory
> MDBBean.java:[146,49] cannot resolve symbol
> symbol  : method createSession (boolean,int)
> location: interface javax.jms.Connection
> MDBBean.java:[149,61] cannot resolve symbol
> symbol  : method createProducer (javax.jms.Destination)
> location: interface javax.jms.Session
> MDBBean.java:[161,32] cannot resolve symbol
> symbol  : method send (javax.jms.MapMessage)
> location: interface javax.jms.MessageProducer
>
> My repository contains the file websphere/j2ee/1/j2ee-1.jar which I
> copied from the WebSphere/lib directory and which indeed does contain
> the classes Maven2 is moaning about.
>
> The dependency config is:
> 
> 
>   websphere
>   j2ee
>   1
> 
> 
>   websphere
>   mail
>   impl
> 
> 
>   websphere
>   activation
> impl
>   
> 
>
>
> I copied the activation-impl.jar and mail-impl.jar into my local repo
> too, because the MANIFEST.MF of j2ee.jar contains them. Still it doesn't
> compile.
>
> Any help at this point is very appreciated.
>
> Is it possible to include the whole WebSphere runtime or would I need to
> import all the jar's to my local repo (like >100 :( )?
>
> Kind regards
> Marcus
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Avoid Dependency version

[Michael McCallum]

On Sun, 20 Jan 2008 17:16:46 Brian E. Fox wrote:
> You can use dependencyManagment in a parent pom to avoid specifying the
> version in all your child poms. If you really want the "latest" you have
I thought the depedencyManagement section was going away in 2.1 because its a 
poor implentation of an externalised version manifest... 

why not use version ranges they work very well, and give you a bit more 
control over your deliverables.

RELEASE and LATEST I guarantee will cause you grief, and IMHO contrary to what 
is emerging as best practice.

-- 
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]

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

Re: Copyright Symbol broken in Javadoc

[Jochen Wiedmann]

On Jan 19, 2008 5:25 PM, Vincent Siveton <[EMAIL PROTECTED]> wrote:

> The bottom uses © for the copyright. So I guess UTF-8 is used in
> command line.

See

http://www.nabble.com/Handling-of-encoding-in-commons-parent-to14975629.html

for my conclusions.


-- 
Look, that's why there's rules, understand? So that you think before
you break 'em.

-- (Terry Pratchett, Thief of Time)

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

Re: [m2][archiva1] Issue deploying to Archiva

[Kaizer H. Sogiawala]

Related question - Is this a case sensitive match?

Thanks!

On 1/14/08, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Jan 14, 2008 11:27 AM, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> > I can deploy my site docs to my remote server just fine, but when I try to
> > deploy a module to my archiva REP, I get a 401 error.
>
> Please choose *one* list and ask your question there.  Someone will
> tell you if you're in the wrong place.  Many of the people who can
> help are already reading both lists, and cross-posting just causes
> duplicate traffic, as well as splitting a conversation so it's hard to
> follow in the archives.
>
> In this case it doesn't look like a problem with Archiva, just a
> problem with configuration, so I'm replying on [EMAIL PROTECTED] You have:
>
> > *pom.xml:*
> >
> > 
> > 
> > dap.internal
> ...
> > 
> > dap.snapshots
> > 
>
> and
>
> > *settings.xml:*
> ...
> > rc_sun66e-site
> > rc_sun66e-repository
> > dap2.internal
> > deployment.webdav
> > deployment.webdav
>
> In order for Maven to figure out what credentials to send to the
> server, the ids need to match in the pom.xml distributionManagement
> section, and settings.xml servers section.
>
> You're probably getting the 401 because Maven isn't supplying any credentials.
>
> --
> Wendy
>
> -
> 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: [m2] continuum dashboard integration?

[Mick Knutson]

Is there no person that is using Continuum in this way? I really do need
some help here please. I would really appreciate it...


On Jan 18, 2008 11:25 AM, Mick Knutson <[EMAIL PROTECTED]> wrote:

> How do I run more than one goal in a series? Can anyone help me?
>
>
>
> On Jan 17, 2008 8:56 AM, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> > Ok, I am switching lists now as I am now into issues with continuum.
> >
> > Issue #1:
> > I followed:
> > http://mojo.codehaus.org/dashboard-maven-plugin/continuum.html
> >
> > Thus I have this setting:
> > clean package site --batch-mode -P documentation -e -
> > Dbuild.type=documentation pom.xml 
> > DEFAULT_SCHEDULE
> >   GROUP true true DAP clean install site maven2 [image: Build]
> > 
> >   [image:
> > Edit]
> > 
> >   [image:
> > Delete]
> > 
> > dashboard-report:dashboard --batch-mode -P documentation -e -
> > Dbuild.type=documentation pom.xml 
> > DEFAULT_SCHEDULE
> >   PROJECT true false dashboard-report:dashboard maven2 [image: Build]
> > 
> >   [image:
> > Edit]
> > 
> >   [image:
> > Delete]
> > 
> > site:deploy --batch-mode -P documentation -e -Dbuild.type=documentation
> > pom.xml 
> > DEFAULT_SCHEDULE
> >   PROJECT true false site:deploy maven2 [image: Build]
> > 
> >   [image:
> > Edit]
> > 
> >   [image:
> > Delete]
> > 
> > But still only the 1st goal is ever run. How can I get the others to
> > run?
> >
> >
> >
> >
> >
> > On Jan 15, 2008 7:00 PM, Kalle Korhonen < [EMAIL PROTECTED]>
> > wrote:
> >
> > > On 1/15/08, Mick Knutson < [EMAIL PROTECTED]> wrote:
> > > >
> > > > http://mojo.codehaus.org/dashboard-maven-plugin/continuum.html
> > > > I do not understand what is meant by first goal, second goal and
> > > third
> > > > goal.
> > > > DO I need to setup a seperate Maven2 project in my default project
> > > group
> > > > for
> > > > each goal?
> > > >
> > >
> > > No. Open your project definition in Continuum (as admin or as user
> > > with
> > > proper rights) and add the three build definitions as explained.
> > >
> > > Kalle
> > >
> > >
> > >
> > > --
> > > > Thanks,
> > > > Mick Knutson
> > > >
> > > > http://www.baselogic.com
> > > > http://www.blincmagazine.com
> > > > http://www.djmick.com
> > > > http://www.myspace.com/mickknutson
> > > > http://www.myspace.com/BLiNCMagazine
> > > > http://tahoe.baselogic.com
> > > > ---
> > > >
> > >
> >
> >
> >
> > --
> >
> > Thanks,
> > Mick Knutson
> >
> > http://www.baselogic.com
> > http://www.blincmagazine.com
> > http://www.djmick.com
> > http://www.myspace.com/mickknutson
> > http://www.myspace.com/BLiNCMagazine
> > http://tahoe.baselogic.com
> > ---
> >
>
>
>
> --
>
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/BLiNCMagazine
> http://tahoe.baselogic.com
> ---
>



-- 
Thanks,
Mick Knutson

http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/BLiNCMagazine
http://tahoe.baselogic.com
---

Re: How to set up an Eclipse library plugin

[Marshall Schor]

I found one way to do the jar building.  The idea is to have the 
eclipse-runtime POM project include two things:


1) a Jar configuration specifying where to find the Eclipse manifest: 
META-INF/MANIFEST.MF


2) an extra ant-run step for the packaging phase which runs the Ant Jar 
task to update the jar that maven built with the additional libraries.
I know this is not the maven way, which is why I'm asking for a better 
way :-)..


-Marshall


Marshall Schor wrote:
We have a multi-jar project set up in the "flat" layout style.  We 
have a parent POM which refs all the child POMs in the  section.
We would like to have a special jar which includes a subset of some of 
the project's jars, packaged as an Eclipse plugin - a library plugin - 
for other plugins to use.  So we made a project for this which I'll 
call the eclipse-runtime plugin.  This project has no source itself; 
it serves only to collect together a (sub)set of other project's jars.
In the eclipse-runtime plugin's POM, I declare dependencies on the 
other projects whose Jars we want to include.  If I run 
eclipse:eclipse on this POM, it puts in  to the "JARs" of these 
other projects (using the corresponding Jars from my local repository) 
in the .project file, and updates the .classpath to have entries that 
reference these.  This make things work in the plug-in development 
environment.  For instance, when I have an eclipse plugin dependency 
on my runtime plugin in another Eclipse plugin-project, this other 
plugin-project compiles OK.


But - the build (both maven and Eclipse) of this runtime plugin 
produces an empty JAR - since there is no source code in the project 
itself.  I need the build to produce a jar which contains all the 
referenced JARs, I think, so when a user downloads installs the 
library plugin using Eclipses "update" mechanism, the referenced jars 
are there.


Any idea how to do this?

-

Another issue:  I tried running eclipse:eclipse goal from the parent 
POM.  I saw in another posting to this list that the eclipse:eclipse 
goal, when run from a parent POM, is supposed to create project 
dependencies, instead of  to jars in the local repository.
I tried this for my plugin projects, and found that it didn't put any 
 in the .project file for these dependencies (as expected), but 
it also didn't update the .classpath either - so as a result, things 
which depend on the runtime plugin to compile now fail to compile.  
The .classpath file has no entries at all for projects this library 
project is depending on.
I did notice that it did the right thing for *non-Eclipse-plugin* 
projects: the .classpath file had the right entries added for 
dependent projects.


Is this a known issue with the eclipse:eclipse goal, when used with 
Eclipse plugin projects?


-Marshall

-
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: Producing 2 JAR's with exclusive content

[Insitu]

Richard Gal <[EMAIL PROTECTED]> writes:

> Hello
>
> Could somebody help me with the following problem:
>
> I have a project that uses some native libraries (dll's). I would like
> to create 2 JAR artifacts out of this project
> - one with the Java classes of the project and
> - another with nothing else but the native libraries.
>

Hello,
The usual maven way is: 
 1 artifact = 1 project

So a simple solution for your problem is:
  1. a project with your java classes 
  2. a project with your native lib eg. in src/main/resources
  3. a toplevel project with these 2 As modules

HTH
-- 
Arnaud Bailly, PhD
OQube - Software Engineering
http://www.oqube.com


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

Re: Eclipse plugin and project references

[TM]

> Yes, when mvn eclipse:eclipse is run for a multi module project, the
> dependencies between the modules will be project dependencies.
> 
I see. After I started it from the root project it did work as wanted.
Thanks.

Still remains the (minor) question to me why does the plugin behaves
different depending on whether it was started from the sub module resp. the
parent project. In my opinion, this shouldn't make a difference.

Thorsten
-- 
View this message in context: 
http://www.nabble.com/Eclipse-plugin-and-project-references-tp14844945s177p14981288.html
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: How to avoid creating a jar?

[Jerome Lacoste]

On Jan 18, 2008 5:39 PM, Joshua ChaitinPollak <[EMAIL PROTECTED]> wrote:
> Hello,
>
> we have a few projects we are building with Maven which do not result
> in jar's being the final output. For those projects we are using the
> maven-assembly-plugin, but when we run 'mvn package' we still end up
> with both our assembly and a jar. How can we prevent the jar from
> being created?
>
> Thanks, and sorry if this is a silly question.

what about using pom  ?

J

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

Re: How to avoid creating a jar?

[nicolas de loof]

The maven-way is to create a maven extension with a custom packaging and
lifecycle, similar to jar one, but without packaging as a .jar.
For example, take a look at
https://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/javascript-maven-extensions
that
creates a "javascript" packaging.

This is not very complex, but also not so trivial, so maybe the pragmatic
solution is to ignore the jar that maven builds if you get what you want in
the assembly !

Nico.


2008/1/18, Joshua ChaitinPollak <[EMAIL PROTECTED]>:
>
> Hello,
>
> we have a few projects we are building with Maven which do not result
> in jar's being the final output. For those projects we are using the
> maven-assembly-plugin, but when we run 'mvn package' we still end up
> with both our assembly and a jar. How can we prevent the jar from
> being created?
>
> Thanks, and sorry if this is a silly question.
>
> -Josh
>
> --
> Joshua ChaitinPollak | Software Engineer
> Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Producing 2 JAR's with exclusive content

[Richard Gal]

Hello

Could somebody help me with the following problem:

I have a project that uses some native libraries (dll's). I would like 
to create 2 JAR artifacts out of this project

- one with the Java classes of the project and
- another with nothing else but the native libraries.

What is the appropriate way to achieve this?

I tried to play with the maven-jar-plugin configuration and did the 
following:

1.
I defined an execution for the maven-jar-plugin that includes the native 
libraries:


org.apache.maven.plugins
maven-jar-plugin
2.2


native
package

jar


nativelibs

${basedir}/native/*.dll





The result is that the created -nativelibs.jar does not have the DLL's.

2.
Then I tried to specify that the native libraries are resources to be 
copied under target/classes:



  

  ${basedir}/native
  
**/*
  

  
  

  org.apache.maven.plugins
  maven-jar-plugin
  2.2
  

  native
  package
  
jar
  
  
nativelibs

  **/*.dll

  

  

  


This time the native libraries are in the -nativelibs.jar but the 
problem is that they are also packaged into the default artifact (.jar)


3.
If I exclude the native libraries from the default execution then I 
cannot include them anymore in another execution.


Thanks for any help.
Richie



signature.asc
Description: OpenPGP digital signature

How to avoid creating a jar?

[Joshua ChaitinPollak]

Hello,

we have a few projects we are building with Maven which do not result  
in jar's being the final output. For those projects we are using the  
maven-assembly-plugin, but when we run 'mvn package' we still end up  
with both our assembly and a jar. How can we prevent the jar from  
being created?


Thanks, and sorry if this is a silly question.

-Josh

--
Joshua ChaitinPollak | Software Engineer
Kiva Systems, Inc., 225 Wildwood Ave, Woburn, MA 01970





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

Configure maven-jetty-plugin logging

[Michael Osipov]

Hi,

I have some serious logging configuration problems with Maven, slf4j and
Jetty.

The jetty plugin was configured this way 
http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#Logging but 
all I see are the log outputs from jetty, none from my webapp made with 
slf4j :-(


Did I something wrong? Is there any approach?

Thx
--
 OOXML - Say NO To Microsoft Office broken standard
http://www.noooxml.org



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

release:prepare no javadoc generation

[Vytautas Čivilis]

Hi.

When using release:prepare plugin, it parses javadocs and generates 
javadoc html files. Is it possible to turn that off?


Thanks!
vyc

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

Re: release:prepare no javadoc generation

[Tom Huybrechts]

Turn of the release profile. If you still want sources, you'll have to add
them yourself.

http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile

On Jan 20, 2008 10:56 AM, Vytautas Čivilis <[EMAIL PROTECTED]> wrote:

> Hi.
>
> When using release:prepare plugin, it parses javadocs and generates
> java

doc html files. Is it possible to turn that off?
>
> Thanks!
> vyc
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

release:prepare no javadoc generation

[Vytautas Čivilis]

Hi.

When using release:prepare plugin, it parses javadocs and generates
javadoc html files. Is it possible to turn that off?

Thanks!
vyc


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

Re: Avoid Dependency version

[Michael Meyer]

amit kumar schrieb:

Hi,
The reason for I thinking about not having version component in the
 tag might result in a better version control in terms of
same version being used across the different modules of the project.
Though not very sure if I am genuine enough when I think that.
As Brian said you can use the dependencyManagment section for this. You 
define the version in the toplevel pom and all sub poms inherit the 
version. I would also lock down the versions of the plugins in the 
pluginManagement section (just my two cents).



And as Wayne pointed
out , is it a good thing to think about?
Wayne is right, don't do it! Your build will not be reproducable. If you 
build your project today, version 1.1.1 (?) of commons-logging will be 
used. If you checkout the same code in one year there will be a newer 
version of commons-logging and if they have changed interfaces in the 
meantime it is possible that your code will not even compile.


michael

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

Re: Avoid Dependency version

[amit kumar]

Hi,
The reason for I thinking about not having version component in the
 tag might result in a better version control in terms of
same version being used across the different modules of the project.
Though not very sure if I am genuine enough when I think that.

Actually when I want to avoid dependency versions, I want to do it in
context of an individual project(irrespective of chil-parent
relationship).My question was that for instance if I am using
commons-logging in my dependency

...
commons-logging
commons-logging
1.0.4


Is there a way around to avoid the version component so that the
latest version gets fetched from the repository? And as Wayne pointed
out , is it a good thing to think about?

Regards,
Amit

On Jan 19, 2008 10:44 PM, Wayne Fay <[EMAIL PROTECTED]> wrote:
> I almost replied with this same content but decided against it.
>
> Amit, you realize that you are heading down a very ugly path if you
> use any of these options, and you will get builds that are all but
> impossible to reproduce etc, right?
>
> Wayne
>
>
>
>
> On 1/19/08, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > You can use dependencyManagment in a parent pom to avoid specifying the
> > version in all your child poms. If you really want the "latest" you have
> > two choices:
> > LATEST - latest snapshot
> > RELEASE - latest release
> >
> > Or you could specify a range like [0,)
> >
> > -Original Message-
> > From: amit kumar [mailto:[EMAIL PROTECTED]
> > Sent: Friday, January 18, 2008 8:38 AM
> > To: Maven Users List
> > Subject: Avoid Dependency version
> >
> > Hi,
> > Can I make it possible for my dependencies(jar files) declared in
> >  tags, not have version. Just like in case of plugin it
> > happens,
> > the latest on gets fetched?
> > When I don't put a version in my dependency tag, it throws error.
> >
> > Regards,
> > Amit
> >
> > -
> > 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]
>
>

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