date:20080905


Hi Brian

As least "jaxws-tools.jar" is missing, and *apparently* several other jars
that are included in the jaxws-ri lib.

(see
"https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/dependencies.html";)

It was not necessary to manually upload any extra dependencies to my
".m2/repository".  

I guess I'm just trying to determine what "extra steps" I have to take to
have my maven builds work using this new Nexus repository manager.

I had assumed -- perhaps incorrectly -- that if my maven builds worked on my
local workstation using my local ".m2/repository", etc,   then, they should
work equally well when using the Nexus repository manager, etc

Since this is apparently not the case, I'd like some suggestions on what
issues I should expect after transitioning and how to fix them.  

Here is a copy of a test project pom...(below)  
(All I'm trying to do in this test is run the "jaxws-maven-plugin" to
generate java binding classes for a simple wsdl)


http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
  4.0.0
  test.jaxws.maven.plugin
  main
  jar
  0.0.1-SNAPSHOT
  main
  http://maven.apache.org
  


maven2-repository.dev.java.net
Java.net Maven 2 Repository
http://download.java.net/maven/2





maven2-repository.dev.java.net
Java.net Maven 2 Repository
http://download.java.net/maven/2





junit
junit
3.8.1
test


com.sun.xml.ws
jaxws-rt
2.1.3






org.codehaus.mojo
jaxws-maven-plugin
1.10


generate-sources

wsimport





C:/testjaxwsplugin/main/src/main/java

C:/testjaxwsplugin/main/src/main/resources
true



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

1.5
1.5











Brian E. Fox wrote:
> 
> It finds the plugin but not the dependencies. Where are these
> dependencies? Are they also in the 3rd party repo? Do you have any
> routing rules defined that may exclude the 3rd party repo for these
> dependencies?
> 
> If you can paste the logs, it would help. I would recommend bringing the
> discussion over to [EMAIL PROTECTED]
> 
> -Original Message-
> From: sairndain [mailto:[EMAIL PROTECTED] 
> Sent: Friday, September 05, 2008 10:42 PM
> To: users@maven.apache.org
> Subject: What are the pitfalls I must be aware of when switching from my
> local ".m2/repository" to the Nexus server?
> 
> 
> Hi
> 
> I have Maven2 installed on my workstation at work, and it works fine...
> 
> Love it.
> 
> I talked one of our adminstrators into installing Nexus on one of our
> development servers to compliment our Subversion repository.
> 
> As soon as we got Nexus running, I installed the 3rd party artifacts I
> use
> in my existing projects and two 3rd party plugins.
> 
> I decided to test my existing builds using the new Nexus server.
> 
> I found they  broke immediately.  
> 
> The first issue I had was with the jaxws-maven-plugin (version 1.10).
> 
> I had already deployed this plugin to the "3rd party" repository.
> 
> Maven2 "finds" the plugin, but, the "dependencies" are missing.
> 
> Why does the plugin work fine with my local Maven2 repository settings
> on my
> workstation... But, has so much trouble when I point my settings to the
> new
> Nexus repository.
> 
> What are the pitfalls I must be aware of when switching from my local
> ".m2/repository" to the Nexus server?
> 
> Thankyou for any guidance on this!
> 
> sd
> 
> P.S.
> 
> I am using the suggested settings configuration set forth

RE: What are the pitfalls I must be aware of when switching from my local ".m2/repository" to the Nexus server?

It finds the plugin but not the dependencies. Where are these
dependencies? Are they also in the 3rd party repo? Do you have any
routing rules defined that may exclude the 3rd party repo for these
dependencies?

If you can paste the logs, it would help. I would recommend bringing the
discussion over to [EMAIL PROTECTED]

-Original Message-
From: sairndain [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 10:42 PM
To: users@maven.apache.org
Subject: What are the pitfalls I must be aware of when switching from my
local ".m2/repository" to the Nexus server?


Hi

I have Maven2 installed on my workstation at work, and it works fine...

Love it.

I talked one of our adminstrators into installing Nexus on one of our
development servers to compliment our Subversion repository.

As soon as we got Nexus running, I installed the 3rd party artifacts I
use
in my existing projects and two 3rd party plugins.

I decided to test my existing builds using the new Nexus server.

I found they  broke immediately.  

The first issue I had was with the jaxws-maven-plugin (version 1.10).

I had already deployed this plugin to the "3rd party" repository.

Maven2 "finds" the plugin, but, the "dependencies" are missing.

Why does the plugin work fine with my local Maven2 repository settings
on my
workstation... But, has so much trouble when I point my settings to the
new
Nexus repository.

What are the pitfalls I must be aware of when switching from my local
".m2/repository" to the Nexus server?

Thankyou for any guidance on this!

sd

P.S.

I am using the suggested settings configuration set forth in the "Maven:
the
definitive gude" book (chapter 16)...i.e., 


  

  
  nexus-public-snapshots
  public-snapshots
 
http://localhost:8081/nexus/content/groups/public-snapshots


  
  nexus
  *
  http://localhost:8081/nexus/content/groups/public

  
  

  development
  

  central
  http://central
  true
  true

  
 

  central
  http://central
  true
  true

  


  
  public-snapshots
  

  public-snapshots
  http://public-snapshots
  false
  true

  
 

  public-snapshots
  http://public-snapshots
  false
  true

  

  
  
development
  
  

  releases
  userid01
  userid01password
  

  snapshots
  userid01
  userid01password
  

  thirdparty
  userid01
  userid01password
 
  



-- 
View this message in context:
http://n2.nabble.com/What-are-the-pitfalls-I-must-be-aware-of-when-switc
hing-from-my-local-%22.m2-repository%22-to-the-Nexus-server--tp842540p84
2540.html
Sent from the maven users mailing list archive at Nabble.com.


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


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

RE: Can nexus be installed on a windows vista 64-bit O.S.?


Thanks for your reply Brian

Please do let me know whether you can find a workaround on your 64-bit Vista
machine.

Any expertise you can provide is much appreciated.  

(NOTE: I'd dump the 64-bit Vista from my new laptop, but, I'm not certain
how much of a pain it would be to find all the replacement drivers I'd need
to revert to XP, etc)

sd



Brian E. Fox wrote:
> 
> Nexus itself should work just fine on Windows 64bit, but the wrapper
> used to launch it might require a different version of the native code.
> You can get a version of it here:
> http://wrapper.tanukisoftware.org/doc/english/download.jsp
> 
> Barring that, hop over to the [EMAIL PROTECTED] list and we can
> figure out some alternatives to get it launched (it is java after all,
> right? ;-)  )
> 
> I happen to have a new 64bit machine waiting to become my new Ubuntu
> based vmware server, so I could try out the 64bit Vista to see what
> gives.
> 
> -Original Message-
> From: sairndain [mailto:[EMAIL PROTECTED] 
> Sent: Friday, September 05, 2008 10:23 PM
> To: users@maven.apache.org
> Subject: Can nexus be installed on a windows vista 64-bit O.S.?
> 
> 
> Hi 
> 
> I have Windows Vista "Home Premium" 64-bit operating system.
> 
> Just want to know whether Nexus can be installed on a Windows Vista
> 64bit
> O.S.
> 
> I've tried installing Nexus using the "InstallNexus.bat"  (found in the
> "nexus-webapp-1.0.0\bin\jsw\windows-x86-32" directory), but, I get the
> following message
> 
> C:\nexus-webapp-1.0.0\bin\jsw\windows-x86-32>InstallNexus.bat
> wrapper  | OpenSCManager failed - Access is denied. (0x5)
> Press any key to continue . . .
> 
> Then, I tried moving the installation folder -- i.e.,
> "nexus-webapp-1.0.0" 
> --   inside my administrator user directory and trying the install
> again. same thing happened
> 
> Do I need to wait for a windows vista 64bit installer before I can begin
> using Nexus on Windows Vista 64bit operating system?
> 
> Thanks for any help on this.
> 
> sd
> -- 
> View this message in context:
> http://n2.nabble.com/Can-nexus-be-installed-on-a-windows-vista-64-bit-O.
> S.--tp842516p842516.html
> Sent from the maven users mailing list archive at Nabble.com.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://n2.nabble.com/Can-nexus-be-installed-on-a-windows-vista-64-bit-O.S.--tp842516p842561.html
Sent from the maven users mailing list archive at Nabble.com.


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

What are the pitfalls I must be aware of when switching from my local ".m2/repository" to the Nexus server?

I have Maven2 installed on my workstation at work, and it works fine...
Love it.

I talked one of our adminstrators into installing Nexus on one of our
development servers to compliment our Subversion repository.

As soon as we got Nexus running, I installed the 3rd party artifacts I use
in my existing projects and two 3rd party plugins.

I decided to test my existing builds using the new Nexus server.

I found they broke immediately.

The first issue I had was with the jaxws-maven-plugin (version 1.10).

I had already deployed this plugin to the "3rd party" repository.

Maven2 "finds" the plugin, but, the "dependencies" are missing.

Why does the plugin work fine with my local Maven2 repository settings on my
workstation... But, has so much trouble when I point my settings to the new
Nexus repository.

What are the pitfalls I must be aware of when switching from my local
".m2/repository" to the Nexus server?

Thankyou for any guidance on this!

P.S.

I am using the suggested settings configuration set forth in the "Maven: the
definitive gude" book (chapter 16)...i.e.,

nexus-public-snapshots
public-snapshots
http://localhost:8081/nexus/content/groups/public-snapshots

nexus
*
http://localhost:8081/nexus/content/groups/public

development

central
http://central
true
true

public-snapshots

public-snapshots
http://public-snapshots
false
true

development

releases
userid01
userid01password

snapshots
userid01
userid01password

thirdparty
userid01
userid01password

--
View this message in context:
http://n2.nabble.com/What-are-the-pitfalls-I-must-be-aware-of-when-switching-from-my-local-%22.m2-repository%22-to-the-Nexus-server--tp842540p842540.html
Sent from the maven users mailing list archive at Nabble.com.

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

RE: Can nexus be installed on a windows vista 64-bit O.S.?

Nexus itself should work just fine on Windows 64bit, but the wrapper
used to launch it might require a different version of the native code.
You can get a version of it here:
http://wrapper.tanukisoftware.org/doc/english/download.jsp

Barring that, hop over to the [EMAIL PROTECTED] list and we can
figure out some alternatives to get it launched (it is java after all,
right? ;-)  )

I happen to have a new 64bit machine waiting to become my new Ubuntu
based vmware server, so I could try out the 64bit Vista to see what
gives.

-Original Message-
From: sairndain [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 10:23 PM
To: users@maven.apache.org
Subject: Can nexus be installed on a windows vista 64-bit O.S.?


Hi 

I have Windows Vista "Home Premium" 64-bit operating system.

Just want to know whether Nexus can be installed on a Windows Vista
64bit
O.S.

I've tried installing Nexus using the "InstallNexus.bat"  (found in the
"nexus-webapp-1.0.0\bin\jsw\windows-x86-32" directory), but, I get the
following message

C:\nexus-webapp-1.0.0\bin\jsw\windows-x86-32>InstallNexus.bat
wrapper  | OpenSCManager failed - Access is denied. (0x5)
Press any key to continue . . .

Then, I tried moving the installation folder -- i.e.,
"nexus-webapp-1.0.0" 
--   inside my administrator user directory and trying the install
again. same thing happened

Do I need to wait for a windows vista 64bit installer before I can begin
using Nexus on Windows Vista 64bit operating system?

Thanks for any help on this.

sd
-- 
View this message in context:
http://n2.nabble.com/Can-nexus-be-installed-on-a-windows-vista-64-bit-O.
S.--tp842516p842516.html
Sent from the maven users mailing list archive at Nabble.com.


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


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

Can nexus be installed on a windows vista 64-bit O.S.?


Hi 

I have Windows Vista "Home Premium" 64-bit operating system.

Just want to know whether Nexus can be installed on a Windows Vista 64bit
O.S.

I've tried installing Nexus using the "InstallNexus.bat"  (found in the
"nexus-webapp-1.0.0\bin\jsw\windows-x86-32" directory), but, I get the
following message

C:\nexus-webapp-1.0.0\bin\jsw\windows-x86-32>InstallNexus.bat
wrapper  | OpenSCManager failed - Access is denied. (0x5)
Press any key to continue . . .

Then, I tried moving the installation folder -- i.e., "nexus-webapp-1.0.0" 
--   inside my administrator user directory and trying the install
again. same thing happened

Do I need to wait for a windows vista 64bit installer before I can begin
using Nexus on Windows Vista 64bit operating system?

Thanks for any help on this.

sd
-- 
View this message in context: 
http://n2.nabble.com/Can-nexus-be-installed-on-a-windows-vista-64-bit-O.S.--tp842516p842516.html
Sent from the maven users mailing list archive at Nabble.com.


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

Re: Refer to the enclosing project's version in the generated archetype

2008/9/6 jwcarman <[EMAIL PROTECTED]>

>
> Brett,
>
> I apologize, but I don't understand what you mean.  When do I do the
> filtering?  Do I need to put the pom.xml file somewhere else in my project
> structure?  Do I just turn on filtering for the place where my pom.xml lies
> now?



Yes, this is on the right track.

Basically, building an archetype is a normal JAR with resources in a certain
location, so if you add more resources with filtering on, they will also be
added.

eg.

  src/main/filtered-resources
  true


Then in src/main/filtered-resources/archetype-resources/pom.xml:

..

  ...
  @project.version@

...

Hopefully that works out for you.

One trick to watch out for here is that some of the archetype substitutes
might also look like expressions and get filtered. There seem to be problems
with escaping to prevent that happening.

Cheers,
Brett

-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: [Modello] xpp3 not writting an int of zero

2008-09-05 Thread rsf

Great.  Thank you for the link.

After Brett's comments, I created a JIRA issue:
http://jira.codehaus.org/browse/MODELLO-118

-Nate

