Re: how is hudson's "maven generated site" link intended to work for multi-module maven builds?

[Andrew Hughes]

Hi Ben,

I've got the same problem.

As you've noted the Hudson "Maven-generated site" appears to be the last
pom/module built and not the highest parent. Also, the use of a url based on
${project.groupId} and ${project.artifactId} is ugly very ugly.
Especially when you get two level's deep on parents (super ugly, broken
references and unworkable).

My proposed solution would be to derive your site distro url's from a
profile property. You could put this in the hudson user's setting.xml or in
the pom.xml itself (which one is circumstantial). The profile can be
activated from the hudson job.

I would expect the distro url to  be a link to the filesystem that is
acutally where the "Maven-generated site" actually resolves too.

Perhaps this would work... I doubt we are the first to encounter this.
Help/Advice would be GREAT :)



On Wed, May 27, 2009 at 6:40 AM, B Smith-Mannschott
wrote:

> I'm sending this missive to user's lists of both hudson and maven
> because it concerns using these two tools together, and I'll need help
> from both parties to make this work.
>
> Rather than separately site-deploying the sites of the 30 or so maven
> projects hudson is building for me at work, I've decided to take
> advantage of hudson's handy "maven generated site" link. (Now that it
> works again!)
>
> This works quite well for single-module maven builds.
>
> Multi-module builds, not so much.
>
> I have a few multi-module maven projects at work, and here are the
> problems:
>
> (1) Hudson's "maven generated site" link links to one of the
> sub-modules instead of linking to the site of the multi-module pom
> project at the root of the defined working copy.
>
> (2) Even if it *did* link to the correct project, instead of some
> random sub-project, it wouldn't work since links to sub-modules are
> broken.
>
> (3) Links to sub-modules are broken. They expect to find in
> target/site/submodule, what is in fact in submodule/target/site.
>
> (4) Links to sub-modules are not even generated unless it happens that
> the multi-module pom project is also the  of each of the
> submodules. Why this is, is anyone's guess.
>
> (5) They will work, if the site is deployed, but then  must be
> defined correctly.
>
> (6) One thing that works, but is ugly is:
> http://example.com/${groupId}/${artifactId} in the
> parent/multi-module pom. The children end up all installing to
> http://example.com/${groupId}/${project.artifactId}/${project.artifactId},
> which is just kind of gross, instead of
> ttp://example.com/${groupId}/${parent.artifactId}/${project.artifactId},
> but I guess that's an effect of the ${} expansion being after, not
> before inheritance is performed.
>
> But, if I deploy the site, I need to separately maintain a page of
> links to those sites, since Hudson's "maven generated site" link does
> not go there, it goes to target/site. I also have a whole separate set
> of URLs to manage, to advertise to my users and to clean up when I
> remove corresponding build jobs. Messy.
>
> I'm trying to simplify my life, not complicated it.
>
>
> Is there some way I can get my multi-module projects to produce a site
> which is accessible through hudson and which makes submodules
> available? Alternately, perhaps it would be possible to somehow
> intelligently combine the project reports from the various submodules
> and merge them all into the site of the multi-module build.
>
>
> I've reached the point now where I'm tempted to just break out beat
> the problem into submission with a generous helping of shell
> scripting, but that doesn't seem very 'mavenesque'.
>
> Has anyone out there already solved this, or a similar problem?
>
> // Ben
>
> -
> To unsubscribe, e-mail: users-unsubscr...@hudson.dev.java.net
> For additional commands, e-mail: users-h...@hudson.dev.java.net
>
>

Re: Getting error "The defined artifact is not an archetype" with AppFuse archetypes

[Ellecer Valencia]

Matt has emailed back about this. Would be best to do it from
command-line, using the page he mentions to create the entire command.

-- Forwarded message --
From: Matt Raible
Date: Thu, Nov 19, 2009 at 2:44 PM
Subject: Re: CP: Problem with Appfuse Maven Archetypes


In 2.1.0-M1, we've changed the name of the archetypes. If you append
"-archetype" onto the name, it should work.

The following page might make it easier (this is also shown in the
QuickStart Guide).

http://static.appfuse.org/archetypes.html

FWIW, I just released 2.1.0-M1 today and plan on writing up a blog
post, release notes, etc. tomorrow.

Matt


On Thu, Nov 19, 2009 at 2:02 PM, Wayne Fay  wrote:
>> Is anyone else getting these errors? I've tested it with archetypes
>> 1-9 (all the AppFuse ones) and they're returning the same error
>
> You should probably ask Matt Raible what's going on with these archetypes...
>
>> I'm using maven 2.0.10 - have these archetypes changed to now require
>> higher versions, or does anyone else know what's happening with them?
>
> Did you try with Maven 2.2.1?
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Creating a war from antrun

[Dan Tran]

configure your pom to use packaging=pom,

get antrun to build your war,

Then use build-helper-maven-plugin to attach your war file to Maven so
that it can be installed/deployed

http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html

-D

On Wed, Nov 18, 2009 at 7:21 PM, Sony Antony  wrote:
> We have to use one of the weblogic provided ant task in order to create a
> war file.
>
> How will I do this with maven.
> I mean should I give the packaging as pom and then produce teh warfile using
> antrun ? ( But then how will the produced war file be installed to teh local
> repository )
>
> Or should I run antrun first and then, unjar and then let the war plugin war
> it up again ?
>
> Any pointer will be appreciated
> --sony
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

How to use was6-maven-plugin from the build servers without local WAS installation

[Rakesh Arora]

was6-maven-plugin requires an installation of WAS on the build machine:
http://mojo.codehaus.org/was6-maven-plugin/usage.html

We want to use this plugin to automate the verification testing by deploying
the ear (on a remote host) as part of the build and run some testcases. It
is not practical to install the WAS on all the build servers.

Any idea?

Thanks,
-Rakesh 
-- 
View this message in context: 
http://old.nabble.com/How-to-use-was6-maven-plugin-from-the-build-servers-without-local-WAS-installation-tp26420087p26420087.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Creating a war from antrun

[Sony Antony]

We have to use one of the weblogic provided ant task in order to create a
war file.

How will I do this with maven.
I mean should I give the packaging as pom and then produce teh warfile using
antrun ? ( But then how will the produced war file be installed to teh local
repository )

Or should I run antrun first and then, unjar and then let the war plugin war
it up again ?

Any pointer will be appreciated
--sony

Re: Getting error "The defined artifact is not an archetype" with AppFuse archetypes

[Wayne Fay]

> Is anyone else getting these errors? I've tested it with archetypes
> 1-9 (all the AppFuse ones) and they're returning the same error

You should probably ask Matt Raible what's going on with these archetypes...

> I'm using maven 2.0.10 - have these archetypes changed to now require
> higher versions, or does anyone else know what's happening with them?

Did you try with Maven 2.2.1?

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Build multiples war with multiples contexts.

[Wayne Fay]

> I have a webapp and two servers and a localhost with diferents databases
> configs and I'm trying to do this:

In general, you should use profiles for this kind of thing:
http://maven.apache.org/guides/mini/guide-building-for-different-environments.html

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Getting error "The defined artifact is not an archetype" with AppFuse archetypes

[Ellecer Valencia]

Hi,

I'm trying to use mvn archetype:generate to create some projects and
noticed that the AppFuse archetypes are generating errors like:

Downloading: 
http://repo1.maven.org/maven2/org/appfuse/archetypes/appfuse-core/2.1.0-M1/appfuse-core-2.1.0-M1.jar
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] The defined artifact is not an archetype
[INFO] 

Is anyone else getting these errors? I've tested it with archetypes
1-9 (all the AppFuse ones) and they're returning the same error

I'm using maven 2.0.10 - have these archetypes changed to now require
higher versions, or does anyone else know what's happening with them?


thanks,

Ellecer

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Build multiples war with multiples contexts.

[Wagner Santos]

Hello,
I have a webapp and two servers and a localhost with diferents databases
configs and I'm trying to do this:
Build war to serverA use contextA
Build war to serverB use contextB
Build war to localhost use contextDefault.

Is it possible? How can I do this?

Thanks!


--
Wagner Santos
MSN/Gtalk: wagner.gsan...@gmail.com
Site: http://www.geracaoelias.blog.br
meadiciona:http://meadiciona.com/wagnergsantos/
Sent from Brasilia, DF, Brazil

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Brian Fox]

