[ANN] Maven Changes Plugin 1.7 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven Changes Plugin 1.7 release! 

http://maven.apache.org/maven-1.x/plugins/changes/


===

Changes in this version include:

  New Features:

o New property maven.changes.outputencoding. 

  Fixed bugs:

o changes:release-version removes spaces after closing tags. Fixes 
  MPCHANGES-31. 
o The encoding of the changes.xml file is not preserved after doing 
  release-version. Fixes MPCHANGES-32. 
o Missing changes.xml makes report fail. Fixes MPCHANGES-30. 
o Add icons used by this plugin. This must be independent of the xdoc plugin. 
  Fixes MPCHANGES-29. 

  Changes:

o It now requires Maven 1.1. 
o Update dom4j dependency to match the one in maven 1.1 core. 
o Replace the deprecated xmlParserAPIs by xml-apis 1.3.03. Fixes MAVEN-1753. 
o Upgrade to commons-io 1.2.  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-changes-plugin
  -Dversion=1.7

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-changes-plugin-1.7.jar
 

Have fun!
-The Maven Changes Plugin development team

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

Re: ftp-wagon : Authentication failed

[Jeff Mutonho]

Hi Guys

Just wondering if anyone got some ideas around this?I've playing around with
it but to no avail


Jeff  Mutonho

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

[ANN] Maven Clover Plugin 1.11.1 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven Clover Plugin 1.11.1 release! 

http://maven.apache.org/maven-1.x/plugins/clover/

The Clover plugin allows measuring test coverage using Clover 
(http://www.cenqua.com/clover). 

===

Changes in this version include:

  Fixed bugs:

o clover:merge should use maven.multiproject.basedir. Fixes MPCLOVER-57. 

  Changes:

o Upgrade to Clover 1.3.13. Fixes MPCLOVER-56.  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-clover-plugin
  -Dversion=1.11.1

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-clover-plugin-1.11.1.jar
 

Have fun!
-The Maven Clover Plugin development team

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

[ANN] Maven Genapp Plugin 2.3.1 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven Genapp Plugin 2.3.1 release! 

http://maven.apache.org/maven-1.x/plugins/genapp/

A collection of example projects showing how to use maven in different 
situations 

===

Changes in this version include:

  Fixed bugs:

o Problem when maven.genapp.repackage.dir is empty. Fixes MPGENAPP-26. 
o Generated poms contain deprecated id elements. Fixes MPGENAPP-27. 

  Changes:

o Update dependencies to unify them between plugins. The following 
  dependencies are updated : commons-jelly-tags-interaction v1.0 to v1.1  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-genapp-plugin
  -Dversion=2.3.1

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-genapp-plugin-2.3.1.jar
 

Have fun!
-The Maven Genapp Plugin development team

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

[ANN] Maven Java Plugin 1.6.1 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven Java Plugin 1.6.1 release! 

http://maven.apache.org/maven-1.x/plugins/java/


===

Changes in this version include:

  Fixed bugs:

o Java report fails build if no source files present. Fixes MPJAVA-45.  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-java-plugin
  -Dversion=1.6.1

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-java-plugin-1.6.1.jar
 

Have fun!
-The Maven Java Plugin development team

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

[ANN] Maven JIRA Plugin 1.3.1 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven JIRA Plugin 1.3.1 release! 

http://maven.apache.org/maven-1.x/plugins/jira/

This plugin downloads issues from Jira and creates a report. 

===

Changes in this version include:

  Fixed bugs:

o If a report isn't generated the plugin fails trying to replace entities in 
  a not existing file. 

  Changes:

o Update jelly dependency to match the ones in maven 1.1 core. 
o Upgrade to log4j 1.2.13. Fixes MAVEN-1759.  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-jira-plugin
  -Dversion=1.3.1

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-jira-plugin-1.3.1.jar
 

Have fun!
-The Maven JIRA Plugin development team

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

[ANN] Maven POM Plugin 1.5.1 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven POM Plugin 1.5.1 release! 

http://maven.apache.org/maven-1.x/plugins/pom/

Basic validation and updating mechanisms for your Project Object Model. 

===

Changes in this version include:

  Fixed bugs:

o Fix schema for pom:validate, the id element is deprecated and replaced by 
  groupId/artifactId. Fixes MPPOM-6. 

  Changes:

o Update dom4j dependency to match the ones in maven 1.1 core.  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-pom-plugin
  -Dversion=1.5.1

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-pom-plugin-1.5.1.jar
 

Have fun!
-The Maven POM Plugin development team

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

[ANN] Maven Simian Plugin 1.6.1 for Maven 1.x released

[Lukas Theussl]

We are pleased to announce the Maven Simian Plugin 1.6.1 release! 

http://maven.apache.org/maven-1.x/plugins/simian/

Simian Plugin for Maven 

===

Changes in this version include:

  Fixed bugs:

o plugin:deregister does not work. Fixes MPSIMIAN-16. 

  Changes:

o Update jelly dependency to match the ones in maven 1.1 core.  

===


To automatically install the plugin, type the following on a single line:

maven plugin:download
  
-Dmaven.repo.remote=http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
  -DgroupId=maven
  -DartifactId=maven-simian-plugin
  -Dversion=1.6.1

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-simian-plugin-1.6.1.jar
 

Have fun!
-The Maven Simian Plugin development team

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

Re: Dowloading dependencies

[dawn.angelito]

Hi Saminda,

You may refer to the following link:
http://people.apache.org/~epunzalan/maven-assembly-plugin/. This doc however
isn't released yet.

Hope this helps!

Dawn


Saminda Abeyruwan-3 wrote:
> 
> Hi all,
> 
> I'm in the process of migrating from Maven1 to Maven2. I've being faced
> the
> following problem.
> 
> I have a requirement to download all the dependencies, In Maven1 i just
> used,
> 
> 
> 
> How do i do the above with Maven2. Is there a built in plugging for this.
> 
> Please do help.
> 
> 
> Thank you,
> 
> Saminda
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Dowloading-dependencies-tf2537384s177.html#a7070546
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: Custom Manifest file

[jiangshachina]

But I'm failed with the action.
I have an simple application project, and put MANIFEST.MF file into
directory
src/main/resources/META-INF
the file has an entry "Main-Class"

But Maven don't add the manifest automatically. I have to do following,



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




src/main/resources/META-INF/MANIFEST.MF







a cup of Java, cheers!
Sha Jiang


Paul Li-2 wrote:
> 
> or you could just add the META-INF/MANIFEST.MF into your resources
> directory ;-)
> 
> maven will automatically package it
> 
> A bit lazy i know.
> 
> Paul
> 
> On 4/12/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
>> Give this a try...
>>
>> 
>>  
>>   
>> org.apache.maven.plugins
>> maven-jar-plugin
>> 
>>   
>> src/main/resources/META-INF/MANIFEST.MF> manifestFile>
>>
>> Wayne
>>
>> On 4/11/06, Karthik Manimaran <[EMAIL PROTECTED]> wrote:
>> > Hi,
>> >
>> > How can I include a custom manifest file for a jar file and a WAR file?
>> >
>> > Thanks and regards,
>> > Karthik.
>> >
>> >
>>
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Custom-Manifest-file-tf1435329s177.html#a7070551
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: Migrating maven repo to a new machine

[Philippe Faes]

Please direct this question to the maven users list, not the continuum
users list.

kind regards

Philippe

On Thu, 2006-10-26 at 13:01 -0700, Prashanth Krishnamurthy wrote:
> Hi,
> 
> We are planning to move the maven repository to a new
> build machine. Is there a recommended process/steps ?
> (How to,...etc) Please advise.
> 
> (This maven repository is used by 2-3 different
> project teams and is very imp for a smooth migration.)
> 
> thanks
> --Prashanth
> 
> 
> 
> __
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 

Re: a help option like ant -projecthelp

[Craig McClanahan]

On 10/29/06, 向秦贤 <[EMAIL PROTECTED]> wrote:


Hi,

Thanks hint. Althrough I'm a newbie to maven, I'd to insist on this help
option, just like maven scanning.
Supposed that a man get a project code, his first work is just to build,
and build what, can build what, he thinks, but maven cannot answer.
Isn't it?



Qinxian, I fear you might have missed the most important part of Wendy's
response to your question:


For the most part, the 'goals' are the lifecycle phases,
and they are the same for every project.


In other words, once you learn Maven, you will *not* need to try to
understand the individual targets of the build script of some particular
project ... it will be just like every other Maven based project.  Learn one
of them, and you've learned the fundamental structure of all of them.

Maven's philosophy about building software is very different from Ant's.  To
become comfortable with it, you have to learn to accept the fact that Maven
is very much about enforcing common standards.  You actually can do a lot of
"nonstandard" things with Maven, but it is so much extra work that you (as a
developer of a project using Maven for builds) are *much* better off going
with the standard conventions that Maven encourages.

If you are simply trying to build a project that has a build infrastructure
based on Maven, then you are a *huge* beneficiary of this.  Simply do the
following:

* Install Maven itself per the instructions on the website.

* Check out or download the sources for the project you want to build.

* Change your directory to the top level directory of that project

* Execute the command "mvn clean install"

* And everything should just work.  No fussing with downloading
 your own dependencies.  No need to edit "build.properties" files.

Personally, I was a long time holdout for using Ant based build
environments.  But, if you look at the current build infrastructure for the
projects I care about (Shale, MyFaces, Struts, (eventually) Jakarta
Commons), you'll see a definite migration towards using Maven build
environments.  Why?  Because it is better -- for both the project developers
*and* the users who want to build the sources of those projects themselves.

So, what should *you* do?  The first thing is to change your question.
Instead of asking "how does the build process for project XYZ work?", simply
ask the question "how does the build process for any Maven-based project
work?"  Answer that question once, and you will instantly understand the
build environment for essentially all Maven based projects.


Regards,


Qinxian



Craig McClanahan

Re: SV: Continuum Startup error even though JAVA_HOME is set up

[Emmanuel Venisse]

Continuum doesn't use ANT_HOME and M2_HOME but use ant and mvn directly from 
PATH

Emmanuel

datech a écrit :

I am still strugling to get it run.
Thanks a lot for your suggestions. Will try what you have suggested and see
if I can through it.

Thanks


Naess, Ronny wrote:

We run Continuum on a unix server and have explicit added JAVA_HOME and
added maven and ant into PATH in run.sh.

On a Windows box it should probably be enough just to have JAVA_HOME,
ANT_HOME (if needed) and M2_HOME configured as environment variables.
You must ofcourse have %ANT_HOME%\bin and %M2_HOME%\bin in %PATH%
aswell. Test in shell by typing ant or mvn to verify. I guess you know
this already and that you have this settings configured and that this
might not be your problem?

-Ronny 