On Fri, 5 Sep 2008 22:01:00 +0200, Hervé BOUTEMY <[EMAIL PROTECTED]>
wrote:
> see http://xircles.codehaus.org/projects/modello/lists
> 
> regards,
> 
> Hervé
> 
> Le vendredi 05 septembre 2008, [EMAIL PROTECTED] a écrit :
>> Which list would be more appropriate to post?  I have some more question
>> about how Modello is working, but I want to post to the correct list.
>>
>> Thanks,
>> -Nate
>>
>>
>> On Fri, 5 Sep 2008 20:16:00 +1000, "Brett Porter"
> <[EMAIL PROTECTED]>
>>
>> wrote:
>> > this is a bit OT for this list... but the reason it is occurring is
>>
>> because
>>
>> > it doesn't populate if it is the default value. Not sure if there's a
> way
>> > to
>> > force that (other than changing the default).
>> > - Brett
>> >
>> > 2008/9/5 <[EMAIL PROTECTED]>
>> >
>> >> Hello,
>> >>
>> >> I have created a .mdo with a required int attribute of "count", and I
>> >
>> > built
>> >
>> >> with the goals "java" and "xpp3-writer".
>> >>
>> >> Here is the snippet from my .mdo file for the attribute.
>> >>
>> >>  
>> >>   1.0.0
>> >>   count
>> >>   true
>> >>   int
>> >>  
>> >>
>> >> The java objects are all created correctly; however, if I put a zero
>> >
>> > into
>> >
>> >> the count field, it is not outputted in the
>> >> XML.  It does output if I use a non-zero value.  I can see in the
>> >
>> > generated
>> >
>> >> file OutputXpp3Writer.java that it is checking for zero before it
> writes
>> >> the attribute.  I assume this is done to determine if a value has
> been
>> >> written into that field.
>> >>
>> >>  if ( tag.getCount() != 0 )
>> >>  {
>> >>... output attribute ...
>> >>  }
>> >>
>> >>
>> >> Is there something else I should put in the .mdo to force this
> attribute
>> >
>> > to
>> >
>> >> write each time?  I have put in a temporary hack of making that
>> >
>> > attribute a
>> >
>> >> String and used Integer.toString(...) in my code, but I don't think
> this
>> >
>> > is
>> >
>> >> a good long term solution as the XML schema would be incorrect.  Is
>> >
>> > there a
>> >
>> >> better work around?
>> >>
>> >> Thanks,
>> >> -Nate
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> > --
>> > Brett Porter
>> > Blog: http://blogs.exist.com/bporter/
>>
>> -
>> 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: [Modello] xpp3 not writting an int of zero

2008-09-05 Thread Hervé BOUTEMY

see http://xircles.codehaus.org/projects/modello/lists

regards,

Hervé

Le vendredi 05 septembre 2008, [EMAIL PROTECTED] a écrit :
> Which list would be more appropriate to post?  I have some more question
> about how Modello is working, but I want to post to the correct list.
>
> Thanks,
> -Nate
>
>
> On Fri, 5 Sep 2008 20:16:00 +1000, "Brett Porter" <[EMAIL PROTECTED]>
>
> wrote:
> > this is a bit OT for this list... but the reason it is occurring is
>
> because
>
> > it doesn't populate if it is the default value. Not sure if there's a way
> > to
> > force that (other than changing the default).
> > - Brett
> >
> > 2008/9/5 <[EMAIL PROTECTED]>
> >
> >> Hello,
> >>
> >> I have created a .mdo with a required int attribute of "count", and I
> >
> > built
> >
> >> with the goals "java" and "xpp3-writer".
> >>
> >> Here is the snippet from my .mdo file for the attribute.
> >>
> >>  
> >>   1.0.0
> >>   count
> >>   true
> >>   int
> >>  
> >>
> >> The java objects are all created correctly; however, if I put a zero
> >
> > into
> >
> >> the count field, it is not outputted in the
> >> XML.  It does output if I use a non-zero value.  I can see in the
> >
> > generated
> >
> >> file OutputXpp3Writer.java that it is checking for zero before it writes
> >> the attribute.  I assume this is done to determine if a value has been
> >> written into that field.
> >>
> >>  if ( tag.getCount() != 0 )
> >>  {
> >>... output attribute ...
> >>  }
> >>
> >>
> >> Is there something else I should put in the .mdo to force this attribute
> >
> > to
> >
> >> write each time?  I have put in a temporary hack of making that
> >
> > attribute a
> >
> >> String and used Integer.toString(...) in my code, but I don't think this
> >
> > is
> >
> >> a good long term solution as the XML schema would be incorrect.  Is
> >
> > there a
> >
> >> better work around?
> >>
> >> Thanks,
> >> -Nate
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
>
> -
> 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: Deploying a file in deploy phase that was not the pom's main packaging


have a look at build-helper-maven-plugin and the attach artifact goal

Sent from my iPod

On 5 Sep 2008, at 20:38, "Scott Carter" <[EMAIL PROTECTED]>  
wrote:


We have an exec in one of our builds that produces an .exe file.  Of  
course

this is not the main packaging for the pom and is not included in the
standard deploy phase.  I am aware you can use the deploy:deploy- 
file goal
from the command line and see those examples.  My question is if  
there is a
way to configure the deploy:deploy-file goal into the pom and pick  
up this
behavior to deploy our .exe as part of the standard deploy phase or  
by just
adding deploy:deploy-file to the command line and having the  
parameters

stored in the pom.

An example of this would be really helpful.

Thanks


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

Re: from workaround to workaround 1

2008-09-05 Thread Dennis Lundberg

Hi

Instructions on how filtering works in the Resources Plugin can be found
on this page:


http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html


[EMAIL PROTECTED] wrote:
> Hi,
> 
>  
> 
> here is a small story about working with Maven. In my experience of 6 months 
> now this happened very often like this. Maven is very hard to manage, not 
> intuitive and error messages are incomprehensible or misleading.
> 
>  
> 
> The problem: We have 5 Maven projects with sub projects. For test classes, 
> the database connection should be defined only once, we put it into the 
> user's settings.xml. Now, how accessing the db-properties in test classes?
> 
> First idea: Filtering! I created properties file in the test/resources 
> directories and tried to filter db properties from the settings properties 
> with
> 
>  
> 
> 
> 
>   
> 
> src/test/resources
> 
> true
> 
>   
> 
> 
> 
>  
> 
> Nothing happens. Filtering seems to be possible only in main/resources. Then 
> I ask myself why have I to define a  when only one value is 
> working? You could hard-code it. This is not intuitive!
> 
>  
> 
>  
> 
> Freundliche Grüße / Kind regards
> 
>  
> 
> Wolfgang Winter
> 
> System Analyst
> 
> 


-- 
Dennis Lundberg

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

Re: Deploying a file in deploy phase that was not the pom's main packaging

2008-09-05 Thread Wayne Fay

The build-helper plugin helps with things like this, generally.

Wayne

On Fri, Sep 5, 2008 at 12:38 PM, Scott Carter <[EMAIL PROTECTED]> wrote:
> We have an exec in one of our builds that produces an .exe file.  Of course
> this is not the main packaging for the pom and is not included in the
> standard deploy phase.  I am aware you can use the deploy:deploy-file goal
> from the command line and see those examples.  My question is if there is a
> way to configure the deploy:deploy-file goal into the pom and pick up this
> behavior to deploy our .exe as part of the standard deploy phase or by just
> adding deploy:deploy-file to the command line and having the parameters
> stored in the pom.
>
> An example of this would be really helpful.
>
> Thanks
>

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

RE: Deploying a file in deploy phase that was not the pom's main packaging

2008-09-05 Thread Edelson, Justin

I've used the build helper plugin for this in the past:
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html

Justin 