This is not related. The dependency plugin has some issues resolving
things from the reactor and ranges in the following goals only:
copy
unpack
go-offline
resolve-plugins


All the other goals set @requiresDependencyResolution test which will
cause Maven to resolve all dependencies prior to the plugin running.
So if you're seeing some error, it's happening in the core. Provide a
sample project and/or some debug output and we might be able to tell
what the problem is.


On Wed, Nov 18, 2009 at 12:59 PM, Stevo Slavić  wrote:
> Likely because dependency plugin has bugs, and I'm suspecting that your
> issue is similar/related to this
> one already reported.
>
> But it's odd that it doesn't fail for you at module mod_c, as build reactor
> should have ordered mod_c to be built/processed before mod_d. Just guessing,
> maybe this mojo doesn't use maven reactor at all, and probably mod_c is
> ordered in list of modules in your parent module after mod_d.
>
> Regards,
> Stevo.
>
> On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold  wrote:
>
>> Hi --
>>
>> I'm trying to track down some other depdendency issues in my project using
>> dependencies:tree, but am getting errors that a module isn't found.
>>
>> I have my project set up with a parent pom and a list of modules, each
>> referencing the parent, etc. Essentially, I have this:
>>
>>    pom.xml # parent, references mods a, b, c, d in 
>>    mod_a/pom.xml # module, no module dependencies
>>    mod_b/pom.xml # module, no module dependencies
>>    mod_c/pom.xml # module, declared dependency on mod_b
>>    mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c
>>
>> From the root workspace directory, I can run things like 'compile' or
>> 'jar:jar'
>> just fine, but for some reason 'dependencies:tree' is failing when it gets
>> to
>> mod_d, complaining that it can't find mod_c.
>>
>> Any ideas what I'm doing wrong?
>>
>> jon
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-changes-plugin: automatic update for release?

[David C. Hicks]

Thanks.  I'll give it a whirl.  We're using Hudson, presently.  It's not
the pulling JIRA information that I think is going to give me issues,
though.  It's that the changes.xml will have version "1.0.0" but the
current version from the CI point of view is "1.0.0-SNAPSHOT".  Unless
the changes plugin is capable of handling that difference.

Thanks again,
Dave

Kalle Korhonen wrote:
> On Wed, Nov 18, 2009 at 1:46 PM, David C. Hicks  wrote:
>   
>> Of course...the build will break after a release because the new
>> changes.xml won't have a section for the new release version.
>> Come to think of it, will that even work?  Since the CI sees a SNAPSHOT
>> version, and the changes.xml doesn't include SNAPSHOT.
>> 
>
> Depending on which integration you use. Will work at least for jira,
> read the docs at
> http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html
>
> Kalle
>
> PS. Off-topic but make dependencies report go faster:
>   
>   
> maven-project-info-reports-plugin
>   2.1
>   
>   
> false
>   
>   
>
> Maybe even dependencyDetailsEnabled to false if you so wish.
>
>   
>> David C. Hicks wrote:
>> 
>>> Good suggestion.  I hadn't really thought of using CI to test the
>>> changes.xml.  That's primarily because I also have the dependencies
>>> report generated as part of the Site generation.  Under normal
>>> circumstances, it takes forever and a day to generate the dependencies
>>> report, since it appears to hit the Internet to find all the
>>> dependencies, instead of using the local repository.
>>>
>>> I suppose I can restructure my CI build to exclude the dependencies
>>> report and get some useful information about the changes report.
>>>
>>> Thanks!
>>>
>>> Kalle Korhonen wrote:
>>>
>>>   
 Changes plugin offers Jira and Trac integration. You can filter your
 changes.xml if you cannot use current version only. Use ci system to
 run the site and changes report so you know if it'll work or not
 before the release.

 Kalle

 On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks  
 wrote:


 
> Hi folks,
>
> I'm using the Changes plugin to both produce a report for my Site and to
> distribute email announcements of changes.  The problem is that if we're
> not careful to remember to update the changes.xml file itself, then our
> release build fails because it doesn't find a change set with the right
> version.  I'd really like to find some way to automatically update the
> changes.xml file during the release build process.  Can anyone recommend
> a plugin that might let me make modifications to this xml file at build
> time?  Or, any other suggestions?
>
> Thanks,
> Dave
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>
>   
 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>   

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-changes-plugin: automatic update for release?

[Kalle Korhonen]

On Wed, Nov 18, 2009 at 1:46 PM, David C. Hicks  wrote:
> Of course...the build will break after a release because the new
> changes.xml won't have a section for the new release version.
> Come to think of it, will that even work?  Since the CI sees a SNAPSHOT
> version, and the changes.xml doesn't include SNAPSHOT.

Depending on which integration you use. Will work at least for jira,
read the docs at
http://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html

Kalle

PS. Off-topic but make dependencies report go faster:


maven-project-info-reports-plugin
2.1


false



Maybe even dependencyDetailsEnabled to false if you so wish.

>
> David C. Hicks wrote:
>> Good suggestion.  I hadn't really thought of using CI to test the
>> changes.xml.  That's primarily because I also have the dependencies
>> report generated as part of the Site generation.  Under normal
>> circumstances, it takes forever and a day to generate the dependencies
>> report, since it appears to hit the Internet to find all the
>> dependencies, instead of using the local repository.
>>
>> I suppose I can restructure my CI build to exclude the dependencies
>> report and get some useful information about the changes report.
>>
>> Thanks!
>>
>> Kalle Korhonen wrote:
>>
>>> Changes plugin offers Jira and Trac integration. You can filter your
>>> changes.xml if you cannot use current version only. Use ci system to
>>> run the site and changes report so you know if it'll work or not
>>> before the release.
>>>
>>> Kalle
>>>
>>> On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks  wrote:
>>>
>>>
 Hi folks,

 I'm using the Changes plugin to both produce a report for my Site and to
 distribute email announcements of changes.  The problem is that if we're
 not careful to remember to update the changes.xml file itself, then our
 release build fails because it doesn't find a change set with the right
 version.  I'd really like to find some way to automatically update the
 changes.xml file during the release build process.  Can anyone recommend
 a plugin that might let me make modifications to this xml file at build
 time?  Or, any other suggestions?

 Thanks,
 Dave


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

A use case that might be of interest for m3

[Benson Margulies]

Here's something that happens to me.

I start working on a medium-sized change. It's not worth a branch. However,
I do want to run the old and new versions in parallel.

Now, I have two annoying choices. (a) I can temporarily edit the versions of
all of my modules to stop collisions. (b) I can make a separate local
repository, and get an entire additional copy of all the maven plugins just
so that I can keep two sets of my artifacts separate.

Oh how I wish that the plugin local repository could be separated from the
dependencies, or, better yet, three buckets: plugins, dependencies, and
things I'm actually building right now.

Re: maven-changes-plugin: automatic update for release?

[David C. Hicks]

Of course...the build will break after a release because the new
changes.xml won't have a section for the new release version.
Come to think of it, will that even work?  Since the CI sees a SNAPSHOT
version, and the changes.xml doesn't include SNAPSHOT. 

David C. Hicks wrote:
> Good suggestion.  I hadn't really thought of using CI to test the
> changes.xml.  That's primarily because I also have the dependencies
> report generated as part of the Site generation.  Under normal
> circumstances, it takes forever and a day to generate the dependencies
> report, since it appears to hit the Internet to find all the
> dependencies, instead of using the local repository.
>
> I suppose I can restructure my CI build to exclude the dependencies
> report and get some useful information about the changes report.
>
> Thanks!
>
> Kalle Korhonen wrote:
>   
>> Changes plugin offers Jira and Trac integration. You can filter your
>> changes.xml if you cannot use current version only. Use ci system to
>> run the site and changes report so you know if it'll work or not
>> before the release.
>>
>> Kalle
>>
>> On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks  wrote:
>>   
>> 
>>> Hi folks,
>>>
>>> I'm using the Changes plugin to both produce a report for my Site and to
>>> distribute email announcements of changes.  The problem is that if we're
>>> not careful to remember to update the changes.xml file itself, then our
>>> release build fails because it doesn't find a change set with the right
>>> version.  I'd really like to find some way to automatically update the
>>> changes.xml file during the release build process.  Can anyone recommend
>>> a plugin that might let me make modifications to this xml file at build
>>> time?  Or, any other suggestions?
>>>
>>> Thanks,
>>> Dave
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>> 
>>>   
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>   
>> 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-changes-plugin: automatic update for release?

