Re: Best practices for java version?

[Stuart McCulloch]

On 29/03/2008, Richard Chamberlain <[EMAIL PROTECTED]> wrote:
>
> If you using java 5 as your JAVA_HOME I would also recommend setting the
> executable compiler to use.
>
> path.to.jdk\1.4.2\bin\javac.exe
>
> Whilst  and  go some way to making sure the language is
> correct, they won't pick up the fact that java 1.4 doesn't have a
> certain version of a runtime library.
>
> For example you could have happily used  and  to compile
> an class that does some XML parsing using java 5 libraries. However when
> you run the code in a 1.4 environment it'll blow up.


you could always set the compiler bootclasspath, as mentioned here:

   http://docs.codehaus.org/x/9fE

so no matter what JDK you use, it will compile against the right classlib:

  
1.3
1.3

  ${some.property}/path/to/some/rt.jar

  

then it's just a matter of getting the relevant rt.jar and either putting it
in
a repository, or providing it as part of your project / developer setup.

HTH

Regards,
>
> Rich
>
>
>
> -Original Message-
> From: Graham Leggett [mailto:[EMAIL PROTECTED]
> Sent: 28 March 2008 19:29
> To: Maven Users List
> Subject: Re: Best practices for java version?
>
> david delbecq wrote:
>
> > What are the best practice when deploying artifact about java version
> > used for compiling? I read somewhere that the purpose of maven release
>
> > process is to make the build "reproductible", but if that build does
> not
> > include aimed compiler, we can't assure a "rebuild" will be fully
> > compatible with previous build, if the java version changed...
>
> Configure the maven-compiler-plugin to specify the specific java version
>
> you need for that particular build. This will ensure your future rebuild
>
> is repeatable, even with a newer JDK version.
>
> Regards,
> Graham
> --
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Cheers, Stuart

Re: Best practices for java version?

[Wendy Smoak]

On Fri, Mar 28, 2008 at 3:50 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Richard Chamberlain wrote:
>
>  > If you using java 5 as your JAVA_HOME I would also recommend setting the
>  > executable compiler to use.
>  >
>  >   path.to.jdk\1.4.2\bin\javac.exe
>
>  The side effect of this is that you produce code that now only compiles
>  on one person's machine, and that is *very* un-repeatable.

You can use a property like ${JAVA_1_4_HOME} as suggested in the
compiler plugin docs.

It's more configuration (devs may have to set that property in
settings.xml) but if you need to compile with a certain JDK, you can d
 This assumes you have control of the release environment, as
you'd want to make sure the property was _really_ set to the location
of a 1.4 JDK.

http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html

-- 
Wendy

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

RE: Best practices for java version?

[Richard Chamberlain]

I agree it's not ideal, but I'm open to suggestions as to how to
guarantee code from a particular project works in a java 1.4
environment?

-Original Message-
From: Graham Leggett [mailto:[EMAIL PROTECTED] 
Sent: 29 March 2008 00:25
To: Maven Users List
Subject: Re: Best practices for java version?

Richard Chamberlain wrote:

> It works internally at our company as we all have build tools (jdk
etc)
> in a standard place. This makes it repeatable and 
> guaranteed not to blow up on a 1.4 environment.

There is no such thing as a "standard" place for build tools - a new 
contractor comes in, and suddenly has to rearrange their laptop to 
accommodate some weird directory structure that is different to their 
existing setup. That's a significant waste of time and money.

Then you decide to upgrade from Win2k to XP, and from XP to Vista, and 
Vista to whatever, and suddenly the default location of the JDK changes 
for whatever reason and all your code breaks.

Hard coding paths is one of the exact things that was rife in ant builds

and that maven moves away from, and that makes code management 
significantly less painful and more robust.

Regards,
Graham
--

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

Re: [m2] issue running selenium with Tomcat 5 with Cargo plugin.

[Mick Knutson]

Ok, I figured out that the context was being set to my 'artifactId-version/'
and when I altered my URL, it worked.
So how do I set the root context via Tomcat and Cargo?


On Fri, Mar 28, 2008 at 7:53 AM, Mick Knutson <[EMAIL PROTECTED]> wrote:

> Ok, I am trying to run Selenium tests on my web app.
> Now when I use this jetty plugin and start my webapp via jetty, I can see
> my app running fine and my index.html (jsf) page displays fine:
>
> *
> org.mortbay.jetty
> maven-jetty-plugin
> 6.1.6
> 
> /
> 3
> 
> 
> src/main/webapp/WEB-INF
>   
> 
> **/*.jsp
> **/*.xhtml
> 
> 
> **/*.properties
> **/*.xml
> 
> 
> 
> 
> 
> *
> *This is just a small bit of the html source from jetty running manually
> or through Selenium IDE:
> http://localhost:8080/index.html
> *
>
> 
>  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"; >
>
> http://www.w3.org/1999/xhtml";>
> 
>
> 
>
> Main Index
> 
>
>  />
>
> 
>
> 
>
> 
> 
>
>
>
> *Now, when I run mvn install to deploy to the following tomcat5 server,
> all my tests show no html thus it appears that under tomcat5 via cargo, the
> pages are not there or they are blank:*
> *
> org.codehaus.cargo
> cargo-maven2-plugin
> 0.3.1
> 
> ${cargo.wait}
> 
> ${cargo.container
> }
> 
> ${cargo.container.url}
> ${installDir}
> 
> 
> 
> ${project.build.directory}/${
> cargo.container}/container
> 
> ${cargo.host
> }
> ${cargo.port
> }
> 
> 
> 
> 
> 
> start-container
> pre-integration-test
> 
> start
> 
> 
> 
> stop-container
> post-integration-test
> 
> stop
> 
> 
> 
> 
> ...
> **tomcat5x*
> **
> *
> http://archive.apache.org/dist/tomcat/tomcat-5/v5.5.26/bin/apache-tomcat-5.5.26.zip
> *
> **
> ***localhost*
> *8080*
> *false*
> *
> *
> *Here is the selenium test:*
>
> *selenium.open("/index.html");
> log.debug
> ("=");
> log.debug("selenium.getTitle(): " + selenium.getTitle());
> log.debug("selenium.getLocation(): " + selenium.getLocation());
> log.debug
> ("=");
> log.debug("selenium.getHtmlSource(): " + selenium.getHtmlSource
> ());
> log.debug
> ("=");
> //Assert.assertEquals(selenium.getTitle(), "Main Index", "'title'
> should equal \"Main Index\"");
>
>
> selenium.open(applicationAddress + "index.html");
> log.debug
> ("=");
> log.debug("selenium.getTitle(): " + selenium.getTitle());
> log.debug("selenium.getLocation(): " + selenium.getLocation());
> log.debug
> ("=");
> log.debug("selenium.getHtmlSource(): " + selenium.getHtmlSource
> ());
> log.debug
> ("=");
> //Assert.assertEquals(selenium.getTitle(), "Main Index", "'title'
> should equal \"Main Index\"");
>
> *
>
> *Here is the selenium stack trace I get.*
>
> *[myproject] INFO [main] LoginTest.init(34) | Starting Selenium client
> [myproject] DEBUG [main] LoginTest.testSuccessfulLogin(62) |
> =
> [myproject] DEBUG [main] Log

Re: Best practices for java version?

[Wayne Fay]

And in response to Martin, in the project I'm recently involved in,
the paths are not hard-coded into the build script itself but rather
in various build.properties files. It is still a total pain and a
hack, IMO. You can't honestly tell me that you enjoy configuring
properties files for every environment/machine, do you? I have better
things to do with my time.

After a lot of time with Maven over the last few years, it will be a
cold day in hell when I go back to making Ant scripts. Instead, I'm
fixing the mistakes of others and getting rid of their Ant scripts.

Wayne

On 3/28/08, Wayne Fay <[EMAIL PROTECTED]> wrote:
> On 3/28/08, Graham Leggett <[EMAIL PROTECTED]> wrote:
> > Hard coding paths is one of the exact things that was rife in ant builds
> > and that maven moves away from, and that makes code management
> > significantly less painful and more robust.
>
> I just got pulled into a project at my work place where they are
> having significant build problems, and guess what, its Ant-city with
> hard-coded paths like you wouldn't believe. For some reason, this
> approach is starting to have problems now that more than 2 devs are
> involved, and the project is getting ready to hit production for the
> first time.
>
> Wayne
>

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

Re: Best practices for java version?

[Wayne Fay]

On 3/28/08, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Hard coding paths is one of the exact things that was rife in ant builds
> and that maven moves away from, and that makes code management
> significantly less painful and more robust.

I just got pulled into a project at my work place where they are
having significant build problems, and guess what, its Ant-city with
hard-coded paths like you wouldn't believe. For some reason, this
approach is starting to have problems now that more than 2 devs are
involved, and the project is getting ready to hit production for the
first time.

Wayne

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

RE: Best practices for java version?

[Martin Gainty]

Richard and Graham
I've been using ANT since 02 placing all environmental (path/classpath) 
information into buildName.propertiesAnyone who is hardcoding paths in Ant 
is'nt using it to its full capability and is negating the original design intent
please reference Use Property Files from Steve Loughran's Ant in Anger paper at
http://ant.apache.org/ant_in_anger.htmlThanks,Martin__Disclaimer
 and confidentiality noteEverything in this e-mail and any attachments relates 
to the official business of Sender. This transmission is of a confidential 
nature and Sender does not endorse distribution to any party other than 
intended recipient. Sender does not necessarily endorse content contained 
within this transmission.> From: [EMAIL PROTECTED]> To: users@maven.apache.org> 
Subject: Re: Best practices for java version?> > Richard Chamberlain wrote:> > 
> It works internally at our company as we all have build tools (jdk etc)> > in 
a standard place. This makes it repeatable and > > guaranteed not to blow up on 
a 1.4 environment.> > There is no such thing as a "standard" place for build 
tools - a new > contractor comes in, and suddenly has to rearrange their laptop 
to > accommodate some weird directory structure that is different to their > 
existing setup. That's a significant waste of time and money.> > Then you 
decide to upgrade from Win2k to XP, and from XP to Vista, and > Vista to 
whatever, and suddenly the default location of the JDK changes > for whatever 
reason and all your code breaks.> > Hard coding paths is one of the exact 
things that was rife in ant builds > and that maven moves away from, and that 
makes code management > significantly less painful and more robust.> > 
Regards,> Graham> --
_
How well do you know your celebrity gossip?
http://originals.msn.com/thebigdebate?ocid=T002MSN03N0707A

Re: Best practices for java version?

[Graham Leggett]

Richard Chamberlain wrote:


It works internally at our company as we all have build tools (jdk etc)
in a standard place. This makes it repeatable and 
guaranteed not to blow up on a 1.4 environment.


There is no such thing as a "standard" place for build tools - a new 
contractor comes in, and suddenly has to rearrange their laptop to 
accommodate some weird directory structure that is different to their 
existing setup. That's a significant waste of time and money.


Then you decide to upgrade from Win2k to XP, and from XP to Vista, and 
Vista to whatever, and suddenly the default location of the JDK changes 
for whatever reason and all your code breaks.


Hard coding paths is one of the exact things that was rife in ant builds 
and that maven moves away from, and that makes code management 
significantly less painful and more robust.


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

Re: Best practices for java version?

[david delbecq]

Graham Leggett a écrit :

david delbecq wrote:

What are the best practice when deploying artifact about java version 
used for compiling? I read somewhere that the purpose of maven 
release process is to make the build "reproductible", but if that 
build does not include aimed compiler, we can't assure a "rebuild" 
will be fully compatible with previous build, if the java version 
changed...


Configure the maven-compiler-plugin to specify the specific java 
version you need for that particular build. This will ensure your 
future rebuild is repeatable, even with a newer JDK version.


Regards,
Graham
--


Thank you all for all solutions, but my concern is very particular about 
"dependencies", when i pickup dependencies on maven repository, how do i 
know about it's transititive dependencies java requirement, there 
doesn't seems to be anything about it in the pom.xml. So when i pickup, 
for example, richfaces, i have absolutely no way to know


