Re: failsafe failures don't fail the build

[Brett Randall]

Check out the suggested bindings at
http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing

Brett


On 8/23/10, Benson Margulies  wrote:
> I have been unable to find a way to make a failure in an integration
> test result in failing the overall build. I have failsafe:verify in
> post-integration, and no joy.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

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

Re: maven 3 and the enforcer plugin

[Brett Randall]

I don't know this plugin/rule well, but looking at your output, could
it relate to the underscore versus hyphen in the detected versus
normalized JDK version string?  Maybe try a hyphen in your version
rule.

Brett


On 8/19/10, EJ Ciramella  wrote:
> Mvn version output:
>
> Apache Maven 3.0-beta-2 (r983206; 2010-08-07 07:00:51-0400)
> Java version: 1.5.0_18
> Java home: C:\Program Files (x86)\Java\jdk1.5.0_18\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows xp" version: "5.2" arch: "x86" Family: "windows"
> 'cmd' is not recognized as an internal or external command,
> operable program or batch file.
>
> Plugin Config:
>
> 
> org.apache.maven.plugins
> maven-enforcer-plugin
> 1.0-beta-1
> 
>   
> enforce-versions
> 
>   enforce
> 
> 
>   
> 
>   [1.5.0_18,)
>   [ERROR] The currently supported version of java is
> 1.5.0_18 or higher
> 
>   
> 
>   
> 
>   
>
> Stacktraces:
>
> [DEBUG]
> ===
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-versions) @
>  ---
> [DEBUG] Created new class realm
> plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1
> [DEBUG] Created new class realm maven.api
> [DEBUG] Populating class realm
> plugin>org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1
> [DEBUG]   Included:
> org.apache.maven.plugins:maven-enforcer-plugin:maven-plugin:1.0-beta-1
> [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:1.5.8
> [DEBUG]   Included:
> org.apache.maven.reporting:maven-reporting-api:jar:2.0.9
> [DEBUG]   Included: org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-10
> [DEBUG]   Included: commons-cli:commons-cli:jar:1.0
> [DEBUG]   Included:
> org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4
> [DEBUG]   Included: commons-lang:commons-lang:jar:2.3
> [DEBUG]   Included: org.apache.maven.enforcer:enforcer-api:jar:1.0-beta-1
> [DEBUG]   Included: org.apache.maven.enforcer:enforcer-rules:jar:1.0-beta-1
> [DEBUG]   Included: org.beanshell:bsh:jar:2.0b4
> [DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.9
> [DEBUG]   Excluded:
> org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
> [DEBUG]   Excluded: classworlds:classworlds:jar:1.1
> [DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-core:jar:2.0.9
> [DEBUG]   Excluded:
> org.apache.maven:maven-plugin-parameter-documenter:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-error-diagnostics:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-plugin-descriptor:jar:2.0.9
> [DEBUG]   Excluded: org.apache.maven:maven-monitor:jar:2.0.9
> [DEBUG] Configuring mojo
> org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce from
> plugin realm ClassRealm[plugin>org
> .apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1, parent:
> ClassRealm[maven.api, parent: null]]
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce' with
> basic configurator -->
> [DEBUG]   (s) fail = true
> [DEBUG]   (s) failFast = false
> [DEBUG]   (f) ignoreCache = false
> [DEBUG]   (s) project = MavenProject:  @ 
> [DEBUG]   (s) version = [1.5.0_18,)
> [DEBUG]   (f) message = [ERROR] The currently supported version of java is
> 1.5.0_18 or higher
> [DEBUG]   (s) rules =
> [org.apache.maven.plugins.enforcer.requirejavavers...@d72200]
> [DEBUG]   (s) session = org.apache.maven.execution.mavensess...@1a80aea
> [DEBUG]   (s) skip = false
> [DEBUG] -- end configuration --
> [DEBUG] Executing rule:
> org.apache.maven.plugins.enforcer.RequireJavaVersion
> [DEBUG] Rule org.apache.maven.plugins.enforcer.RequireJavaVersion is
> cacheable.
> [DEBUG] Detected Java String: 1.5.0_18
> [DEBUG] Normalized Java String: 1.5.0-18
> [DEBUG] Parsed Version: Major: 1 Minor: 5 Incremental: 0 Build: 18
> Qualifier: null
> [DEBUG] Adding failure due to exception
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: [ERROR] The
> currently supported version of java is 1.5.0_18 or higher
> at
> org.apache.maven.plugins.enforcer.AbstractVersionEnforcer.enforceVersion(AbstractVersionEnforcer.java:101)
> at
> org.apache.maven.plugins.enforcer.RequireJavaVersion.execute(RequireJavaVersion.java:65)
> at
> org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:185)
> 

Re: maven set wrong JRE version

[Brett Randall]

I've not used openjdk for a while, but worth checking your Eclipse
setting for Java -> JREs -> Execution Environments (typed from memory)
and make sure that your 1.6 openjdk JDK is registered/linked as an
execution environment JRE for 1.6.

Brett


On 8/18/10, Daniel Rindt  wrote:
> Hello,
>
> i am using m2eclipse and have installed latest openjdk 1.6. My project
> are created with m2eclipse, maven download the dependencies successfully
> but after that, eclipse complains with:
> = Build path specifies execution environment J2SE-1.4. There are no JREs
> installed in the workspace that are strictly compatible with this
> environment. =
> I can manually switch in the project settings the JRE, but m2eclipse
> overwrites it after a while.
>
> How to fix it?
>
> Thanks in advance
> --
> Daniel Rindt 
> Visetics
>

-- 
Sent from my mobile device

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

Re: maven compile can't resolve the class in rt.jar

[Brett Randall]

It might be worthwhile reading this:
http://blogs.sun.com/enterprisetechtips/entry/using_jax_ws_with_maven
, and particularly the comments around:

"Also, to run the sample with JDK 6 prior to the JDK 6 Update 4
release, you need use the endorsed override mechanism by copying the
jaxb-api.jar and jaxws-api.jar files to /lib/endorsed, where
 refers to the directory in which the runtime software is
installed -- this is the top-level directory of the Java SE Runtime
Environment or the
jre directory in the JDK. If you run the sample with JDK 6 Update 4 or
later, you do not need to use the override mechanism"

Brett


On 7/31/10, Alex Kuznetsov  wrote:
> We are having problem with maven.
> "maven compile" can't resolve the class in rt.jar
>
> Error: cannot find symbol symbol  : class Action location: package
> javax.xml.ws
>
>
> We are using :
> Maven version: 2.0.9
> Java version: 1.6.0_03
> OS name: "sunos" version: "5.10" arch: "sparc" Family: "unix"
>
> Thanks,
> Alex
>

-- 
Sent from my mobile device

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

Re: Why does maven build on dos prompt keeps waiting for user to press enter?

[Brett Randall]

What is Maven executing and what is in the output right before each
pause/prompt?

Brett

On 7/28/10, Kannan Jayaprakasam  wrote:
> For my pom.xml based maven build, at multiple places it waits and keeps
> waiting until I press Enter. This is a huge time waster because for a big
> project I have to constantly monitor the window and keep pressing Enter. How
> to make it just proceed without waiting? Pressing a number of Enters
> beforehand doesn't help.
>
>

-- 
Sent from my mobile device

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

Re: GWT on Maven Central

[Brett Randall]

The developer: 
http://maven.apache.org/guides/mini/guide-central-repository-upload.html

Send a request to the project developers/maintainers in the first instance.

Brett


On 7/14/10, Justin Edelson  wrote:
> Does anyone know who is responsible for getting the GWT jars up on Maven
> Central?
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

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

Re: maven runtime error java.net.UnknownHostException: repo1.maven.org.

[Brett Randall]

This posting describes some DNS resolver changes that one user found
they needed - something OS/distribution specific and not your OS, but
might be worth a check:
http://www.mail-archive.com/users@maven.apache.org/msg90647.html .

You're on Linux, so you might run tcpdump and see if Maven is calling
your expected DNS server.

Best
Brett

On Thu, Jul 1, 2010 at 3:50 PM, Andrew Bucknell  wrote:
> Thanks for the suggestion Brett but it appears that wasn’t the right fix. I
> updated to jdk 1.6.0_20. Im getting the same error in the same place.
>
> Caused by: java.net.UnknownHostException: repo1.maven.org
>
>
> -Original Message-
> From: Brett Randall [mailto:javabr...@gmail.com]
> Sent: Thursday, 1 July 2010 11:37 AM
> To: Maven Users List
> Subject: Re: maven runtime error java.net.UnknownHostException:
> repo1.maven.org.
>
> Someone else posted similar a few weeks back with the same JDK
> version, which is pretty old:
> http://maven.40175.n5.nabble.com/Maven-in-5-minutes-doesn-t-work-tt510820.ht
> ml#a510820
>
> "Thanks for the support guys, it was not a proxy issue. I upgraded my
> JDK/JRE
> from 1.6.0_03 to 1.6.0_20 and it all came back on the track, a bit strange
> though. "
>
> I'd try updating to a current patch release of JDK 1.6.0 on you platform.
>
> Best
> Brett
>
> On Thu, Jul 1, 2010 at 11:13 AM, Andrew Bucknell 
> wrote:
>> I downloaded maven 2.2.1 on to my debian box and am having problems with
> it.
>> I am not using a proxy or a firewall yet I am getting the following debug
>> messages - most notably
>>
>>
>>
>> Caused by: java.net.UnknownHostException: repo1.maven.org.
>>
>>
>>
>> I am able to resolve the hostname using nslookup from the command line.
> The
>> notes I have found so far suggest such problems are typically caused by
>> proxies
>>
>> Or firewalls, but as I have neither I am stumped. Any suggestions?
>>
>>
>>
>> Andrew
>>
>>
>>
>>
>>
>> and...@melb-web:~/mvntest$ mvn -X archetype:generate
>>
>> + Error stacktraces are turned on.
>>
>> Apache Maven 2.2.1 (r801777; 2009-08-07 05:16:01+1000)
>>
>> Java version: 1.6.0_03
>>
>> Java home: /usr/local/java/jdk1.6.0_03/jre
>>
>> Default locale: en_AU, platform encoding: UTF-8
>>
>> OS name: "linux" version: "2.6.22-3-amd64" arch: "i386" Family: "unix"
>>
>> [DEBUG] Building Maven user-level plugin registry from:
>> '/home/andrew/.m2/plugin-registry.xml'
>>
>> [DEBUG] Building Maven global-level plugin registry from:
>> '/usr/local/apache/maven/conf/plugin-registry.xml'
>>
>> [INFO] Scanning for projects...
>>
>> [INFO] Searching repository for plugin with prefix: 'archetype'.
>>
>> [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins
>>
>> [INFO] org.apache.maven.plugins: checking for updates from central
>>
>> [DEBUG] Using Wagon implementation lightweight from default mapping for
>> protocol http
>>
>> [DEBUG] Checking for pre-existing User-Agent configuration.
>>
>> [DEBUG] Adding User-Agent configuration.
>>
>> [DEBUG] Connecting to repository: 'central' with url:
>> 'http://repo1.maven.org/maven2'.
>>
>> [DEBUG] Using Wagon implementation lightweight from default mapping for
>> protocol http
>>
>> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be
>> retrieved from repository: central due to an error: Error transferring
> file:
>> repo1.maven.org
>>
>> [DEBUG] Exception
>>
>> org.apache.maven.wagon.TransferFailedException: Error transferring file:
>> repo1.maven.org
>>
>>        at
>>
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(Lig
>> htweightHttpWagon.java:143)
>>
>>        at
>> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
>>
>>        at
>> org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
>>
>>        at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
>>
>>        at
>>
> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultW
>> agonManager.java:546)
>>
>>        at
>>
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(De
>> faultWagonManager.java:443)
>>
>>        at
>>
> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManag

Re: maven runtime error java.net.UnknownHostException: repo1.maven.org.

[Brett Randall]

Someone else posted similar a few weeks back with the same JDK
version, which is pretty old:
http://maven.40175.n5.nabble.com/Maven-in-5-minutes-doesn-t-work-tt510820.html#a510820

"Thanks for the support guys, it was not a proxy issue. I upgraded my JDK/JRE
from 1.6.0_03 to 1.6.0_20 and it all came back on the track, a bit strange
though. "

I'd try updating to a current patch release of JDK 1.6.0 on you platform.

Best
Brett

On Thu, Jul 1, 2010 at 11:13 AM, Andrew Bucknell  wrote:
> I downloaded maven 2.2.1 on to my debian box and am having problems with it.
> I am not using a proxy or a firewall yet I am getting the following debug
> messages - most notably
>
>
>
> Caused by: java.net.UnknownHostException: repo1.maven.org.
>
>
>
> I am able to resolve the hostname using nslookup from the command line. The
> notes I have found so far suggest such problems are typically caused by
> proxies
>
> Or firewalls, but as I have neither I am stumped. Any suggestions?
>
>
>
> Andrew
>
>
>
>
>
> and...@melb-web:~/mvntest$ mvn -X archetype:generate
>
> + Error stacktraces are turned on.
>
> Apache Maven 2.2.1 (r801777; 2009-08-07 05:16:01+1000)
>
> Java version: 1.6.0_03
>
> Java home: /usr/local/java/jdk1.6.0_03/jre
>
> Default locale: en_AU, platform encoding: UTF-8
>
> OS name: "linux" version: "2.6.22-3-amd64" arch: "i386" Family: "unix"
>
> [DEBUG] Building Maven user-level plugin registry from:
> '/home/andrew/.m2/plugin-registry.xml'
>
> [DEBUG] Building Maven global-level plugin registry from:
> '/usr/local/apache/maven/conf/plugin-registry.xml'
>
> [INFO] Scanning for projects...
>
> [INFO] Searching repository for plugin with prefix: 'archetype'.
>
> [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins
>
> [INFO] org.apache.maven.plugins: checking for updates from central
>
> [DEBUG] Using Wagon implementation lightweight from default mapping for
> protocol http
>
> [DEBUG] Checking for pre-existing User-Agent configuration.
>
> [DEBUG] Adding User-Agent configuration.
>
> [DEBUG] Connecting to repository: 'central' with url:
> 'http://repo1.maven.org/maven2'.
>
> [DEBUG] Using Wagon implementation lightweight from default mapping for
> protocol http
>
> [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be
> retrieved from repository: central due to an error: Error transferring file:
> repo1.maven.org
>
> [DEBUG] Exception
>
> org.apache.maven.wagon.TransferFailedException: Error transferring file:
> repo1.maven.org
>
>        at
> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(Lig
> htweightHttpWagon.java:143)
>
>        at
> org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
>
>        at
> org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
>
>        at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
>
>        at
> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultW
> agonManager.java:546)
>
>        at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(De
> faultWagonManager.java:443)
>
>        at
> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManag
> er.resolve(DefaultRepositoryMetadataManager.java:97)
>
>        at
> org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(Defau
> ltPluginMappingManager.java:103)
>
>        at
> org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(Defau
> ltPluginMappingManager.java:87)
>
>        at
> org.apache.maven.plugin.DefaultPluginMappingManager.getByPrefix(DefaultPlugi
> nMappingManager.java:61)
>
>        at
> org.apache.maven.plugin.DefaultPluginManager.getPluginDefinitionForPrefix(De
> faultPluginManager.java:159)
>
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(Defaul
> tLifecycleExecutor.java:1801)
>
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggrega
> tionNeeds(DefaultLifecycleExecutor.java:462)
>
>        at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
> Executor.java:175)
>
>        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.java:39
> )
>
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .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.mainWithExi

Re: m2eclipse Mailing List

[Brett Randall]

Hi Shelli,

I too had the same problem a few weeks back.  I tried to raise this
via email to the list admin.

Regards
Brett

On Fri, Jun 11, 2010 at 6:34 AM, Shelli Orton  wrote:
> Hi,
> This post isn't Maven related, but I thought someone on this list may
> know... is the m2eclipse mailing list being managed?
>
> I tried to subscribe to the m2eclipse mailing list by sending an email
> to user-subscr...@m2eclipse.codehaus.org but it never sent me back any
> confirmation email. I sent an email to i...@sonatype.com asking if the
> mailing list was still running a couple of weeks ago and haven't
> received any response back to that either.
>
> Then I found another way to subscribe via
> http://xircles.codehaus.org/lists/info/search. So I did and am now
> receiving emails sent to the list. However, I can't send the list
> emails. They get bounced back with a failure notice:
>
> ---
>
> Hi. This is the qmail-send program at mail.codehaus.org.
> I'm afraid I wasn't able to deliver your message to the following
> addresses.
> This is a permanent error; I've given up. Sorry it didn't work out.
>
> :
> Sorry, only subscribers may post. If you are a subscriber, please
> forward this
> message to user-ow...@m2eclipse.codehaus.org to get your new address
> included. (#5.7.2)
>
> ---
>
> I've forwarded this message as instructed twice now without result so
> far (it's been a couple days now).
>
> It sucks to be only able to read messages and not to send them.
>
> Thanks in advance!
>
> -
> 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: Unable to execute package target on centos machine

[Brett Randall]

On Fri, May 14, 2010 at 4:43 PM, Vijay Shanker Dubey
 wrote:
> Hi
>
> I am working on a maven project to build a simple utility api.
>
> The same source code when build on my office win XP machine, was successful.
> Now i am at home and working with same source code on CentOS machine. Here
> the build process failed strangely.
>
> The error it reports is ideally in my points should we warning message. As
> shown below.
>
> [ERROR] com.vsd.Provider:[12,240] The import java.util.Set is never used
>
> Can you please give me some idea, where can I look into?
> Regards,
> Vijay Shanker Dubey
>

Check that you are running the latest version of
maven-compiler-plugin, or at least 2.2.  You might be seeing
http://jira.codehaus.org/browse/MCOMPILER-118 .

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

Re: Truncated pom.xml when artifact deployed to local repository

[Brett Randall]

Hi Ross,

I saw your http://issues.hudson-ci.org/browse/HUDSON-6370 , and
wondered if you had seen (closed, not reproducible)
http://jira.codehaus.org/browse/MNG-2551 , which seems similar.  Might
not help much since it was not resolved.

Brett

On Wed, May 12, 2010 at 7:39 PM, Ross Hedley (AS400)
 wrote:
> I'm using Maven 2.2.1 in conjunction with Hudson on Linux (OEL 5.3)  and
> it seems that if a project pom.xml is more than 4096 bytes, Hudson only
> writes up to 4096 bytes when it deploys it to the repository (truncating
> it in the process). This means that any projects dependent on this one
> won't build. Any poms less than 4096 bytes seem to deploy fine. This
> only occurs when the project is built via Hudson as building/deploying
> is fine using maven my local development machine using the same OS.
> This probably isn't a maven issue per se but just wondered if anyone
> else has had this problem?
> Incidentally I get the same problem on Ubuntu 9.10 so I don't think it's
> the OS.
> Perhaps someone could recommend an alternative Continuous Integration
> Server?
>
> Many Thanks.
>
>
>
>
> 
> Please visit our website www.greggs.co.uk
>
> Greggs plc is a public limited company, registered in England and Wales, 
> registered number 502851, registered office Fernwood House, Clayton Road, 
> Jesmond, Newcastle upon Tyne NE2 1TL.
> Confidentiality:  This email and its attachments are intended for the above 
> named only and may be confidential.  If they have come to you in error you 
> must take no action based on them, nor must you copy or show them to anyone; 
> please reply to this email and highlight the error.
> Security Warning: Please note that this email has been created in the 
> knowledge that Internet email is not a 100% secure communications medium.  We 
> advise that you understand and accept this lack of security when emailing us.
> Viruses: Although we have taken steps to ensure that this email and 
> attachments are free from any virus, we advise that in keeping with good 
> computing practice the recipient should ensure they are actually virus free. 
> Visit our website at: Http://www.greggs.co.uk
>
> This e-mail has been scanned for all viruses by Star. The
> service is powered by MessageLabs. For more information on a proactive
> anti-virus service working around the clock, around the globe, visit:
> http://www.star.net.uk
> 

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

Re: Test fail for release:perform only - no failure info

[Brett Randall]

Nice one. Adding an svn:ignore to a new project/module's target
directory is about the first thing I do for a new artifact.

Brett


On 3/16/10, Randall Fidler  wrote:
> Finally!  As suspected... it was some stupid trivial item.  I'm posting this
> just so the thread on the mail archive will be complete.
>
> Effectively what was causing the issue was some of surefire reports got
> checked into the scm under the target directory
> {project}/target/surefire-reports.  This is what caused surefire via release
> plugin to fail on the perform goal and not the prepare goal.  Reason being
> is that prepare runs a clean (and I usually run mvn clean release:prepare
> anyhow) as it's first step.  When the release goal was running, it would
> check out the entire project again to {project}/target/checkout/ in which
> those same surefire reports that were in the scm, would be placed into
> {project}/target/checkout/target/surefire-reports.  As a consequence, the
> surefire plugin would bomb on perform and not prepare (because prepare
> deleted them via it's own clean execution). Perform would does not run a
> clean so when it checked out the entire project again, the reports were in
> the target directory which throws surefire for a loop.
>
> I wish surefire would give you more information, such as it had a problem
> with a report file already existing, that would have saved SO much time, oh
> well.
>
> Lesson learned: Make sure you don't check anything into your projects target
> directory on your SCM, IT'S NOT A GOOD IDEA! ;)
>
>
> Regards,
>
> Randall
>
> -Original Message-
> From: Randall Fidler [mailto:randall.fid...@testadvantage.com]
> Sent: Monday, March 15, 2010 1:32 PM
> To: Maven Users List
> Subject: RE: Test fail for release:perform only - no failure info
>
> Wayne,
>
> One issue... how do you get the "maven.surefire.debug" option to the
> surefire plugin since it's running via the release plugin?  For instance, if
> I try to tell it just to skip tests, (i.e. -Dmaven.test.skip=true) it won't
> because the release plugin has it's own surefire config (I'm guessing).  So
> even if I want to debug it using Eclipse to attach to the test jvm, I don't
> see how can I get that parameter to the surefire instance that the release
> plugin is firing up.  I'll try anyhow, but think this will be a problem.
>
> Regards,
>
> Randall
>
> -Original Message-
> From: Wayne Fay [mailto:wayne...@gmail.com]
> Sent: Monday, March 15, 2010 1:14 PM
> To: Maven Users List
> Subject: Re: Test fail for release:perform only - no failure info
>
>>    I read somewhere that you can hook a debugger to the surefire plugin,
>> is that what you're talking about?  I believe that plugin has a parameter
>> that tells it to wait until the "debugger" has connected and then it
>> proceeds
>> to run the tests.
>
> Googling "maven surefire debugger" brought the proper results to the
> top... give it a try. ;-)
>
> 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
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

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

Re: mvn archetype:create breaks on js file

[Brett Randall]

archetype:create is deprecated in favour of archetype:generate, so try
archetype:generate. See its interactiveMode setting for a
non-interactive option.

Brett


On 3/15/10, Antoine van Wel  wrote:
> Hi,
>
> I'm building an archetype using "mvn archetype:create-from-project".
> In my project there are several javascript files. Installing the
> generated archetype works fine. The moment I try to create a project
> from this archetype on the command-line using "mvn archetype:create",
> I get an error, which seems to indicate Velocity cannot handle the
> javascript files in the project.
>
> Which is actually a problem of Velocity, but the files should not be
> touched by Velocity in the first place. I tried to disable filtering
> them:
>
>
>   src/main/webapp
>   
> **/*.png
> **/*.js
> **/*.css
>   
> 
>
> and tried several alternatives, but none of them seems to be working:
> it does not stop Velocity from touching the files, and then choking on
> them. Any ideas if I'm doing something wrong? Version used: maven
> 2.0.9 and maven-archetype-plugin 2.0-alpha-4.
>
> However, the interactive "mvn archetype:generate" seems to work
> perfectly, which makes me believe this is a bug.
>
>
> Thanks,
>
> Antoine.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

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

Re: Problem with JAVA_HOME relative path

[Brett Randall]

Are you running Eclipse IDE?  Looks similar to
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-UnabletolocatetheJavacCompilerError


Brett

On Mon, Feb 1, 2010 at 12:00 PM, Andrew Hughes  wrote:

> Hi All,
>
> I get the following error and I'm pretty sure that the problem is hidden
> somewhere. Things of interest are in *bold* below
>
> [INFO] Compiling 16 source files to
> D:\Workspace\gwt1.6-maven2-starter-app-1.0\server\target\classes
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
> Unable to locate the Javac Compiler in:
>  C:\Program Files\Java\jdk1.6.0_14\*..\lib*\tools.jar
> Please ensure you are using JDK 1.4 or above and not a JRE (the
> com.sun.tools.javac.Main class is required). In most cases you can change
> the location of your Java installation by setting the JAVA_HOME environment
> variable.
>
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Mon Feb 01 10:09:48 CST 2010
> [INFO] Final Memory: 12M/25M
> [INFO]
> 
>
> D:\Workspace\gwt1.6-maven2-starter-app-1.0\parent>*echo %JAVA_HOME%*
> *C:\Program Files\Java\jdk1.6.0_14*
> *
> *
>
> My JAVA_HOME appears to be set correctly, pointing to jdk1.6.0_14. However,
> the compiler plugin is looking for ..\lib\tools.jar. Which does not exist,
> because the ".." (up one directory) path is actually pointing to
> 'C:\Program
> Files\Java\lib\tools.jar' which is obviously wrong.
>
> Any idea's where the relative path could be getting trashed?
>
> Cheers :)
>
> p.s. to get the source for the code I am trying to build:
> svn checkout *http*://
> gwt-maven2-starter-app.googlecode.com/svn/trunk/gwt-maven2-starter-app-read-only
>

Re: compile:compile failure on sun proprietary implementation API usage

[Brett Randall]

Try this page, 
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
look for rt.jar under System Dependencies.

Brett


On 1/18/10, Dan Tran  wrote:
> I am using Sun JDK on windows  version 1.6.0_17
>
> -Dan
>
> On Sun, Jan 17, 2010 at 3:52 PM, Erlend Hamnaberg  wrote:
>> Are you using Openjdk? then this fails.
>>
>> Use the JDK shipped by sun, and you should be ok.
>>
>> -- Erlend
>>
>> On Mon, Jan 18, 2010 at 12:28 AM, Dan Tran  wrote:
>>
>>> Hello,
>>>
>>> I just inherit an project that I am trying to convert to maven and hit
>>> a compilation error  ( using java 1.6, target/source = 1.6 )
>>>
>>> ts\admin\db_devices\DBCollectorHousekeepingServlet.java:[28,15]
>>> sun.misc.BASE64Decoder is Sun proprietary API and may be removed in a
>>> future release
>>>
>>> Eclispe IDE does not fail this call.  Why Maven?
>>>
>>> I found a link to this failure, with no resolution
>>> http://www.mail-archive.com/users@maven.apache.org/msg103349.html
>>>
>>> Is there a way to make it a warning?
>>>
>>> Thanks
>>>
>>>
>>> -Dan
>>>
>>> -
>>> 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
>
>

-- 
Sent from my mobile device

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

Re: assembly is deprecated. What to use?

[Brett Randall]

Yes, this one: http://jira.codehaus.org/browse/MPH-59 "Describe goal says
everything is deprecated".  Says fixed in 2.1.1.

On Wed, Dec 9, 2009 at 7:42 AM, Justin Edelson wrote:

> That looks like a bug in the help plugin.
>
> On Tue, Dec 8, 2009 at 3:27 PM, Andrew Gaydenko  wrote:
>
> > On Tuesday 08 December 2009 23:09:27 Justin Edelson wrote:
> > > Not all, just some:
> > > http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html
> > >
> > > That page tells you which goals to use to replace the deprecated goals.
> > >
> > > Justin
> >
> > Justin,
> >
> > So the (trimmed) output shown below is a lie :-) I'm definitely
> frustrated
> > -
> > have thought "mvn help:describe" outputs most precision information...
> > Where
> > does the most "official" plugins information takes place?
> >
> >
> > Andrew
> >
> >
> > //-
> > $ mvn help:describe
> -Dplugin=org.apache.maven.plugins:maven-assembly-plugin
> > ...
> > [INFO] org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4
> > ...
> > assembly:assembly
> >  Deprecated. No reason given
> >
> > assembly:attached
> >  Deprecated. Use goal: 'assembly' (from the command line) or 'single'
> (from
> > a
> >  lifecycle binding) instead.
> >
> > assembly:directory
> >  Deprecated. No reason given
> >
> > assembly:directory-inline
> >  Deprecated. Use goal: 'directory' (from the command line) or
> >  'directory-single' (from a lifecycle binding) instead.
> >
> > assembly:directory-single
> >  Deprecated. No reason given
> >
> > assembly:help
> >  Deprecated. No reason given
> >
> > assembly:single
> >  Deprecated. No reason given
> >
> > assembly:unpack
> >  Deprecated. Use org.apache.maven.plugins:maven-dependency-plugin goal:
> > unpack
> >  or unpack-dependencies instead.
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

Re: [m2] maven does not launch on ubuntu 9.10

[Brett Randall]

Hi Adrian,

I'm sure you've seen the unresolved bug 542162 on the Debian lists.  Can you
confirm - have you tried downloading the Maven binary bundle from
maven.apache.org, or are you still trying to run the
Ubuntu/Canonical/Debian-upstream bundle?  What does `which mvn` produce? I
recommend you try a non-bundled binary install.

Brett



On Mon, Nov 30, 2009 at 7:04 PM, Adrian Herscu  wrote:

> Thanks for your fast reply, Brett.
>
> Currently I have:
>
> p...@ubuntu-desktop:~$ java -version
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
> p...@ubuntu-desktop:~$ javac -version
> javac 1.6.0_16
> p...@ubuntu-desktop:~$ mvn --version
>
> org.codehaus.classworlds.NoSuchRealmException
>at org.codehaus.classworlds.ClassWorld.getRealm(ClassWorld.java:128)
>at org.codehaus.classworlds.Launcher.getMainRealm(Launcher.java:181)
>at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:290)
>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)
> p...@ubuntu-desktop:~$
>
> Adrian.
>
>
> Brett Randall wrote:
>
>> A few folks have run into problems with the Ubuntu 9.10 upgrade. I'm
>> running
>> that kit with Maven 2.2.0 without problems.
>>
>> From memory some of the problems stemmed from:
>>
>> * Running the Maven bundle from Canonical - best bet is probably to run
>> the
>> plain distro if you hit problems
>> * The initial default behaviour of 9.10 to remove Sun JDK5, which may
>> leave
>> you without a modern JDK without knowing it. Make sure you install a
>> suitable JDK and set PATH and JAVA_HOME.
>>
>> Please post the output of "mvn --version" if still in doubt.
>>
>> Best
>> Brett
>>
>> On Mon, Nov 30, 2009 at 6:32 AM, Adrian Herscu 
>> wrote:
>>
>>  Hi all,
>>>
>>> After upgrading from Ubuntu 9.04 to 9.10 Maven suddenly failed to launch
>>> with the following exception:
>>>
>>> p...@ubuntu-desktop:~/wirexn$ mvn --version
>>> java.io.FileNotFoundException: /usr/share/maven2/bin/m2.conf (No such
>>> file
>>> or directory)
>>>   at java.io.FileInputStream.open(Native Method)
>>>   at java.io.FileInputStream.(FileInputStream.java:106)
>>>   at java.io.FileInputStream.(FileInputStream.java:66)
>>>   at
>>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:407)
>>>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>>>
>>> Looks like the m2.conf file is a symlink to ../conf/m2.conf, but there is
>>> no such file! Created an empty m2.conf file with one line:
>>> # m2.conf
>>> saved, and now I am getting:
>>>
>>> p...@ubuntu-desktop:~/wirexn$ mvn --version
>>> org.codehaus.classworlds.NoSuchRealmException
>>>   at
>>> org.codehaus.classworlds.ClassWorld.getRealm(ClassWorld.java:128)
>>>   at
>>> org.codehaus.classworlds.Launcher.getMainRealm(Launcher.java:181)
>>>   at
>>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:290)
>>>   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)
>>>
>>> Also, tried to reinstall the Maven package through Synaptic.
>>>
>>> What should I check?
>>>
>>> TIA,
>>> Adrian.
>>>
>>>
>>> -
>>> 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: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

[Brett Randall]

Hi Ellecer,

Just scanning through this thread I'm not sure if anyone has asked you to
run "mvn help:effective-pom" in the problem environment. Does that show the
correct variable substitution?

Brett

On Tue, Nov 24, 2009 at 5:39 PM, Ellecer Valencia  wrote:

> Hi Other Brett,
>
> It's a similar problem, except that the environment settings are
> coming from the shell environment and not a setttings.xml
>
>
> Ellecer
>
>
>
> On Mon, Nov 23, 2009 at 6:16 PM, Brett Randall 
> wrote:
> > Hi Ellecer,
> >
> > Is there a chance you are seeing
> http://jira.codehaus.org/browse/MNG-4148 ,
> > which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does
> that
> > fit your parent POM hierarchy?
> >
> > Other Brett
> >
> > On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia 
> wrote:
> >
> >> On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter 
> wrote:
> >> > Did you also "export WL_HOME"?
> >> >
> >> > I tried something similar here and it works fine in 2.2.1.
> >> >
> >> > - Brett
> >>
> >> Hi Brett,
> >>
> >> I'd presume the environment variable being there means that's already
> >> happened. =)
> >>
> >> This entry is in .bashrc so I'm pretty sure the environment var is
> >> always created.
> >>
> >> export WL_HOME=/usr/java/weblogic
> >>
> >> I've just created a new session window and see these errors when I run
> >> with "mvn -o -X -e package"
> >>
> >> Validation Errors:
> >> [DEBUG] For dependency Dependency {groupId=weblogic,
> >> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> >> must specify an absolute path systemPath.
> >> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> >> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> >> must specify an absolute path systemPath.
> >>
> >>
> >> Ellecer
> >>
> >> >
> >> > On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
> >> >
> >> >> But that's exactly the problem - it *is* defined in the environment.
> :(
> >> >>
> >> >> $ls -l $WL_HOME/server/lib/webservices.jar
> >> >> -rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
> >> >> /usr/java/weblogic/server/lib/webservices.jar
> >> >>
> >> >>
> >> >> $echo $WL_HOME
> >> >> /usr/java/weblogic
> >> >>
> >> >>
> >> >> The Maven project  I am trying to build has a pom.xml with a parent
> pom
> >> >>
> >> >>
> >> >>super_pom
> >> >>mypackage
> >> >>1.0.2-SNAPSHOT
> >> >>
> >> >>
> >> >> and it's in super_pom where the weblogic dependency is declared.
> >> >>
> >> >>
> >> >>
> >> >> On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox 
> wrote:
> >> >>> Well Maven sees it just like the message:
> >> >>> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> >> >>> artifactId=weblogic, version=10.0, type=jar}: system-scoped
> dependency
> >> >>> must specify an absolute path systemPath.
> >> >>>
> >> >>>
> >> >>> So since the first one works and the second one doesn't, that leads
> me
> >> >>> to believe that WL_HOME isn't defined in your environment.
> >> >>>
> >> >>> On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia <
> elle...@gmail.com>
> >> wrote:
> >> >>>> Hi Brian,
> >> >>>>
> >> >>>> Could you please clarify what's actually "plain wrong" about it?
> >> >>>>
> >> >>>> Going back to the example I posted:
> >> >>>>
> >> >>>>   
> >> >>>>  com.sun
> >> >>>>  rt
> >> >>>>  1.5.0.11
> >> >>>>  system
> >> >>>>  ${java.home}/lib/rt.jar
> >> >>>>
> >> >>>>
> >> >>>>  weblogic
> >> >>>>  weblogic
> >> >>>>  10.0
> >

Re: [m2] maven does not launch on ubuntu 9.10

[Brett Randall]

A few folks have run into problems with the Ubuntu 9.10 upgrade. I'm running
that kit with Maven 2.2.0 without problems.

>From memory some of the problems stemmed from:

* Running the Maven bundle from Canonical - best bet is probably to run the
plain distro if you hit problems
* The initial default behaviour of 9.10 to remove Sun JDK5, which may leave
you without a modern JDK without knowing it. Make sure you install a
suitable JDK and set PATH and JAVA_HOME.

Please post the output of "mvn --version" if still in doubt.

Best
Brett

On Mon, Nov 30, 2009 at 6:32 AM, Adrian Herscu  wrote:

> Hi all,
>
> After upgrading from Ubuntu 9.04 to 9.10 Maven suddenly failed to launch
> with the following exception:
>
> p...@ubuntu-desktop:~/wirexn$ mvn --version
> java.io.FileNotFoundException: /usr/share/maven2/bin/m2.conf (No such file
> or directory)
>at java.io.FileInputStream.open(Native Method)
>at java.io.FileInputStream.(FileInputStream.java:106)
>at java.io.FileInputStream.(FileInputStream.java:66)
>at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:407)
>at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> Looks like the m2.conf file is a symlink to ../conf/m2.conf, but there is
> no such file! Created an empty m2.conf file with one line:
> # m2.conf
> saved, and now I am getting:
>
> p...@ubuntu-desktop:~/wirexn$ mvn --version
> org.codehaus.classworlds.NoSuchRealmException
>at org.codehaus.classworlds.ClassWorld.getRealm(ClassWorld.java:128)
>at org.codehaus.classworlds.Launcher.getMainRealm(Launcher.java:181)
>at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:290)
>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)
>
> Also, tried to reinstall the Maven package through Synaptic.
>
> What should I check?
>
> TIA,
> Adrian.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

[Brett Randall]

Hi Ellecer,

Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148 ,
which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does that
fit your parent POM hierarchy?

Other Brett

On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia  wrote:

> On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter  wrote:
> > Did you also "export WL_HOME"?
> >
> > I tried something similar here and it works fine in 2.2.1.
> >
> > - Brett
>
> Hi Brett,
>
> I'd presume the environment variable being there means that's already
> happened. =)
>
> This entry is in .bashrc so I'm pretty sure the environment var is
> always created.
>
> export WL_HOME=/usr/java/weblogic
>
> I've just created a new session window and see these errors when I run
> with "mvn -o -X -e package"
>
> Validation Errors:
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
>
>
> Ellecer
>
> >
> > On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
> >
> >> But that's exactly the problem - it *is* defined in the environment. :(
> >>
> >> $ls -l $WL_HOME/server/lib/webservices.jar
> >> -rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
> >> /usr/java/weblogic/server/lib/webservices.jar
> >>
> >>
> >> $echo $WL_HOME
> >> /usr/java/weblogic
> >>
> >>
> >> The Maven project  I am trying to build has a pom.xml with a parent pom
> >>
> >>
> >>super_pom
> >>mypackage
> >>1.0.2-SNAPSHOT
> >>
> >>
> >> and it's in super_pom where the weblogic dependency is declared.
> >>
> >>
> >>
> >> On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox  wrote:
> >>> Well Maven sees it just like the message:
> >>> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> >>> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> >>> must specify an absolute path systemPath.
> >>>
> >>>
> >>> So since the first one works and the second one doesn't, that leads me
> >>> to believe that WL_HOME isn't defined in your environment.
> >>>
> >>> On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia 
> wrote:
> >>>> Hi Brian,
> >>>>
> >>>> Could you please clarify what's actually "plain wrong" about it?
> >>>>
> >>>> Going back to the example I posted:
> >>>>
> >>>>   
> >>>>  com.sun
> >>>>  rt
> >>>>  1.5.0.11
> >>>>  system
> >>>>  ${java.home}/lib/rt.jar
> >>>>
> >>>>
> >>>>  weblogic
> >>>>  weblogic
> >>>>  10.0
> >>>>  system
> >>>>  ${env.WL_HOME}/server/lib/weblogic.jar
> >>>>
> >>>>
> >>>> Do you mean the first one, referencing "${java.home}" is correct and
> >>>> the one referencing "${env.WL_HOME}" is wrong? So what should we do to
> >>>> make it work?
> >>>>
> >>>>
> >>>> thanks,
> >>>>
> >>>> Ellecer
> >>>>
> >>>>
> >>>> On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox 
> wrote:
> >>>>>>
> >>>>>>
> >>>>>> Maybe 2.2.2 will fix it. =)
> >>>>>
> >>>>> Not likely. The pom is plain wrong an it was a bug in 2.x which
> allowed it
> >>>>> to go unnoticed.
> >>>>>
> >>>>>> On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall  >
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> http://jira.codehaus.org/browse/MNG-4379 ... or did your team log
> that
> >>>>>>> :).
> >>>>>>>
> >>>>>>> On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia <
> elle...@gmail.com>
> >>>>>>> wrote:
> >>>>>>>
> >>>

Re: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

[Brett Randall]

http://jira.codehaus.org/browse/MNG-4379 ... or did your team log that :).

On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia  wrote:

> Hi Brett,
>
> Thanks for the suggestion. I may have found the issue. Would it be this:
>
>
> Validation Errors:
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG]
>
> [DEBUG]   mypackage:myartifact:jar:1.0.2:compile (selected for compile)
> [DEBUG] Skipping disabled repository central
> [DEBUG] myartifact: using locally installed snapshot
> [WARNING] POM for 'mypackage:myartifact:pom:1.0.2-SNAPSHOT:test' is
> invalid.
>
> Its dependencies (if any) will NOT be available to the current build.
> [DEBUG] Reason: Failed to validate POM for project
> mypackage:myartifact at Artifact
> [mypackage:myartifact:pom:1.0.2-SNAPSHOT:test]
> [DEBUG]
> Validation Errors:
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For dependency Dependency {groupId=weblogic,
> artifactId=webservices, version=10.0, type=jar}: system-scoped
> dependency must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
> must specify an absolute path systemPath.
> [DEBUG] For managed dependency Dependency {groupId=weblogic,
> artifactId=webservices, version=10.0, type=jar}: system-scoped
> dependency must specify an absolute path systemPath.
> [DEBUG]
>
>
> Now in this project, we are inheriting from a parent POM (standardised
> for our department) with entries like this:
> (WL_HOME is Weblogic install directory)
>
>
>  
>com.sun
>tools
>1.5.0.11
>system
>${java.home}/../lib/tools.jar
>  
>  
>com.sun
>rt
>1.5.0.11
>system
>${java.home}/lib/rt.jar
>  
>  
>weblogic
>weblogic
>10.0
>system
>${env.WL_HOME}/server/lib/weblogic.jar
>  
>  
>weblogic
>webservices
>10.0
>system
>${env.WL_HOME}/server/lib/webservices.jar
>  
>
>
> Now it only fails on the Weblogic related entries. With the Java
> system dependencies it seems to do fine.
>
> Has the handling of this changed from 2.0.* to 2.2.*?
>
> If so, what should we replace it with?
>
> And will these settings also work for  people still using maven 2.0.10?
>
>
> Ellecer
>
>
>
> On Fri, Nov 20, 2009 at 1:01 PM, Brett Randall 
> wrote:
> > Hi Ellecer
> >
> > What is the output of mvn -e -X ...
> >
> > Brett
> >
> > On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia  >wrote:
> >
> >> Hi,
> >>
> >> How come when I try a build using Maven 2.2.1 I get multiple messages
> like
> >> this:
> >>
> >> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
> >> invalid.
> >>
> >> Its dependencies (if any) will NOT be available to the current build."
> >>
> >> These errors weren't displaying when I was using Maven 2.0.10
> >>
> >> I'm trying to use the newer version of Maven but I can't proceed with
> >> these error messages.
> >>
> >> How can I find out what are the actual errors it's referring to? I
> >> didn't come across any mention of relevant POM format changes going
> >> from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
> >> would be a great help!  Is there a way to validate the pom and get
> >> format error details  from Maven?
> >>
> >>
> >> thanks,
> >>
> >> Ellecer
> >>
> >> -
> >> 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: "[WARNING] POM is invalid." error messages in Maven 2.2.1 but not in 2.0.10

[Brett Randall]

Hi Ellecer

What is the output of mvn -e -X ...

Brett

On Fri, Nov 20, 2009 at 11:41 AM, Ellecer Valencia wrote:

> Hi,
>
> How come when I try a build using Maven 2.2.1 I get multiple messages like
> this:
>
> "[WARNING] POM for 'mypackage.artifact:pom:1.0.2-SNAPSHOT:compile' is
> invalid.
>
> Its dependencies (if any) will NOT be available to the current build."
>
> These errors weren't displaying when I was using Maven 2.0.10
>
> I'm trying to use the newer version of Maven but I can't proceed with
> these error messages.
>
> How can I find out what are the actual errors it's referring to? I
> didn't come across any mention of relevant POM format changes going
> from Maven 2.0.* to 2.1.* or 2.2.* - if anyone has any info on this it
> would be a great help!  Is there a way to validate the pom and get
> format error details  from Maven?
>
>
> thanks,
>
> Ellecer
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: tracking down jetty/tomcat dependencies

[Brett Randall]

On Fri, Oct 30, 2009 at 6:45 AM, Benson Margulies wrote:

> I've got code that works fine when run as a pojo and fails when run in a
> webapp, either via tomcat:run or jetty:run. I suspect, because I can't
> think
> of anything else, that there is detritus in the 'system' classpaths of
> these
> containers. However, mvn dependency:tree does not tell me much about the
> maven-jetty-plugin. Neither does dependency:resolve-plugins.
>
> Is there some way to get a clearer view of this question?
>

What is the mode of failure?

Brett

Re: Maven and Eclipse (WTP)

[Brett Randall]

All else fails you could access via Nabble:
http://www.nabble.com/Maven-Eclipse---User-f14525.html .

Cheers
Brett

On Mon, Oct 19, 2009 at 2:52 PM, Damon Silver  wrote:

> Off-topic:  On that note, I've tried half a dozen times to subscribe to the
> M2Eclipse Users list via the link on that page to no avail.  Is there some
> other avenue to use instead, or someone who has to be notified that the
> subscription link is broken?
>
> Thanks,
>
> Damon
>
> -Original Message-
> From: Jason van Zyl [mailto:ja...@sonatype.com]
> Sent: Saturday, October 17, 2009 11:58 AM
> To: Maven Users List
> Subject: Re: Maven and Eclipse (WTP)
>
> Use the M2Eclipse user list for M2Eclipse questions.
>
> http://m2eclipse.sonatype.org/project-information.html
>
> On 2009-10-17, at 12:23 PM, Formenti, Giovanni wrote:
>
> > Hi,
> > I have to manage a JEE project with Eclipse and Maven. We'd like to
> > use M2Eclise and WTP (but we can also use JBoss Tools) to deploy an
> > EAR (3 module: JAR, WAR and EAR) in JBoss running inside the IDE,
> > i.e. our development environment.
> > Has someone tips on how to manage this configuration? Do you have
> > guideline about how to configure maven and eclipse to allow these
> > tools integration?
> > Thank you in advance for any suggestions...
> >
> > Best Regards
> > Giovanni
> > This message contains information that may be privileged or
> > confidential and is the property of the Capgemini Group. It is
> > intended only for the person to whom it is addressed. If you are not
> > the intended recipient, you are not authorized to read, print,
> > retain, copy, disseminate, distribute, or use this message or any
> > part thereof. If you receive this message in error, please notify
> > the sender immediately and delete all copies of this message.
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> --
>
>
> -
> 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: How to display/transfer maven compilation errors/logs in Web page

[Brett Randall]

Use Hudson + Maven. Hudson will capture the console output and errors for you.


On 10/14/09, harishsyndrome  wrote:
>
> Thanks for your reply.
>
> But My requirment is quite different.
> For Example:
>
>
>
>> public class mavenEmbedded
>> {
>>  public static void main(String args[])
>>  {
>>  try
>>  {
>>  File projectDirectory = new File( getBasedir(),
>> "src/examples/simple-project" );
>>
>> File user = new File( projectDirectory, "settings.xml" );
>>
>> Configuration configuration = new DefaultConfiguration()
>> .setUserSettingsFile( user )
>> .setClassLoader(
>> Thread.currentThread().getContextClassLoader() );
>>
>> ConfigurationValidationResult validationResult =
>> MavenEmbedder.validateConfiguration( configuration );
>>
>> if ( validationResult.isValid() )
>> {
>> MavenEmbedder embedder = new MavenEmbedder( configuration );
>>
>> MavenExecutionRequest request = new
>> DefaultMavenExecutionRequest()).setBaseDirectory( projectDirectory
>> ).setGoals( Arrays.asList( new String[]{"clean", "install"} ) );
>>
>> MavenExecutionResult result = embedder.execute(request);
>>
>> if ( result.hasExceptions() )
>> {
>> fail( ((Exception)result.getExceptions().get( 0
>> )).getMessage() );
>> }
>>
>> //
>> 
>> // You may want to inspect the project after the execution.
>> //
>> 
>>
>> MavenProject project = result.getProject();
>>
>> // Do something with the project
>>
>> String groupId = project.getGroupId();
>>
>> String artifactId = project.getArtifactId();
>>
>> String version = project.getVersion();
>>
>> String name = project.getName();
>>
>> String environment = project.getProperties().getProperty(
>> "environment" );
>>
>> //assertEquals( "development", environment );
>>
>> System.out.println( "You are working in the '" + environment +
>> "' environment!" );
>> }
>> else
>> {
>> if ( ! validationResult.isUserSettingsFilePresent() )
>> {
>> System.out.println( "The specific user settings file '" +
>> user + "' is not present." );
>> }
>> else if ( ! validationResult.isUserSettingsFileParses() )
>> {
>> System.out.println( "Please check your settings file, it
>> is not well formed XML." );
>> }
>> }
>>  }
>>  
>>  catch(Exception e)
>>  {
>>  e.printStackTrace();
>>  }
>>
>>
>>  }
>>
>> }
>>
>
> This part of Code inputs a Project Folder and Does Clean and Install tasks
> of Maven. This is my service method which does of Compiliing the Code.
>
>
> If there exists an error in the project. The Error/Warning/Logs will  be
> thrown to the Console.I want that error messages to be shown in the Web
> Page.
>
> One way, i can have a Logger and reflect the logger in the web page. I dont
> want to do that. IAm looking for any Api/Jar (Not War or Ear) which can do
> the work.
>
> Thanks again for your reply. And i need some more help from
> here...Desperately.
> --
> View this message in context:
> http://www.nabble.com/How-to-display-transfer-maven-compilation-errors-logs-in-Web-page-tp25867220p25888247.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
>
>

-- 
Sent from my mobile device

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

Re: Differences between app servers

[Brett Randall]

Hi Jim

If you are not already using them, you might like to take a look at
Maven Profiles. By activating a profile, you can influence the
artifacts and resources which make up a particular build e.g.
targeting a specific appserver.

If you write a lot of web apps for deployment to different appservers,
you might end up writing your own archetype with profiles in place for
this - I'm not aware of any existing.

Brett


On 10/8/09, Jim Collings  wrote:
> Not so much.  Take Weblogic for example. You really can't deploy a
> Struts2 based WAR file to it because of library conflicts. It would be
> cool if I could specify somehow, somewhere that this is a Weblogic
> project.  Then it would always build as an ear and would include a
> weblogic-application.xml with the excludes/prefers set so that the
> conflicts don't happen. Also Weblogic insists on APP-INF rather than
> WEB-INF. Perhaps that is related to the fact that it is now an *.ear
> file though, I don't know.
>
> On Wed, Oct 7, 2009 at 3:59 AM, Brett Randall  wrote:
>> On Wed, Oct 7, 2009 at 11:21 AM, Jim C.  wrote:
>>
>>> Are there archetypes or something else out there that will differentiate
>>> between application servers?  We try to write cross platform Java and it
>>> seems like our app server vendors are fighting us tooth and nail. I
>>> suppose that is the reason for GlassFish but our shop isn't allowed to
>>> use it.
>>>
>>>
>>> Jim C.
>>>
>>>
>> What types of issue/differences are you facing? Are they compile/deploy or
>> runtime issues?
>>
>> Brett
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

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

Re: Differences between app servers

[Brett Randall]

On Wed, Oct 7, 2009 at 11:21 AM, Jim C.  wrote:

> Are there archetypes or something else out there that will differentiate
> between application servers?  We try to write cross platform Java and it
> seems like our app server vendors are fighting us tooth and nail. I
> suppose that is the reason for GlassFish but our shop isn't allowed to
> use it.
>
>
> Jim C.
>
>
What types of issue/differences are you facing? Are they compile/deploy or
runtime issues?

Brett

Re: [ANN] Apache Source-Release Assembly Descriptor 1.0 Released

[Brett Randall]

On Sat, Aug 22, 2009 at 9:00 AM, John Casey  wrote:

> It appears that the site/repository synchronization is moving slowly, so
> please be patient and these artifacts and site updates should be showing up
> before long. I want to make sure I get this announcement out before I forget
> it, though.
>
> ---
>
> The Maven team is pleased to announce the release of Apache
> Source-Release Assembly Descriptor, version 1.0.
>
> This is a standardized assembly descriptor for use in the
> maven-assembly-plugin. Source-release artifacts are archives which
> contain the full project structure (sources only, no build output) that
> are the subject of an ASF release vote.
>
>
> http://maven.apache.org/apache-resource-bundles/apache-source-release-assembly-descriptor/
>
> This assembly descriptor should be coming to a parent POM near you, and
> should eventually be an automatic part of every ASF release. For now, it
> has been configured into the release process for Maven projects that
> inherit from maven-parent version 13 (also recently released). If you
> want to try out the source-release descriptor in the meantime, you can
> include a configuration like the following:
>
> 
>  
>
>  maven-assembly-plugin
>  2.2-beta-4
>
>  
>
>  org.apache.apache.resources
>
> apache-source-release-assembly-descriptor
>  1.0
>
>  
>
>  
>
>  source-release
>  package
>  
>single
>  
>  
>
>  source-release
>
>gnu
>true
>  
>
>  
>
>  
> 
>
> Enjoy,
>
> The Maven Team
>
> --
> John Casey
> Developer, PMC Member - Apache Maven (http://maven.apache.org)
> Blog: http://www.ejlife.net/blogs/buildchimp/
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Thanks John, this is great - I've been looking for something just like this.
Any idea when the doc-link in the announcement will sync-up? It's still
showing 404 for me.

Best
Brett

Re: How to add SYSTEM scope dependency to manifest?

[Brett Randall]

If you can't or won't follow the advice to install the artifact into a
repository manager, then simply use install-file to install it to your
local repo, the change the scope to compile.

Best
Brett


On 8/13/09, REMIJAN, MICHAEL J [AG/1000]  wrote:
> There are many reasons why a project would use a JAR file which isn't in a
> repository. So I'm assuming Maven cannot be configured to handle this?   It
> seems to me if I can configure the  to include
> system dependencies then I should also be able to make a
> similar configuration with the .  Or is there
> another way of accomplishing the same thing?
>
> -Original Message-
> From: Brian Fox [mailto:bri...@infinity.nu]
> Sent: Wednesday, August 12, 2009 1:58 PM
> To: Maven Users List
> Subject: Re: How to add SYSTEM scope dependency to manifest?
>
> System scope is meant for system objects that would be present on the
> target os, something like MFC.dll etc. Using it to work around having
> the jar in a repository is a definite anti-pattern.  Instead have it
> uploaded to your Corporate Nexus repository.
>
> On Wed, Aug 12, 2009 at 1:10 PM, REMIJAN, MICHAEL J
> [AG/1000] wrote:
>> The jar is not in any repository so I read it off of the file system by
>> setting the dependency to system This is the only scope
>> which can read jars off the file system.  If the scope is changed to
>> compile, Maven will want to pull it from a repository.  The m2 plugin for
>> eclipse gives an error if  is set and the scope is not system.
>>
>> -Original Message-
>> From: Wayne Fay [mailto:wayne...@gmail.com]
>> Sent: Wednesday, August 12, 2009 9:46 AM
>> To: Maven Users List
>> Subject: Re: How to add SYSTEM scope dependency to manifest?
>>
>>> if a dependency is defined as system then 
>>> does not include it in the manifest.  I need to include it in the
>>> manifest.  Any ideas?
>>
>> Is there a reason the obvious answer -- change it to a different scope
>> eg compile -- is not acceptable?
>>
>> Wayne
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>> -
>> This e-mail message may contain privileged and/or confidential
>> information, and is intended to be received only by persons entitled to
>> receive such information. If you have received this e-mail in error,
>> please notify the sender immediately. Please delete it and all attachments
>> from any servers, hard drives or any other media. Other use of this e-mail
>> by you is strictly prohibited.
>>
>>
>> All e-mails and attachments sent and received are subject to monitoring,
>> reading and archival by Monsanto, including its subsidiaries. The
>> recipient of this e-mail is solely responsible for checking for the
>> presence of "Viruses" or other "Malware". Monsanto, along with its
>> subsidiaries, accepts no liability for any damage caused by any such code
>> transmitted by or accompanying this e-mail or any attachment.
>> -
>>
>>
>> -
>> 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
>
>
>
> -
> This e-mail message may contain privileged and/or confidential information,
> and is intended to be received only by persons entitled to receive such
> information. If you have received this e-mail in error, please notify the
> sender immediately. Please delete it and all attachments from any servers,
> hard drives or any other media. Other use of this e-mail by you is strictly
> prohibited.
>
>
> All e-mails and attachments sent and received are subject to monitoring,
> reading and archival by Monsanto, including its subsidiaries. The recipient
> of this e-mail is solely responsible for checking for the presence of
> "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts
> no liability for any damage caused by any such code transmitted by or
> accompanying this e-mail or any attachment.
> -
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

-

Re: FATAL ERROR: Unable to read settings.xml

[Brett Randall]

On Tue, Aug 11, 2009 at 11:00 PM, RFatton  wrote:

>
> Hi all,
>
> New to maven, having trouble getting it working.
>
> I'm using ubuntu and ran "sudo apt-get install maven2" for install.
>
> Also added M2_HOME=/usr/share/maven2, export M2=$M2_HOME/bin, export
> PATH=$M2:$PATH to enviroment.
>
> When I run mvn -version I get:
>
> Maven version: 2.0.9
> Java version: 1.5.0
> OS name: "linux" version: "2.6.24-23-xen" arch: "x86_64" Family: "unix"
>
> But when I try to do anything with mvn I get an error (full error below)
> saying Unable to read settings.xml.
>
> I've found the setting.xml at /etc/maven2/settings.xml
> (/usr/share/maven2/conf is linked to this file location) so tried "mvn -s
> /etc/maven2/settings.xml" and "mvn -s /usr/share/maven2/conf/settings.xml"
> resulting in the sam error.
>
> Tried copying settings.xml to ~/.m2, same error.
>
> Same error when i tried very smiple settings.xml file with:
>
> 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/xsd/settings-1.0.0.xsd";>
>  
>   
>  true
>  http
>  MYPROXY
>  8080
>
>  
>
> 
>
> and
>
> 
>  
>   
>  true
>  http
>  MYPROXY
>  8080
>
>  
>
> 
>
>
> Does this error mean that maven can't find the settings.xml file? (if so
> how
> do I fix it)
>
> How do I know which settings.xml file is being used, system or user?
>
> Do I need to edit settings.xml from it's default at the beginning? If so
> wouldn't one of the simple versions I hev work?
>
> Thanks for help,
>
>
>
>
> ERROR:
>
> When I try "mvn -e package":
>
> + Error stacktraces are turned on.
> -
> this realm = plexus.core
> urls[0] = file:/usr/share/maven2/lib/jsch.jar
> urls[1] = file:/usr/share/maven2/lib/wagon-provider-api.jar
> urls[2] = file:/usr/share/maven2/lib/wagon-file.jar
> urls[3] = file:/usr/share/maven2/lib/doxia-sink-api.jar
> urls[4] = file:/usr/share/maven2/lib/maven2.jar
> urls[5] = file:/usr/share/maven2/lib/plexus-interactivity-api.jar
> urls[6] = file:/usr/share/maven2/lib/wagon-ssh.jar
> urls[7] = file:/usr/share/maven2/lib/wagon-ssh-external.jar
> urls[8] = file:/usr/share/maven2/lib/xml-apis.jar
> urls[9] = file:/usr/share/maven2/lib/plexus-interpolation.jar
> urls[10] = file:/usr/share/maven2/lib/plexus-container-default.jar
> urls[11] = file:/usr/share/maven2/lib/wagon-ssh-common.jar
> urls[12] = file:/usr/share/maven2/lib/wagon-http-shared.jar
> urls[13] = file:/usr/share/maven2/lib/wagon-http-lightweight.jar
> urls[14] = file:/usr/share/maven2/lib/commons-cli.jar
> urls[15] = file:/usr/share/maven2/lib/plexus-utils.jar
> urls[16] = file:/usr/share/maven2/lib/jtidy.jar
> Number of imports: 0
> -
> FATAL ERROR: Unable to read settings.xml
> Error stacktrace:
>
> org.codehaus.plexus.component.repository.exception.ComponentLookupException:
> Unable to lookup component
> 'org.apache.maven.settings.MavenSettingsBuilder',
> it could not be created
>   at
>
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335)
>   at org.codehaus.plexus.embed.Embedder.lookup(Embedder.java:78)
>   at org.apache.maven.cli.MavenCli.buildSettings(MavenCli.java:309)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>   at java.lang.reflect.Method.invoke(libgcj.so.90)
>   at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>   at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>   at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>   at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by:
> org.codehaus.plexus.component.factory.ComponentInstantiationException:
> Could
> not instanciate component: role:
> 'org.apache.maven.settings.MavenSettingsBuilder', implementation:
> 'org.apache.maven.settings.DefaultMavenSettingsBuilder'
>   at
>
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77)
>   at
>
> org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:62)
>   at
>
> org.codehaus.plexus.DefaultPlexusContainer.createComponentInstance(DefaultPlexusContainer.java:1464)
>   at
>
> org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:93)
>   at
>
> org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:92)
>   at
>
> org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:331)
>   ...8 more
> Caused by: java.lang.NoClassDefFoundError:
> org.apache.maven.settings.DefaultMavenSettingsBuilder
>   at java.lang.Class.initializeClass(libgcj.so.90)
>   at java.lang.Class.newInstance(libgcj.so.90)
>   at
>
> org.codehaus.plexus.component.factory.java.Jav

Re: Maven for Non-Java Projects

[Brett Randall]

On Mon, Aug 10, 2009 at 10:50 PM, David Hoffer  wrote:

> We are currently using it for flex in addition to java, for flex the builds
> work fine the only negative is the plugins that allow direct IDE
> integration
> are not as complete as they are for Java.
>
> Regarding C/C++ I have tried to use this in the past, I think I was using
> the nar plugin but can't be sure.  There were a couple of road-blocking
> bugs/missing-features that prevented us from using maven for these types of
> projects.  If I recall correctly the issues were that it did not have
> support for the new universal OSX binaries and on Windows you couldn't
> specify the compiler version.  I.e. it would use whatever MSVC version it
> found on the system, and we had to support multiple versions (this is
> probably true on other platforms as well).  You could probably modify the
> plugins when you find issues like these but I didn't go down that path.
> (This was a couple+ years ago so if these are kept current they may be
> fixed
> by now.)
>
> -Dave
>
> On Mon, Aug 10, 2009 at 5:58 AM, Jan Wedel  wrote:
>
> > Hi there!
> >
> > I already searched google for some help but it seems that it's not
> > really common to use Maven for non-Java projects.
> >
> > However, we plan to be platform and language-independent by supporting
> > e.g. embedded Java, C, C++ and Python. The question is if it is feasible
> > to use Maven for all projects?
> > I found the maven-native-plugin and maven-nar-plugin but I'm not really
> > sure if it supports everything that's needed. We are looking for a
> > server-based central repository maintaining different projects and
> > libraries in various languages.
> >
> > Can anybody who uses or used any of these or other plug-ins to support
> > non-Java projects please respond with some comments, hints, suggestions,
> > pro and cons etc. that might be helpful?
> >
> > Thanks a lot!
> >
> > Jan
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

I haven't yet had much joy with Maven-plugins for building Windows-native
DLLs from C++ using the MSVC compiler, so if anyone would like to nominate
their favorite plugin there.  native-mave-plugin seems out-of date or not
maintained for latest MSVC compiler versions?

Brett

Re: Release from branch - Subversion is not happy.

[Brett Randall]

On Thu, Aug 6, 2009 at 5:53 AM, David C. Hicks  wrote:

> I am getting this error when attempting to release:prepare from a branch:
>
>Unable to tag SCM
>Provider message:
>The svn tag command failed.
>Command output:
>svn: Commit failed (details follow):
>svn: Source url
>'svn://svn.enttek.com/allureglobal/dm/branches/salient-0.9.22' is
>from different repository
>
> I've seen Subversion complain about URLs not matching before, but that
> was always when checking into the same portion of the repository.  In
> this case, I assume that the maven-release-plugin is attempting to
> create a new tag in the "tags" area.
>
> My command line is:   mvn --batch-mode -DpreparationGoals="clean
> install" release:prepare
> Any ideas how I can get this working?  I'm unable to release a branch
> for testing because of this error.
>
> Thanks,
> Dave
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
What are your SCM URLs?  This has come up before when a username was
included in the SCM URL.  Google finds this:
http://www.mail-archive.com/users@maven.apache.org/msg74843.html .

Best
Brett

Re: [PLEASE TEST] Maven 2.2.1-RC2

[Brett Randall]

On Wed, Aug 5, 2009 at 12:21 PM, Brian Fox  wrote:

> That's an ld bug in the release plugin. It bumps the property to
> the being released version but doesn't bump it to the next dev
> version.
>
> On Tue, Aug 4, 2009 at 8:41 PM, Brett Randall wrote:
> > On Tue, Aug 4, 2009 at 9:49 AM, John Casey 
> wrote:
> >
> >> Hi again,
> >>
> >> After Brett sorted out some issues that got lost in the source-control
> mess
> >> on my localhost, and I resolved a couple more stragglers that came up as
> a
> >> result of testing out RC1, I think we're in better shape to attempt a
> >> release again.
> >>
> >> Before we do, I'd like to get as many eyes as possible on this latest
> >> release candidate:
> >>
> >>
> >>
> https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
> >>
> >> Please file JIRA issues for anything you come across that still seems
> >> broken. The list of issues we've resolved so far for this release is
> here:
> >>
> >>
> >>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15328
> >>
> >> Thanks!
> >>
> >> -john
> >>
> >> ---
> >> John Casey
> >> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> >> Member, Apache Software Foundation
> >>
> >> "What we have to learn to do, we learn by doing."
> >>   -Aristotle
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> > Hi John,
> >
> > in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development
> > iteration, @800602, it looks like the maven-release-plugin has not bumped
> >
> > 
> >2.2.1-RC2
> >
> > ... to RC3-SNAPSHOT.  Is this a deploy-regression, or am I missing
> > something?  This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a
> clean
> > repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2
> >
> >
> https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600&r2=800602&diff_format=h
> >
> https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602&content-type=text%2Fplain
> >
> > Cheers
> > Brett
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Thanks Brian - I'll bug the current state of the 2.2.x branch then, and see
if I can find the release plugin bug you refer to and whether it has
regressed or is still open.

Cheers
BRett

Re: [PLEASE TEST] Maven 2.2.1-RC2

[Brett Randall]

On Tue, Aug 4, 2009 at 9:49 AM, John Casey  wrote:

> Hi again,
>
> After Brett sorted out some issues that got lost in the source-control mess
> on my localhost, and I resolved a couple more stragglers that came up as a
> result of testing out RC1, I think we're in better shape to attempt a
> release again.
>
> Before we do, I'd like to get as many eyes as possible on this latest
> release candidate:
>
>
> https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2
>
> Please file JIRA issues for anything you come across that still seems
> broken. The list of issues we've resolved so far for this release is here:
>
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=15328
>
> Thanks!
>
> -john
>
> ---
> John Casey
> Developer and PMC Member, Apache Maven (http://maven.apache.org)
> Member, Apache Software Foundation
>
> "What we have to learn to do, we learn by doing."
>   -Aristotle
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Hi John,

in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development
iteration, @800602, it looks like the maven-release-plugin has not bumped


2.2.1-RC2

... to RC3-SNAPSHOT.  Is this a deploy-regression, or am I missing
something?  This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a clean
repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2

https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600&r2=800602&diff_format=h
https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602&content-type=text%2Fplain

Cheers
Brett

Re: Sun Jar files.

[Brett Randall]

On Mon, Aug 3, 2009 at 11:51 PM, Samir  wrote:

> I'm trying to compile one of the simpler projects I have which depends on
> log4j.
>
> As soon as I try to compile it, I get:
>
>
>   Missing:
>   --
>   1) javax.jms:jms:jar:1.1
>
> Try downloading the file manually from:
> http://java.sun.com/products/jms/docs.html
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=javax.jms -DartifactId=jms
>   -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file
>
> Alternatively, if you host your own repository you can deploy the
>   file there:
> mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms
>   -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
>   -DrepositoryId=[id]
>
> Path to dependency:
>   1) com.ntkn:NTKNSharedLib:jar:1.3.0
>   2) log4j:log4j:jar:1.2.15
>   3) javax.jms:jms:jar:1.1
>
> Okay.. fine.  I go the website and grab the file and I get a choice between
> a pdf file and a .ps file.  Now, I suppose I can add those to my repo, but
> I'm not sure what type of packaging to use nor which one I should get.
> Any help appreciated.
>
> --
> Sam
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
If you don't need the JMS features in log4j, you can exclude that dependency
(it ought to have been made optional). See
http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-problems-in-maven-using-exclusions/.

Brett

Re: Dependency missing on Windows

[Brett Randall]

Hi Robert,

javax.xml.stream was added to the JDK @1.6 (6) - could it be that you 
are building locally with a 1.6 JDK whereas your CI server is using 1.5 
(which I don't think covers this dependency in the JDK)?


I know you have detailed some info contra to that, but it seems the most 
likely reason to me.  Either way I'm pretty sure this dep is not in JDK 
1.4 on your server, which would explain the missing dep.  Double-check 
your local/remote build JDKs.


Best
Brett


robert.kl...@innovations.de wrote:

Hi,

I have a strange experience with a missing dependency. The problem
occurred when upgrading spring-ws-core to version 1.5.7. In that version
they changed a dependency from stax:stax-api to
javax.xml.stream:stax-api.

This change worked fine on my machine (yeah, I know) but broke the build
on our ci server, as the new dependency resolved to stax-api-1.0-2.jar
which is built with Java 1.5 and not 1.4 (which we unfortunately must
support).

The interesting thing: when calling mvn dependency:tree on the server
showed the dependency but it did not appear on my machine

This of course would explain, why the build worked locally.

Can anybody explain this difference in dependency resolution?

Some details
- The server is running Linux with Maven 2.0.9 and Java 1.5
- I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with same
result) and Java 1.6
- Same Repositories
- Server and Windows should use Java 1.4 for building
- It is mulit-module project
- In the project is a transitive dependency to stax:stax-api in version
1.0.1 (this version was used by spring-ws-core before the upgrade)

Cheers,

Robert Klaus
Business Rules Management
  



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

Re: Vote for more Maven documentation

[Brett Randall]

+1


On 7/17/09, Dan Tran  wrote:
> It seems you are spamming the list to get attention, so far it does
> not work, so please stop it
>
> my 2c
>
> -D
>
> On Thu, Jul 16, 2009 at 10:38 AM, Peter
> Horlock wrote:
>> 2009/7/16 Manos Batsis 
>>
>>>
>>> It should be fair to assume that if Tim needed opinions, he would just
>>> ask
>>> for them. Once.
>>>
>>> Cheers,
>>>
>>> Manos
>>>
>>
>> Actually, just in case you didn't notice, you'r spaming the list with even
>> more unrelated stuff than I did.
>> My mail was at least, related, even if I sended it twice - I just think
>> that
>> not everyone might have seen it (and it seems so as still more and more
>> people are voting), and to give them a chance to vote too.
>> Love you too!
>> P.s.: Did I already tell you to vote here:
>> http://www.doodle.com/p42ebutub2zx4kb4
>>
>> ;-)
>>
>> Cheers,
>>
>> Peter
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-- 
Sent from my mobile device

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

Re: maven spring eclipse and properties/spring config

[Brett Randall]

Hi Justin,

What is the license?  http://www.box-spring.org/license.html doesn't yet 
list one .


Brett

Edelson, Justin wrote:

This is getting a little off-topic, but I feel obliged to mention that we 
recently open sourced our generalized solution for dealing with the problem of 
environmental-specific Spring configuration, known as BoxSpring. Our experience 
with both Spring and our prior DI container lead to the conclusion that 
property placeholder was not a suitable solution. You can read the details of 
this project at http://www.box-spring.org/.
 
Justin




From: Mohan KR [mailto:kmoh@gmail.com]
Sent: Sat 7/11/2009 1:31 PM
To: 'Maven Users List'
Subject: RE: maven spring eclipse and properties/spring config



Yup, that is a decision you have to make. But in general, the approach I
have been using is
this:
- You spring-context files rarely should be different for each environment
(if you think hard enough, you
  can achieve it :)).
- We externalize all environment specific information from Spring Context
files as properties and use
  Spring PPC (property placeholder) to substitute the relevant values during
the Bean Factory lifecycle.
- You can do all the resource filtering (maven) on *those* properties files
above that are externalized.
  
It will take a very long message or an article to show an example :), but

information above should get
you going, I hope.

Thanks,
mohan kr

-Original Message-
From: Tim O'Brien [mailto:tobr...@discursive.com]
Sent: Saturday, July 11, 2009 11:03 AM
To: Maven Users List
Subject: Re: maven spring eclipse and properties/spring config

On Fri, Jul 10, 2009 at 1:54 PM, Vincent Fumo wrote:
  

I'm converting an old project to maven and I have a question re: spring.
This project has about 20 spring config files and it reads them all in on
startup and uses the  In addition I have 4 properties files
(local/dev/qa/prod) that I'd like to use to inject/filter/substitute


values
  

into them depending on the build. Lastly I am using the eclipse plugin to
generate an eclipse project.
What I need to know is the following :

1) where should I put the spring files? I am considering
src/main/resources/spring



If you load them from the classpath, put them in src/main/resources.
By default everything in this directory will end up in target/classes
(if your project uses a packaging of "jar")

  

2) how should I best filter the props files? Should I use maven for this
(using profiles in some way), or should I load the files in the app and


use
  

the spring properties configurator?



I don't think anyone on this list is qualified to make this
architectural decision for you.   But, if you wanted to use Maven
Resource filtering, you could. You would have a single properties
file:  whatever.properties which would contain references to arbitrary
properties such as "${whatever.jdbc.url}", then you would use profiles
and configure resource filtering on this properties file.

  

3) what is the best way to use the eclipse plugin to generate a project
where I can run the app and it can see the newly filtered spring files
(instead of the src ones)?




m2eclipse is going to automatically call "process-resources
resources:testResources" every time you change a resource and copy the
result to target/classes. You can control the profile via your
project's Maven preferences in m2eclipse.


  

Can anyone help me out? I'd certainly give more info if needed.




-
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: How can I set maven memory size?

[Brett Randall]

env MAVEN_OPTS="-Xms256m -Xmx1024m" mvn install

youhaodeyi wrote:

Can I use it as command line argument instead of setting environment
variable?


dchicks wrote:
  

set the MAVEN_OPTS environment variable...

export MAVEN_OPTS="-Xms256m -Xmx1024m"


Something like that.


youhaodeyi wrote:


I got a maven project and compile it by maven. Then I got the error
"java.lang.OutOfMemoryError: Java heap space". How can I set the memory
size
running mvn command?

thanks.
  
  



  



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

Re: This might be the easiest filter question you have ever seen

[Brett Randall]

Hi Grant,

It should work as you want it too.  Which version of Maven and the 
resources plugin? Do you have any other overlapping resource 
declarations from another profile?


Brett

Grant Rettke wrote:

This might be the easiest filter question you have ever seen...

I want to filter a properties file located related to the pom under
/src/main/conf/db2was/com/silvermoongroup/fsa/jndi.properties, so I
added the following entry:




src/main/conf/db2was

**/*.properties

true


...

When I run this, the properties file is not filtered, but it shows up
where I expect it:

target\smg-iaa-fsa-web-1.0\WEB-INF\classes\com\silvermoongroup\fsa

Now, when I set up the resource directory slightly incorrectly, and
instead specify:

src/main/conf/db2was/com/silvermoongroup/fsa

The properties file does get filtered!

However, it shows up in target/classes which is the default and of
course not desired.

Any clues what I am doing wrong here?

I must be doing something really stupid; which is why I can't figure it out!

-
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: running junit test via ant using antrun plugin

[Brett Randall]

I've not dealt with this before so take this advice with a grain of 
salt, but here's something to try: Run mvn dependency:tree to see if 
another dependency elsewhere is relying on junit 3.x - maybe you can fix 
or exclude it.


Best
Brett

ZJacobson wrote:

Hi-

I must be doing something really stupid.  I can't get ant to use junit 4
when invoked via the antrun plugin.  My tests all fail because the test
runner can't find any tests (since none of the tests extend TestCase). If I
just run the tests via the ant script, the tests run and pass.  But when I
run via maven (which antcall's the same ant script) the test don't run.  Is
there a way to figure out why it seems that ant is only finding junit 3.x? 
mvn -X doesn't give me ant -debug.


This is the configuration of maven-antrun-plugin:
 
  
ant-tests
test

  

  

  


  run

  
  

  
 
  ant
  ant-nodeps
  1.7.0
 
 
  ant  
  ant-junit  
  1.6.5  
   
   
  junit  
  junit  
  4.4

 
  

Thanks-
Zak

  



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

2.0.9->2.1.0 change/regression in relocation WARNING?

[Brett Randall]

Hi,

I'm trying to understand if there is a regression or deliberate change 
in WARNING reporting of relocated artifacts between Maven 2.0.9 and 
Maven 2.1.0.


I tested with a well-known relocated artifact servletapi:servletapi:2.3 
which is relocated to javax.servlet:servlet-api:2.3.  Test POM and test 
results follow.  Basically, no WARNING is issued in 2.1.0, whereas a 
clear one is issued in 2.0.9.  I've used dependency:resolve as the goal 
below, but the same happens for a full install lifecycle.


Regression or intended and if so, how should we be alerted to 
relocations? Apologies if this is well understood.


Thanks
Brett

Test POM:

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
   relocation-warning
   0.0.1-SNAPSHOT
   
   
   servletapi
   servletapi
   2.3
   
   


Output of dependency:resolve 2.0.9 (snipped output):

mvn --version
Maven version: 2.0.9
Java version: 1.6.0_13
OS name: "linux" version: "2.6.28-13-generic" arch: "amd64" Family: "unix"

#mvn dependency:resolve

[WARNING] While downloading servletapi:servletapi:2.3
 This artifact has been relocated to javax.servlet:servlet-api:2.3.


and 2.1.0 (full output):

mvn --version
Apache Maven 2.1.0 (r755702; 2009-03-19 06:10:27+1100)
Java version: 1.6.0_13
Java home: /usr/lib/jvm/java-6-sun-1.6.0.13/jre
Default locale: en_AU, platform encoding: UTF-8
OS name: "linux" version: "2.6.28-13-generic" arch: "amd64" Family: "unix"

mvn dependency:resolve[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] 


[INFO] Building Unnamed - test:relocation-warning:jar:0.0.1-SNAPSHOT
[INFO]task-segment: [dependency:resolve]
[INFO] 


[INFO] [dependency:resolve]
[INFO]
[INFO] The following files have been resolved:
[INFO]javax.servlet:servlet-api:jar:2.3:compile
[INFO]
[INFO] 


[INFO] BUILD SUCCESSFUL
[INFO] 


[INFO] Total time: 2 seconds
[INFO] Finished at: Tue Jul 07 16:49:30 EST 2009
[INFO] Final Memory: 21M/289M
[INFO] 




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

Re: assist request with missing m2eclipse dependency

[Brett Randall]

Hi Tony,

I'm not sure what the bundle type is that you are referencing, but I 
think if you remove that and pick up the default jar it will work.


Best
Brett

tony_k wrote:

i'll preface this with the fact that i'm new to maven and m2eclipse, so
forgive me if i'm being dense,
but i'm just trying to build a java project in eclipse/galileo using the
m2eclipse plugin,
and i'm specifying the dependency:
Code:


org.springframework.security
spring-security-core
2.0.4
bundle
compile


and i'm getting:

Quote:
Missing artifact
org.springframework.security:spring-security-core:bundle:2.0.4:compile

- the spring-security-core-2.0.4 pom and jar artifacts are in the
appropriate dir in my local .m2 tree
(org/springframework/security/spring-security-core/2.0.4)

- could this be an m2eclipse/maven issue, something having to do with
"bundle" packaging, both or neither?

- could it be a misleading error message where it's really an issue with one
of the myriad transitive dependencies but it's not telling me which one is
the issue?

any guidance appreciated...

thx,
tony. 
  



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

Re: System scope dependency can't find class in rt.jar?

[Brett Randall]

Long shot - I know that "newest" in /usr/lib/jvm/newest/jdk/jre/lib/rt.jar
suggests it is a JDK6 JDK, but might be worth double-checking on the build
machine, in case a JDK5 slipped in unnoticed (which won't have this class).
I see you've extracted the classes from the JAR, but maybe you did this from
a different copy.

Brett

On Thu, May 7, 2009 at 1:57 AM, Charles McCallum wrote:

> I need to reference WSBindingProvider, a class in the standard rt.jar:
>
>  package edu.upenn.library.itadd.dla.fedora;
>  ...
>  import com.sun.xml.internal.ws.developer.WSBindingProvider;
>  ...
>WSBindingProvider bp = (WSBindingProvider)port;
>  ...
>
> This builds fine in Eclipse (without maven), but when I try to build from
> the commandline I get this:
>
>  ...
>  [INFO]
> 
>  [ERROR] BUILD FAILURE
>  [INFO]
> 
>  [INFO] Compilation failure
>
>  
> /usr/local/dla-input/lib/java/FedoraPost/src/main/java/edu/upenn/library/itadd/dla/fedora/Post.java:[16,40]
> package com.sun.xml.internal.ws.developer does not exist
>
>  
> /usr/local/dla-input/lib/java/FedoraPost/src/main/java/edu/upenn/library/itadd/dla/fedora/Post.java:[101,5]
> cannot find symbol
>  symbol  : class WSBindingProvider
>  location: class edu.upenn.library.itadd.dla.fedora.Post
>  ...
>
> I've tried several different things in the POM, but they make no
> difference. Here's one permutation:
>
>
>  dummy
>  dummy
>  1
>  system
>  /usr/lib/jvm/newest/jdk/jre/lib/rt.jar
>
>
> -- As I understand it, this is an appropriate use of system scope: This
> class should just be available through the JDK on any installation.
>
> -- If I could get it to work, I'd certainly use a property reference in the
> systemPath, but here I'm specifying the path explicitly so there's one less
> variable.
>
> -- For system scope, my understanding is that the groupId, artifactId, and
> version can be arbitrary. For example,
> http://mail-archives.apache.org/mod_mbox/maven-users/200710.mbox/%3c4725b62a.3080...@udo.edu%3e
>
>
> I have a work-around: that is to strip the rt.jar down to just the
> subpackage we need, and put it in our local repository, but that really
> doesn't seem like the right thing to do. Any suggestions?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: jetty:run class path

[Brett Randall]

The FNFE is pretty clear about where Spring is expecting to find your
context file based on your configuration. Note that this file is
optional for Spring MVC, otherwise for that config you need to have
applicationContext.xml under WEB-INF and therefore in
src/main/webapp/WEB-INF by default.

This problem is one of Spring config so it's probably best discussed
on one of their forums.

Brett


On 4/29/09, Don Hosek  wrote:
> It's being loaded using
>
>   
>   contextConfigLocation>
>   applicationContext.xml
>   
>
> in the web.xml file. My servlet.xml is under WEB-INF and that doesn't
> seem to be the problem. The relevant bit of logs appears to be
>
> INFO: Loading XML bean definitions from ServletContext resource [/WEB-
> INF/applicationContext.xml]
> Apr 27, 2009 8:38:53 PM org.springframework.web.context.ContextLoader
> initWebApplicationContext
> SEVERE: Context initialization failed
> org.springframework.beans.factory.BeanDefinitionStoreException:
> IOException parsing XML document from ServletContext resource [/WEB-
> INF/applicationContext.xml]; nested exception is
> java.io.FileNotFoundException: Could not open ServletContext resource
> [/WEB-INF/applicationContext.xml]
>   at
> org
> .springframework
> .beans
> .factory
> .xml
> .XmlBeanDefinitionReader
> .loadBeanDefinitions(XmlBeanDefinitionReader.java:349)
>
>
> On 28 Apr 2009, at 14.50, Brett Randall wrote:
>
>> Which mechanism are you using in Spring to load the context?  What
>> error/stack-trace do you get?
>>
>> Note that if you are using Spring MVC and a DispatcherServlet, it
>> expects by
>> default to find the context file under WEB-INF directly, so your
>> source path
>> would be src/main/webapp/WEB-INF/myservlet-servlet.xml .
>>
>> Brett
>>
>> On Wed, Apr 29, 2009 at 7:17 AM, Don Hosek 
>> wrote:
>>
>>> Hmm, I've got a spring application context XML file stored in
>>> src/main/resources But it's not being found in the classpath when I
>>> do mvn
>>> jetty:run. Checking the target/classes directory when I run it, I
>>> see the
>>> file there, but it's not being found by the jetty container. What
>>> should I
>>> be doing?
>>>
>>> -dh
>>>
>>>
>>> -
>>> 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
>
>

-- 
Sent from my mobile device

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

Re: jetty:run class path

[Brett Randall]

Which mechanism are you using in Spring to load the context?  What
error/stack-trace do you get?

Note that if you are using Spring MVC and a DispatcherServlet, it expects by
default to find the context file under WEB-INF directly, so your source path
would be src/main/webapp/WEB-INF/myservlet-servlet.xml .

Brett

On Wed, Apr 29, 2009 at 7:17 AM, Don Hosek  wrote:

> Hmm, I've got a spring application context XML file stored in
> src/main/resources But it's not being found in the classpath when I do mvn
> jetty:run. Checking the target/classes directory when I run it, I see the
> file there, but it's not being found by the jetty container. What should I
> be doing?
>
> -dh
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Incompatible initial and maximum heap sizes specified

[Brett Randall]

Google finds a number of Sun JDK bugs for this error message - which
JDK/version are you using?

As a workaround, try setting -Xms and -Xmx to the same value if you can
tolerate that setting.

Brett

On Wed, Apr 29, 2009 at 6:01 AM, johnnyCash <
deniseandjohn.di...@tiscali.co.uk> wrote:

>
> Have just tried to install MAVEN 2.1.0 and set all my system variables.
> Every
> different version of MAVEN_OPTS results in ...
>
> C:\Users\John>mvn --version
> Error occurred during initialization of VM
> Incompatible initial and maximum heap sizes specified
>
> It is currently a user variable ...
> MAVEN_OPTS=-Xms256m -Xmx512m
>
> Any ideas?
> --
> View this message in context:
> http://www.nabble.com/Incompatible-initial-and-maximum-heap-sizes-specified-tp23284917p23284917.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: Checking the java class version in maven artifacts

[Brett Randall]

I think this was asked on the list last week, or recently anyway.  The
poster was pointed at https://animal-sniffer.dev.java.net/ .

Brett

On Sun, Mar 22, 2009 at 6:43 AM, Stefan Armbruster
wrote:

> Hi,
>
> is there a maven plugin that provides a in-depth check of the java class
> version in a generated artifact, e.g. a war file?
> Assume a deployment environment using jdk 1.4. Developers work on java 6.
> The
> deployment should fail, if any java class has a class version >48 (48 is
> the
> version for 1.4). For java code inside the projects that's easy by setting
> source and target to 1.4 in maven-compiler-plugin. But how to make sure
> that
> no dependency jar contains any class file >48?
>
> It would be rather easy to implement a mojo for this job. I wonder if this
> feature already exists somewhere - I don't want to reinvent the wheel
> twice.
>
> Regards,
> Stefan
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: maven errors on xml security package

[Brett Randall]

Hi Kevin,

Have you configured the -source and -target options of the
maven-compiler-plugin?

Best
Brett

On Fri, Mar 6, 2009 at 8:57 AM, Kevin Witten wrote:

> Hello,
>
> I'm having trouble building with maven. The issue is that it can't find the
> xml security packages.
> I'm using the java jdk 1.6_06 which includes the apache xml security
> package.
> This builds fine using ant, but we are converting to maven and I can't get
> this to build with maven.
>
> Any help would be appreciated.
>
>
> Here is the error:
>
> $ mvn clean install
> [INFO] Scanning for projects...
> [INFO]
> 
> [INFO] Building tr69lib
> [INFO]task-segment: [clean, install]
> [INFO]
> 
> [INFO] [clean:clean]
> [INFO] Deleting directory
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\target
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Compiling 124 source files to
> c:\Codebase\DocomoIntertouch\Shared\tr69lib
> \target\classes
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\SetVouchers.java:[4,53]
> package com.sun.org.apache.xml.internal.security.utils does not exist
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\ISetVouchers.java:[3,53]
> package com.sun.org.apache.xml.internal.security.utils does not exist
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\SetVouchers.java:[22,16]
> cannot find symbol
> symbol  : class Base64
> location: class com.nomadix.tr69.cpemethods.SetVouchers
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\SetVouchers.java:[33,26]
> cannot find symbol
> symbol  : class Base64
> location: class com.nomadix.tr69.cpemethods.SetVouchers
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\SetVouchers.java:[40,15]
> cannot find symbol
> symbol  : class Base64
> location: class com.nomadix.tr69.cpemethods.SetVouchers
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\ISetVouchers.java:[20,19]
> cannot find symbol
> symbol  : class Base64
> location: interface com.nomadix.tr69.cpemethods.ISetVouchers
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\ISetVouchers.java:[27,8]
> cannot find symbol
> symbol  : class Base64
> location: interface com.nomadix.tr69.cpemethods.ISetVouchers
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\SetVouchers.java:[29,36]
> cannot find symbol
> symbol  : class Base64
> location: class com.nomadix.tr69.cpemethods.SetVouchers
>
> c:\Codebase\DocomoIntertouch\Shared\tr69lib\src\main\java\com\nomadix\tr69\cpemethods\SetVouchers.java:[53,11]
> cannot find symbol
> symbol  : class Base64
> location: class com.nomadix.tr69.cpemethods.SetVouchers
>
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Thu Mar 05 13:52:22 PST 2009
> [INFO] Final Memory: 10M/18M
> [INFO]
> 
>
>
>
> Kevin Witten
> Software Engineer
> Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA
> 91320  *  USA
> direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax
> interTouch Group of Companies  *  a NTT DoCoMo Group company
> Enhancing Guest Experience
> www.inter-touch.com *  www.maginet.net<
> http://www.maginet.net/> *  www.percipia.com *
> www.nomadix.com   *  www.azure.com.au<
> http://www.azure.com.au/>
>
> 
> Notice? The information and attachment(s) contained in this communication
> are intended for the addressee only, and may be confidential and/or legally
> privileged. If you have received this communication in error, please contact
> the sender immediately, and delete this communication from any computer or
> network system. Any interception, review, printing, copying,
> re-transmission, dissemination, or other use of, or taking of any action
> upon this information by persons or entities other than the intended
> recipient is strictly prohibited by law and may subject them to criminal or
> civil liability. None of the interTouch Group of Companies shall be liable
> for the improper and/or incomplete transmission of the

Re: Can no longer create war file

[Brett Randall]

What happens if you "mvn clean" or otherwise brute-force delete the
offending folder:

C:\Workspaces\ResultReporter\resultreporter\player\player-core\target\classes
(Access is denied)

Brett

On Fri, Feb 27, 2009 at 9:53 PM, Johan S  wrote:

>
> Hi
>
> Suddenly I can't create a war file, with package, install, or war...
> Can't figure out what I have done. It says "Access denied" to classes
> folder. But the jar that is build and should be injected as dependency
> lands
> in the target folder. I have tried to manually copy the file to classes
> folder, but without any luck.
>
> Any help, please...
>
> Error stacktrace:
> org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in
> the plugin manager executing goal
> 'org.apache.maven.plugins:maven-war-plugin:2.1-alpha-2:war': Mojo execution
> failed.
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:505)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:265)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>at
> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>at
>
> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>at
>
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>at
>
> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:585)
>at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
>at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
>at org.codehaus.classworlds.Launcher.main(Launcher.java:31)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Mojo execution
> failed.
>at
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:601)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:498)
>... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to copy
> file for artifact[com.resultreporter.player:player-core:jar:1.1.0:compile]
>at
>
> org.apache.maven.plugin.war.packaging.ArtifactsPackagingTask.performPackaging(ArtifactsPackagingTask.java:125)
>at
>
> org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.handleArtifacts(WarProjectPackagingTask.java:183)
>at
>
> org.apache.maven.plugin.war.packaging.WarProjectPackagingTask.performPackaging(WarProjectPackagingTask.java:103)
>at
>
> org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439)
>at
>
> org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375)
>at
> org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181)
>at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143)
>at
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:579)
>... 21 more
> Caused by: java.io.FileNotFoundException:
>
> C:\Workspaces\ResultReporter\resultreporter\player\player-core\target\classes
> (Access is denied)
>at java.io.FileInputStream.open(Native Method)
>at java.io.FileInputStream.(FileInputStream.java:106)
>at
>
> org.codehaus.plexus.util.io.FileInputStreamFacade.getInputStream(FileInputStreamFacade.java:78)
>at
> org.codehaus.plexus.util.FileUtils.copyStreamToFile(FileUtils.java:1057)
>at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:965)
>at
>
> org.apache.maven.plugin.war.packaging.AbstractWarPackagingTask.copyFile(AbstractWarPackagingTask.java:293)
>at
>
> org.apache.maven.plugin.war.packaging.AbstractWarPackagingTask$1.registered(AbstractWarPackagingTask.java:150)
>at
>
> org.apache.maven.plugin.war.util.WebappSt