[David C. Hicks]

Good suggestion.  I hadn't really thought of using CI to test the
changes.xml.  That's primarily because I also have the dependencies
report generated as part of the Site generation.  Under normal
circumstances, it takes forever and a day to generate the dependencies
report, since it appears to hit the Internet to find all the
dependencies, instead of using the local repository.

I suppose I can restructure my CI build to exclude the dependencies
report and get some useful information about the changes report.

Thanks!

Kalle Korhonen wrote:
> Changes plugin offers Jira and Trac integration. You can filter your
> changes.xml if you cannot use current version only. Use ci system to
> run the site and changes report so you know if it'll work or not
> before the release.
>
> Kalle
>
> On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks  wrote:
>   
>> Hi folks,
>>
>> I'm using the Changes plugin to both produce a report for my Site and to
>> distribute email announcements of changes.  The problem is that if we're
>> not careful to remember to update the changes.xml file itself, then our
>> release build fails because it doesn't find a change set with the right
>> version.  I'd really like to find some way to automatically update the
>> changes.xml file during the release build process.  Can anyone recommend
>> a plugin that might let me make modifications to this xml file at build
>> time?  Or, any other suggestions?
>>
>> Thanks,
>> Dave
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>> 
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>   

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-changes-plugin: automatic update for release?

[Kalle Korhonen]

Changes plugin offers Jira and Trac integration. You can filter your
changes.xml if you cannot use current version only. Use ci system to
run the site and changes report so you know if it'll work or not
before the release.

Kalle

On Wed, Nov 18, 2009 at 12:56 PM, David C. Hicks  wrote:
> Hi folks,
>
> I'm using the Changes plugin to both produce a report for my Site and to
> distribute email announcements of changes.  The problem is that if we're
> not careful to remember to update the changes.xml file itself, then our
> release build fails because it doesn't find a change set with the right
> version.  I'd really like to find some way to automatically update the
> changes.xml file during the release build process.  Can anyone recommend
> a plugin that might let me make modifications to this xml file at build
> time?  Or, any other suggestions?
>
> Thanks,
> Dave
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Jonathan Gold]

Jamie --

Thanks for the response. I don't have mod_d depending on a snapshot -- just on
the sibling module itself. Also, I'm not installing versions in the local repo
at the point I'm seeing this problem (and would rather not, actually, since it's
just for development anyway).

If mod_d was depending on a SNAPSHOT version (I saw something about SNAPSHOTS in
the docs, I'll go back and take a look), do you think that would have some
effect?

jon

On Wed, Nov 18, 2009 at 12:30:34PM -0800, Jamie Whitehouse wrote:
> AFAIK dependency tree does not run in the reactor.  Is mod_d depending
> on a SNAPSHOT version of mod_c?  Do you have that version installed in
> your local repo?
> 
> I have used dependency tree many time on a large mutli-module project so
> I can attest that it does work in some form. 
> 
> -Original Message-
> From: Jonathan Gold [mailto:jgold...@gmail.com] 
> Sent: Wednesday, November 18, 2009 12:37 PM
> To: users@maven.apache.org
> Subject: Why would 'mvn dependencies:tree' fail while 'mvn compile'
> works?
> 
> Hi --
> 
> I'm trying to track down some other depdendency issues in my project
> using dependencies:tree, but am getting errors that a module isn't
> found.
> 
> I have my project set up with a parent pom and a list of modules, each
> referencing the parent, etc. Essentially, I have this:
> 
> pom.xml # parent, references mods a, b, c, d in 
> mod_a/pom.xml # module, no module dependencies
> mod_b/pom.xml # module, no module dependencies
> mod_c/pom.xml # module, declared dependency on mod_b
> mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c
> 
> >From the root workspace directory, I can run things like 'compile' or
> 'jar:jar'
> just fine, but for some reason 'dependencies:tree' is failing when it
> gets to mod_d, complaining that it can't find mod_c.
> 
> Any ideas what I'm doing wrong?
> 
> jon
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
>   
> ---
> CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain 
> confidential and proprietary information of Alcatel-Lucent and/or its 
> affiliated entities. Access by the intended recipient only is authorized. Any 
> liability arising from any party acting, or refraining from acting, on any 
> information contained in this e-mail is hereby excluded. If you are not the 
> intended recipient, please notify the sender immediately, destroy the 
> original transmission and its attachments and do not disclose the contents to 
> any other person, use it for any purpose, or store or copy the information in 
> any medium. Copyright in this e-mail and any attachments belongs to 
> Alcatel-Lucent and/or its affiliated entities.
>   
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven-changes-plugin: automatic update for release?

[David C. Hicks]

Hi folks,

I'm using the Changes plugin to both produce a report for my Site and to
distribute email announcements of changes.  The problem is that if we're
not careful to remember to update the changes.xml file itself, then our
release build fails because it doesn't find a change set with the right
version.  I'd really like to find some way to automatically update the
changes.xml file during the release build process.  Can anyone recommend
a plugin that might let me make modifications to this xml file at build
time?  Or, any other suggestions?

Thanks,
Dave


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Jamie Whitehouse]

AFAIK dependency tree does not run in the reactor.  Is mod_d depending
on a SNAPSHOT version of mod_c?  Do you have that version installed in
your local repo?

I have used dependency tree many time on a large mutli-module project so
I can attest that it does work in some form. 

-Original Message-
From: Jonathan Gold [mailto:jgold...@gmail.com] 
Sent: Wednesday, November 18, 2009 12:37 PM
To: users@maven.apache.org
Subject: Why would 'mvn dependencies:tree' fail while 'mvn compile'
works?

Hi --

I'm trying to track down some other depdendency issues in my project
using dependencies:tree, but am getting errors that a module isn't
found.

I have my project set up with a parent pom and a list of modules, each
referencing the parent, etc. Essentially, I have this:

pom.xml # parent, references mods a, b, c, d in 
mod_a/pom.xml # module, no module dependencies
mod_b/pom.xml # module, no module dependencies
mod_c/pom.xml # module, declared dependency on mod_b
mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c

>From the root workspace directory, I can run things like 'compile' or
'jar:jar'
just fine, but for some reason 'dependencies:tree' is failing when it
gets to mod_d, complaining that it can't find mod_c.

Any ideas what I'm doing wrong?

jon

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



---
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain 
confidential and proprietary information of Alcatel-Lucent and/or its 
affiliated entities. Access by the intended recipient only is authorized. Any 
liability arising from any party acting, or refraining from acting, on any 
information contained in this e-mail is hereby excluded. If you are not the 
intended recipient, please notify the sender immediately, destroy the original 
transmission and its attachments and do not disclose the contents to any other 
person, use it for any purpose, or store or copy the information in any medium. 
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or 
its affiliated entities.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Defining NetBeans 6.7 Actions Externally In Maven2 2.2.1

[Milos Kleint]

sorry, there is no such way, not an supported one. You can surely configure
a project to have something executed with a given configuration via
profiles, but I suppose that is not what you are looking for. Maven2 is
different from m1 and also the ide integration became more elaborate. Some
properties you can set, like IDE's deployment server, JDK platform to use or
similar, but it became unpractical for action bindings..

Milos

On Wed, Nov 18, 2009 at 9:05 PM, rickbryant  wrote:

>
> Milos,
>
> Thanks for your reply and we are already aware of how to bind
> NetBeans/Maven
> actions within the NetBeans application. However, instead of configuring
> NetBeans for this we want to be able to do the same thing declaratively
> using properties in the external Maven profiles.xml file. We have done this
> successfully in the past with NetBeans 5.5/Maven 1.0.2 and just need to
> know
> if it can be done with the latest version of these applications.
>
> Thanks,
> Rick
>
>
> Bugzilla from mkle...@gmail.com wrote:
> >
> >
> http://wiki.netbeans.org/MavenBestPractices#Binding_Maven_goals_to_IDE_actions
> >
> > <
> http://wiki.netbeans.org/MavenBestPractices#Binding_Maven_goals_to_IDE_actions
> >
> > Milos
> >
> > On Wed, Nov 18, 2009 at 7:37 PM, rickbryant  wrote:
> >
> >>
> >> All:
> >>
> >> We just upgraded from Maven1 1.0.2 to Maven2 2.2.1 and from NetBeans 5.5
> >> to
> >> NetBeans 6.7. With our previous setup we could specify NetBeans 5.5
> >> actions
> >> in the Maven1 1.0.2 build.properties file as follows:
> >> maven.netbeans.exec.debug.single=-Dmaven.mevenide.run.classname=%CLASS%
> >> java:compile mevenide:debug-class
> >> maven.netbeans.exec.run.single=-Dmaven.mevenide.run.classname=%CLASS%
> >> java:compile mevenide:run-class
> >> maven.netbeans.exec.rebuild=clean web-deploy-nowar
> >> maven.netbeans.exec.build=web-deploy-nowar
> >> and the corresponding menu selections in NetBeans 5.5 would use these
> >> actions instead of the built in actions.
> >>
> >> Is it possible to also specify NetBeans 6.7 actions externally in the
> >> Maven2
> >> 2.2.1 profiles.xml (or pom.xml or settings.xml) file? If so, which
> >> specific
> >> NetBeans 6.7 action attributes are available and how are these declared?
> >>
> >> Thanks,
> >> Rick
> >>
> >> --
> >> View this message in context:
> >>
> http://old.nabble.com/Defining-NetBeans-6.7-Actions-Externally-In-Maven2-2.2.1-tp26413299p26413299.html
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/Defining-NetBeans-6.7-Actions-Externally-In-Maven2-2.2.1-tp26413299p26414750.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Defining NetBeans 6.7 Actions Externally In Maven2 2.2.1

[rickbryant]

Milos,

Thanks for your reply and we are already aware of how to bind NetBeans/Maven
actions within the NetBeans application. However, instead of configuring
NetBeans for this we want to be able to do the same thing declaratively
using properties in the external Maven profiles.xml file. We have done this
successfully in the past with NetBeans 5.5/Maven 1.0.2 and just need to know
if it can be done with the latest version of these applications. 

Thanks,
Rick 


Bugzilla from mkle...@gmail.com wrote:
> 
> http://wiki.netbeans.org/MavenBestPractices#Binding_Maven_goals_to_IDE_actions
> 
> 
> Milos
> 
> On Wed, Nov 18, 2009 at 7:37 PM, rickbryant  wrote:
> 
>>
>> All:
>>
>> We just upgraded from Maven1 1.0.2 to Maven2 2.2.1 and from NetBeans 5.5
>> to
>> NetBeans 6.7. With our previous setup we could specify NetBeans 5.5
>> actions
>> in the Maven1 1.0.2 build.properties file as follows:
>> maven.netbeans.exec.debug.single=-Dmaven.mevenide.run.classname=%CLASS%
>> java:compile mevenide:debug-class
>> maven.netbeans.exec.run.single=-Dmaven.mevenide.run.classname=%CLASS%
>> java:compile mevenide:run-class
>> maven.netbeans.exec.rebuild=clean web-deploy-nowar
>> maven.netbeans.exec.build=web-deploy-nowar
>> and the corresponding menu selections in NetBeans 5.5 would use these
>> actions instead of the built in actions.
>>
>> Is it possible to also specify NetBeans 6.7 actions externally in the
>> Maven2
>> 2.2.1 profiles.xml (or pom.xml or settings.xml) file? If so, which
>> specific
>> NetBeans 6.7 action attributes are available and how are these declared?
>>
>> Thanks,
>> Rick
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Defining-NetBeans-6.7-Actions-Externally-In-Maven2-2.2.1-tp26413299p26413299.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Defining-NetBeans-6.7-Actions-Externally-In-Maven2-2.2.1-tp26413299p26414750.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Defining NetBeans 6.7 Actions Externally In Maven2 2.2.1

[Milos Kleint]

http://wiki.netbeans.org/MavenBestPractices#Binding_Maven_goals_to_IDE_actions


Milos

On Wed, Nov 18, 2009 at 7:37 PM, rickbryant  wrote:

>
> All:
>
> We just upgraded from Maven1 1.0.2 to Maven2 2.2.1 and from NetBeans 5.5 to
> NetBeans 6.7. With our previous setup we could specify NetBeans 5.5 actions
> in the Maven1 1.0.2 build.properties file as follows:
> maven.netbeans.exec.debug.single=-Dmaven.mevenide.run.classname=%CLASS%
> java:compile mevenide:debug-class
> maven.netbeans.exec.run.single=-Dmaven.mevenide.run.classname=%CLASS%
> java:compile mevenide:run-class
> maven.netbeans.exec.rebuild=clean web-deploy-nowar
> maven.netbeans.exec.build=web-deploy-nowar
> and the corresponding menu selections in NetBeans 5.5 would use these
> actions instead of the built in actions.
>
> Is it possible to also specify NetBeans 6.7 actions externally in the
> Maven2
> 2.2.1 profiles.xml (or pom.xml or settings.xml) file? If so, which specific
> NetBeans 6.7 action attributes are available and how are these declared?
>
> Thanks,
> Rick
>
> --
> View this message in context:
> http://old.nabble.com/Defining-NetBeans-6.7-Actions-Externally-In-Maven2-2.2.1-tp26413299p26413299.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Defining NetBeans 6.7 Actions Externally In Maven2 2.2.1

[rickbryant]

All:

We just upgraded from Maven1 1.0.2 to Maven2 2.2.1 and from NetBeans 5.5 to
NetBeans 6.7. With our previous setup we could specify NetBeans 5.5 actions
in the Maven1 1.0.2 build.properties file as follows:
maven.netbeans.exec.debug.single=-Dmaven.mevenide.run.classname=%CLASS%
java:compile mevenide:debug-class
maven.netbeans.exec.run.single=-Dmaven.mevenide.run.classname=%CLASS%
java:compile mevenide:run-class
maven.netbeans.exec.rebuild=clean web-deploy-nowar
maven.netbeans.exec.build=web-deploy-nowar
and the corresponding menu selections in NetBeans 5.5 would use these
actions instead of the built in actions.

Is it possible to also specify NetBeans 6.7 actions externally in the Maven2
2.2.1 profiles.xml (or pom.xml or settings.xml) file? If so, which specific
NetBeans 6.7 action attributes are available and how are these declared?

Thanks,
Rick
 
-- 
View this message in context: 
http://old.nabble.com/Defining-NetBeans-6.7-Actions-Externally-In-Maven2-2.2.1-tp26413299p26413299.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Stevo Slavić]

You could try to install your project first, and after that run
dependency:tree.

Regards,
Stevo.

On Wed, Nov 18, 2009 at 7:05 PM, Jonathan Gold  wrote:

> Thanks for the response. In fact, I have all of my modules listed in
> depdendency
> order in the parent pom, so it's quite odd indeed.
>
> Thanks for the tip -- I voted for the bug, for what it's worth.
>
> jon
>
> On Wed, Nov 18, 2009 at 06:59:41PM +0100, Stevo Slavić wrote:
> > Likely because dependency plugin has bugs, and I'm suspecting that your
> > issue is similar/related to this
> > one already reported.
> >
> > But it's odd that it doesn't fail for you at module mod_c, as build
> reactor
> > should have ordered mod_c to be built/processed before mod_d. Just
> guessing,
> > maybe this mojo doesn't use maven reactor at all, and probably mod_c is
> > ordered in list of modules in your parent module after mod_d.
> >
> > Regards,
> > Stevo.
> >
> > On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold 
> wrote:
> >
> > > Hi --
> > >
> > > I'm trying to track down some other depdendency issues in my project
> using
> > > dependencies:tree, but am getting errors that a module isn't found.
> > >
> > > I have my project set up with a parent pom and a list of modules, each
> > > referencing the parent, etc. Essentially, I have this:
> > >
> > >pom.xml # parent, references mods a, b, c, d in 
> > >mod_a/pom.xml # module, no module dependencies
> > >mod_b/pom.xml # module, no module dependencies
> > >mod_c/pom.xml # module, declared dependency on mod_b
> > >mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c
> > >
> > > From the root workspace directory, I can run things like 'compile' or
> > > 'jar:jar'
> > > just fine, but for some reason 'dependencies:tree' is failing when it
> gets
> > > to
> > > mod_d, complaining that it can't find mod_c.
> > >
> > > Any ideas what I'm doing wrong?
> > >
> > > jon
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Jonathan Gold]