1) does it requires a java 1.4, java 5 or java 6 runtime
2) do it's transitive dependency depends on java 1.4, java 5 or java 6
3) in the end, will it run on my java 1.4 server?

It's very frustrating to work 2 weeks porting from maven1 to maven2 and 
in the end discover the transitive dependecies brings up java 5 
requirement our production server can't cope with :)


Now that mean i either

1) upgrade server (seems resonnable) to java 5
2) go to each classload exception, one at a time, to pickup a wrong java 
requirement library, rebuild it on java 1.4 and the publish it in 
internal repo, hoping it won't collide with the "official" builded file. 
It's a very long process, since the exceptions doe not occur at init 
time, but in middle of day work.


Even if i do 1) i have no garantee that none of the jar are build on 
java 6, which would be a problem since our prod environnement has, 
afaik, absolutely no java 6 jvm available.





Considering Those point, a sideway question too, could it be possible to 
ask maven to recompile very dependencies when building a project? Since 
sources are published along jar and scm informations is present in 
pom.xml, it should be faisible, no?


And another one, could this (information about jvm or even "java 
version", be added to jar? using the extension mecanism, in future maven 
version?)


Regards,
David Delbecq



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

RE: Best practices for java version?

[Richard Chamberlain]

It works internally at our company as we all have build tools (jdk etc)
in a standard place. This makes it repeatable and 
guaranteed not to blow up on a 1.4 environment.

I agree that this could certainly be a problem. Maybe there's a nicer
solution with profiles etc?

Regards,

Richard

-Original Message-
From: Graham Leggett [mailto:[EMAIL PROTECTED] 
Sent: 28 March 2008 22:50
To: Maven Users List
Subject: Re: Best practices for java version?

Richard Chamberlain wrote:

> If you using java 5 as your JAVA_HOME I would also recommend setting
the
> executable compiler to use.
> 
>   path.to.jdk\1.4.2\bin\javac.exe

The side effect of this is that you produce code that now only compiles 
on one person's machine, and that is *very* un-repeatable.

Regards,
Graham
--

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

Re: Best practices for java version?

[Graham Leggett]

Richard Chamberlain wrote:


If you using java 5 as your JAVA_HOME I would also recommend setting the
executable compiler to use.

path.to.jdk\1.4.2\bin\javac.exe


The side effect of this is that you produce code that now only compiles 
on one person's machine, and that is *very* un-repeatable.


Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature

RE: Best practices for java version?

[Richard Chamberlain]

If you using java 5 as your JAVA_HOME I would also recommend setting the
executable compiler to use.

path.to.jdk\1.4.2\bin\javac.exe

Whilst  and  go some way to making sure the language is
correct, they won't pick up the fact that java 1.4 doesn't have a
certain version of a runtime library.

For example you could have happily used  and  to compile
an class that does some XML parsing using java 5 libraries. However when
you run the code in a 1.4 environment it'll blow up.

Regards,

Rich


-Original Message-
From: Graham Leggett [mailto:[EMAIL PROTECTED] 
Sent: 28 March 2008 19:29
To: Maven Users List
Subject: Re: Best practices for java version?

david delbecq wrote:

> What are the best practice when deploying artifact about java version 
> used for compiling? I read somewhere that the purpose of maven release

> process is to make the build "reproductible", but if that build does
not 
> include aimed compiler, we can't assure a "rebuild" will be fully 
> compatible with previous build, if the java version changed...

Configure the maven-compiler-plugin to specify the specific java version

you need for that particular build. This will ensure your future rebuild

is repeatable, even with a newer JDK version.

Regards,
Graham
--



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

Fw: Query on using maven-assembly-plugin.

[logachandru . x . rajamanickam]

Hello,

Please let me know your ideas on resolving this issue.


Thanks & Regards,
Logu Rajamanickam


- Forwarded by Logachandru X Rajamanickam/JPMCHASE on 03/28/2008 04:02 
PM -

[EMAIL PROTECTED] 
03/28/2008 11:26 AM
Please respond to
"Maven Users List" 


To
"Maven Users List" 
cc

Subject
Query on using maven-assembly-plugin.






Hi,

I'm using maven-assembly-plugin in my POM and the assembly descriptor as 
below to generate a JAR package. The resultant artifact package is in the 
form of artifact-1.0-DEV.jar. But I require the package in the form of 
artifact-DEV-1.0.jar. What I need here is the assemblyId should get 
appended to the POM's artifactId before the version. Can anyone please 
advise how this can be done.

//POM with assembly plugin


maven-assembly-plugin

  
ASSEMBLY-DEV
   compile
   
attached
   
   

${basedir}/sql-DEV.xml

${pom.artifactId}
${basedir}/target/dev
   
 



//Assembly Descriptor - sql-DEV.xml


DEV

jar



 ${basedir}/../../../../Database/tables

 
*.sql
   


 


Thanks & Regards,
Logu Rajamanickam

-
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

basepath . rescanned for compiler:testCompile

[Steve Suehs]

We are running into an issue with one of our child projects.
The compiler:testCompile builds the tests we expect, but wait! then it 
does more: it starts looking in "." for more tests to compile, 
revisiting files it has already built via  a different path.
The compile fails with both a duplicate class error and a bad class file 
error since


   ./test/my/package/MyClass.java
conflicts with
   my.package.MyClass
and does not contain
   test.my.package.MyClass
but instead contains
   my.package.MyClass

I've got debug and verbose turned on for the compiler plugin and for 
maven and I can see that "." is the last entry in the search path for 
source files, after a large number of

   /home/me/.m2/repository/dependencies/xxx-tests.jar, etc,
we see
  .]]
in the test source path

This is not explicitly specified in the pom or the parent pom.

Why! Where is it coming from?  What further paths of investigation are 
recommended before debugging the compiler plugin!?


-s




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

Re: file system repo not work

[Alessandro Ferrucci]

I am using m2eclipse.

thanks

alessandro ferrucci

Brian E. Fox wrote:

Which eclipse plugin are you using? Maven-eclipse-plugin, m2eclipse or
q4e?

-Original Message-
From: Alessandro Ferrucci [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 28, 2008 11:29 AM

To: users@maven.apache.org
Subject: file system repo not work

Hello,

I have the relevant pom snippet below.  The problem is really with the 
eclipse plugin.  The plugin reports not being able to download the 2 
dependencies entity-client-1.0 and newsml-2.0.0.jar which are in my 
sandbox in the following location:


/home/ferucci/europa_workspace/photos/

This used to work on my macbook (which died last week :) ), but on my 
linux box it does not.


Eclipse complains of now being able to download the 2 given 
dependencies, but when I build with maven, it builds just fine and the 
jar gets downloaded in my local repo (from my sandbox). 

what could be wrong with eclipse? what are some debugging tricks I can 
try out with the maven eclipse plugin?


thanks

alessandro ferrucci




http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

4.0.0
com.aol.pubt.photos.common
Photos
photos
0.0.1
DPIS



true
src/main/resources/

**/myconfig-ingestor.properties
**/log4j.properties
**/telescope.xsd
**/newsML.dtd
**/xsl/*.xsl



true
etc/

**/*



true
release/

**/*





maven-compiler-plugin

1.5
1.5
true
true






local sandbox repo
DPIS Commons Sandbox repo
file://${basedir}/release/lib




org.apache
newsml
2.0


com.aol.cm.entity
entity-client
1.0






-
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]

RE: file system repo not work

[Brian E. Fox]

Which eclipse plugin are you using? Maven-eclipse-plugin, m2eclipse or
q4e?

-Original Message-
From: Alessandro Ferrucci [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 28, 2008 11:29 AM
To: users@maven.apache.org
Subject: file system repo not work

Hello,

I have the relevant pom snippet below.  The problem is really with the 
eclipse plugin.  The plugin reports not being able to download the 2 
dependencies entity-client-1.0 and newsml-2.0.0.jar which are in my 
sandbox in the following location:

/home/ferucci/europa_workspace/photos/

This used to work on my macbook (which died last week :) ), but on my 
linux box it does not.

Eclipse complains of now being able to download the 2 given 
dependencies, but when I build with maven, it builds just fine and the 
jar gets downloaded in my local repo (from my sandbox). 

what could be wrong with eclipse? what are some debugging tricks I can 
try out with the maven eclipse plugin?

thanks

alessandro ferrucci




http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.aol.pubt.photos.common
Photos
photos
0.0.1
DPIS



true
src/main/resources/

**/myconfig-ingestor.properties
**/log4j.properties
**/telescope.xsd
**/newsML.dtd
**/xsl/*.xsl



true
etc/

**/*



true
release/

