Re: Jabber not working
I fixed the NPE. Can you try the latest snapshot? http://maven.zones.apache.org/~continuum/builds/branches/continuum-1.0.x/continuum-20060312.02.tar.gz Emmanuel [EMAIL PROTECTED] a écrit : Hi All, I'm using continuum 1.0.3 and added a shell project. then in my pom notifiers i have typejabber/type configuration hostmx.company.com/host port5222/port loginraghu guru/login passwordpassword/password domainNamecompany.com/domainName sslConnectionfalse/sslConnection address[EMAIL PROTECTED]/address isGroupfalse/isGroup /configuration sendOnErrortrue/sendOnError sendOnFailuretrue/sendOnFailure sendOnWarningfalse/sendOnWarning but when i build it, getting the error as 4377956 [Thread-1] INFO org.codehaus.plexus.notification.notifier.Notifier:jabber - Current build state: 2, previous build state: 3 4383040 [Thread-1] ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:build-project - Error while executing task. java.lang.NullPointerException at org.codehaus.plexus.jabber.DefaultJabberClient.logon(DefaultJabberClient.java:103) at org.apache.maven.continuum.notification.jabber.JabberContinuumNotifier.sendMessage(JabberContinuumNotifier.java:218) at org.apache.maven.continuum.notification.jabber.JabberContinuumNotifier.sendNotification(JabberContinuumNotifier.java:135) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.sendNotification(DefaultContinuumNotificationDispatcher.java:170) at org.apache.maven.continuum.notification.DefaultContinuumNotificationDispatcher.buildComplete(DefaultContinuumNotificationDispatcher.java:96) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:363) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:534) I guess i'm missing something thats why getting NullPointer , anyone has any idea on this?? Thanks, Raghu
Re: maven versions
Continuum 1.0.2 use maven 2.0 api that load projects in continuum but builds are done with user-installed maven. Continuum 1.0.3 (that will be release in few days) will use maven 2.0.3 api. You can try a snapshot of it : http://maven.zones.apache.org/~continuum/builds/branches/continuum-1.0.x/continuum-20060312.02.tar.gz Emmanuel uwe schaefer a écrit : hi afaics, there is a maven 2.0.1 bundled and used within the current continuum version, right ? my build-server (linux) seems to suffer from a bug that is fixed in 2.0.2. is there a way making continuum work with the user-installed maven instead of the bundled one ? or am i completely wrong ? cu uwe http://uwe.codesmell.de/blog
Re: [m2,maven-proxy,newbie] Struggling with maven-proxy
On 3/11/06, Poitras , Alexandre [EMAIL PROTECTED] wrote: You have to declare it as mirror of central in your settings.xml file. OK. I added these lines to my settings.xml: mirrors mirror idwolloxmirror/id namewollox mirror/name urlhttp://localhost:1516/repository/url mirrorOfcentral/mirrorOf /mirror /mirrors And I modified my pom.xml so that there are no repository nor pluginRepositories specifications anymore. Now, when calling mvn clean the following happens: [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-clean-plugin' could not be found on repository : central [DEBUG] maven-clean-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the latest version org.apache.maven.plugins:maven-clean-plugin:pom:LATEST [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-clean-plugin:pom:LATEST [DEBUG] maven-clean-plugin: using locally installed snapshot [DEBUG] Artifact not found - using stub model: Unable to determine the release version org.apache.maven.plugins:maven-clean-plugin:pom:RELEASE [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-clean-plugin:pom:RELEASE [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-clean-plugin' does not exist or no valid version could be found [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-clean-plugin' does no t exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1247) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:9 79) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java: 943) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:450) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-cl ean-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. java:225) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager. java:87) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:160) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1218) ... 18 more And my maven-proxy instances shows: Y:\maven-proxyjava -jar maven-proxy-standalone-0.2-app.jar maven-proxy.properties maven-proxy Unversioned 2006-03-12 09:14:36,265 [INFO ] proxy.config.RepoConfiguration - Disabling snapshot cache 2006-03-12 09:14:36,281 [INFO ] proxy.config.RepoConfiguration - Disabling snapshot cache 2006-03-12 09:14:36,281 [INFO ] proxy.config.RepoConfiguration - Repo[www-ibiblio-org]: Enabling cache with period of 3 600 seconds 2006-03-12 09:14:36,281 [INFO ] proxy.config.RepoConfiguration - Repo[dist-codehaus-org]: Enabling cache with period of
RE: Maven 2.0 and j2ee and serious work
Hi Roberto, -Original Message- From: Roberto N Nanamura [mailto:[EMAIL PROTECTED] Sent: dimanche 12 mars 2006 01:45 To: users@maven.apache.org Subject: Maven 2.0 and j2ee and serious work [snip] If maven 2 wants to be taken seriously it MUST support j2ee and web services otherwise maven 1.1 will stick for much longer than you expect. Ok, 2 things here: * Either you're not aware that those plugins exist: ejb, war, ear, axistool, cargo, xdoclet1 and 2, etc * Or you think there are features missing in them, in which case, could you please let us know which ones exactly? Thanks -Vincent ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin:download in m2
Hi, From what I can tell, the andromda plugin for m2 can currently not be downloaded, either because of a bug in the plugin or in maven2. until that is resolved. You have to download the sources and build the plugin yourself. For building and installing it - as you said m2 shall be used for it - I assume a simple mvn clean install should be enough. Note: I'm a maven2 newbie myself and have never used andromda, so use my comments with care ;-) Kind Regards, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Software Design Engineer - Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2,maven-proxy,newbie] Struggling with maven-proxy
On 3/11/06, Khin, Gerald [EMAIL PROTECTED] wrote: [...] So there seems to be still something else that is not correct. In spite of missing no trip wires on my way I managed it in the end. The culprit was the line repo.www-ibiblio-org.url=http://www.ibiblio.org/maven in my maven-proxy.properties configuration file. After replacing it by repo.www-ibiblio-org.url=http://www.ibiblio.org/maven2 everything works like a charm. Thanks a lot, Alexandre, to point me to the right direction. Regards Gerald - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2: changelog plugin password issue
changelog plugin 2.0-beta-1 doesn't use maven-scm but scm plugin use it. You can try changelog plugin 2.0-beta-2-SNAPSHOT, this version use maven-scm too. Emmanuel [EMAIL PROTECTED] a écrit : Hi, I am using maven 2.0.2 and changelog plugin 2.0-beta-1. running mvn site or mvn changelog:changelog results in the stacktrace below and an empty changelog.xml file. running mvn scm:changelog however works, I mean in the logging I can see clearly that it's connecting to cvs. thanks for your help, Peter part of my pom.xml: scm connectionscm:cvs:pserver:[EMAIL PROTECTED]:path:tofolder /connection developerConnection scm:cvs:pserver:[EMAIL PROTECTED]:path:tofolder/developerConnection /scm plugin groupIdorg.codehaus.mojo/groupId artifactIdchangelog-maven-plugin/artifactId version2.0-beta-1/version reportSets reportSet iddual-report/id configuration typerange/type range30/range /configuration reports reportchangelog/report reportfile-activity/report reportdev-activity/report /reports /reportSet /reportSets /plugin This is the resulting changelog.xml file: ?xml version=1.0 encoding=ISO-8859-1 ? changelog changeset start=2006-02-08 end=2006-03-11 /changeset /changelog and here is the stack trace: [INFO] [changelog:changelog] [INFO] Generating changed sets xml to: C:\development\eclipse\workspace\aa\b\target\changelog.xml [ERROR] Error processing command org.netbeans.lib.cvsclient.connection.AuthenticationException: Wrong Password. at org.netbeans.lib.cvsclient.connection.PServerConnection.openConnection(PServerConnection.java:202) at org.netbeans.lib.cvsclient.connection.PServerConnection.open(PServerConnection.java:298) at org.apache.maven.cvslib.CvsConnection.connect(CvsConnection.java:119) at org.apache.maven.cvslib.CvsConnection.processCommand(CvsConnection.java:433) at org.apache.maven.cvslib.CvsChangeLogGenerator.getEntries(CvsChangeLogGenerator.java:98) at org.apache.maven.changelog.ChangeLog.generateSets(ChangeLog.java:430) at org.apache.maven.changelog.ChangeLog.doExecute(ChangeLog.java:369) at org.apache.maven.changelog.ChangeLogReport.getChangeLog(ChangeLogReport.java:263) at org.apache.maven.changelog.ChangeLogReport.generateChangeSetsFromSCM(ChangeLogReport.java:218) at org.apache.maven.changelog.ChangeLogReport.getChangedSets(ChangeLogReport.java:198) at org.apache.maven.changelog.ChangeLogReport.executeReport(ChangeLogReport.java:173) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117) at org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:92) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:324) 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) [INFO] ChangeSet between 2006-02-08 and 2006-03-11: 0 entries [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Fri Mar 10 17:57:25 CET 2006 [INFO] Final Memory: 4M/9M [INFO]
[M2] Uploading non-maven jars to a repository
Is there a command to help you upload and generate a fake POM to a repository (as opposed to your local file system). I have found mvn install:install-file -Dfile=path-to-file -DgroupId=group-id \ -DartifactId=artifact-id -Dversion=version -Dpackaging=packaging For putting the file into the local repository but this does not generate check sums and if you upload these jars to a shared repository maven complains. This would make it a lot easier for people to set up POM's for Ibiblio or for private repositories of jars with licenses that prohibit being uploaded to ibiblio. Any one got any ideas? Thanks Ben
Re: [M2] Uploading non-maven jars to a repository
On 3/12/06, Ben Gidley [EMAIL PROTECTED] wrote: Is there a command to help you upload and generate a fake POM to a repository (as opposed to your local file system). You can create an 'upload bundle' with mvn repository:bundle-create Uploading to ibiblio is described here; it should work the same for your own repository: http://maven.apache.org/guides/mini/guide-ibiblio-upload.html mvn install:install-file -Dfile=path-to-file -DgroupId=group-id \ -DartifactId=artifact-id -Dversion=version -Dpackaging=packaging This one also has -DgeneratePom=true, but it's still for your local repository. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Stacktrace when downloading from repo - HELP
Hi,
I got the following stack trace when trying to download from an internal
mvn2 repo.
from the specified remote repositories:
R (https://my.internal.host/mvn),
central (http://repo1.maven.org/maven2)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:140)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:63)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit
ory(DefaultMavenProjectBuilder.java:386)
... 26 more
Caused by: org.apache.maven.wagon.TransferFailedException: Error
transferring file
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData
(LightweightHttpWagon.java:99)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(Defa
ultWagonManager.java:369)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul
tWagonManager.java:282)
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Defaul
tWagonManager.java:244)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau
ltArtifactResolver.java:124)
... 28 more
Caused by: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
at
com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1476
)
at
com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
at
com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHa
ndshaker.java:847)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHands
haker.java:106)
at
com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:4
33)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java
:815)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSo
cketImpl.java:1025)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.
java:1038)
at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:402
)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Ab
stractDelegateHttpsURLConnection.java:170)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnec
tion.java:913)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsUR
LConnectionImpl.java:234)
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData
(LightweightHttpWagon.java:85)
... 33 more
Caused by: sun.security.validator.ValidatorException: PKIX path building
failed: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
at
sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221)
at
sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:1
45)
at sun.security.validator.Validator.validate(Validator.java:203)
at
com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X50
9TrustManagerImpl.java:172)
at
com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSL
ContextImpl.java:320)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHa
ndshaker.java:840)
... 44 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
at
sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPat
hBuilder.java:236)
at
java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194)
at
sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216)
... 49 more
Here is the pom.xml
project
. . .
nameFooBar/name
groupId foobar/groupId
artifactId${pom.name}/artifactId
version1.0/version
packagingjar/packaging
repositories
repository
idR/id
layoutdefault/layout
urlhttps://my.internal.host/mvn/url
/repository
/repositories
dependencies
dependency
groupIdsomeGroup/groupId
artifactIdsomeArtifact/artifactId
version1.0/version
scopecompile/scope
/dependency
/dependencies
/project
And here is the settings.xml
settings
servers
server
idR/id
Re: how to point 'mvn archetype:create' at internal repository?
Thanks Wendy. To summarise, the currently released maven-archetype-plugin does have an issue, which means that it can only see archetypes which are in the default repository. However, if you're prepared to build the archetype components from source, a new feature has since been added that lets you specify the repositories you wish to use on the commandline. See http://jira.codehaus.org/browse/ARCHETYPE-1 for full details. On 11 Mar 2006, at 14:33, Wendy Smoak wrote: I can confirm that it does NOT work ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: native-maven-plugin usage
Oleg, see below to the pom
Here are some main points:
- The provider is aware of /c /Fo /OUT ( output flags)
- I removed /c and /Fo flags,msvc provider is aware of this flag
- I removed /Include . It includes automatically add it since you already
define it in source configuration
- I remove /out flag in linker option, the provider is ware of this flag,
I added /lib to tell linker it is a static lib build
- remove ${basedir}, not needed, maven is aware of this
- you need to use the right envFactory for VS.NET, you have msvc6. What
do you have?
- The NPE is possibibly from empty source element, i will try to produce
and add test cases
- Please check out the source code in SVN for see example
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdcom.bmc.txm.common.transport/groupId
artifactIdtxm-transport-c2j-socket-lib/artifactId
packaginglib/packaging
version1.0-SNAPSHOT/version
nameTXM Transport C Socket Library/name
urlhttp://maven.apache.org/url
dependencies
!-- there is no dependencies - stabdalone static C library --
/dependencies
build
plugins
!--
http://mojo.codehaus.org/maven-native/native-maven-plugin/introduction.html--
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdnative-maven-plugin/artifactId
extensionstrue/extensions
configuration
compilerProvidermsvc/compilerProvider
!-- setup compiler/link environment according to msvc 6
vcvars32.bat
--
!-- without this setting, you will need to setup the environment out
side of Maven --
envFactoryNameorg.codehaus.mojo.natives.msvc.MSVC6EnvFactory
/envFactoryName
compilerStartOptions
compilerStartOption
/O2 /D WIN32 /D NDEBUG /D _CONSOLE /D _MBCS /FD /EHsc /MD /GS
/W3 /nologo /Wp64 /Zi /TP
/compilerStartOption
/compilerStartOptions
sources
source
directorySrc/directory
fileNames
fileNameAnywareSocket.cpp/fileName
/fileNames
/source
!-- additional include path --
source
directory../Include /directory
/source
linkerStartOptions
linkerStartOption /lib /linkerStartOption
/linkerStartOptions
/configuration
/plugin
/plugins
/build
/project
On 3/12/06, Fraimovich, Oleg [EMAIL PROTECTED] wrote:
Hi Dan,
As far as I understand you are developer of the plug-in. It would be very
kind of to advice me.
I'm Java developer that must to build C++ static library under windows. I
developed it using .NET Visual Studio. While I run maven (see the pom
attached) I get the following output.
Could you please advice what I missed.
Thanks a lot in advance.
P:\p4client\projects\infrastructure\transport\dev\txm-transport-c2j\AnywareSocketmvn
compile
Listening for transport dt_socket at address: 5025
[INFO] Scanning for projects...
[INFO]
[INFO] Building TXM Transport C Socket Library
[INFO]task-segment: [compile]
[INFO]
[INFO] [native:compile]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.codehaus.mojo.natives.compiler.AbstractCCompiler.getCommandLine(
AbstractCCompiler.java:83)
at org.codehaus.mojo.natives.msvc.MSVCCompiler.getCommandLine(
MSVCCompiler.java:73)
at org.codehaus.mojo.natives.compiler.AbstractCompiler.compile(
AbstractCompiler.java:74)
at org.codehaus.mojo.natives.plugin.NativeCompileMojo.execute(
NativeCompileMojo.java:162)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:531)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:47
2)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.jav
a:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:139)
at
Re: Maven 2.0 and j2ee and serious work
Hi Roberto, I don't know what do you mean with the lack of the j2ee support because we are using it for web applications, ejbs, ears, web services,... Regards On 3/11/06, Roberto N Nanamura [EMAIL PROTECTED] wrote: Hi, I use maven 1.1 in my project in Bank of America and it has been very handy. But I reluctant to migrate to Maven 2.0 because of the lack of the j2ee support. It does not matter how nice and wonderful the new features of Maven 2.0 are, at the end of day is how it can support serious work. I can play it around for entertainment but I will stick to Maven 1 until I see a minimum of enterprise level application support in Maven 2.0 (and I am including j2ee and web services in the minimum requirement level). If maven 2 wants to be taken seriously it MUST support j2ee and web services otherwise maven 1.1 will stick for much longer than you expect. Thanks for the good work on maven 1 and I hope maven 2 will improve (at lot - with much better documentation) Roberto N Nanamura -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0 and j2ee and serious work
Same here. I think the documentation is a little bit too fragmented and it intimidated some people, they don't know where to start and they wonder in wich order they should read the documents. Maybe you should provide some *tracks* à la Cocoon. What do you think? On 3/12/06, Carlos Sanchez [EMAIL PROTECTED] wrote: Hi Roberto, I don't know what do you mean with the lack of the j2ee support because we are using it for web applications, ejbs, ears, web services,... Regards On 3/11/06, Roberto N Nanamura [EMAIL PROTECTED] wrote: Hi, I use maven 1.1 in my project in Bank of America and it has been very handy. But I reluctant to migrate to Maven 2.0 because of the lack of the j2ee support. It does not matter how nice and wonderful the new features of Maven 2.0 are, at the end of day is how it can support serious work. I can play it around for entertainment but I will stick to Maven 1 until I see a minimum of enterprise level application support in Maven 2.0 (and I am including j2ee and web services in the minimum requirement level). If maven 2 wants to be taken seriously it MUST support j2ee and web services otherwise maven 1.1 will stick for much longer than you expect. Thanks for the good work on maven 1 and I hope maven 2 will improve (at lot - with much better documentation) Roberto N Nanamura -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] defining new lifecycle / packaging with maven-plugin-tools-ant
Hi, I think what you're looking for is in here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html There's a section there discussing how you can specify a new packaging. -lester [EMAIL PROTECTED] wrote: Hi, some of you might have followed my trials to setup a new project [1]: I'm now trying to work on the first step, which is using the assembly plugin to stuff all generated sources into a zip/jar file. The problem is, that during the build lifecycle I actually only want two plugins to be executed: 1) my custom plugin in the generate-sources phase and 2) the assembly plugin for packaging. How can that be achieved? When I define only those plugins and no packaging, maven defaults to the jar packaging, which is invoking a lot of other unwanted plugins/mojos. I tried to define a new packaging in my plugin for the source code generation, but I don't know how to do that. I was following the giode [2] so far, but there isn't explained how the plexus/components.xml can be integrated, or if it's possible at all. [1] http://www.mail-archive.com/users@maven.apache.org/msg37006.html [2] http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html Thanks for your feedback. Andreas Ebbert-Karroum Software Design Engineer - Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-94123838 Heltorfer Straße 1, 40472 Düsseldorf, Germany This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PROBLEM SOLVED : Line too long error when I try to fork the compiler for jdk1.3
On 3/13/06, Sanjay Choudhary [EMAIL PROTECTED] wrote: javac @options @class other options) Yep, that's how the problem has been solved elsewhere like in Javadoc. Nice work! 1. How can I share my code with maven group, this will enable us to close bug http:/jira/codehaus.org/browse/MCCOMPILER-22? http://maven.apache.org/guides/development/guide-m2-development.html##Creating%20and%20submitting%20a%20patch attach the patch to MCOMPLIER-22 2. How can I share these maven jars with my other team members?(need to do tomorrow morning . I will hate to email them these new versions of jars. Is there a way I can install them in my companies snapshot repository? (This will involve adding distribution entries in POM.xml for both the projects. Is it OK?). Any suggestions/ideas. You've got the right idea here. Change the distributionManagement section of your local POM copies to deploy to your own snapshot repository and run mvn deploy, then have the developers include that repository as their pluginRepository (see http://maven.apache.org/guides/development/guide-testing-development-plugins.html for an example). Thanks, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to add release-info
Hi All I'm using maven2.0.2 when i deploy my artifacts i want to create an xml file called release-info.xml so when these artifacts deployed into server, and when i need to know the deployed version of my artifact i can directly access this xml to see. These xml contains the buildnumber,date,and some other details.. Is this possible with maven build,? is there something maven already does it?, any one has any idea on this , please share
maven for eclipse plug-in project
Hi, As now I'm working on eclipse plug-in project, is there maven 2.0 plug-in for building eclipse plug-in project stead of I build it from eclipse? Thanks a lot. brgds Peter