Thanks for the response. In fact, I have all of my modules listed in depdendency
order in the parent pom, so it's quite odd indeed.

Thanks for the tip -- I voted for the bug, for what it's worth.

jon

On Wed, Nov 18, 2009 at 06:59:41PM +0100, Stevo Slavić wrote:
> Likely because dependency plugin has bugs, and I'm suspecting that your
> issue is similar/related to this
> one already reported.
> 
> But it's odd that it doesn't fail for you at module mod_c, as build reactor
> should have ordered mod_c to be built/processed before mod_d. Just guessing,
> maybe this mojo doesn't use maven reactor at all, and probably mod_c is
> ordered in list of modules in your parent module after mod_d.
> 
> Regards,
> Stevo.
> 
> On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold  wrote:
> 
> > Hi --
> >
> > I'm trying to track down some other depdendency issues in my project using
> > dependencies:tree, but am getting errors that a module isn't found.
> >
> > I have my project set up with a parent pom and a list of modules, each
> > referencing the parent, etc. Essentially, I have this:
> >
> >pom.xml # parent, references mods a, b, c, d in 
> >mod_a/pom.xml # module, no module dependencies
> >mod_b/pom.xml # module, no module dependencies
> >mod_c/pom.xml # module, declared dependency on mod_b
> >mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c
> >
> > From the root workspace directory, I can run things like 'compile' or
> > 'jar:jar'
> > just fine, but for some reason 'dependencies:tree' is failing when it gets
> > to
> > mod_d, complaining that it can't find mod_c.
> >
> > Any ideas what I'm doing wrong?
> >
> > jon
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Stevo Slavić]

Likely because dependency plugin has bugs, and I'm suspecting that your
issue is similar/related to this
one already reported.

But it's odd that it doesn't fail for you at module mod_c, as build reactor
should have ordered mod_c to be built/processed before mod_d. Just guessing,
maybe this mojo doesn't use maven reactor at all, and probably mod_c is
ordered in list of modules in your parent module after mod_d.

Regards,
Stevo.

On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold  wrote:

> Hi --
>
> I'm trying to track down some other depdendency issues in my project using
> dependencies:tree, but am getting errors that a module isn't found.
>
> I have my project set up with a parent pom and a list of modules, each
> referencing the parent, etc. Essentially, I have this:
>
>pom.xml # parent, references mods a, b, c, d in 
>mod_a/pom.xml # module, no module dependencies
>mod_b/pom.xml # module, no module dependencies
>mod_c/pom.xml # module, declared dependency on mod_b
>mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c
>
> From the root workspace directory, I can run things like 'compile' or
> 'jar:jar'
> just fine, but for some reason 'dependencies:tree' is failing when it gets
> to
> mod_d, complaining that it can't find mod_c.
>
> Any ideas what I'm doing wrong?
>
> jon
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Why would 'mvn dependencies:tree' fail while 'mvn compile' works?

[Jonathan Gold]

Hi --

I'm trying to track down some other depdendency issues in my project using
dependencies:tree, but am getting errors that a module isn't found.

I have my project set up with a parent pom and a list of modules, each
referencing the parent, etc. Essentially, I have this:

pom.xml # parent, references mods a, b, c, d in 
mod_a/pom.xml # module, no module dependencies
mod_b/pom.xml # module, no module dependencies
mod_c/pom.xml # module, declared dependency on mod_b
mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c

>From the root workspace directory, I can run things like 'compile' or 'jar:jar'
just fine, but for some reason 'dependencies:tree' is failing when it gets to
mod_d, complaining that it can't find mod_c.

Any ideas what I'm doing wrong?

jon

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re : WTP support and Standard Directory Layout

[Julien HENRY]

If your configuration files need to be in the build path, I suggest to move 
them to src/main/resources.

src/main/config is never used AFAIK, so it main be simply a conventional place 
to put config files that will not be packaged in the artifact (someone can 
correct me if I am wrong).


++

Julien