**/*





maven-compiler-plugin

1.5
1.5
true
true






local sandbox repo
DPIS Commons Sandbox repo
file://${basedir}/release/lib




org.apache
newsml
2.0


com.aol.cm.entity
entity-client
1.0






-
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: Multi-module archetypes

[Raphaël Piéroni]

Hi John,

This feature is provided by the 2.0-alpha-3 version
of the Archetype plugin. This version is not yet released.
But you can try the last snapshot by adding a repository
to apache snapshot [1].

1. The goal to call from the project directory (or parent in
case of a multi module) is 'mvn archetype:create-from-project'.
2. Then go to the target/generated-sources/archetype directory
and see if the generated archetype is correct.
install the archetype in your local repository by calling
'mvn install' as usual.
3. Then go to a fresh directory and call
'mvn archetype:generate -DarchetypeCatalog=local'.

Step 3 may don't work because repositories defined
in profiles in the settings.xml file are recognised only
when maven is called in a project's directory. One may
try to use the apache's snapshot repository as mirror of
central (not tested).

Another workaround i see is compiling the plugin from the
sources.

Please share your experience of using the plugin afterward.

Thanks,

Raphaël

[1]: in settings.xml :

apache-snapshots


apache-snapshot
Apache Snapshots

false
never
warn


always
warn


http://people.apache.org/maven-snapshot-repository/
default




apache-snapshot
Apache Snapshots

false
never
warn


always
warn


http://people.apache.org/maven-snapshot-repository/
default





2008/3/28, Prystash,John <[EMAIL PROTECTED]>:
>
>  I'm stepping into my first foray into creating archeyptes.  In general,
>  is there support for creating an archetype for a multi-module project?
>  Or is better to build a project with multiple archetypes?  My first
>  thought would be I'd have problem injecting the parent project name into
>  the directory structure?
>
> MyService
> MyService-core
> MyService-container
>
>  Thanks
>

Re: Best practices for java version?

[Graham Leggett]

david delbecq wrote:

What are the best practice when deploying artifact about java version 
used for compiling? I read somewhere that the purpose of maven release 
process is to make the build "reproductible", but if that build does not 
include aimed compiler, we can't assure a "rebuild" will be fully 
compatible with previous build, if the java version changed...


Configure the maven-compiler-plugin to specify the specific java version 
you need for that particular build. This will ensure your future rebuild 
is repeatable, even with a newer JDK version.


Regards,
Graham
--




smime.p7s
Description: S/MIME Cryptographic Signature

Re: "Cannot execute mojo: eclipse."

[Wayne Fay]

On 3/28/08, Attila Szegedi <[EMAIL PROTECTED]> wrote:
>
> Again, the conclusion I reached based on the observed symptoms was
> that this is a Maven issue. Actually, it *is* a Maven issue; why would
> Maven2 be allowed to break in such an ugly manner when facing a Maven1-
> compliant project? Some sort of version mismatch detection and a clean
> fail-fast behavior with an explanatory error message would be in
> order, methinks... Would certainly reduce the kind of mailing list
> traffic that you'd like to avoid :-)

Maven expects that users realize this is a M2 (or M1) project they are
dealing with, and that they are using the proper M2/M1 binaries etc.
Perhaps that is a poor assumption.

Feel free to file this in JIRA, perhaps someone will add code to
support the "when mvn runs, if pom.xml not there but project.xml is,
warn user they probably should be using Maven1 binaries instead" use
case you're proposing.

Wayne

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

Re: Best practices for java version?

[Wim Deblauwe]

You can use the Maven Enforcer plugin (
http://maven.apache.org/plugins/maven-enforcer-plugin/ ) to force a specifc
JDK for the modules you are building yourself. But I don't think there is
anything for your dependencies that you can specify.

regards,

Wim

2008/3/28, david delbecq <[EMAIL PROTECTED]>:
>
> Hello,
>
> using maven2, i notice that, while there are options to specify which
> java version to use when compiling, there is little information on
> released jars in repo about which version there are compiled for. It's a
> problem in an environment where the java version has limitation. For
> example, we are working now on a tomcat using java 1.4. After upgrading
> to maven and making a test deploy, we noticed that some of the
> transitive dependencies are build with java 1.5. But nothing on project
> makes it visible until you deploy and requires one of those jars.
>
> So question is, are there any recommendations on how to handle java
> version in releases and in dependencies. If, in the build, i set the
> "target" and "source" in compiler, will the compiler check that
> dependencies respect those target (so in my case, if i point to 1.4, it
> will build error because some transitive dep are java 5?)
>
> What are the best practice when deploying artifact about java version
> used for compiling? I read somewhere that the purpose of maven release
> process is to make the build "reproductible", but if that build does not
> include aimed compiler, we can't assure a "rebuild" will be fully
> compatible with previous build, if the java version changed...
>
> Thanks for giving information :)
>
> Regards,
> David Delbecq
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Best practices for java version?

[david delbecq]

Hello,

using maven2, i notice that, while there are options to specify which 
java version to use when compiling, there is little information on 
released jars in repo about which version there are compiled for. It's a 
problem in an environment where the java version has limitation. For 
example, we are working now on a tomcat using java 1.4. After upgrading 
to maven and making a test deploy, we noticed that some of the 
transitive dependencies are build with java 1.5. But nothing on project 
makes it visible until you deploy and requires one of those jars.


So question is, are there any recommendations on how to handle java 
version in releases and in dependencies. If, in the build, i set the 
"target" and "source" in compiler, will the compiler check that 
dependencies respect those target (so in my case, if i point to 1.4, it 
will build error because some transitive dep are java 5?)


What are the best practice when deploying artifact about java version 
used for compiling? I read somewhere that the purpose of maven release 
process is to make the build "reproductible", but if that build does not 
include aimed compiler, we can't assure a "rebuild" will be fully 
compatible with previous build, if the java version changed...


Thanks for giving information :)

Regards,
David Delbecq

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

Re: "Cannot execute mojo: eclipse."

[Attila Szegedi]

On 2008.03.28., at 15:35, Wayne Fay wrote:

In the future, you might just go right to the source and ask the
originating team responsible for the code why it doesn't compile. So
in this case, ask Atlassian directly.


Not being able to run "mvn eclipse:eclipse" (and several other fairly  
straightforward mvn tasks) seemed generic enough to me that I assumed  
it is a problem with my Maven setup and not in the project I tried to  
work with.
The Maven's error message was less than helpful in explaining what's  
going on, and digging the web with Google for the error message also  
didn't yield satisfactory results.





(IMO the Maven users list cannot possibly hope to support every single
developer who stumbles across an open-source project that uses Maven
as their build tool and then has a problem building the code. So most
questions like these should be sent to the responsible development
team first, then if they can't help you can forrward it here. You may
be doing them a favor by notifying them of a problem they didn't even
know they had! )


I agree - I often end up saying the same to Struts 2 users when  
they're seeking help on the FreeMarker list :-)


Again, the conclusion I reached based on the observed symptoms was  
that this is a Maven issue. Actually, it *is* a Maven issue; why would  
Maven2 be allowed to break in such an ugly manner when facing a Maven1- 
compliant project? Some sort of version mismatch detection and a clean  
fail-fast behavior with an explanatory error message would be in  
order, methinks... Would certainly reduce the kind of mailing list  
traffic that you'd like to avoid :-)


Thanks to Nick for help,
  Attila.

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

resource plugin - does it require a profile?

[Dooing]

Hi,

I found out that the resource plugin is capable of simply copying files to a 
directory. I would like to use this to update files in my tomcat webapps 
project folder (when necessary). However, I am already using the plugin to copy 
resources to the war file that is generated in the regular build phases (1):

   
 
${basedir}/src/configuration

  *.xml

...
  


I tried to additionally add (2):

  maven-resources-plugin
   
${MY_OUTPUT_DIR}

  
   ${MYRESOURCES_DIRECTORY}
  
**/*.jsp 
**/*.js  
**/*.css
 ...
   
 
 
 


However, this (2) didn't work out - Maven still used the settings I had 
specified under build.

Finally I found a temporary solution, using profiles:
...

myspecialfunc


 
  ${MYRESOURCES_DIRECTORY}
  
 **/*.jsp

 **/*.js 
 **/*.css
  ...
   
 
   


...

Then, when calling: 

mvn resources:resources -P myspecialfunc

it works as desired. However I don't really like it that way, as the other 
developers would have to remember this kinda complicated call.
Isn't there an easier way to get this done?

Thanks in advance,

Stefanie
-- 
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED]

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

Re: apt-get repository

[Jason van Zyl]

Yes, both of these IDE integrations support the Nexus indexer which  
allows you access to all dependency information in the central  
repository.


On 28-Mar-08, at 3:15 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>  
wrote:
Maybe you can use Eclipse (m2eclipse [1]) or Netbeans(mevenide [2])  
with their maven plugin. Those plugins index the central repository  
and allow you to search and add dependencies.


[1] http://m2eclipse.codehaus.org
[2] http://mevenide.codehaus.org

Hth,

Nick S.


-Original Message-
From: neo anderson [mailto:[EMAIL PROTECTED]
Sent: Fri 3/28/2008 10:58
To: users@maven.apache.org
Subject: apt-get repository


I have one question. Does any maven command or plugin support serach  
and add
dependency automatically (a bit like Debian apt-get)? For instance,  
I use

archetype to create an ejb project. Then I want to use jboss as my ejb
container. So I need to add a lot of dependencies. Is there any  
command or

plugin like 'mvn dependency:search-jboss'/ 'mvn dependency:add-jboss'
enabling mvn to automatically accomplish the dependencies section?  
Though
those dependencies can be added manually by editing the pom.xml, it  
is a bit
tedious step and easily to mistype the wrong characters. Or is there  
any

better way to accomplish such task?

Thank you very much,
--
View this message in context: 
http://www.nabble.com/apt-get-repository-tp16348997s177p16348997.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]




Thanks,

Jason

--
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
--

We all have problems. How we deal with them is a measure of our worth.

-- Unknown 





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

Re: Mvn 2 plugin to copy files?

[Dooing]

>I use the antrun plugin for copying files around and such. You just put in
>the ant equivalent to your xml, which shouldn't be much different from what
>you have.

Could you give an example of how this is done? I don't know much about antrun 
and how to use it...

Thanks in advance,

Stefanie
-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

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

Error deploying artifact (Is a directory)

[David Delbecq]

Hello,

i try to deploy a .war to our release repository, but mvn deploy fails 
with this message:



[INFO] [install:install]
[INFO] No primary artifact to install, installing attached artifacts 
instead.
[INFO] Installing 
/home/delbd/dev/workspaces/intranet/RMI_intranet/target/intranet-1.0-SNAPSHOT-production.war 
to 
/home/delbd/.m2/repository/be/meteo/intranet/1.0-SNAPSHOT/intranet-1.0-SNAPSHOT-production.war

[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from restricted
[INFO] 


[ERROR] BUILD ERROR
[INFO] 

[INFO] Error deploying artifact: 
/home/delbd/dev/workspaces/intranet/RMI_intranet/target/classes (Is a 
directory)
Why does it try to deploy my target/classes folder? I saw no option in 
maven deploy plugin documentation about how to specify which archetype 
to upload.


The only particularities that may have influence on process are below. 
Any suggestion on what's wrong?


Thanks

  
maven-war-plugin

  ${webapp.classifier}  
  webapp

  

  
  configSets/${config.configSet}


  
  
${project.build.directory}/mergedFiles


  

  

production

  
type
production
  
  
  

production
production
  



--
David Delbecq
Institut Royal Météorologique
Ext:557


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

Re: Mvn 2 plugin to copy files?

[Lee Meador]

I use the antrun plugin for copying files around and such. You just put in
the ant equivalent to your xml, which shouldn't be much different from what
you have.

-- Lee

On Fri, Mar 28, 2008 at 10:58 AM, <[EMAIL PROTECTED]> wrote:

> Hi,
>
> While tomcat is running, I would like to move some files from my source
> folder to my tomcat/webapps/myproject folder - in case I altered these files
> - by calling some plugin and or goal.
>
> Using Maven 1, we had a custom goal for this:
>
>  
>
>  
>
>
>
>  
>   
>
>
>   
>   
>  
>
>  
>
> Now when using Maven 2, I've read custom goals using jelly are not
> supported by Maven 2 - one should create a custom plugin instead. Is this
> really necessary in this case? I guess there must be some plugin doing just
> the same job without having to develop a custom plugin. I tried mvn
> resources:resources, but this didn't work.
>
> Any ideas? I am helpless!!! :-(((
>
> Thanks in advance - your help's greatly appreciated!!!
>
> Stefanie
> --
> Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

Query on using maven-assembly-plugin.

[logachandru . x . rajamanickam]

Hi,

I'm using maven-assembly-plugin in my POM and the assembly descriptor as 
below to generate a JAR package. The resultant artifact package is in the 
form of artifact-1.0-DEV.jar. But I require the package in the form of 
artifact-DEV-1.0.jar. What I need here is the assemblyId should get 
appended to the POM's artifactId before the version. Can anyone please 
advise how this can be done.

//POM with assembly plugin


maven-assembly-plugin

  
ASSEMBLY-DEV
   compile
   
attached
   
   

${basedir}/sql-DEV.xml

${pom.artifactId}
${basedir}/target/dev
   
 



//Assembly Descriptor - sql-DEV.xml


DEV

jar



 ${basedir}/../../../../Database/tables

 
*.sql
   


 


Thanks & Regards,
Logu Rajamanickam

-
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.

All repos disappear after attempt at "add remote repository"

[David Delbecq]

Using archiva 1.0.1, when i try to add a remote repository, after i 
click the "add", the interface comme back to my form, with all i filled 
in, without error message, but my list of repositories have now 
disappeared. I currently have have 4 local repos, and 4 remote repos, 
with links between remote repos and local repos. I have to restart the 
server to get them back. That's problematic, sinc i want to add a 
repository to archiva, and i can't do it. Server logs give no more 
informations. There is absolutely no output in logs during the operation!


Any clue where that comes from? I didn't find any existing bug report 
for this...


--
David Delbecq
Institut Royal Météorologique
Ext:557

Mvn 2 plugin to copy files?

[Dooing]

Hi,

While tomcat is running, I would like to move some files from my source folder 
to my tomcat/webapps/myproject folder - in case I altered these files - by 
calling some plugin and or goal.

Using Maven 1, we had a custom goal for this:

 

  



  
   


   
   
  

  

Now when using Maven 2, I've read custom goals using jelly are not supported by 
Maven 2 - one should create a custom plugin instead. Is this really necessary 
in this case? I guess there must be some plugin doing just the same job without 
having to develop a custom plugin. I tried mvn resources:resources, but this 
didn't work.

Any ideas? I am helpless!!! :-(((

Thanks in advance - your help's greatly appreciated!!!

Stefanie
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

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

maven plugin question

[Guillaume Boucherie]

Hi all,

I want to make a maven2 plugin for selenium-grid.
This selenium tools try to read a file named "grid_configuration.yml" at the
root of the classpath with ClassLoader.getResources().
In my plugin I create a "grid_configuration.yml" file but how can I had it
to the classpath ?
Thanks

Guillaume B.

maven-archiver

[Urooj Khan]

hi..

i get two directories called 'maven-archiver' and 'archive-tmp' in my target
directory
i dont know how and why these directories are being created.. is there a way
to stop this?

this is my pom.xml


  4.0.0
  elections
  elections
  Election
  v3_0_0_4
  Election
  http:///elections/
  
https://bugzilla.ca/
  
  2006
  
  
  
  
  
  
  
${basedir}/source
${basedir}/src/test

  
maven-jar-plugin

  elections

 
  
maven-javadoc-plugin

  http://java.sun.com/j2se/1.4.2/docs/api/
  private

  
  
maven-surefire-plugin

  
**/*Test.java
  

  
  