Re: Maven Integration for Eclipse - does it support modules?

[Brett Randall]

Try Maven->Update Project Configuration after setting maven-compiler-plugin
configuration.  And I think you want:


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

1.4
1.4



Best
Brett

On Tue, Feb 24, 2009 at 4:53 AM, sebb  wrote:

> On 18/02/2009, Jason van Zyl  wrote:
> > It is always better to import Maven projects as Maven projects, not
> normal
> > projects and then enabling dependency management. We should probably just
> > remove that option as it seems to confuse many people and can also
> corrupt
> > your eclipse projects.
> >
> >  The version of Java used is determined by the JDT integration which
> obeys
> > anything you have setup in the compiler plugin. If nothing is set then
> the
> > default of 1.4 is chosen. This is the configuration framework in action
> and
> > the POM is the source of truth if you are using m2e.
> >
>
> Java version selection does not seem to work, even when the project is
> checked out as a Maven project.
>
> E.g. I checked out maven/surefire/trunk as a Maven project (using
> current version 0.9.7)
>
> This created several projects - looks to be one for each module.
>
> However, all of the projects have been set to use Java 1.3, even
> though some of the POMs specify 1.4.
>
> For example, the surefire-junit4 and surefire-testng POMs have:
>
> maven-compiler-plugin
> 
>  false
>  1.4
> 
>
> yet Eclipse is configured for Java 1.3.
>
> Likewise maven-surefire-plugin, maven-surefire-report-plugin.
>
> [Surefire-booter and surefire-integration-tests seem to require 1.4,
> but fail to specify it in the POM]
>
> >
> >  On 18-Feb-09, at 8:30 AM, sebb wrote:
> >
> >
> > > Thanks, that's fixed it.
> > >
> > > Unfortunately it does not seem to deal with multiple Java versions
> > > well - I would expect it to set the Java version to the highest
> > > version it finds - or at least warn the user that there are multiple
> > > requirements.
> > >
> > > On 18/02/2009, Stefan Seidel  wrote:
> > >
> > > > You have to do:
> > > > right click on project -> Maven -> Enable nested modules
> > > >
> > > > HTH,
> > > >
> > > > Stefan
> > > >
> > > >
> > > > On Wed, 18 Feb 2009 00:45:11 +
> > > > sebb  wrote:
> > > >
> > > >
> > > > > I tried enabling Maven Dependency Management on a project with
> modules
> > > > > (Surefire 2.4.3) and the dependencies from the top-level project
> were
> > > > > added OK, but none of the dependencies for any of the modules were
> > > > > added.
> > > > >
> > > > > Is this the expected behaviour? Or is it a bug?
> > > > >
> > > > > If if is expected, how can one use the plugin with modules?
> > > > >
> > > > > [Using version 0.0.12.20071107-2300 in Eclipse 3.4.1]
> > > > >
> > > > >
> > > >
> > > >
> > > > >
> > -
> > > > > To unsubscribe, e-mail:
> > users-unsubscr...@maven.apache.org
> > > > > For additional commands, e-mail: users-h...@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > best regards
> > > >
> > > > Stefan Seidel
> > > > Software Developer
> > > > 
> > > > VUB Printmedia GmbH
> > > > Chopinstraße 4, D-04103 Leipzig
> > > > tel.+49 (341) 9 60 50 93
> > > > fax.+49 (341) 9 60 50 92
> > > > mail.   ssei...@vub.de
> > > > web.www.vub.de
> > > >
> > > > HRB Köln 24015
> > > > UStID DE 122 649 251
> > > > GF Dr. Achim Preuss Neudorf,
> > > > Dr. Christian Preuss Neudorf
> > > >
> > > >
> > -
> > > > 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
> > >
> > >
> >
> >  Thanks,
> >
> >  Jason
> >
> >  --
> >  Jason van Zyl
> >  Founder,  Apache Maven
> >  jason at sonatype dot com
> >  http://twitter.com/jvanzyl
> >  --
> >
> >  Selfish deeds are the shortest path to self destruction.
> >
> >   -- The Seven Samuari, Akira Kurosawa
> >
> >
> >
> > -
> >  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: Getting error when trying to generate report