- Message d'origine 
> De : Richard Hauswald 
> À : users@maven.apache.org
> Envoyé le : Mer 18 Novembre 2009, 13 h 09 min 35 s
> Objet : WTP support and Standard Directory Layout
> 
> Hello list,
> as described in the Standard Directory Layout
> (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
> configuration files should be placed under src/main/config . But this
> directory is not included in the build path. The directories
> 
> src/main/filters
> src/test/java
> src/test/resources
> src/test/filters
> 
> are ignored too. Is this intended behaviour or a bug?
> 
> Thanks,
> Richard
> 
> 
> 
> -- 
> Richard Hauswald
> Blog: http://tnfstacc.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/richardhauswald
> Xing: http://www.xing.com/profile/Richard_Hauswald
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: maven post install plugin?

[Jamie Whitehouse]

You could use the maven-exec or maven-antrun plugins and bind those to
the phase that you need.  See
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycl
e.html#Lifecycle_Reference .

If you really need it to run after Maven has installed the artifacts
into the local repo I think you may be out of luck.  There is no
'post-install' phase that you could use, although I suspect that binding
to install will be good enough.

-Original Message-
From: eyal edri [mailto:eyal.e...@gmail.com] 
Sent: Wednesday, November 18, 2009 6:20 AM
To: Maven Users List
Subject: maven post install plugin?

Is there a maven plugin/configuration that enables you to run post
install actions?

in rpm.spec file you can specify %post actions such as "mkdir -p
/var/spool/app/logs" or running bash scripts.

is there an equivalent plugin in maven? or one has to write a new plugin
in order to accomplish this ?

thanks!

--
Eyal Edri


---
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain 
confidential and proprietary information of Alcatel-Lucent and/or its 
affiliated entities. Access by the intended recipient only is authorized. Any 
liability arising from any party acting, or refraining from acting, on any 
information contained in this e-mail is hereby excluded. If you are not the 
intended recipient, please notify the sender immediately, destroy the original 
transmission and its attachments and do not disclose the contents to any other 
person, use it for any purpose, or store or copy the information in any medium. 
Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or 
its affiliated entities.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Embedder thread safety

[Anders Hammar]

Fabien,

Please understand that you're cutting edge here and not very many people
have this deep insight in Maven 3. Thus, getting an answer could take more
than one day, if you get one at all.
Also, the maven developer list might be more appropriate for questions like
this.

/Anders

On Wed, Nov 18, 2009 at 14:43, Fabien Coppens wrote:

> Hi folks.
> Any chance I can get an answer to those questions below ?
> Thanks.
> Fabien
>
>  Original Message 
> Subject: Maven Embedder thread safety
> Date: Tue, 17 Nov 2009 14:45:55 +0100
> From: Fabien Coppens 
> Reply-To: Maven Users List 
> To: users@maven.apache.org
>
>
>
> Hi all.
>
> I'm using Maven Embedder 3.0-alpha-2 to execute a dependency:resolve goal
> on a
> large number of POM files (several thousand), using a Java batch runtime.
> For
> performance reasons, I use a thread pool (ThreadPoolExecutor) to
> parallelize the
> calls to the embedder's execute method.
> However, after a quick look at the code, it seems that the execute method
> is not
> thread safe, is that correct ?
>
> Secondary question : I downloaded both maven-embedder-3.0-alpha-3.jar and
> maven-embedder-3.0-alpha-4.jar, and in both jars the
> org.apache.maven.embedder
> API is missing. Any reasons why ?
>
> Fabien
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: WTP support and Standard Directory Layout

[Richard Hauswald]

thanks for your help

On Wed, Nov 18, 2009 at 2:12 PM, Anders Hammar  wrote:
> http://m2eclipse.sonatype.org/project-information.html
>
> On Wed, Nov 18, 2009 at 14:07, Richard Hauswald <
> richard.hausw...@googlemail.com> wrote:
>
>> I got the link to this mailing list from:
>> http://maven.apache.org/plugins/maven-eclipse-plugin/mail-lists.html
>>
>> Can you point me to the right location?
>>
>> On Wed, Nov 18, 2009 at 2:05 PM, Anders Hammar  wrote:
>> > Ok, wrong mailing list then. Try the m2eclipse one.
>> >
>> > /Anders
>> >
>> > On Wed, Nov 18, 2009 at 13:44, Richard Hauswald <
>> > richard.hausw...@googlemail.com> wrote:
>> >
>> >> I'm referring the eclipse build path.
>> >>
>> >> On Wed, Nov 18, 2009 at 1:21 PM, Anders Hammar 
>> wrote:
>> >> > Is this a Maven question or an Eclipse (WTP) question? The subject
>> says
>> >> WTP
>> >> > so I wonder what build path you're referring to.
>> >> >
>> >> > /Anders
>> >> >
>> >> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
>> >> > richard.hausw...@googlemail.com> wrote:
>> >> >
>> >> >> Hello list,
>> >> >> as described in the Standard Directory Layout
>> >> >> (
>> >> >>
>> >>
>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>> >> >> )
>> >> >> configuration files should be placed under src/main/config . But this
>> >> >> directory is not included in the build path. The directories
>> >> >>
>> >> >> src/main/filters
>> >> >> src/test/java
>> >> >> src/test/resources
>> >> >> src/test/filters
>> >> >>
>> >> >> are ignored too. Is this intended behaviour or a bug?
>> >> >>
>> >> >> Thanks,
>> >> >> Richard
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Richard Hauswald
>> >> >> Blog: http://tnfstacc.blogspot.com/
>> >> >> LinkedIn: http://www.linkedin.com/in/richardhauswald
>> >> >> Xing: http://www.xing.com/profile/Richard_Hauswald
>> >> >>
>> >> >> -
>> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Richard Hauswald
>> >> Blog: http://tnfstacc.blogspot.com/
>> >> LinkedIn: http://www.linkedin.com/in/richardhauswald
>> >> Xing: http://www.xing.com/profile/Richard_Hauswald
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Richard Hauswald
>> Blog: http://tnfstacc.blogspot.com/
>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>



-- 
Richard Hauswald
Blog: http://tnfstacc.blogspot.com/
LinkedIn: http://www.linkedin.com/in/richardhauswald
Xing: http://www.xing.com/profile/Richard_Hauswald

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Embedder thread safety

[Fabien Coppens]

Hi folks.
Any chance I can get an answer to those questions below ?
Thanks.
Fabien

 Original Message 
Subject: Maven Embedder thread safety
Date: Tue, 17 Nov 2009 14:45:55 +0100
From: Fabien Coppens 
Reply-To: Maven Users List 
To: users@maven.apache.org



Hi all.

I'm using Maven Embedder 3.0-alpha-2 to execute a dependency:resolve goal on a
large number of POM files (several thousand), using a Java batch runtime. For
performance reasons, I use a thread pool (ThreadPoolExecutor) to parallelize the
calls to the embedder's execute method.
However, after a quick look at the code, it seems that the execute method is not
thread safe, is that correct ?

Secondary question : I downloaded both maven-embedder-3.0-alpha-3.jar and
maven-embedder-3.0-alpha-4.jar, and in both jars the org.apache.maven.embedder
API is missing. Any reasons why ?

Fabien


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: WTP support and Standard Directory Layout

[Anders Hammar]

http://m2eclipse.sonatype.org/project-information.html

On Wed, Nov 18, 2009 at 14:07, Richard Hauswald <
richard.hausw...@googlemail.com> wrote:

> I got the link to this mailing list from:
> http://maven.apache.org/plugins/maven-eclipse-plugin/mail-lists.html
>
> Can you point me to the right location?
>
> On Wed, Nov 18, 2009 at 2:05 PM, Anders Hammar  wrote:
> > Ok, wrong mailing list then. Try the m2eclipse one.
> >
> > /Anders
> >
> > On Wed, Nov 18, 2009 at 13:44, Richard Hauswald <
> > richard.hausw...@googlemail.com> wrote:
> >
> >> I'm referring the eclipse build path.
> >>
> >> On Wed, Nov 18, 2009 at 1:21 PM, Anders Hammar 
> wrote:
> >> > Is this a Maven question or an Eclipse (WTP) question? The subject
> says
> >> WTP
> >> > so I wonder what build path you're referring to.
> >> >
> >> > /Anders
> >> >
> >> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
> >> > richard.hausw...@googlemail.com> wrote:
> >> >
> >> >> Hello list,
> >> >> as described in the Standard Directory Layout
> >> >> (
> >> >>
> >>
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> >> >> )
> >> >> configuration files should be placed under src/main/config . But this
> >> >> directory is not included in the build path. The directories
> >> >>
> >> >> src/main/filters
> >> >> src/test/java
> >> >> src/test/resources
> >> >> src/test/filters
> >> >>
> >> >> are ignored too. Is this intended behaviour or a bug?
> >> >>
> >> >> Thanks,
> >> >> Richard
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Richard Hauswald
> >> >> Blog: http://tnfstacc.blogspot.com/
> >> >> LinkedIn: http://www.linkedin.com/in/richardhauswald
> >> >> Xing: http://www.xing.com/profile/Richard_Hauswald
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> >> For additional commands, e-mail: users-h...@maven.apache.org
> >> >>
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Richard Hauswald
> >> Blog: http://tnfstacc.blogspot.com/
> >> LinkedIn: http://www.linkedin.com/in/richardhauswald
> >> Xing: http://www.xing.com/profile/Richard_Hauswald
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
>
>
> --
> Richard Hauswald
> Blog: http://tnfstacc.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/richardhauswald
> Xing: http://www.xing.com/profile/Richard_Hauswald
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: WTP support and Standard Directory Layout

[Richard Hauswald]

I got the link to this mailing list from:
http://maven.apache.org/plugins/maven-eclipse-plugin/mail-lists.html

Can you point me to the right location?

On Wed, Nov 18, 2009 at 2:05 PM, Anders Hammar  wrote:
> Ok, wrong mailing list then. Try the m2eclipse one.
>
> /Anders
>
> On Wed, Nov 18, 2009 at 13:44, Richard Hauswald <
> richard.hausw...@googlemail.com> wrote:
>
>> I'm referring the eclipse build path.
>>
>> On Wed, Nov 18, 2009 at 1:21 PM, Anders Hammar  wrote:
>> > Is this a Maven question or an Eclipse (WTP) question? The subject says
>> WTP
>> > so I wonder what build path you're referring to.
>> >
>> > /Anders
>> >
>> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
>> > richard.hausw...@googlemail.com> wrote:
>> >
>> >> Hello list,
>> >> as described in the Standard Directory Layout
>> >> (
>> >>
>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>> >> )
>> >> configuration files should be placed under src/main/config . But this
>> >> directory is not included in the build path. The directories
>> >>
>> >> src/main/filters
>> >> src/test/java
>> >> src/test/resources
>> >> src/test/filters
>> >>
>> >> are ignored too. Is this intended behaviour or a bug?
>> >>
>> >> Thanks,
>> >> Richard
>> >>
>> >>
>> >>
>> >> --
>> >> Richard Hauswald
>> >> Blog: http://tnfstacc.blogspot.com/
>> >> LinkedIn: http://www.linkedin.com/in/richardhauswald
>> >> Xing: http://www.xing.com/profile/Richard_Hauswald
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Richard Hauswald
>> Blog: http://tnfstacc.blogspot.com/
>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>



-- 
Richard Hauswald
Blog: http://tnfstacc.blogspot.com/
LinkedIn: http://www.linkedin.com/in/richardhauswald
Xing: http://www.xing.com/profile/Richard_Hauswald

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: WTP support and Standard Directory Layout

[Anders Hammar]

Ok, wrong mailing list then. Try the m2eclipse one.

/Anders

On Wed, Nov 18, 2009 at 13:44, Richard Hauswald <
richard.hausw...@googlemail.com> wrote:

> I'm referring the eclipse build path.
>
> On Wed, Nov 18, 2009 at 1:21 PM, Anders Hammar  wrote:
> > Is this a Maven question or an Eclipse (WTP) question? The subject says
> WTP
> > so I wonder what build path you're referring to.
> >
> > /Anders
> >
> > On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
> > richard.hausw...@googlemail.com> wrote:
> >
> >> Hello list,
> >> as described in the Standard Directory Layout
> >> (
> >>
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> >> )
> >> configuration files should be placed under src/main/config . But this
> >> directory is not included in the build path. The directories
> >>
> >> src/main/filters
> >> src/test/java
> >> src/test/resources
> >> src/test/filters
> >>
> >> are ignored too. Is this intended behaviour or a bug?
> >>
> >> Thanks,
> >> Richard
> >>
> >>
> >>
> >> --
> >> Richard Hauswald
> >> Blog: http://tnfstacc.blogspot.com/
> >> LinkedIn: http://www.linkedin.com/in/richardhauswald
> >> Xing: http://www.xing.com/profile/Richard_Hauswald
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
>
>
> --
> Richard Hauswald
> Blog: http://tnfstacc.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/richardhauswald
> Xing: http://www.xing.com/profile/Richard_Hauswald
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: WTP support and Standard Directory Layout

[Richard Hauswald]

I'm referring the eclipse build path.

On Wed, Nov 18, 2009 at 1:21 PM, Anders Hammar  wrote:
> Is this a Maven question or an Eclipse (WTP) question? The subject says WTP
> so I wonder what build path you're referring to.
>
> /Anders
>
> On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
> richard.hausw...@googlemail.com> wrote:
>
>> Hello list,
>> as described in the Standard Directory Layout
>> (
>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
>> )
>> configuration files should be placed under src/main/config . But this
>> directory is not included in the build path. The directories
>>
>> src/main/filters
>> src/test/java
>> src/test/resources
>> src/test/filters
>>
>> are ignored too. Is this intended behaviour or a bug?
>>
>> Thanks,
>> Richard
>>
>>
>>
>> --
>> Richard Hauswald
>> Blog: http://tnfstacc.blogspot.com/
>> LinkedIn: http://www.linkedin.com/in/richardhauswald
>> Xing: http://www.xing.com/profile/Richard_Hauswald
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>



-- 
Richard Hauswald
Blog: http://tnfstacc.blogspot.com/
LinkedIn: http://www.linkedin.com/in/richardhauswald
Xing: http://www.xing.com/profile/Richard_Hauswald

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

NPE in maven-plugin-plugin-2.5.1

[Sommers, Elizabeth]

I finally got my plugin to compile and when I try to run it on a test
project I get this NPE dump.  Notice that none of this code is generated
by me. But is all part of the code that is parsing components.xml (I
think).  After the dump I am including the relevant part of my
component.xml.

 getDate is properly processed but resources never gets called.


All of this code worked with earlier (2.0.5 - 2.0.9) versions of maven
Any help will be appreciated.

Thanks
Liz


[INFO] Trace
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:394)
at java.util.Properties.setProperty(Properties.java:143)
at
org.apache.maven.project.ModelUtils.cloneProperties(ModelUtils.java:1264
)
at
org.apache.maven.project.ModelUtils.cloneModelBaseFields(ModelUtils.java
:318)
at
org.apache.maven.project.ModelUtils.cloneModel(ModelUtils.java:953)
at
org.apache.maven.project.DefaultMavenProjectBuilder.calculateConcreteSta
teInternal(DefaultMavenProjectBuilder.java:1855)
at
org.apache.maven.project.DefaultMavenProjectBuilder.calculateConcreteSta
te(DefaultMavenProjectBuilder.java:1814)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.calculateConcreteSta
te(DefaultLifecycleExecutor.java:795)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default
LifecycleExecutor.java:591)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:180)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)