org.apache.maven.plugins
maven-assembly-plugin
2.2-beta-2

  
dist.xml
  

  

  
  

  xml-apis
  xml-apis
  1.0.b2

 
  

  
maven-changes-plugin

  ${basedir}/xdocs/changes.xml

  
  
maven-javadoc-plugin
  
  
maven-surefire-report-plugin
  

  
  

  default
  Default Repository
  file:///build/dist


  default
  Default Site
  scp://maven.ca/sites/maven.ca/docs/elections

  



-- 
Urooj Khan

[m2] How do I start tomcat and deploy my war via cargo manually?

[Mick Knutson]

I have the following plugin that starts and stops for my integration tests,
but I want to manually start Tomcat, then deploy my war

 *   
org.codehaus.cargo
cargo-maven2-plugin
0.3.1

${cargo.wait}

${cargo.container
}


${cargo.container.url}
${installDir}



${project.build.directory}/${
cargo.container}/container

${cargo.host
}
${cargo.port
}





start-container
pre-integration-test

start



stop-container
post-integration-test

stop




*
Do I just run:

1. mvn cargo:start
2. mvn cargo:deploy

??

When I do this, I get the following:

*[INFO] [talledLocalContainer] [myproject] TRACE [main]
CachedIntrospectionResults.(267) | Found bean property
'filterInvocationDefinitionSo
urce' of type [
org.acegisecurity.intercept.web.FilterInvocationDefinitionSource]
[INFO] [talledLocalContainer] [myproject] TRACE [main]
TypeConverterDelegate.doConvertValue(315) | Converting String to [interface
org.acegisecur
ity.intercept.web.FilterInvocationDefinitionSource] using property editor [
org.acegisecurity.intercept.web.FilterInvocationDefinitionSourceEditor
@9fe84e]
[INFO] [talledLocalContainer] [myproject] DEBUG [main]
DefaultListableBeanFactory.invokeInitMethods(1331) | Invoking
afterPropertiesSet() on bean
 with name 'filterChainProxy'
[INFO] [talledLocalContainer] [myproject] DEBUG [main]
DefaultListableBeanFactory.doGetBean(213) | Returning cached instance of
singleton bean 'o
rg.springframework.transaction.config.internalTransactionAdvisor'
[INFO] [talledLocalContainer] [myproject] DEBUG [main]
DefaultListableBeanFactory.run(406) | Finished creating instance of bean
'filterChainProxy
'
[INFO] [talledLocalContainer] [myproject] DEBUG [main]
DefaultListableBeanFactory.doGetBean(213) | Returning cached instance of
singleton bean 'f
ilterChainProxy'
[INFO] [talledLocalContainer] [myproject] INFO [main]
UrlRewriteFilter.info(227)
| loaded (conf ok)
[INFO] [talledLocalContainer] 28-Jan-2008 08:39:15
org.apache.catalina.startup.HostConfig deployWAR
[INFO] [talledLocalContainer] INFO: Deploying web application archive
cargocpc.war
[INFO] [talledLocalContainer] 28-Jan-2008 08:39:15
org.apache.coyote.http11.Http11BaseProtocol start
[INFO] [talledLocalContainer] INFO: Starting Coyote HTTP/1.1 on http-8080
[INFO] [talledLocalContainer] 28-Jan-2008 08:39:15
org.apache.catalina.startup.Catalina start
[INFO] [talledLocalContainer] INFO: Server startup in 11640 ms
[INFO] [talledLocalContainer] Tomcat 5.5.26 started on port [8080]
[INFO]

*


But I get a 404 error for *http://localhost:8080/index.html*

-- 
Thanks,
Mick Knutson

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

file system repo not work

[Alessandro Ferrucci]

Hello,

I have the relevant pom snippet below.  The problem is really with the 
eclipse plugin.  The plugin reports not being able to download the 2 
dependencies entity-client-1.0 and newsml-2.0.0.jar which are in my 
sandbox in the following location:


/home/ferucci/europa_workspace/photos/

This used to work on my macbook (which died last week :) ), but on my 
linux box it does not.


Eclipse complains of now being able to download the 2 given 
dependencies, but when I build with maven, it builds just fine and the 
jar gets downloaded in my local repo (from my sandbox). 

what could be wrong with eclipse? what are some debugging tricks I can 
try out with the maven eclipse plugin?


thanks

alessandro ferrucci