[Brett Randall]

I'd try googling "ResourceManager : unable to find resource
'VM_global_library.vm' in any resource loader" - I did and got lots of juicy
hits suggesting particular plug versions etc. - have you tried those
suggestions?

Best
Brett

On Sun, Feb 22, 2009 at 6:39 AM, John Wooten  wrote:

> INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using  VM library template VM_global_library.vm
> :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro :  VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle]
> [INFO] Source directory does not exist - skipping report.
> [INFO] [pmd:pmd]
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] [pmd:cpd]
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO] [statemgmt:start-fork]
> [IN
>
> Apparently a VM_global_library.vm is missing?  Where do I specify it?
>

Re: Searching for Artifacts in maven

[Brett Randall]

Try the Repositories tab.

On Fri, Feb 20, 2009 at 10:18 PM, Vishal Pahwa  wrote:

>
> Thanx for giving me the search link.
>
> Now that I know what is the groupId and artifactId of the particular
> artifact.
>
> How can I get to know on which mirror this artifact is present so that I
> can add that mirror url in my proxy apllication.
>
> Regards
>
> Vishal
>
> -Original Message-
> From: Nord, James [mailto:jn...@nds.com]
> Sent: Friday, February 20, 2009 4:26 PM
> To: Maven Users List
> Subject: RE: Searching for Artifacts in maven
>
> Either use a managed proxy like nexus that has this functionality or try
> here
> http://www.mvnbrowser.com/artifacts-search.html
>
> /James
>
> > -Original Message-
> > From: Vishal Pahwa [mailto:vpa...@sapient.com]
> > Sent: 20 February 2009 10:52
> > To: Maven Users List
> > Subject: Searching for Artifacts in maven
> >
> >
> > Hi
> >
> > As we know that in maven we used to address any artifact with
> > the groupId and artifactId.
> >
> > Now if I just know which version of a specific artifact I
> > need to use in my project, then what would be the best way to
> > get to know the artifactId and the groupId with which this
> > artifact would be available in any of the Maven mirrors so
> > that I can add this dependency in pom.xml
> >
> >
> > Regards
> >
> > Vishal
> >
> >
>
>
> **
> This e-mail is confidential, the property of NDS Ltd and intended for the
> addressee only. Any dissemination, copying or distribution of this message
> or any attachments by anyone other than the intended recipient is strictly
> prohibited. If you have received this message in error, please immediately
> notify the postmas...@nds.com and destroy the original message. Messages
> sent to and from NDS may be monitored. NDS cannot guarantee any message
> delivery method is secure or error-free. Information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> We do not accept responsibility for any errors or omissions in this message
> and/or attachment that arise as a result of transmission. You should carry
> out your own virus checks before opening any attachment. Any views or
> opinions presented are solely those of the author and do not necessarily
> represent those of NDS.
>
> To protect the environment please do not print this e-mail unless
> necessary.
>
> NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales Registered
> no. 3080780 VAT no. GB 603 8808 40-00
>
> **
>
> -
> 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: recurrent exception

[Brett Randall]

Top hit on Google for: DashboardUtils getDocument() SAXException Premature
end of file

is: https://jira.codehaus.org/browse/MOJO-1292

May be relevant to your issue.

Brett

On Mon, Feb 16, 2009 at 10:02 PM, Giovanni Azua wrote:

> Hi,
>
> I have lately seen this exception below recurrently popping out in my
> build.
> Any clues?
>
> TIA,
> Regards,
> Giovanni
>
> [ERROR] DashboardUtils getDocument() SAXException:
> org.xml.sax.SAXParseException: Premature end of file.
>at
>
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:23
> 9)
>at
>
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBu
> ilderImpl.java:283)
>at
>
> org.codehaus.mojo.dashboard.report.plugin.DashBoardUtils.getDocument(DashBoa
> rdUtils.java:886)
>at
>
> org.codehaus.mojo.dashboard.report.plugin.DashBoardUtils.getTaglistReport(Da
> shBoardUtils.java:834)
>at
>
> org.codehaus.mojo.dashboard.report.plugin.DashBoardUtils.getDashBoardMavenPr
> oject(DashBoardUtils.java:308)
>at
>
> org.codehaus.mojo.dashboard.report.plugin.DashBoardReportMojo.executeReport(
> DashBoardReportMojo.java:280)
>at
>
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.
> java:98)
>at
>
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDo
> cumentRenderer.java:139)
>at
>
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Default
> SiteRenderer.java:269)
>at
>
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRe
> nderer.java:101)
>at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
>at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
>at
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManage
> r.java:451)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLife
> cycleExecutor.java:558)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:499)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifec
> ycleExecutor.java:478)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
> ures(DefaultLifecycleExecutor.java:330)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Defa
> ultLifecycleExecutor.java:291)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
> Executor.java:142)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
> )
>at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
> .java:25)
>at java.lang.reflect.Method.invoke(Method.java: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)
>
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Maven 2.0.9 NullpointerException when running tests

