Re: [m2] maven does not launch on ubuntu 9.10
Well something else does not work now :(
p...@ubuntu-desktop:~$ mvn validate -e
+ Error stacktraces are turned on.
FATAL ERROR: Unable to start the embedded plexus container
Error stacktrace:
org.codehaus.plexus.PlexusContainerException: Error starting container
at
org.codehaus.plexus.DefaultPlexusContainer.start(DefaultPlexusContainer.java:795)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:220)
at org.codehaus.plexus.embed.Embedder.start(Embedder.java:183)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:177)
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.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentRepositoryException:
Component descriptor role:
'org.sonatype.plexus.components.cipher.PlexusCipher', implementation:
'org.sonatype.plexus.components.cipher.DefaultPlexusCipher', role hint:
'default' has a hint, but there are other implementations that don't
at
org.codehaus.plexus.component.repository.DefaultComponentRepository.addComponentDescriptor(DefaultComponentRepository.java:184)
at
org.codehaus.plexus.DefaultPlexusContainer.addComponentDescriptor(DefaultPlexusContainer.java:515)
at
org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:738)
at
org.codehaus.plexus.DefaultPlexusContainer.start(DefaultPlexusContainer.java:779)
... 12 more
p...@ubuntu-desktop:~$
I will replace all files.
Adrian.
Adrian Herscu wrote:
Solved.
I extracted the
http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-2.2.1-bin.tar.gz/apache-maven-2.2.1/bin/m2.conf
file:
main is org.apache.maven.cli.compat.CompatibleMain from plexus.core
set maven.home default ${user.home}/m2
[plexus.core]
load ${maven.home}/lib/*.jar
and now it works :)
Adrian.
Brett Randall wrote:
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.
Re: [m2] maven does not launch on ubuntu 9.10
Solved.
I extracted the
http://www.apache.org/dyn/closer.cgi/maven/binaries/apache-maven-2.2.1-bin.tar.gz/apache-maven-2.2.1/bin/m2.conf
file:
main is org.apache.maven.cli.compat.CompatibleMain from plexus.core
set maven.home default ${user.home}/m2
[plexus.core]
load ${maven.home}/lib/*.jar
and now it works :)
Adrian.
Brett Randall wrote:
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
-
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
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
[m2] maven does not launch on ubuntu 9.10
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
[m2] multi-project with plugin dependencies fails to build
Hi all, I am trying to set up a multi-project build in which one module depends on the Maven plugin created by other module. So far, the only way I could build the project is by building the Maven plugin module and then activate the multi-project build. Is there any possibility to define the plugin dependency? Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [m2.2.1] BUILD ERROR -- (attached a test case)
PING! Adrian Herscu wrote: Test case attached in root.7z Adrian. Adrian Herscu wrote: Hi all, I have the following multi-project structure: root +my-maven-plugin +my-component My component requires my Maven plugin in order to build. Hence it declares: ... org.foo my-maven-plugin 1.0-beta-1-SNAPSHOT true ... After deleting the org/foo hive in my local repository I ran mvn -o validate on the root and got: [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] root [INFO] my-maven-plugin [INFO] my-component [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: System is offline. Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.foo -DartifactId =my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.foo -DartifactId=my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] Shouldn't it build my-maven-plugin before?! 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: [m2.2.1] BUILD ERROR -- (attached a test case)
Test case attached in root.7z Adrian. Adrian Herscu wrote: Hi all, I have the following multi-project structure: root +my-maven-plugin +my-component My component requires my Maven plugin in order to build. Hence it declares: ... org.foo my-maven-plugin 1.0-beta-1-SNAPSHOT true ... After deleting the org/foo hive in my local repository I ran mvn -o validate on the root and got: [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] root [INFO] my-maven-plugin [INFO] my-component [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: System is offline. Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.foo -DartifactId =my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.foo -DartifactId=my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] Shouldn't it build my-maven-plugin before?! Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[m2.2.1] BUILD ERROR -- Plugin could not be found
Hi all, I have the following multi-project structure: root +my-maven-plugin +my-component My component requires my Maven plugin in order to build. Hence it declares: ... org.foo my-maven-plugin 1.0-beta-1-SNAPSHOT true ... After deleting the org/foo hive in my local repository I ran mvn -o validate on the root and got: [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] root [INFO] my-maven-plugin [INFO] my-component [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Plugin could not be found - check that the goal name is correct: System is offline. Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.foo -DartifactId =my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.foo -DartifactId=my-maven-plugin -Dversion=1.0-beta-1-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT org.foo:my-maven-plugin:maven-plugin:1.0-beta-1-SNAPSHOT [INFO] [INFO] For more information, run Maven with the -e switch [INFO] Shouldn't it build my-maven-plugin before?! Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [m2] yet another cyclic dependency issue
Thanks. Stephen Connolly wrote: create a generator-test module for testing the generator 2009/10/1 Adrian Herscu Hi all, (I already read all post regarding cyclic dependencies) My project has two modules: 1) generator -- depends on the "samples" for testing 2) sample -- depends on the "generator" for building I used to unpack the samples artifact into the target directory of the generator before running the generator's test. Any "clean" way out of this cyclic dependency? 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
[m2] yet another cyclic dependency issue
Hi all, (I already read all post regarding cyclic dependencies) My project has two modules: 1) generator -- depends on the "samples" for testing 2) sample -- depends on the "generator" for building I used to unpack the samples artifact into the target directory of the generator before running the generator's test. Any "clean" way out of this cyclic dependency? TIA, Adrian. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn deploy -- CHECKSUM FAILED
Tried that... Didn't work :(
I found that the Maven Snapshots Repository location changed and some
components are not found once I deleted the local repository contents.
Fixed that and now seems to work (I haven't finished the testing).
Thanks for your reply,
Adrian.
Saritha SV wrote:
Try deleting the contents of specified artifact from the repository . Some
metadata xml file must have got corrupted .
Thanks,
Saritha
On Sun, Aug 23, 2009 at 10:02 PM, Adrian Herscu wrote:
Hi all,
I am using Maven 2.2.1 on Sun JDK 1.6.0_16.
When I am running mvn deploy I am getting this output:
Z:\sandbox>mvn deploy -N
[INFO] Scanning for projects...
[INFO]
[INFO] Building wireXN Sandbox
[INFO]task-segment: [deploy]
[INFO]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing Z:\sandbox\pom.xml to C:\Documents and
Settings\pm\.m2\reposit
ory\org\wirexn\sandbox\wirexn-sandbox\1.0-alpha-2-SNAPSHOT\wirexn-sandbox-1.0-al
pha-2-SNAPSHOT.pom
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from snapsh...@wirexn.org
Uploading: sftp://
web.sourceforge.net/home/groups/w/wi/wirexn/htdocs/snapshots/o
rg/wirexn/sandbox/wirexn-sandbox/1.0-alpha-2-SNAPSHOT/wirexn-sandbox-1.0-alpha-2
-SNAPSHOT.pom
[INFO] Retrieving previous metadata from snapsh...@wirexn.org
[INFO] Uploading repository metadata for: 'snapshot
org.wirexn.sandbox:wirexn-sa
ndbox:1.0-alpha-2-SNAPSHOT'
[INFO] Retrieving previous metadata from snapsh...@wirexn.org
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'da39a3ee5e
6b4b0d3255bfef95601890afd80709'; remote =
'a19397abb9b9ce5f3735dfc626a8699dff573
1e3' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'da39a3ee5e
6b4b0d3255bfef95601890afd80709'; remote =
'a19397abb9b9ce5f3735dfc626a8699dff573
1e3' - IGNORING
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Error installing metadata:
Error up
dating group repository metadata
input contained no data
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 minute 55 seconds
[INFO] Finished at: Sun Aug 23 19:27:58 IDT 2009
[INFO] Final Memory: 10M/19M
[INFO]
Tried to do mvn dependency:purge-local-repository -- didn't help :(
What else should I check?
Thanks,
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
mvn deploy -- CHECKSUM FAILED
Hi all,
I am using Maven 2.2.1 on Sun JDK 1.6.0_16.
When I am running mvn deploy I am getting this output:
Z:\sandbox>mvn deploy -N
[INFO] Scanning for projects...
[INFO]
[INFO] Building wireXN Sandbox
[INFO]task-segment: [deploy]
[INFO]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing Z:\sandbox\pom.xml to C:\Documents and
Settings\pm\.m2\reposit
ory\org\wirexn\sandbox\wirexn-sandbox\1.0-alpha-2-SNAPSHOT\wirexn-sandbox-1.0-al
pha-2-SNAPSHOT.pom
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from snapsh...@wirexn.org
Uploading:
sftp://web.sourceforge.net/home/groups/w/wi/wirexn/htdocs/snapshots/o
rg/wirexn/sandbox/wirexn-sandbox/1.0-alpha-2-SNAPSHOT/wirexn-sandbox-1.0-alpha-2
-SNAPSHOT.pom
[INFO] Retrieving previous metadata from snapsh...@wirexn.org
[INFO] Uploading repository metadata for: 'snapshot
org.wirexn.sandbox:wirexn-sa
ndbox:1.0-alpha-2-SNAPSHOT'
[INFO] Retrieving previous metadata from snapsh...@wirexn.org
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'da39a3ee5e
6b4b0d3255bfef95601890afd80709'; remote =
'a19397abb9b9ce5f3735dfc626a8699dff573
1e3' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'da39a3ee5e
6b4b0d3255bfef95601890afd80709'; remote =
'a19397abb9b9ce5f3735dfc626a8699dff573
1e3' - IGNORING
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Error installing metadata:
Error up
dating group repository metadata
input contained no data
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 minute 55 seconds
[INFO] Finished at: Sun Aug 23 19:27:58 IDT 2009
[INFO] Final Memory: 10M/19M
[INFO]
Tried to do mvn dependency:purge-local-repository -- didn't help :(
What else should I check?
Thanks,
Adrian.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[m2] mvn install fails because of connection errors
Hi all, During mvn install builds, there is a frequent connection error: Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/system-serialization/trunk' svn: PROPFIND of '/system-serialization/trunk': could not connect to server (https://svn.wirexn.net) --- In this case the build is flagged as BUILD ERROR. Is it possible to make it retry the connection? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] deploying a multi-module project fails because of communication errors
Hi all, I have a multi-module project project which is built nightly by Continuum with the deploy goal. Most of the time the build fails because of communication errors, such as: [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from [EMAIL PROTECTED] Uploading: https://webdav.wirexn.net:443/snapshots/org/wirexn/sandbox/wsguiweb/wirexn-wsgui-web/1.0-alpha-1-SNAPSHOT/wirexn-wsgui-web-1.0-alpha-1-SNAPSHOT.war Nov 3, 2008 3:24:19 AM org.apache.commons.httpclient.HttpMethodBase processRequest INFO: Recoverable exception caught when processing request org.apache.commons.httpclient.HttpException: Unbuffered entity enclosing request can not be repeated. at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:436) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2316) at org.apache.commons.httpclient.HttpMethodBase.processRequest(HttpMethodBase.java:2651) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1087) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:643) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497) at org.apache.maven.wagon.providers.webdav.CorrectedWebdavResource.putMethod(CorrectedWebdavResource.java:156) at org.apache.maven.wagon.providers.webdav.WebDavWagon.put(WebDavWagon.java:287) at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244) at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80) at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.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) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: PUT request for: org/wirexn/sandbox/wsguiweb/wirexn-wsgui-web/1.0-alpha-1-SNAPSHOT/wirexn-wsgui-web-1.0-alpha-1-SNAPSHOT.war to wirexn-wsgui-web-1.0-alpha-1-SNAPSHOT.war failed Unbuffered entity enclosing request can not be repeated. [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from [EMAIL PROTECTED] Uploading: https://webdav.wirexn.net:443/snapshots/org/wirexn/sandbox/sample/swing-client-sample/1.0-alpha-2-SNAPSHOT/swing-client-sample-1.0-alpha-2-SNAPSHOT.jar [INFO] Retrieving previous metadata from [EMAIL PROTECTED] [INFO] Uploading repository metadata for: 'artifact org.wirexn.sandbox.sample:swing-client-sample' [INFO] Uploading project information for swing-client-sample 1.0-alpha-2-SNAPSHOT [INFO] Retrieving previous metadata from [EMAIL PROTECTED] [INFO] Uploading repository metadata for: 'snapshot org.wirexn.sandbox.sample:swing-client-sample:1.0-alpha-2-SNAPSHOT' [INFO] Retrieving previous build number from [EMAIL PROTECTED] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error retrieving previous build number for artifact 'org.wirexn.sandbox.sample:swing-client-sample:jar:jar-with-dependencies': repository metadata for: 'snapshot org.wirexn.s
[2.0.9] connection timed out
Hi all, I have a Continuum nightly schedule that runs a mvn deploy. Sometimes the connection to the remote repository times out and I am getting an error such: [INFO] [deploy:deploy] altDeploymentRepository = null [INFO] Retrieving previous build number from [EMAIL PROTECTED] Uploading: https://webdav.wirexn.net:443/snapshots/org/wirexn/buildsys/ant/bs/wirexn-buildsys-ant-bs/1.0-beta-1-SNAPSHOT/wirexn-buildsys-ant-bs-1.0-beta-1-SNAPSHOT.jar [INFO] Retrieving previous metadata from [EMAIL PROTECTED] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error installing artifact's metadata: repository metadata for: 'snapshot org.wirexn.buildsys.ant.bs:wirexn-buildsys-ant-bs:1.0-beta-1-SNAPSHOT' could not be retrieved from repository: [EMAIL PROTECTED] due to an error: Failed to transfer file: https://webdav.wirexn.net:443/snapshots/org/wirexn/buildsys/ant/bs/wirexn-buildsys-ant-bs/1.0-beta-1-SNAPSHOT/maven-metadata.xml. Return code is: 0 Connection timed out: connect Any way to make it retry? Perhaps, setting a different timeout limit? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] archetype repository requires authentication
Hi Dave, and thanks for the fast reply. I already have a settings.xml and the build works by retrieving artifacts from the repositories defined in it. However, the archetypes are not searched in those repositories only in the central Maven repository :( I don't know why it does not use the settings.xml file to query for additional repositories... Adrian. Dave Newton wrote: --- On Sat, 9/20/08, Adrian Herscu wrote: I have written an archetype and deployed to my remote repository. The repository requires authentication. The problem is when somebody runs mvn archetype:generate ... -DarchetypeRepository=http://my.repo he gets a 401 from the server and generation fails of course. Is there any possibility to supply credentials? This might help, although I haven't tried it :/ http://maven.apache.org/guides/mini/guide-configuring-maven.html See the "Security and Deployment Settings" section; it sounds like the element may do what you want. HTH, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] archetype repository requires authentication
Hi all, I have written an archetype and deployed to my remote repository. The repository requires authentication. The problem is when somebody runs mvn archetype:generate ... -DarchetypeRepository=http://my.repo he gets a 401 from the server and generation fails of course. Is there any possibility to supply credentials? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] is it possible to package a newly archetype-generated project?
Done. http://jira.codehaus.org/browse/ARCHETYPE-205 Raphaël Piéroni wrote: Hi Adrian, This is not currently implemented. Please fill a jira enhancement http://jira.codehaus.org/browse/ARCHETYPE Raphaël 2008/9/17 Adrian Herscu <[EMAIL PROTECTED]>: Hi all, I am integrating some code generator into Maven. Currently, I have a project archetype and a plugin that wraps the generator. In the current arrangement creating a project is a three steps process: 1. mvn archetype:generate 2. cd 3. mvn package/install/whatever I would like to make it a one step process - like: mvn archetype:generate -DrunTo=package Anyone tried something similar? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] is it possible to package a newly archetype-generated project?
Hi all, I am integrating some code generator into Maven. Currently, I have a project archetype and a plugin that wraps the generator. In the current arrangement creating a project is a three steps process: 1. mvn archetype:generate 2. cd 3. mvn package/install/whatever I would like to make it a one step process - like: mvn archetype:generate -DrunTo=package Anyone tried something similar? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] how to change the defaults of a lifecycle-bound plugin
Anyone can help with this? Adrian. Adrian Herscu wrote: Hi all, In my build lifecycle (components.xml) I am using the maven-dependency-plugin. Here is a snippet: org.apache.maven.lifecycle.mapping.LifecycleMapping blah org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping default org.apache.maven.plugins:maven-resources-plugin:resources org.apache.maven.plugins:maven-dependency-plugin::unpack-dependencies, ... Now, I need the org.apache.maven.plugins:maven-dependency-plugin::unpack-dependencies goal to be invoked with different default values. What is the easiest way to achieve this? TIA, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] specifying default properties for my mojo
Hi all,
I have written a mojo using ANT.
In my.mojos.xml I have sections like:
failOnError
failOnError
false
false
${failOnError}
boolean
Indicates whether the build will continue even
if there are compilation errors; defaults to true.
The problem is within the ${failOnError}
line. It works correctly as long as the user specifies failOnError on
the command line, i.e.: mvn -DfailOnError=true ... or mvn
-DfailOnError=false ...
I alse tried to specify true but then the
user cannot change the value through the command line :(
I would like to define a default value for the failOnError property
somewhere, but still let the user change that value through the command
line. How can achieve this?
TIA,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] how to change the defaults of a lifecycle-bound plugin
Hi all, In my build lifecycle (components.xml) I am using the maven-dependency-plugin. Here is a snippet: org.apache.maven.lifecycle.mapping.LifecycleMapping blah org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping default org.apache.maven.plugins:maven-resources-plugin:resources org.apache.maven.plugins:maven-dependency-plugin::unpack-dependencies, ... Now, I need the org.apache.maven.plugins:maven-dependency-plugin::unpack-dependencies goal to be invoked with different default values. What is the easiest way to achieve this? TIA, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] the maven-release-plugin alters the eol style of cdata sections
This "solution" causes other problem with subversion -- the error message look like this: svn: Can't move access is denied I couldn't make it work, even on a clean working copy with minimum running processes (search, anti-virus, tortoisesvn). The only remedy was to comment out the CDATA section :( Any suggestions? Adrian Herscu wrote: Hi all, Spent an hour or so to discover why subversion fails to commit the pom.xml during a release:prepare... If the pom.xml file contains CDATA sections (as required by few plugins, such as the maven-eclipse-plugin), then the end of line sequence of these lines is changed to LF. The only solution I have found is to change the svn:eol-style of the pom.xml to LF. Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] the maven-release-plugin alters the eol style of cdata sections
Hi all, Spent an hour or so to discover why subversion fails to commit the pom.xml during a release:prepare... If the pom.xml file contains CDATA sections (as required by few plugins, such as the maven-eclipse-plugin), then the end of line sequence of these lines is changed to LF. The only solution I have found is to change the svn:eol-style of the pom.xml to LF. Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] how to set log4j system properties for the axis2 maven plugin
Hi all,
I know that questions regarding setting log4j and system properties were
asked many times, however I could not find anything that works for me.
I am trying to make the axis2 plugin run during my build, and I am
getting this error:
[INFO] [axis2-wsdl2code:wsdl2code {execution: default}]
log4j:WARN No appenders could be found for logger
(org.apache.axis2.i18n.Project
ResourceBundle).
log4j:WARN Please initialize the log4j system properly.
java.io.FileNotFoundException:
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at java.io.FileInputStream.(FileInputStream.java:66)
at
org.apache.axis2.wsdl.codegen.CodegenConfigLoader.loadConfig(CodegenC
onfigLoader.java:161)
at
org.apache.axis2.wsdl.codegen.CodeGenConfiguration.(CodeGenConf
iguration.java:371)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
ionEngine.java:85)
at
org.apache.axis2.maven2.wsdl2code.WSDL2CodeMojo.execute(WSDL2CodeMojo
.java:396)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error parsing WSDL
The only way to make enable log4j logging was to invoke Maven with:
mvn -Dlog4j.configuration=file:///C:\my-log4j.properties
I tried to put that property in the settings.xml and in the pom.xml with
no success.
What is the correct way to specify Java system properties not using the
-D command line parameter?
TIA,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] compiling a generic method with maven fails
VUB Stefan Seidel wrote: Now, I discovered that under Maven 2 with the following maven-compiler-plugin configuration: 1.6 1.6 Add true Stefan Why should that work? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] compiling a generic method with maven fails
Checked the eclipse.tools.jdt newsgroup; seems that there are many more
inconsistencies like these between the JDT compiler and javac, all of
those which I saw are regarded to generics.
Adrian.
P.S. And there is no switch in Eclipse to make it compile with javac,
except making it create and ANT build file.
Adrian Herscu wrote:
I thought about this... Problem is, that there are more than ten
dependencies and the sources are stored into three different
directories... Configuring javac for this, seems like a nightmare!
I have changed the return type of the method from V to AbstractView,
added a cast to V somewhere, and that solved the problem with Maven.
Knew that these generics are more trouble than worth!
Is there some switch in Eclipse to make it compile with javac?
Wayne Fay wrote:
Can you try compiling with the Sun JDK 1.6 directly eg javac ...?
Wayne
On 3/5/08, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I have this generic method which compiles fine under Eclipse 3.3:
public abstract class AbstractApplication {
...
private V getViewFor(final Class viewClass) {
class InternalRunnable
implements Runnable {
private V frame;
public void run() {
try {
frame = viewClass.newInstance();
frame
.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setVisible(true);
} catch (final InstantiationException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (final IllegalAccessException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
...
}
And the code runs OK on the Sun JRE 6.0.
Now, I discovered that under Maven 2 with the following
maven-compiler-plugin configuration:
1.6
1.6
the build fails with the following compilation error:
[INFO] Compilation failure
C:\documents\pm\project-trunks\wirexn\sandbox\swing-client-sample\src\main\java\
org\wirexn\sandbox\wsgui\AbstractApplication.java:[103,23] incompatible
types
found : org.wirexn.sandbox.wsgui.view.AbstractView
required: V
C:\documents\pm\project-trunks\wirexn\sandbox\swing-client-sample\src\main\java\
org\wirexn\sandbox\wsgui\AbstractApplication.java:[103,23] incompatible
types
found : org.wirexn.sandbox.wsgui.view.AbstractView
required: V
Any suggestions?
Thanks in advance,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] compiling a generic method with maven fails
I thought about this... Problem is, that there are more than ten
dependencies and the sources are stored into three different
directories... Configuring javac for this, seems like a nightmare!
I have changed the return type of the method from V to AbstractView,
added a cast to V somewhere, and that solved the problem with Maven.
Knew that these generics are more trouble than worth!
Is there some switch in Eclipse to make it compile with javac?
Wayne Fay wrote:
Can you try compiling with the Sun JDK 1.6 directly eg javac ...?
Wayne
On 3/5/08, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I have this generic method which compiles fine under Eclipse 3.3:
public abstract class AbstractApplication {
...
private V getViewFor(final Class viewClass) {
class InternalRunnable
implements Runnable {
private V frame;
public void run() {
try {
frame = viewClass.newInstance();
frame
.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setVisible(true);
} catch (final InstantiationException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (final IllegalAccessException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
...
}
And the code runs OK on the Sun JRE 6.0.
Now, I discovered that under Maven 2 with the following
maven-compiler-plugin configuration:
1.6
1.6
the build fails with the following compilation error:
[INFO] Compilation failure
C:\documents\pm\project-trunks\wirexn\sandbox\swing-client-sample\src\main\java\
org\wirexn\sandbox\wsgui\AbstractApplication.java:[103,23] incompatible
types
found : org.wirexn.sandbox.wsgui.view.AbstractView
required: V
C:\documents\pm\project-trunks\wirexn\sandbox\swing-client-sample\src\main\java\
org\wirexn\sandbox\wsgui\AbstractApplication.java:[103,23] incompatible
types
found : org.wirexn.sandbox.wsgui.view.AbstractView
required: V
Any suggestions?
Thanks in advance,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] compiling a generic method with maven fails
Hi all,
I have this generic method which compiles fine under Eclipse 3.3:
public abstract class AbstractApplicationextends AbstractView, C extends AbstractControl> {
...
private V getViewFor(final Class viewClass) {
class InternalRunnable
implements Runnable {
private V frame;
public void run() {
try {
frame = viewClass.newInstance();
frame
.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setVisible(true);
} catch (final InstantiationException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (final IllegalAccessException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
}
...
}
And the code runs OK on the Sun JRE 6.0.
Now, I discovered that under Maven 2 with the following
maven-compiler-plugin configuration:
1.6
1.6
the build fails with the following compilation error:
[INFO] Compilation failure
C:\documents\pm\project-trunks\wirexn\sandbox\swing-client-sample\src\main\java\
org\wirexn\sandbox\wsgui\AbstractApplication.java:[103,23] incompatible
types
found : org.wirexn.sandbox.wsgui.view.AbstractView
required: V
C:\documents\pm\project-trunks\wirexn\sandbox\swing-client-sample\src\main\java\
org\wirexn\sandbox\wsgui\AbstractApplication.java:[103,23] incompatible
types
found : org.wirexn.sandbox.wsgui.view.AbstractView
required: V
Any suggestions?
Thanks in advance,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Jetty 6 Plugin does not recognize custom webapp source directory
Hi, What if I have an additional webapp source folder, like: org.apache.maven.plugins maven-war-plugin src-gen/main/webapp How can I tell Jetty to deploy this folder as well? TIA, Adrian. Brett Porter wrote: Hi Matt, Check out the Jetty docs: http://jetty.mortbay.org/jetty6/maven-plugin/howto.html You can configure the web resources path. Unfortunately, we haven't enabled a mechanism for the war plugin to share its configuration. - Brett On 1/11/06, Matt Raible <[EMAIL PROTECTED]> wrote: I decided to try Brett's Jetty 6 HowTo this morning: http://blogs.codehaus.org/people/brett/archives/001306_developing_with_jetty_where_have_you_been_all_my_life.html Unfortunately, it doesn't seem to work with my custom webapp source directory. Here's my pom.xml: maven-war-plugin web org.mortbay.jetty maven-jetty6-plugin 10 / [INFO] [jetty6:run] [INFO] Configuring Jetty for project: Equinox [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] Webapp source directory C:\Source\equinox\src\main\webapp does not exist [INFO] - --- [INFO] For more information, run Maven with the -e switch [INFO] - --- [INFO] Total time: 3 minutes 25 seconds [INFO] Finished at: Tue Jan 10 07:40:45 MST 2006 [INFO] Final Memory: 4M/8M [INFO] - Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
Hi Nicolas, How do I specify a different source directory? I have looked into the sources and found this: http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/javascript-maven-plugin/src/main/java/org/codehaus/mojo/javascript/CompileMojo.java Tried the my/source/directory under the build section and got this: [INFO] [INFO] basedir C:\documents\pm\project-trunks\wirexn\sandbox\extjs-client-sample \src\main\javascript does not exist [INFO] [INFO] Trace java.lang.IllegalStateException: basedir C:\documents\pm\project-trunks\wirexn\s andbox\extjs-client-sample\src\main\javascript does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java: 542) at org.codehaus.mojo.javascript.CompileMojo.execute(CompileMojo.java:130 ) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.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) Adrian. nicolas de loof wrote: The war-package process source scripts and place them in the packaging folder used by the war plugin to create the exploded war, before archivaing a .war. Nico 2008/2/26, Adrian Herscu <[EMAIL PROTECTED]>: Harlan, thanks for your fast reply. It works! However, I am not sure what the war-package does (as in the example here: http://mojo.codehaus.org/javascript-maven-tools/guide-webapp-development.html ) Adrian. Harlan Iverson wrote: The javascript plugin is currently sandboxed, so following these instructions should make it available: http://mojo.codehaus.org/using-sandbox-plugins.html The other option is to download the source and run mvn install locally. The location in the plugin's maven site is wrong, it is here: http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/ You'll need to check out the top level, as the plugin depends on other modules. Good luck. Harlan On Mon, Feb 25, 2008 at 12:40 PM, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, In which repository is this plugin hosted? I am getting: Missing: -- 1) org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.mojo.javascript -Dartifact Id=javascript-maven-plugin \ -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.javascript -DartifactId=j avascript-maven-plugin \ -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-S NAPSHOT 2) org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1- SNAPSHOT -- 1 required artifact is missing. for artifact: org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-SNAPSHOT from the specified remote repositories: [EMAIL PROTECTED] (http://webdav.wirexn.net/snapshots), central (http://repo1.maven.org/maven2), wirexn.net (http://webdav.wirexn.net/repository) TIA, Adrian. nicolas de loof wrote: You can look at
Re: Javascript support
Harlan, thanks for your fast reply. It works! However, I am not sure what the war-package does (as in the example here: http://mojo.codehaus.org/javascript-maven-tools/guide-webapp-development.html) Adrian. Harlan Iverson wrote: The javascript plugin is currently sandboxed, so following these instructions should make it available: http://mojo.codehaus.org/using-sandbox-plugins.html The other option is to download the source and run mvn install locally. The location in the plugin's maven site is wrong, it is here: http://svn.codehaus.org/mojo/trunk/sandbox/javascript-maven-tools/ You'll need to check out the top level, as the plugin depends on other modules. Good luck. Harlan On Mon, Feb 25, 2008 at 12:40 PM, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, In which repository is this plugin hosted? I am getting: Missing: -- 1) org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.mojo.javascript -Dartifact Id=javascript-maven-plugin \ -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.javascript -DartifactId=j avascript-maven-plugin \ -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-S NAPSHOT 2) org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1- SNAPSHOT -- 1 required artifact is missing. for artifact: org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-SNAPSHOT from the specified remote repositories: [EMAIL PROTECTED] (http://webdav.wirexn.net/snapshots), central (http://repo1.maven.org/maven2), wirexn.net (http://webdav.wirexn.net/repository) TIA, Adrian. nicolas de loof wrote: You can look at the jslint report that will check for some structural rules ( http://mojo.codehaus.org/javascript-maven-tools/javascript-report-maven-plugin/index.html ) Not sure, but syntactic errors should be detected also. 2008/2/18, Insitu <[EMAIL PROTECTED]>: Hello, I would like to know what is the current status/plans of the various javascript handling plugins out there. Few months ago there has been some discussions on this topic and some talks about merging projects. I am currently using jstools plugin, with jsunit for test execution, and would like to know if someone has done work on "verifying" or "compiling" the javascript, using eg. Rhino or other parser to ensure syntactic correctness of javascript. Regards, -- Arnaud Bailly, PhD OQube - Software Engineering http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Javascript support
Hi all, In which repository is this plugin hosted? I am getting: Missing: -- 1) org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.mojo.javascript -Dartifact Id=javascript-maven-plugin \ -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.codehaus.mojo.javascript -DartifactId=j avascript-maven-plugin \ -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-S NAPSHOT 2) org.codehaus.mojo.javascript:javascript-maven-plugin:jar:1.0-alpha-1- SNAPSHOT -- 1 required artifact is missing. for artifact: org.wirexn.sandbox.extjs:extjs-client-sample:javascript:1.0-alpha-1-SNAPSHOT from the specified remote repositories: [EMAIL PROTECTED] (http://webdav.wirexn.net/snapshots), central (http://repo1.maven.org/maven2), wirexn.net (http://webdav.wirexn.net/repository) TIA, Adrian. nicolas de loof wrote: You can look at the jslint report that will check for some structural rules ( http://mojo.codehaus.org/javascript-maven-tools/javascript-report-maven-plugin/index.html ) Not sure, but syntactic errors should be detected also. 2008/2/18, Insitu <[EMAIL PROTECTED]>: Hello, I would like to know what is the current status/plans of the various javascript handling plugins out there. Few months ago there has been some discussions on this topic and some talks about merging projects. I am currently using jstools plugin, with jsunit for test execution, and would like to know if someone has done work on "verifying" or "compiling" the javascript, using eg. Rhino or other parser to ensure syntactic correctness of javascript. Regards, -- Arnaud Bailly, PhD OQube - Software Engineering http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] how to download a single file
Hi all, I am trying to set up a build for an Axis2-based WebService client. The axis2-wsdl2code-maven-plugin works only for local WSDL files, so the next thing I want to do is to configure Maven to download the remote WSDL file before executing the wsdl2code goal. Is there any Maven plugin I can use for this task? Or, should I use an ant task? TIA, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] how to set log4j system properties for the axis2 maven plugin
Hi all,
I know that questions regarding setting log4j and system properties were
asked many times, however I could not find anything that works for me.
I am trying to make the axis2 plugin run during my build, and I am
getting this error:
[INFO] [axis2-wsdl2code:wsdl2code {execution: default}]
log4j:WARN No appenders could be found for logger
(org.apache.axis2.i18n.Project
ResourceBundle).
log4j:WARN Please initialize the log4j system properly.
java.io.FileNotFoundException:
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.(FileInputStream.java:106)
at java.io.FileInputStream.(FileInputStream.java:66)
at
org.apache.axis2.wsdl.codegen.CodegenConfigLoader.loadConfig(CodegenC
onfigLoader.java:161)
at
org.apache.axis2.wsdl.codegen.CodeGenConfiguration.(CodeGenConf
iguration.java:371)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat
ionEngine.java:85)
at
org.apache.axis2.maven2.wsdl2code.WSDL2CodeMojo.execute(WSDL2CodeMojo
.java:396)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error parsing WSDL
The only way to make enable log4j logging was to invoke Maven with:
mvn -Dlog4j.configuration=file:///C:\my-log4j.properties
I tried to put that property in the settings.xml and in the pom.xml with
no success.
What is the correct way to specify Java system properties not using the
-D command line parameter?
TIA,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] how to make my custom packaging recognized by the eclipse plugin?
Hi all, I am using Maven 2 to build projects based on my own framework. Because the framework requires different tools and dependency resolving mechanism, I had to create a dedicated lifecycle. Now I am thinking about some way to integrate the build of my framework with the build of a Java-based Web application. The first thing I have tried was to generate the Eclipse project descriptors and noticed that the .classpath file is not generated. There was a similar issue with the PDE projects which are packaged as ZIP-s (I found that this has been fixed in MECLIPSE-279). I believe that if I will add all the WAR's lifecycle goals to my custom lifecycle then the build artifact created will be indistinguishable from that created by the WAR packaging. Is it true? Is there any way to make the Eclipse plugin "believe" that some custom packaging type is a "Java" type? Thanks, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] is it possible to clean the target site deployment directory?
Hi all, During the deployment of a Maven generated site the old site is still in place. Is it possible to configure Maven to delete the old site before the deployment of the new one? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Replacement for Ant's FixCRLF
Have you found some example? Trevor Torrez wrote: As noted at the end of the antrun plugins' usage page (http://maven.apache.org/plugins/maven-antrun-plugin/usage.html) the resources plugin can be used in lieu of Ant's FixCRLF task. Any example on how to do this when the build takes place on a windows continuous build server and the assembly deployment is to a unix machine (requiring unix line endings for the shell scripts)? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] SSL certificate name does not match
Perhaps sometime, someone will want to add a switch that turns off host
name verification. This seems to be supported in the HttpClient 4.0 API.
Any comments?
Adrian Herscu wrote:
Hi David,
Thanks for your reply.
I checked that blog; however the solution described there seems to
belong to other problem:
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
[This happens] when trying to open an SSL connection to a host using
JSSE. What this usually means is that the server is using a test
certificate (possibly generated using keytool) rather than a certificate
from a well known commercial Certification Authority such as Verisign or
GoDaddy. Web browsers display warning dialogs in this case, but since
JSSE cannot assume an interactive user is present it just throws an
exception by default.
Because I am somewhat desperate, I have tested that program. It seems to
do what the standard keytool does... I copied the generated jssecacert
file into my ${jre.home}/lib/security directory and hoped for the
best... But it didn't happen :-( I checked that the file was read using
a file monitor, and it was read.
It seems that the solution could only be provided by applications (
http://java.sun.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#ciphersuitechoice).
In this case, Maven should provide the option to override the default
host name checking algorithm with a do-nothing one.
Adrian.
David Williams wrote:
Sorry it was late when I replied. = ) Here's the link
http://blogs.sun.com/andreas/entry/no_more_unable_to_find
On 10/11/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Yeah... Where is the link :-)?
I tried to play with the keytool program. I have imported the SSL
certificate into my key store; this creates a file named .keystore in
C:\Documents and Settings\me. I tried to run Maven and DAVExplorer;
their behavior did not change :-(
Now the weird things:
1. I have monitored the file access to the .keystore file. When I am
running keytool -list the .keystore file is accessed (seems like my file
monitoring program works). When I am running Maven or DAVExplorer, the
.keystore file is not accessed at all!
2. Maven is able to upload files to my WebDAV server! If I am building
all my modules locally, then I can run mvn deploy and the files are
uploaded!!!
Adrian.
Tim Kettler wrote:
Where's the link :-)?
David Williams schrieb:
Adrian,
This link may help you. This java program allows you to manually
accept the
cert and place the generated file in your JDK or JRE. Then the java
keeps
it as an accept cert. I have not tried this with Maven but it worked
with
another application where the cert didn't match the server name. Down
side
is that it would have to be on every user's machine.
Thanks,
David
On 10/10/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am hosting my project sources and binaries with some external
provider. He cannot set up an SSL certificate for my domain name...
Meanwhile, the only alternative is accept those SSL warnings about
domain name mismatch. I am getting them in my browser and also in my
SVN
client.
Now I am trying to set up Maven to build and deploy my project to
this
provider. The problem is that I am getting these messages from Maven:
[WARNING] repository metadata for: 'snapshot
org.wirexn.build.extensions:wirexn-
build-extensions:1.0-alpha-4-SNAPSHOT' could not be retrieved from
repository: s
[EMAIL PROTECTED] due to an error: Error transferring file
[INFO] Repository '[EMAIL PROTECTED]' will be blacklisted
...and the artifacts cannot be resolved (of course).
I tried to see if this is a JRE specific problem. Downloaded a
Java-based WebDAV client (DAVExplorer), and it fails to connect with
this error message:
javax.net.ssl.SSLException: Name in certificate "his.domain.name"
does
not match host name " my.domain.name"
Anyone knows about a hidden switch/option/configuration file to make
the
JRE accept the SSL connection even if the host name doesn't match to
that on the certificate?
Please help,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] SSL certificate name does not match
Hi David,
Thanks for your reply.
I checked that blog; however the solution described there seems to
belong to other problem:
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
[This happens] when trying to open an SSL connection to a host using
JSSE. What this usually means is that the server is using a test
certificate (possibly generated using keytool) rather than a certificate
from a well known commercial Certification Authority such as Verisign or
GoDaddy. Web browsers display warning dialogs in this case, but since
JSSE cannot assume an interactive user is present it just throws an
exception by default.
Because I am somewhat desperate, I have tested that program. It seems to
do what the standard keytool does... I copied the generated jssecacert
file into my ${jre.home}/lib/security directory and hoped for the
best... But it didn't happen :-( I checked that the file was read using
a file monitor, and it was read.
It seems that the solution could only be provided by applications (
http://java.sun.com/javase/6/docs/technotes/guides/security/jsse/JSSERefGuide.html#ciphersuitechoice).
In this case, Maven should provide the option to override the default
host name checking algorithm with a do-nothing one.
Adrian.
David Williams wrote:
Sorry it was late when I replied. = ) Here's the link
http://blogs.sun.com/andreas/entry/no_more_unable_to_find
On 10/11/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Yeah... Where is the link :-)?
I tried to play with the keytool program. I have imported the SSL
certificate into my key store; this creates a file named .keystore in
C:\Documents and Settings\me. I tried to run Maven and DAVExplorer;
their behavior did not change :-(
Now the weird things:
1. I have monitored the file access to the .keystore file. When I am
running keytool -list the .keystore file is accessed (seems like my file
monitoring program works). When I am running Maven or DAVExplorer, the
.keystore file is not accessed at all!
2. Maven is able to upload files to my WebDAV server! If I am building
all my modules locally, then I can run mvn deploy and the files are
uploaded!!!
Adrian.
Tim Kettler wrote:
Where's the link :-)?
David Williams schrieb:
Adrian,
This link may help you. This java program allows you to manually
accept the
cert and place the generated file in your JDK or JRE. Then the java
keeps
it as an accept cert. I have not tried this with Maven but it worked
with
another application where the cert didn't match the server name. Down
side
is that it would have to be on every user's machine.
Thanks,
David
On 10/10/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am hosting my project sources and binaries with some external
provider. He cannot set up an SSL certificate for my domain name...
Meanwhile, the only alternative is accept those SSL warnings about
domain name mismatch. I am getting them in my browser and also in my
SVN
client.
Now I am trying to set up Maven to build and deploy my project to this
provider. The problem is that I am getting these messages from Maven:
[WARNING] repository metadata for: 'snapshot
org.wirexn.build.extensions:wirexn-
build-extensions:1.0-alpha-4-SNAPSHOT' could not be retrieved from
repository: s
[EMAIL PROTECTED] due to an error: Error transferring file
[INFO] Repository '[EMAIL PROTECTED]' will be blacklisted
...and the artifacts cannot be resolved (of course).
I tried to see if this is a JRE specific problem. Downloaded a
Java-based WebDAV client (DAVExplorer), and it fails to connect with
this error message:
javax.net.ssl.SSLException: Name in certificate "his.domain.name" does
not match host name " my.domain.name"
Anyone knows about a hidden switch/option/configuration file to make
the
JRE accept the SSL connection even if the host name doesn't match to
that on the certificate?
Please help,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] SSL certificate name does not match
Yeah... Where is the link :-)? I tried to play with the keytool program. I have imported the SSL certificate into my key store; this creates a file named .keystore in C:\Documents and Settings\me. I tried to run Maven and DAVExplorer; their behavior did not change :-( Now the weird things: 1. I have monitored the file access to the .keystore file. When I am running keytool -list the .keystore file is accessed (seems like my file monitoring program works). When I am running Maven or DAVExplorer, the .keystore file is not accessed at all! 2. Maven is able to upload files to my WebDAV server! If I am building all my modules locally, then I can run mvn deploy and the files are uploaded!!! Adrian. Tim Kettler wrote: Where's the link :-)? David Williams schrieb: Adrian, This link may help you. This java program allows you to manually accept the cert and place the generated file in your JDK or JRE. Then the java keeps it as an accept cert. I have not tried this with Maven but it worked with another application where the cert didn't match the server name. Down side is that it would have to be on every user's machine. Thanks, David On 10/10/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, I am hosting my project sources and binaries with some external provider. He cannot set up an SSL certificate for my domain name... Meanwhile, the only alternative is accept those SSL warnings about domain name mismatch. I am getting them in my browser and also in my SVN client. Now I am trying to set up Maven to build and deploy my project to this provider. The problem is that I am getting these messages from Maven: [WARNING] repository metadata for: 'snapshot org.wirexn.build.extensions:wirexn- build-extensions:1.0-alpha-4-SNAPSHOT' could not be retrieved from repository: s [EMAIL PROTECTED] due to an error: Error transferring file [INFO] Repository '[EMAIL PROTECTED]' will be blacklisted ...and the artifacts cannot be resolved (of course). I tried to see if this is a JRE specific problem. Downloaded a Java-based WebDAV client (DAVExplorer), and it fails to connect with this error message: javax.net.ssl.SSLException: Name in certificate "his.domain.name" does not match host name "my.domain.name" Anyone knows about a hidden switch/option/configuration file to make the JRE accept the SSL connection even if the host name doesn't match to that on the certificate? Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] SSL certificate name does not match
Hi all, I am hosting my project sources and binaries with some external provider. He cannot set up an SSL certificate for my domain name... Meanwhile, the only alternative is accept those SSL warnings about domain name mismatch. I am getting them in my browser and also in my SVN client. Now I am trying to set up Maven to build and deploy my project to this provider. The problem is that I am getting these messages from Maven: [WARNING] repository metadata for: 'snapshot org.wirexn.build.extensions:wirexn- build-extensions:1.0-alpha-4-SNAPSHOT' could not be retrieved from repository: s [EMAIL PROTECTED] due to an error: Error transferring file [INFO] Repository '[EMAIL PROTECTED]' will be blacklisted ...and the artifacts cannot be resolved (of course). I tried to see if this is a JRE specific problem. Downloaded a Java-based WebDAV client (DAVExplorer), and it fails to connect with this error message: javax.net.ssl.SSLException: Name in certificate "his.domain.name" does not match host name "my.domain.name" Anyone knows about a hidden switch/option/configuration file to make the JRE accept the SSL connection even if the host name doesn't match to that on the certificate? Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] anyone tried to run Eclipse plugin test with pde:test?
Yes. I have managed to tell the compiler to skip the tests classes and this way to make the build "succeed". After playing with it few hours I understood that I must supply a test.xml file (though I still don't know how to invoke the test through). But even, if I will supply such test.xml it will not run because the compiler can't compile the tests. I still do not understand why the maven compiler and surefire plugins are called... If I have to supply my own test.xml file then I can do there whatever I need, including compilation and of course testing! Adrian. Dan Tran wrote: is this related to pde-maven-plugin? -D On 6/13/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, I have my tests in a src/test/java folder and launching them from the IDE works just fine. Tried to run them using maven install and the compiler cannot find the application classes (from src/main/java) :-( Tried to move the test classes into src/main/java just to make them compile and got this: [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] No tests to run. [INFO] [pde:test] [INFO] [install:install] ...still no tests are run :-( Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] anyone tried to run Eclipse plugin test with pde:test?
Hi all, I have my tests in a src/test/java folder and launching them from the IDE works just fine. Tried to run them using maven install and the compiler cannot find the application classes (from src/main/java) :-( Tried to move the test classes into src/main/java just to make them compile and got this: [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] No tests to run. [INFO] [pde:test] [INFO] [install:install] ...still no tests are run :-( Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin and PDE: do dependencies work?
Hi Graham, "Upgraded" to 2.4-SNAPSHOT solved the missing .classpath issue :-) Besides the .classpath issue, the eclipse:eclipse also does some bad changes to the OSGI manifest file. It tries to "guess" the right bundle name from the maven artifactId and version, but it gets it wrong (labels are not accepted in OSGI bundle versions). I think that maven-eclipse-plugin is a small issue... The big one is pde-maven-plugin. I have managed to make it build my empty eclipse feature and plugins, but now when I need to add dependencies to these plugins it does not add those dependencies to the compile classpath. Any suggestions? Thanks, Adrian. Graham Leggett wrote: On Mon, June 11, 2007 5:45 pm, Adrian Herscu wrote: I have a similar problem... Added a dependency to my PDE project run mvn eclipse:clean eclipse:eclipse and only the .project file is generated (without those linkedResources!). The .classpath file is not generated at all!!! Moreover, running mvn install on the project fails because the dependency is not in the classpath :-( This is a separate problem, fixed in http://jira.codehaus.org/browse/MECLIPSE-279. I am trying to get the maven-eclipse-plugin to a state where it a) works and is b) documented, but this is turning out to be a bit of a nightmare. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-eclipse-plugin and PDE: do dependencies work?
Hi, I have a similar problem... Added a dependency to my PDE project run mvn eclipse:clean eclipse:eclipse and only the .project file is generated (without those linkedResources!). The .classpath file is not generated at all!!! Moreover, running mvn install on the project fails because the dependency is not in the classpath :-( Adrian. Graham Leggett wrote: Hi all, I have been having an interesting time trying to get some eclipse plugin code built with maven, and I would like to check whether a number of assumptions made by maven-eclipse-plugin are still valid against modern copies of Eclipse. When maven-eclipse-plugin creates the .project file, entries such as the following are created to refer to jar dependencies: abbot-0.13.0.jar 1 C:/[path]/.m2/repository/abbot/abbot/0.13.0/abbot-0.13.0.jar ... When an attempt is made to build code using the eclipse IDE, the classpath is picked up correctly, and code that depends on these linked dependencies builds and runs correctly. However: As soon as an attempt is made to export the plugin using the Eclipse export plugin wizard, these linked dependencies are ignored. The linked dependencies do not show up in the final plugin build, the log of the plugin export process is full of java compile errors about missing packages caused by these missing jars. So, the question is: Does the "link" method as shown above still work in Eclipse v3.2.x, and is maven-eclipse-plugin producing a bogus .project file? Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] cyclic dependency created by build plugin?!
Hi all, I have four projects: 0) root -- contains lang, lang-comp and maven-lang-plugin 1) lang -- contains a sample project written in the language "lang" depends on nothing but requires maven-lang-plugin to build 2) lang-comp -- contains a "lang" compiler depends on lang for testing 3) maven-lang-plugin -- contains a maven plugin for the "lang" compiler depends on lang-comp Trying to mvn install the root leads to a cyclic dependency error stating something like this: lang-comp --> lang --> maven-lang-plugin --> lang-comp. Why? (I think it should not because: 1) the dependency of lang-comp on lang is for testing only; 2) lang depends on maven-lang-plugin only for build) Any way out?... Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] pde-maven-plugin fails during release
Another interesting discovery... Checked out the project in a different
directory with a different depth, did a mvn package and the build.xml
file was updated according to the new directory depth. Why it does not
happen during the release:perform build?!
Anyway, I have found a temporary solution by adding this to my pom/build
section:
org.apache.maven.plugins
maven-release-plugin
${basedir}/../${groupId}-checkout
Adrian.
Adrian Herscu wrote:
I am aware about there are some badly coded Java programs that cannot
deal with spaces in Windoze paths... Therefore I am using only the short
DOS notation (PROGRA~1 instead of "Program Files").
I have only one feature -- its pom.xml is appended below.
I moved the checkout directory from ./${basedir}/target to . (so it is
now at the same depth as ${basedir}). Did a mvn package and the build
succeeds! My conclusion, is that the problem arises from those relative
paths in the build.xml file below.
Adrian.
Here is the feature's pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.acme.lang.eclipse
acme-lang-eclipse
1.0-alpha-1
com.acme.lang.eclipse.feature
acme-lang-eclipse-feature
1.0-alpha-1-SNAPSHOT
zip
acme Language Feature for Eclipse
Integrates acme projects into the Eclipse IDE.
scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
hosted-projects.com
Central acme Repository
https://someserver.com:443/dav/acme/repository
true
false
[EMAIL PROTECTED]
Central acme Repository
https://someserver.com:443/dav/acme/snapshots
false
true
org.codehaus.mojo
pde-maven-plugin
true
${eclipse.home}
org.apache.maven.plugins
maven-eclipse-plugin
true
org.eclipse.pde.FeatureNature
org.eclipse.pde.FeatureBuilder
Dan Tran wrote:
how many features you do you have? could you post the pom on for the
feature?
I see you are using Program Files on your path , this make me nervous,
even
thou it should work :-)
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.ui_3.2.0.I20060605-
1400.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
> and you have no problem during normal build?
>
> what does your projects structure look like?
>
> -D
>
>
> On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
>>
>> Hi all,
>>
>> I am trying to release my Eclipse plugins and I am getting lots of
"The
>> import some.eclipse.package cannot be resolved" compilation errors
>> during the release:perform goal.
>>
>> I have tried to run mvn package on the target/checkout directory
and I
>> am getting the same errors... It seems that the build.xml file cannot
be
>> run outside of the ${basedir} directory...
>>
>> Any workaround for this situation?
>> How
Re: [m2] pde-maven-plugin fails during release
I am aware about there are some badly coded Java programs that cannot
deal with spaces in Windoze paths... Therefore I am using only the short
DOS notation (PROGRA~1 instead of "Program Files").
I have only one feature -- its pom.xml is appended below.
I moved the checkout directory from ./${basedir}/target to . (so it is
now at the same depth as ${basedir}). Did a mvn package and the build
succeeds! My conclusion, is that the problem arises from those relative
paths in the build.xml file below.
Adrian.
Here is the feature's pom.xml:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.acme.lang.eclipse
acme-lang-eclipse
1.0-alpha-1
com.acme.lang.eclipse.feature
acme-lang-eclipse-feature
1.0-alpha-1-SNAPSHOT
zip
acme Language Feature for Eclipse
Integrates acme projects into the Eclipse IDE.
scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
hosted-projects.com
Central acme Repository
https://someserver.com:443/dav/acme/repository
true
false
[EMAIL PROTECTED]
Central acme Repository
https://someserver.com:443/dav/acme/snapshots
false
true
org.codehaus.mojo
pde-maven-plugin
true
${eclipse.home}
org.apache.maven.plugins
maven-eclipse-plugin
true
org.eclipse.pde.FeatureNature
org.eclipse.pde.FeatureBuilder
Dan Tran wrote:
how many features you do you have? could you post the pom on for the
feature?
I see you are using Program Files on your path , this make me nervous, even
thou it should work :-)
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.ui_3.2.0.I20060605-
1400.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
> and you have no problem during normal build?
>
> what does your projects structure look like?
>
> -D
>
>
> On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
>>
>> Hi all,
>>
>> I am trying to release my Eclipse plugins and I am getting lots of
"The
>> import some.eclipse.package cannot be resolved" compilation errors
>> during the release:perform goal.
>>
>> I have tried to run mvn package on the target/checkout directory and I
>> am getting the same errors... It seems that the build.xml file cannot
be
>> run outside of the ${basedir} directory...
>>
>> Any workaround for this situation?
>> How about tweaking the release:perform goal?
>>
>> Adrian.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] pde-maven-plugin fails during release
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.ui_3.2.0.I20060605-1400.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
and you have no problem during normal build?
what does your projects structure look like?
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
during the release:perform goal.
I have tried to run mvn package on the target/checkout directory and I
am getting the same errors... It seems that the build.xml file cannot be
run outside of the ${basedir} directory...
Any workaround for this situation?
How about tweaking the release:perform goal?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] pde-maven-plugin fails during release
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
during the release:perform goal.
I have tried to run mvn package on the target/checkout directory and I
am getting the same errors... It seems that the build.xml file cannot be
run outside of the ${basedir} directory...
Any workaround for this situation?
How about tweaking the release:perform goal?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] looking for link checker
Hi all, As part of my M2 projects I am maintaining their documentation in HTML format. I am looking for a M2 (or ANT) plugin that checks HTML links given a root directory. Anyone knows about such a thing? TIA, Adrian. P.S. I have googled about and found nothing except the Maven (1.x) LinkChecker which works on Maven generated documentation only. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] archetype resources generated in wrong directory
I think it is already described by the Jira report here: http://jira.codehaus.org/browse/ARCHETYPE-54 I have added my vote. Adrian. Milos Kleint wrote: unfortunately won't work with the current archetype plugin. I have the same problem. the "resource is source" trick used to work a while back but not anymore. The only solution I found is to use the archetypeng code at mojo.codehaus.org that will eventually replace the current archetype codebase anyway (I hope so at least) Milos Kleint On 5/28/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi all, I am trying to write an archetype for my project and discovered that the resources are always copied into the src/main/resources/ generated directory instead of being copied into the src/main/resource/my/groupid/ (in parallel with the sources src/main/mylang/my/groupid/). I have tried to specify the resource directory in the pom.xml, but didn't help. I have tried to specify the resources as sources, but in this case Maven fails with some error message about using two source directories... Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] archetype resources generated in wrong directory
Hi all, I am trying to write an archetype for my project and discovered that the resources are always copied into the src/main/resources/ generated directory instead of being copied into the src/main/resource/my/groupid/ (in parallel with the sources src/main/mylang/my/groupid/). I have tried to specify the resource directory in the pom.xml, but didn't help. I have tried to specify the resources as sources, but in this case Maven fails with some error message about using two source directories... Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2.0.6] seems like a classloader issue...
Very sad... Plexus... Forehead... Bunches of classloaders... and still it cannot use different versions of plugins... Max Bowsher wrote: Adrian Herscu wrote: Hi all, In a multi-project P, child #1 (cP1) runs before child #2 (cP2). In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in order to use ant-1.7.0 instead of ant-1.6.5). When running mvn install on P, the cP1 builds normally, but the cP2 fails because it uses the maven-antrun-plugin:1.1 instead of maven-antrun-plugin:1.1-INTERNAL :-( If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the dependencies from cP2, then everything works fine! Sadly, Maven doesn't seem to be able to cope with using different versions of a plugin in different projects within a multi-project build. It just uses the first it encountered within the built. Max. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2.0.6] seems like a classloader issue...
Hi all, In a multi-project P, child #1 (cP1) runs before child #2 (cP2). In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in order to use ant-1.7.0 instead of ant-1.6.5). When running mvn install on P, the cP1 builds normally, but the cP2 fails because it uses the maven-antrun-plugin:1.1 instead of maven-antrun-plugin:1.1-INTERNAL :-( If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the dependencies from cP2, then everything works fine! Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] how to call a mojo from other mojo
Hi Wendy, I have described my problem in a previous post ([m2] Configuring mojo parameters), but got not replies still :-( Basically, it is one mojo implemented in ANT which needs to get the work of other mojo before (maven-dependency-plugin:unpack-dependencies). I can see to ways: 1) call the other mojo directly; 2) do some trick in the plexus components.xml descriptor, or somewhere else, to pass the other mojo the "right" parameters. Please help, Adrian. Wendy Smoak wrote: On 5/13/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: How is this related to my problem? You'll probably get more useful responses if you describe the problem you're trying to solve, rather than the solution you're having trouble implementing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] how to call a mojo from other mojo
How is this related to my problem? Jochen Wiedmann wrote: On 5/13/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: After digging an hour in the documentation and sources I have no example of calling other mojos from an ANT-based mojo. Is it possible? How? I have recently developed a "subclass" of the war plugin. It is duplicating the war plugins fields (yes, doing copy&paste in the source code) and acting as a proxy to an instance of the war plugin. I haven't yet published the source code, but I intend to do that in the near future. (Docs are to be written.) Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] how to call a mojo from other mojo
Hi all, After digging an hour in the documentation and sources I have no example of calling other mojos from an ANT-based mojo. Is it possible? How? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Configuring mojo parameters
Hi all,
I am building a M2 plugin to handle my special artifacts.
For this purpose I have defined a custom lifecycle and bound my mojos
and additional mojos to it.
One of the additional mojos is the
maven-dependencies-plugin:unpack-dependencies. This mojo has an
outputDirectory parameter which is set by default to
${project.build.directory}/dependencies. I need it to point to a
different directory.
I thought about wrapping this mojo with my own mojo and this way passing
the "right" parameters to it. Something like this:
compile
bring-dependencies
org.apache.maven.plugins:maven-dependency-plugin::unpack-dependencies
...
outputDirectory
outputDirectory
...
${project.build.outputDirectory}
...
However, when executed this fails with:
[INFO] Failed to execute: Executing Ant script:
/com/acme/builder.build.xml
[org.apache.maven.plugins:maven-dependency-plugin::unpack-depende
ncies]: Failed to execute.
Target
`org.apache.maven.plugins:maven-dependency-plugin::unpack-dependencies' d
oes not exist in this project.
How do I access other mojos from my own ANT-based mojo?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] adding classpathentry with maven-eclipse-plugin
Here is one use case (or probably something missing from maven-eclipse-plugin): - add a resource folder to your Java project - add it in the pom.xml - write some code to load some resource (e.g. using getResourceAsStream) - test the project using M2 -- the resource will be found - test the project in Eclipse -- the resource will *not* be found In order to run/test/debug the project in Eclipse, you will have to manually add that resource folder to the .classpath descriptor file. The maven-eclipse-plugin could automatically add that resource folder as a classpathentry. Adrian. Adrian Herscu wrote: Solved by adding that classpath using the build-helper-maven-plugin. Thorsten Heit wrote: Hi Adrian, Is there some way to add a classpathentry such as to the .classpath file? It seems that the plugin knows only about classpath containers :-( AFAIK no. The plugin only adds all the dependencies contained in your pom.xml to the .classpath file. Just for curiosity: What's your use case? Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] cobertura-maven-plugin specify: '-Dinstrumentation=VALUE'
Version 2.1 always reports 100% coverage... Wayne Fay wrote: I checked the user@ archive and sure enough, this is a bug in the documentation -- you must wrap the nodes insides . Same with and I assume . Wayne On 4/23/07, Wayne Fay <[EMAIL PROTECTED]> wrote: Any reason you're using 2.0 instead of 2.1? Give it a try and see if it works any better. Also, perhaps try wrapping your ignore node(s) inside an ignores node: ... Wayne On 4/22/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: > Hi all, > > I am using the cobertura-maven-plugin 2.0 and I want to make it ignore > the classes in some package, so I am specifying: > > > org.foo.* > > > This causes the build to fail with the following message: > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to configure plugin parameters for: > org.codehaus.mojo:cobertura-maven-plugin:2.0 > > on the command line, specify: '-Dinstrumentation=VALUE' > > Cause: Cannot find setter nor field in > org.codehaus.mojo.cobertura.configuration.ConfigInstrumentation for 'ignore' > > Adrian. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation.
rg.apache.tools.ant.Main.main(),5,org.apache.tools.ant.Main]
[DEBUG] Setting accessibility to true in order to invoke main().
Buildfile: C:\documents\pm\project-trunks\acme\lang\compiler\decompile.xml
Wayne Fay wrote:
What's mvn -X look like?
Wayne
On 4/23/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
Using Maven 2.0.6 and the exec-maven-plugin 1.1-beta-1, the following
messages appear during the java goal execution:
[INFO] Preparing exec:java
[WARNING] Removing: java from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [exec:java {execution: default}]
Buildfile: C:\documents\pm\backyard\some-ant-build.xml
The effect is that the build lifecycle ends immediately after the
execution of the java goal :-(
What should I check?
Please help,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] maven-antlr-plugin searches for generated files in the source directory
Hi all,
Using Maven 2.0.6 and maven-antlr-plugin 2.0-beta-2-SNAPSHOT configured
as follows:
${basedir}/src/main/antlr/com/acme/lang/compiler
${basedir}/src/main/antlr/com/acme/lang/compiler
super.g
ext1.g
super.g
ext2.g
super.g
Otherwise I get the following errors:
[INFO] [antlr:generate {execution: default}]
[INFO] Using Antlr grammar:
C:\documents\pm\backyard\compiler\src\main\antlr\com\acme\lang\compiler\super.g
ANTLR Parser Generator Version 2.7.4 1989-2004 jGuru.com
[INFO] Using Antlr grammar:
C:\documents\pm\backyard\compiler\src\main\antlr\com
\acme\lang\compiler\ext1.g
ANTLR Parser Generator Version 2.7.4 1989-2004 jGuru.com
error: cannot find/copy importVocab file
C:\documents\pm\backyard\compiler\src\m
ain\antlr\com\acme\lang\compiler\SuperTokenTypes.txt
error: cannot find/copy importVocab file
C:\documents\pm\backyard\compiler\src\m
ain\antlr\com\acme\lang\compiler\SuperTokenTypes.txt
C:\documents\pm\backyard\compiler\target\generated-sources\antlr\com\acme\lang
\compiler\expandedext1.g:17:9: warning:Redefinition of token in toke
ns {...}: BLOCK
...and many other redefinition warnings ...
The same error is generated for each extN.
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] adding classpathentry with maven-eclipse-plugin
Solved by adding that classpath using the build-helper-maven-plugin. Thorsten Heit wrote: Hi Adrian, Is there some way to add a classpathentry such as to the .classpath file? It seems that the plugin knows only about classpath containers :-( AFAIK no. The plugin only adds all the dependencies contained in your pom.xml to the .classpath file. Just for curiosity: What's your use case? Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] [WARNING] Removing: java from forked lifecycle, to prevent recursive invocation.
Hi all,
Using Maven 2.0.6 and the exec-maven-plugin 1.1-beta-1, the following
messages appear during the java goal execution:
[INFO] Preparing exec:java
[WARNING] Removing: java from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [exec:java {execution: default}]
Buildfile: C:\documents\pm\backyard\some-ant-build.xml
The effect is that the build lifecycle ends immediately after the
execution of the java goal :-(
What should I check?
Please help,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exec-maven-plugin java goal stops the build lifecycle
OK -- I am posting the issue on the [EMAIL PROTECTED] list. Adrian. Jerome Lacoste wrote: On 4/22/07, Adrian Herscu <[EMAIL PROTECTED]> wrote: Hi Steven, I am invoking Maven as usual: mvn clean install If I am removing the exec-maven-plugin then the build lifecycle completes as expected. Adrian. 1- report problems releated to the exec mojo project on the mojo user list ( <[EMAIL PROTECTED]>) 2- which version of the exec mojo are you using ? 3- what if you only do mvn install ? Is there still a problem of shortened build lifecycle ? 4- can you send the relevant extract of your pom.xml as well as from the ouput of mvn -X clean install ? 5- can you send a test project that reproduces the problem ? Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exec-maven-plugin java goal stops the build lifecycle
Hi Steven, I am invoking Maven as usual: mvn clean install If I am removing the exec-maven-plugin then the build lifecycle completes as expected. Adrian. Steven Rowe wrote: Hi Adrian, How are you invoking Maven? "mvn package"? (or some lifecycle phase after process-test-resources)? Steve Adrian Herscu wrote: Hi all, I am using the exec-maven-plugin to run some Java program. The java goal is bound to the process-test-resource build phase. The exec-maven-plugin:java runs at the designated phase but no other thing runs afterwards -- the build finishes with this message: BUILD SUCCESSFUL Total time: 1 second Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] cobertura-maven-plugin specify: '-Dinstrumentation=VALUE'
Hi all, I am using the cobertura-maven-plugin 2.0 and I want to make it ignore the classes in some package, so I am specifying: org.foo.* This causes the build to fail with the following message: [ERROR] BUILD ERROR [INFO] [INFO] Failed to configure plugin parameters for: org.codehaus.mojo:cobertura-maven-plugin:2.0 on the command line, specify: '-Dinstrumentation=VALUE' Cause: Cannot find setter nor field in org.codehaus.mojo.cobertura.configuration.ConfigInstrumentation for 'ignore' Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] repo connection timeout too high
Hi all, Is it possible to reduce the repository connection timeout? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] exec-maven-plugin java goal stops the build lifecycle
Hi all, I am using the exec-maven-plugin to run some Java program. The java goal is bound to the process-test-resource build phase. The exec-maven-plugin:java runs at the designated phase but no other thing runs afterwards -- the build finishes with this message: BUILD SUCCESSFUL Total time: 1 second Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] adding classpathentry with maven-eclipse-plugin
Hi all, Is there some way to add a classpathentry such as to the .classpath file? It seems that the plugin knows only about classpath containers :-( Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exec-maven-plugin fails because path containing spaces
Good idea! Only problem is that "antrun" doesn't know about Ant 1.7...
(and I need a specific feature of a specific task which is available
only in Ant 1.7)
franz see wrote:
Good day,
How about using the antrun plugin instead? ( see [1] )
Cheers,
Franz
[1] http://maven.apache.org/plugins/maven-antrun-plugin/
Adrian Herscu-2 wrote:
Added
C:\DOCUME~1\pm\M2639C~1\REPOSI~1
to the M2 install settings.xml.
But, this may require changes in other machines as well :-(
Phill Moran wrote:
Surround them in quotes or use the dos short for. For instance "program
files"
== "progra~1"
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: April 16, 2007 3:07 PM
To: users@maven.apache.org
Subject: [m2] exec-maven-plugin fails because path containing spaces
Hi all,
I am trying to run Ant 1.7 from within Maven 2 using the
exec-maven-plugin.
org.codehaus.mojo
exec-maven-plugin
process-test-resources
java
org.apache.tools.ant.Main
${basedir}
-buildfile
${basedir}/mybuild.xml
It seems that there is a problem with Windows paths containing spaces.
Anyone knows about a decent workaround?
Thanks,
Adrian.
P.S. The error log:[[
BUILD FAILED
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119)
at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at org.apache.tools.ant.Main.runBuild(Main.java:663)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.Main.start(Main.java:161)
at org.apache.tools.ant.Main.main(Main.java:250)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:271)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.URISyntaxException: Illegal character in path at
index 18:
file:/C:/Documents and
Settings/pm/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
at java.net.URI$Parser.fail(URI.java:2816)
at java.net.URI$Parser.checkChars(URI.java:2989)
at java.net.URI$Parser.parseHierarchical(URI.java:3073)
at java.net.URI$Parser.parse(URI.java:3021)
at java.net.URI.(URI.java:578)
at java.net.URI.create(URI.java:840)
... 20 more
Total time: 0 seconds
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119)
at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at org.apache.tools.ant.Main.runBuild(Main.java:663)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.Main.start(Main.java:161)
at org.apache.tools.ant.Main.main(Main.java:250)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:271)
at java.lang.Th
[m2] exec-maven-plugin in a multiproject
Hi all,
I am using Maven 2.0.6 with the exec-maven-plugin 1.1-beta-1.
My project has a structure similar to this:
root
+child1
+child2
In child2 I am using the java goal and in child1 I am using the exec goal.
When I am building child2 alone everything works fine.
When I am building the root I am getting the error below.
If I remove the exec-maven-plugin from child1 then every works fine
again. Something from the first instance (child1) interferes with the
second instance (child2).
Please help,
Adrian.
Here is the error:
[INFO] Preparing exec:java
[WARNING] Removing: java from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [exec:java {execution: default}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
---
constituent[0]:
file:/C:/PROGRA~1/Java/MAVEN-~1.6/bin/../lib/maven-core-2.0.6-ub
er.jar
constituent[1]:
file:/C:/DOCUME~1/pm/M2639C~1/REPOSI~1/org/myproject/build/extensio
ns/myproject-build-extensions/1.0-alpha-1/myproject-build-extensions-1.0-alpha-1.jar
[AH] NOTE: this artifact is produced by some other child under the root.
[AH] NOTE: I have other children which use it, but without using the
exec-maven-plugin, and it doesn't interfere.
---
java.lang.NullPointerException
at
org.apache.maven.usability.MojoExecutionExceptionDiagnoser.diagnose(M
ojoExecutionExceptionDiagnoser.java:64)
at
org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(Erro
rDiagnostics.java:84)
at
org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:711)
at org.apache.maven.DefaultMaven.logError(DefaultMaven.java:656)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:131)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] exec-maven-plugin fails because path containing spaces
Added
C:\DOCUME~1\pm\M2639C~1\REPOSI~1
to the M2 install settings.xml.
But, this may require changes in other machines as well :-(
Phill Moran wrote:
Surround them in quotes or use the dos short for. For instance "program files"
== "progra~1"
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: April 16, 2007 3:07 PM
To: users@maven.apache.org
Subject: [m2] exec-maven-plugin fails because path containing spaces
Hi all,
I am trying to run Ant 1.7 from within Maven 2 using the exec-maven-plugin.
org.codehaus.mojo
exec-maven-plugin
process-test-resources
java
org.apache.tools.ant.Main
${basedir}
-buildfile
${basedir}/mybuild.xml
It seems that there is a problem with Windows paths containing spaces.
Anyone knows about a decent workaround?
Thanks,
Adrian.
P.S. The error log:[[
BUILD FAILED
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119)
at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at org.apache.tools.ant.Main.runBuild(Main.java:663)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.Main.start(Main.java:161)
at org.apache.tools.ant.Main.main(Main.java:250)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:271)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.URISyntaxException: Illegal character in path at index 18:
file:/C:/Documents and
Settings/pm/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
at java.net.URI$Parser.fail(URI.java:2816)
at java.net.URI$Parser.checkChars(URI.java:2989)
at java.net.URI$Parser.parseHierarchical(URI.java:3073)
at java.net.URI$Parser.parse(URI.java:3021)
at java.net.URI.(URI.java:578)
at java.net.URI.create(URI.java:840)
... 20 more
Total time: 0 seconds
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119)
at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at org.apache.tools.ant.Main.runBuild(Main.java:663)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.Main.start(Main.java:161)
at org.apache.tools.ant.Main.main(Main.java:250)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:271)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.URISyntaxException: Illegal character in path at index 18:
file:/C:/Documents and
Settings/pm/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
at java.net.URI$Parser.fail(URI.java:2816)
at java.net.URI$Parser.checkChars(URI.java:2989)
at java.net.URI$Parser.parseHierarchical(URI.j
[m2] exec-maven-plugin fails because path containing spaces
Hi all,
I am trying to run Ant 1.7 from within Maven 2 using the exec-maven-plugin.
org.codehaus.mojo
exec-maven-plugin
process-test-resources
java
org.apache.tools.ant.Main
${basedir}
-buildfile
${basedir}/mybuild.xml
It seems that there is a problem with Windows paths containing spaces.
Anyone knows about a decent workaround?
Thanks,
Adrian.
P.S. The error log:[[
BUILD FAILED
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
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.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119)
at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at org.apache.tools.ant.Main.runBuild(Main.java:663)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.Main.start(Main.java:161)
at org.apache.tools.ant.Main.main(Main.java:250)
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.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:271)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.URISyntaxException: Illegal character in path at
index 18: file:/C:/Documents and
Settings/pm/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
at java.net.URI$Parser.fail(URI.java:2816)
at java.net.URI$Parser.checkChars(URI.java:2989)
at java.net.URI$Parser.parseHierarchical(URI.java:3073)
at java.net.URI$Parser.parse(URI.java:3021)
at java.net.URI.(URI.java:578)
at java.net.URI.create(URI.java:840)
... 20 more
Total time: 0 seconds
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:842)
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.apache.tools.ant.launch.Locator.fromURI(Locator.java:162)
at
org.apache.tools.ant.launch.Locator.getResourceSource(Locator.java:119)
at org.apache.tools.ant.launch.Locator.getClassSource(Locator.java:90)
at org.apache.tools.ant.Project.setAntLib(Project.java:313)
at org.apache.tools.ant.Project.initProperties(Project.java:309)
at org.apache.tools.ant.Project.init(Project.java:295)
at org.apache.tools.ant.Main.runBuild(Main.java:663)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.Main.start(Main.java:161)
at org.apache.tools.ant.Main.main(Main.java:250)
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.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:271)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.URISyntaxException: Illegal character in path at
index 18: file:/C:/Documents and
Settings/pm/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
at java.net.URI$Parser.fail(URI.java:2816)
at java.net.URI$Parser.checkChars(URI.java:2989)
at java.net.URI$Parser.parseHierarchical(URI.java:3073)
at java.net.URI$Parser.parse(URI.java:3021)
at java.net.URI.(URI.java:578)
at java.net.URI.create(URI.java:840)
... 20 more
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] is it possible to bind multiple mojos to a build phase?
Thanks, it worked :-) Adrian. franz see wrote: Good day to you, Adrian, Trying doing this instead ... org.foo:foo-maven:compile, org.foo:foo-maven:validate-xml, org.foo:foo-maven:validate ... For examples, see the package and install phases of the 'maven-plugin' role-hint in [1]. Cheers, Franz [1] http://svn.apache.org/repos/asf/maven/components/trunk/maven-core/src/main/resources/META-INF/plexus/components.xml Adrian Herscu-2 wrote: Hi all, I tried to bind several mojos to the same build phase org.apache.maven.lifecycle.mapping.LifecycleMapping foo org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping default org.apache.maven.plugins:maven-resources-plugin:resources org.foo:foo-maven:compile org.foo:foo-maven:validate-xml org.foo:foo-maven:validate ...and it seems like the only one entry is bound. Any suggestions? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] is it possible to bind multiple mojos to a build phase?
Hi all, I tried to bind several mojos to the same build phase org.apache.maven.lifecycle.mapping.LifecycleMapping foo org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping default org.apache.maven.plugins:maven-resources-plugin:resources org.foo:foo-maven:compile org.foo:foo-maven:validate-xml org.foo:foo-maven:validate ...and it seems like the only one entry is bound. Any suggestions? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2][maven-dependency-plugin] unpack-dependencies issue
Hi Brian,
Thanks for your suggestion!
I have changed the includeGroupIds clause to be more specific and now it
builds correctly from the parent and this solved my problem.
However, there is still something wrong, because with the previous
configuration, the child was successfully built when activated directly.
Adrian.
Brian E. Fox wrote:
Based on the fact that the [dependency:unpack-dependencies {execution:
default}]
Is showing up, the plugin is executing, it's possible that it isn't
finding anything to copy. Try removing the includes and excludes and let
it run with default behavior, you should see it copying all dependencies
of this project. You can then start narrowing it down.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: Tuesday, March 27, 2007 1:39 PM
To: users@maven.apache.org
Subject: Re: [m2][maven-dependency-plugin] unpack-dependencies issue
Hi Brian,
Here are the relevant POM sections (if you need the entire POMs, please
let me know):
The parent
samples
lang
1nd child -- samples
org.apache.maven.plugins
maven-dependency-plugin
2.0-alpha-3
process-resources
unpack-dependencies
${project.build.outputDirectory}
...
2nd child -- lang -- depends on the first child
org.apache.maven.plugins
maven-dependency-plugin
2.0-alpha-3
unpack-samples-and-decompiler
generate-test-resources
unpack-dependencies
${project.build.directory}/unpacked-dependencies
tDirectory>
test
true
org.wirexn
...
Thanks for your fast reply,
Adrian.
Brian E. Fox wrote:
Can you paste your config?
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: Tuesday, March 27, 2007 8:14 AM
To: users@maven.apache.org
Subject: [m2][maven-dependency-plugin] unpack-dependencies issue
Hi all,
When running the maven-dependency-plugin in a multi-project, it works
only for the first child project. The following messages appear on the
console:
[INFO] [dependency:unpack-dependencies {execution: default}] [INFO]
Expanding: C:\some.war into C:\target\somefiles
It does not work in any child projects afterwards. Only this message
will appear on the console:
[INFO] [dependency:unpack-dependencies {execution: default}]
Any suggestion?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2][maven-dependency-plugin] unpack-dependencies issue
Hi Brian,
Here are the relevant POM sections (if you need the entire POMs, please
let me know):
The parent
samples
lang
1nd child -- samples
org.apache.maven.plugins
maven-dependency-plugin
2.0-alpha-3
process-resources
unpack-dependencies
${project.build.outputDirectory}
...
2nd child -- lang -- depends on the first child
org.apache.maven.plugins
maven-dependency-plugin
2.0-alpha-3
unpack-samples-and-decompiler
generate-test-resources
unpack-dependencies
${project.build.directory}/unpacked-dependencies
test
true
org.wirexn
...
Thanks for your fast reply,
Adrian.
Brian E. Fox wrote:
Can you paste your config?
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: Tuesday, March 27, 2007 8:14 AM
To: users@maven.apache.org
Subject: [m2][maven-dependency-plugin] unpack-dependencies issue
Hi all,
When running the maven-dependency-plugin in a multi-project, it works
only for the first child project. The following messages appear on the
console:
[INFO] [dependency:unpack-dependencies {execution: default}]
[INFO] Expanding: C:\some.war into C:\target\somefiles
It does not work in any child projects afterwards. Only this message
will appear on the console:
[INFO] [dependency:unpack-dependencies {execution: default}]
Any suggestion?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2][maven-dependency-plugin] unpack-dependencies issue
Hi all,
When running the maven-dependency-plugin in a multi-project, it works
only for the first child project. The following messages appear on the
console:
[INFO] [dependency:unpack-dependencies {execution: default}]
[INFO] Expanding: C:\some.war into C:\target\somefiles
It does not work in any child projects afterwards. Only this message
will appear on the console:
[INFO] [dependency:unpack-dependencies {execution: default}]
Any suggestion?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Release:perform fails becuase of checkstyle plugin
This happens whenever the maven-checkstyle-plugin does not find the
specified configuration file.
Adrian.
Ziv Ben-Eliahu wrote:
Short description of the problem
*
When running "mvn release:perform", "Checkstyle" report plugin fails on:
[WARNING] Unable to load parent project from repository: Could not
find the model file 'D:\projectParent\projectA\target\checkout\..\pom.xml'.
[INFO] Skipped "Maven Surefire Report" report, file
"surefire-report.html" already exists f
[INFO] Generate "Checkstyle" report.
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] String index out of range: -1
[INFO]
[INFO] Trace
java.lang.StringIndexOutOfBoundsException: String index out of
range: -1
at java.lang.String.substring(String.java:1768)
at
org.codehaus.classworlds.UrlUtils.normalizeUrlPath(UrlUtils.java:28)
at
org.codehaus.classworlds.DefaultClassRealm.getResource(DefaultClassRealm.java:284)
at
org.codehaus.classworlds.RealmClassLoader.getResource(RealmClassLoader.java:237)
at
org.apache.maven.plugin.checkstyle.Locator.resolveLocation(Locator.java:117)
at
org.apache.maven.plugin.checkstyle.CheckstyleReport.getConfigFile(CheckstyleReport.j
Long description of the problem
*
The project structure looks like this:
Parent-1.0-alpha-4
+A-1.0-alpha-3-SNAPSHOT
The parent hold checkstyle configuration.
Project A-1.0-alpha-3-SNAPSHOT have these in the pom.xml:
maven-checkstyle-plugin
${basedir}/../src/config/checkstyle/my-checks.xml
maven-javadoc-plugin
maven-surefire-report-plugin
org.codehaus.mojo
jdepend-maven-plugin
org.codehaus.mojo
cobertura-maven-plugin
2.0
In project A-1.0-alpha-3-SNAPSHOT (under the parent) I do the following
with Maven2:
> mvn site
SUCCESS and give complete report
> mvn release:clean release:prepare
SUCCESS
> mvn release:perform
BUILD ERROR
cause: as specified above, in the short description.
A possible meaning of the cause - it tried to get to the parent pom.xml.
But since it is under target\checkout the parent is not one directory up.
When I removed the configuration line:
${basedir}/../src/config/checkstyle/my-checks.xml
and did a new release:preform, the checkstyle still had the same problem
but it continued to SUCCESS by using a default checkstyle settings
instead of my settings. The message was:
[WARNING] Unable to load parent project from repository: Could not
find the model file 'D:\projectParent\projectA\target\checkout\..\pom.xml'.
[INFO] Skipped "Maven Surefire Report" report, file
"surefire-report.html" already exists for the English version.
[INFO] Generate "Checkstyle" report.
[INFO] There are 511 checkstyle errors.
[WARNING] Unable to locate Source XRef to link to - DISABLED
[ERROR] VM #displayTree: error : too few arguments to macro. Wanted
2 got 0
[ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1
got 0
[INFO] Generate "JavaDocs" report.
Does someone have an idea why this is happening?
Thanks, Ziv.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] incorrect dependency during test
Hi all, I have a very interesting issue with M2 tests... The project structure looks like this: Parent-1.0-alpha-3-SNAPSHOT +A-1.0-alpha-3-SNAPSHOT +B-1.0-alpha-3-SNAPSHOT A-1.0-alpha-3-SNAPSHOT depends on B-1.0-alpha-2 (not on the SNAPSHOT!) B-1.0-alpha-3-SNAPSHOT has some changes in one of its classes which require a class that was not present in its previous release (alpha-2). Attempting to run mvn clean test on the parent fails because one of the A's tests throws java.lang.NoClassDefFoundError complaining about the aforementioned class. However, running mvn clean install succeeds! Running mvn clean test on A alone succeeds also! Removing the B reference from parent's child modules list enables us to run a successful mvn clean test on the parent! Any suggestion? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] binding to the site phase
Hi all, Is it possible to bind something to the site phase? In META-INF/plexus/components.xml I have tried: org.apache.maven.lifecycle.mapping.LifecycleMapping foo org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping org.foo.buildsys.maven:foo-buildsys-maven:validate-xml org.apache.maven.plugins:maven-resources-plugin:resources org.foo.buildsys.maven:foo-buildsys-maven:compile org.foo.buildsys.maven:foo-buildsys-maven:testValidate-xml org.apache.maven.plugins:maven-resources-plugin:testResources org.foo.buildsys.maven:foo-buildsys-maven:testCompile org.foo.buildsys.maven:foo-buildsys-maven:test org.apache.maven.plugins:maven-install-plugin:install org.foo.buildsys.maven:foo-buildsys-maven:war org.apache.maven.plugins:maven-deploy-plugin:deploy I understand that the site phase is not part of the default lifecycle, but I cannot figure out how do I create the binding. Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] artifacts are not resolved when mirror is not available
Hi all, I am trying to setup an internal Maven mirror for our company using Proximity. Proximity seems to work for the predefined repositories. I still having trouble with defining additional repositories (Proximity fails to start when those additional repositories are added...). Went home and tried to do a build. The mirror on my company's internal network is not available and Maven cannot download its artifacts :-( Any suggestion? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] eclipse:make-artifacts does not exists?!
Hi all, I am trying to use Eclipse jars in my M2 project. The mvn eclipse:make-artifacts (http://maven.apache.org/plugins/maven-eclipse-plugin/make-artifacts-mojo.html) returns: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'eclipse'. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: eclipse:make-artifacts [INFO] Any suggestion? Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] HOWTO release with a snapshot parent
So the whole point of releases is "rebuild" -- i.e. given a release label and the software repository, the system can be rebuilt. Is that correct? Thanks for your feedback, Adrian. Dan Tran wrote: > that is not allowed since there is no guarantee you can rebuild the release > with a dependent snapshot ( ie parent ) > > -D > > > On 12/6/06, Adrian Herscu <[EMAIL PROTECTED]> wrote: >> >> Hi all, >> >> I am trying to release a module using the maven-release-plugin. >> The module has a parent which was not released yet (its siblings are not >> released also). >> When running release:prepare on that module Maven complains that its >> parent is a SNAPSHOT, so it cannot complete the release preparation :-( >> >> This seems related to the following issue in Jira: >> http://jira.codehaus.org/browse/MRELEASE-96 >> >> Currently, I am thinking about releasing the whole project (from the >> root). >> >> Please advice, >> Adrian. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] HOWTO release with a snapshot parent
Hi all, I am trying to release a module using the maven-release-plugin. The module has a parent which was not released yet (its siblings are not released also). When running release:prepare on that module Maven complains that its parent is a SNAPSHOT, so it cannot complete the release preparation :-( This seems related to the following issue in Jira: http://jira.codehaus.org/browse/MRELEASE-96 Currently, I am thinking about releasing the whole project (from the root). Please advice, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] HOWTO release with a snapshot parent
Hi all, I am trying to release a module using the maven-release-plugin. The module has a parent which was not released yet (its siblings are not released also). When running release:prepare on that module Maven complains that its parent is a SNAPSHOT, so it cannot complete the release preparation :-( This seems related to the following issue in Jira: http://jira.codehaus.org/browse/MRELEASE-96 Currently, I am thinking about releasing the whole project (from the root). Please advice, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn: Caught signal
Hi all, I am using Subversion 1.3.2 through Apache 2.0.55. Sometimes my Continuum builds fail with the following error message: Provider message: The svn command failed. Command output: --- svn: Caught signal --- Did a Google on "svn: Caught signal" but there are only 12 results and no answer. What should I check? Moreover, after such errors no further automatic build attempts occur and somebody must hit the build now button in order to make Continuum builds work again. Is this some kind of "feature"? Adrian.
Re: can't remove project
Hi all, Tried not to touch the keyboard/mouse at all during the "add" operation of some multi-module project, and the same thing happened again but with different project (now I have two projects duplicated instead of one -- the conclusion might be that it is better to do a refresh while adding projects ;-) Adrian. Here is the stack trace: ognl.MethodFailedException: Method "removeProject" failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ? NestedThrowables: SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'PROJECT_BUILP8_FK2' for key (4). The statement has been rolled back.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.codehaus.plexus.formica.action.DeleteEntity.uponSuccessfulValidation(DeleteEntity.java:57) at org.codehaus.plexus.formica.action.DeleteEntity.execute(DeleteEntity.java:47) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ javax.jdo.JDOUserException: One or more instances could not be deleted at org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersistenceManager.java:1438) at org.jpox.store.rdbms.scostore.ElementContainerStore.clear(ElementContainerStore.java:595) at org.jpox.store.mapping.CollectionMapping.preDelete(CollectionMapping.java:304) at org.jpox.store.mapping.CollectionMapping.deleteDependent(CollectionMapping.java:332) at org.jpox.store.rdbms.table.ClassTable.deleteDependent(ClassTable.java:2280) at org.jpox.store.StoreManager.deleteDependent(StoreManager.java:838) at org.jpox.state.StateManagerImpl.deletePersistent(StateManagerImpl.java:4049) at org.jpox.AbstractPersistenceManager.internalDeletePersistent(AbstractPersistenceManager.java:1391) at org.jpox.AbstractPersistenceManager.deletePersistent(AbstractPersistenceManager.java:1402) at org.codehaus.plexus.jdo.PlexusJdoUtils.removeObject(PlexusJdoUtils.java:53) at org.apache.maven.continuum.store.JdoContinuumStore.removeObject(JdoContinuumStore.java:969) at org.apache.maven.continuum.store.JdoContinuumStore.removeProject(JdoContinuumStore.java:901) at org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinuum.java:328) 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 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at
Re: [m2] Packaging as directory
Hi Olivier and thanks for your fast reply.
I need the validation to work with most tools and without any special
configuration/programming. Therefore the first solution, accessing the
schema in an archive, is not suitable.
The other solution seems suitable at first sight. But what about the
version information? After all, we use Maven also because of the central
artifact repository, in which artifacts are stored in a versioned manner.
Putting the schema files in the site, makes them unversioned entities
and this is not true. Schema files change from time to time and
backwards compatibility cannot be always preserved -- therefore we need
the versioning stuff.
Is it possible to write an M2 plugin to do the "directory" packaging?
Adrian.
LAMY Olivier wrote:
> Hi,
> Workarounds for this :
> I have done this with putting schema in src/main/resources.
> The result is an artifact which contains only the schemas.
> For validation : add the artifact in dependencies and load the schema with a
> getResource and use your favorite parser.
>
> An other one is to put your schemas in src/site/resources and deploy your
> site (the schemas will in the root folder of the web site). With this one,
> you can use schemaLocation.
>
> --
> Olivier
>
>
> -Message d'origine-----
> De : news [mailto:[EMAIL PROTECTED] De la part de Adrian Herscu
> Envoyé : samedi 23 septembre 2006 13:54
> À : users@maven.apache.org
> Objet : [m2] Packaging as directory
>
> Hi all,
>
> I have a project which contains only XML schema files.
> Other project files depend on these XML schemas for validation, i.e.
> there must be some fixed URL for the XML validator to find the appropriate
> XML schema for each one of the validating XML files (this URL is contained by
> the XML schemaLocation property).
>
> I would like to point the XML schemaLocation property to an URL in my M2
> repository where the XML schema files are deployed. The problem is that the
> deployment artifact is archived as a WAR file and the repository server does
> not know how to unpack the archive on demand and the schema files remain
> unaccessible :-(
>
> I am thinking about a "directory" packaging type -- is it possible?
> Any other solution?
>
> Thanks in advance,
> Adrian.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> This e-mail, any attachments and the information contained therein ("this
> message") are confidential and intended solely for the use of the
> addressee(s). If you have received this message in error please send it back
> to the sender and delete it. Unauthorized publication, use, dissemination or
> disclosure of this message, either in whole or in part is strictly prohibited.
> **
> Ce message électronique et tous les fichiers joints ainsi que les
> informations contenues dans ce message ( ci après "le message" ), sont
> confidentiels et destinés exclusivement à l'usage de la personne à laquelle
> ils sont adressés. Si vous avez reçu ce message par erreur, merci de le
> renvoyer à son émetteur et de le détruire. Toutes diffusion, publication,
> totale ou partielle ou divulgation sous quelque forme que se soit non
> expressément autorisées de ce message, sont interdites.
> **
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Packaging as directory
Hi all, I have a project which contains only XML schema files. Other project files depend on these XML schemas for validation, i.e. there must be some fixed URL for the XML validator to find the appropriate XML schema for each one of the validating XML files (this URL is contained by the XML schemaLocation property). I would like to point the XML schemaLocation property to an URL in my M2 repository where the XML schema files are deployed. The problem is that the deployment artifact is archived as a WAR file and the repository server does not know how to unpack the archive on demand and the schema files remain unaccessible :-( I am thinking about a "directory" packaging type -- is it possible? Any other solution? Thanks in advance, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
General Build Question
Hi all, I apologize if this is not the right place to ask these kind of questions but could not think about anything better. My scenario is as follows: - one hosted svn repo for daily work - one local svn repo as fallback, synchronized daily against the hosted repo The problem is with the changing URLs whenever we need to switch from the hosted repo to the local repo: 1) We need to relocate all our working copies 2) We need to fix all POMs by replacing all occurrences of the hosted URL with the local URL 3) Commit all changes 4) Reconfigure Continuum with the new POMs I am thinking about using some proxy server to do the URL rewriting. So everything will work as it was on the local repo, but if the URL rewriting is activated then local URLs would be transformed to hosted URLs. Is there a better solution? Thanks for advice, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] problem w/ dependency-maven-plugin:unpack-dependencies
Any encouraging news about this issue?...
Brian E. Fox wrote:
> This is a known issue caused by maven reacting differently when run from
> a parent. I'll attempt to find a workaround, but IMNSHO, this is a
> defect in maven core.
>
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
> Sent: Monday, March 20, 2006 6:24 PM
> To: users@maven.apache.org
> Subject: [m2] problem w/ dependency-maven-plugin:unpack-dependencies
>
> Hi all,
>
> I have a project with two war modules (app1, app2) that depend one on
> the other. I have defined a parent pom.xml (root) in order to be able to
> build both project modules at once.
>
> In one of the war modules (app2) I am using the dependency-maven-plugin
> in order to merge the artifact produced by the other war module (app1)
> into a deployable artifact.
>
> When I am building app2 directly everything works as expected (the app1
> artifact is expanded in the webappDirectory).
>
> A weird thing happens when I am building root: the
> dependency-maven-plugin does not expand the dependencies.
>
> Adrian.
>
> The pom.xml files are:
>
> 1) The root:
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
> com.mycompany
> mycompany
> 1.0-SNAPSHOT
>
> pom
>
>
> mycompany-app1
> mycompany-app2
>
>
>
>
>
> 2) app1:
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
>
> com.mycompany
> mycompany
> 1.0-SNAPSHOT
>
>
> com.mycompany.app1
> mycompany-app1
> war
> 1.0-SNAPSHOT
>
> Maven Webapp #1
> http://maven.apache.org
>
>
>
>
>
>
> 3) app2:
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
>
> com.mycompany
> mycompany
> 1.0-SNAPSHOT
>
>
> com.mycompany.app2
> mycompany-app2
> war
> 1.0-SNAPSHOT
>
> Maven Webapp #2
> http://maven.apache.org
>
>
>
> com.mycompany.app1
> mycompany-app1
> 1.0-SNAPSHOT
> war
>
>
>
>
>
>
> org.codehaus.mojo
> dependency-maven-plugin
>
>
> process-resources
>
> unpack-dependencies
>
>
>
> ${project.build.directory}/${project.build.finalName} outputDirectory>
>
>
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] problem w/ antcall in ANT-based mojo
Wayne, thanks for your reply. I will try your idea now. Wayne Fay wrote: > When you create the my/project/path/build.xml file and add the task to > that file, does the antcall function work as you expected? > > Not saying this is the proper solution, just trying to help figure it out... > > Wayne > > > On 3/19/06, Adrian Herscu <[EMAIL PROTECTED]> wrote: >> Hi all, >> >> When using antcall in an ANT-based mojo the build fails with >> >> [ERROR] BUILD ERROR >> [INFO] >> - >> --- >> [INFO] Failed to execute: Executing Ant script: >> /my/plugin/path/mymojo.build.xml [my-target]: Failed to execute. >> >> my/project/path/build.xml (The system cannot find the file s >> pecified) >> >> (of course in my project dir. there is no build.xml) >> >> ANT's documentation >> (http://ant.apache.org/manual/CoreTasks/antcall.html) says that antcall >> invokes targets in the same build file, namely in mymojo.build.xml -- so >> why it tries to find build.xml in project's directory? >> >> Thanks for any hint, >> Adrian. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] problem w/ dependency-maven-plugin:unpack-dependencies
Hi all,
I have a project with two war modules (app1, app2) that depend one on
the other. I have defined a parent pom.xml (root) in order to be able to
build both project modules at once.
In one of the war modules (app2) I am using the dependency-maven-plugin
in order to merge the artifact produced by the other war module (app1)
into a deployable artifact.
When I am building app2 directly everything works as expected (the app1
artifact is expanded in the webappDirectory).
A weird thing happens when I am building root: the
dependency-maven-plugin does not expand the dependencies.
Adrian.
The pom.xml files are:
1) The root:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.mycompany
mycompany
1.0-SNAPSHOT
pom
mycompany-app1
mycompany-app2
2) app1:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.mycompany
mycompany
1.0-SNAPSHOT
com.mycompany.app1
mycompany-app1
war
1.0-SNAPSHOT
Maven Webapp #1
http://maven.apache.org
3) app2:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.mycompany
mycompany
1.0-SNAPSHOT
com.mycompany.app2
mycompany-app2
war
1.0-SNAPSHOT
Maven Webapp #2
http://maven.apache.org
com.mycompany.app1
mycompany-app1
1.0-SNAPSHOT
war
org.codehaus.mojo
dependency-maven-plugin
process-resources
unpack-dependencies
${project.build.directory}/${project.build.finalName}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] How to get the plugin's root path
Hi all, I am writing an ANT-based plugin which needs to validate a set of XML files. I would like to have the schema files packaged inside the plugin JAR and wondered how to reference those files. Please help, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] problem w/ antcall in ANT-based mojo
Hi all, When using antcall in an ANT-based mojo the build fails with [ERROR] BUILD ERROR [INFO] - --- [INFO] Failed to execute: Executing Ant script: /my/plugin/path/mymojo.build.xml [my-target]: Failed to execute. my/project/path/build.xml (The system cannot find the file s pecified) (of course in my project dir. there is no build.xml) ANT's documentation (http://ant.apache.org/manual/CoreTasks/antcall.html) says that antcall invokes targets in the same build file, namely in mymojo.build.xml -- so why it tries to find build.xml in project's directory? Thanks for any hint, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2][ibiblio-upload-request] ant-testutil-1.6.5.jar
Carlos, Wayne, please see my comments below. Adrian. Carlos Sanchez wrote: > Apache projects are responsible of putting their stuff in the apache > maven repo, which is copied to ibiblio ant-testutil.jar is even not available as a standalone binary download -- you have to download the ANT sources and then build it yourself (what a fun!). > > On 3/9/06, Wayne Fay <[EMAIL PROTECTED]> wrote: >> That doesn't matter! Anyone can submit a Maven bundle for uploading >> into Maven repo. >> >> Personally I've submitted a few artifacts following the instructions >> on that page. Just put "NOT A DEVELOPER" in the JIRA task, per the >> instructions... >> >> Wayne >> This seems bizarre! Then you could submit a trojan?... Perhaps others did that?... Perhaps we already have few trojans on our systems?... That's scary!!! >> >> On 3/9/06, Adrian Herscu <[EMAIL PROTECTED]> wrote: >>> But I am not one of the ANT developers... >>> I will ask for help on the ANT user list. >>> >>> Wayne Fay wrote: >>>> Realistically, if you want this to end up in Maven repo, you will need >>>> to follow the directions on the website to make a Maven bundle etc and >>>> upload to Jira under project MavenUpload: >>>> http://maven.apache.org/guides/mini/guide-ibiblio-upload.html >>>> >>>> If you don't follow those directions, then you're just crossing your >>>> fingers and hoping someone else does it for you as a result of this >>>> email. ;-) >>>> >>>> Wayne >>>> >>>> >>>> On 3/9/06, Adrian Herscu <[EMAIL PROTECTED]> wrote: >>>>> Hi all, >>>>> >>>>> Can someone upload the ant-testutil.jar to IBiblio? >>>>> This jar is not distributed as part of the ANT binary distribution. >>>>> I have built it today from ANT 1.6.5 sources (and it works now from my >>>>> local repository). >>>>> Attached the ant-testutil-1.6.5.jar and its maven-metadata-local.xml as >>>>> it shows up in my local repository. >>>>> >>>>> TIA >>>>> Adrian. >>>>> >>>>> >>>>> >>>>> >>>>> - >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>> >>> - >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> > > > -- > 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]
