[M2] maven-javadoc-plugin - Stylesheetfile Bug
The use of the property stylesheetfile in the plugin maven-javadoc-plugin and it is not function properly. I use the configuration in my pom: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId configuration outputDirectorytarget/javadoc/outputDirectory stylesheetfilejavadocsStyle.css/stylesheetfile /configuration /plugin and it does override the default javadoc stylesheet with my own. ccadete -- View this message in context: http://www.nabble.com/-M2--maven-javadoc-plugin---Stylesheetfile-Bug-tf2172542.html#a6007001 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
plexus dependency: no where to be found
Hi all, After midnight last night Maven's archiver plugin is now trying to find the following artifact. I'm not using a snapshot of the jar plugin so I don't understand what's going on. How can I fix this situation? Here's the output from the build. NOTE that everything like mvn test works well so long as a jar is not asked to be generated. Thanks, Alex Downloading: http://snapshots.maven.codehaus.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.pom [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://cvs.apache.org/maven-snapshot-repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.pom [WARNING] Unable to get resource from repository apache.snapshots (http://cvs.apache.org/maven-snapshot-repository) Downloading: http://snapshots.maven.codehaus.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.jar [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://cvs.apache.org/maven-snapshot-repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://cvs.apache.org/maven-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-archiver \ -Dversion=1.0-alpha-7-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-20060826.162339-6 2) org.apache.maven:maven-archiver:jar:2.2-SNAPSHOT 3) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-20060826.162339-6 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), snapshots (http://snapshots.maven.codehaus.org/maven2) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Maven Assembly Error
-- View this message in context: http://www.nabble.com/-M2--Maven-Assembly-Error-tf2172774.html#a6007640 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Maven Assembly Error
When I run maven-assembly-plugin version 2.1 it gives the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-assembly-plugin:2.1:assembly': Unable to find the mojo 'org.apache.ma ven.plugins:maven-assembly-plugin:2.1:assembly' in the plugin 'org.apache.maven. plugins:maven-assembly-plugin' org/codehaus/plexus/archiver/ArchiverException I run it like mvn assembly:assembly I am using in my pom: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId configuration descriptors descriptorsrc/main/assembly/release.xml/descriptor /descriptors /configuration /plugin and the assembly file: ?xml version=1.0 ? assembly idsrc/id formats formattar.gz/format formattar.bz2/format formatzip/format /formats fileSets fileSet includes includeREADME*/include includeLICENSE*/include includeNOTICE*/include includepom.xml/include /includes /fileSet fileSet directorysrc/directory /fileSet /fileSets /assembly ccadete -- View this message in context: http://www.nabble.com/-M2--Maven-Assembly-Error-tf2172791.html#a6007683 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Java System Properties in pom.xml
I've changed the parameter from String to File, but the problem still exist. I thought at first that it had something to do with the File parameter residing in a bean, so I tried with both File (fileFile) and String (stringFile) directly. Using Linux so paths should have slashes /. bean (backslash \ exists after target): [DEBUG] (s) outputFile = /home/jimisola/p4clients/lt/iso/main/product/common/target\generated-resources/buildinfo-java-common-1.4.0.0-SNAPSHOT.properties File (fileFileslash/backslash\/fileFile) [DEBUG] (f) fileFile = /home/jimisola/p4clients/lt/iso/main/product/common/slash/backslash\ String (stringFileslash/backslash\/stringFile): [DEBUG] (f) stringFile = slash/backslash\ Using File obviously replaced input (slash/backslash\) with the absolute path, but backslashes are not replaced. Am I missing out on something? Should this be handled by Maven and dependency injection mechanism (Plexus)? Regards, Jimisola -- View this message in context: http://www.nabble.com/Using-Java-System-Properties-in-pom.xml-tf2161474.html#a6010105 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plexus dependency: no where to be found
Hi Alex Please add this URL to the *new* codehaus snapshot repository: http://snapshots.repository.codehaus.org/ I think that this repo was added after crash at codehaus. It seems that new snapshots are deployed to this new repo. -- Dennis Lundberg Alex Karasulu wrote: Hi all, After midnight last night Maven's archiver plugin is now trying to find the following artifact. I'm not using a snapshot of the jar plugin so I don't understand what's going on. How can I fix this situation? Here's the output from the build. NOTE that everything like mvn test works well so long as a jar is not asked to be generated. Thanks, Alex Downloading: http://snapshots.maven.codehaus.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.pom [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://cvs.apache.org/maven-snapshot-repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.pom [WARNING] Unable to get resource from repository apache.snapshots (http://cvs.apache.org/maven-snapshot-repository) Downloading: http://snapshots.maven.codehaus.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.jar [WARNING] Unable to get resource from repository snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://cvs.apache.org/maven-snapshot-repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/plexus-archiver-1.0-alpha-7-SNAPSHOT.jar [WARNING] Unable to get resource from repository apache.snapshots (http://cvs.apache.org/maven-snapshot-repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.codehaus.plexus -DartifactId=plexus-archiver \ -Dversion=1.0-alpha-7-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-20060826.162339-6 2) org.apache.maven:maven-archiver:jar:2.2-SNAPSHOT 3) org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.1-20060826.162339-6 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), snapshots (http://snapshots.maven.codehaus.org/maven2) - 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: plexus dependency: no where to be found
Dennis Lundberg wrote: Hi Alex Please add this URL to the *new* codehaus snapshot repository: http://snapshots.repository.codehaus.org/ I think that this repo was added after crash at codehaus. It seems that new snapshots are deployed to this new repo. Still did not work. I had to check out plexus and compile install to get it to be ok for me. Others though at directory.apache.org are having this issue now too. Can someone deploy this stuff to the repo? Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Java System Properties in pom.xml
I was under the impression / would _always_ work, on either platform
when passing a path to the File class.
The String version is definitely not going to do much for you, it
doesn't know it's supposed to be a path.
Here's a quick test I whipped up, outputting whether a file exists
given a relative path to it with both Windows and Linux path
separators on both platforms:
Test.java--
import java.io.File;
public class Test {
public static void main(String[] args) {
System.out.println(args[0]: + args[0]);
File f = new File(args[0]);
System.out.println(f.getAbsolutePath() + exists? + f.exists());
}
}
-
Running this on my main machine (linux):
[EMAIL PROTECTED] ~ $ java Test Desktop\\Movies
args[0]: Desktop\Movies
/home/nick/Desktop\Movies exists? false
[EMAIL PROTECTED] ~ $ java Test Desktop/Movies
args[0]: Desktop/Movies
/home/nick/Desktop/Movies exists? true
-
Running this on my windows VM:
C:\DOCUME~1\nickjava Test Desktop/test
args[0]: Desktop/test
C:\DOCUME~1\nick\Desktop\test exists? true
C:\DOCUME~1\nickjava Test Desktop\test
args[0]: Desktop\test
C:\DOCUME~1\nick\Desktop\test exists? true
-
So as you can see, the File class is tolerant of windows, but the /
path separator works in both cases. I would just stick with that. I
don't really know exactly what issue this was causing you, unless it
was just confusion on the Windows-user side. Actual manipulation of
the file should always work if you use / separators in relative paths.
On 8/27/06, Jimisola Laursen [EMAIL PROTECTED] wrote:
I've changed the parameter from String to File, but the problem still exist.
I thought at first that it had something to do with the File parameter
residing in a bean,
so I tried with both File (fileFile) and String (stringFile) directly.
Using Linux so paths should have slashes /.
bean (backslash \ exists after target):
[DEBUG] (s) outputFile =
/home/jimisola/p4clients/lt/iso/main/product/common/target\generated-resources/buildinfo-java-common-1.4.0.0-SNAPSHOT.properties
File (fileFileslash/backslash\/fileFile)
[DEBUG] (f) fileFile =
/home/jimisola/p4clients/lt/iso/main/product/common/slash/backslash\
String (stringFileslash/backslash\/stringFile):
[DEBUG] (f) stringFile = slash/backslash\
Using File obviously replaced input (slash/backslash\) with the absolute
path, but backslashes are not replaced.
Am I missing out on something? Should this be handled by Maven and
dependency injection mechanism (Plexus)?
Regards,
Jimisola
--
View this message in context:
http://www.nabble.com/Using-Java-System-Properties-in-pom.xml-tf2161474.html#a6010105
Sent from the Maven - Users forum at Nabble.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]
Re: plexus dependency: no where to be found
Alex Karasulu wrote: Dennis Lundberg wrote: Hi Alex Please add this URL to the *new* codehaus snapshot repository: http://snapshots.repository.codehaus.org/ I think that this repo was added after crash at codehaus. It seems that new snapshots are deployed to this new repo. Still did not work. I had to check out plexus and compile install to get it to be ok for me. Others though at directory.apache.org are having this issue now too. Can someone deploy this stuff to the repo? I talked to Jason about this yesterday and he has already deployed a snapshot to the repo: http://snapshots.repository.codehaus.org/org/codehaus/plexus/plexus-archiver/1.0-alpha-7-SNAPSHOT/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is it possible to publish a WAR w/o WEB-INF/lib?
I've made quite a bit of headway this week converting AppFuse to use Maven 2[1]. Thanks to everyone on this list for their help. You can now create a new project with a simple pom.xml: project modelVersion4.0.0/modelVersion groupIdcom.mycompany/groupId artifactIdtest-appfuse/artifactId packagingwar/packaging version1.0/version repositories repository idappfuse/id urlhttp://static.appfuse.org/repository/url /repository /repositories dependencies dependency groupIdorg.appfuse/groupId artifactIdappfuse-struts-war/artifactId version2.0-SNAPSHOT/version typewar/type /dependency /dependencies /project The problem with this setup is you won't get the WARs dependencies in your classpath. I've found that including the JAR and the WAR as dependencies solves this issue. dependencies dependency groupIdorg.appfuse/groupId artifactIdappfuse-struts/artifactId version2.0-SNAPSHOT/version /dependency dependency groupIdorg.appfuse/groupId artifactIdappfuse-struts-war/artifactId version2.0-SNAPSHOT/version typewar/type /dependency /dependencies To control the dependencies that end up in your final WEB-INF/lib, I've found it necessary to do the following: plugin artifactIdmaven-war-plugin/artifactId configuration dependentWarExcludesWEB-INF/lib/dependentWarExcludes /configuration /plugin Is it possible to adjust appfuse-struts-war's pom.xml so it builds it's own WAR correctly (when using mvn package), but installs the WAR w/o any JARs? That seems like the best way to set things up so dependencies can still be a part of the end user's project, and they can get the WAR overlaid w/o getting JARs from it. Thanks, Matt [1] http://raibledesigns.com/page/rd?entry=appfuse_2_0_status1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Help:Describe Error
When I execute the following command: mvn help:describe -DgroupId=org.apache.maven.archetypes -DartifactId=maven-archetype-webapp The response is an error message, with a null pointer exception. I known that this artifact is not a plugin, is an archetype. I guess, is that maven is not cheking if the artifact that I request is really a plugin that I can describe. -- View this message in context: http://www.nabble.com/-M2--Help%3ADescribe-Error-tf2173974.html#a6011356 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Java System Properties in pom.xml
Nick Veys wrote: I was under the impression / would _always_ work, on either platform when passing a path to the File class. Me too. That's why I tested on Linux with backslashes in the path.. So as you can see, the File class is tolerant of windows, but the / path separator works in both cases. I would just stick with that. I don't really know exactly what issue this was causing you, unless it was just confusion on the Windows-user side. Actual manipulation of the file should always work if you use / separators in relative paths. I was started to assume that there was a bug in Maven while in fact the JRE was a fault. Seems kind of odd that it doesn't work both ways. One would think that Sun would have taken care of that. Anyway, problem solved. Thank you for your little test. Regards, Jimisola -- View this message in context: http://www.nabble.com/Using-Java-System-Properties-in-pom.xml-tf2161474.html#a6011493 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Time to put some structure to Maven User FAQ on Wiki?
Hi! I had a look at the wiki pages concerning Maven User FAQ on the Wiki http://docs.codehaus.org/display/MAVENUSER/FAQs-1 http://docs.codehaus.org/display/MAVENUSER/FAQs and must say that there is no structure which makes it hard to find things. Have anyone thought of restructuring it a bit? Ideally, there would be a two main sections for - Using Maven: locating plugins, repositories, Ant, reporting, dependencies, ... - Developing for Maven (Plugins) I'd appreciate input as I believe that providing a better structure would make it a) easier for people to use and b) easier for users to contribute. Regards, Jimisola -- View this message in context: http://www.nabble.com/Time-to-put-some-structure-to-Maven-User-FAQ-on-Wiki--tf2174095.html#a6011646 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time to put some structure to Maven User FAQ on Wiki?
Yes, we talked about this on the dev list some time back We should start a cokbook section that has some detailed examples. On 28/08/06, Jimisola Laursen [EMAIL PROTECTED] wrote: Hi! I had a look at the wiki pages concerning Maven User FAQ on the Wiki http://docs.codehaus.org/display/MAVENUSER/FAQs-1 http://docs.codehaus.org/display/MAVENUSER/FAQs and must say that there is no structure which makes it hard to find things. Have anyone thought of restructuring it a bit? Ideally, there would be a two main sections for - Using Maven: locating plugins, repositories, Ant, reporting, dependencies, ... - Developing for Maven (Plugins) I'd appreciate input as I believe that providing a better structure would make it a) easier for people to use and b) easier for users to contribute. Regards, Jimisola -- View this message in context: http://www.nabble.com/Time-to-put-some-structure-to-Maven-User-FAQ-on-Wiki--tf2174095.html#a6011646 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Apache Maven - http://maven.apache.org Better Builds with Maven book - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: plexus dependency: no where to be found
You are using a snapshot repository for plugins somewhere I suspect, though - which is the reason you'd be getting these updates. - Brett On 28/08/06, Alex Karasulu [EMAIL PROTECTED] wrote: Dennis Lundberg wrote: Hi Alex Please add this URL to the *new* codehaus snapshot repository: http://snapshots.repository.codehaus.org/ I think that this repo was added after crash at codehaus. It seems that new snapshots are deployed to this new repo. Still did not work. I had to check out plexus and compile install to get it to be ok for me. Others though at directory.apache.org are having this issue now too. Can someone deploy this stuff to the repo? Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Apache Maven - http://maven.apache.org Better Builds with Maven book - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time to put some structure to Maven User FAQ on Wiki?
Brett Porter wrote: Yes, we talked about this on the dev list some time back We should start a cokbook section that has some detailed examples. That sounds really useful. Is there a proposal for a FAQ / CookBook restructuring? Was there discussion a while back on restructing the whole documentation on the site etc? While at it, User Contributed on maven.apache.org would clearer if it said FAQ (User Contributed). I often come back to the documentation - it's essential (especially for Maven newbies). Now I often find it lacking or hard to find. The latter has become better since I am getting acquainted with Maven's documentation (Guides, Wiki etc on Maven site, mailing lists and BBwM boo). Kind regards, Jimisola -- View this message in context: http://www.nabble.com/Time-to-put-some-structure-to-Maven-User-FAQ-on-Wiki--tf2174095.html#a6012632 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time to put some structure to Maven User FAQ on Wiki?
The problem with docs is that they'll never be good enough :) Most of the plugin documentation has been rewritten recently which is very helpful, but it still needs to be easily locatable from the web site. The same question was asked on dev@ so I'll post the list of things we had queued up there. - Brett On 28/08/06, Jimisola Laursen [EMAIL PROTECTED] wrote: Brett Porter wrote: Yes, we talked about this on the dev list some time back We should start a cokbook section that has some detailed examples. That sounds really useful. Is there a proposal for a FAQ / CookBook restructuring? Was there discussion a while back on restructing the whole documentation on the site etc? While at it, User Contributed on maven.apache.org would clearer if it said FAQ (User Contributed). I often come back to the documentation - it's essential (especially for Maven newbies). Now I often find it lacking or hard to find. The latter has become better since I am getting acquainted with Maven's documentation (Guides, Wiki etc on Maven site, mailing lists and BBwM boo). Kind regards, Jimisola -- View this message in context: http://www.nabble.com/Time-to-put-some-structure-to-Maven-User-FAQ-on-Wiki--tf2174095.html#a6012632 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Apache Maven - http://maven.apache.org Better Builds with Maven book - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Java System Properties in pom.xml
On 8/27/06, Jimisola Laursen [EMAIL PROTECTED] wrote: Nick Veys wrote: I was under the impression / would _always_ work, on either platform when passing a path to the File class. Me too. That's why I tested on Linux with backslashes in the path.. So as you can see, the File class is tolerant of windows, but the / path separator works in both cases. I would just stick with that. I don't really know exactly what issue this was causing you, unless it was just confusion on the Windows-user side. Actual manipulation of the file should always work if you use / separators in relative paths. I was started to assume that there was a bug in Maven while in fact the JRE was a fault. Seems kind of odd that it doesn't work both ways. One would think that Sun would have taken care of that. Anyway, problem solved. Yeah, thats why I said you can just use *forward slash* for paths. Backslashes are not platform neutral in Java. Thank you for your little test. Regards, Jimisola -- View this message in context: http://www.nabble.com/Using-Java-System-Properties-in-pom.xml-tf2161474.html#a6011493 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond
Re: Using Java System Properties in pom.xml
I was started to assume that there was a bug in Maven while in fact the JRE was a fault. Seems kind of odd that it doesn't work both ways. One would think that Sun would have taken care of that. Anyway, problem solved. Yeah, thats why I said you can just use *forward slash* for paths. Backslashes are not platform neutral in Java. It was not obvious that it was a just as in must :) Now, we know. Regards, Jimisola -- View this message in context: http://www.nabble.com/Using-Java-System-Properties-in-pom.xml-tf2161474.html#a6013188 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Java System Properties in pom.xml
On 8/27/06, Jimisola Laursen [EMAIL PROTECTED] wrote: I was started to assume that there was a bug in Maven while in fact the JRE was a fault. Seems kind of odd that it doesn't work both ways. One would think that Sun would have taken care of that. Anyway, problem solved. Yeah, thats why I said you can just use *forward slash* for paths. Backslashes are not platform neutral in Java. It was not obvious that it was a just as in must :) Touché ;) Now, we know. Regards, Jimisola -- View this message in context: http://www.nabble.com/Using-Java-System-Properties-in-pom.xml-tf2161474.html#a6013188 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Eric Redmond http://codehaus.org/~eredmond
Re: [m2] Incorrect manifest generation in jar file
Alexandre Poitras wrote: I think you can espace new line by using the '\' character like in properties files. I have never tested for new lines but it works for quotes so it should work. For example : a string with a continuation line \ continuation line On 12/6/05, Arnaud Bailly [EMAIL PROTECTED] wrote: Hi, I had a very strange problem which I don't know the ultimate responsibilit: some bug or feature of maven or one of its component. In one project, I kept having exceptions NoClassDefFoundError while trying to load classes from the generated jar file. After some investigations, I found this was caused by the incorrect format of the MANIFEST.MF file, which itself was caused by the description tag in the pom containing newline characters ! This tag is copied verbatim as the Specification-Title attribute of the manifest, so I think newlines should be escaped. -- Arnaud Bailly - Ingénieur de Recherche NORSYS 1, rue de la Cense des Raines ZAC du Moulin 59710 ENNEVELIN Tel : (33) 3 28 76 56 76 Fax : (33) 3 28 76 57 00 Web : http://www.norsys.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ufortunately the description element in the pom also appears in the generated site. That doesn't look very good with backslashes in it :( -- View this message in context: http://www.nabble.com/-m2--Incorrect-manifest-generation-in-jar-file-tf686887.html#a6013364 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Incorrect manifest generation in jar file
On 8/27/06, ericr [EMAIL PROTECTED] wrote: Ufortunately the description element in the pom also appears in the generated site. That doesn't look very good with backslashes in it :( IMO the Specification-Title should come from the name element, not the description. There's definitely a JIRA issue for this, but I don't know how it was resolved. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] copy of Central Repository
Hi Jeff, I am sorry I did not understand your original mail. Further reading confirms that Proximity is what I am looking for. Could you please clarify one question before I charge down this path ? I actually control the internal.central repository. I don't allow developers to pollute the internal.central repository with any version of the software they want. Before the internal.central repository is upgraded we get a consensus from the development team. This ensures that we don't get any library conflicts. I controlled this in maven.1.x by ensuring that the internal.central repository was owned by xxx and xxx's localRepository was pointing to internal.central. This ensured that only xxx could place libraries into the repository and all the developers would get an error if the library did not exist. My initial reading of Proximity indicates that it will download from repo1.maven.org (or from where ever) _automatically_ when it can't find the library in internal.central. Is there a way of controlling this. Would I be able to control who can _automatically_ populate internal.central and give an error to the others ? Thanks again for you assistance in this issue. Thanks Lakshman -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Friday, 25 August 2006 10:24 PM To: 'Maven Users List' Subject: RE: [m2] copy of Central Repository That's fine, these products allow manual installation as well (in fact, they expect you to). This handles the use cases of using commercial artifacts (Oracle, MQ Series, and Java itself, etc.) and installing artifacts from your own company's products. By your statement, I wonder if you misunderstand how they are used/what they do. FYI, We use Proximity; it works great. I suggest reading its docs/site info. -Original Message- From: Lakshman Srilakshmanan [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 3:20 AM To: Maven Users List Cc: [EMAIL PROTECTED] Subject: RE: [m2] copy of Central Repository Hi We can't do this because from time to time we may need to download files manually and install it. Thanks Lakshman -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey De Smet Sent: Friday, 25 August 2006 5:57 PM To: users@maven.apache.org Subject: Re: [m2] copy of Central Repository Putting up a maven proxy might solve your problem: the first time a jar is needed it downloads it from the central repo and caches it. There are 3 free implementations I know of: maven-proxy (from the maven guys): beta?, abandoned in favor of Archiva Archiva (from the maven guys): beta, needs to be build from source, but has some positive remarks on this list Proximity (from 3th party): sounds more stable, has had a bunch of releases and some positive remarks on this list Check this list for Archiva and proximity. Lakshman Srilakshmanan wrote, On 2006-08-25 8:53 AM: Hi All, In maven 1.x I could execute maven once on a project and build my local repository. I could then copy it on to my company's central server and get all the developers to refer to this for updates. When I needed a new plugin or dependency, I could run maven 1.x against ibiblio and follow the above process. The above strategy ensured that we had only the plugins dependencies we needed and not the whole central repository of 5G. I am not going into the details of how I kept this up-to-date as it would side track the main issue that I wish to discuss. Now, in maven 2 I did the same process as described above. The build started breaking, with errors such as -- plugin 'xxx' does not exist or no valid version could be found --. Further investigation revealed this problem was due to two missing files in my repository. a) maven-metadata.xml b) maven-metadata.xml.sha1 In my local repository these files are named as a) maven-metadata-central.xml b) maven-metadata-central.xml.sha1 so when I copied my local repository to my company's central repository the above files caused the problem. When I renamed the files as required, maven 2 was happy and everything started to work again. So my question is, is there a easier way of getting the required components from maven central repository copied to my company's central server without having to take a full copy ? Well, an alternative is to create a script to traverse the repository and rename the files as required. I would much appreciate to hear from anyone who has solved this problem or is there a tool/process that I have overlooked. Thanks in advance Lakshman -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
RE: [m2] copy of Central Repository
Hi Marc, Yes, I have done -U on my build. All that the -U does is reach out to the central repository and grab the latest version of the libraries/plugin you are using. We started using mvn deploy:deploy-file, but then realised that if we did a full build on the box that hosts our internal repo - this would do the job - and it does. However, I would like to know if there is a better or 'proper' solution to this. The problem I have is making the internal repos mentioned in your email above into an internal central repository that developers could use as a central repository. I hope I have clarified my problem to make it more clear. Thanks Lakshman -Original Message- From: Marc L. Veary [mailto:[EMAIL PROTECTED] Sent: Friday, 25 August 2006 7:23 PM To: 'Maven Users List' Subject: RE: [m2] copy of Central Repository Hi Lakshman, We have a number of these files some are *-local.xml, some are *-ibiblio.xml, some are the name of the repo from setting.xml on dev machines. I'm not an expert at this, and please excuse if I am stating the obvious, but did you try using -U switch? Kind regards, -- Marc -Original Message- From: Lakshman Srilakshmanan [mailto:[EMAIL PROTECTED] Sent: 25 August 2006 09:18 To: Maven Users List Subject: RE: [m2] copy of Central Repository Hi Marc, I did a full build on the box that hosts our internal repo, but as explained, it did not work for me. I have also explained, below, my finding why it did not work. Could you please confirm the name of the following files in your repository. a) maven-metadata*.xml b) maven-metadata*.xml.sha1 Is it possible you are still looking at the central server at http://repo1.maven.org/maven2 ?? Thanks Lakshman -Original Message- From: Marc L. Veary [mailto:[EMAIL PROTECTED] Sent: Friday, 25 August 2006 5:40 PM To: 'Maven Users List' Subject: RE: [m2] copy of Central Repository Hi. We started using mvn deploy:deploy-file, but then realised that if we did a full build on the box that hosts our internal repo - this would do the job - and it does. However, I would like to know if there is a better or 'proper' solution to this. Kind regards, -- Marc -Original Message- From: Lakshman Srilakshmanan [mailto:[EMAIL PROTECTED] Sent: 25 August 2006 07:54 To: Maven Users List Subject: [m2] copy of Central Repository Hi All, In maven 1.x I could execute maven once on a project and build my local repository. I could then copy it on to my company's central server and get all the developers to refer to this for updates. When I needed a new plugin or dependency, I could run maven 1.x against ibiblio and follow the above process. The above strategy ensured that we had only the plugins dependencies we needed and not the whole central repository of 5G. I am not going into the details of how I kept this up-to-date as it would side track the main issue that I wish to discuss. Now, in maven 2 I did the same process as described above. The build started breaking, with errors such as -- plugin 'xxx' does not exist or no valid version could be found --. Further investigation revealed this problem was due to two missing files in my repository. a) maven-metadata.xml b) maven-metadata.xml.sha1 In my local repository these files are named as a) maven-metadata-central.xml b) maven-metadata-central.xml.sha1 so when I copied my local repository to my company's central repository the above files caused the problem. When I renamed the files as required, maven 2 was happy and everything started to work again. So my question is, is there a easier way of getting the required components from maven central repository copied to my company's central server without having to take a full copy ? Well, an alternative is to create a script to traverse the repository and rename the files as required. I would much appreciate to hear from anyone who has solved this problem or is there a tool/process that I have overlooked. Thanks in advance Lakshman - 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]