[Brett Randall]

I Googled that stack trace for you and it pointed me straight to the POI FAQ
here: http://poi.apache.org/faq.html#faq-N10006 .  Classpath debugging
advice there - you might need to check if you have an overlapping
dependency, so dependency:analyze and dependency:tree are probably good
starts.

Best
Brett

On Tue, Jan 27, 2009 at 6:24 AM, aminm  wrote:

>
>
>
> Dave Newton wrote:
> >
> > Geoffrey Wiseman wrote:
> >> On Sun, Jan 25, 2009 at 7:21 PM, Dave Newton 
> >> wrote:
> >>> Does 4.5 not work?
> >> I was just responding to Amin's comment about JUnit 4.4 [...]
> >
> > Ah, missed that--never mind :)
> >
> > Dave
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> >
>
> Hi
>
> Thanks for the replies!  I managed to get the surefire plugin to use junit
> 4.  However I am getting some strange behaviour, in that some of my tests
> fail, while they all run fine in eclipse.  I am using text mining as a
> dependency and exclude the version of poi that comes with it.   The
> exception that I get is
>
>
> testCanCreateLuceneDocumentForMSWordDocument(com.amin.app.lucene.index.handler.ms.MSWordHandlerTest)
> Time elapsed: 0.038 sec  <<< ERROR!
> java.lang.NoSuchMethodError:
>
> org.apache.poi.poifs.filesystem.POIFSFileSystem.getRoot()Lorg/apache/poi/poifs/filesystem/DirectoryNode;
>at org.apache.poi.hwpf.HWPFDocument.(HWPFDocument.java:158)
>at
> org.apache.poi.hwpf.extractor.WordExtractor.(WordExtractor.java:59)
>at
>
> com.amin.app.lucene.index.handler.ms.MSWordHandler.extractText(MSWordHandler.java:16)
>
>
> I know that this exception occurs if I am using an old version of poi
> (2.5),
> even though I have excluded the version that comes with text mining.  I
> have
> added
>
>
>org.apache.poi
>poi
>3.5-beta4
>compile
>
>
> This is very strange and I can't understand why the tests won't run.
>
> Any help again would be appreciated.
>
>
>
> --
> View this message in context:
> http://n2.nabble.com/Maven-2.0.9-NullpointerException-when-running-tests-tp2209372p2220012.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: Iterating through a files using maven plugin

