Re: make maven work in sun solaris 10
Trying 38.97.124.18... Connected to repo1.maven.org. Escape character is '^]'. ^C^] -- Olivier 2008/10/6 Wayne Fay [EMAIL PROTECTED]: Seems like your DNS resolution is not working properly. You need to talk to who ever your sysadmin is to get that fixed, and then Maven should work fine. And if *you* are the sysadmin of this box, you need to get help from a Solaris beginners forum to get your box set up and working on the Internet properly, then try Maven again. Wayne On Mon, Oct 6, 2008 at 9:15 AM, 陈思淼 [EMAIL PROTECTED] wrote: you can ping repo1.maven.org to verify the network working. Maven can work in Solaris of cause because that SUN's home platform. and maven is a java program. 2008/10/7 Patrizio Munzi [EMAIL PROTECTED] Hi everybody, I've been trying to make maven work on SUN Solaris 10 for the last few days, but since I'm not a Solaris administration expert I had no luck. I have the following exception: Caused by: java.net.UnknownHostException: repo1.maven.org I think it's related to some Solaris network configurations, but I don't know how to solve them. Can anyone help me...? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *Patrizio Munzi* Product Specialist Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: make maven work in sun solaris 10
Hi, I've finally managed to make maven work on my sun solaris machine Since I haven't got either a proxy or a firewall to configure, I was strongly convicted that there were some DNS configuration to do. There you go... I just had to add the following to lines to the file: /etc/nsswitch.conf - hosts: files dns ipnodes: files dns - Thanks to everydoby. Daniele De Francesco wrote: Hi, I experienced such an issue when rying to make maven work in a proxied environment... do you know whether there is a specific proxy configuration of that box or perhaps a firewall that you should take account for? If so...you know well how to get rid of the problem... -- Daniele De Francesco Senior Java Architect Value Team Italia 2008/10/7 Patrizio Munzi [EMAIL PROTECTED] Hi, I checked the file /etc/resolv.conf and it seems ok. Also the command: -- [EMAIL PROTECTED] ~]$ telnet repo1.maven.org 80 Trying 38.97.124.18... Connected to repo1.maven.org. Escape character is '^]'. ^C Connection to repo1.maven.org closed by foreign host. works properly. -- Here's my exception stack trace. Anyway I'm quite sure that it's a network configuration problem. -- [EMAIL PROTECTED] ~]$ mvn -X archetype:create -DgroupId=test -DartifactId=test + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.6.0_06 OS name: sunos version: 5.10 arch: sparc Family: unix [DEBUG] Building Maven user-level plugin registry from: '/export/home/munzi/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/usr/local/maven-2.0.9/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [DEBUG] Exception org.apache.maven.wagon.TransferFailedException: Error transferring file at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:470) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:370) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97) at org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:103) at org.apache.maven.plugin.DefaultPluginMappingManager.loadPluginMappings(DefaultPluginMappingManager.java:87) at org.apache.maven.plugin.DefaultPluginMappingManager.getByPrefix(DefaultPluginMappingManager.java:61) at org.apache.maven.plugin.DefaultPluginManager.getPluginDefinitionForPrefix(DefaultPluginManager.java:154) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1468) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:405) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) 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) Caused by: java.net.UnknownHostException: repo1.maven.org at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java
make maven work in sun solaris 10
Hi everybody, I've been trying to make maven work on SUN Solaris 10 for the last few days, but since I'm not a Solaris administration expert I had no luck. I have the following exception: Caused by: java.net.UnknownHostException: repo1.maven.org I think it's related to some Solaris network configurations, but I don't know how to solve them. Can anyone help me...? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: make maven work in sun solaris 10
I already tried to ping repo1.maven.org and it worked. I know maven can work on solaris, I'm not a maven newbie, I 've been using it for a year. As I said I think it's a network configuration problem. I've already done any under my knowledge sun solaris network configurations but I still have the same problem. Any other help..?? ??? wrote: you can ping repo1.maven.org to verify the network working. Maven can work in Solaris of cause because that SUN's home platform. and maven is a java program. 2008/10/7 Patrizio Munzi [EMAIL PROTECTED] Hi everybody, I've been trying to make maven work on SUN Solaris 10 for the last few days, but since I'm not a Solaris administration expert I had no luck. I have the following exception: Caused by: java.net.UnknownHostException: repo1.maven.org I think it's related to some Solaris network configurations, but I don't know how to solve them. Can anyone help me...? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *Patrizio Munzi* Product Specialist Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: removing maven files from jar
Hi,
you have to use the exclude tag.
Take a look here:
http://maven.apache.org/plugins/maven-jar-plugin/jar-mojo.html
Regards.
I am Who i am wrote:
Hi All,
How to remove maven related files like maven folder / pom.xml /
pom.properties files from the jar file being created, i have the following
in my pom, but still seeing the maven directory with pom / .xml/.properties
under META-INF directory, my jar plugin version is 2.2
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
execution
idCUSTOM-MANIFEST/id
goals
goaljar/goal
/goals
configuration
archive
manifestFile${basedir}/../wsear/META-INF/MANIFEST.MF/manifestFile
addMavenDescriptorfalse/addMavenDescriptor
/archive
/configuration
/execution
/executions
/plugin
/plugins
/build
Please help
--
*Patrizio Munzi*
Product Engineer
Viale Bruno Buozzi, 19 - 00197 Roma (Italy)
tel: +39 06 4543 3540
fax: +39 06 4543 3587
mobile: +39 393 7195 164
mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
web: http://www.eris4.com http://www.eris4.com/
skype: eris4_munzi skype:eris4_munzi?add
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
excluding files from jar doesn't work completely well - maven-jar-plugin 2.2
Hi All, I'm trying to exclude some files from the built jar by using the maven-jar-plugin exclude feature. Here's my configuration: excludes exclude**/*.properties/exclude exclude**/*.xml/exclude exclude**/*.xsd/exclude /excludes Although all the specified files are actually excluded from the deployed jar, the directory paths of the excluded files are still created into the jar. I mean, if I have the following files under the resources directory: resources/log4j.properties resources/xml/file.xml resources/xml/schema/schema.xsd These files won't be included in the built jar, but I'll still have the following path into it: resources/xml/schema/ Is anyone aware of this problem with the maven-jar-plugin...? Thanks. Cheers Patrizio -- *Patrizio Munzi* Product Engineer Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: excluding files from jar doesn't work completely well - maven-jar-plugin 2.2
Thanks for your answer, so is it a real problem...? Thanks Olivier Lamy wrote: Post an issue in jira. And attach a simple project test case to reproduce the issue. Thanks, -- Olivier 2008/3/11, Patrizio Munzi [EMAIL PROTECTED]: Hi All, I'm trying to exclude some files from the built jar by using the maven-jar-plugin exclude feature. Here's my configuration: excludes exclude**/*.properties/exclude exclude**/*.xml/exclude exclude**/*.xsd/exclude /excludes Although all the specified files are actually excluded from the deployed jar, the directory paths of the excluded files are still created into the jar. I mean, if I have the following files under the resources directory: resources/log4j.properties resources/xml/file.xml resources/xml/schema/schema.xsd These files won't be included in the built jar, but I'll still have the following path into it: resources/xml/schema/ Is anyone aware of this problem with the maven-jar-plugin...? Thanks. Cheers Patrizio -- *Patrizio Munzi* Product Engineer Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - 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] -- *Patrizio Munzi* Product Engineer Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: excluding files from jar doesn't work completely well - maven-jar-plugin 2.2
Yes, you're right. Not a so heavy issue. Just a correctness remark. I've already filed a jira issue for it with simple project test case. Regards, Patrizio [EMAIL PROTECTED] wrote: It doesn't surprise me too much that the maven-jar-plugin still creates empty directories even when all files that were in that directory have been excluded. I haven't checked myself, but it sounds like a situation that the plugin author could easily have overlooked. But it doesn't cause any problems does it? Just a minor wastage of space in the generated jarfile? In this case, it is probably worth filing a jira issue for this, but it should be marked minor or even trivial unless it causes actual problems for programs. Regards, Simon Patrizio Munzi schrieb: Thanks for your answer, so is it a real problem...? Thanks Olivier Lamy wrote: Post an issue in jira. And attach a simple project test case to reproduce the issue. Thanks, -- Olivier 2008/3/11, Patrizio Munzi [EMAIL PROTECTED]: Hi All, I'm trying to exclude some files from the built jar by using the maven-jar-plugin exclude feature. Here's my configuration: excludes exclude**/*.properties/exclude exclude**/*.xml/exclude exclude**/*.xsd/exclude /excludes Although all the specified files are actually excluded from the deployed jar, the directory paths of the excluded files are still created into the jar. I mean, if I have the following files under the resources directory: resources/log4j.properties resources/xml/file.xml resources/xml/schema/schema.xsd These files won't be included in the built jar, but I'll still have the following path into it: resources/xml/schema/ Is anyone aware of this problem with the maven-jar-plugin...? Thanks. Cheers Patrizio -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- *Patrizio Munzi* Product Engineer Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
excluding files from jar doesn't work completely well - maven-jar-plugin 2.2
Hi All, I'm trying to exclude some files from the built jar by using the maven-jar-plugin exclude feature. Here's my configuration: excludes exclude**/*.properties/exclude exclude**/*.xml/exclude exclude**/*.xsd/exclude /excludes Although all the specified files are actually excluded from the deployed jar, the directory paths of the excluded files are still created into the jar. I mean, if I have the following files under the resources directory: resources/log4j.properties resources/xml/file.xml resources/xml/schema/schema.xsd These files won't be included in the built jar, but I'll still have the following path into it: resources/xml/schema/ Is anyone aware of this problem with the maven-jar-plugin...? Thanks. Cheers Patrizio -- *Patrizio Munzi* Product Engineer Viale Bruno Buozzi, 19 - 00197 Roma (Italy) tel: +39 06 4543 3540 fax: +39 06 4543 3587 mobile: +39 393 7195 164 mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: http://www.eris4.com http://www.eris4.com/ skype: eris4_munzi skype:eris4_munzi?add - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven properties seem not to work in profile activation feature
Hi all,
I'm trying to manage profiles activations/deactivations by using the
activation tag among with the file tag.
What I would like to do is to activate a particular profile only if a
specified folder is present into the local repository.
The profile configuration I'm using is the following:
profiles
profile
idapache/id
activation
activeByDefaultfalse/activeByDefault
file
missing${settings.localRepository}/org/apache/maven/plugins/maven-jar-plugin/2.2-SNAPSHOT/missing
/file
/activation
repositories
[...]
/repositories
pluginRepositories
[...]
/pluginRepositories
/profile
/profiles
Now, if I use the explicit path of the local repository everything works
well, instead if I use the property ${settings.localRepository} id
doesn't work. It seems that maven isn't able to give a value to the
property. I tried this profile configuration in both settings.xml and
pom.xml files.
Moreover I even tried to use different properties (e.g. ${user.dir}.
${usr.home}) but in all the case I had no successful results.
Have I missed something...?
Is there any problem in managing properties..?
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven properties seem not to work in profile activation feature
Hi,
so file based profile activation can't be used without breaking down
project portability.
Is there any workaround...?
By the way there is already an issue about that on Jira...
Thanks a lot.
BR
Patrizio
nicolas de loof wrote:
You're right, properties interpolation IS NOT used to compute file path
during profile activation.
The main cause is that profiles may define / override properties values.
I agree that some properties like ${basedir} and ${settings.x} MAY be
supported, as this restriction makes the file based activation useless.
Not sure but there may allready be a Jira issue about this. Please search or
create one for this, as this SHOULD be fixed in future maven 2.x
Nico.
2008/1/16, Patrizio Munzi [EMAIL PROTECTED]:
Hi all,
I'm trying to manage profiles activations/deactivations by using the
activation tag among with the file tag.
What I would like to do is to activate a particular profile only if a
specified folder is present into the local repository.
The profile configuration I'm using is the following:
profiles
profile
idapache/id
activation
activeByDefaultfalse/activeByDefault
file
missing${settings.localRepository
}/org/apache/maven/plugins/maven-jar-plugin/2.2-SNAPSHOT/missing
/file
/activation
repositories
[...]
/repositories
pluginRepositories
[...]
/pluginRepositories
/profile
/profiles
Now, if I use the explicit path of the local repository everything works
well, instead if I use the property ${settings.localRepository} id
doesn't work. It seems that maven isn't able to give a value to the
property. I tried this profile configuration in both settings.xml and
pom.xml files.
Moreover I even tried to use different properties (e.g. ${user.dir}.
${usr.home}) but in all the case I had no successful results.
Have I missed something...?
Is there any problem in managing properties..?
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
*Patrizio Munzi*
Product Engineer
Viale Bruno Buozzi, 19 - 00197 Roma (Italy)
tel: +39 06 4543 3540
fax: +39 06 4543 3587
mobile: +39 393 7195 164
mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
web: http://www.eris4.com http://www.eris4.com/
skype: eris4_munzi skype:eris4_munzi?add
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