com.pragmatics.package-tools:maven-package-plugin:getDate



org.apache.maven.plugins:maven-resources-plugin:resources,

com.pragmatics.package-tools:maven-package-plugin:delete-bogus,

com.pragmatics.package-tools:maven-package-plugin:generate-segdocs,

com.pragmatics.package-tools:maven-package-plugin:prepare




...



Elizabeth Sommers
Build and Release Engineer
Pragmatics, Inc.
703.761.4033

www.pragmatics.com 

Practical. Reliable. Secure.

This e-mail message, including any attachments, is intended only for the
identified recipient(s). It may contain proprietary or otherwise legally
protected information of Pragmatics, Inc. Any unauthorized review, use,
copying, disclosure or distribution is strictly prohibited. If you have
received this communication in error and are not the intended recipient,
please immediately notify the sender of this message by reply e-mail and
delete or otherwise destroy the e-mail, attachments, and any copies.

 

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: WTP support and Standard Directory Layout

[Anders Hammar]

Is this a Maven question or an Eclipse (WTP) question? The subject says WTP
so I wonder what build path you're referring to.

/Anders

On Wed, Nov 18, 2009 at 13:09, Richard Hauswald <
richard.hausw...@googlemail.com> wrote:

> Hello list,
> as described in the Standard Directory Layout
> (
> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
> )
> configuration files should be placed under src/main/config . But this
> directory is not included in the build path. The directories
>
> src/main/filters
> src/test/java
> src/test/resources
> src/test/filters
>
> are ignored too. Is this intended behaviour or a bug?
>
> Thanks,
> Richard
>
>
>
> --
> Richard Hauswald
> Blog: http://tnfstacc.blogspot.com/
> LinkedIn: http://www.linkedin.com/in/richardhauswald
> Xing: http://www.xing.com/profile/Richard_Hauswald
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

WTP support and Standard Directory Layout

[Richard Hauswald]

Hello list,
as described in the Standard Directory Layout
(http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
configuration files should be placed under src/main/config . But this
directory is not included in the build path. The directories

src/main/filters
src/test/java
src/test/resources
src/test/filters

are ignored too. Is this intended behaviour or a bug?

Thanks,
Richard



-- 
Richard Hauswald
Blog: http://tnfstacc.blogspot.com/
LinkedIn: http://www.linkedin.com/in/richardhauswald
Xing: http://www.xing.com/profile/Richard_Hauswald

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

maven post install plugin?

[eyal edri]

Is there a maven plugin/configuration that enables you to run post install
actions?

in rpm.spec file you can specify %post actions such as "mkdir -p
/var/spool/app/logs" or running bash scripts.

is there an equivalent plugin in maven? or one has to write a new plugin in
order to accomplish this ?

thanks!

-- 
Eyal Edri

Re: maven assembly: how to create an execution JAR without packing the dependencies

[eyal edri]

Finally it worked ! :) (thanks Alexander!)

Summarizing:

in order to create an executable JAR file that will depend on other
libraries/jars from other internal project or external without including
them inside the JAR's project:

1. use maven jar plugin to define the mail class in the manifest:
2. use maven dependency plugin to copy the dependencies to your classpath.


one last thing, how to i tell the pom to copy the executable jar to it's
target dir (e.g. /usr/local/bin).
i can do it with copy-resources, but i don't think it was meant for it..


here's the full pom.xml:


http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
  4.0.0
  com.company.url.unknowns
  IncreasePriority
  jar
  1.00.
  IncreasePriority
  http://maven.apache.org
  