[Brett Randall]

Would referencing it as a  in your POM and allowing it to bind by
default to the generate-sources phase work, rather than running the
individual mojo?

Brett

On Thu, Jan 22, 2009 at 4:49 PM, arve  wrote:

>
> hi,
> I run a maven task mvn appfuse:gen -Dentity=Pojo name.
> if i have 100 pojos in a folder i have to run the same command 100 times.
> Instead is there some plugin/trick whcih could iterate the same command
> with
> different pojo names with a  single command?
> --
> View this message in context:
> http://www.nabble.com/Iterating-through-a-files-using-maven-plugin-tp21598334p21598334.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: What does this mean?

[Brett Randall]

Is this intermittent? Does running with -e -X give any additional hints?  Do
you have a MAVEN_OPTS set with -Xmx - could you be running out of heap
(perhaps at around 512M)?

Best
Brett

On Mon, Jan 19, 2009 at 5:05 PM, David Jencks wrote:

>
> Results :
> Tests run: 1837, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] There are test failures.
> [INFO]
> 
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> 
> [INFO] Total time: 66 minutes 20 seconds
> [INFO] Finished at: Sun Jan 18 19:05:55 PST 2009
> [INFO] Final Memory: 51M/508M
> [INFO]
> 
>
> I think this has happened twice now.
>
> maven 2.0.9, I'm building activemq trunk.
>
> thanks
> david jencks
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Cannot compile simple code