http://maven.apache.org/POM/4.0.0";
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd";>

   4.0.0
   com.aol.pubt.photos.common
   Photos
   photos
   0.0.1
   DPIS
   
   
   
   true
   src/main/resources/
   
   **/myconfig-ingestor.properties
   **/log4j.properties
   **/telescope.xsd
   **/newsML.dtd
   **/xsl/*.xsl
   
   
   
   true
   etc/
   
   **/*
   
   
   
   true
   release/
   
   **/*
   
   
   
   
   
   maven-compiler-plugin
   
   1.5
   1.5
   true
   true
   
   
   
   
   
   
   local sandbox repo
   DPIS Commons Sandbox repo
   file://${basedir}/release/lib
   
   
   
   
   org.apache
   newsml
   2.0
   
   
   com.aol.cm.entity
   entity-client
   1.0
   
   




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

Multi-module archetypes

[Prystash,John]

I'm stepping into my first foray into creating archeyptes.  In general,
is there support for creating an archetype for a multi-module project?
Or is better to build a project with multiple archetypes?  My first
thought would be I'd have problem injecting the parent project name into
the directory structure?

MyService
MyService-core
MyService-container

Thanks

[m2] issue running selenium with Tomcat 5 with Cargo plugin.

[Mick Knutson]

Ok, I am trying to run Selenium tests on my web app.
Now when I use this jetty plugin and start my webapp via jetty, I can see my
app running fine and my index.html (jsf) page displays fine:

*
org.mortbay.jetty
maven-jetty-plugin
6.1.6

/
3


src/main/webapp/WEB-INF
  

**/*.jsp
**/*.xhtml


**/*.properties
**/*.xml





*
*This is just a small bit of the html source from jetty running manually or
through Selenium IDE:
http://localhost:8080/index.html
*


http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"; >
http://www.w3.org/1999/xhtml";>


Main Index










*Now, when I run mvn install to deploy to the following tomcat5 server, all
my tests show no html thus it appears that under tomcat5 via cargo, the
pages are not there or they are blank:*
*
org.codehaus.cargo
cargo-maven2-plugin
0.3.1

${cargo.wait}

${cargo.container
}

${cargo.container.url}
${installDir}



${project.build.directory}/${
cargo.container}/container

${cargo.host
}
${cargo.port
}





start-container
pre-integration-test

start



stop-container
post-integration-test

stop




...
**tomcat5x*
**
*
http://archive.apache.org/dist/tomcat/tomcat-5/v5.5.26/bin/apache-tomcat-5.5.26.zip
*
**
***localhost*
*8080*
*false*
*
*
*Here is the selenium test:*

*selenium.open("/index.html");
log.debug
("=");
log.debug("selenium.getTitle(): " + selenium.getTitle());
log.debug("selenium.getLocation(): " + selenium.getLocation());
log.debug
("=");
log.debug("selenium.getHtmlSource(): " + selenium.getHtmlSource());
log.debug
("=");
//Assert.assertEquals(selenium.getTitle(), "Main Index", "'title'
should equal \"Main Index\"");


selenium.open(applicationAddress + "index.html");
log.debug
("=");
log.debug("selenium.getTitle(): " + selenium.getTitle());
log.debug("selenium.getLocation(): " + selenium.getLocation());
log.debug
("=");
log.debug("selenium.getHtmlSource(): " + selenium.getHtmlSource());
log.debug
("=");
//Assert.assertEquals(selenium.getTitle(), "Main Index", "'title'
should equal \"Main Index\"");

*

*Here is the selenium stack trace I get.*

*[myproject] INFO [main] LoginTest.init(34) | Starting Selenium client
[myproject] DEBUG [main] LoginTest.testSuccessfulLogin(62) |
=
[myproject] DEBUG [main] LoginTest.testSuccessfulLogin(63) |
selenium.getTitle():
[myproject] DEBUG [main] LoginTest.testSuccessfulLogin(64) |
selenium.getLocation(): http://localhost:8080/index.html
[myproject] DEBUG [main] LoginTest.testSuccessfulLogin(65) |
=
[myproject] DEBUG [main] LoginTest.testSuccessfulLogin(66) |
selenium.getHtmlSource(): 
[myproject] DEBUG [main] LoginTest.testSuccessfulLogin(67) |
=
[myproject] DEBUG [main] LoginTest.testSucces

RE: How create 2 *.jar

[Chris Helck]

I'd like to piggy back on to this discussion.

All our production builds are done in a controlled environment.
Different projects use make, ant, maven1, maven2, and custom scripts. We
would like, when a build is done, for the final artifacts to end up in a
dumb file location on the build box. Final artifacts tend to be
installers, usually not jar files. The guys doing the build don't really
care about maven or repositories, they just want to start the build, and
then get the results.

So my question is: how to make maven1 and maven2 do an extra copy into a
directory? 

Thanks,
C. Helck
 

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 28, 2008 10:25 AM
To: Maven Users List
Subject: Re: How create 2 *.jar

Tell us more about the remote directory. Is this a "Maven repository"
or is it simply a dumb file location? How do the other people get the
file, are they running Maven also or something else?

The more information you provide, the better the response will be.
Generally, I would suggest that you set up something like Archiva and
use "mvn deploy" to copy the file into Archiva.

Wayne

On 3/28/08, author <[EMAIL PROTECTED]> wrote:
>
> My project (my *.jar file) used by others team-members. When i use 
> 'mvn package' goal, i recive 1 *.jar file in my project folder in
folder target.
> Then i copy my *.jar file to remote directory, which shared for all 
> others team member. How can i do it automatically (for example using 
> pom.xml or ect).
> THX
> --
> View this message in context: 
> http://www.nabble.com/How-create-2-*.jar-tp16325044s177p16349642.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]
>
>

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


**
This communication and all information (including, but not limited to,
 market prices/levels and data) contained therein (the "Information") is
 for informational purposes only, is confidential, may be legally
 privileged and is the intellectual property of ICAP plc and its affiliates
 ("ICAP") or third parties. No confidentiality or privilege is waived or
 lost by any mistransmission. The Information is not, and should not
 be construed as, an offer, bid or solicitation in relation to any
 financial instrument or as an official confirmation of any transaction.
 The Information is not warranted, including, but not limited, as to
 completeness, timeliness or accuracy and is subject to change
 without notice. ICAP assumes no liability for use or misuse of the
 Information. All representations and warranties are expressly
 disclaimed. The Information does not necessarily reflect the views of
 ICAP. Access to the Information by anyone else other than the
 recipient is unauthorized and any disclosure, copying, distribution or
 any action taken or omitted to be taken in reliance on it is prohibited. If
 you receive this message in error, please immediately delete it and all
 copies of it from your system, destroy any hard copies of it and
 notify the sender.
**


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

Re: "Cannot execute mojo: eclipse."

[Wayne Fay]

In the future, you might just go right to the source and ask the
originating team responsible for the code why it doesn't compile. So
in this case, ask Atlassian directly.

(IMO the Maven users list cannot possibly hope to support every single
developer who stumbles across an open-source project that uses Maven
as their build tool and then has a problem building the code. So most
questions like these should be sent to the responsible development
team first, then if they can't help you can forrward it here. You may
be doing them a favor by notifying them of a problem they didn't even
know they had! )

Wayne

On 3/28/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Otherwise, you could try the distribution of the plugin ;)
>
> http://svn.atlassian.com/svn/public/contrib/jira/jira-calendar-plugin/distributions/
>
> Hth,
>
> Nick S.
>
>

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

Re: "Cannot execute mojo: eclipse."

[Attila Szegedi]

I can't exactly se how can that help me with my customization of the  
plugin's code :-)


Attila.


On 2008.03.28., at 15:27, <[EMAIL PROTECTED]> wrote:

Otherwise, you could try the distribution of the plugin ;)

http://svn.atlassian.com/svn/public/contrib/jira/jira-calendar-plugin/distributions/

Hth,

Nick S.








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

Re: Third Party Jar

[Wayne Fay]

There is already an XML plugin in Codehaus which has XSLT
functionality. Why don't you just take a look at it before moving too
far down this path of possibly re-implementing an existing solution?

http://mojo.codehaus.org/xml-maven-plugin/

Wayne

On 3/28/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote:
> It seems that this goes deeper. What I actually need to do is create a Maven
> plugin that performs an XSL transformation using Saxon 9. I unpacked the
> Saxon 9 jar and added the classes to my plugin jar to make sure the
> transformer is loaded. However, it seems that the transformer won't get
> loaded, even when I run Maven with
>-
> Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
> Some people seem to have worked around this by specifying the Saxon
> dependency in the client pom.xml but this doesn't seem to work if I make the
> transformation call from the plugin Jar. I even set the property manually in
> the plugin:
>TransformerFactory factory = TransformerFactory.newInstance();
> But without any luck. The transformer will not be found
>
> Thanks in advance
>
> On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]>
> wrote:
>
> > Hello guys,
> >
> > Sorry to bother you with such issues, but I've googling my brains out with
> > this without any relevant results.
> > I have a question regarding bundling a 3rd party jar in a Maven Plugin. I
> > am a bit new to Maven and Maven plugins.
> > I tried bundling it in the plugin jar and adding it to the Class-Path
> > attribute of MANIFEST.MF, but it seems to be ignored when using the
> > plugin.
> > Another question would be: assuming that somehow this 3rd party jar will
> > make it into a public repository, what is the proper way to configure the
> > dependency to make sure that the client (plugin user) will download and load
> > this jar correctly without having to configure 3rd third party dependency in
> > the pom.xml?
> >
> > Many thanks in advance
> >
> > --
> > Cosmin Marginean
>
>
>
>
> --
> Cosmin Marginean
>

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

RE: "Cannot execute mojo: eclipse."

[nicklist]

Otherwise, you could try the distribution of the plugin ;)

http://svn.atlassian.com/svn/public/contrib/jira/jira-calendar-plugin/distributions/

Hth,

Nick S.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Fri 3/28/2008 15:23
To: Maven Users List
Subject: RE: "Cannot execute mojo: eclipse."
 
It seems that version of the jira-plugin still uses maven 1 (You've got a 
project.xml file, not a pom.xml file), so maven 2 will not work on that plugin.

The trunk of the plugin is using m2 instead of m1, so you could try that one (I 
don't know how stable the trunk is) or you could try using maven 1.

Hth,

Nick S.


-Original Message-
From: Attila Szegedi [mailto:[EMAIL PROTECTED]
Sent: Fri 3/28/2008 15:05
To: users@maven.apache.org
Subject: "Cannot execute mojo: eclipse."
 
Hi folks,

I'm trying to use Maven to build a project that uses it (fwiw, it's  
the calendar plugin for JIRA: 
). I just can't seem to be able to get anything to run, let me  
elaborate further:

I downloaded and installed Maven 2.0.8, on Mac OS X. I put it in /usr/ 
local/apache-maven-2.0.8 and symlinked it to /usr/local/apache-maven.  
M2_HOME points to /usr/local/apache-maven, M2 to $M2_HOME/bin. M2/mvn  
is also symlinked into /usr/local/bin (so it's on path - I don't like  
putting new items into my path).

The version info is as:

$mvn --version
Maven version: 2.0.8
Java version: 1.5.0_13
OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix"

As suggested by Atlassian on their "How to build an Atlassian plugin"  
page at 
, I also added their settings.xml to the ~/.m2/ directory, see 
 >.

The problem is: I can't get "mvn eclipse:eclipse" to run. Here's an  
attempt from the same directory where the pom.xml and maven.xml for  
the project are:

$ mvn -e eclipse:eclipse
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]  

[INFO] Building Maven Default Project
[INFO]task-segment: [eclipse:eclipse]
[INFO]  

[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO]  

[ERROR] BUILD ERROR
[INFO]  

[INFO] Cannot execute mojo: eclipse. It requires a project with an  
existing pom.xml, but the build is not using one.
[INFO]  

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute  
mojo: eclipse. It requires a project with an existing pom.xml, but the  
build is not using one.
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
564)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot  
execute mojo: eclipse. It requires a project with an existing pom.xml,  
but the build is not using one.
at  
org 
.apache 
.maven 
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373)
at  
org 
.apach

RE: "Cannot execute mojo: eclipse."

[nicklist]

It seems that version of the jira-plugin still uses maven 1 (You've got a 
project.xml file, not a pom.xml file), so maven 2 will not work on that plugin.

The trunk of the plugin is using m2 instead of m1, so you could try that one (I 
don't know how stable the trunk is) or you could try using maven 1.

Hth,

Nick S.


-Original Message-
From: Attila Szegedi [mailto:[EMAIL PROTECTED]
Sent: Fri 3/28/2008 15:05
To: users@maven.apache.org
Subject: "Cannot execute mojo: eclipse."
 
Hi folks,

I'm trying to use Maven to build a project that uses it (fwiw, it's  
the calendar plugin for JIRA: 
). I just can't seem to be able to get anything to run, let me  
elaborate further:

I downloaded and installed Maven 2.0.8, on Mac OS X. I put it in /usr/ 
local/apache-maven-2.0.8 and symlinked it to /usr/local/apache-maven.  
M2_HOME points to /usr/local/apache-maven, M2 to $M2_HOME/bin. M2/mvn  
is also symlinked into /usr/local/bin (so it's on path - I don't like  
putting new items into my path).

The version info is as:

$mvn --version
Maven version: 2.0.8
Java version: 1.5.0_13
OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix"

As suggested by Atlassian on their "How to build an Atlassian plugin"  
page at 
, I also added their settings.xml to the ~/.m2/ directory, see 
 >.

The problem is: I can't get "mvn eclipse:eclipse" to run. Here's an  
attempt from the same directory where the pom.xml and maven.xml for  
the project are:

$ mvn -e eclipse:eclipse
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]  

[INFO] Building Maven Default Project
[INFO]task-segment: [eclipse:eclipse]
[INFO]  

[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO]  

[ERROR] BUILD ERROR
[INFO]  

[INFO] Cannot execute mojo: eclipse. It requires a project with an  
existing pom.xml, but the build is not using one.
[INFO]  

[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute  
mojo: eclipse. It requires a project with an existing pom.xml, but the  
build is not using one.
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
564)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 
430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot  
execute mojo: eclipse. It requires a project with an existing pom.xml,  
but the build is not using one.
at  
org 
.apache 
.maven 
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373)
at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
539)
... 16 more
[INFO]  

[INFO] Total time: < 1 second
[INFO] Finished at: Fri Mar 28 15:03:02 CET 2008
[INFO] Final Memory: 2M/4M
[INFO]  
-

Re: How create 2 *.jar

[Wayne Fay]

Tell us more about the remote directory. Is this a "Maven repository"
or is it simply a dumb file location? How do the other people get the
file, are they running Maven also or something else?

The more information you provide, the better the response will be.
Generally, I would suggest that you set up something like Archiva and
use "mvn deploy" to copy the file into Archiva.

Wayne

On 3/28/08, author <[EMAIL PROTECTED]> wrote:
>
> My project (my *.jar file) used by others team-members. When i use 'mvn
> package' goal, i recive 1 *.jar file in my project folder in folder target.
> Then i copy my *.jar file to remote directory, which shared for all others
> team member. How can i do it automatically (for example using pom.xml or
> ect).
> THX
> --
> View this message in context: 
> http://www.nabble.com/How-create-2-*.jar-tp16325044s177p16349642.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]
>
>

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

"Cannot execute mojo: eclipse."

[Attila Szegedi]

(Apologies if this gets received twice; I sent the first copy before I  
got the registration confirmation back from the mailing list manager)


Hi folks,

I'm trying to use Maven to build a project that uses it (fwiw, it's  
the calendar plugin for JIRA: ). I just can't seem to be able to get anything to run, let me  
elaborate further:


I downloaded and installed Maven 2.0.8, on Mac OS X. I put it in /usr/ 
local/apache-maven-2.0.8 and symlinked it to /usr/local/apache-maven.  
M2_HOME points to /usr/local/apache-maven, M2 to $M2_HOME/bin. M2/mvn  
is also symlinked into /usr/local/bin (so it's on path - I don't like  
putting new items into my path).


The version info is as:

$mvn --version
Maven version: 2.0.8
Java version: 1.5.0_13
OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix"

As suggested by Atlassian on their "How to build an Atlassian plugin"  
page at , I also added their settings.xml to the ~/.m2/ directory, see .


The problem is: I can't get "mvn eclipse:eclipse" to run. Here's an  
attempt from the same directory where the pom.xml and maven.xml for  
the project are:


$ mvn -e eclipse:eclipse
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]  


[INFO] Building Maven Default Project
[INFO]task-segment: [eclipse:eclipse]
[INFO]  


[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO]  


[ERROR] BUILD ERROR
[INFO]  

[INFO] Cannot execute mojo: eclipse. It requires a project with an  
existing pom.xml, but the build is not using one.
[INFO]  


[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute  
mojo: eclipse. It requires a project with an existing pom.xml, but the  
build is not using one.
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
564)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeTaskSegments(DefaultLifecycleExecutor.java:278)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
	at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)

at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 
430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot  
execute mojo: eclipse. It requires a project with an existing pom.xml,  
but the build is not using one.
	at  
org 
.apache 
.maven 
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
539)

... 16 more
[INFO]  


[INFO] Total time: < 1 second
[INFO] Finished at: Fri Mar 28 15:03:02 CET 2008
[INFO] Final Memory: 2M/4M
[INFO]  



Any help appreciated.

Attila.

--
home: http://www.szegedi.org
weblog: http://constc.blogspot.com

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

maven2 assembly plug-in

[Urooj Khan]

Sorry if this is a repost... Not sure if the first one got out...



-- Forwarded message --
From: Urooj Khan <[EMAIL PROTECTED]>
Date: Thu, 27 Mar 2008 20:04:24 -0400
Subject: maven2 assembly plug-in
To: users@maven.apache.org

i'm using the assembly plug-in to create an assembly in the form of a
directory which contains my
jar file which is created by maven and it also contains a lib directory with
all the jar files that are dependencies of this build

this is what my assembly xml looks like


  dist
  
dir
  
  false
  

  target
  
  
*.jar
  

  
  

  /lib
  false
  runtime

  



when i run $>mvn clean package assembly:assembly

i get my ${project}.jar in the target directory and i also get a directory
called ${project.build.dir} inside the target directory.
this directory contains my ${project}.jar and a /lib directory with all the
dependency jars...

i want to rename ${project.build.dir} that maven creates to just
${project}.dir

any idea how i can do that?

please help.

thanks.

-uk

-- 
Sent from Gmail for mobile | mobile.google.com

Urooj Khan

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

"Cannot execute mojo: eclipse."

[Attila Szegedi]

Hi folks,

I'm trying to use Maven to build a project that uses it (fwiw, it's  
the calendar plugin for JIRA: ). I just can't seem to be able to get anything to run, let me  
elaborate further:


I downloaded and installed Maven 2.0.8, on Mac OS X. I put it in /usr/ 
local/apache-maven-2.0.8 and symlinked it to /usr/local/apache-maven.  
M2_HOME points to /usr/local/apache-maven, M2 to $M2_HOME/bin. M2/mvn  
is also symlinked into /usr/local/bin (so it's on path - I don't like  
putting new items into my path).


The version info is as:

$mvn --version
Maven version: 2.0.8
Java version: 1.5.0_13
OS name: "mac os x" version: "10.5.2" arch: "i386" Family: "unix"

As suggested by Atlassian on their "How to build an Atlassian plugin"  
page at , I also added their settings.xml to the ~/.m2/ directory, see .


The problem is: I can't get "mvn eclipse:eclipse" to run. Here's an  
attempt from the same directory where the pom.xml and maven.xml for  
the project are:


$ mvn -e eclipse:eclipse
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'eclipse'.
[INFO]  


[INFO] Building Maven Default Project
[INFO]task-segment: [eclipse:eclipse]
[INFO]  


[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO]  


[ERROR] BUILD ERROR
[INFO]  

[INFO] Cannot execute mojo: eclipse. It requires a project with an  
existing pom.xml, but the build is not using one.
[INFO]  


[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute  
mojo: eclipse. It requires a project with an existing pom.xml, but the  
build is not using one.
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
564)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor 
.executeTaskSegments(DefaultLifecycleExecutor.java:278)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)

at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at  
sun 
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 
39)
	at  
sun 
.reflect 
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 
25)

at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
	at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 
430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot  
execute mojo: eclipse. It requires a project with an existing pom.xml,  
but the build is not using one.
	at  
org 
.apache 
.maven 
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373)
	at  
org 
.apache 
.maven 
.lifecycle 
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
539)

... 16 more
[INFO]  


[INFO] Total time: < 1 second
[INFO] Finished at: Fri Mar 28 15:03:02 CET 2008
[INFO] Final Memory: 2M/4M
[INFO]  



Any help appreciated.

Attila.

--
home: http://www.szegedi.org
weblog: http://constc.blogspot.com

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

RE: Maven Assembly Plugin

[Brian E. Fox]

You need to specify a base directory to search in the fileset element.
Take a look at the standard assembly descriptors shown on the plugin
site.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 28, 2008 7:52 AM
To: users@maven.apache.org
Subject: Maven Assembly Plugin

Hi,

I am trying to create a zip file containing all static web content, to
be put on a separate Apache server. The Maven Assembly plugin seems to
be meant to be used for such a task -
http://maven.apache.org/plugins/maven-assembly-plugin/

According to the instructions given, I added:

...

  maven-assembly-plugin

  
 
${basedir}/my-maven-assembly-desc.xml
  




to my parent pom.

Then I created the file my-maven-assembly-desc.xml in the base directory
of my subproject:



myzip

zip




**/*.css
**/*.js
**/*.pdf
**/favicon.ico
**/*.gif
**/*.jpg
**/*.png
**/robots.txt
**/*.xsd



true
false


However, when executing mvn assembly:assembly I get this error:

[INFO] [assembly:assembly]
[INFO] Reading assembly descriptor:
D:\MYPROJECT/my-maven-assembly-desc.xml
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to create assembly: Error creating assembly archive myzip:
You must set at least one file.

Any ideas what's wrong here?


Thanks in advance!

Stefanie

-
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: RE : [deploy-plugin] Abort deploy when a target is present

[Brian E. Fox]

I'd have to check on this. I know in 2.1 it's on by default and there is no way 
to force it. Perhaps Jason put it in the wagon manager or something and not the 
plugin. 

-Original Message-
From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 28, 2008 2:53 AM
To: Maven Users List
Subject: RE : [deploy-plugin] Abort deploy when a target is present

Great news!

I had a quick look on 
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-deploy-plugin/ and 
did not see any log related to it.
So was there already a logged bug about this: 
http://jira.codehaus.org/browse/MDEPLOY-74

What/where is the "new code", some 3.x or something? So, is there another svn 
repository for this? In fact, I'd be happy to be able to either use a new 
released version or help merging back this feature if possible.

Cheers

 Message d'origine
De: Brian E. Fox [mailto:[EMAIL PROTECTED]
Date: jeu. 27/03/2008 18:45
À: Maven Users List
Objet : RE: [deploy-plugin] Abort deploy when a target is present
 
This is the default in the new code, but it wasn't merged back to 2.0.x I 
believe.

-Original Message-
From: MATHUS Baptiste [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2008 9:32 AM
To: Maven Users List
Subject: [deploy-plugin] Abort deploy when a target is present

Hi all,

Recently, some developers did a release manually. So they put a release version 
in the pom and triggered a deploy. Everything fine but...
The thing is: they forgot to re-update the pom.version to a new snapshot 
version.

So, as the code is continuously integrated, at each new commit, the recent 
release was "automatically" overridden many times with the snapshot code before 
realizing it :-/.
So, what I would like is to be able to put an additional option for maven when 
run inside the continuous integration server, something like 
-DdontOverrideRelease, that would make fail the deployment if the released 
artefact is already present.

I've taken a quick look at
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html but it 
seems it's not currently possible.
What do you think? Can a file an feature request about it in the plugin tracker?

Thanks a lot.

Cheers.
--
Baptiste


-
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: How to delete JSPs after precompilation?

[Olivier Jacob]

Hello again :)

Now I've the configuration at hand, here it is :


org.codehaus.mojo.jspc
jspc-maven-plugin



compile







org.codehaus.mojo.jspc
jspc-compiler-tomcat5
2.0-alpha-1





org.apache.maven.plugins
maven-war-plugin

${pom.basedir}/target/jspweb.xml

**/*.jsp,**/*.jspf



Looks a lot easier to me.

Olivier

On Thu, Mar 27, 2008 at 11:37 PM, Glen Mazza <[EMAIL PROTECTED]> wrote:

>
> I found the answer to my problem and would like to save it here for the
> archives.
>
> The basic process I followed was: after the WAR is created, use the
> maven-antrun-plugin to open it up, delete the JSP's, and rezip the WAR.
>  To
> do this, I added the following execution to my maven-antrun-plugin
> 
> as follows:
>
>
> 
>   pre-integration-test
>   removeJSPs
>   
>  
>  src="${project.build.directory}/${project.build.finalName}.war"
>dest="${project.build.directory}/myTmp" />
> 
> includes="**/*.jsp" />
> 
>  file="${project.build.directory}/${project.build.finalName}.war" />
> 
> destfile="${project.build.directory}/${project.build.finalName}.war"/>
> 
>   
>   
>   
>  run
>   
> 
>
> I chose the "pre-integration-test" phase so it runs right after the
> "package" (WAR creation) phase[1].  The process above also creates a
> temporary "target/myTmp" folder to do the opening and re-zipping of the
> WAR
> file.  The last  above removes it.
>
> [1]
>
> http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference
>
>
>
> Glen Mazza wrote:
> >
> > Hello All,
> >
> > The page[1] below nicely shows us how to precompile JSPs before the WAR
> is
> > created.  It works perfectly well.  Problem is though, we have an
> > additional requirement to delete the JSPs after they are precompiled, so
> > that no JSPs are in the WAR (only their compiled versions are to stay.)
> > How can we modify [1] below--what else do we need to do--to delete the
> > JSPs *before* the WAR is created?
> >
> > This is what we have tried:
> >
> >   maven-antrun-plugin
> >   
> > 
> >   process-classes
> >   deploy
> >   
> > 
> >   
> >  > dir="${project.build.directory}/${project.build.finalName}"
> > includes="**/*.jsp" />
> >   
> > 
> >   
> >   
> > run
> >   
> > 
> >   
> > 
> >
> > But we can't get it to work--either the generated resources directory it
> > looks in is not yet created, perhaps we've gotten the goal and/or phase
> > mixed up, or?  Any help would be much appreciated!
> >
> > Regards,
> > Glen
> >
> > [1] http://mojo.codehaus.org/jspc-maven-plugin/usage.html
> >
>
> --
> View this message in context:
> http://www.nabble.com/How-to-delete-JSPs-after-precompilation--tp16331157s177p16339518.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]
>
>