company
http://www.company.com
  
  

  ${env.USER}
  ${user.name}
  ${env.us...@company.com 
  company
  http://www.company.com
  
developer
  
  +2

  
  


org.apache.maven.plugins
maven-dependency-plugin

  
copy-dependencies
package

  copy-dependencies


  /usr/lib/company/java
  false
  false
  true

  

  
  
maven-resources-plugin
2.4.1

  
copy-conf
install

  copy-resources



/etc/ct-urlf-increase-priority/
  

  src/main/resources
  true
  
**/*.properties
  

  

  
  
copy-cron
install

  copy-resources


  /etc/cron.d/
  

  src/main/resources
  true
  
**/*.cron
  

  

  

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

  
   

com.company.url.unknowns.IncreasePriority
   true
   /usr/lib/company/java
   
  

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

  1.6
  1.6

  
  
org.apache.maven.plugins
maven-deploy-plugin
2.4
  

${project.groupId}-${project.artifactId}
  
  

  junit
  junit
  3.8.1
  test


  javax.mail
  mail
  1.4.1


  com.company.file.IniFile
  IniFile
  1.00.


  com.company.sql.DbUtil
  DbUtil
  1.00.0001

  
  
UTF-8
  
  

  company
  http://localhost:8081/nexus/content/repositories/company/

  
  

  company
  company Maven Repository

file://localhost/home/eyale/sonatype-work/nexus/storage/company/

  




On Tue, Nov 17, 2009 at 8:33 PM, Alexander  wrote:

> Question was how make executable jar without including all dependencies in
> application jar but in separate folder.
>
> 2009/11/18 Brian Fox 
>
> >
> >
> http://www.sonatype.com/people/2009/08/how-to-make-an-executable-jar-in-maven/
> >
> > On Tue, Nov 17, 2009 at 1:12 PM, eyal edri  wrote:
> > > i will, once i get to work tomorrow :)
> > >
> > > thanks for the help.
> > >
> > > On Tue, Nov 17, 2009 at 8:05 PM, Alexander 
> > wrote:
> > >
> > >> Dont be shy, just try it.
> > >>
> > >> 2009/11/17 eyal edri 
> > >>
> > >> > can i use the 'dependency:copy-dependencies<
> > >> >
> > >>
> >
> http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html
> > >> > >'
> > >> > goal in this project to tell it to copy all it's
> > >> > dependencies to the "lib" dir?
> > >> > like shown in here:
> > >> >
> > >> >
> > >> > 
> > >> >
> > >> >  
> > >> >org.apache.maven.plugins
> > >> >maven-dependency-plugin
> > >> >
> > >> >  
> > >> >copy-dependencies
> > >> >package
> > >> >
> > >> >  copy-dependencies
> > >> >
> > >> >
> > >> >  /usr/local/app
> > >> >  false
> > >> >  false
> > >> >  true
> > >> >
> > >> >  
> > >> >
> > >> >  
> > >> >
> > >> >  
> > >> >
> > >> >
> > >> >
> > >> > btw: (when you said  *lib*,
> > >> >
> > >> > does this means "projectHome/lib" is the classPath?)
> > >> >
> > >> >
> > >> > On Tue, Nov 17, 2009 at 4:51 PM, Alexander 
> > >

Re: Remote resource plugin doesn't work in release plugin

[alien.sulin]

use maven plugin like this  "mvn somePlugin:goal -Dparam=value" in cmd

the "param" should be the param of somePlugin supply?

And, the ${variable} in the pom file,it should be a variable which maven can
know it,
it can be a environment variable of OS or a property file  configed in the
pom

hope help you , Please forgive my poor English - -

2009/11/17 Max Grigoriev 

> Hi everybody,
>
>
>
> I have a project which uses remote-resources (hibernate mapping files).
>
>
>
> My pom.xml
>
>
>
> ...
>
> 
>
> maven-remote-resources-plugin
>
> 1.1
>
> 
>
> 
>
> 
>
> process
>
> 
>
> 
>
> 
>
>
> com.myproj.sws2:sws-mapping:${sws.mapping.version}
>
> 
>
>
> ${project.build.directory}
>
> false
>
> 
>
> 
>
> 
>
> 
>
> ...
>
> 
>
> maven-release-plugin
>
> 2.0-beta-9
>
> 
>
> https://path-to-svn/tags
>
> 
>
> 
>
> ...
>
>
>
>
>
> When I make mvn package -Dsws.mapping.version=2.0.0 - everything's ok and
> resources are resolved and downloaded also they are put to WAR file.
>
>
>
> But when I try to release this project:
>
>
>
> mvn release:clean release:prepare  -Dsws.mapping.version=2.0.0
> -Dusername=svn_user -Dpassword=svn_passwd
>
>
>
>
>
> And I  receive error:
>
> [INFO] [INFO] [remote-resources:process {execution: default}]
>
> [INFO] [WARNING] Unable to get resource
> 'com.myproj.sws2:sws-mapping:jar:null' from repository myrep (
> http://maven.myrepcom:8081): While configuring wagon for 'mavuser':
>
> Unable to apply wagon configuration.
>
>  [INFO] [INFO]
> 
>
> [INFO] [ERROR] BUILD ERROR
>
> [INFO] [INFO]
> 
>
> [INFO] [INFO] Resources JAR cannot be found.
>
>
>
> As you can see, resource version is unset -
> 'com.myproj.sws2:sws-mapping:jar:null'.
>
>
>
> Why my property (sws.mapping.version) is null not 2.0.0 as I set in command
> line ?
>
>
>
>
>
> Thanks
>
>


-- 
alien.sulin(苏琳冲)
SuLinchong
Qq387973308
Msn  sulinch...@hotmail.com

Re: Maven plugin version number

[Gajo Csaba]

Good idea, I did that approach and it works great!


Anders Hammar wrote:

I would go the normal Java way. Store the version in the manifest and then
use the java.lang.Package object, like this:
clazz.getPackage().getImplementationVersion()

There are loads of discussion about this on the net. Here's one:
http://forums.sun.com/thread.jspa?threadID=642761

/Anders

2009/11/18 Gajo Csaba 

  

Hello,

I'm writing a plugin which is generating certain files, and I would like to
add something like a "Generated by xxx version 1.2.3" string to each file it
generates. The problem is, how can the plugin know its own version (without
hardcoding it)?

Regards, Csaba


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org





  



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven plugin version number

[Nick Stolwijk]

If you get the project inside your plugin you can ask it for the the
plugin map, the key inside the map is groupid:artifactid.

Thus:

/** @parameter default-value="${project}" */
private org.apache.maven.project.MavenProject mavenProject;


mavenProject.getPluginArtifactMap().get("com.example:example-plugin").getVersion();

Hth,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl



2009/11/18 Gajo Csaba :
> Hello,
>
> I'm writing a plugin which is generating certain files, and I would like to
> add something like a "Generated by xxx version 1.2.3" string to each file it
> generates. The problem is, how can the plugin know its own version (without
> hardcoding it)?
>
> Regards, Csaba
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven plugin version number

[Anders Hammar]

I would go the normal Java way. Store the version in the manifest and then
use the java.lang.Package object, like this:
clazz.getPackage().getImplementationVersion()

There are loads of discussion about this on the net. Here's one:
http://forums.sun.com/thread.jspa?threadID=642761

/Anders

2009/11/18 Gajo Csaba 

> Hello,
>
> I'm writing a plugin which is generating certain files, and I would like to
> add something like a "Generated by xxx version 1.2.3" string to each file it
> generates. The problem is, how can the plugin know its own version (without
> hardcoding it)?
>
> Regards, Csaba
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Maven plugin version number

[Gajo Csaba]

Hello,

I'm writing a plugin which is generating certain files, and I would like 
to add something like a "Generated by xxx version 1.2.3" string to each 
file it generates. The problem is, how can the plugin know its own 
version (without hardcoding it)?


Regards, Csaba


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

apache openjpa trunk doesn't work with maven-3.0-alpha-4

[Prashant Bhat]

Hi,

I tested the latest maven-3.0-alpha-4 release with the apache openjpa trunk
code, and this fails with the following message. But the same works with
maven-2.2.1

>>$ mvn install

[INFO] Scanning for projects...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   The project org.apache.openjpa:openjpa-persistence:2.0.0-SNAPSHOT
(/home/user/snapshots/openjpa/openjpa-persistence/pom.xml) has 1 error
[ERROR] Failed to determine activation for profile jdk6-compiler: For
input string: "0_16"
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

The pom contains profile activation like this: 

   [1.6,)
 

My maven & jdk version details:

>>$ mvn -version

Apache Maven 3.0-alpha-4 (r835944; 2009-11-14 02:06:31+0800)
Java version: 1.6.0_16
Java home: /usr/lib/jvm/java-6-sun-1.6.0.16/jre
Default locale: en_SG, platform encoding: UTF-8
OS name: "linux" version: "2.6.31-14-generic" arch: "i386" Family: "unix"

Hope this helps in finding the solution for this issue.

Regards,
Prashant

-- 
View this message in context: 
http://old.nabble.com/apache-openjpa-trunk-doesn%27t-work-with-maven-3.0-alpha-4-tp26404401p26404401.html
Sent from the Maven - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

axis2 with rampart.mar and addressing.mar not being signed by webstart-maven-plugin

[Jaime Hablutzel Egoavil]

Hi, I'm receiving this message when building a jnlp project:

No resources found in
D:\desarrollo\ModuloEpicrisisMvn\src\main\jnlp\resources
Skipping artifact of type mar for jnlp
Skipping artifact of type mar for jnlp


Is the a way to recognize .rar extension packages instead of only .jar???

-- 
Jaime Hablutzel

(tildes omitidas intencionalmente) 9 8964 0369