[Brett Randall]

The missing symbol method was added in Java 1.5.  Maven defaults to source
level 1.4.  Set your source/target to a minimum of 1.5 on the
maven-compiler-plugin, see
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html.

Brett

On Mon, Jan 12, 2009 at 10:11 PM, SamadLotia wrote:

>
> Hello fellow Maven users,
> I have been trying to compile an OSGi project created using the PAX
> scripts.
> In the source file ConsoleTaskManager.java on line 15 I have written:
>
> System.out.println(java.lang.String.format("%s", "Why will not this
> compile?"));
>
> When I type "mvn install", I get the following error message:
>
> [INFO] [pax:compile]
> [INFO] Compiling 5 source files to
> /Users/slotia/src/csplugins-slotia/work-pir-api/target/classes
> [INFO] [recovering meta-data]
> [INFO]
> 
> [ERROR] BUILD FAILURE
> [INFO]
> 
> [INFO] Compilation failure
>
> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
> cannot find symbol
> symbol  : method format(java.lang.String,java.lang.String)
> location: class java.lang.String
>
>
> /Users/slotia/src/csplugins-slotia/work-pir-api/src/main/java/org/cytoscape/work/internal/ConsoleTaskManager.java:[15,41]
> cannot find symbol
> symbol  : method format(java.lang.String,java.lang.String)
> location: class java.lang.String
>
> If I uncomment the offending line, the project compiles fine. I also wrote
> a
> 5-line class file with the offending line, and it compiles fine with javac.
> This suggests that there probably isn't a problem with the JDK. I have
> tried
> to clean the project, which deletes the target directory, delete the runner
> directory, and delete the .m2 directory, but it still does not compile.
>
> Here are some specs of my system:
> OS: Mac OS X 10.5.6
> Java: 1.5.0_16-b06-284 32-bit
> Maven: 2.0.9
>
> I am completely lost as to how to fix this. Any help would be greatly
> appreciated. Thank you.
> --
> View this message in context:
> http://www.nabble.com/Cannot-compile-simple-code-tp21412538p21412538.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: how I can ensure that Maven include my own MANIFEST.MF instead of its generated one?

[Brett Randall]

 are covered in the Maven POM reference here
http://maven.apache.org/pom.html#Plugins .  They are nested within a
.

On Sun, Jan 4, 2009 at 11:00 AM, sarah.kho  wrote:

>
> Thank you for the link, unfortunately my build file has no   tag
> inside it. An I can not find out where I should put those tags.  dot hey
> goes inside the  tag?
>
> Thanks
>
>
>
>
>
> Olivier Lamy wrote:
> >
> > Hi,
> > Maybe have a look here
> > http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html
> > .
> >
> > HTH,
> > --
> > Olivier
> >
> > 2009/1/3 legolas :
> >>
> >> Hi
> >> Thank you for reading my post
> >> Can someone please let me know how I can ensure that Maven uses my own
> >> Manifest.MF instead of the one it generates?
> >> I tried to use **/*.MF to ensure that it will include
> >> my
> >> file but it uses its own generated file which is not what I need. I test
> >> the
> >> syntax of **/*.MF and it works for other files and
> not
> >> for the Manifest.mf
> >>
> >> Thanks.
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21268718.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
> >>
> >>
> >
> > -
> > 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://www.nabble.com/how-I-can-ensure-that-Maven-include-my-own-MANIFEST.MF-instead-of-its-generated-one--tp21268718p21271085.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: mvn dependency:resolve what's it for?

[Brett Randall]

>>my project was initially compiled with spring 2.5.6 and after that i
compiled it with spring 2.0.8

How did you enact the change from 2.5.6 to 2.0.8? Did you make a hard-change
to the dependency version, or did you activate a profile?

If you activated a profile, then to see the same results with
dependency:resolve, you would also need to activate the same profile when
running that goal.

On Mon, Dec 22, 2008 at 10:11 PM, aymen83  wrote:

>
> my question is
> if i compile my project with spring 2.0.8 for exemple and i tape mvn
> dependency:reslove the CLI will show that the project was compiled using
> it?
>
> i asked this question because my project was initially compiled with spring
> 2.5.6 and after that i compiled it with spring 2.0.8 so when i tape mvn
> dependency:resolve i see spring 2.5.6 so i was wondering if it was really
> compiled with version2.0.8? or is there another CLI that can be more
> specific?
>
> thanks
>
>
> Brett Randall-2 wrote:
> >
> > According to
> > http://maven.apache.org/plugins/maven-dependency-plugin/index.html ,
> >
> > dependency:resolve<
> http://maven.apache.org/plugins/maven-dependency-plugin/resolve-mojo.html
> >tells
> > Maven to resolve all dependencies and displays the version.
> >
> > This is what it does for my projects.  Do you have a specific question
> > about
> > its operation?
> >
> > On Mon, Dec 22, 2008 at 9:52 PM, aymen83  wrote:
> >
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/mvn-dependency%3Aresolve-what%27s-it-for--tp21125880p21125880.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://www.nabble.com/mvn-dependency%3Aresolve-what%27s-it-for--tp21125880p21126140.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: mvn dependency:resolve what's it for?

[Brett Randall]

According to
http://maven.apache.org/plugins/maven-dependency-plugin/index.html ,

dependency:resolvetells
Maven to resolve all dependencies and displays the version.

This is what it does for my projects.  Do you have a specific question about
its operation?

On Mon, Dec 22, 2008 at 9:52 PM, aymen83  wrote:

>
>
> --
> View this message in context:
> http://www.nabble.com/mvn-dependency%3Aresolve-what%27s-it-for--tp21125880p21125880.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: maven-assembly-plugin resource filtering with shared assembly

[Brett Randall]

Well the good news here is that I updated to maven-assembly-plugin
2.2-beta-3-SNAPSHOT, and the filtering outlined below just works, regardless
of the build start-point.  I couldn't spot where this was fixed.

>From the svn logs it looks like 2.2-beta-3 could go final soon, so I'll
switch back from the SNAPSHOT when I see that announced on the list.

Cheers
Brett

On Sun, Dec 21, 2008 at 9:07 PM, Brett Randall  wrote:

> Hi,
>
>
> I'm having trouble with resource-filtering in an assembly which is shared
> amongst multiple modules in a multi-module project, according to the
> recipe in MDG 
> 12.6.1<http://books.sonatype.com/maven-book/reference/assemblies.html#d0e16128>.
> Maven 2.0.9, Assembly 2.2-beta-2.
>
>
>
> What I'm seeing is this: when I run "mvn package" from a module, it is
> filtering resources correctly (namely substituting ${project.version} - I'm
> not trying to use and file-based filters), however when running "mvn
> package" in the parent directory/project with no other changes, resource
> filtering does not occur.  The shared assembly module has a  with
> true, and this is the one being filtered when run from
> the module.
>
>
>
> When I run in the parent project, the reactor order is:
>
>
>
>1. The shared assembly module (has no parent)
>2. The parent project
>3. Module A (child of 2)
>4. Module B (child of 2)
>5. Module C (child of 2)
>6. An all-modules distribution module (has no parent)
>
>
>
> All POMs have the same groupId and version (a -SNAPSHOT).  Is this enough
> info for anyone to suggest what might be stopping resource-filtering from
> working from the parent/top-level project?
>

maven-assembly-plugin resource filtering with shared assembly

[Brett Randall]

Hi,


I'm having trouble with resource-filtering in an assembly which is shared
amongst multiple modules in a multi-module project, according to the recipe
in MDG 
12.6.1.
Maven 2.0.9, Assembly 2.2-beta-2.



What I'm seeing is this: when I run "mvn package" from a module, it is
filtering resources correctly (namely substituting ${project.version} - I'm
not trying to use and file-based filters), however when running "mvn
package" in the parent directory/project with no other changes, resource
filtering does not occur.  The shared assembly module has a  with
true, and this is the one being filtered when run from
the module.



When I run in the parent project, the reactor order is:



   1. The shared assembly module (has no parent)
   2. The parent project
   3. Module A (child of 2)
   4. Module B (child of 2)
   5. Module C (child of 2)
   6. An all-modules distribution module (has no parent)



All POMs have the same groupId and version (a -SNAPSHOT).  Is this enough
info for anyone to suggest what might be stopping resource-filtering from
working from the parent/top-level project?

Re: Compiling one module into another

[Brett Randall]

Hi Brendon,

Perhaps this article on Creating Skinny
WARsmight
help, demonstrating the use of
packagingExcludes.
 Busting-out the Core library dependency as provided or compiling it
separately into the WAR projects seems like a bit much just to prevent a
bunch of Core's dependencies from shipping ...

Best
Brett

On Thu, Dec 18, 2008 at 7:03 AM, Brendon Davidson wrote:

> Hello,
>
> We have three projects under a single parent project.  The structure is as
> follows:
>
> ParentProject
>  - Core (jar)
>  - Project A (war)
>  - Project B (war)
>
> Core is a set of classes that are used for DB access by both Project A and
> Project B.
>
> We want to keep the size of the war files down.  We've achieved this so far
> by setting their dependencies as provided since most of them will change
> very rarely.  We then provide them locally by adding the dependencies to
> jetty and we manually add the dependency jars to production.
>
> Currently, even core is set as provided in projects A and B (otherwise
> core's dependencies get added to the war which makes the war file huge).  So
> when we deploy a project, we have to upload the latest core jar into the
> Tomcat's lib directory and replace the war file with the new war.  This is
> not the end of the world, but we'd like to get it to where we can simply
> upload the new war.  Ideally, compiling project A(or B) would also compile
> the core classes into war file (WEB-INF/classes/...).
>
> Is this possible?  Thus far, I have been unable to figure out how to get
> this working the way we want.  Any suggestions would be greatly appreciated.
>
> Thanks,
>
> Brendon
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Re: MAVEN certifications

[Brett Randall]

http://letmegooglethatforyou.com/?q=letmegooglethatforyou

Sweet sweet recursion :).

On Wed, Dec 17, 2008 at 7:02 AM,  wrote:

> As opposed to www.just&^%^inggoogleit.com which is the blatantly rude way
> :)
>
>
> On Dec 16, 2008 7:50pm, Wayne Fay  wrote:
>
>> > Just out of curiosity, why is this your new favorite site? So to take
>>
> this
>
>>
>> > off topic, but I saw this and wonder where the use case for this site
>>
> is? i
>
>>
>> > think I might be missing something
>>
>>
>>
>> LetMeGoogleThatForYou.com provides a means of teaching someone how to
>>
>> use Google, in case they don't already know. It is a (mildly rude) way
>>
>> of (indirectly) reprimanding someone when they ask a question that can
>>
>> easily be answered without asking someone else, while still answering
>>
>> the question they asked.
>>
>>
>>
>> The best use of the site I've seen lately was someone on this list
>>
>> asking for the definition of "modicum" after I used that word in an
>>
>> email.
>>
>>
>>
>> Wayne
>>
>>
>>
>> -
>>
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>

Re: archetype-catalog.xml location - archetype:crawl versus archetype:generate

[Brett Randall]

Thanks Raphaël.  Your comments and the Jira issue make it clear.

Regards
Brett

On Thu, Nov 27, 2008 at 6:28 PM, Raphaël Piéroni
<[EMAIL PROTECTED]>wrote:

> This problem is known.
> http://jira.codehaus.org/browse/ARCHETYPE-142
>
> the crawl goal is intended to create a catalog for a remote repository
> (but called in the fs of that repository)
>
> the local catalog is intended to be updated : by hand
> or by the create-from-project goal.
>
> This is why the locations are different. Please note
> that the crawl goal can be configured to create a catalog
> in another directory from where it search.
>
> Hope this helps.
>
>
> Raphaël
>
> 2008/11/27 Brett Randall <[EMAIL PROTECTED]>:
> > Hi,
> >
> > I've just started working with our own archetypes, so very possible that
> I
> > am missing something here:
> >
> > 1) We created a new archetype and "mvn install" -ed it to local.
> > 2) Went to ~/.m2 (on Windows) and ran "mvn archetype:crawl".  This
> created
> > archetype-catalog.xml in the sub-directory "repository".
> > 3) Ran "mvn archetype:generate -DarchetypeCatalog=local", but could not
> > locate the archetype.
> > 4) Noticed that the documenation
> > here<
> http://maven.apache.org/plugins/maven-archetype-plugin/generate-mojo.html#archetypeCatalog
> >suggests
> > that -DarchetypeCatalog=local is a synonym for
> > file://~/.m2/archetype-catalog.xml (i.e. not
> > file://~/.m2/*repository*/archetype-catalog.xml
> > .
> > 5) Moved archetype-catalog.xml up one folder and everything is fine -
> > archetype:generate finds the catalog.
> >
> > So do archetype:crawl and archetype:generate have different expectations
> on
> > where archetype-catalog.xml should live, and is this expected?
> >
> > Thanks
> > Brett
> >
>

archetype-catalog.xml location - archetype:crawl versus archetype:generate

[Brett Randall]

Hi,

I've just started working with our own archetypes, so very possible that I
am missing something here:

1) We created a new archetype and "mvn install" -ed it to local.
2) Went to ~/.m2 (on Windows) and ran "mvn archetype:crawl".  This created
archetype-catalog.xml in the sub-directory "repository".
3) Ran "mvn archetype:generate -DarchetypeCatalog=local", but could not
locate the archetype.
4) Noticed that the documenation
heresuggests
that -DarchetypeCatalog=local is a synonym for
file://~/.m2/archetype-catalog.xml (i.e. not
file://~/.m2/*repository*/archetype-catalog.xml
.
5) Moved archetype-catalog.xml up one folder and everything is fine -
archetype:generate finds the catalog.

So do archetype:crawl and archetype:generate have different expectations on
where archetype-catalog.xml should live, and is this expected?

Thanks
Brett