-Opprinnelig melding-
Fra: datech [mailto:[EMAIL PROTECTED] 
Sendt: 26. oktober 2006 22:35

Til: continuum-users@maven.apache.org
Emne: Re: Continuum Startup error even though JAVA_HOME is set up


Does that mean, I will need to modify the run.bat (for Windows NT) to
include Maven Home and Ant Home?
But I don't see it referring to Maven home and Ant Home in the bat file.
I still haven't solved the problem. Please help with more hints.

Thanks



Naess, Ronny wrote:

I had simulare problems on Solaris.
I ended up specifying JAVA_HOME and M2_HOME and updating PATH with 
M2_HOME\bin inside run.sh As I now JAVA_HOME must exist and maven/ant 
must exist in path when running continuum. For me it was not enough to

specify them in user environment

-Ronny

-Opprinnelig melding-
Fra: datech [mailto:[EMAIL PROTECTED]
Sendt: 25. oktober 2006 02:17
Til: continuum-users@maven.apache.org
Emne: Continuum Startup error even though JAVA_HOME is set up


I did find this problem in forums but the resolution specified didn't 
work for me. I do have JAVA_HOME set up in my system and also I tried 
modifying the wrapper.conf to specify the absolute path to my 
JAVA_HOME instead of it using %JAVA_HOME%, but that didn't work too.


I am getting  this error while trying to start up Continuum from 
Win32/run.bat script

| Critical error: wait for JVM process failed
Press any key to continue . . .


Please suggest what else could I change to make it work.


--
View this message in context:
http://www.nabble.com/Continuum-Startup-error-even-though-JAVA_HOME-is
-s
et-up-tf2504948.html#a6984052
Sent from the Continuum - Users mailing list archive at Nabble.com.







--
View this message in context:
http://www.nabble.com/Continuum-Startup-error-even-though-JAVA_HOME-is-s
et-up-tf2504948.html#a7019334
Sent from the Continuum - Users mailing list archive at Nabble.com.


!DSPAM:45411c0b56669724523251!

Re: Debug project?

[Max Cooper]

On Sun, 2006-10-29 at 22:18 -0800, jiangshachina wrote:
> Hi Max,
> > I suspect that this is what was really happening in your previous setup
> > anyway, and that the Eclipse WTP plugin just took care of the details
> > for you.
> Really, I always don't care the detail WTP plugin does.
> But in my memory, it's needn't set any extra statements into
> run.sh/run.bat(JBoss) for (local) debugging, when I use plugins(Eclipse WTP,
> MyEclipse) .
> 
My point was just that WTP almost certainly runs JBoss with debugging
on, and sets up the Eclipse debug session for you, without requiring you
to be aware of the details.

There is more than one way to turn debugging on in JBoss, without
editing run.bat. On Windows, setting debug options in the JAVA_OPTS
environment variable before calling run.bat would turn debugging on. Or
you could ignore run.bat completely and use your own script to run
JBoss, setting whatever options you want. Maybe WTP even starts JBoss in
the same process as Eclipse (doubtful, but possible), I don't know. 

My team doesn't actually edit JBoss's run.bat to turn debugging on. We
use a heavily customized version of jboss-maven-plugin, which has it's
own run scripts. We modified the script to optionally set debug options
in JAVA_OPTS, before the script calls the standard JBoss run.bat script.

-Max

> a cup of Java, cheers!
> Sha Jiang
> 
> 
> Max Cooper wrote:
> > 
> > To make the JBoss JVM listen for debugger, you set some params in the 
> > run.bat script (or run.sh/run.conf on *nix). There should be a section 
> > already in the run script to turn debugging on -- look for "JPDA 
> > options". You just uncomment the lines to enable remote debugging.
> > 
> > Note that by default it sets "suspend=y", which will cause the JVM to 
> > wait until you connect the debugger before it does anything (like start 
> > the server). This is useful if you need to debug things at startup, but 
> > I normally set "suspend=n", so the server will start normally, and I can 
> > just connect and disconnect the debugger whenever I want. You probably 
> > want to change this to "suspend=n".
> > 
> > Note what the port number is (default is 8787) -- you will need to tell 
> > Eclipse the port number when you setup the debug session.
> > 
> > No other files are affected.
> > 
> > Debugging (JPDA) is a standard feature of Java, and has nothing to do 
> > with Maven.
> > 
> > In Eclipse, you setup a debug session, and tell eclipse which server and 
> > port number the JBoss JVM is listening to (e.g. localhost:8787).
> > 
> > I suspect that this is what was really happening in your previous setup 
> > anyway, and that the Eclipse WTP plugin just took care of the details 
> > for you.
> > 
> > -Max
> > 
> > jiangshachina wrote:
> >> Hi Max,
> >> I think remote debug local server(I'm using JBoss) would be OK.
> >> But it there alternative approach for local debugging?
> >> 
> >> If use remote debugging, shall I re-config some parameters in web.xml or
> >> other conf files?
> >> Thanks!
> >> 
> >> a cup of Java, cheers!
> >> Sha Jiang
> >> 
> >> 
> >> Max Cooper wrote:
> >>> It sounds like your primary requirement is "how can I debug my webapp".
> >>>
> >>> My project uses Maven to build and deploy a webapp to a server running
> >>> on the local machine, and then we connect the Eclipse debugger to the
> >>> local server via the standard Java "remote" debugging interface.
> >>>
> >>> -Max
> >>>
> >>> On Sun, 2006-10-29 at 00:28 -0700, jiangshachina wrote:
>  Hello,
>  Currently, I use an Eclipse plugin(WTP) to create a Web application.
>  And I use the plugin to export(deploy) the Web application to an
>  Web/Application Server(JBoss)'s deploy directory.
>  Then I can debug the application when the server is running.
> 
>  The function is provided by the plugin.
>  If the project isn't created by the plugin, the plugin cannot deploy
>  the
>  app(may since directory layout).
>  And I cannot debug the app with server(it's a serious problem).
> 
>  Now I want to use Maven and it's standard directory structure.
>  But how Maven to fulfil the requirement?
> 
>  a cup of Java, cheers!
>  Sha Jiang
> >>>
> >>> -
> >>> 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: Maven 1.1 RC1 SNAPSHOT needs testers

[Arnaud HERITIER]

Hi,

  We just pushed a new snapshot here :
http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061029/
  Since the last one mentionned below :
  - we fixed a problem on the encoding of the pom when maven installs a
plugin. If you had some special character in the pom (accents, ...), maven
wasn't able to read the pom, that it previously generated.
  - we improved the reporting of errors during the build.  Now you should
have by default the stack of errors.
  - this snapshot bundles last released plugins : maven-simian-plugin v
1.6.1, maven-pom-plugin v 1.5.1, maven-jira-plugin v 1.3.1,
maven-java-plugin v 1.6.1, maven-genapp-plugin v 2.3.1, maven-clover-plugin
v 1.11.1, maven-changes-plugin v. 1.7
  - it contains the snapshots of maven-nsis-plugin v 2.1 and
maven-pdf-plugin v 2.5.1
  - the windows installer was slightly modified to put MAVEN_HOME in the
system environment variables if the user has admin rights

Cheers

Arnaud



Arnaud HERITIER wrote:
> 
> Hi everybody,
> 
>   We just deployed a new SNAPSHOT of maven 1.1 RC1 [1].   This version
> incorporates 2 important changes and we would like to have your feedback :
> 
>-   MAVEN-1755 : We fixed the last main backward incompability with
>maven 1.0.x, this new version supports XML entities in the POM.
>-   MAVEN-1789 : The default repository is now
> http://repo1.maven.org/maven/
> 
> 
>   ( These two issues aren't yet closed because we have to update the
> documentation and we are waiting for your feedback ;-) )
> 
>   Be careful, that to use this snapshot version, you'll certainly have to
> define the following set of remote repositories to download dependencies.
> maven.repo.remote =
> http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
> 
>   These version includes severals plugins [4] updated since the beta 3,
> and
> particularly the fix for MPARTIFACT-71 to avoid the error about the
> rejected
> key of the host if you use the scp or the sftp protocols to deploy your
> artifacts.
> 
>   The more feedbacks we'll have, the more stable will be the RC1 !!
> 
>   Thanks for your help...
> 
>   Cheers,
> 
> The maven team.
> 
> [1]
> http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/
> [2] http://jira.codehaus.org/browse/MAVEN-1755
> [3] http://jira.codehaus.org/browse/MAVEN-1789
> [4] http://jira.codehaus.org/browse/MAVEN-1769
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-1.1-RC1-SNAPSHOT-needs-testers-tf2413198s177.html#a7071132
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: Custom Manifest file

[jiangshachina]

I find another problem.
If the project is Web application, then META-INF/MANIFEST.MF will be
inserted into classes directory.
Obviously, Maven thinks META-INF/MANIFEST.MF is resource since it's in
src/main/resources directory(standard resource path).

How can I cancel the problem?

a cup of Java, cheers!
Sha Jiang


jiangshachina wrote:
> 
> But I'm failed with the action.
> I have an simple application project, and put MANIFEST.MF file into
> directory
> src/main/resources/META-INF
> the file has an entry "Main-Class"
> 
> But Maven don't add the manifest automatically. I have to do following,
> 
>   
>   
>   org.apache.maven.plugins
>   maven-jar-plugin
>   
>   
>   
>   
> src/main/resources/META-INF/MANIFEST.MF
>   
>   
>   
>   
>   
> 
> 
> a cup of Java, cheers!
> Sha Jiang
> 
> 
> Paul Li-2 wrote:
>> 
>> or you could just add the META-INF/MANIFEST.MF into your resources
>> directory ;-)
>> 
>> maven will automatically package it
>> 
>> A bit lazy i know.
>> 
>> Paul
>> 
>> On 4/12/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
>>> Give this a try...
>>>
>>> 
>>>  
>>>   
>>> org.apache.maven.plugins
>>> maven-jar-plugin
>>> 
>>>   
>>> src/main/resources/META-INF/MANIFEST.MF>> manifestFile>
>>>
>>> Wayne
>>>
>>> On 4/11/06, Karthik Manimaran <[EMAIL PROTECTED]> wrote:
>>> > Hi,
>>> >
>>> > How can I include a custom manifest file for a jar file and a WAR
>>> file?
>>> >
>>> > Thanks and regards,
>>> > Karthik.
>>> >
>>> >
>>>
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Custom-Manifest-file-tf1435329s177.html#a7071194
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: Custom Manifest file

[jiangshachina]

Of course, I can locate MANIFEST.MF to another directory.
I just be curious of why application project have not the trouble.
And I cannot use standard directory structure.

a cup of Java, cheers!
Sha Jiang



jiangshachina wrote:
> 
> I find another problem.
> If the project is Web application, then META-INF/MANIFEST.MF will be
> inserted into classes directory.
> Obviously, Maven thinks META-INF/MANIFEST.MF is resource since it's in
> src/main/resources directory(standard resource path).
> 
> How can I cancel the problem?
> 
> a cup of Java, cheers!
> Sha Jiang
> 
> 
> jiangshachina wrote:
>> 
>> But I'm failed with the action.
>> I have an simple application project, and put MANIFEST.MF file into
>> directory
>> src/main/resources/META-INF
>> the file has an entry "Main-Class"
>> 
>> But Maven don't add the manifest automatically. I have to do following,
>> 
>>  
>>  
>>  org.apache.maven.plugins
>>  maven-jar-plugin
>>  
>>  
>>  
>>  
>> src/main/resources/META-INF/MANIFEST.MF
>>  
>>  
>>  
>>  
>>  
>> 
>> 
>> a cup of Java, cheers!
>> Sha Jiang
>> 
>> 
>> Paul Li-2 wrote:
>>> 
>>> or you could just add the META-INF/MANIFEST.MF into your resources
>>> directory ;-)
>>> 
>>> maven will automatically package it
>>> 
>>> A bit lazy i know.
>>> 
>>> Paul
>>> 
>>> On 4/12/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
 Give this a try...

 
  
   
 org.apache.maven.plugins
 maven-jar-plugin
 
   
 src/main/resources/META-INF/MANIFEST.MF>>> manifestFile>

 Wayne

 On 4/11/06, Karthik Manimaran <[EMAIL PROTECTED]> wrote:
 > Hi,
 >
 > How can I include a custom manifest file for a jar file and a WAR
 file?
 >
 > Thanks and regards,
 > Karthik.
 >
 >

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

-- 
View this message in context: 
http://www.nabble.com/Custom-Manifest-file-tf1435329s177.html#a7071364
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Using maven-antrun-plugin and taskdef

[Jeff Mutonho]

I've configured the maven-antrun-plugin as follows :


  maven-antrun-plugin
  
   
   pre-integration-test
   



   

   
  
  
   run
  
 

   


and added  ant-jmeter1-0.jar to my dependencies.However , when I run
'mvn install' I get the following build error :

[INFO] [site:attach-descriptor]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Error executing ant tasks

Embedded error: taskdef class org.programmerplanet.ant.taskdefs.jmeter.JMeterTas
k cannot be found
[INFO] 


Is it  correct to do a "taskdef" definition  the way I did?



Jeff  Mutonho

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Sync with Maven 1 repo

[Saminda Abeyruwan]

Hi All,

I want to sync the .maven  (Maven1 )repo with Maven2 build. This is because,
some of the projects we've using has Maven1 and the SNAPHSOT of them
uploaded  there locally. Is it possible to sync the .maven repo with Maven2
build. Is this possible. If not what are the alternative ways ?

Thank you

Saminda

Re: configuring logging

[Emmanuel Venisse]

You can configure it in wrapper.conf 
(http://wrapper.tanukisoftware.org/doc/english/prop-logfile.html)

I don't think jws delete older log files

Emmanuel

Rajiv Kumar Poddar a écrit :

Hi,
Continuum generates a single log file wrapper.log and keeps appending all
the logs to it. Can we configure it so that it generates the wrapper.log
file on per day basis? 
If this can be done, than can we also configure to delete older log files?
 
Thanks for your help.
 
Rajiv Poddar

problem with using my plugin

[Joachim Van der Auwera]

I am trying to write a custom plugin, but when I try to use it, I get 
the following exception :


[INFO] Internal error in the plugin manager executing goal 
'be.unid:Uni-d-maven-plugin:0.8-SNAPSHOT:generate': Error adding plugin 
dependency 'be.unid:Uni-d-generate:jar' into plugin manager: Cannot add 
jar resource: 
/home/joachim/.m2/repository/be/unid/Uni-d-generate/0.8-SNAPSHOT/Uni-d-generate-0.8-SNAPSHOT.jar 
(error discovering new components)

input contained no data

However, the jar file mentioned in the message exists at the given location.
I am using maven 2.0.4

Any ideas what if wrong or how I can fix/work around this?

Thanks for the help,
Joachim

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

Re: Codehaus repository needed even using released plugins only

[Syvalta]

Edwin Punzalan wrote:
> 
> That's correct, released plugins should only have released dependencies.
> 
> Please provide the stacktrace so we can see if what you say really 
> happened and which plugin breaks that.
> 

Unfortunately I can't currently reproduce that in my machine. Here's the
output from my colleague (without stack trace, I'll see if he's still seeing
the problem and provide the trace if possible). 

[INFO]

[INFO] Building parent project
[INFO]task-segment: [install]
[INFO]

Downloading:
http://dist.codehaus.org/org.mortbay.jetty/jars/servlet-api-2.5-6.0.0beta12.jar
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

Error transferring file
  org.mortbay.jetty:servlet-api-2.5:jar:6.0.0beta12

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  codehaus (http://dist.codehaus.org),
  apache.snapshots (http://svn.apache.org/maven-snapshot-repository),
  snapshots (http://snapshots.maven.codehaus.org/maven2)
Path to dependency: 
1) org.apache.maven.plugins:maven-site-plugin:maven-plugin:2.0-beta-5
2) org.mortbay.jetty:jetty:jar:6.0.0beta12
3) org.mortbay.jetty:servlet-api-2.5:jar:6.0.0beta12

Caused by I/O exception: Connection timed out: connect


So it seems that for some reason the artifact was tried to be downloaded
only from dist.codehaus. Unfortunately I'm not sure in what circumstances
this occurs.

Seems that Struts folks have seen similar behaviour with dependencies (see
the last line of the second comment):
https://issues.apache.org/struts/browse/STR-2952
-- 
View this message in context: 
http://www.nabble.com/Codehaus-repository-needed-even-using-released-plugins-only-tf2520820s177.html#a7073157
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Maven 2: How to test a new plugin

[James Walker]

Hi.

I've a library that I built under Maven 1.

It provides an ant task which does a bunch of code generation.

Under maven 1 I was able to test the ant task during the test goal by 
running the task in a pre-goal and ensuring the output was dumped 
somewhere that it was able to be found and used during the rest of the 
testing.


In fact as far as I can tell under Maven 2 I can not just run the ant 
task and have it generate to something like target/src/java, and have 
the compilation steps find that new source path.  This is ok because I 
figured I might as well add a Maven 2 plugin which provides the code 
generation functionality.


This led me to testing the new plugin and the question of "how?".

I want to be able to compile the plugin, use it to generate some source, 
then compile the source and run it through some tests.


Is this at all possible?  I get the impression it might not be - at this 
time it seems I have to have the plugin installed/available as maven 
starts up - otherwise it'll have a fit.


It almost seems I need another module which provides the plugin and to 
have compiled+installed that module first?


Any hints?

How are other people testing their plugins?

Thanks for any help,
James.

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

Re: Using maven-antrun-plugin and taskdef

[Marco Mistroni]

hello
you'd nee dto specify classpath somewhere...
here's a sample (i m using custom jboss xdoclet task)


 
 

 
 
   
   
   
   
   
   
   
   
   
   
   

   
   
   
   

   
   

hth
marco

On 10/30/06, Jeff Mutonho <[EMAIL PROTECTED]> wrote:


I've configured the maven-antrun-plugin as follows :

 
   maven-antrun-plugin
   

pre-integration-test

 
 
 

 

   
   
run
   
  
 



and added  ant-jmeter1-0.jar to my dependencies.However , when I run
'mvn install' I get the following build error :

[INFO] [site:attach-descriptor]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error executing ant tasks

Embedded error: taskdef class
org.programmerplanet.ant.taskdefs.jmeter.JMeterTas
k cannot be found
[INFO]



Is it  correct to do a "taskdef" definition  the way I did?



Jeff  Mutonho

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Hibernate mapping resource path in Maven

[Andy Buckley]

Hi,

I just started converting a Java project using Hibernate (www.hibernate.org) to
build with Maven rather than Ant. While I was able to get log4j logging working
again by placing my log4j.properties file in src/main/resources, and putting
hibernate.cfg.xml in the same place does result in it getting picked up by
Hibernate at runtime, I can't seem to get the mapping resource entries correct.

My directory structure is now

src/main
\ resources
|  \ hibernate.cfg.xml
|
\ java/cedar/hepdata/model
  \ Author.hbm.xml
  \ Axis.hbm.xml
  \ etc.

and in hibernate.cfg.xml, I've got mapping entries like this:



which result in errors like

Running cedar.hepdata.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec
Running cedar.hepdata.test.HDOMTest
Initial SessionFactory creation failed: org.hibernate.MappingNotFoundException:
resource: src/main/java/cedar/hepdata/model/Author.hbm.xml not found

I've also tried resource="/src/...", resource="../src/..." and a bunch of
others (even absolute paths, which are useless from a portability point of
view) and none seem to work. Any suggestions? I suspect that the
hibernate.cfg.xml file is getting copied into the target/{,test-}classes
directories and the *.hbm.xml files aren't: should the *.hbm.xml files also be
located in src/main/resources/ to make this work?

Please help!

Andy


PS. Sorry if this is a recurring question: The only mention on the mailing list
archives that I've seen about getting Hibernate working was using mappings like

but these seem to require Hibernate Annotations and I'm not (yet) using them.
The Hibernate doc/FAQ pages aren't much help either, since they only seem to be
referring to Maven 1.x.

-- 
Andy Buckley: CEDAR @ IPPP, Durham
Work: www.cedar.ac.uk
www.insectnation.org

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

Proxy at maven 2

[Michael Post]

Hello,

i want to run a maven-script (openJPA), but maven can not access to internet 
through our internal proxy.

I have create the file build.properties under C:\document and settings\post 
with the following content:

# Maven ${user.home}/build.properties
# General local settings - overrides
maven.proxy.host=[IP-Adress]
maven.proxy.port=8081 

As [IP-Adress] is inserted the real adress.

I am very be pleased if you can help me.

Thanks

Michael

Re: Proxy at maven 2

[Xavier Outhier]

Michael Post wrote:

Hello,

i want to run a maven-script (openJPA), but maven can not access to internet 
through our internal proxy.

I have create the file build.properties under C:\document and settings\post 
with the following content:

# Maven ${user.home}/build.properties
# General local settings - overrides
maven.proxy.host=[IP-Adress]
maven.proxy.port=8081 


As [IP-Adress] is inserted the real adress.

I am very be pleased if you can help me.

Thanks

Michael

The settings for maven (2) is an xml file at this location:
C:\Documents and Settings\\.m2\settings.xml

- <#> 

<
-   <#> 
 true
 http
 
 
 
 


[...]


Username and password can also be set depends on your config.

HTH,

Xavier.



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

Re: Hibernate mapping resource path in Maven

[Marco Mistroni]

Hello,
 yes you should make sure that your hibernate files end up in the resources
directory of your src/java

after that there isno need to put absolute path for your classes, you can
just puit

cedar/hepdata/Author.hbm.xml

and that should work..

hth
marco


On 10/30/06, Andy Buckley <[EMAIL PROTECTED]> wrote:


Hi,

I just started converting a Java project using Hibernate (
www.hibernate.org) to
build with Maven rather than Ant. While I was able to get log4j logging
working
again by placing my log4j.properties file in src/main/resources, and
putting
hibernate.cfg.xml in the same place does result in it getting picked up by
Hibernate at runtime, I can't seem to get the mapping resource entries
correct.

My directory structure is now

src/main
\ resources
|  \ hibernate.cfg.xml
|
\ java/cedar/hepdata/model
  \ Author.hbm.xml
  \ Axis.hbm.xml
  \ etc.

and in hibernate.cfg.xml, I've got mapping entries like this:



which result in errors like

Running cedar.hepdata.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec
Running cedar.hepdata.test.HDOMTest
Initial SessionFactory creation failed:
org.hibernate.MappingNotFoundException:
resource: src/main/java/cedar/hepdata/model/Author.hbm.xml not found

I've also tried resource="/src/...", resource="../src/..." and a bunch of
others (even absolute paths, which are useless from a portability point of
view) and none seem to work. Any suggestions? I suspect that the
hibernate.cfg.xml file is getting copied into the target/{,test-}classes
directories and the *.hbm.xml files aren't: should the *.hbm.xml files
also be
located in src/main/resources/ to make this work?

Please help!

Andy


PS. Sorry if this is a recurring question: The only mention on the mailing
list
archives that I've seen about getting Hibernate working was using mappings
like

but these seem to require Hibernate Annotations and I'm not (yet) using
them.
The Hibernate doc/FAQ pages aren't much help either, since they only seem
to be
referring to Maven 1.x.

--
Andy Buckley: CEDAR @ IPPP, Durham
Work: www.cedar.ac.uk
www.insectnation.org

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

HELP: Running site goal on a cutom packaging

[Prasad Kashyap]

I need some help with running the site goal on a custom packaging.

This is how the packaging is defined..
http://rifers.org/paste/show/2093

On running 'mvn site' on a pom with this packaging, I get

[DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
Lifecycle ID: site. Error: Component descriptor cannot be found in the
component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingintegration-test.
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingintegration-test.
   at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323)
   at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440)



In the above components.xml, I tried merging both the 
elements under the same  for the same . The
default execution of the pom failed. I had to separate the 
into separate  elements.

Can someone please guide me into the correct path here ?

Thanx
Prasad.


org.apache.maven.lifecycle.mapping.LifecycleMapping
integration-test
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping



default

org.apache.maven.plugins:maven-resources-plugin:testResources
org.apache.maven.plugins:maven-compiler-plugin:testCompile
org.apache.maven.plugins:maven-jar-plugin:jar
org.apache.maven.plugins:maven-surefire-plugin:test
org.apache.maven.plugins:maven-install-plugin:install
org.apache.maven.plugins:maven-deploy-plugin:deploy







org.apache.maven.lifecycle.mapping.LifecycleMapping
integration-test
org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping



   site
   
 pre-site
 site
 post-site
 site-deploy
   
   
 org.apache.maven.plugins:maven-site-plugin:site
 org.apache.maven.plugins:maven-site-plugin:deploy
   
 



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

Re: Hibernate mapping resource path in Maven

[Aleksei Valikov]

Hi.


I just started converting a Java project using Hibernate (www.hibernate.org) to
build with Maven rather than Ant. While I was able to get log4j logging working
again by placing my log4j.properties file in src/main/resources, and putting
hibernate.cfg.xml in the same place does result in it getting picked up by
Hibernate at runtime, I can't seem to get the mapping resource entries correct.

My directory structure is now

src/main
\ resources
|  \ hibernate.cfg.xml
|
\ java/cedar/hepdata/model
  \ Author.hbm.xml
  \ Axis.hbm.xml
  \ etc.


1. Put your HBM files into resources, not into java. You should have 
src/main/resource/cedar/hepdata/mode/Autor.hbm.xml etc.


2. Use



Bye.
/lexi

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

filtering web.xml

[Valerio Schiavoni]

hello everyone,
i know this has been discussed recently (also here:
http://www.nabble.com/War-plugin-and-filtering-webapp-files-t1617964.html) ,
but thevarious  solutions and hacks proposed haven't solved my issue :(

Consider this snippet of web.xml:

   contextConfigLocation
   
   classpath*:/acegi.xml
   classpath*:/springapp-servlet.xml
   classpath*:/datasource-populator.xml
   ${dbms.filter}
   


I'd like to change the value of the dbms.filter variable value depending on
a given profile.
So i have the following in my pom.xml:
//configuration for the maven-war-plugin


   ${basedir}/src/main/filters/webxml-filter.xml
   

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

${basedir}/src/main/webapp

**/*.xml

 
 




then, a profile :


   postgres
   
   
   dbms
   postgres
   
   
   
   classpath*:/springapp-pgdb.xml
   
   

so that when I issue : mvn clean -Ddbms=postgres i'm expecting the
web.xmlfile to be filled with the value
specified in the postgres profile. which actually is not happening.
the  element is there only because I read it fixes some current
issues, and it actually refers to an empty filter file.

any suggestion is very appreciated.
--
http://valerioschiavoni.blogspot.com
http://jroller.com/page/vschiavoni

Re: [m2] eclipse plugin - too many jar showing in package explorer

[Man-Chi Leung]

hi Daniel ,

thanks so much for your reply.
today, I also come across the some solution blogged by Matt Riable at 2004  :-D
http://raibledesigns.com/page/rd?anchor=eclipse_tips

~manchi

On 2006-10-17 04:13:43 +0800, Daniel Serodio <[EMAIL PROTECTED]> said:


Man-Chi Leung wrote:

hi,

after I did  "mvn eclipse:eclipse" and got the project imported to
eclipse

I found a very long list of jar showing in eclipse's Package Explorer.

however, not all the jars that i am actually programming for ,  i
believe , they are simply the dependencies of dependencies.

in eclipse plugin, how can I only include those dependencies that are
stated in pom.xml and add them in .classpath eclipse conf file ?

pls help
~manchi

Is the problem is the "clutter" in the Package Explorer, try adding a
"*.jar" filter to this view.

HTH,
Daniel Serodio





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

Assigning an existing Maven1 local repo to Maven2 local repo

[Saminda Abeyruwan]

Hi All,

I'm new to Maven2. Please aid me to rectify the following Maven1 to Maven2
migration problem.

We have projects written with Maven1 and when we build the projects (They
are SNAPSHOT), basically these snapshots uploaded to local .maven repo.

We have been in the process of converting all Maven1 projects to Maven2.
Until the conversion completed,  some converted Maven2  projects need to
refer  to some of the jars in Maven1 repo (.maven). Is it possible to say to
pom.xml to get the relevant jars from Maven1 repository. What are the
options available for me to get this working.

Please do help.

Thank you

Saminda

Re: java2iiop (Visibroker)

[Jim Bethancourt]

Dan,
Awesome!  Thanks so much.  I'd be happy to help where I can.
Jim

On 10/29/06, Dan Tran <[EMAIL PROTECTED]> wrote:

Jim, I just cookedup a set of maven wrappers for visibroker tools.
Please provide feedbacks, patches, docs if you find it it useful.

You will need to check out the source at mojo-sandbox

The site is at  http://mojo.codehaus.org/visibroker-maven-plugin/


-D


On 10/28/06, Jim Bethancourt <[EMAIL PROTECTED]> wrote:
>
> Hi Tim,
> I've been tinkering with migrating the build process for the place
> where I work from Ant to Maven 2 and noticed that you worked on a
> VisiBroker plugin for Maven 2 and had considered posting it.  Any
> chance you could consider posting it?  I know I could put it to use
> quickly and I'm sure plenty of other folks using VisiBroker would find
> it very useful too.
>
> Thanks,
> Jim
>
> On 6/27/06, TimHedger <[EMAIL PROTECTED]> wrote:
> >
> > Thanks Dan - got most of it working now.
> > --
> > View this message in context:
> http://www.nabble.com/java2iiop-%28Visibroker%29-tf1846831.html#a5071927
> > Sent from the Maven - Users forum 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]
>
>




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

Maven 2 SCM ?

[Sebastien Brunot]

Hi,
 
does anybody know the URL of the maven 2 sources repository ? I can't
find it on the maven web site...
 
Thanks,
 
Sebastien

Re: filtering web.xml

[Valerio Schiavoni]

for sake of completeness, i also tried with maven-war-plugin version 2.0.1 .

here is the stacktrace:
[INFO] Failure

Embedded error: IOException parsing XML document from ServletContext
resource [/${dbms.filter}]; nested exception is
java.io.FileNotFoundException: Could not open ServletContext resource [/${
dbms.filter}]

i also tried putting this:
dbms.filter = classpath*:/springapp-pgdb.xml

in the webxml-filter.xml (that is the filter definition file), without any
luck.


On 10/30/06, Valerio Schiavoni <[EMAIL PROTECTED]> wrote:


hello everyone,
i know this has been discussed recently (also here: 
http://www.nabble.com/War-plugin-and-filtering-webapp-files-t1617964.html
) , but thevarious  solutions and hacks proposed haven't solved my issue
:(

Consider this snippet of web.xml:

contextConfigLocation

classpath*:/acegi.xml
classpath*:/springapp-servlet.xml
classpath*:/datasource-populator.xml
${dbms.filter}



I'd like to change the value of the dbms.filter variable value depending
on a given profile.
So i have the following in my pom.xml:
//configuration for the maven-war-plugin


${basedir}/src/main/filters/webxml-filter.xml


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


  
 true

${basedir}/src/main/webapp
 
 **/*.xml
 
  
  
 



then, a profile :


postgres


dbms
postgres



classpath*:/springapp-pgdb.xml



so that when I issue : mvn clean -Ddbms=postgres i'm expecting the web.xmlfile 
to be filled with the value
specified in the postgres profile. which actually is not happening.
the  element is there only because I read it fixes some current
issues, and it actually refers to an empty filter file.

any suggestion is very appreciated.
--
http://valerioschiavoni.blogspot.com
http://jroller.com/page/vschiavoni





--
http://valerioschiavoni.blogspot.com
http://jroller.com/page/vschiavoni

Version validation of "provided" dependencies

[Jonas Olsson]

Hi!

We're introducing Maven to our multi-artifact product build and we'de
really like to get full usage of the dependency mechanism. We've got
many shared libraries as "provided" dependencies which are also included
in the top level artifact to complete the assembly, but "normal" Maven
version validation does not include "provided" dependencies, so
out-of-the-box we don't keep feed-back on if all artifacts are OK with
the actual shared library versions we're including.
Is there a way (or plugin) to perform this "deeper" kind of version
validation or are we wrong in asking?

Thank you for input!

--
Jonas Olsson
System Designer
Cambio Healthcare Systems

Detta e-mail har blivit undersökt av http://www.virus112.se


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

mevenide vs. m2eclipse?

[Steinar Bang]

I'm currently using the m2eclipse plugin in eclipse 3.2, and it
works. 

But today I thought that it was a pity that it didn't have a POM
editor.  So I googled for "eclipse pom editor" and discovered
"mevenide". 
 http://mevenide.codehaus.org/mevenide-ui-eclipse/features.html
(which has a POM editor, in case you wondered)

So I'm wondering about the relationship between m2eclipse and
mevenide, eg. are they in conflict?  Are they complimentary?  What
advantages do one offer over the other?

Googling for "mevenide vs. m2eclipse" found me this
 http://www.onjava.com/pub/a/onjava/2006/03/29/maven-2-0.html?page=last
search for "mevenide" in that page for "Eclipse integration" and
you'll find an article saying mevenide only supports maven 1.x.

But this was in April.  Does anyone know if that's still the case?

The http://mevenide.codehaus.org/ says the NetBeans plugin has Maven 2
support, but since nonde of the other mentions it I'm assuming they
are still on Maven 1.x?

Thanx!


- Steinar


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

[maven 1.x][jnlp plugin 1.4.1] takes very long time to sign jars

[vincent . juge]

Hi,

I am using jnlp 1.4.1 plugin to generate my webstart client.

At step of signing jars, it takes very very long time (more than 1h30) to 
sign just a few number of jars.
The weird thing is that the cpu is nearly idle, an the memory is not full.

My question is : 
- Is it possible to be a bug  ? and / or
- Is it possible to add the ability to the plugin to pass the 
signing of jars ? In this case it would be possible to sign the jars 
separately.

Thanks for your answer;

regards.


This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

-

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.

Re: mevenide vs. m2eclipse?

[Milos Kleint]

yup. exactly as you assume.

the eclipse related code at mevenide only supports maven1. The only
maven2 related codebase we have currently is the netbeans module.

Milos

On 10/30/06, Steinar Bang <[EMAIL PROTECTED]> wrote:

I'm currently using the m2eclipse plugin in eclipse 3.2, and it
works.

But today I thought that it was a pity that it didn't have a POM
editor.  So I googled for "eclipse pom editor" and discovered
"mevenide".
 http://mevenide.codehaus.org/mevenide-ui-eclipse/features.html
(which has a POM editor, in case you wondered)

So I'm wondering about the relationship between m2eclipse and
mevenide, eg. are they in conflict?  Are they complimentary?  What
advantages do one offer over the other?

Googling for "mevenide vs. m2eclipse" found me this
 http://www.onjava.com/pub/a/onjava/2006/03/29/maven-2-0.html?page=last
search for "mevenide" in that page for "Eclipse integration" and
you'll find an article saying mevenide only supports maven 1.x.

But this was in April.  Does anyone know if that's still the case?

The http://mevenide.codehaus.org/ says the NetBeans plugin has Maven 2
support, but since nonde of the other mentions it I'm assuming they
are still on Maven 1.x?

Thanx!


- Steinar


-
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: Version validation of "provided" dependencies

[Tom Huybrechts]

Hi Jonas,

I'm not sure if this is what you're asking, but the dependencyManagement
section of the pom makes it a lot easier to ensure your versions stay in
sync between different projects. Just specify each dependencies' version
once in that section of the top-level POM...

Tom

On 10/30/06, Jonas Olsson <[EMAIL PROTECTED]> wrote:


Hi!

We're introducing Maven to our multi-artifact product build and we'de
really like to get full usage of the dependency mechanism. We've got
many shared libraries as "provided" dependencies which are also included
in the top level artifact to complete the assembly, but "normal" Maven
version validation does not include "provided" dependencies, so
out-of-the-box we don't keep feed-back on if all artifacts are OK with
the actual shared library versions we're including.
Is there a way (or plugin) to perform this "deeper" kind of version
validation or are we wrong in asking?

Thank you for input!

--
Jonas Olsson
System Designer
Cambio Healthcare Systems


Detta e-mail har blivit undersökt av http://www.virus112.se



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

SV: Version validation of "provided" dependencies

[Jonas Olsson]

I'll try to visualise the issue:


pom.xml (top level artifact, "the deliverable")
 |
 +- submodule A 1.0
 |   |
 |   +- shared 1.0 [provided]
 |
 +- submodule B 1.1
 |   |
 |   +- shared 1.1 [provided]
 |
 +- shared 1.0 [runtime]


I want a way for maven to tell me, when packaging the top level artifact, that 
submodule B is in conflict with the shared 1.0 we chose to include. Currently 
this is not done (provided dependencies are ignored, probably on the assumption 
that they are EXTERNALLY provided).

/jonas

-Ursprungligt meddelande-
Från: Tom Huybrechts [mailto:[EMAIL PROTECTED] 
Skickat: den 30 oktober 2006 16:18
Till: Maven Users List
Ämne: Re: Version validation of "provided" dependencies

Hi Jonas,

I'm not sure if this is what you're asking, but the dependencyManagement
section of the pom makes it a lot easier to ensure your versions stay in
sync between different projects. Just specify each dependencies' version
once in that section of the top-level POM...

Tom

On 10/30/06, Jonas Olsson <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> We're introducing Maven to our multi-artifact product build and we'de
> really like to get full usage of the dependency mechanism. We've got
> many shared libraries as "provided" dependencies which are also included
> in the top level artifact to complete the assembly, but "normal" Maven
> version validation does not include "provided" dependencies, so
> out-of-the-box we don't keep feed-back on if all artifacts are OK with
> the actual shared library versions we're including.
> Is there a way (or plugin) to perform this "deeper" kind of version
> validation or are we wrong in asking?
>
> Thank you for input!
>
> --
> Jonas Olsson
> System Designer
> Cambio Healthcare Systems
>
> 
> Detta e-mail har blivit undersökt av http://www.virus112.se
>
> 
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


This e-mail has been scanned for viruses by http://www.virus112.se


Detta e-mail har blivit undersökt av http://www.virus112.se


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

Re: dev-activity report

[Attila Mezei-Horvati]

Yes, indeed. The dev-activity report works only if the
developer ids match the scm user ids. 

thanks for all your help,
Attila


 

Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates 
(http://voice.yahoo.com)


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

Re: problem with using my plugin

[Eric Redmond]

Try running it in debug mode with the -X attribute.

On 10/30/06, Joachim Van der Auwera <[EMAIL PROTECTED]> wrote:


I am trying to write a custom plugin, but when I try to use it, I get
the following exception :

[INFO] Internal error in the plugin manager executing goal
'be.unid:Uni-d-maven-plugin:0.8-SNAPSHOT:generate': Error adding plugin
dependency 'be.unid:Uni-d-generate:jar' into plugin manager: Cannot add
jar resource:
/home/joachim/.m2/repository/be/unid/Uni-d-generate/0.8-SNAPSHOT/Uni-
d-generate-0.8-SNAPSHOT.jar
(error discovering new components)
input contained no data

However, the jar file mentioned in the message exists at the given
location.
I am using maven 2.0.4

Any ideas what if wrong or how I can fix/work around this?

Thanks for the help,
Joachim

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





--
Eric Redmond
http://codehaus.org/~eredmond

Re: Maven 2 SCM ?

[Eric Redmond]

http://repo1.maven.org/maven2 is the central repository. There is no special
repo for sources... they're just packaged and deployed along with the
standard artifacts.

Eric

On 10/30/06, Sebastien Brunot <[EMAIL PROTECTED]> wrote:


Hi,

does anybody know the URL of the maven 2 sources repository ? I can't
find it on the maven web site...

Thanks,

Sebastien





--
Eric Redmond
http://codehaus.org/~eredmond

Re: Version validation of "provided" dependencies

[Tom Huybrechts]

I don't know the dependency convergence report handle provided dependencies,
but it's worth a try. If you build a default site, this report will be
included. An example can be seen at
http://maven.apache.org/ref/current/dependency-convergence.html

Tom


On 10/30/06, Jonas Olsson <[EMAIL PROTECTED]> wrote:


I'll try to visualise the issue:


pom.xml (top level artifact, "the deliverable")
|
+- submodule A 1.0
|   |
|   +- shared 1.0 [provided]
|
+- submodule B 1.1
|   |
|   +- shared 1.1 [provided]
|
+- shared 1.0 [runtime]


I want a way for maven to tell me, when packaging the top level artifact,
that submodule B is in conflict with the shared 1.0 we chose to include.
Currently this is not done (provided dependencies are ignored, probably on
the assumption that they are EXTERNALLY provided).

/jonas

-Ursprungligt meddelande-
Från: Tom Huybrechts [mailto:[EMAIL PROTECTED]
Skickat: den 30 oktober 2006 16:18
Till: Maven Users List
Ämne: Re: Version validation of "provided" dependencies

Hi Jonas,

I'm not sure if this is what you're asking, but the dependencyManagement
section of the pom makes it a lot easier to ensure your versions stay in
sync between different projects. Just specify each dependencies' version
once in that section of the top-level POM...

Tom

On 10/30/06, Jonas Olsson <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> We're introducing Maven to our multi-artifact product build and we'de
> really like to get full usage of the dependency mechanism. We've got
> many shared libraries as "provided" dependencies which are also included
> in the top level artifact to complete the assembly, but "normal" Maven
> version validation does not include "provided" dependencies, so
> out-of-the-box we don't keep feed-back on if all artifacts are OK with
> the actual shared library versions we're including.
> Is there a way (or plugin) to perform this "deeper" kind of version
> validation or are we wrong in asking?
>
> Thank you for input!
>
> --
> Jonas Olsson
> System Designer
> Cambio Healthcare Systems
>
>

> Detta e-mail har blivit undersökt av http://www.virus112.se
>
>

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



This e-mail has been scanned for viruses by http://www.virus112.se




Detta e-mail har blivit undersökt av http://www.virus112.se



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

Re: [maven 1.x][jnlp plugin 1.4.1] takes very long time to sign jars

[Lukas Theussl]

Hi,

First note that the jnlp plugin is not officially supported anymore by 
the Maven team. However, browsing the open bugs [1] there is none that 
would apply to your description. Quickly looking through the 
plugin.jelly file, I think the signing should be skipped if the property 
maven.jnlp.signjar.store [2] is not defined (or the corresponding file 
does not exist).


HTH,
-Lukas

[1] http://jira.codehaus.org/browse/MPJNLP
[2] http://maven.apache.org/maven-1.x/plugins/jnlp/properties.html

[EMAIL PROTECTED] wrote:

Hi,

I am using jnlp 1.4.1 plugin to generate my webstart client.

At step of signing jars, it takes very very long time (more than 1h30) to 
sign just a few number of jars.

The weird thing is that the cpu is nearly idle, an the memory is not full.

My question is : 
- Is it possible to be a bug  ? and / or
- Is it possible to add the ability to the plugin to pass the 
signing of jars ? In this case it would be possible to sign the jars 
separately.


Thanks for your answer;

regards.


This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 


-

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.





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

Re: Maven 2 SCM ?

[Rémy Sanlaville]

Hi,

Have a look to
https://svn.apache.org/repos/asf/maven/

HTH,

Rémy

2006/10/30, Sebastien Brunot <[EMAIL PROTECTED]>:


Hi,

does anybody know the URL of the maven 2 sources repository ? I can't
find it on the maven web site...

Thanks,

Sebastien

Re: Modifying a web application's web.xml at build time

[Carlos A. Carnero Delgado]

On 10/29/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

... That is, the auth filter is different in the live environment,
when running the integration tests, and when running
'local' on my workstation.


That's nice, but I think it will not help me. Your method, using
properties, can change which servlet to use. I'd like to turn it on or
off.

Thanks a lot,
Carlos.
--
 grah windows just crashed again, unstable crap.
 Windows isn't unstable, it's just spontaneous.

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

Re: Maven 2: How to test a new plugin

[John Casey]

Hi James,

The approach I've taken with the assembly plugin and a couple of other
plugin-like libraries is two-level:

1. unit tests, where I'm testing at the method level where I can and using
EasyMock where I have to.

2. integration tests, for which I'm using the maven-invoker-plugin, the
maven-plugin-management-plugin, and a series of maven projects under src/it.
This allows me to express a set of use cases as real Maven projects, then
verify the result of the build using a Beanshell script.

I've found that the combination of these strategies works well. BTW, the
maven-plugin-management-plugin is still in the maven sandbox...not quite
ready for release (lacks documentation and a few tests still). The
maven-invoker-plugin may also be in the sandbox, but if so, it is ready to
release, just needs to be done.

You can checkout my testing approach here:

http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin

HTH,

-john

On 10/30/06, James Walker <[EMAIL PROTECTED]> wrote:


Hi.

I've a library that I built under Maven 1.

It provides an ant task which does a bunch of code generation.

Under maven 1 I was able to test the ant task during the test goal by
running the task in a pre-goal and ensuring the output was dumped
somewhere that it was able to be found and used during the rest of the
testing.

In fact as far as I can tell under Maven 2 I can not just run the ant
task and have it generate to something like target/src/java, and have
the compilation steps find that new source path.  This is ok because I
figured I might as well add a Maven 2 plugin which provides the code
generation functionality.

This led me to testing the new plugin and the question of "how?".

I want to be able to compile the plugin, use it to generate some source,
then compile the source and run it through some tests.

Is this at all possible?  I get the impression it might not be - at this
time it seems I have to have the plugin installed/available as maven
starts up - otherwise it'll have a fit.

It almost seems I need another module which provides the plugin and to
have compiled+installed that module first?

Any hints?

How are other people testing their plugins?

Thanks for any help,
James.

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

RE: Using maven-antrun-plugin and taskdef

[Chris Hilton]

You need to add the jar as a dependency to the antrun plugin, something
like:


org.apache.maven.plugins
maven-antrun-plugin

  ...


  
ant
ant-jmeter
1.0
  

  

Chris

> -Original Message-
> From: Jeff Mutonho [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 30 October, 2006 03:40
> To: Maven Users List
> Subject: Using maven-antrun-plugin and taskdef
> 
> I've configured the maven-antrun-plugin as follows :
> 
>  
>maven-antrun-plugin
>
> 
> pre-integration-test
> 
>  
>   classname="org.programmerplanet.ant.taskdefs.jmeter.JMeterTask"/>
> jmeterhome="D:\jakarta-jmeter-2.2"
>resultlog="${basedir}/loadtests/JMeterResults.jtl">
>  includes="*.jmx"/>
>  
> 
>
>
> run
>
>   
>  
> 
> 
> 
> and added  ant-jmeter1-0.jar to my dependencies.However , 
> when I run 'mvn install' I get the following build error :
> 
> [INFO] [site:attach-descriptor]
> [INFO] [antrun:run {execution: default}] [INFO] Executing 
> tasks [INFO] 
> --
> --
> [ERROR] BUILD ERROR
> [INFO] 
> --
> --
> [INFO] Error executing ant tasks
> 
> Embedded error: taskdef class 
> org.programmerplanet.ant.taskdefs.jmeter.JMeterTas
> k cannot be found
> [INFO] 
> --
> --
> 
> 
> Is it  correct to do a "taskdef" definition  the way I did?
> 
> 
> 
> Jeff  Mutonho
> 
> GoogleTalk : ejbengine
> Skype: ejbengine
> Registered Linux user number 366042
> 
> -
> 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]

Overriding Central Repository

[ccadete]

Hi,

I override my maven central repository, using this,


  central
  central
  My Maven repository
  http://my.maven.repo.com


but now, although it download packages, maven can't found the plugins !!
First, I clean up the repository, to force the download of the jar's.
Then I make, for example:

mvn archetype:create -DgroupId=pt.matrix -DartifactId=matrix

And

[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not
ex
st or no valid version could be found
[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 1 second
[INFO] Finished at: Mon Oct 30 16:23:43 GMT 2006
[INFO] Final Memory: 1M/2M
[INFO]



It download some packages, but the archetype plugin does not, why ?


CCadete



The plugins are there of course...
-- 
View this message in context: 
http://www.nabble.com/Overriding-Central-Repository-tf2540428s177.html#a7077660
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: Overriding Central Repository

[ccadete]

I notice that it creates the directory tree and maven-metadata-central.xml
files of the plugin.

But with no jar!! How can it be ?


CCadete


-- 
View this message in context: 
http://www.nabble.com/Overriding-Central-Repository-tf2540428s177.html#a7077933
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: problem with using my plugin

[Joachim Van der Auwera]

Ok, it first indicated that it is using a locally installed version, 
then gives the error, the relevant bits seem to be (starting from the 
plugin, continuing with the dependencies, and ending with the error 
stacktrace :



[DEBUG] Uni-d-maven-plugin: resolved to version 0.8-SNAPSHOT from local 
repository

[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d-maven-plugin: using locally installed snapshot
[DEBUG] Retrieving parent-POM: be.unid:Uni-d::0.8-SNAPSHOT for project: 
be.unid:Uni-d-maven-plugin:maven-plugin:0.8-SNAPSHOT from the repository.

[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d: using locally installed snapshot
[DEBUG] Uni-d-maven-plugin: using locally installed snapshot
[DEBUG] be.unid:Uni-d-maven-plugin:maven-plugin:0.8-SNAPSHOT:runtime 
(selected for runtime)

[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d-generate: using locally installed snapshot
[DEBUG] Retrieving parent-POM: be.unid:Uni-d::0.8-SNAPSHOT for project: 
be.unid:Uni-d-generate:jar:0.8-SNAPSHOT from the repository.

[DEBUG] Uni-d: using locally installed snapshot
[DEBUG]   be.unid:Uni-d-generate:jar:0.8-SNAPSHOT:runtime (selected for 
runtime)

[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d-util: using locally installed snapshot
[DEBUG] Retrieving parent-POM: be.unid:Uni-d::0.8-SNAPSHOT for project: 
be.unid:Uni-d-util:jar:0.8-SNAPSHOT from the repository.

[DEBUG] Uni-d: using locally installed snapshot
[DEBUG] be.unid:Uni-d-util:jar:0.8-SNAPSHOT:runtime (selected for 
runtime)
[DEBUG]   org.jboss:jboss-common-jdbc-wrapper:jar:4.0.4:runtime 
(selected for runtime)
[DEBUG]   org.javolution:javolution:jar:3.7.10:runtime (selected for 
runtime)

[DEBUG]   net.sf.fscript:fscript:jar:1.17:runtime (selected for runtime)
[DEBUG]   com.toedter:jcalendar:jar:1.3.2:runtime (selected for runtime)
[DEBUG]   org.jboss:jboss-j2ee:jar:4.0.4:runtime (selected for runtime)
[DEBUG]   commons-httpclient:commons-httpclient:jar:2.0.2:runtime 
(selected for runtime)
[DEBUG] commons-logging:commons-logging:jar:1.0.3:runtime 
(selected for runtime)
[DEBUG]   org.jboss:jbosssx-client:jar:4.0.4:runtime (selected for 
runtime)

[DEBUG] xerces:xercesImpl:jar:2.4.0:runtime (selected for runtime)
[DEBUG] velocity:velocity-dep:jar:1.4:runtime (selected for runtime)
[DEBUG] jalopy:jalopy:jar:1.5rc3:runtime (selected for runtime)
[DEBUG]   log4j:log4j:jar:1.2.8:runtime (selected for runtime)
[DEBUG] ant:ant:jar:1.6.5:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for 
project: null:maven-project:jar:2.0.4 from the repository.
[DEBUG]   org.apache.maven:maven-project:jar:2.0.4:runtime (selected for 
runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for 
project: org.apache.maven:maven-artifact:jar:2.0.4 from the repository.
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.4:runtime (selected 
for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: 
org.codehaus.plexus:plexus-containers::1.0.3 for project: 
null:plexus-container-default:jar:1.0-alpha-9 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.plexus:plexus::1.0.4 for 
project: org.codehaus.plexus:plexus-containers:pom:1.0.3 from the 
repository.
[DEBUG] 
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime 
(selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime 
(removed - nearer found: 1.1)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2:runtime (selected 
for runtime)

[DEBUG]   junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for 
project: null:maven-settings:jar:2.0.4 from the repository.
[DEBUG] org.apache.maven:maven-settings:jar:2.0.4:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for 
project: org.apache.maven:maven-model:jar:2.0.4 from the repository.
[DEBUG]   org.apache.maven:maven-model:jar:2.0.4:runtime (selected 
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for 
project: org.apache.maven:maven-artifact-manager:jar:2.0.4 from the 
repository.
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.4:runtime 
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven.wagon:wagon::1.0-alpha-6 
for project: null:wagon-provider-api:jar:1.0-alpha-6 from the repository.
[DEBUG]   
org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6:runtime 
(selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime 
(removed - nearer found: 1.1)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for 
project: org.apache.maven:maven-repository-metadata:jar:2.0.4 from the 
repository.
[DEBUG]   
org.apache.maven:maven-repository-metadata:jar:2.0.4:runtime (selected 
for ru

Re : Re: Proxy at maven 2

[Michael Post]

Hello Xavier,

thanks for your answer.

--
2006 Oct 30 - 14:54
Xavier Outhier <[EMAIL PROTECTED]>
--
>The settings for maven (2) is an xml file at this location:
>C:Documents and Settings.m2settings.xml
>
>- <#> 
> 
><
>-   <#> 
>  true
>  http
>  
>  
>  
>  
>
>
>[...]
>
>
>Username and password can also be set depends on your config.
>

this was exactly the correct point. Now it has been done perfectly.

Thanks Michael

Re: Hibernate mapping resource path in Maven

[Andy Buckley]

Aleksei Valikov wrote:

> 1. Put your HBM files into resources, not into java. You should have
> src/main/resource/cedar/hepdata/mode/Autor.hbm.xml etc.
> 
> 2. Use
> 
> 

Fantastic, thanks. The whole tree seems not to be needed, so just making e.g.
src/main/resource/hbm/Author.hbm.xml and pointing the config file at those
seems to work nicely, without having a chain of empty directories for no
particular reason.

Thank you!
Andy

-- 
Andy Buckley: CEDAR @ IPPP, Durham
Work: www.cedar.ac.uk
www.insectnation.org

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

RE: Inherited property resolution

[Morgovsky, Alexander \(US - Glen Mills\)]

Thanks for your help. 


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


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

doxia-maven-plugin - special characters (German Umlaut, etc...)

[MartinAhrer]

I have several .APT documents hat were created for a site processed by the
maven-site-plugin. Everything works fine even with special characters (like
like Ä, etc...) in the generated HTML.

The maven-site-plugin is configured for ISO-8859-1.

maven-site-plugin

en
ISO-8859-1


All .APT documents are using the ISO-8859-1 encoding (my eclipse IDE is
configured with -Dfile.encoding=ISO-8859-1).

Now I have added the doxia-maven-plugin for creating a  PDF book from all
.APT documents that were written for the site.
The doxia-maven-plugin throws a ExceptionConverter:
org.xml.sax.SAXParseException: Invalid byte 2 of 2-byte UTF-8 sequence
 exception when processing any .APT document that contains a special
character (like Ä).

With some experiments I have figured out when converting the .APT documents
from  ISO-8859-1 to UTF-8 the doxia-maven-plugin creates a perfectly fine
(with correct special characters) PDF !

BUT now the the site HTML does not show special characters properly.

I have extended these tests for the XDOC doxia module. All of the .APT files
that are using the UTF-8 encoding do not produce proper HTML whereas all
.APT files with ISO-8859-1 encoding produce correct HTML.

Now I hope somebody can give me a clou on how to get both the
maven-site-plugin and the doxia-maven-plugin working with special
characters!

To me it looks like the maven-site-plugin and doxia-maven-plugin do not work
the same way regarding file encoding!

Thanks
  Martin


-- 
View this message in context: 
http://www.nabble.com/doxia-maven-plugin---special-characters-%28German-Umlaut%2C-etc...%29-tf2540610s177.html#a7078235
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: HELP: Running site goal on a cutom packaging

[John Casey]

If you want to provide a custom packaging type, there are a few things you
may need to do:

1. Think about your artifact handling for this packaging...if it needs to be
on the classpath, if it is subject to transitive dependency resolution, etc.

2. Define your lifecycle mapping in a components.xml within the plugin or
build extension you intend to use to share it. This file goes in the
plugin/build extension project under:

src/main/resources/META-INF/plexus/components.xml

3a. If your custom packaging takes advantage of behavior in a custom plugin,
you may want to include it via the plugin:


 
   
 [...]
 true
[...]

The extensions flag tells Maven to look here for custom packaging, artifact
handlers, etc.

3b. If your custom packaging DOESN'T use a custom plugin, as in the case
where you just want to remap phase bindings from another lifecycle mapping,
you should consider using a build extension. Build extensions are
plain-vanilla jars that contain the component descriptor as outlined in (2)
above; it doesn't have to have any associated code with it, just that
descriptor. Then, include this in the POM of your project with the custom
packaging, as:


 [...]
 your-custom
 [...]

 
   
 
   ...
   ...
   ...
 
   
 


HTH,

John

On 10/30/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote:


I need some help with running the site goal on a custom packaging.

This is how the packaging is defined..
http://rifers.org/paste/show/2093

On running 'mvn site' on a pom with this packaging, I get

[DEBUG] Error looking up lifecycle mapping to retrieve optional mojos.
Lifecycle ID: site. Error: Component descriptor cannot be found in the
component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingintegration-test.

org.codehaus.plexus.component.repository.exception.ComponentLookupException
:
Component descriptor cannot be found in the component repository:
org.apache.maven.lifecycle.mapping.LifecycleMappingintegration-test.
at org.codehaus.plexus.DefaultPlexusContainer.lookup(
DefaultPlexusContainer.java:323)
at org.codehaus.plexus.DefaultPlexusContainer.lookup(
DefaultPlexusContainer.java:440)



In the above components.xml, I tried merging both the 
elements under the same  for the same . The
default execution of the pom failed. I had to separate the 
into separate  elements.

Can someone please guide me into the correct path here ?

Thanx
Prasad.


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

RE: Maven 2 SCM ?

[Sebastien Brunot]

Thanks, that's exactly what I was looking for...

Sebastien 

-Original Message-
From: Rémy Sanlaville [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 30, 2006 4:55 PM
To: Maven Users List
Subject: Re: Maven 2 SCM ?

Hi,

Have a look to
https://svn.apache.org/repos/asf/maven/

HTH,

Rémy

2006/10/30, Sebastien Brunot <[EMAIL PROTECTED]>:
>
> Hi,
>
> does anybody know the URL of the maven 2 sources repository ? I can't 
> find it on the maven web site...
>
> Thanks,
>
> Sebastien
>
>

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

Re: Maven 2 SCM ?

[Eric Redmond]

Ah sorry. "repository" threw me for a loop when in Maven Mode.

Eric

On 10/30/06, Sebastien Brunot <[EMAIL PROTECTED]> wrote:


Thanks, that's exactly what I was looking for...

Sebastien

-Original Message-
From: Rémy Sanlaville [mailto:[EMAIL PROTECTED]
Sent: Monday, October 30, 2006 4:55 PM
To: Maven Users List
Subject: Re: Maven 2 SCM ?

Hi,

Have a look to
https://svn.apache.org/repos/asf/maven/

HTH,

Rémy

2006/10/30, Sebastien Brunot <[EMAIL PROTECTED]>:
>
> Hi,
>
> does anybody know the URL of the maven 2 sources repository ? I can't
> find it on the maven web site...
>
> Thanks,
>
> Sebastien
>
>

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





--
Eric Redmond
http://codehaus.org/~eredmond

executable jar with all dependencies

[Enda Ridge]

Hi,
I'd be grateful for help with the following please.
I've looked at similar threads but cannot get the results to apply in my 
own circumstances.


I am using Maven2 with a multiple module project. The package command 
works fine, placing a jar in each module's target directory.


I would like to produce a single executable jar for the whole project, 
including all dependent jars from my repository and all generated jars 
from my own project.


I've seen posts mentioning the assembly and jar plugins but cannot find 
any instructions on the project's web site.


Thanks in advance,
Enda

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

[M2] Keeping plugins up to date

[Siegmann Daniel, NY]

Today I ran into a strange bug, which was fixed after I tried explicitly
using Surefire 2.2.

But this brought up a question: what is the best way to keep plugins up to
date? Maven2 releases are so infrequent that it seems the default plugin
versions are quite out of date.

It would be very time consuming to have to track releases for all the core
plugins, set the versions explicitly in the POM for all our projects, and
then keep these versions up to date.

How have the rest of you dealt with this?

--
Daniel Siegmann
FJA-US, Inc.
(212) 840-2618 ext. 139

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

Managing Release Jars

[Pin Ngee Koh]

I have a jar, say X.jar,  which is reference by numerous projects.
Developers are changing and releasing various versions of X.jar for releases.
What is the best way to manage the POM files of projects which depends on it.

1. Use version range? E.g [1.0,2.0)
   This option has potential of picking up unintended latest release of X.jar
2. Manually update reach project's POM file and up a minor version?
   This option is labor intensive and difficult to manage. Also,
increasing a minor version in projects seems wrong and weird.

What's a better way you would suggest?

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

Re: executable jar with all dependencies

[John Casey]

You might start by looking here:

http://maven.apache.org/plugins/maven-assembly-plugin

You might be able to achieve this using the built-in jar-with-dependencies
descriptorRef, along with a custom manifest entry...for the manifest
customizations, you could add this to the assembly plugin configuration:


 
   
 some.class.Main
   
 


If the jar-with-dependencies assembly type doesn't work, you might have to
create your own assembly descriptor, specify a dependencySet within that,
and specify true.

HTH,

John

On 10/30/06, Enda Ridge <[EMAIL PROTECTED]> wrote:


Hi,
I'd be grateful for help with the following please.
I've looked at similar threads but cannot get the results to apply in my
own circumstances.

I am using Maven2 with a multiple module project. The package command
works fine, placing a jar in each module's target directory.

I would like to produce a single executable jar for the whole project,
including all dependent jars from my repository and all generated jars
from my own project.

I've seen posts mentioning the assembly and jar plugins but cannot find
any instructions on the project's web site.

Thanks in advance,
Enda

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

Sync with Maven 1 repo

[Morgovsky, Alexander \(US - Glen Mills\)]

Yes, set the type of the repository to "legacy" using
legacy.  Here is an example.


 
x
x
legacy
"the url to your repository"

false


...


Thanks. 


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


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

continuum, release and dependencies

[Luca Dall'Olio]

Dear Maven Users,
I am trying to automate the release process by using continuum and maven 2.
Actually I am having this problem : I can release my root project, but any
other project depending on it fails during the release:prepare, because the
version-range dependency
(say [5.0.0,) ) about the root project is resolved against the latest
continuum build which is a SNAPSHOT.

If I try to write the dependency version as RELEASE everything seem to work,
but this makes life hard on the developer's side, since they should stay on
the latest SNAPSHOT; continuum itself should stay on the SNAPSHOT except
during releases too...

I am thinking of writing a couple of profiles and declaring different
versions by using the dependencymanagement mechanism, is this the right
choice?

Shouldn't the release plugin resolve an open-right version range against the
latest RELEASE instead of the latest SNAPSHOT?

By the way, the release plugin doesn't seem to create the release-pom.xml,
and this makes it very hard to reproduce the release afterwards... Its code
seem to be all commented out, have you got any workaround?

Thank you very much in advance,

Luca Dall'Olio


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

Re: Managing Release Jars

[John Casey]

Unless your projects are released in lock-step, you probably want to update
the dependency version manually. While this is labor intensive, it also
guarantees that you know exactly what you're building. As you analyze and
test against newer versions of the dependency, you can manage that small
piece of dependency metadata manually without much difficulty.

If you're releasing all of the projects as a single app with a single
version, you might use dependencyManagement from an application-level parent
POM.

HTH,

John

On 10/30/06, Pin Ngee Koh <[EMAIL PROTECTED]> wrote:


I have a jar, say X.jar,  which is reference by numerous projects.
Developers are changing and releasing various versions of X.jar for
releases.
What is the best way to manage the POM files of projects which depends on
it.

1. Use version range? E.g [1.0,2.0)
This option has potential of picking up unintended latest release of
X.jar
2. Manually update reach project's POM file and up a minor version?
This option is labor intensive and difficult to manage. Also,
increasing a minor version in projects seems wrong and weird.

What's a better way you would suggest?

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

Re: mevenide vs. m2eclipse?

[Martin van den Bemt]

I am working on a m2 eclipse plugin, but that is not public yet..

Mvgr,
Martin

Steinar Bang wrote:

I'm currently using the m2eclipse plugin in eclipse 3.2, and it
works. 


But today I thought that it was a pity that it didn't have a POM
editor.  So I googled for "eclipse pom editor" and discovered
"mevenide". 
 http://mevenide.codehaus.org/mevenide-ui-eclipse/features.html

(which has a POM editor, in case you wondered)

So I'm wondering about the relationship between m2eclipse and
mevenide, eg. are they in conflict?  Are they complimentary?  What
advantages do one offer over the other?

Googling for "mevenide vs. m2eclipse" found me this
 http://www.onjava.com/pub/a/onjava/2006/03/29/maven-2-0.html?page=last
search for "mevenide" in that page for "Eclipse integration" and
you'll find an article saying mevenide only supports maven 1.x.

But this was in April.  Does anyone know if that's still the case?

The http://mevenide.codehaus.org/ says the NetBeans plugin has Maven 2
support, but since nonde of the other mentions it I'm assuming they
are still on Maven 1.x?

Thanx!


- Steinar


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





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

Re: [m2] changes-maven-plugin - announcement-mail

[Dennis Lundberg]

Two more things to try out.

First of all, you should be using the maven-changes-plugin instead of 
the changes-maven-plugin. Your pom should have these lines:


org.apache.maven.plugins
maven-changes-plugin

Secondly you could try this:

  
[EMAIL PROTECTED]
  

in analogy to your toAddresses element.

--
Dennis Lundberg

[EMAIL PROTECTED] wrote:
Hi, 
how can I configure the 'from' ?


Do it like this:



${basedir}/src/changes
xx.xx.xx.xx

xx



[EMAIL PROTECTED]




[EMAIL PROTECTED]


[EMAIL PROTECTED]




doesn't works ;-(
It takes always the first developert from ${project.developers}

Fredy
 

Kabel Deutschland bietet Ihnen Internet, Telefonieren und Fernsehen aus einer Hand. Informieren Sie sich über unsere Produkte unter 


www.kabeldeutschland.de
 
Diese E-Mail und etwaige Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind, benachrichtigen Sie bitte den Absender und vernichten Sie anschließend diese Mail und die Anlagen.



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




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

Re: [M2] Changelog plugin report unknown range

[Sam Anabtawi]

So is there any solution or any kind of work around? Can I manually change
that message somewhere?
A message saying "Changes from an unknown range" on my most important site
page does not seem to impress my boss alot :\




Allan Ramirez wrote:
> 
> Hi Nate,
> 
> As far as I know, the plugin does not resolve the last revision dates 
> for each tag. Maybe the text  "Changes from an unknown range" should be 
> replace with "Changes from  to "
> 
> -allan
> 
> Nate wrote:
>> When I generate the changelog plugin using the tag type with CVS, I get
>> the following string at the top of the page: "Changes from an unknown
>> range".
>>
>> Here is part of my POM:
>> 
>>  org.apache.maven.plugins
>>  maven-changelog-plugin
>>  2.0-SNAPSHOT
>>  
>>   
>>single-report
>>
>> tag
>> 
>>  MyApp_0_7_rc1
>>  MyApp_0_7_rc2
>> 
>>
>> ...
>>   
>>  
>> 
>>
>> If I use the date or range type, that field is filled in correctly with
>> the date range.  I looked at the changelog.xml file that is generated for
>> both the tag type and a date type, and the start and end dates attributes
>> were not filled in for the tag output.  I believe these start and end
>> attributes are was is being read in by the report generator and used for
>> the range.
>>
>> Generated changelog.xml from tag type:
>> 
>>  
>>   
>>...
>>
>> Generated changelog.xml from date type:
>> 
>>  
>>   
>>...
>>
>> I looked into the changelog plugin source, and found that the changeset
>> element and attributes are generated by an SCM plugin object.  I tried to
>> go into that source code, but I was unsuccessful in tracking down the
>> exact location where those fields are filled in.  Is it possible to get
>> the tag range displayed instead of an unknown date range?
>>
>> Thanks,
>> -Nate
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>   
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-M2--Changelog-plugin-report-unknown-range-tf2510906s177.html#a7081238
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: [M2] Changelog plugin report unknown range

[Sam Anabtawi]

I guess I could just make the change in the html. That works ok for now, but
I have to reapply these changes every time I generate a new site.


Sam Anabtawi wrote:
> 
> So is there any solution or any kind of work around? Can I manually change
> that message somewhere?
> A message saying "Changes from an unknown range" on my most important site
> page does not seem to impress my boss alot :\
> 
> 
> 
> 
> Allan Ramirez wrote:
>> 
>> Hi Nate,
>> 
>> As far as I know, the plugin does not resolve the last revision dates 
>> for each tag. Maybe the text  "Changes from an unknown range" should be 
>> replace with "Changes from  to "
>> 
>> -allan
>> 
>> Nate wrote:
>>> When I generate the changelog plugin using the tag type with CVS, I get
>>> the following string at the top of the page: "Changes from an unknown
>>> range".
>>>
>>> Here is part of my POM:
>>> 
>>>  org.apache.maven.plugins
>>>  maven-changelog-plugin
>>>  2.0-SNAPSHOT
>>>  
>>>   
>>>single-report
>>>
>>> tag
>>> 
>>>  MyApp_0_7_rc1
>>>  MyApp_0_7_rc2
>>> 
>>>
>>> ...
>>>   
>>>  
>>> 
>>>
>>> If I use the date or range type, that field is filled in correctly with
>>> the date range.  I looked at the changelog.xml file that is generated
>>> for
>>> both the tag type and a date type, and the start and end dates
>>> attributes
>>> were not filled in for the tag output.  I believe these start and end
>>> attributes are was is being read in by the report generator and used for
>>> the range.
>>>
>>> Generated changelog.xml from tag type:
>>> 
>>>  
>>>   
>>>...
>>>
>>> Generated changelog.xml from date type:
>>> 
>>>  
>>>   
>>>...
>>>
>>> I looked into the changelog plugin source, and found that the changeset
>>> element and attributes are generated by an SCM plugin object.  I tried
>>> to
>>> go into that source code, but I was unsuccessful in tracking down the
>>> exact location where those fields are filled in.  Is it possible to get
>>> the tag range displayed instead of an unknown date range?
>>>
>>> Thanks,
>>> -Nate
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>   
>> 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/-M2--Changelog-plugin-report-unknown-range-tf2510906s177.html#a7081308
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Struts[2] scope = prototype

[Scott Purcell]

In the 'equinox-struts2-hibernate-1.7' I deployed and I am running
through the code trying to understand it. Anyway, there is a file called
"action-servlet.xml" which is a Spring bean definition file. Within it
is has this:

 



 

When I referenced my Spring in Action book, it states that all beans are
singleton by default. But you can set the singleton="false" to make it a
prototype. A blueprint they state. But they do not mention
scope="prototype".

 

Is this something new and the book is obsolete?

 

Thanks,

 

Re: Struts[2] scope = prototype

[Don Brown]

I believe that's a Spring 2 thing.  Now, you can have multiple scopes
in addition to singleton and not singleton.

Don

On 10/30/06, Scott Purcell <[EMAIL PROTECTED]> wrote:

In the 'equinox-struts2-hibernate-1.7' I deployed and I am running
through the code trying to understand it. Anyway, there is a file called
"action-servlet.xml" which is a Spring bean definition file. Within it
is has this:







When I referenced my Spring in Action book, it states that all beans are
singleton by default. But you can set the singleton="false" to make it a
prototype. A blueprint they state. But they do not mention
scope="prototype".



Is this something new and the book is obsolete?



Thanks,







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

Compiler Version?

[Scott Purcell]

Is it possible to find out the current version that is being used when I
do a build? 

 

Thanks,

 

Re: Struts[2] scope = prototype

[Wayne Fay]

You realize this is the Maven Users list right, and not Spring Users...

Wayne

On 10/30/06, Don Brown <[EMAIL PROTECTED]> wrote:

I believe that's a Spring 2 thing.  Now, you can have multiple scopes
in addition to singleton and not singleton.

Don

On 10/30/06, Scott Purcell <[EMAIL PROTECTED]> wrote:
> In the 'equinox-struts2-hibernate-1.7' I deployed and I am running
> through the code trying to understand it. Anyway, there is a file called
> "action-servlet.xml" which is a Spring bean definition file. Within it
> is has this:
>
>
>
>  scope="prototype">
>
>
>
> When I referenced my Spring in Action book, it states that all beans are
> singleton by default. But you can set the singleton="false" to make it a
> prototype. A blueprint they state. But they do not mention
> scope="prototype".
>
>
>
> Is this something new and the book is obsolete?
>
>
>
> Thanks,
>
>
>
>
>

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

Install jdev plugin

[Dudu]

I downloaded the source code of jdev plugin of Trinidad (my faces)repository
and I did mvn install, all files was compiled and installed sucefully but
when I do mvn jdev:jdev, maven says that the jdev plugin doesn't exists

I am using the trunk source code.
Thanks
--
--
Dudu
GoogleTalk: eduardopichler[at]gmail[dot]com
skype:eduardopichler

RE: Struts[2] scope = prototype

[Scott Purcell]

Ooops,
Sorry about that ...Monday

-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 30, 2006 2:29 PM
To: Maven Users List
Subject: Re: Struts[2] scope = prototype

You realize this is the Maven Users list right, and not Spring Users...

Wayne

On 10/30/06, Don Brown <[EMAIL PROTECTED]> wrote:
> I believe that's a Spring 2 thing.  Now, you can have multiple scopes
> in addition to singleton and not singleton.
>
> Don
>
> On 10/30/06, Scott Purcell <[EMAIL PROTECTED]> wrote:
> > In the 'equinox-struts2-hibernate-1.7' I deployed and I am running
> > through the code trying to understand it. Anyway, there is a file
called
> > "action-servlet.xml" which is a Spring bean definition file. Within
it
> > is has this:
> >
> >
> >
> >  > scope="prototype">
> >
> >
> >
> > When I referenced my Spring in Action book, it states that all beans
are
> > singleton by default. But you can set the singleton="false" to make
it a
> > prototype. A blueprint they state. But they do not mention
> > scope="prototype".
> >
> >
> >
> > Is this something new and the book is obsolete?
> >
> >
> >
> > Thanks,
> >
> >
> >
> >
> >
>
> -
> 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: Compiler Version?

[Eric Redmond]

You can get the version as a property in the POM via ${java.version}. If you
want it to output to the screen, you can use the antrun plugin  tag.

Eric

On 10/30/06, Scott Purcell <[EMAIL PROTECTED]> wrote:


Is it possible to find out the current version that is being used when I
do a build?



Thanks,








--
Eric Redmond
http://codehaus.org/~eredmond

Re: Install jdev plugin

[Eric Redmond]

http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html

Eric

On 10/30/06, Dudu <[EMAIL PROTECTED]> wrote:


I downloaded the source code of jdev plugin of Trinidad (my
faces)repository
and I did mvn install, all files was compiled and installed sucefully but
when I do mvn jdev:jdev, maven says that the jdev plugin doesn't
exists

I am using the trunk source code.
Thanks
--
--
Dudu
GoogleTalk: eduardopichler[at]gmail[dot]com
skype:eduardopichler





--
Eric Redmond
http://codehaus.org/~eredmond

Re: mevenide vs. m2eclipse?

[Steinar Bang]

> Martin van den Bemt <[EMAIL PROTECTED]>:

> I am working on a m2 eclipse plugin, but that is not public yet..

Thanx for the information!

Will it be better than m2eclipse?  :-)


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

Re: problem with using my plugin

[Eric Redmond]

Is the file readable/executable by your account? If so, perhaps it's the
plugin descriptor.

Go ahead and send me the
/home/joachim/.m2/repository/be/unid/Uni-d-generate/0.8-SNAPSHOT/Uni-
d-generate-0.8-SNAPSHOT.jar file (not to this group, though). I can take a
look.

Eric
[EMAIL PROTECTED]

On 10/30/06, Joachim Van der Auwera <[EMAIL PROTECTED]> wrote:


Ok, it first indicated that it is using a locally installed version,
then gives the error, the relevant bits seem to be (starting from the
plugin, continuing with the dependencies, and ending with the error
stacktrace :


[DEBUG] Uni-d-maven-plugin: resolved to version 0.8-SNAPSHOT from local
repository
[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d-maven-plugin: using locally installed snapshot
[DEBUG] Retrieving parent-POM: be.unid:Uni-d::0.8-SNAPSHOT for project:
be.unid:Uni-d-maven-plugin:maven-plugin:0.8-SNAPSHOT from the repository.
[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d: using locally installed snapshot
[DEBUG] Uni-d-maven-plugin: using locally installed snapshot
[DEBUG] be.unid:Uni-d-maven-plugin:maven-plugin:0.8-SNAPSHOT:runtime
(selected for runtime)
[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d-generate: using locally installed snapshot
[DEBUG] Retrieving parent-POM: be.unid:Uni-d::0.8-SNAPSHOT for project:
be.unid:Uni-d-generate:jar:0.8-SNAPSHOT from the repository.
[DEBUG] Uni-d: using locally installed snapshot
[DEBUG]   be.unid:Uni-d-generate:jar:0.8-SNAPSHOT:runtime (selected for
runtime)
[DEBUG] Skipping disabled repository central
[DEBUG] Uni-d-util: using locally installed snapshot
[DEBUG] Retrieving parent-POM: be.unid:Uni-d::0.8-SNAPSHOT for project:
be.unid:Uni-d-util:jar:0.8-SNAPSHOT from the repository.
[DEBUG] Uni-d: using locally installed snapshot
[DEBUG] be.unid:Uni-d-util:jar:0.8-SNAPSHOT:runtime (selected for
runtime)
[DEBUG]   org.jboss:jboss-common-jdbc-wrapper:jar:4.0.4:runtime
(selected for runtime)
[DEBUG]   org.javolution:javolution:jar:3.7.10:runtime (selected for
runtime)
[DEBUG]   net.sf.fscript:fscript:jar:1.17:runtime (selected for
runtime)
[DEBUG]   com.toedter:jcalendar:jar:1.3.2:runtime (selected for
runtime)
[DEBUG]   org.jboss:jboss-j2ee:jar:4.0.4:runtime (selected for
runtime)
[DEBUG]   commons-httpclient:commons-httpclient:jar:2.0.2:runtime
(selected for runtime)
[DEBUG] commons-logging:commons-logging:jar:1.0.3:runtime
(selected for runtime)
[DEBUG]   org.jboss:jbosssx-client:jar:4.0.4:runtime (selected for
runtime)
[DEBUG] xerces:xercesImpl:jar:2.4.0:runtime (selected for runtime)
[DEBUG] velocity:velocity-dep:jar:1.4:runtime (selected for runtime)
[DEBUG] jalopy:jalopy:jar:1.5rc3:runtime (selected for runtime)
[DEBUG]   log4j:log4j:jar:1.2.8:runtime (selected for runtime)
[DEBUG] ant:ant:jar:1.6.5:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for
project: null:maven-project:jar:2.0.4 from the repository.
[DEBUG]   org.apache.maven:maven-project:jar:2.0.4:runtime (selected for
runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for
project: org.apache.maven:maven-artifact:jar:2.0.4 from the repository.
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.4:runtime (selected
for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.1:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM:
org.codehaus.plexus:plexus-containers::1.0.3 for project:
null:plexus-container-default:jar:1.0-alpha-9 from the repository.
[DEBUG] Retrieving parent-POM: org.codehaus.plexus:plexus::1.0.4 for
project: org.codehaus.plexus:plexus-containers:pom:1.0.3 from the
repository.
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:runtime
(selected for runtime)
[DEBUG]   org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime
(removed - nearer found: 1.1)
[DEBUG]   classworlds:classworlds:jar:1.1-alpha-2:runtime (selected
for runtime)
[DEBUG]   junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for
project: null:maven-settings:jar:2.0.4 from the repository.
[DEBUG] org.apache.maven:maven-settings:jar:2.0.4:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for
project: org.apache.maven:maven-model:jar:2.0.4 from the repository.
[DEBUG]   org.apache.maven:maven-model:jar:2.0.4:runtime (selected
for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven:maven::2.0.4 for
project: org.apache.maven:maven-artifact-manager:jar:2.0.4 from the
repository.
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.4:runtime
(selected for runtime)
[DEBUG] Retrieving parent-POM: org.apache.maven.wagon:wagon::1.0-alpha-6
for project: null:wagon-provider-api:jar:1.0-alpha-6 from the repository.
[DEBUG]
org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6:runtime
(selected for runtime)
[DEBUG] org.codehaus.plexus:ple

HOWTO: Have assembly plugin call package automatically before doing assembly?

[Jan Thomä]

Hi,

currently i am using the assembly - plugin, to assemble a multi-module project 
into a single directory containing the binary output of all modules. However, 
i always have to call package before assembly, otherwise the assembly-plugin 
states that i should call package before assembly and fails. Is there some 
way to have package automatically called by assembly, as this is very 
repetitive and actually i don't see a reason why assembly does not call 
package by default... Any insights are appreciated.

Thank you and best regards,
Jan
-- 

Jan Thomä
insOMnia - We never sleep...   http://www.insomnia-hq.de


pgph4jPyuTG0r.pgp
Description: PGP signature

Re: Maven 2: How to test a new plugin

[James Walker]

Hi John,

Thanks for all that - I'll spend some time flicking through your code - 
it sounds similiar enough that it should answer all my questions.


Cheers,
James.


John Casey wrote:

Hi James,

The approach I've taken with the assembly plugin and a couple of other
plugin-like libraries is two-level:

1. unit tests, where I'm testing at the method level where I can and using
EasyMock where I have to.

2. integration tests, for which I'm using the maven-invoker-plugin, the
maven-plugin-management-plugin, and a series of maven projects under 
src/it.

This allows me to express a set of use cases as real Maven projects, then
verify the result of the build using a Beanshell script.

I've found that the combination of these strategies works well. BTW, the
maven-plugin-management-plugin is still in the maven sandbox...not quite
ready for release (lacks documentation and a few tests still). The
maven-invoker-plugin may also be in the sandbox, but if so, it is ready to
release, just needs to be done.

You can checkout my testing approach here:

http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin

HTH,

-john

On 10/30/06, James Walker <[EMAIL PROTECTED]> wrote:


Hi.

I've a library that I built under Maven 1.

It provides an ant task which does a bunch of code generation.

Under maven 1 I was able to test the ant task during the test goal by
running the task in a pre-goal and ensuring the output was dumped
somewhere that it was able to be found and used during the rest of the
testing.

In fact as far as I can tell under Maven 2 I can not just run the ant
task and have it generate to something like target/src/java, and have
the compilation steps find that new source path.  This is ok because I
figured I might as well add a Maven 2 plugin which provides the code
generation functionality.

This led me to testing the new plugin and the question of "how?".

I want to be able to compile the plugin, use it to generate some source,
then compile the source and run it through some tests.

Is this at all possible?  I get the impression it might not be - at this
time it seems I have to have the plugin installed/available as maven
starts up - otherwise it'll have a fit.

It almost seems I need another module which provides the plugin and to
have compiled+installed that module first?

Any hints?

How are other people testing their plugins?

Thanks for any help,
James.

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

finalName

[Shelley Lock]

The 4.0.0 POM schema indicates that the finalName includes the extension [1], 
but when running "package," the default packaging type extension is 
automatically appended.  For example, if test.zip is 
used for a jar project, the resulting artifact is test.zip.jar.  Is this an 
issue with the package goal or a miscommunication in the xsd?

[1] http://maven.apache.org/maven-v4_0_0.xsd

 
-
Get your email and see which of your friends are online - Right on the  new 
Yahoo.com

Re: HOWTO: Have assembly plugin call package automatically before doing assembly?

[Wendy Smoak]

On 10/30/06, Jan Thomä <[EMAIL PROTECTED]> wrote:


currently i am using the assembly - plugin, to assemble a multi-module project
into a single directory containing the binary output of all modules. However,
i always have to call package before assembly, otherwise the assembly-plugin
states that i should call package before assembly and fails. Is there some
way to have package automatically called by assembly, as this is very
repetitive and actually i don't see a reason why assembly does not call
package by default... Any insights are appreciated.


John Casey once explained why you have to call assembly:assembly
separately in Maven 2.0.

See:  
http://www.nabble.com/Re%3A-building-assemblies-from-the-top-level-project-directory-p4735063.html

--
Wendy

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

Migrating to a new build machine

[Prashanth Krishnamurthy]

Hi,

We are planning to move the maven repository to a new
build machine. Is there a recommended process/steps ?
(How to,...etc) Please advise.

(This maven repository is used by 2-3 different
project teams and is very imp for a smooth migration.)

thanks
--Prashanth



 

Access over 1 million songs - Yahoo! Music Unlimited 
(http://music.yahoo.com/unlimited)


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

Can a project use a plugin that is part of the project - bootstrap issue

[J. Matthew Pryor]

I am trying to work through a "boot-strap" issue.

Currently we have a multi-project that includes a maven-plugin module 
that is then used to build other modules in the multi-project.


As you might expect a clean checkout & build at the top-level fails 
because mvn says it can't find the plugin in question (it hasn't been 
built yet).


Is there any way to do this? Or do I have to break the plugin out into 
its own project & build it separately?


Thanks,
Matthew

p.s. I posted this question once before but did so as a reply and was 
worried it got lost in that noise, apologies for the duplication


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

Re: finalName

[Wendy Smoak]

On 10/30/06, Shelley Lock <[EMAIL PROTECTED]> wrote:

The 4.0.0 POM schema indicates that the finalName includes the extension [1], but when running 
"package," the default packaging type extension is automatically appended.  For example, if 
test.zip is used for a jar project, the resulting artifact is 
test.zip.jar.  Is this an issue with the package goal or a miscommunication in the xsd?


Shelley, the xsd for Maven 2.0.4 differs from the comments that you
pasted on MNG-1676.  What version did you copy that from?


From http://maven.apache.org/ref/2.0.4/maven-model/maven.html :

finalNameThe filename (excluding the extension, and with no path
information) that the produced artifact will be called. The default
value is ${artifactId}-${version}.

(This started as discussion on http://jira.codehaus.org/browse/MNG-1676 .)

--
Wendy

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

Re: finalName

[Wendy Smoak]

On 10/30/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:


Shelley, the xsd for Maven 2.0.4 differs from the comments that you
pasted on MNG-1676.  What version did you copy that from?


Must read footnotes. :)

Okay, so the docs for finalName differ on
  http://maven.apache.org/maven-v4_0_0.xsd
and
  http://maven.apache.org/ref/2.0.4/maven-model/maven.html

My guess is that the xsd needs to be re-generated, since the 2.0.4
docs describe the current behavior.

--
Wendy

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

Re: Can a project use a plugin that is part of the project - bootstrap issue

[J. Matthew Pryor]

OK so it seems my nabble searching is pretty lousy ... there was a 
similar post recently


The solution I have come up with is to use profiles in the top-level POM 
to contain the modules declarations


I create a bootstrap profile which contains the minimal modules, then an 
'all' profile that contains all modules and has 
true


So the fresh top level build does this:

mvn -P bootstrap clean install

That seems to work fine

Cheers,
jmp

J. Matthew Pryor wrote:

I am trying to work through a "boot-strap" issue.

Currently we have a multi-project that includes a maven-plugin module 
that is then used to build other modules in the multi-project.


As you might expect a clean checkout & build at the top-level fails 
because mvn says it can't find the plugin in question (it hasn't been 
built yet).


Is there any way to do this? Or do I have to break the plugin out into 
its own project & build it separately?


Thanks,
Matthew

p.s. I posted this question once before but did so as a reply and was 
worried it got lost in that noise, apologies for the duplication


-
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: Can a project use a plugin that is part of the project - bootstrap issue

[William Ferguson]

Matt,

There was a similar post over the weekend
http://www.nabble.com/Impossible-to-build-ourproject-from-scratch-tf2519
755s177.html#a7027880

Hope it helps.

William 

> -Original Message-
> From: J. Matthew Pryor [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 31 October 2006 9:18 AM
> To: Maven Users List
> Subject: Can a project use a plugin that is part of the 
> project - bootstrap issue
> 
> I am trying to work through a "boot-strap" issue.
> 
> Currently we have a multi-project that includes a 
> maven-plugin module that is then used to build other modules 
> in the multi-project.
> 
> As you might expect a clean checkout & build at the top-level 
> fails because mvn says it can't find the plugin in question 
> (it hasn't been built yet).
> 
> Is there any way to do this? Or do I have to break the plugin 
> out into its own project & build it separately?
> 
> Thanks,
> Matthew
> 
> p.s. I posted this question once before but did so as a reply 
> and was worried it got lost in that noise, apologies for the 
> duplication
> 
> -
> 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: Migrating to a new build machine

[Dan Tran]

I think you may want to provide the topology of your build systems. I saw
your message twice
but still dont get what you want ;-)

-D


On 10/30/06, Prashanth Krishnamurthy <[EMAIL PROTECTED]> wrote:


Hi,

We are planning to move the maven repository to a new
build machine. Is there a recommended process/steps ?
(How to,...etc) Please advise.

(This maven repository is used by 2-3 different
project teams and is very imp for a smooth migration.)

thanks
--Prashanth






Access over 1 million songs - Yahoo! Music Unlimited
(http://music.yahoo.com/unlimited)


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

Problem building project site, please help.

[Russell Healy]

Hello

I am having a problem building my project site. I am using Maven 2.0.4.

Maven messages below are in  elements.

The error message is:




[INFO] Building Generic Application Core
[INFO]task-segment: [site]
[INFO] -
[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] Preparing surefire-report:report
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://cftiw486.winz.govt.nz:8081/internal/nz/govt/msd/generic-app-api/1.0-SN
APSHOT/generic-app-api-1.0-20061030.230311-1.pom
[INFO] ---
[ERROR] BUILD ERROR
[INFO] ---
[INFO] Error building POM (may not be this project's POM).


Project ID: nz.govt.msd:generic-app-api

Reason: Error getting POM for 'nz.govt.msd:generic-app-api' from the
repository:
Error transferring file
  nz.govt.msd:generic-app-api:pom:1.0-20061030.230311-1

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  internal (http://cftiw486.winz.govt.nz:8081/internal)




The pom for generic-app-api definitely exists at:

http://cftiw486.winz.govt.nz:8081/internal/nz/govt/msd/generic-app-api/1.0-SN
APSHOT/generic-app-api-1.0-20061030.230311-1.pom


An earlier error message in the build is:




[WARNING] repository metadata for: 'artifact
org.apache.maven.skins:maven-default-skin' could not be retrieved from
repository: internal due to an error: Error transferring file
[INFO] Repository 'internal' will be blacklisted



Is this the reason Maven cannot find the pom?

If so, I attempted to deploy-file the skin using:

mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=1.0 -Dpackaging=jar
-Dfile=maven-default-skin-1.0.jar -DrepositoryId=internal
-Durl=file://c:/dev/mvn-repositories/internal

And I get this error:




[ERROR] BUILD FAILURE
[INFO] --
[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-default-skin:jar:RELEASE



So (after deleting from my internal repository) I try:

mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar
-Dfile=maven-default-skin-1.0.jar -DrepositoryId=internal
-Durl=file://c:/dev/mvn-repositories/internal


And I get the same error on the project site build:





[ERROR] BUILD FAILURE
[INFO] --
[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-default-skin:jar:RELEASE




Any help would be greatly appreciated.

Thanks and regards,

Russell Healy




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

Problem building project site, please help.

[Russell Healy]

Hello

I am having a problem building my project site. I am using Maven 2.0.4.

Maven messages below are in  elements.

The error message is:




[INFO] Building Generic Application Core
[INFO]task-segment: [site]
[INFO] 


[INFO] Preparing javadoc:javadoc
[INFO] No goals needed for project - skipping
[INFO] Preparing surefire-report:report
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
Downloading: 
http://cftiw486.winz.govt.nz:8081/internal/nz/govt/msd/generic-app-api/1.0-SNAPSHOT/generic-app-api-1.0-20061030.230311-1.pom
[INFO] 


[ERROR] BUILD ERROR
[INFO] 


[INFO] Error building POM (may not be this project's POM).


Project ID: nz.govt.msd:generic-app-api

Reason: Error getting POM for 'nz.govt.msd:generic-app-api' from the 
repository: Error transferring file

  nz.govt.msd:generic-app-api:pom:1.0-20061030.230311-1

from the specified remote repositories:
  central (http://repo1.maven.org/maven2),
  internal (http://cftiw486.winz.govt.nz:8081/internal)




The pom for generic-app-api definitely exists at:

http://cftiw486.winz.govt.nz:8081/internal/nz/govt/msd/generic-app-api/1.0-SNAPSHOT/generic-app-api-1.0-20061030.230311-1.pom


An earlier error message in the build is:




[WARNING] repository metadata for: 'artifact 
org.apache.maven.skins:maven-default-skin' could not be retrieved from 
repository: internal due to an error: Error transferring file

[INFO] Repository 'internal' will be blacklisted



Is this the reason Maven cannot find the pom?

If so, I attempted to deploy-file the skin using:

mvn deploy:deploy-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin -Dversion=1.0 -Dpackaging=jar 
-Dfile=maven-default-skin-1.0.jar -DrepositoryId=internal 
-Durl=file://c:/dev/mvn-repositories/internal


And I get this error:




[ERROR] BUILD FAILURE
[INFO] 


[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin \

-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-default-skin:jar:RELEASE



So (after deleting from my internal repository) I try:

mvn install:install-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar 
-Dfile=maven-default-skin-1.0.jar -DrepositoryId=internal 
-Durl=file://c:/dev/mvn-repositories/internal



And I get the same error on the project site build:





[ERROR] BUILD FAILURE
[INFO] 


[INFO] The skin does not exist: Unable to determine the release version

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.skins 
-DartifactId=maven-default-skin \

-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file


  org.apache.maven.skins:maven-default-skin:jar:RELEASE




Any help would be greatly appreciated.

Thanks and regards,

Russell Healy

---
This email message and any attachment(s) is intended only for the 
person(s) or entity(entities) to whom it is addressed. The 
information it contains may be classified as IN CONFIDENCE and may be

legally privileged. If you are not the intended recipient any use,
disclosure or copying of the message or attachment(s) is strictly 
prohibited. If you have received this message in error please 
notify us immediately and destroy it and any attachment(s).

Thank you. The Ministry of Social Development accepts no
responsibility for changes made to this message or to any
attachment(s) after transmission from the Ministry.
---


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

Re: Problem building project site, please help.

[Russell Healy]

A bit more information - when I remove my internal repository from both my
settings file and my parent pom  section, I am able to
build my project site successfully. Of course, I want to use an internal
repository, so the problem remains.

Does this make sense to anyone?

Thanks

Russell


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

How to create zip of all artifacts during release goal?

[dhoffer]

I have a multi-module maven project and when I run the release goal and
deploy the web site for this project I want to create a zip of the artifacts
and all their dependents.  I would like this zip file to be downloadable
from the deployed web site.

How can I do this?  I have used the assembly plugin in the past but that
requires a different command to be run (not part of release) plus it doesn't
integrate with the web site.  I am not clear how dependency-maven-plugin and
maven-dependency-plugin are to be used (and how they differ).  

What's the best way to do this?
-- 
View this message in context: 
http://www.nabble.com/How-to-create-zip-of-all-artifacts-during-release-goal--tf2543635s177.html#a7087474
Sent from the Maven - Users mailing list archive at Nabble.com.


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

custom dependency mangement

[sumit shah]

Dear Maven Users:

I'm trying to integrate maven 2.0.4 into our projects.  Internally we 
have our own dependency/distribution/packaging mechanism, but would like 
to leverage the power of maven.  I am trying to integrate the use of 
maven with our existing mechanism.  I believe I have most issues sorted 
out except for managing dependencies.  I have a few ideas but I'm not 
sure what the best practice should be and was hoping to get ideas, 
thoughts, or advice on this from the community.


Here are some of my ideas

(1)  Using a custom XML element, instead of :


  junit
  junit
  3.8.1


have something like :


  junit-patched
  junit-patched
  3.8.1


and write a plugin that is aware of our current mechanism. This plugin 
can then add the junit-patched.jar to the classpaths based on the file 
location our existing distribution/packaging mechanism.


(2)  Use a specific groupId in the dependency that would trigger a 
plugin that would add it to the classpath appropriately.


(3)  Use the systemPath mechanism


  junit-patched
  junit-patched
  3.8.1
  system
/customdistributiondeploymentroot/lib/jars/junit.jar



Does this make sense?  The idea is to use the dependencies in their 
current location without the need to copy it into a local repository as 
we have made quite a bit of investment in our current mechanism, since 
we use it for qa, production, launches etc.



Thanks for any insight!


Sumit

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

Re: Migrating to a new build machine

[Max Cooper]

What do you use this repository for, specifically? For example, my team 
has a maven-proxy instance that we use for jars that can't be on public 
repos because of license issues. We have no other "shared" repos.


How does the team access it (web server, Samba share, NFS, ...)?

Where is the configuration stored that indicates that the repo you are 
moving should be used (as part of the pom.xml for your projects, as part 
of each developer's settings.xml, via an abstract name that will need to 
be changed in your DNS server, ...)?


-Max

Prashanth Krishnamurthy wrote:

Hi,

We are planning to move the maven repository to a new
build machine. Is there a recommended process/steps ?
(How to,...etc) Please advise.

(This maven repository is used by 2-3 different
project teams and is very imp for a smooth migration.)

thanks
--Prashanth



 

Access over 1 million songs - Yahoo! Music Unlimited 
(http://music.yahoo.com/unlimited)



-
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: Custom Manifest file

[jiangshachina]

In Web application project, I want to put MANIFEST.MF into
main/resources/META-INF directory(it's the same as that in simply
application project).
And I don't want META-INF/MANIFEST.MF to be copied into
webapp_archive_file/WEB-INF/classes.
How can I achieve that? Use filter file?

a cup of Java, cheers!
Sha Jiang


jiangshachina wrote:
> 
> Of course, I can locate MANIFEST.MF to another directory.
> I just be curious of why application project have not the trouble.
> And I cannot use standard directory structure.
> 
> a cup of Java, cheers!
> Sha Jiang
> 
> 
> 
> jiangshachina wrote:
>> 
>> I find another problem.
>> If the project is Web application, then META-INF/MANIFEST.MF will be
>> inserted into classes directory.
>> Obviously, Maven thinks META-INF/MANIFEST.MF is resource since it's in
>> src/main/resources directory(standard resource path).
>> 
>> How can I cancel the problem?
>> 
>> a cup of Java, cheers!
>> Sha Jiang
>> 
>> 
>> jiangshachina wrote:
>>> 
>>> But I'm failed with the action.
>>> I have an simple application project, and put MANIFEST.MF file into
>>> directory
>>> src/main/resources/META-INF
>>> the file has an entry "Main-Class"
>>> 
>>> But Maven don't add the manifest automatically. I have to do following,
>>> 
>>> 
>>> 
>>> org.apache.maven.plugins
>>> maven-jar-plugin
>>> 
>>> 
>>> 
>>> 
>>> src/main/resources/META-INF/MANIFEST.MF
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> a cup of Java, cheers!
>>> Sha Jiang
>>> 
>>> 
>>> Paul Li-2 wrote:
 
 or you could just add the META-INF/MANIFEST.MF into your resources
 directory ;-)
 
 maven will automatically package it
 
 A bit lazy i know.
 
 Paul
 
 On 4/12/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> Give this a try...
>
> 
>  
>   
> org.apache.maven.plugins
> maven-jar-plugin
> 
>   
> src/main/resources/META-INF/MANIFEST.MF manifestFile>
>
> Wayne
>
> On 4/11/06, Karthik Manimaran <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > How can I include a custom manifest file for a jar file and a WAR
> file?
> >
> > Thanks and regards,
> > Karthik.
> >
> >
>
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Custom-Manifest-file-tf1435329s177.html#a7087688
Sent from the Maven - Users mailing list archive at Nabble.com.


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