-- 
Olivier Jacob
Consultant - OCTO Technology
50, avenue des Champs Elysées
75008 Paris

Re: RE: Maven Assembly Plugin

[Dooing]

I guess I should mention I am not using the default maven project structure -
for example, the static source code is under src/war -
maybe I will have to adjust the maven assembly default paths?

Thanks,

Stefanie



-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

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

Re: RE: Maven Assembly Plugin

[Dooing]

> Inside of my fileSet element I have included a:
> 
> ${basedir}
> 
> Element...
> 
> Does this help?

nope, unfortunately, it didnt work.

This, as I understand it, simple says "take all files from basedir".

Thanks,

Stefanie
-- 
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

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

Re: Maven Jetty Plugin and filtered resources

[Bruno Aranda]

I have the same problem as explained below. Does someone know of a
solution or alternative?

Thanks,

Bruno

On 26/10/2006, Martin Gilday <[EMAIL PROTECTED]> wrote:
> Hi,
>  I am trying to use the Jetty plugin for Maven but have my web.xml
>  filtered with properties.  This is mainly as I have a "sandbox" profile
>  which when active would change the spring config file being used.
>
>  I have tried using the WAR plugin to define some filtered resources
>
>  
>   
> org.apache.maven.plugins
> maven-war-plugin
> 2.0
> 
>   
> 
>   src/main/webapp
>   true
> 
>   
> 
>   
>  
>
>  When I use "mvn package" the web.xml is filtered correctly, for both
>  profiles.  However when I use "mvn jetty:run" the properties are not
>  substituted.
>
>  Is it possible to do this?
>
>  Thanks,
>  Martin.
>
>  -
>  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: How create 2 *.jar

[author]

My project (my *.jar file) used by others team-members. When i use 'mvn
package' goal, i recive 1 *.jar file in my project folder in folder target.
Then i copy my *.jar file to remote directory, which shared for all others
team member. How can i do it automatically (for example using pom.xml or
ect).
THX
-- 
View this message in context: 
http://www.nabble.com/How-create-2-*.jar-tp16325044s177p16349642.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: Maven Assembly Plugin

[Matthew Tordoff]

   
Inside of my fileSet element I have included a:

${basedir}

Element...

Does this help?


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 28 March 2008 11:52
To: users@maven.apache.org
Subject: Maven Assembly Plugin

Hi,

I am trying to create a zip file containing all static web content, to
be put on a separate Apache server. The Maven Assembly plugin seems to
be meant to be used for such a task -
http://maven.apache.org/plugins/maven-assembly-plugin/

According to the instructions given, I added:

...

  maven-assembly-plugin

  
 
${basedir}/my-maven-assembly-desc.xml
  




to my parent pom.

Then I created the file my-maven-assembly-desc.xml in the base directory
of my subproject:



myzip

zip