-Original Message-
From: Scott Carter [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 3:39 PM
To: Maven Users List
Subject: Deploying a file in deploy phase that was not the pom's main
packaging

We have an exec in one of our builds that produces an .exe file.  Of
course this is not the main packaging for the pom and is not included in
the standard deploy phase.  I am aware you can use the
deploy:deploy-file goal from the command line and see those examples.
My question is if there is a way to configure the deploy:deploy-file
goal into the pom and pick up this behavior to deploy our .exe as part
of the standard deploy phase or by just adding deploy:deploy-file to the
command line and having the parameters stored in the pom.

An example of this would be really helpful.

Thanks

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

RE: Maven/OS X Development Question

2008-09-05 Thread Martin Gainty


that will only compound the problem as your "user-friendly" MAC will suddenly 
re-appear on your desk
with even more bugs than it had before 

try
mvn -e install

Martin
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


> Date: Fri, 5 Sep 2008 12:22:17 -0500
> From: [EMAIL PROTECTED]
> To: users@maven.apache.org
> Subject: Re: Maven/OS X Development Question
> 
> Hi Scott,
> 
> Thanks for the reply.  I am able to do "regular" java development 
> (Elipse, IntelliJ, ant, JBoss, Tomcat, Geronimo, webapps, ears, jar 
> files etc).  However, when I use *any* version of Maven and perform a 
> "mvn install", I get an error.
> 
> I've documented it here 
> (http://discussions.apple.com/thread.jspa?threadID=1695479&tstart=15) 
> and have spent considerable (far too much) time on it already.
> 
> I've even updated the Java version from the Apple site.  About the only 
> other thing I can think to do, besides throwing my computer from the top 
> of the highest building I can find, is to reinstall OS X.
> 
> Thanks again,
> John
> 
> Scott Ryan wrote:
> > I have exactly that configuration and it has been working fine for over a
> > year.  You might try to see if Appfuse works on it.  Appfuse has an
> > Archetype that will build a totally new self contained running application
> > for you.  Anything I can do to help let me know.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

_
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/

Deploying a file in deploy phase that was not the pom's main packaging

2008-09-05 Thread Scott Carter

We have an exec in one of our builds that produces an .exe file.  Of course
this is not the main packaging for the pom and is not included in the
standard deploy phase.  I am aware you can use the deploy:deploy-file goal
from the command line and see those examples.  My question is if there is a
way to configure the deploy:deploy-file goal into the pom and pick up this
behavior to deploy our .exe as part of the standard deploy phase or by just
adding deploy:deploy-file to the command line and having the parameters
stored in the pom.

An example of this would be really helpful.

Thanks

RE: dependencies.dependency.version is missing

You don't have the version in the dependency or dependencyManagement
section for that exact dependency. I'm a little confused by your
reference to the parent element as it is orthogonal to the dependency.
Does your parent have this version specified properly? Why are you using
org.jboss.seam as your parent?

-Original Message-
From: Nicola Benaglia [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 11:32 AM
To: users@maven.apache.org
Subject: dependencies.dependency.version is missing

Hi,
I am using seam with maven and now I want to use a new version
(2.1.0.BETA1)

On my project's root pom I wrote the new version in:

org.jboss.seam
root
2.1.0.BETA1

In my ejb sub-project I get the error when trying to compile.

'dependencies.dependency.version' is missing for
org.jboss.seam:jboss-seam

Changing again to the previous version (2.1.0.A1), everything is okay.

I cannot figure out what kind of problem is because:
- version is written correctly (as written in 
http://repository.jboss.com/maven2/org/jboss/seam/root/2.1.0.BETA1/root-
2.1.0.BETA1.pom)
- jboss repository is present in my root pom.

Any suggestion please?
Best regards.
N

-
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: from workaround to workaround 3

I'm pretty sure activeByDefault is not used in settings, this is for the
pom only. That's what the activeProfiles section is for.

-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 6:27 AM
To: Maven Users List
Subject: Re: from workaround to workaround 3

On Fri, Sep 5, 2008 at 9:45 AM, <[EMAIL PROTECTED]> wrote:

> >
> > By the way, the settings.xml contains this:
> >   
> > jboss
> > 
> >
>
>
> You need to change this to
>
>  true
>
> as
>
> assert "true".equalsIgnoreCase("") == false;
>
>
> > 
> > 
> >oracle.jdbc.driver.OracleDriver
> >ing_epa
> >ing_epa
> >jdbc:oracle:thin:@deneb:1521:WLP
> >...
> > 
> >   
> >  
> >
> >  
> >jboss
> >  
> >
>
> [Winter, Wolfgang] okay, maybe. But I activated the profile explicitly
> in the last line! Please excuse me when I criticize, but for me this
is
> bad design. This is not what a dumb user like me expects, regardless
of
> the setting of 


Actually no, when you specify  (that is equivalent to
false) which AFAIK is overriding the
 section.

If you had removed the  entirely it would be active

-Stephen

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

RE: from workaround to workaround 3

All you have to do is enable filtering on src/test/resources. I don't believe 
filtering is enabled on src/main/resources by default either.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 2:53 AM
To: users@maven.apache.org
Subject: from workaround to workaround 3

Hi,

This is the third part of: how accessing properties from settings in test 
classes?

Finally I copied the -maven-plugin file by file from the codehaus server into 
our internal repository and now it was found by Maven. However, on running it 
during the generate-test-resources phase nothing happens. Why? I looked into 
the source code of the plugin. It uses project.getActiveProfiles() and this 
method returns an empty list. But I have a profile defined in settings which is 
set active with . Why does the getActiveProfiles() method 
returns zero?

At the end of this frustrating story I wrote a plugin myself which did the task 
of writing all properties from settings into a file in target directory which 
uses ${project.properties} and finally this works but it was a really long way 
for a simple problem.

Freundliche Grüße / Kind regards

Wolfgang Winter

System Analyst

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

RE: Maven/OS X Development Question

2008-09-05 Thread Sean Hennessy

Hi John,

I did not see if the expected  "java -version" matches that of your mvn -x 
output shared.
I recall a link operation ( ln -s ) was required on Mac volume to get newer JDK 
hooked up correctly.

Sean

-Original Message-
From: John [mailto:[EMAIL PROTECTED]
Sent: Friday, September 05, 2008 10:22 AM
To: Maven Users List
Subject: Re: Maven/OS X Development Question

Hi Scott,

Thanks for the reply.  I am able to do "regular" java development (Elipse, 
IntelliJ, ant, JBoss, Tomcat, Geronimo, webapps, ears, jar files etc).  
However, when I use *any* version of Maven and perform a "mvn install", I get 
an error.

I've documented it here
(http://discussions.apple.com/thread.jspa?threadID=1695479&tstart=15)
and have spent considerable (far too much) time on it already.

I've even updated the Java version from the Apple site.  About the only other 
thing I can think to do, besides throwing my computer from the top of the 
highest building I can find, is to reinstall OS X.

Thanks again,
John

Scott Ryan wrote:
> I have exactly that configuration and it has been working fine for
> over a year.  You might try to see if Appfuse works on it.  Appfuse
> has an Archetype that will build a totally new self contained running
> application for you.  Anything I can do to help let me know.

-
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: problem using the buildnumber plugin with maven

the difference is that version has to be evaluated prior to any  
lifecycle phase or plugin execution


if you define a property in your pom it is available when constructing  
the model


the buildnumber plugin is attached to the first phase and the property  
is defined at that point, but by then version had been defined and you  
are stuck


Sent from my iPod

On 5 Sep 2008, at 17:54, Matthias Grunwalde  
<[EMAIL PROTECTED]> wrote:




Wayne, you state that the groupId, artifactId and version are always  
used

when publishing to a repo, so I tried specifying ${buildNumber} as the
version, as in
${buildNumber}

However, this didn't get interpolated correctly, leading to an  
artifact in

my repo called ArtifactId-${buildNumber}.

If I do the same using a "normal" property, as in:
${my.property}
...

  111


Then I get an ArtifactId-111 in my repo.

Does this seem like a bug in the build number plugin, that it isn't
interpolating correctly, or that the ${buildNumber} is a kind of  
property
that doesn't get interpolated when specified in a ...version>

section?

Is this the same problem as
http://jira.codehaus.org/browse/MOJO-909
?

Kind regards,
Matthias.



Wayne Fay wrote:


Sorry, I didn't intend to mislead you. I was only trying to address
part of your question, the "how do I get buildnumber to put its  
number

in my artifact's name during the build" part, not the "how do I get
that artifact installed with that same name" which, as Wendy says, is
not possible.

Artifacts always go into the local repo cache using the groupId,
artifactId, and version you have declared in the pom -- it completely
ignores the finalName.

finalName is only useful for changing the name of a war/ear and then
pulling it out of /target to use it for something else directly.

Wayne



--
View this message in context: 
http://www.nabble.com/problem-using-the-buildnumber-plugin-with-maven-tp17077968p19335391.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



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

Customizable Maven Project

2008-09-05 Thread JoshM


Maven Users -

I'm relatively new to Maven and would like to request guidance on setting up
a project, customizable per client.  The project is a pretty standard
Struts2/Spring project, and we currently control customization using Ant. 
Each "client version" of the product can overwrite a few configuration
files:

CORE PRODUCT

/src...
/resources
--- application.properties // e.g. Contains configuration parameters set at
build/deploy time.
/config
-- ReportRules.xml
-- ReportBuilding.xml
-- /reports
 Sales_Report.xml
 Income_Report.xml

CUSTOM PROJECT

/config
-- ReportBuilding.xml // e.g. Should overwrite the core version when
deployed.
-- /reports
 Sales_Report.xml // e.g. Should overwrite the core version when
deployed.
 Income_Report.xml // e.g. Should be added when deployed.

As you can see, the CUSTOM PROJECT (e.g. for a particular client) has
certain files that should be added (or overwrite) files in the CORE product. 
We have multiple (20+) customized client versions.  I've been reading
documentation at the main Maven site, and have seen some various options:

* WAR Overlay
* Child Modules
* External Resources
* Etc.

I'm struggling with the best approach to make this happen.  I'm not sure if
it's better for the parent (CORE) to point at the possible children (CUSTOM
- which changes per client), or if it's better for the children (CUSTOM) to
point back up at the CORE.

Also, I need to be sure that when we're developing, if we want to build a
CUSTOM version, we can pass configuration parameters that make it into the
application.properties file (defined only at CORE, with tokens).

Please let me know if I can provide any additional information, and I
appreciate any advice or additional places I could look for guidance.

Thank you,
Josh
-- 
View this message in context: 
http://www.nabble.com/Customizable-Maven-Project-tp19337330p19337330.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

RE: Unable to download "org.apache.maven.plugins:maven-dependency-plugin:pom:2.0"

I can't see anything obvious in your config, and ibiblio does have the
file:
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/plugins/m
aven-dependency-plugin/2.0/

So either there is bad metadata in your local repo, or you have some
connection problem/firewall etc.

-Original Message-
From: thomas2004 [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 12:54 PM
To: users@maven.apache.org
Subject: Unable to download
"org.apache.maven.plugins:maven-dependency-plugin:pom:2.0"


Hi all, the following is my pom.xml. As I run mvn clean I got error:

[code]
[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-dependency-plugin
Version: 2.0

Reason: Unable to download the artifact from any repository

  org.apache.maven.plugins:maven-dependency-plugin:pom:2.0

from the specified remote repositories:
  ibiblio.org (http://mirrors.ibiblio.org/pub/mirrors/maven2)


[INFO]

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

[INFO] Total time: 42 seconds
[INFO] Finished at: Fri Sep 05 18:44:00 CEST 2008
[INFO] Final Memory: 1M/3M
[INFO]


[/code]

My "pom.xml":
[code]




maven-dependency-plugin



copy-dependencies
package


copy-dependencies



provided






maven-assembly-plugin


make-assembly
package


attached






assembly.xml





maven-war-plugin




true



WEB-INF/lib/*.jar




[/code]
-- 
View this message in context:
http://www.nabble.com/Unable-to-download-%22org.apache.maven.plugins%3Am
aven-dependency-plugin%3Apom%3A2.0%22-tp19335385p19335385.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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


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

RE: How to disable a plugin?

The inherited flag in the plugin block is broken, but in 2.0.9 we made
sure the inherited flag inside the execution block does work.

-Original Message-
From: youhaodeyi [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 05, 2008 2:40 AM
To: users@maven.apache.org
Subject: How to disable a plugin?


In the parent pom, it includes copy-dependency plugin which I want to
disable
in the child pom. I use this configuration:



org.apache.maven.plugins

maven-dependency-plugin
false


But every time running 'mvn package', it will copy all the dependencies
to
the child module. How can I disable this?
-- 
View this message in context:
http://www.nabble.com/How-to-disable-a-plugin--tp19325716p19325716.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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


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

Re: Maven/OS X Development Question

2008-09-05 Thread John


Hi Scott,

Thanks for the reply.  I am able to do "regular" java development 
(Elipse, IntelliJ, ant, JBoss, Tomcat, Geronimo, webapps, ears, jar 
files etc).  However, when I use *any* version of Maven and perform a 
"mvn install", I get an error.


I've documented it here 
(http://discussions.apple.com/thread.jspa?threadID=1695479&tstart=15) 
and have spent considerable (far too much) time on it already.


I've even updated the Java version from the Apple site.  About the only 
other thing I can think to do, besides throwing my computer from the top 
of the highest building I can find, is to reinstall OS X.


Thanks again,
John

Scott Ryan wrote:

I have exactly that configuration and it has been working fine for over a
year.  You might try to see if Appfuse works on it.  Appfuse has an
Archetype that will build a totally new self contained running application
for you.  Anything I can do to help let me know.


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

Re: m2eclipse's build problem - pmd:cpd doesn't have a default lifecycle phase

2008-09-05 Thread Eugene Kuleshov



  By default m2eclipse is using Maven 2.1-SNAPSHOT, and it seem like you are
hitting into backward incompatibilities with version you are using in the
command line.
  To workaround that you can configure default Maven runtime to use the same
version as you are using in the command line. See Window / Preferences /
Maven / Installations.

  regards,
  Eugene



komadich wrote:
> 
> I am trying to do the "mvn install" from Eclipse. I use the Maven Eclipse
> Plugin. When I try to to run "mvn" with any goal i get this error: 
> 
> [INFO] task-segment: [process-resources]
> [INFO]
> 
> [ERROR] 
> 
> Maven cannot calculate your build plan, given the following information:
> 
> Tasks:
> - process-resources
> 
> Current project:
> Group-Id: com.steria.sib-vis
> Artifact-Id: sib-vis-common
> Version: 2.x-SNAPSHOT
> From file: D:\workspace\SIB-VIS\apps\sib-vis\sib-vis-common\pom.xml
> 
> 
> Error message: Mojo descriptor: pmd:cpd doesn't have a default lifecycle
> phase. Please specify a  for this goal in your POM.
> Root error message: Mojo descriptor: pmd:cpd doesn't have a default
> lifecycle phase. Please specify a  for this goal in your POM.
> 
> 
> I don't get this error when launching Maven commands from the command
> prompt. 
> 

-- 
View this message in context: 
http://www.nabble.com/m2eclipse%27s-build-problem---pmd%3Acpd-doesn%27t-have-a-default-lifecycle-phase-tp19329122p19335863.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Maven/OS X Development Question

2008-09-05 Thread Scott Ryan

I have exactly that configuration and it has been working fine for over a
year.  You might try to see if Appfuse works on it.  Appfuse has an
Archetype that will build a totally new self contained running application
for you.  Anything I can do to help let me know.

Scott Ryan
President/CTO
Soaring Eagle L.L.C.
Highlands Ranch, Co. 80129
(303) 263-3044
[EMAIL PROTECTED]
www.soaringeagleco.com

On Fri, Sep 5, 2008 at 10:20 AM, John <[EMAIL PROTECTED]> wrote:

> Hi,
>
> Is anyone developing using Maven and Java 5 on OS X Leopard with a first
> generation Macbook Pro (MBP) Core Duo?
>
> I am experiencing an odd issue that only seems present on a Core Duo and
> I've tried it on a Core 2 Duo (MBP/OS X Leopard), Windows XP and RHEL Linux
> and only the first gen Core Duo has the issue.
>
> Just curious if anyone else is using a MBP Core Duo for development...
>
> Thanks,
> John
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: problem using the buildnumber plugin with maven

2008-09-05 Thread Matthias Grunwalde

Wayne, you state that the groupId, artifactId and version are always used
when publishing to a repo, so I tried specifying ${buildNumber} as the
version, as in
 ${buildNumber}

However, this didn't get interpolated correctly, leading to an artifact in
my repo called ArtifactId-${buildNumber}.

If I do the same using a "normal" property, as in:
${my.property}
...

   111

Then I get an ArtifactId-111 in my repo.

Does this seem like a bug in the build number plugin, that it isn't
interpolating correctly, or that the ${buildNumber} is a kind of property
that doesn't get interpolated when specified in a ...
section?

Is this the same problem as
http://jira.codehaus.org/browse/MOJO-909
?

Kind regards,
Matthias.

Wayne Fay wrote:
> 
> Sorry, I didn't intend to mislead you. I was only trying to address
> part of your question, the "how do I get buildnumber to put its number
> in my artifact's name during the build" part, not the "how do I get
> that artifact installed with that same name" which, as Wendy says, is
> not possible.
> 
> Artifacts always go into the local repo cache using the groupId,
> artifactId, and version you have declared in the pom -- it completely
> ignores the finalName.
> 
> finalName is only useful for changing the name of a war/ear and then
> pulling it out of /target to use it for something else directly.
> 
> Wayne
> 

-- 
View this message in context: 
http://www.nabble.com/problem-using-the-buildnumber-plugin-with-maven-tp17077968p19335391.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Unable to download "org.apache.maven.plugins:maven-dependency-plugin:pom:2.0"

2008-09-05 Thread thomas2004


Hi all, the following is my pom.xml. As I run mvn clean I got error:

[code]
[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-dependency-plugin
Version: 2.0

Reason: Unable to download the artifact from any repository

  org.apache.maven.plugins:maven-dependency-plugin:pom:2.0

from the specified remote repositories:
  ibiblio.org (http://mirrors.ibiblio.org/pub/mirrors/maven2)


[INFO]

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

[INFO] Total time: 42 seconds
[INFO] Finished at: Fri Sep 05 18:44:00 CEST 2008
[INFO] Final Memory: 1M/3M
[INFO]


[/code]

My "pom.xml":
[code]



maven-dependency-plugin


copy-dependencies
package


copy-dependencies



provided





maven-assembly-plugin


make-assembly
package

attached






assembly.xml




maven-war-plugin




true



WEB-INF/lib/*.jar




[/code]
-- 
View this message in context: 
http://www.nabble.com/Unable-to-download-%22org.apache.maven.plugins%3Amaven-dependency-plugin%3Apom%3A2.0%22-tp19335385p19335385.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Refer to the enclosing project's version in the generated archetype

2008-09-05 Thread jwcarman

Brett,

I apologize, but I don't understand what you mean.  When do I do the
filtering?  Do I need to put the pom.xml file somewhere else in my project
structure?  Do I just turn on filtering for the place where my pom.xml lies
now?

Brett Porter wrote:
> 
> You are best to filter this in when creating the original artifact using
> the
> conventional resource filtering.
> - Brett
> 

-- 
View this message in context: 
http://www.nabble.com/Refer-to-the-enclosing-project%27s-version-in-the-generated-archetype-tp19287364p19335329.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: release:perform fails

2008-09-05 Thread Ken Tanaka


Be sure to issue
svn update
before the "mvn release:perform". This can fix some types of errors, 
even though it prints nothing and an "svn status" command appears to 
show the project up to date.


-Ken

Chris Graham wrote:




Ok, it is attempting to check out this:

http://svn.warpspeed.com.au/svn/repos/FireDragon/tags/FireDragon-1.0.8/

which does not have the complete contents of all of the projects in it (but
I guess that it should...)

so, release:prepare may not be working after all...

-Chris

  



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

Re: Maven/OS X Development Question

2008-09-05 Thread Gert Wohlgemuth


well everything works with mine

maven 2.0.9
java 1.5
osx leopard
1 gb ram


gert wohlgemuth

blog
http://berlinguyinca.blogspot.com

work:
http://fiehnlab.ucdavis.edu/staff/wohlgemuth


On Sep 5, 2008, at 9:20 AM, John <[EMAIL PROTECTED]> wrote:


Hi,

Is anyone developing using Maven and Java 5 on OS X Leopard with a  
first generation Macbook Pro (MBP) Core Duo?


I am experiencing an odd issue that only seems present on a Core Duo  
and I've tried it on a Core 2 Duo (MBP/OS X Leopard), Windows XP and  
RHEL Linux and only the first gen Core Duo has the issue.


Just curious if anyone else is using a MBP Core Duo for development...

Thanks,
John

-
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/OS X Development Question

2008-09-05 Thread John


Hi,

Is anyone developing using Maven and Java 5 on OS X Leopard with a first 
generation Macbook Pro (MBP) Core Duo?


I am experiencing an odd issue that only seems present on a Core Duo and 
I've tried it on a Core 2 Duo (MBP/OS X Leopard), Windows XP and RHEL 
Linux and only the first gen Core Duo has the issue.


Just curious if anyone else is using a MBP Core Duo for development...

Thanks,
John

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

Re: How to merge pom files ?

2008-09-05 Thread John Prystash

You might want to take a look at the shade plugin

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

A configuration like the following should create a jar containing the classes 
from the two t4 jars you depend on:

 
org.apache.maven.plugins
maven-shade-plugin

  
package

  shade


  

  t4:t4-core-utils
  t4:t4-common-utils

  

  

  



- Original Message 
From: Olivier THIERRY <[EMAIL PROTECTED]>
To: users@maven.apache.org
Sent: Friday, September 5, 2008 10:52:00 AM
Subject: How to merge pom files ?

Hi all,

I have two Maven projects named t4-core-utils and t4-core-commons. They
build jar artifacts and install them to my M2 repository.
Now I want to build a jar that merges both jars (extract files from these
jars and add them to a new jar) then install it to M2 repository so that it
can be used as a dependency in other Maven projects.

I tried to use Maven Assembly plugin to achieve this. I could create the new
jar and install it to M2 repo, but I have problems with the way pom file is
generated in M2 repo.

The pom.xml is as following (t4-parent is used for dependency management) :

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

t4
t4-parent
1.0-SNAPSHOT

  1.0-SNAPSHOT
  T4 Core All
 
  
  t4
  t4-core-utils
  ${version}
  
  
  fr.horoquartz.t4
  t4-core-commons
  ${version}
  
  

  
  
  maven-assembly-plugin
  


src/main/assembly/t4-core-all.xml
  
  false
  


package

attached



  
  
  


And the t4-core-all.xml file :


http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0../../../../exchange-ws-api/assembly-1.1.0-SNAPSHOT.xsd
">
t4-core-all
  
jar
  
  false
  
   
   true
   
   
   META-INF/persistence.xml
   META-INF/ejb-jar.xml
   
  
   false

  


src/main/assembly/persistence.xml
META-INF


src/main/assembly/ejb-jar.xml
META-INF




The pom generated for t4-core-all just contains dependencies to
t4-core-utils and t4-core-commons. So when adding t4-core-all as a
dependency, I have all classes twice, in t4-core-all and in t4-core-commons
or t4-core-utils ... Actually what I need is that the pom for t4-core-all
contains transitive dependencies from t4-core-utils and t4-core-commons (for
example hibernate, commons-lang, etc...), and not dependencies to
t4-core-utils and t4-core-commons. A kind of pom merging. Is there a way to
do this ?

Thanks in advance,

Olivier

Re: [Modello] xpp3 not writting an int of zero

2008-09-05 Thread rsf


Which list would be more appropriate to post?  I have some more question
about how Modello is working, but I want to post to the correct list.

Thanks,
-Nate


On Fri, 5 Sep 2008 20:16:00 +1000, "Brett Porter" <[EMAIL PROTECTED]>
wrote:
> this is a bit OT for this list... but the reason it is occurring is
because
> it doesn't populate if it is the default value. Not sure if there's a way
> to
> force that (other than changing the default).
> - Brett
> 
> 2008/9/5 <[EMAIL PROTECTED]>
> 
>> Hello,
>>
>> I have created a .mdo with a required int attribute of "count", and I
> built
>> with the goals "java" and "xpp3-writer".
>>
>> Here is the snippet from my .mdo file for the attribute.
>>
>>  
>>   1.0.0
>>   count
>>   true
>>   int
>>  
>>
>> The java objects are all created correctly; however, if I put a zero
> into
>> the count field, it is not outputted in the
>> XML.  It does output if I use a non-zero value.  I can see in the
> generated
>> file OutputXpp3Writer.java that it is checking for zero before it writes
>> the attribute.  I assume this is done to determine if a value has been
>> written into that field.
>>
>>  if ( tag.getCount() != 0 )
>>  {
>>... output attribute ...
>>  }
>>
>>
>> Is there something else I should put in the .mdo to force this attribute
> to
>> write each time?  I have put in a temporary hack of making that
> attribute a
>> String and used Integer.toString(...) in my code, but I don't think this
> is
>> a good long term solution as the XML schema would be incorrect.  Is
> there a
>> better work around?
>>
>> Thanks,
>> -Nate
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/


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

dependencies.dependency.version is missing

2008-09-05 Thread Nicola Benaglia

Hi,
I am using seam with maven and now I want to use a new version (2.1.0.BETA1)

On my project's root pom I wrote the new version in:


org.jboss.seam
root
2.1.0.BETA1
 

In my ejb sub-project I get the error when trying to compile.

'dependencies.dependency.version' is missing for org.jboss.seam:jboss-seam

Changing again to the previous version (2.1.0.A1), everything is okay.

I cannot figure out what kind of problem is because:
- version is written correctly (as written in 
http://repository.jboss.com/maven2/org/jboss/seam/root/2.1.0.BETA1/root-2.1.0.BETA1.pom)
- jboss repository is present in my root pom.

Any suggestion please?
Best regards.
N

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

Re: Resource filtering in WAR overlays

2008-09-05 Thread Schrodt, Martin

Thank you Rémy, that was the link I needed.

To quote the relevant part:

8<-
In the last war plugin SNAPSHOT, there is now a new configuration
parameter which prevent filtering on file extensions :

  

  pdf

  

The default values are jpg,jpeg,gif,bmp,png
8<-

I think it would be nicer to have a list of explicitly filtered extensions, 
but, this will work reasonably well, too.

Thank you, will try it Monday morning, have a nice weekend!

Martin

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

Re: how, exactly, does maven compare versions

>From my reading of the code, anything with a qualifier is older than
anything without a qualifier

thus 1.01-blah < 1.01


On Fri, Sep 5, 2008 at 2:49 PM, Wim Deblauwe <[EMAIL PROTECTED]> wrote:

> Hi,
>
> we have a kind of strange version mechanism, and I wonder I can 'translate'
> this to maven.
>
> This is how it works:
> E1.01.01
> E1.01.02
> ..
> V1.01
>
> Versions starting with E are test builds leading into the release (V1.01 in
> the example)
>
> Is 1.01 considered newer then 1.01-E01 for example?
>
> regards,
>
> Wim
>
> 2008/9/5 Benjamin Smith-Mannschott <[EMAIL PROTECTED]>
>
> >
> > On Sep 4, 2008, at 22:09, Stephen Connolly wrote:
> >
> >  On Thu, Sep 4, 2008 at 8:52 PM, Benjamin Smith-Mannschott:
> >>
> >>> Yes. That helped, as did
> >>>
> http://docs.codehaus.org/display/MAVEN/Extending+Maven+2.0+Dependencies
> >>>
> >>> Which actually comes out and says that qualifier and build nr are
> >>> mutually
> >>> exclusive. The syntax given says this too, but I wasn't seeing it.
> >>> Another
> >>> way of looking at it, I suppose, is that everything following "1.2.3-"
> is
> >>> taken as single qualifier, which is compared numerically if it happens
> to
> >>> be
> >>> composed only of digits and otherwise compared as a string.
> >>>
> >>
> >>
> >> Yep:
> >>
> >>
> >>
> http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#155
> >>
> >>
> > Aha! thanks! I was grubbing around in the source of the 2.0.x branch
> > yesterday after I wrote my message looking for exactly this class, only I
> > didn't find it. ;-)
> >
> >
> >>> It seems that '.2.3', in the example above is optional, those parts
> taken
> >>> to be zero if missing. If any alphanumerics get mixed up in there or
> >>> about
> >>> without a separating hyphen the whole thing goes textual and is just
> >>> compared as a single string. At least that's what I understood.  So
> >>> presumably, if we're comparing two version strings with eachother and
> one
> >>> is
> >>> "well formed" and the other is not, they just get compared as if they
> >>> were
> >>> both not well formed.
> >>>
> >>
> >>
> >> Nope:
> >>
> >>
> >>
> http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#54
> >>
> >> If one is treated as a string (because it's malformed) the other will
> >> always
> >> be newer (because it has a build number)
> >>
> >
> > Actually, it looks like the build number only enters into it when both
> have
> > a build number, but build number and qualifier are mutually exclusive, so
> > the logic exits early if one has a qualifier and the other doesn't.
> >
> > Somehow that logic makes me a little queezy, but at least it does appear
> to
> > sort consistently.
> >
> >
> > // Ben
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

How to merge pom files ?

2008-09-05 Thread Olivier THIERRY

Hi all,

I have two Maven projects named t4-core-utils and t4-core-commons. They
build jar artifacts and install them to my M2 repository.
Now I want to build a jar that merges both jars (extract files from these
jars and add them to a new jar) then install it to M2 repository so that it
can be used as a dependency in other Maven projects.

I tried to use Maven Assembly plugin to achieve this. I could create the new
jar and install it to M2 repo, but I have problems with the way pom file is
generated in M2 repo.

The pom.xml is as following (t4-parent is used for dependency management) :

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

t4
t4-parent
1.0-SNAPSHOT

  1.0-SNAPSHOT
  T4 Core All
 
  
  t4
  t4-core-utils
  ${version}
  
  
  fr.horoquartz.t4
  t4-core-commons
  ${version}
  
  

  
  
  maven-assembly-plugin
  


src/main/assembly/t4-core-all.xml
  
  false
  


package

attached



  
  
  


And the t4-core-all.xml file :


http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0../../../../exchange-ws-api/assembly-1.1.0-SNAPSHOT.xsd
">
t4-core-all
  
jar
  
  false
  
   
   true
   
   
   META-INF/persistence.xml
   META-INF/ejb-jar.xml
   
  
   false

  


src/main/assembly/persistence.xml
META-INF


src/main/assembly/ejb-jar.xml
META-INF




The pom generated for t4-core-all just contains dependencies to
t4-core-utils and t4-core-commons. So when adding t4-core-all as a
dependency, I have all classes twice, in t4-core-all and in t4-core-commons
or t4-core-utils ... Actually what I need is that the pom for t4-core-all
contains transitive dependencies from t4-core-utils and t4-core-commons (for
example hibernate, commons-lang, etc...), and not dependencies to
t4-core-utils and t4-core-commons. A kind of pom merging. Is there a way to
do this ?

Thanks in advance,

Olivier

Re: Problem of resolving eclipse swt linux library

2008-09-05 Thread lukewpatterson



Andrew Robinson-5 wrote:
> 
> BTW, if you plan on using JFace, do not use the libraries from maven,
> use your own from eclipse. The maven pom files for the uploaded SWT
> and JFace jars are incompatible. I found it much easier to install my
> own jars into my local repo than trying to fight the versions that are
> in the central repositories.
> 

Sounds like a good recommendation.  I regret using the stuff from central
repo. [1]

Best Regards,

Luke

[1] -
http://www.nabble.com/Re%3A-Dependency-problem-for-org.eclipse.core%3Aruntime%3A3.3.100-v20070530-p19332764.html
-- 
View this message in context: 
http://www.nabble.com/Problem-of-resolving-eclipse-swt-linux-library-tp19103219p19332992.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Dependency problem for org.eclipse.core:runtime:3.3.100-v20070530

2008-09-05 Thread lukewpatterson

On a related note, you might want to use the
someEclipseGroupId:Bundle-SymbolicName flavor of the Eclipse dependencies.

I have been looking for "official" answers to the "official" Eclipse
coordinates question, but haven't found any. From my understanding of a
discussion [1] on the dev list, the use of
someEclipseGroupId
someEclipseArtifactId
is discouraged in favor
someEclipseGroupId
Bundle-SymbolicName
So in the case of "runtime", you would use
org.eclipse.core:org.eclipse.core.runtime instead of
org.eclipse.core:runtime.

For the Eclipse stuff, there are no relocation poms deployed in the central
repo which form a relationship between the
someEclipseGroupId:someEclipseArtifactId and
someEclipseGroupId:Bundle-SymbolicName flavors. I don't know if that is a
good thing or a bad thing. In my projects, I chose to use the
someEclipseGroupId:someEclipseArtifactId flavor, and that might have been a
mistake. Now I have deployed projects which contain exclusion filters for
the someEclipseGroupId:Bundle-SymbolicName flavor.

[1] -
http://www.nabble.com/What-is-the-official-Eclipse-repo-layout-(was%3A-How-to-use-central-repo-into-an-Eclipse-project-)-td17396298.html#a17396578
--
View this message in context:
http://www.nabble.com/Dependency-problem-for-org.eclipse.core%3Aruntime%3A3.3.100-v20070530-tp19327179p19332764.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

RE: Problem witrh "Maven Integration for Eclipse"

Since it was uninstalled, it probably removed the m2e nature on that
project. You can reimport it, or I think if you right click it you can
enable the maven management on it.

-Original Message-
From: thomas2004 [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 04, 2008 3:09 AM
To: users@maven.apache.org
Subject: Problem witrh "Maven Integration for Eclipse"

Hi all,

Last week I installed the "Maven Integration for Eclipse" (from
http://m2eclipse.sonatype.org/update) in Eclipse Ganymede and it runs.
I.g.
I can see the maven logo in the context-menu when I right click on a
project.

Yesterday I uninstall the "Maven Integration for Eclipse" because of
some
reason. Today as I installed it again, though I can find the maven from
the
"Installed Software", but I can't see the maven logo any more in the
context-menu when I right click on a project.

Someone knows why?
-- 
View this message in context:
http://www.nabble.com/Problem-witrh-%22Maven-Integration-for-Eclipse%22-
tp19304616p19304616.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

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

Re: how, exactly, does maven compare versions

2008-09-05 Thread Wim Deblauwe

Hi,

we have a kind of strange version mechanism, and I wonder I can 'translate'
this to maven.

This is how it works:
E1.01.01
E1.01.02
..
V1.01

Versions starting with E are test builds leading into the release (V1.01 in
the example)

Is 1.01 considered newer then 1.01-E01 for example?

regards,

Wim

2008/9/5 Benjamin Smith-Mannschott <[EMAIL PROTECTED]>

>
> On Sep 4, 2008, at 22:09, Stephen Connolly wrote:
>
>  On Thu, Sep 4, 2008 at 8:52 PM, Benjamin Smith-Mannschott:
>>
>>> Yes. That helped, as did
>>> http://docs.codehaus.org/display/MAVEN/Extending+Maven+2.0+Dependencies
>>>
>>> Which actually comes out and says that qualifier and build nr are
>>> mutually
>>> exclusive. The syntax given says this too, but I wasn't seeing it.
>>> Another
>>> way of looking at it, I suppose, is that everything following "1.2.3-" is
>>> taken as single qualifier, which is compared numerically if it happens to
>>> be
>>> composed only of digits and otherwise compared as a string.
>>>
>>
>>
>> Yep:
>>
>>
>> http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#155
>>
>>
> Aha! thanks! I was grubbing around in the source of the 2.0.x branch
> yesterday after I wrote my message looking for exactly this class, only I
> didn't find it. ;-)
>
>
>>> It seems that '.2.3', in the example above is optional, those parts taken
>>> to be zero if missing. If any alphanumerics get mixed up in there or
>>> about
>>> without a separating hyphen the whole thing goes textual and is just
>>> compared as a single string. At least that's what I understood.  So
>>> presumably, if we're comparing two version strings with eachother and one
>>> is
>>> "well formed" and the other is not, they just get compared as if they
>>> were
>>> both not well formed.
>>>
>>
>>
>> Nope:
>>
>>
>> http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#54
>>
>> If one is treated as a string (because it's malformed) the other will
>> always
>> be newer (because it has a build number)
>>
>
> Actually, it looks like the build number only enters into it when both have
> a build number, but build number and qualifier are mutually exclusive, so
> the logic exits early if one has a qualifier and the other doesn't.
>
> Somehow that logic makes me a little queezy, but at least it does appear to
> sort consistently.
>
>
> // Ben
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released

Yep, basically 4 digit version numbers are not in the maven format!

On Fri, Sep 5, 2008 at 2:37 PM, Stephen Duncan Jr
<[EMAIL PROTECTED]>wrote:

> On Fri, Sep 5, 2008 at 9:24 AM, Stephen Duncan Jr
> <[EMAIL PROTECTED]>wrote:
>
> > My first attempt to run it gave this output that seems...incorrect:
> >
> > [INFO] The following dependency updates are available:
> > [INFO]   c3p0:c3p0 .. 0.9.1.2 ->
> > 0.9.0
> >
> >
> Sorry about the noise; I see from the FAQ that a fourth digit in a version
> number isn't handled numerically by default...
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>

Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released

2008-09-05 Thread Stephen Duncan Jr

On Fri, Sep 5, 2008 at 9:24 AM, Stephen Duncan Jr
<[EMAIL PROTECTED]>wrote:

> My first attempt to run it gave this output that seems...incorrect:
>
> [INFO] The following dependency updates are available:
> [INFO]   c3p0:c3p0 .. 0.9.1.2 ->
> 0.9.0
>
>
Sorry about the noise; I see from the FAQ that a fourth digit in a version
number isn't handled numerically by default...

-- 
Stephen Duncan Jr
www.stephenduncanjr.com

RE: Dependency problem for org.eclipse.core:runtime:3.3.100-v20070530

2008-09-05 Thread Caraivan Constantin

Hello,

Yeah, I could, but wouldn't it be better to just FIX the problem? I'm
even willing to contact the person responsible for that pom, if I could
just find out who he/she is.

Regards,
___
Costin Caraivan


From: Stephen Connolly [mailto:[EMAIL PROTECTED] 
Sent: 5 septembrie 2008 14:58
To: Maven Users List
Subject: Re: Dependency problem for
org.eclipse.core:runtime:3.3.100-v20070530

Could you not work around the issue with exclusions?

On Fri, Sep 5, 2008 at 11:45 AM, Caraivan Constantin
<[EMAIL PROTECTED]>wrote:

> Hello,
>
> I solved the problem locally, but I need the problem solved on repo1 
> (I can't rely on people I distribute my pom.xmls to change their local

> repositories).
> It goes like this: My build -> org.eclipse.core:runtime -> 
> org.eclipse.equinox:app. org.eclipse.core:runtime, which is public, 
> has an error in the pom.
>
> I don't want to work around the problem because:
> a) it's very hard to do it (due to various issues)
> b) it's just plain better to fix the error upstream
>
> What I want to say: the org.eclipse.core:runtime:3.3.100-v20070530
> currently in the main Maven repo DOES NOT BUILD AT ALL (or at least 
> should not build), considering the pom.xml present there.
>
> Who should I contact to get the problem fixed? Who is responsible for 
> building org.eclipse.core? Or can I send a modified pom.xml containing

> this fix, and someone can upload it after a review? :)
>
> Thank you,
> ___
> Costin Caraivan
>
> -Original Message-
> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
> Sent: 5 septembrie 2008 13:24
> To: Maven Users List
> Subject: Re: Dependency problem for
> org.eclipse.core:runtime:3.3.100-v20070530
>
> Look at the version rules
>
> 1.0.0-anything < 1.0.0
>
> if you set the version range as [1.0.0-,2.0.0) you should be OK


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

Re: Resource filtering in WAR overlays

2008-09-05 Thread Rémy Sanlaville

Hi,

Have a look to this discussion
http://www.nabble.com/damage-image-files-td15431864.html#a15432280.
I think it could help.

Rémy

Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released

2008-09-05 Thread Stephen Duncan Jr

On Thu, Sep 4, 2008 at 7:18 PM, Stephen Connolly <
[EMAIL PROTECTED]> wrote:

> The Mojo team is pleased to announce the release of the Versions Maven
> Plugin, version 1.0-alpha-1.
>
> This plugin allows:
> * the querying for newer versions of plugins used in a project.
> * the querying for newer versions of dependencies used in a project.
> * updating a project's parent to the latest available version
>  (e.g. useful for syncing with corporate poms to ensure the latest is
>  used prior to rolling a release)
> * updating properties defined in a project to the latest version of a
> specific
>  artifact (e.g. for ensuring that a suite of dependencies are all the same
> version)
>
> http://mojo.codehaus.org/versions-maven-plugin/
>
> You can run mvn -up to get the latest version of the plugin, or specify
> the version in your project's plugin configuration:
>
> 
>  org.codehaus.mojo
>  versions-maven-plugin
>  1.0-alpha-1
> 
>
> Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
>
> ** Bug
>* [MVERSIONS-1] - javadoc plugin doesn't have its version specified but
> it has
>* [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> plugins that are not defined in the pom.
>
> ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
>* [MVERSIONS-3] - display-plugin-updates does not identify the plugin
> version as not being provided when derived from the super-pom
>
> Enjoy,
>
> -The Mojo team
>

My first attempt to run it gave this output that seems...incorrect:

[INFO] The following dependency updates are available:
[INFO]   c3p0:c3p0 .. 0.9.1.2 ->
0.9.0


-- 
Stephen Duncan Jr
www.stephenduncanjr.com

Resource filtering in WAR overlays

2008-09-05 Thread Schrodt, Martin

Hi List,

I am successfully using resources filtering in a WAR overlay
(maven-war-plugin 2.1-alpha-2). I enabled it using the filtered=true
attribute like this:


  example
  application
  true


The process is also described here:
http://www.nabble.com/War-Overlays-and-resources-filtering-td15272334.ht
ml

However, when enabling filtering, it seems ALL the files from the base
WAR are filtered, sadly including some JAR-files that get corrupted
during the process. So, simple question: Is there a way to limit the
filtering
 
a) to some filetypes (for example *.properties)
b) to some base WAR directories (non recursive WEB-INF/classes only)

?

Thank you!
Martin

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

Re: Dependency problem for org.eclipse.core:runtime:3.3.100-v20070530

Could you not work around the issue with exclusions?

On Fri, Sep 5, 2008 at 11:45 AM, Caraivan Constantin <[EMAIL PROTECTED]>wrote:

> Hello,
>
> I solved the problem locally, but I need the problem solved on repo1 (I
> can't rely on people I distribute my pom.xmls to change their local
> repositories).
> It goes like this: My build -> org.eclipse.core:runtime ->
> org.eclipse.equinox:app. org.eclipse.core:runtime, which is public, has
> an error in the pom.
>
> I don't want to work around the problem because:
> a) it's very hard to do it (due to various issues)
> b) it's just plain better to fix the error upstream
>
> What I want to say: the org.eclipse.core:runtime:3.3.100-v20070530
> currently in the main Maven repo DOES NOT BUILD AT ALL (or at least
> should not build), considering the pom.xml present there.
>
> Who should I contact to get the problem fixed? Who is responsible for
> building org.eclipse.core? Or can I send a modified pom.xml containing
> this fix, and someone can upload it after a review? :)
>
> Thank you,
> ___
> Costin Caraivan
>
> -Original Message-
> From: Stephen Connolly [mailto:[EMAIL PROTECTED]
> Sent: 5 septembrie 2008 13:24
> To: Maven Users List
> Subject: Re: Dependency problem for
> org.eclipse.core:runtime:3.3.100-v20070530
>
> Look at the version rules
>
> 1.0.0-anything < 1.0.0
>
> if you set the version range as [1.0.0-,2.0.0) you should be OK
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

m2eclipse's build problem - pmd:cpd doesn't have a default lifecycle phase

2008-09-05 Thread komadich


Hi, 

I am trying to do the "mvn install" from Eclipse. I use the Maven Eclipse
Plugin. When I try to to run "mvn" with any goal i get this error: 

[INFO] task-segment: [process-resources]
[INFO]

[ERROR] 

Maven cannot calculate your build plan, given the following information:

Tasks:
- process-resources

Current project:
Group-Id: com.steria.sib-vis
Artifact-Id: sib-vis-common
Version: 2.x-SNAPSHOT
>From file: D:\workspace\SIB-VIS\apps\sib-vis\sib-vis-common\pom.xml


Error message: Mojo descriptor: pmd:cpd doesn't have a default lifecycle
phase. Please specify a  for this goal in your POM.
Root error message: Mojo descriptor: pmd:cpd doesn't have a default
lifecycle phase. Please specify a  for this goal in your POM.


I don't get this error when launching Maven commands from the command
prompt. 
-- 
View this message in context: 
http://www.nabble.com/m2eclipse%27s-build-problem---pmd%3Acpd-doesn%27t-have-a-default-lifecycle-phase-tp19329122p19329122.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Refer to the enclosing project's version in the generated archetype

You are best to filter this in when creating the original artifact using the
conventional resource filtering.
- Brett

2008/9/5 jwcarman <[EMAIL PROTECTED]>

>
> Brett,
>
> Yes, I want it to be the same as the version of the archetype (I tried
> ${archetypeVersion}, but that stays as it is too).  The archeytpe has a
> "sibiling" which is my "core library."
>
>
> Brett Porter wrote:
> >
> > Sorry, I misunderstood that it was actually inside the archetype. Do you
> > want it to be replaced with the version of the archetype (that should
> > probably be filtered in at build time), or to be the one that is prompted
> > for when generating the archetype project (${version} instead)?
> > Cheers,
> > Brett
> >
> --
> View this message in context:
> http://www.nabble.com/Refer-to-the-enclosing-project%27s-version-in-the-generated-archetype-tp19287364p19329034.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: Refer to the enclosing project's version in the generated archetype

2008-09-05 Thread jwcarman


Brett,

Yes, I want it to be the same as the version of the archetype (I tried
${archetypeVersion}, but that stays as it is too).  The archeytpe has a
"sibiling" which is my "core library."  


Brett Porter wrote:
> 
> Sorry, I misunderstood that it was actually inside the archetype. Do you
> want it to be replaced with the version of the archetype (that should
> probably be filtered in at build time), or to be the one that is prompted
> for when generating the archetype project (${version} instead)?
> Cheers,
> Brett
> 
-- 
View this message in context: 
http://www.nabble.com/Refer-to-the-enclosing-project%27s-version-in-the-generated-archetype-tp19287364p19329034.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Refer to the enclosing project's version in the generated archetype

Sorry, I misunderstood that it was actually inside the archetype. Do you
want it to be replaced with the version of the archetype (that should
probably be filtered in at build time), or to be the one that is prompted
for when generating the archetype project (${version} instead)?
Cheers,
Brett

2008/9/5 jwcarman <[EMAIL PROTECTED]>

>
> Brett,
>
> That actually doesn't get translated for me (that was the first thing I
> tried).  It shows up in the resulting pom when I generate a project from
> the
> archetype exactly as you typed it.
>
>
> Brett Porter wrote:
> >
> > ${project.version}
> >
>
> --
> View this message in context:
> http://www.nabble.com/Refer-to-the-enclosing-project%27s-version-in-the-generated-archetype-tp19287364p19328727.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

RE: Dependency problem for org.eclipse.core:runtime:3.3.100-v20070530

2008-09-05 Thread Caraivan Constantin

Hello,

I solved the problem locally, but I need the problem solved on repo1 (I
can't rely on people I distribute my pom.xmls to change their local
repositories). 
It goes like this: My build -> org.eclipse.core:runtime ->
org.eclipse.equinox:app. org.eclipse.core:runtime, which is public, has
an error in the pom.

I don't want to work around the problem because:
a) it's very hard to do it (due to various issues)
b) it's just plain better to fix the error upstream

What I want to say: the org.eclipse.core:runtime:3.3.100-v20070530
currently in the main Maven repo DOES NOT BUILD AT ALL (or at least
should not build), considering the pom.xml present there.

Who should I contact to get the problem fixed? Who is responsible for
building org.eclipse.core? Or can I send a modified pom.xml containing
this fix, and someone can upload it after a review? :)

Thank you,
___
Costin Caraivan

-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED] 
Sent: 5 septembrie 2008 13:24
To: Maven Users List
Subject: Re: Dependency problem for
org.eclipse.core:runtime:3.3.100-v20070530

Look at the version rules

1.0.0-anything < 1.0.0

if you set the version range as [1.0.0-,2.0.0) you should be OK

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

Re: Refer to the enclosing project's version in the generated archetype

2008-09-05 Thread jwcarman

Brett,

That actually doesn't get translated for me (that was the first thing I
tried).  It shows up in the resulting pom when I generate a project from the
archetype exactly as you typed it.   

Brett Porter wrote:
> 
> ${project.version}
> 

-- 
View this message in context: 
http://www.nabble.com/Refer-to-the-enclosing-project%27s-version-in-the-generated-archetype-tp19287364p19328727.html
Sent from the Maven - Users mailing list archive at Nabble.com.

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

Re: from workaround to workaround 3

On Fri, Sep 5, 2008 at 9:45 AM, <[EMAIL PROTECTED]> wrote:

> >
> > By the way, the settings.xml contains this:
> >   
> > jboss
> > 
> >
>
>
> You need to change this to
>
>  true
>
> as
>
> assert "true".equalsIgnoreCase("") == false;
>
>
> > 
> > 
> >oracle.jdbc.driver.OracleDriver
> >ing_epa
> >ing_epa
> >jdbc:oracle:thin:@deneb:1521:WLP
> >...
> > 
> >   
> >  
> >
> >  
> >jboss
> >  
> >
>
> [Winter, Wolfgang] okay, maybe. But I activated the profile explicitly
> in the last line! Please excuse me when I criticize, but for me this is
> bad design. This is not what a dumb user like me expects, regardless of
> the setting of 


Actually no, when you specify  (that is equivalent to
false) which AFAIK is overriding the
 section.

If you had removed the  entirely it would be active

-Stephen

Re: Dependency problem for org.eclipse.core:runtime:3.3.100-v20070530

Look at the version rules

1.0.0-anything < 1.0.0

if you set the version range as [1.0.0-,2.0.0) you should be OK

On Fri, Sep 5, 2008 at 9:39 AM, Caraivan Constantin <[EMAIL PROTECTED]>wrote:

> Hello,
>
> I'm new to this list, so here it goes :)
>
> I'm using repo1.maven.org and I need org.eclipse.core:runtime, version
> 3.3.100-v20070530 for a build. Unfortunately there are some dependency
> problems, and the build fails. I'll explain the problems:
>
> I have this in the org.eclipse.core:runtime pom.xml:
>
> 
>org.eclipse.equinox
>app
>[1.0.0,2.0.0)
> 
>
> The version of this dependency that is in repo1 is 1.0.0-v20070606:
>
> org.eclipse.equinox
> app
> 1.0.0-v20070606
>
> This causes the version check to fail and the build fails too.
>
> Do you have any ideas about how I can solve this, or who I need to
> contact to solve the problem?
>
> Thank you,
> ___
> Costin Caraivan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Modello] xpp3 not writting an int of zero

this is a bit OT for this list... but the reason it is occurring is because
it doesn't populate if it is the default value. Not sure if there's a way to
force that (other than changing the default).
- Brett

2008/9/5 <[EMAIL PROTECTED]>

> Hello,
>
> I have created a .mdo with a required int attribute of "count", and I built
> with the goals "java" and "xpp3-writer".
>
> Here is the snippet from my .mdo file for the attribute.
>
>  
>   1.0.0
>   count
>   true
>   int
>  
>
> The java objects are all created correctly; however, if I put a zero into
> the count field, it is not outputted in the
> XML.  It does output if I use a non-zero value.  I can see in the generated
> file OutputXpp3Writer.java that it is checking for zero before it writes
> the attribute.  I assume this is done to determine if a value has been
> written into that field.
>
>  if ( tag.getCount() != 0 )
>  {
>... output attribute ...
>  }
>
>
> Is there something else I should put in the .mdo to force this attribute to
> write each time?  I have put in a temporary hack of making that attribute a
> String and used Integer.toString(...) in my code, but I don't think this is
> a good long term solution as the XML schema would be incorrect.  Is there a
> better work around?
>
> Thanks,
> -Nate
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: Downloading POM and JAR of plugin

I think this is a known bug that it uses the repositories for POMs instead
of the pluginRepositories in some circumstances.
You can add a normal repository definition for your internal repository.
Probably a better solution is to use mirroring to delegate all requests to
your internal repositories, and configure a repository manager to handle
which should be served internally and which should be downloaded.

Cheers,
Brett

2008/9/5 JH <[EMAIL PROTECTED]>

>
> Hi all,
>
> I made some adjustments to a plugin and deployed it in our own repository.
> Another project uses the plugin and has an additional pluginrepository
> defined to use the plugin. For some reason, the JAR gets fetched correctly,
> but the POM never makes it to the client. Result is a number of missing
> dependencies when the plugin tries to run. I've noticed this when running
> the install goal (plugin is configured to run within install phase)
>
> [INFO] artifact org.codehaus.mojo.webstart:webstart-maven-plugin: checking
> for updates from internal-deploy
> [INFO] artifact org.codehaus.mojo.webstart:webstart-maven-plugin: checking
> for updates from central
> Downloading:
>
> http://repo1.maven.org/maven2/org/codehaus/mojo/webstart/webstart-maven-plugin/1.0-alpha-2-custom-20080904/webstart-maven-plugin-1.0-alpha-2-custom-20080904.pom
> Downloading:
>
> http://mvn.internal.com/maven2/deploy/org/codehaus/mojo/webstart/webstart-maven-plugin/1.0-alpha-2-custom-20080904/webstart-maven-plugin-1.0-alpha-2-custom-20080904.jar
> 64Kdownloaded
>
> I'm not really sure why the pom and jar get different urls to download
> from,
> seems like a bug to me. I also thought that the first plugin repository
> would get the job, and this should be our internal repository. If nothing
> is
> found, the next one is tried (in this case the central repo). Isn't this
> correct?
>
> Any pointers on this one? I'm using maven 2.0.9 on Ubuntu 8.04.
>
> Kind Regards,
> Jan
> --
> View this message in context:
> http://www.nabble.com/Downloading-POM-and-JAR-of-plugin-tp19309819p19309819.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: mvn compile works mvn site-deploy causes complation error

it appears the site deploy is using different source code or different
plugins to compilation. Which report is causing the failure? Does the nature
of the compile error indicate the problem?
Unfortunately the information in your mail is not enough to go on much
further.

Good luck,
Brett

2008/9/4 <[EMAIL PROTECTED]>

> Hello,
>
> i try to setup my multi module project. I am trying to setup the site
> generation after all compile dependencies are now resolved and no compile
> error is caused durring mvn compile.
> When i do a mvn site-deploy i get a compile error, anyone has a clue what
> the heck is going on ? Also a mvn clean before does not fix this problem :/
>
> best regards,
> Jens
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: release-plugin: dependency version not adjusted within

this is typical as the profile is not considered part of the build unless
activated.
However, it seems reasonable to adjust profile dependencies in the way you
indicated, so I'd say it's a bug you can file.

To workaround it, I suggest putting the value in a property outside the
profile so that it should be updated.

Cheers,
Brett

2008/9/4 Cla Emanuel Monsch <[EMAIL PROTECTED]>

> hi there
>
> while executing release:prepare the versions of dependencies to submodules
> are adjusted correct. but they're just adapted to the new version if they
> are not defined within a  section.
> the profile 'jboss' was activated correct. i've checked that with
> help:active-profiles.
>
> ---
> have a look at this section of the pom.xml.tag file.
>
> release version: esp-blabla-1.0
> current dev version: 1.0.0-SNAPSHOT
>
> adjusted correct:
>
>  
> 
>ch.abc.project1
>esp-business-logic
>esp-blabla-1.0
>esp-ejb-jboss
> 
>  
>
>
>
> not adjusted:
>
>  
>  
>
>  jboss
>  
>
>  ch.abc.project1
>  esp-business-logic
>  1.0.0-SNAPSHOT
>  esp-ejb-jboss
>
>  
>
>
>
> any ideas?
>
> thanks,
> cla
>
>
> --
> Projekt «Robot Team Challenge»: Wir fördern den Nachwuchs
> www.informatica08.ch/robot
>
> Cla Emanuel Monsch | [EMAIL PROTECTED]
> phone +41-44-247 79 06 | fax +41-44-247 70 75
> Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: Refer to the enclosing project's version in the generated archetype

${project.version}

2008/9/3 jwcarman <[EMAIL PROTECTED]>

>
> I have a project that contains a core library and a couple of archetypes
> that
> I want to use it.  How do I put a dependency in my archetypes that says
> "use
> the core library from the same version as me"?  Does that make sense?
> --
> View this message in context:
> http://www.nabble.com/Refer-to-the-enclosing-project%27s-version-in-the-generated-archetype-tp19287364p19287364.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released

Yes, Archiva will proxy and merge the metadata as well if configured to do
so.
- Brett

2008/9/5 Stephen Connolly <[EMAIL PROTECTED]>

> That is a good question...
>
> I would think that when you ask for the latest maven-metatdata.xml archivia
> will check if it's cache is out of date and then query central...
>
> if you do mvn -U do you get the latest version of a plugin automatically
> (if
> yes, then the answer is yes, if no then the answer is no)
>
> FYI, we're using nexus and have no issues in this regard
>
> -Stephen
>
> On Fri, Sep 5, 2008 at 7:46 AM, Wim Deblauwe <[EMAIL PROTECTED]>
> wrote:
>
> > Does it work if you are not using the central repo directly but a
> > repository
> > manager (archiva in my case) in between. Will this plugin "see" the newer
> > versions, even if they are not in archiva yet?
> >
> > regards,
> >
> > Wim
> >
> > 2008/9/5 Stephen Connolly <[EMAIL PROTECTED]>
> >
> > > The Mojo team is pleased to announce the release of the Versions Maven
> > > Plugin, version 1.0-alpha-1.
> > >
> > > This plugin allows:
> > > * the querying for newer versions of plugins used in a project.
> > > * the querying for newer versions of dependencies used in a project.
> > > * updating a project's parent to the latest available version
> > >  (e.g. useful for syncing with corporate poms to ensure the latest is
> > >  used prior to rolling a release)
> > > * updating properties defined in a project to the latest version of a
> > > specific
> > >  artifact (e.g. for ensuring that a suite of dependencies are all the
> > same
> > > version)
> > >
> > > http://mojo.codehaus.org/versions-maven-plugin/
> > >
> > > You can run mvn -up to get the latest version of the plugin, or specify
> > > the version in your project's plugin configuration:
> > >
> > > 
> > >  org.codehaus.mojo
> > >  versions-maven-plugin
> > >  1.0-alpha-1
> > > 
> > >
> > > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> > >
> > > ** Bug
> > >* [MVERSIONS-1] - javadoc plugin doesn't have its version specified
> > but
> > > it has
> > >* [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> > > plugins that are not defined in the pom.
> > >
> > > ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> > >* [MVERSIONS-3] - display-plugin-updates does not identify the
> plugin
> > > version as not being provided when derived from the super-pom
> > >
> > > Enjoy,
> > >
> > > -The Mojo team
> > >
> >
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

Re: from workaround to workaround 1

On Friday 05 September 2008 [EMAIL PROTECTED] wrote:
> But for me the
> problem is not only documentation but also a user-friendly design. Take
> the filtering example: For main/resources you have
> main/resources ... And for test/resources you have
> to say
> test/resources ...
> This is redundant information in the configuration! I am not used to have
> such redundancies. It is not what I (and probably many developers)
> expect.

I didn't test it now, but usually the defaults are quite intuitive. And
that's also what [0] says. So you don't have to specify the directory
if you use mavens default structure.

regards,
- martin

[0] 
http://maven.apache.org/plugins/maven-resources-plugin/examples/resource-directory.html

signature.asc
Description: This is a digitally signed message part.

Re: Plugin development : how to get the Model from an Artifact

2008-09-05 Thread Julien Graglia

Le vendredi 05 septembre 2008 à 10:48 +0200, Julien Graglia a écrit :
> Hi, I wonder how to get the org.apache.maven.model.Model from an
> org.apache.maven.artifact.Artifact ??
> 

I reply to myself ... I just found how to do that : 
see
http://bensherlock.co.uk/projects/software-engineering/java-webapp/writing-a-maven-plugin

Component needed : 

/**
 * @component role="org.apache.maven.project.MavenProjectBuilder"
 * @required
 */
private MavenProjectBuilder mavenProjectBuilder;

/**
 * @parameter expression="${project.remoteArtifactRepositories}"
 * @required
 * @readonly
 */
private List remoteArtifactRepositories;

/**
 * The artifact repository to use.
 * @parameter expression="${localRepository}"
 * @required
 * @readonly
 */
private ArtifactRepository localRepository;

Code : 

getLog().info("Project : getArtifacts:  " + 
project.getArtifacts().size());
for (final Artifact artifact : (Set) 
project.getArtifacts()) {
getLog().info("" + artifact + ", " + 
artifact.getClass());
try {
final MavenProject aProject = 
mavenProjectBuilder.buildFromRepository(artifact,
remoteArtifactRepositories, 
localRepository);
 // !yes!
} catch (final ProjectBuildingException ex) {
getLog().error("Unable to load project for 
artifact " + artifact, ex);
// TODO handle ex!
}
}


-- 
Julien Graglia - NetCeler



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

Re: Generate file that lists module jars

the plugin doesn't have this sort of capability - it would instead require
making a plugin to write the file itself and including that in the assembly.
- Brett

2008/9/1 Frank Durden <[EMAIL PROTECTED]>

> Hi,
>
> When making a zip assembly, I'd need to generate a file that contains a
> list
> of the modules contained in the zip (just the modules, not the transitive
> dependencies). So if my pom has:
>
>
>moduleA
>moduleB
>
>
> I'd get a file (e.g modules.txt) in the zip that would say:
>
> moduleA-0.0.1.jar
> moduleB-0.0.1.jar
>
> Any pointers to a plugin that could do that or any other help would be
> greatly appreciated. Thanks!
>
> --
> FD
>



-- 
Brett Porter
Blog: http://blogs.exist.com/bporter/

AW: from workaround to workaround 1

[Winter, Wolfgang] Hi all, thanks for your answers and sorry if I started this 
more general criticism about Maven. I am only a dumb user who just started 
setting up projects with Maven and it is really a great tool concerning project 
structuring and building. And Rainer is probably right when he states all you 
need is there but not easy to find.
But for me the problem is not only documentation but also a user-friendly 
design. Take the filtering example: For main/resources you have 
main/resources ...
And for test/resources you have to say
test/resources ...
This is redundant information in the configuration! I am not used to have such 
redundancies. It is not what I (and probably many developers) expect. If you 
design this more obvious and intuitive lacks in documentation are much less 
bothering.

-Ursprüngliche Nachricht-
Von: Rainer Pruy [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 5. September 2008 10:40
An: Maven Users List
Betreff: Re: from workaround to workaround 1

After all,
I consider this classical paradigm of "all you need is there, just obstructed 
by details all over".

"Filtering did not work" because  does filtering for mainstream, but 
Wolfgang needed filtering for "test".
If you know what to look for, this distinction is quite obvious from the docs.
But for the hurrying user trying to overcome an immediate problem, this is 
easily to be overlooked.

This is (implicit) reason to a number of complaints in maven related lists.
Due to the distributed and fine-grain nature of maven and it's plugins.
Information is spread across numerous locations without much "interconnection" 
of semantics.
For "using" a plugin, it is always implied the (potential) user is absolutely 
aware of any implications of the interaction of that
plugin with the rest of the maven "runtime".

Probably we can keep that in mind when working on documentation:

- explicitly state the environment and effects of a plugin
- always encourage users/readers to "get the overall picture" first (or restate 
the essentials?)

May be that will improve "user experience" in the long.

As in most cases the problem is not some feature not being "available",
but some wanted feature not being discoverable easily (esp. if it has to be 
constructed using several existing components).
And maven has a lot of bricks to build from. but also a lot of points to get 
something plugged to.
And is not (always) quite obvious to the ordinary "user" what effects are 
possible and what needs something new.

Regards
Rainer

Asgeir S. Nilsen schrieb:
> Wolfgang,
> For test resources you should use the  element, not the
>  element.  The documentation is a bit shallow on this matter.
> 
> Asgeir
> 
> On Fri, Sep 5, 2008 at 08:46, <[EMAIL PROTECTED]> wrote:
> 
>> Hi,
>>
>>
>>
>> here is a small story about working with Maven. In my experience of 6
>> months now this happened very often like this. Maven is very hard to manage,
>> not intuitive and error messages are incomprehensible or misleading.
>>
>>
>>
>> The problem: We have 5 Maven projects with sub projects. For test classes,
>> the database connection should be defined only once, we put it into the
>> user's settings.xml. Now, how accessing the db-properties in test classes?
>>
>> First idea: Filtering! I created properties file in the test/resources
>> directories and tried to filter db properties from the settings properties
>> with
>>
>>
>>
>> 
>>
>>  
>>
>>src/test/resources
>>
>>true
>>
>>  
>>
>> 
>>
>>
>>
>> Nothing happens. Filtering seems to be possible only in main/resources.
>> Then I ask myself why have I to define a  when only one value is
>> working? You could hard-code it. This is not intuitive!
>>
>>
>>
>>
>>
>> Freundliche Grüße / Kind regards
>>
>>
>>
>> Wolfgang Winter
>>
>> System Analyst
>>
>>

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

Plugin development : how to get the Model from an Artifact

2008-09-05 Thread Julien Graglia

Hi, I wonder how to get the org.apache.maven.model.Model from an
org.apache.maven.artifact.Artifact ??


getLog().info("Project : getArtifacts:  " + project.getArtifacts().size());
for (final Artifact artifact : (Set) project.getArtifacts()) {
getLog().info("" + artifact + ", " + artifact.getClass());
Model m = ;

}

Thx!


-- 
Julien Graglia - NetCeler
tel : 04-92-57-12-12


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

AW: from workaround to workaround 3

>
> > I looked into the source code of the plugin. It uses
> > project.getActiveProfiles() and this method returns an empty list.
But
> I
> > have a profile defined in settings which is set active with
> > . Why does the getActiveProfiles() method returns
zero?
>
> Try using the maven-help-plugin to find out some details. The goal
> help:active-profiles shows you which profiles are active.
>
> help:effective-pom and help:effective-settings show you the effective
> pom.xml resp. settings.xml file. Are your profiles defined there?
>
> You really don't need to write your own plugin just for filtering some
> resource-files.
>
> hth,
> - martin
>
> [Winter, Wolfgang] help:active-profiles executed on the parent pom:
> Active Profiles for Project 'net.atos.wlp:core:pom:0.0.1-SNAPSHOT':
> There are no active profiles.
> Active Profiles for Project
> 'net.atos.wlp:plugin-setproperties:maven-plugin:0.0.1-SNAPSHOT':
> There are no active profiles.
> Active Profiles for Project
> 'net.atos.wlp:core-database:jar:0.0.1-SNAPSHOT':
> There are no active profiles.
> ...
>
> Profiles are configured in the users/settings.xml so
help:effective-pom
> gives no information about profiles
>
> Execution of help:effective-settings: The workaround story continues:
> [ERROR] org.apache.maven.plugins.help.EffectiveSettingsMojo#execute()
> caused a linkage error (java.lang.NoSuchMethodError). Check the
realms:
>
> NOTE:
> Plugin realm is:
> /plugins/org.apache.maven.plugins:maven-help-plugin:[EMAIL 
> PROTECTED]/thread:main
> Container realm is: plexus.core
>
> Realm ID:
> /plugins/org.apache.maven.plugins:maven-help-plugin:[EMAIL 
> PROTECTED]/thread:main
> urls[0] =
>
file:/D:/projekte/maven-repository/org/apache/maven/plugins/maven-help-p
> lugin/2.1/maven-help-plugin-2.1.jar
> urls[1] =
>
file:/D:/projekte/maven-repository/org/codehaus/plexus/plexus-utils/1.5.
> 6/plexus-utils-1.5.6.jar
> urls[2] =
> file:/D:/projekte/maven-repository/junit/junit/3.8.1/junit-3.8.1.jar
> urls[3] =
>
file:/D:/projekte/maven-repository/org/apache/maven/wagon/wagon-http-sha
> red/1.0-beta-2/wagon-http-shared-1.0-beta-2.jar
> urls[4] =
>
file:/D:/projekte/maven-repository/jtidy/jtidy/4aug2000r7-dev/jtidy-4aug
> 2000r7-dev.jar
> urls[5] =
>
file:/D:/projekte/maven-repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0
> .b2.jar
> urls[6] =
>
file:/D:/projekte/maven-repository/org/apache/maven/maven-error-diagnost
> ics/2.0.6/maven-error-diagnostics-2.0.6.jar
> urls[7] =
>
file:/D:/projekte/maven-repository/org/apache/maven/maven-plugin-registr
> y/2.0.6/maven-plugin-registry-2.0.6.jar
> urls[8] =
>
file:/D:/projekte/maven-repository/org/apache/maven/wagon/wagon-ssh-comm
> on/1.0-beta-2/wagon-ssh-common-1.0-beta-2.jar
> urls[9] =
>
file:/D:/projekte/maven-repository/org/apache/maven/plugin-tools/maven-p
> lugin-tools-api/2.4.3/maven-plugin-tools-api-2.4.3.jar
> urls[10] =
file:/D:/projekte/maven-repository/jdom/jdom/1.0/jdom-1.0.jar
> urls[11] =
>
file:/D:/projekte/maven-repository/com/thoughtworks/xstream/xstream/1.3/
> xstream-1.3.jar
> urls[12] =
>
file:/D:/projekte/maven-repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.
> jar
> urls[13] =
>
file:/D:/projekte/maven-repository/commons-lang/commons-lang/2.4/commons
> -lang-2.4.jar
>
> Realm ID: plexus.core
>
>
>
> java.lang.NoSuchMethodError:
>
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/set
> tings/RuntimeInfo;
>at
>
org.apache.maven.plugins.help.EffectiveSettingsMojo.copySettings(Effecti
> veSettingsMojo.java:189)
>at
>
org.apache.maven.plugins.help.EffectiveSettingsMojo.execute(EffectiveSet
> tingsMojo.java:89)
>at
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
> nager.java:579)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> Failures(DefaultLifecycleExecutor.java:498)
>at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentFo
> rProject(DefaultLifecycleExecutor.java:265)
> ...
>
> By the way, the settings.xml contains this:
>   
> jboss
> 
>


You need to change this to

  true

as

assert "true".equalsIgnoreCase("") == false;


> 
> 
>oracle.jdbc.driver.OracleDriver
>ing_epa
>ing_epa
>jdbc:oracle:thin:@deneb:1521:WLP
>...
> 
>   
>  
>
>  
>jboss
>  
>

[Winter, Wolfgang] okay, maybe. But I activated the profile explicitly
in the last line! Please excuse me when I criticize, but for me this is
bad design. This is not what a dumb user like me expects, regardless of
the setting of 

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

Re: from workaround to workaround 1

2008-09-05 Thread Rainer Pruy

After all,
I consider this classical paradigm of "all you need is there, just obstructed 
by details all over".

"Filtering did not work" because  does filtering for mainstream, but 
Wolfgang needed filtering for "test".
If you know what to look for, this distinction is quite obvious from the docs.
But for the hurrying user trying to overcome an immediate problem, this is 
easily to be overlooked.

This is (implicit) reason to a number of complaints in maven related lists.
Due to the distributed and fine-grain nature of maven and it's plugins.
Information is spread across numerous locations without much "interconnection" 
of semantics.
For "using" a plugin, it is always implied the (potential) user is absolutely 
aware of any implications of the interaction of that
plugin with the rest of the maven "runtime".

Probably we can keep that in mind when working on documentation:

- explicitly state the environment and effects of a plugin
- always encourage users/readers to "get the overall picture" first (or restate 
the essentials?)

May be that will improve "user experience" in the long.

As in most cases the problem is not some feature not being "available",
but some wanted feature not being discoverable easily (esp. if it has to be 
constructed using several existing components).
And maven has a lot of bricks to build from. but also a lot of points to get 
something plugged to.
And is not (always) quite obvious to the ordinary "user" what effects are 
possible and what needs something new.

Regards
Rainer

Asgeir S. Nilsen schrieb:
> Wolfgang,
> For test resources you should use the  element, not the
>  element.  The documentation is a bit shallow on this matter.
> 
> Asgeir
> 
> On Fri, Sep 5, 2008 at 08:46, <[EMAIL PROTECTED]> wrote:
> 
>> Hi,
>>
>>
>>
>> here is a small story about working with Maven. In my experience of 6
>> months now this happened very often like this. Maven is very hard to manage,
>> not intuitive and error messages are incomprehensible or misleading.
>>
>>
>>
>> The problem: We have 5 Maven projects with sub projects. For test classes,
>> the database connection should be defined only once, we put it into the
>> user's settings.xml. Now, how accessing the db-properties in test classes?
>>
>> First idea: Filtering! I created properties file in the test/resources
>> directories and tried to filter db properties from the settings properties
>> with
>>
>>
>>
>> 
>>
>>  
>>
>>src/test/resources
>>
>>true
>>
>>  
>>
>> 
>>
>>
>>
>> Nothing happens. Filtering seems to be possible only in main/resources.
>> Then I ask myself why have I to define a  when only one value is
>> working? You could hard-code it. This is not intuitive!
>>
>>
>>
>>
>>
>> Freundliche Grüße / Kind regards
>>
>>
>>
>> Wolfgang Winter
>>
>> System Analyst
>>
>>

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

Dependency problem for org.eclipse.core:runtime:3.3.100-v20070530

2008-09-05 Thread Caraivan Constantin

Hello,

I'm new to this list, so here it goes :)

I'm using repo1.maven.org and I need org.eclipse.core:runtime, version
3.3.100-v20070530 for a build. Unfortunately there are some dependency
problems, and the build fails. I'll explain the problems:

I have this in the org.eclipse.core:runtime pom.xml:


org.eclipse.equinox
app
[1.0.0,2.0.0)


The version of this dependency that is in repo1 is 1.0.0-v20070606:

org.eclipse.equinox
app
1.0.0-v20070606

This causes the version check to fail and the build fails too.

Do you have any ideas about how I can solve this, or who I need to
contact to solve the problem?

Thank you,
___
Costin Caraivan

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

Re: from workaround to workaround 3

On Friday 05 September 2008 [EMAIL PROTECTED] wrote:
> Profiles are configured in the users/settings.xml so help:effective-pom
> gives no information about profiles

It does, your profiles are just not activated! See Stephen's mail why they 
are not activated.

hth,
- martin

signature.asc
Description: This is a digitally signed message part.

Re: from workaround to workaround 3

On Fri, Sep 5, 2008 at 9:23 AM, <[EMAIL PROTECTED]> wrote:

>
> On Friday 05 September 2008 [EMAIL PROTECTED] wrote:
>
> > I looked into the source code of the plugin. It uses
> > project.getActiveProfiles() and this method returns an empty list. But
> I
> > have a profile defined in settings which is set active with
> > . Why does the getActiveProfiles() method returns zero?
>
> Try using the maven-help-plugin to find out some details. The goal
> help:active-profiles shows you which profiles are active.
>
> help:effective-pom and help:effective-settings show you the effective
> pom.xml resp. settings.xml file. Are your profiles defined there?
>
> You really don't need to write your own plugin just for filtering some
> resource-files.
>
> hth,
> - martin
>
> [Winter, Wolfgang] help:active-profiles executed on the parent pom:
> Active Profiles for Project 'net.atos.wlp:core:pom:0.0.1-SNAPSHOT':
> There are no active profiles.
> Active Profiles for Project
> 'net.atos.wlp:plugin-setproperties:maven-plugin:0.0.1-SNAPSHOT':
> There are no active profiles.
> Active Profiles for Project
> 'net.atos.wlp:core-database:jar:0.0.1-SNAPSHOT':
> There are no active profiles.
> ...
>
> Profiles are configured in the users/settings.xml so help:effective-pom
> gives no information about profiles
>
> Execution of help:effective-settings: The workaround story continues:
> [ERROR] org.apache.maven.plugins.help.EffectiveSettingsMojo#execute()
> caused a linkage error (java.lang.NoSuchMethodError). Check the realms:
>
> NOTE:
> Plugin realm is:
> /plugins/org.apache.maven.plugins:maven-help-plugin:[EMAIL 
> PROTECTED]/thread:main
> Container realm is: plexus.core
>
> Realm ID:
> /plugins/org.apache.maven.plugins:maven-help-plugin:[EMAIL 
> PROTECTED]/thread:main
> urls[0] =
> file:/D:/projekte/maven-repository/org/apache/maven/plugins/maven-help-p
> lugin/2.1/maven-help-plugin-2.1.jar
> urls[1] =
> file:/D:/projekte/maven-repository/org/codehaus/plexus/plexus-utils/1.5.
> 6/plexus-utils-1.5.6.jar
> urls[2] =
> file:/D:/projekte/maven-repository/junit/junit/3.8.1/junit-3.8.1.jar
> urls[3] =
> file:/D:/projekte/maven-repository/org/apache/maven/wagon/wagon-http-sha
> red/1.0-beta-2/wagon-http-shared-1.0-beta-2.jar
> urls[4] =
> file:/D:/projekte/maven-repository/jtidy/jtidy/4aug2000r7-dev/jtidy-4aug
> 2000r7-dev.jar
> urls[5] =
> file:/D:/projekte/maven-repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0
> .b2.jar
> urls[6] =
> file:/D:/projekte/maven-repository/org/apache/maven/maven-error-diagnost
> ics/2.0.6/maven-error-diagnostics-2.0.6.jar
> urls[7] =
> file:/D:/projekte/maven-repository/org/apache/maven/maven-plugin-registr
> y/2.0.6/maven-plugin-registry-2.0.6.jar
> urls[8] =
> file:/D:/projekte/maven-repository/org/apache/maven/wagon/wagon-ssh-comm
> on/1.0-beta-2/wagon-ssh-common-1.0-beta-2.jar
> urls[9] =
> file:/D:/projekte/maven-repository/org/apache/maven/plugin-tools/maven-p
> lugin-tools-api/2.4.3/maven-plugin-tools-api-2.4.3.jar
> urls[10] = file:/D:/projekte/maven-repository/jdom/jdom/1.0/jdom-1.0.jar
> urls[11] =
> file:/D:/projekte/maven-repository/com/thoughtworks/xstream/xstream/1.3/
> xstream-1.3.jar
> urls[12] =
> file:/D:/projekte/maven-repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.
> jar
> urls[13] =
> file:/D:/projekte/maven-repository/commons-lang/commons-lang/2.4/commons
> -lang-2.4.jar
>
> Realm ID: plexus.core
>
>
>
> java.lang.NoSuchMethodError:
> org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/set
> tings/RuntimeInfo;
>at
> org.apache.maven.plugins.help.EffectiveSettingsMojo.copySettings(Effecti
> veSettingsMojo.java:189)
>at
> org.apache.maven.plugins.help.EffectiveSettingsMojo.execute(EffectiveSet
> tingsMojo.java:89)
>at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
> nager.java:579)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> Failures(DefaultLifecycleExecutor.java:498)
>at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentFo
> rProject(DefaultLifecycleExecutor.java:265)
> ...
>
> By the way, the settings.xml contains this:
>   
> jboss
> 
>


You need to change this to

  true

as

assert "true".equalsIgnoreCase("") == false;


> 
> 
>oracle.jdbc.driver.OracleDriver
>ing_epa
>ing_epa
>jdbc:oracle:thin:@deneb:1521:WLP
>...
> 
>   
>  
>
>  
>jboss
>  
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

AW: from workaround to workaround 3

On Friday 05 September 2008 [EMAIL PROTECTED] wrote:

> I looked into the source code of the plugin. It uses
> project.getActiveProfiles() and this method returns an empty list. But
I
> have a profile defined in settings which is set active with
> . Why does the getActiveProfiles() method returns zero?

Try using the maven-help-plugin to find out some details. The goal 
help:active-profiles shows you which profiles are active. 

help:effective-pom and help:effective-settings show you the effective 
pom.xml resp. settings.xml file. Are your profiles defined there?

You really don't need to write your own plugin just for filtering some 
resource-files.

hth,
- martin

[Winter, Wolfgang] help:active-profiles executed on the parent pom: 
Active Profiles for Project 'net.atos.wlp:core:pom:0.0.1-SNAPSHOT': 
There are no active profiles.
Active Profiles for Project
'net.atos.wlp:plugin-setproperties:maven-plugin:0.0.1-SNAPSHOT': 
There are no active profiles.
Active Profiles for Project
'net.atos.wlp:core-database:jar:0.0.1-SNAPSHOT': 
There are no active profiles.
...

Profiles are configured in the users/settings.xml so help:effective-pom
gives no information about profiles

Execution of help:effective-settings: The workaround story continues:
[ERROR] org.apache.maven.plugins.help.EffectiveSettingsMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError). Check the realms:

NOTE:
Plugin realm is:
/plugins/org.apache.maven.plugins:maven-help-plugin:[EMAIL 
PROTECTED]/thread:main
Container realm is: plexus.core

Realm ID:
/plugins/org.apache.maven.plugins:maven-help-plugin:[EMAIL 
PROTECTED]/thread:main
urls[0] =
file:/D:/projekte/maven-repository/org/apache/maven/plugins/maven-help-p
lugin/2.1/maven-help-plugin-2.1.jar
urls[1] =
file:/D:/projekte/maven-repository/org/codehaus/plexus/plexus-utils/1.5.
6/plexus-utils-1.5.6.jar
urls[2] =
file:/D:/projekte/maven-repository/junit/junit/3.8.1/junit-3.8.1.jar
urls[3] =
file:/D:/projekte/maven-repository/org/apache/maven/wagon/wagon-http-sha
red/1.0-beta-2/wagon-http-shared-1.0-beta-2.jar
urls[4] =
file:/D:/projekte/maven-repository/jtidy/jtidy/4aug2000r7-dev/jtidy-4aug
2000r7-dev.jar
urls[5] =
file:/D:/projekte/maven-repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0
.b2.jar
urls[6] =
file:/D:/projekte/maven-repository/org/apache/maven/maven-error-diagnost
ics/2.0.6/maven-error-diagnostics-2.0.6.jar
urls[7] =
file:/D:/projekte/maven-repository/org/apache/maven/maven-plugin-registr
y/2.0.6/maven-plugin-registry-2.0.6.jar
urls[8] =
file:/D:/projekte/maven-repository/org/apache/maven/wagon/wagon-ssh-comm
on/1.0-beta-2/wagon-ssh-common-1.0-beta-2.jar
urls[9] =
file:/D:/projekte/maven-repository/org/apache/maven/plugin-tools/maven-p
lugin-tools-api/2.4.3/maven-plugin-tools-api-2.4.3.jar
urls[10] = file:/D:/projekte/maven-repository/jdom/jdom/1.0/jdom-1.0.jar
urls[11] =
file:/D:/projekte/maven-repository/com/thoughtworks/xstream/xstream/1.3/
xstream-1.3.jar
urls[12] =
file:/D:/projekte/maven-repository/xpp3/xpp3_min/1.1.4c/xpp3_min-1.1.4c.
jar
urls[13] =
file:/D:/projekte/maven-repository/commons-lang/commons-lang/2.4/commons
-lang-2.4.jar

Realm ID: plexus.core

java.lang.NoSuchMethodError:
org.apache.maven.settings.Settings.getRuntimeInfo()Lorg/apache/maven/set
tings/RuntimeInfo;
at
org.apache.maven.plugins.help.EffectiveSettingsMojo.copySettings(Effecti
veSettingsMojo.java:189)
at
org.apache.maven.plugins.help.EffectiveSettingsMojo.execute(EffectiveSet
tingsMojo.java:89)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa
nager.java:579)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:498)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentFo
rProject(DefaultLifecycleExecutor.java:265)
...

By the way, the settings.xml contains this:

 jboss

oracle.jdbc.driver.OracleDriver
ing_epa
ing_epa
jdbc:oracle:thin:@deneb:1521:WLP
...

jboss

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

Re: How to disable a plugin?

2008-09-05 Thread youhaodeyi


This configure works.
thanks

Asgeir S. Nilsen-2 wrote:
> 
> In the submodule where you don't want the plugin to run, add a 
> element with the following elements within:
> 
>   
> some-id
> none
>   
> 
> 
> On Fri, Sep 5, 2008 at 08:40, youhaodeyi <[EMAIL PROTECTED]> wrote:
> 
>>
>> In the parent pom, it includes copy-dependency plugin which I want to
>> disable
>> in the child pom. I use this configuration:
>>
>> 
>>   
>> org.apache.maven.plugins
>>
>>  maven-dependency-plugin
>>false
>> 
>>
>> But every time running 'mvn package', it will copy all the dependencies
>> to
>> the child module. How can I disable this?
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-disable-a-plugin--tp19325716p19325716.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/How-to-disable-a-plugin--tp19325716p19326911.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released

That is a good question...

I would think that when you ask for the latest maven-metatdata.xml archivia
will check if it's cache is out of date and then query central...

if you do mvn -U do you get the latest version of a plugin automatically (if
yes, then the answer is yes, if no then the answer is no)

FYI, we're using nexus and have no issues in this regard

-Stephen

On Fri, Sep 5, 2008 at 7:46 AM, Wim Deblauwe <[EMAIL PROTECTED]> wrote:

> Does it work if you are not using the central repo directly but a
> repository
> manager (archiva in my case) in between. Will this plugin "see" the newer
> versions, even if they are not in archiva yet?
>
> regards,
>
> Wim
>
> 2008/9/5 Stephen Connolly <[EMAIL PROTECTED]>
>
> > The Mojo team is pleased to announce the release of the Versions Maven
> > Plugin, version 1.0-alpha-1.
> >
> > This plugin allows:
> > * the querying for newer versions of plugins used in a project.
> > * the querying for newer versions of dependencies used in a project.
> > * updating a project's parent to the latest available version
> >  (e.g. useful for syncing with corporate poms to ensure the latest is
> >  used prior to rolling a release)
> > * updating properties defined in a project to the latest version of a
> > specific
> >  artifact (e.g. for ensuring that a suite of dependencies are all the
> same
> > version)
> >
> > http://mojo.codehaus.org/versions-maven-plugin/
> >
> > You can run mvn -up to get the latest version of the plugin, or specify
> > the version in your project's plugin configuration:
> >
> > 
> >  org.codehaus.mojo
> >  versions-maven-plugin
> >  1.0-alpha-1
> > 
> >
> > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> >
> > ** Bug
> >* [MVERSIONS-1] - javadoc plugin doesn't have its version specified
> but
> > it has
> >* [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> > plugins that are not defined in the pom.
> >
> > ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> >* [MVERSIONS-3] - display-plugin-updates does not identify the plugin
> > version as not being provided when derived from the super-pom
> >
> > Enjoy,
> >
> > -The Mojo team
> >
>

Re: from workaround to workaround 1

2008-09-05 Thread Asgeir S. Nilsen

Wolfgang,
For test resources you should use the  element, not the
 element.  The documentation is a bit shallow on this matter.

Asgeir

On Fri, Sep 5, 2008 at 08:46, <[EMAIL PROTECTED]> wrote:

> Hi,
>
>
>
> here is a small story about working with Maven. In my experience of 6
> months now this happened very often like this. Maven is very hard to manage,
> not intuitive and error messages are incomprehensible or misleading.
>
>
>
> The problem: We have 5 Maven projects with sub projects. For test classes,
> the database connection should be defined only once, we put it into the
> user's settings.xml. Now, how accessing the db-properties in test classes?
>
> First idea: Filtering! I created properties file in the test/resources
> directories and tried to filter db properties from the settings properties
> with
>
>
>
> 
>
>  
>
>src/test/resources
>
>true
>
>  
>
> 
>
>
>
> Nothing happens. Filtering seems to be possible only in main/resources.
> Then I ask myself why have I to define a  when only one value is
> working? You could hard-code it. This is not intuitive!
>
>
>
>
>
> Freundliche Grüße / Kind regards
>
>
>
> Wolfgang Winter
>
> System Analyst
>
>

Re: How to disable a plugin?

2008-09-05 Thread Asgeir S. Nilsen

In the submodule where you don't want the plugin to run, add a 
element with the following elements within:

  
some-id
none
  


On Fri, Sep 5, 2008 at 08:40, youhaodeyi <[EMAIL PROTECTED]> wrote:

>
> In the parent pom, it includes copy-dependency plugin which I want to
> disable
> in the child pom. I use this configuration:
>
> 
>org.apache.maven.plugins
>
>  maven-dependency-plugin
>false
> 
>
> But every time running 'mvn package', it will copy all the dependencies to
> the child module. How can I disable this?
> --
> View this message in context:
> http://www.nabble.com/How-to-disable-a-plugin--tp19325716p19325716.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

AW: from workaround to workaround 2


> Second idea: I found the properties-maven-plugin which has a goal that
writes all settings properties into a file. Fine, that's what I need.
However, this plugin is not on the rep01.maven server but only on a
codehaus server. So I defined an additional repository:

No need to use that plugin. You can use the maven-resources-plugin for
the same. See

 
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.h
tml

[Winter, Wolfgang] Hi Jochen, please see my mail from workaround to
workaround 1: I did not succeed in filtering TEST/resources

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

Re: how, exactly, does maven compare versions

2008-09-05 Thread Benjamin Smith-Mannschott

On Sep 4, 2008, at 22:09, Stephen Connolly wrote:

On Thu, Sep 4, 2008 at 8:52 PM, Benjamin Smith-Mannschott:

Yes. That helped, as did
http://docs.codehaus.org/display/MAVEN/Extending+Maven+2.0+Dependencies

Which actually comes out and says that qualifier and build nr are
mutually
exclusive. The syntax given says this too, but I wasn't seeing it.
Another
way of looking at it, I suppose, is that everything following
"1.2.3-" is
taken as single qualifier, which is compared numerically if it
happens to be

composed only of digits and otherwise compared as a string.

Yep:

http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#155

Aha! thanks! I was grubbing around in the source of the 2.0.x branch
yesterday after I wrote my message looking for exactly this class,
only I didn't find it. ;-)

It seems that '.2.3', in the example above is optional, those parts
taken
to be zero if missing. If any alphanumerics get mixed up in there
or about

without a separating hyphen the whole thing goes textual and is just
compared as a single string. At least that's what I understood. So
presumably, if we're comparing two version strings with eachother
and one is
"well formed" and the other is not, they just get compared as if
they were

both not well formed.

Nope:

http://maven.apache.org/ref/current/maven-artifact/xref/org/apache/maven/artifact/versioning/DefaultArtifactVersion.html#54

If one is treated as a string (because it's malformed) the other
will always

be newer (because it has a build number)

Actually, it looks like the build number only enters into it when both
have a build number, but build number and qualifier are mutually
exclusive, so the logic exits early if one has a qualifier and the
other doesn't.

Somehow that logic makes me a little queezy, but at least it does
appear to sort consistently.

// Ben

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

AW: from workaround to workaround 2

On Friday 05 September 2008 [EMAIL PROTECTED] wrote:
>
>
>   
>
>  codehaus
>
>  codehaus Repository for plugins
>
>  http://snapshots.repository.codehaus.org
>
>  default
>
>   
>
>
>
>
>
> However, Maven was not able to download the plugin. It ignores the
> pluginRepository and searches only on central. Why defining a
> pluginRepository when it is not used by Maven?

What version of the plugin are you using? If it's a SNAPSHOT, you have
to 
enabled snapshots in your repository configuration by adding

true

If it's not a SNAPSHOT, you are using the wrong repository.

hth,
- martin

[Winter, Wolfgang] yes, Martin, it is a snapshot, so maybe that's the
reason. However, for my taste there is too much special knowledge
necessary for a simple task which could be more intuitive. But I do not
change now anything. You know: never change a running system :-)

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

Re: from workaround to workaround 3

On Friday 05 September 2008 [EMAIL PROTECTED] wrote:

> I looked into the source code of the plugin. It uses
> project.getActiveProfiles() and this method returns an empty list. But I
> have a profile defined in settings which is set active with
> . Why does the getActiveProfiles() method returns zero?

Try using the maven-help-plugin to find out some details. The goal 
help:active-profiles shows you which profiles are active. 

help:effective-pom and help:effective-settings show you the effective 
pom.xml resp. settings.xml file. Are your profiles defined there?

You really don't need to write your own plugin just for filtering some 
resource-files.

hth,
- martin

signature.asc
Description: This is a digitally signed message part.

Re: from workaround to workaround 2