**/*.css
**/*.js
**/*.pdf
**/favicon.ico
**/*.gif
**/*.jpg
**/*.png
**/robots.txt
**/*.xsd



true
false


However, when executing mvn assembly:assembly I get this error:

[INFO] [assembly:assembly]
[INFO] Reading assembly descriptor:
D:\MYPROJECT/my-maven-assembly-desc.xml
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to create assembly: Error creating assembly archive myzip:
You must set at least one file.

Any ideas what's wrong here?


Thanks in advance!

Stefanie

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




The content of this e-mail is confidential and may be privileged. It may be 
read, copied and used only by the intended recipient and may not be disclosed, 
copied or distributed. If you received this email in error, please contact the 
sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete 
it and do not disclose its contents to any person. You should take full 
responsibility for checking this email for viruses. Markit reserves the right 
to monitor all e-mail communications through its network.
Markit and its affiliated companies make no warranty as to the accuracy or 
completeness of any information contained in this message and hereby exclude 
any liability of any kind for the information contained herein. Any opinions 
expressed in this message are those of the author and do not necessarily 
reflect the opinions of Markit.
For full details about Markit, its offerings and legal terms and conditions, 
please see Markit's website at http://www.markit.com  .

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

RE: switch by profile? How to switch between (Archiva) environments?

[nicklist]

What I've done on my laptop:

I created multiple settings.xml (settings.xml.home, settings.xml.work, etc) and 
with a script I make a symlink to the right settings.xml.x to settings.xml. 
Just run the command once and I am set for that environment.

Hth,

Nick S.


-Original Message-
From: [EMAIL PROTECTED] on behalf of Maria Odea Ching
Sent: Fri 3/28/2008 11:54
To: Maven Users List
Subject: Re: switch  by profile? How to switch between (Archiva) 
environments?
 
Hi Torsten,

The  cannot be configured with profiles. What you could do instead
is set each repository in different profiles using the  section,
and just activate which profile you want to use for a specific build.

This might help too:
http://maven.apache.org/archiva/docs/1.0.1/userguide/using-repository.html

Thanks,
Deng

On Fri, Mar 28, 2008 at 6:00 PM, <[EMAIL PROTECTED]> wrote:

> Hi,
>
> actually we have a file-based Repository, so for that I have the following
>  section in my settings.xml:
>
>
>  GDCAMS-2.5-Main - mirror of central repo1.maven.org/maven2
>  GD proxy for central repository
>  file:/V:/3L_Solutions/08. Entwicklungsprojekte/PDV
> CMS/40_Builds/Repositories/GDCAMS-2.5-Main
>  central
>
>
> Now, I want to use Archiva as Repository, so I need to modify the
> settings.xml to:
>
>
>  archiva.default
>  Archiva Internal Repository
>  http://myserver:8080/archiva/repository/internal
>  central
>
>
> How can I support both environments?
> I need to support both, because for older branches I won't change the
> build environment, but for the newest ( Main\Latest) I will use Archiva.
>
> I know about the -s option - is there a profile based solution, too?
>
> Thanx, Torsten
>

Maven Assembly Plugin

[Dooing]

Hi,

I am trying to create a zip file containing all static web content, to be put 
on a separate Apache server. The Maven Assembly plugin seems to be meant to be 
used for such a task - http://maven.apache.org/plugins/maven-assembly-plugin/

According to the instructions given, I added:

...

  maven-assembly-plugin

  
${basedir}/my-maven-assembly-desc.xml
  




to my parent pom.

Then I created the file my-maven-assembly-desc.xml in the base directory of my 
subproject:



myzip

zip




**/*.css
**/*.js
**/*.pdf
**/favicon.ico
**/*.gif
**/*.jpg
**/*.png
**/robots.txt
**/*.xsd



true
false


However, when executing mvn assembly:assembly I get this error:

[INFO] [assembly:assembly]
[INFO] Reading assembly descriptor: D:\MYPROJECT/my-maven-assembly-desc.xml
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Failed to create assembly: Error creating assembly archive myzip: You 
must set at least one file.

Any ideas what's wrong here?


Thanks in advance!

Stefanie

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

Re: switch by profile? How to switch between (Archiva) environments?

[Maria Odea Ching]

Hi Torsten,

The  cannot be configured with profiles. What you could do instead
is set each repository in different profiles using the  section,
and just activate which profile you want to use for a specific build.

This might help too:
http://maven.apache.org/archiva/docs/1.0.1/userguide/using-repository.html

Thanks,
Deng

On Fri, Mar 28, 2008 at 6:00 PM, <[EMAIL PROTECTED]> wrote:

> Hi,
>
> actually we have a file-based Repository, so for that I have the following
>  section in my settings.xml:
>
>
>  GDCAMS-2.5-Main - mirror of central repo1.maven.org/maven2
>  GD proxy for central repository
>  file:/V:/3L_Solutions/08. Entwicklungsprojekte/PDV
> CMS/40_Builds/Repositories/GDCAMS-2.5-Main
>  central
>
>
> Now, I want to use Archiva as Repository, so I need to modify the
> settings.xml to:
>
>
>  archiva.default
>  Archiva Internal Repository
>  http://myserver:8080/archiva/repository/internal
>  central
>
>
> How can I support both environments?
> I need to support both, because for older branches I won't change the
> build environment, but for the newest ( Main\Latest) I will use Archiva.
>
> I know about the -s option - is there a profile based solution, too?
>
> Thanx, Torsten
>

RE: apt-get repository

[nicklist]

Maybe you can use Eclipse (m2eclipse [1]) or Netbeans(mevenide [2]) with their 
maven plugin. Those plugins index the central repository and allow you to 
search and add dependencies.

[1] http://m2eclipse.codehaus.org
[2] http://mevenide.codehaus.org

Hth,

Nick S.


-Original Message-
From: neo anderson [mailto:[EMAIL PROTECTED]
Sent: Fri 3/28/2008 10:58
To: users@maven.apache.org
Subject: apt-get repository
 

I have one question. Does any maven command or plugin support serach and add
dependency automatically (a bit like Debian apt-get)? For instance, I use
archetype to create an ejb project. Then I want to use jboss as my ejb
container. So I need to add a lot of dependencies. Is there any command or
plugin like 'mvn dependency:search-jboss'/ 'mvn dependency:add-jboss'
enabling mvn to automatically accomplish the dependencies section? Though
those dependencies can be added manually by editing the pom.xml, it is a bit
tedious step and easily to mistype the wrong characters. Or is there any
better way to accomplish such task? 

Thank you very much, 
-- 
View this message in context: 
http://www.nabble.com/apt-get-repository-tp16348997s177p16348997.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: apt-get repository

[MATHUS Baptiste]

I you use eclipse, give a try to m2eclipse, there's an "add dependency" that 
has a autocomplete feature.

Cheers.

> -Message d'origine-
> De : neo anderson [mailto:[EMAIL PROTECTED] 
> Envoyé : vendredi 28 mars 2008 10:58
> À : users@maven.apache.org
> Objet : apt-get repository
> 
> 
> I have one question. Does any maven command or plugin support 
> serach and add dependency automatically (a bit like Debian 
> apt-get)? For instance, I use archetype to create an ejb 
> project. Then I want to use jboss as my ejb container. So I 
> need to add a lot of dependencies. Is there any command or 
> plugin like 'mvn dependency:search-jboss'/ 'mvn dependency:add-jboss'
> enabling mvn to automatically accomplish the dependencies 
> section? Though those dependencies can be added manually by 
> editing the pom.xml, it is a bit tedious step and easily to 
> mistype the wrong characters. Or is there any better way to 
> accomplish such task? 
> 
> Thank you very much,
> --
> View this message in context: 
> http://www.nabble.com/apt-get-repository-tp16348997s177p16348997.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]
> 

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

Re: Deploy artifact to archiva for the first time - error

[Paul G]

Brett,

I have tried adding a user with repository observer and manager roles and
have also tried giving the guest user the repository manager role as well.
But still it does not work. I have even tried putting a wrong password/wrong
user name in my settings.xml to see what sort of error I get back, but I
still got the same error. I even tried to deploy the snapshot to the realse
only repo and I still got the same error.

Now I'm really confused, must admit I got artifactory working quicker that
this! 

Below is my user set up in settings.xml

  archiva.team.snapshot
  deployer
  password1234




Brett Porter wrote:
> 
> I think this is a result of not having permissions to write that file
> on the server
> 
> On 28/03/2008, Paul G <[EMAIL PROTECTED]> wrote:
>>
>>  I have just set Archiva as per the docs my build works fine all the
>> artifacts
>>  are downloaded within Archiva. But when I come to deploy to a newly
>> created
>>  repository managed by Archiva using web dav I get the following error
>>  [INFO] Error deploying artifact: Resource to deploy not found: File:
>> 
>> http://localhost:8800/archiva/repository/team_snapshot/psg/scratch/beanUtils/BeanUtilsEx/0.0.1-SNAPSHOT/BeanUtilsEx-0.0.1-20080327.223426-1.jar
>>  does not exist
>>
>>  This is my pom file
>>  
>> 
>> archiva.team.release
>> Internal Release Repository
>> 
>>
>> dav:http://localhost:8800/archiva/repository/team_release/
>> 
>> 
>> 
>> archiva.team.snapshot
>> Internal Snapshot Repository
>> 
>>
>> dav:http://localhost:8800/archiva/repository/team_snapshot/
>> 
>> 
>> 
>>
>>  Why is webdav complaining the artifact is not found, surely it is not
>> there
>>  as it is the first time I have deployed?
>>  Help I'm confused. Below is the full stack trace when running in debug.
>>  [INFO] Error deploying artifact: Resource to deploy not found: File:
>>  http://loca
>> 
>> lhost:8800/archiva/repository/team_snapshot/psg/scratch/beanUtils/BeanUtilsEx/0.
>>  0.1-SNAPSHOT/BeanUtilsEx-0.0.1-20080327.224101-1.jar does not exist
>>
>>  [INFO]
>>  
>>  [INFO] Trace
>>  org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
>>  artifact
>>  : Resource to deploy not found: File:
>>  http://localhost:8800/archiva/repository/t
>> 
>> eam_snapshot/psg/scratch/beanUtils/BeanUtilsEx/0.0.1-SNAPSHOT/BeanUtilsEx-0.0.1-
>>  20080327.224101-1.jar does not exist
>> at
>>  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
>>  ultLifecycleExecutor.java:564)
>> at
>>  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
>>  fecycle(DefaultLifecycleExecutor.java:480)
>> at
>>  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
>>  ltLifecycleExecutor.java:459)
>> at
>>  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
>>  dleFailures(DefaultLifecycleExecutor.java:311)
>> at
>>  org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
>>  ts(DefaultLifecycleExecutor.java:278)
>> at
>>  org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
>>  fecycleExecutor.java:143)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>  java:39)
>> at
>>  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>  sorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>>  org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>>  org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>>
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>  Caused by: org.apache.maven.plugin.MojoExecutionException: Error
>> deploying
>>  artif
>>  act: Resource to deploy not found: File:
>>  http://localhost:8800/archiva/repositor
>> 
>> y/team_snapshot/psg/scratch/beanUtils/BeanUtilsEx/0.0.1-SNAPSHOT/BeanUtilsEx-0.0
>>  .1-20080327.224101-1.jar does not exist
>> at
>>  org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174
>>  )
>> at
>>  org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
>>  nManager.java:447)
>> at
>>  or

apt-get repository

[neo anderson]

I have one question. Does any maven command or plugin support serach and add
dependency automatically (a bit like Debian apt-get)? For instance, I use
archetype to create an ejb project. Then I want to use jboss as my ejb
container. So I need to add a lot of dependencies. Is there any command or
plugin like 'mvn dependency:search-jboss'/ 'mvn dependency:add-jboss'
enabling mvn to automatically accomplish the dependencies section? Though
those dependencies can be added manually by editing the pom.xml, it is a bit
tedious step and easily to mistype the wrong characters. Or is there any
better way to accomplish such task? 

Thank you very much, 
-- 
View this message in context: 
http://www.nabble.com/apt-get-repository-tp16348997s177p16348997.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]

switch by profile? How to switch between (Archiva) environments?

[torsten . reinhard]

Hi, 

actually we have a file-based Repository, so for that I have the following 
 section in my settings.xml:


  GDCAMS-2.5-Main - mirror of central repo1.maven.org/maven2
  GD proxy for central repository
  file:/V:/3L_Solutions/08. Entwicklungsprojekte/PDV 
CMS/40_Builds/Repositories/GDCAMS-2.5-Main
  central


Now, I want to use Archiva as Repository, so I need to modify the 
settings.xml to:


  archiva.default
  Archiva Internal Repository
  http://myserver:8080/archiva/repository/internal
  central


How can I support both environments? 
I need to support both, because for older branches I won't change the 
build environment, but for the newest ( Main\Latest) I will use Archiva.

I know about the -s option - is there a profile based solution, too?

Thanx, Torsten

Re: How to checkout the Project from cvs in Maven2.0.7 without using eclipse.

[Sowmya . R]

Welcome :)
I am also don't know which build is correct. I am using build 2.0.7 to build
jar and war. I don't have idea about web service.


On Fri, Mar 28, 2008 at 12:46 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:

>
> Thank you so much for your help.  I was working until very late last night
> and I was executing the command that you sent me at the wrong directory
> level! - so, now I have got the maven build checking the project out.
>
> I do have a question now, whats the correct maven model to build and ear
> that has a war and jar and a web service? - I'd be very grateful if I
> could
> get some pointers here!.
>
>
> Sowmya.R wrote:
> >
> > Hi,  I am also new user of this maven.
> >
> > I will tell you one simple step to do this.
> >
> > checkout the project from cvs using eclipse.With in the project your
> going
> > to get pom.xml.
> > using that pom.xml just replace the values in SCM your having in
> username
> > and password (what I have sent earlier) .
> >  You can use that pom.xml itself and give the  with in
> > build
> > to checkout folder  and run command : mvn scm:checkout
> >
> >  In my project I am using maven to checkout dynamically
> > different projects.So I am giving branch name in command line.
> >
> > In your case may be or  tags are
> > missing.You have to give the proper values to variables in the command
> i.e
> > .
> > username ,password and branch name.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Fri, Mar 28, 2008 at 2:15 AM, [EMAIL PROTECTED] <
> > [EMAIL PROTECTED]> wrote:
> >
> >>
> >> Hi Sowmya.R
> >>
> >> Thanks so much for your reply.  I have tried what the code that you
> sent
> >> me
> >> but I get an error.  Below is my pom.xml...
> >>
> >> 
> >> http://maven.apache.org/POM/4.0.0";
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> >> http://maven.apache.org/maven-v4_0_0.xsd";>
> >>   4.0.0
> >>  wosi
> >>  wosi
> >>  pom
> >>  1.0
> >>  wosi
> >>  http://maven.apache.org
> >>
> >>  
> >>
> >> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
> >> :/data/cvsroot/aspen-crm/${mybranch}
> >>
> >> 
> >> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
> >> :/data/cvsroot/aspen-crm/${mybranch}
> >>
> >> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
> >> :/data/cvsroot/aspen-crm/${mybranch}
> >>  
> >>
> >>  
> >>
> >>
> >>   
> >>org.apache.maven.plugins
> >>maven-project-info-reports-plugin
> >>
> >>  
> >>
> >>  dependencies
> >>  index
> >>  project-team
> >>  dependency-convergence
> >>  
> >>  
> >>  
> >>  license
> >>  summary
> >>  scm
> >>
> >>  
> >>  
> >>  
> >>
> >> 
> >>
> >>  
> >>
> >>  
> >>
> >>  junit
> >>  junit
> >>  3.8.1
> >>  test
> >>
> >>  
> >>  
> >>wosi-domain
> >>wosi-integration
> >>wosi-services
> >>wosi-utils
> >>wosi-web
> >>  
> >> 
> >>
> >> ..and I am using the command specified in your email but I am
> getting
> >> the following error
> >>
> >> [INFO] Scanning for projects...
> >> [INFO] Searching repository for plugin with prefix: 'scm'.
> >> [INFO]
> >>
> --
> >> [INFO] Building Maven Default Project
> >> [INFO]task-segment: [scm:checkout] (aggregator-style)
> >> [INFO]
> >>
> --
> >> [INFO] [scm:checkout]
> >> [INFO]
> >>
> 
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >>
> 
> >> [INFO] Cannot run checkout command :
> >>
> >> Embedded error: Can't load the scm provider.
> >> You need to define a connectionUrl parameter
> >> [INFO]
> >>
> 
> >> [INFO] For more information, run Maven with the -e switch
> >> [INFO]
> >>
> 
> >> [INFO] Total time: 4 seconds
> >> [INFO] Finished at: Thu Mar 27 20:41:41 GMT 2008
> >> [INFO] Final Memory: 5M/10M
> >> [INFO]
> >>
> 
> >>
> >>
> >> .I would be very grateful if you could give me some pointers
> here...
> >>
> >> Thanks in advance!.
> >>
> >>
> >> Sowmya.R wrote:
> >> >
> >> > Hi,
> >> > To checkout the project you have to include scm tag
> >> >
> >> >  
> >> > scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
> >> > ://folder/${mybranch}
> >> > 
> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
> >> > ://folder/${mybranch}
> >> > scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
> >> > ://folder/${mybranch}
> >> >   
> >> >
> >> > give the respective f

Re: Third Party Jar

[Cosmin Marginean]

It seems that this goes deeper. What I actually need to do is create a Maven
plugin that performs an XSL transformation using Saxon 9. I unpacked the
Saxon 9 jar and added the classes to my plugin jar to make sure the
transformer is loaded. However, it seems that the transformer won't get
loaded, even when I run Maven with
-
Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
Some people seem to have worked around this by specifying the Saxon
dependency in the client pom.xml but this doesn't seem to work if I make the
transformation call from the plugin Jar. I even set the property manually in
the plugin:
TransformerFactory factory = TransformerFactory.newInstance();
But without any luck. The transformer will not be found

Thanks in advance

On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]>
wrote:

> Hello guys,
>
> Sorry to bother you with such issues, but I've googling my brains out with
> this without any relevant results.
> I have a question regarding bundling a 3rd party jar in a Maven Plugin. I
> am a bit new to Maven and Maven plugins.
> I tried bundling it in the plugin jar and adding it to the Class-Path
> attribute of MANIFEST.MF, but it seems to be ignored when using the
> plugin.
> Another question would be: assuming that somehow this 3rd party jar will
> make it into a public repository, what is the proper way to configure the
> dependency to make sure that the client (plugin user) will download and load
> this jar correctly without having to configure 3rd third party dependency in
> the pom.xml?
>
> Many thanks in advance
>
> --
> Cosmin Marginean




-- 
Cosmin Marginean

Re: jboss data-source not included in jboss-app.xml

[elaroche]

thanks mate, later is better than never :handshake:

Ernesto Salgado wrote:
> 
> This response arrives a bit late :wistle:, i know ... but here is the
> solution.
> 
> The problem is that the latest release of maven-ear-plugin at the moment
> is 2.3.1, and this version don't implement this feature yet!!!
> 
> data-sources tag is considered since version 2.3.2, and actually
> maven-ear-plugin is in 2.3.2-SNAPSHOT version.
> 
> You can download the source code of the plugin from Apache's SVN, package
> and install the SNAPSHOT version on your local repository.
> 
> Best regards.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/jboss-data-source-not-included-in-jboss-app.xml-tp15061842s177p16347854.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 checkout the Project from cvs in Maven2.0.7 without using eclipse.

[[EMAIL PROTECTED]]

Thank you so much for your help.  I was working until very late last night
and I was executing the command that you sent me at the wrong directory
level! - so, now I have got the maven build checking the project out.  

I do have a question now, whats the correct maven model to build and ear
that has a war and jar and a web service? - I'd be very grateful if I could
get some pointers here!.


Sowmya.R wrote:
> 
> Hi,  I am also new user of this maven.
> 
> I will tell you one simple step to do this.
> 
> checkout the project from cvs using eclipse.With in the project your going
> to get pom.xml.
> using that pom.xml just replace the values in SCM your having in username
> and password (what I have sent earlier) .
>  You can use that pom.xml itself and give the  with in
> build
> to checkout folder  and run command : mvn scm:checkout
> 
>  In my project I am using maven to checkout dynamically
> different projects.So I am giving branch name in command line.
> 
> In your case may be or  tags are
> missing.You have to give the proper values to variables in the command i.e
> .
> username ,password and branch name.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Fri, Mar 28, 2008 at 2:15 AM, [EMAIL PROTECTED] <
> [EMAIL PROTECTED]> wrote:
> 
>>
>> Hi Sowmya.R
>>
>> Thanks so much for your reply.  I have tried what the code that you sent
>> me
>> but I get an error.  Below is my pom.xml...
>>
>> 
>> http://maven.apache.org/POM/4.0.0";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>   4.0.0
>>  wosi
>>  wosi
>>  pom
>>  1.0
>>  wosi
>>  http://maven.apache.org
>>
>>  
>>
>> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
>> :/data/cvsroot/aspen-crm/${mybranch}
>>
>> 
>> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
>> :/data/cvsroot/aspen-crm/${mybranch}
>>
>> scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
>> :/data/cvsroot/aspen-crm/${mybranch}
>>  
>>
>>  
>>
>>
>>   
>>org.apache.maven.plugins
>>maven-project-info-reports-plugin
>>
>>  
>>
>>  dependencies
>>  index
>>  project-team
>>  dependency-convergence
>>  
>>  
>>  
>>  license
>>  summary
>>  scm
>>
>>  
>>  
>>  
>>
>> 
>>
>>  
>>
>>  
>>
>>  junit
>>  junit
>>  3.8.1
>>  test
>>
>>  
>>  
>>wosi-domain
>>wosi-integration
>>wosi-services
>>wosi-utils
>>wosi-web
>>  
>> 
>>
>> ..and I am using the command specified in your email but I am getting
>> the following error
>>
>> [INFO] Scanning for projects...
>> [INFO] Searching repository for plugin with prefix: 'scm'.
>> [INFO]
>> --
>> [INFO] Building Maven Default Project
>> [INFO]task-segment: [scm:checkout] (aggregator-style)
>> [INFO]
>> --
>> [INFO] [scm:checkout]
>> [INFO]
>> 
>> [ERROR] BUILD ERROR
>> [INFO]
>> 
>> [INFO] Cannot run checkout command :
>>
>> Embedded error: Can't load the scm provider.
>> You need to define a connectionUrl parameter
>> [INFO]
>> 
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> 
>> [INFO] Total time: 4 seconds
>> [INFO] Finished at: Thu Mar 27 20:41:41 GMT 2008
>> [INFO] Final Memory: 5M/10M
>> [INFO]
>> 
>>
>>
>> .I would be very grateful if you could give me some pointers here...
>>
>> Thanks in advance!.
>>
>>
>> Sowmya.R wrote:
>> >
>> > Hi,
>> > To checkout the project you have to include scm tag
>> >
>> >  
>> > scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
>> > ://folder/${mybranch}
>> > scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
>> > ://folder/${mybranch}
>> > scm:cvs:pserver:${myname}:[EMAIL PROTECTED]
>> > ://folder/${mybranch}
>> >   
>> >
>> > give the respective folder information ti checkout.
>> >
>> > 
>> > org.apache.maven.plugins
>> > maven-project-info-reports-plugin
>> > 
>> >   
>> > 
>> >   dependencies
>> >   index
>> >   project-team
>> >   dependency-convergence
>> >   
>> >   
>> >   
>> >   license
>> >   summary
>> >   scm
>> > 
>> >   
>> >   
>> >   
>> > include this plugin
>> >
>> > run the maven using following command.

Third Party Jar

[Cosmin Marginean]

Hello guys,

Sorry to bother you with such issues, but I've googling my brains out with
this without any relevant results.
I have a question regarding bundling a 3rd party jar in a Maven Plugin. I am
a bit new to Maven and Maven plugins.
I tried bundling it in the plugin jar and adding it to the Class-Path
attribute of MANIFEST.MF, but it seems to be ignored when using the plugin.
Another question would be: assuming that somehow this 3rd party jar will
make it into a public repository, what is the proper way to configure the
dependency to make sure that the client (plugin user) will download and load
this jar correctly without having to configure 3rd third party dependency in
the pom.xml?

Many thanks in advance

-- 
Cosmin Marginean