Re: Plugin to validate the class file version of built artifacts?
2009/3/17 Stephen Connolly stephen.alan.conno...@gmail.com: google this animal sniffer Kohsuke it should give you what you're after Thanks Stephen, this was what I was looking for! For the email archives: http://animal-sniffer.dev.java.net Ringo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Artifact version and fileset filtering
Hi, Le Thu, 12 Mar 2009 12:48:23 +0100, Landais Gabriel gland...@bluexml.com a écrit : I want to set the parent version of a generated model through an archetype:generate. It has to be set to the archetype version as parent pom and archetype share the same version (both are modules of my project). I've finally created a mojo able to update all versions in my project, including superpom used by artifact. It works great in my project, using best practice in module versioning (at least I tried!). The root pom declares the version and all modules declare version in parent pom version. I parse poms with JDOM, and modules are processed directly by Maven, so no specific code for module handling. Sources available on demand. Gabriel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven vs. Hudson
Hello, Can anybody tell me what are de differences between Maven and Hudson? Thanks in advance, Luke
Re: Maven vs. Hudson
Hudson planify and run any maven goal and give you the status of your project. I installed hudson and configured it to checkout my project from svn and run mvn clean package every night. If anybody break a test or introduce any error, hudson send an email to our mailing list and i also can see reports made by hudson about the time it takes to build the project and so on... It's http://en.wikipedia.org/wiki/Continuous_integration � wrote: Hello, Can anybody tell me what are de differences between Maven and Hudson? Thanks in advance, Luke - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Activation of multiple profiles at the same time
Hello,
I'm facing some behavior regarding activation of multiple profiles within a
pom.xml, which is contrary to what I was expecting. Maybe someone can help.
I have a pom consisting of three profiles:
profiles
profile!-- Set tools.jar for most SUN JDKs. --
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
toolsJAR${java.home}/../lib/tools.jar/toolsJAR
/properties
/profile
profile!-- Mac OSX Java JDK doesn't has separate tools.jar. --
idtools-jar-mac/id
activation
activeByDefaultfalse/activeByDefault
os
familyMac/family
/os
/activation
properties
toolsJAR${java.home}/../Classes/classes.jar/toolsJAR
/properties
/profile
!--
Add external dependency to StAX API (JSR-173) and Woodstox (which is an
implementation of JSR-173). Both are not part of JDK 1.5. Starting from
JDK 1.6 the built-in implementation is used.
--
profile
idjdk1.5/id
activation
activeByDefaultfalse/activeByDefault
jdk1.5/jdk
/activation
dependencies
dependency
groupIdorg.codehaus.woodstox/groupId
artifactIdwoodstox-core-asl/artifactId
version4.0.3/version
/dependency
/dependencies
/profile
/profiles
What I want to achieve is that for platforms other than Mac OS _and_ Java
version 1.5.* the profiles default _and_ jdk1.5 will be activated. For
platforms other than Mac OS _and_ Java 1.6 only the profile default should
be activated. Finally, for the Mac OS platform the profile tools-jar-mac
_and_ jdk1.5 should be activated for Java 1.5; while only profile
tools-jar-mac should be activated for Java 1.6.
It seems to me that activation of profiles is exclusive, i.e., only one
profile is activated at a time. For instance, when using mvn
help:active-profiles on a Linux machine with Java 1.5 SDK, I see only
profile jdk1.5 activated, but what I was expecting is that default would
be activated as well. Is there any way to achieve automatic activation of
multiple profiles apart from explicitly stating profiles via -P on the
command line.
-- Thorsten
--
View this message in context:
http://www.nabble.com/Activation-of-multiple-profiles-at-the-same-time-tp22576838p22576838.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Extracting classpath for an application from maven
Thanks , i think thats the best and proper way to get it .! On Wed, Mar 18, 2009 at 1:18 PM, Nicolas R. nromane...@jaxio.com wrote: Hello, Try to run 'mvn dependency:build-classpath' Here is the doc: http://maven.apache.org/plugins/maven-dependency-plugin/plugin-info.html Nicolas -- http://www.springfuse.com www.springfuse.com Roman Kournjaev wrote: Hi All I have a maven based application, well now i want to run it in cmd mode, it means just executing the compiled class. How do i extract the classpath for this application from my pom easilly ? Thanks in advance. Roman -- View this message in context: http://www.nabble.com/Extracting-classpath-for-an-application-from-maven-tp22386575p22576977.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Extracting classpath for an application from maven
Hello, Try to run 'mvn dependency:build-classpath' Here is the doc: http://maven.apache.org/plugins/maven-dependency-plugin/plugin-info.html Nicolas -- http://www.springfuse.com www.springfuse.com Roman Kournjaev wrote: Hi All I have a maven based application, well now i want to run it in cmd mode, it means just executing the compiled class. How do i extract the classpath for this application from my pom easilly ? Thanks in advance. Roman -- View this message in context: http://www.nabble.com/Extracting-classpath-for-an-application-from-maven-tp22386575p22576977.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Artifact version and fileset filtering
how is this different from running mvn -N versions:update-child-modules 2009/3/18 Landais Gabriel gland...@bluexml.com Hi, Le Thu, 12 Mar 2009 12:48:23 +0100, Landais Gabriel gland...@bluexml.com a écrit : I want to set the parent version of a generated model through an archetype:generate. It has to be set to the archetype version as parent pom and archetype share the same version (both are modules of my project). I've finally created a mojo able to update all versions in my project, including superpom used by artifact. It works great in my project, using best practice in module versioning (at least I tried!). The root pom declares the version and all modules declare version in parent pom version. I parse poms with JDOM, and modules are processed directly by Maven, so no specific code for module handling. Sources available on demand. Gabriel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
compile-time only depend - how to reference without generating transitive dependency?
AIUI, compile scope means compile, test and run, and generates a transitive dependency. There are some dependencies that are compile-time only, for example annotations, and Java specification jars - i.e. API-only jars that have no implementation. What is the best way to define such a dependency? The Maven site suggests using provided, but this does not solve the problem. Maybe there should be acompile-only scope? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven vs. Hudson
Maven is a project centric build tool Hudson is an build automation server. Which can automate the the running of Ant or Maven or Scripts. --- Thank You... Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- 2009/3/18 Łukasz Warchoł warchol...@gmail.com Hello, Can anybody tell me what are de differences between Maven and Hudson? Thanks in advance, Luke
need persistence.xml for building and testing, but not in final artifact
I am trying to create a generic JPA jar that just has my JPA related classes. Then I plan to have another jar with my domain objects for use in various projects. What I need to do, is have my persistence.xml in my src/main/resources for building and testing, but omitted in my final jar. This way my domain.jar can add the persistence.xml I tried: *resources resource directorysrc/main/resources/directory excludes excludeapplicationContext*.xml/exclude exclude**/persistence.xml/exclude /excludes filteringtrue/filtering /resource resource directorysrc/main/resources/directory includes includeapplicationContext*.xml/include /includes excludes exclude**/persistence.xml/exclude /excludes filteringfalse/filtering /resource /resources testResources testResource directorysrc/main/resources/directory includes include**/persistence.xml/include /includes filteringtrue/filtering /testResource testResource directorysrc/test/resources/directory filteringtrue/filtering excludes excludedatabase.properties/exclude /excludes /testResource /testResources * But it appears that my hibernate3 plugin is not finding it in the classpath. I found this posting http://www.nabble.com/Hibernate3-Maven-Plugin-NPE-td18836071.html But no resolution. Can anyone help? --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com ---
RE: Activation of multiple profiles at the same time
It seems to me that activation of profiles is exclusive, i.e., only one profile
is activated at a time.
No you can cumulate profiles
profiles
profile
idid1/id
activationactiveByDefaulttrue/activeByDefault/activation
/profile
profile
idid2/id
activationactiveByDefaulttrue/activeByDefault/activation
/profile
/profiles
Mvn help:active-profiles
The following profiles are active:
- id1 (source: pom)
- id2 (source: pom)
- dev (source: settings.xml)
- delphi (source: settings.xml)
- delphi (source: settings.xml)
-Message d'origine-
De : TM [mailto:thorsten.moel...@unibas.ch]
Envoyé : mercredi 18 mars 2009 12:08
À : users@maven.apache.org
Objet : Activation of multiple profiles at the same time
Hello,
I'm facing some behavior regarding activation of multiple profiles within a
pom.xml, which is contrary to what I was expecting. Maybe someone can help.
I have a pom consisting of three profiles:
profiles
profile!-- Set tools.jar for most SUN JDKs. --
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
toolsJAR${java.home}/../lib/tools.jar/toolsJAR
/properties
/profile
profile!-- Mac OSX Java JDK doesn't has separate tools.jar. --
idtools-jar-mac/id
activation
activeByDefaultfalse/activeByDefault
os
familyMac/family
/os
/activation
properties
toolsJAR${java.home}/../Classes/classes.jar/toolsJAR
/properties
/profile
!--
Add external dependency to StAX API (JSR-173) and Woodstox (which is an
implementation of JSR-173). Both are not part of JDK 1.5. Starting from
JDK 1.6 the built-in implementation is used.
--
profile
idjdk1.5/id
activation
activeByDefaultfalse/activeByDefault
jdk1.5/jdk
/activation
dependencies
dependency
groupIdorg.codehaus.woodstox/groupId
artifactIdwoodstox-core-asl/artifactId
version4.0.3/version
/dependency
/dependencies
/profile
/profiles
What I want to achieve is that for platforms other than Mac OS _and_ Java
version 1.5.* the profiles default _and_ jdk1.5 will be activated. For
platforms other than Mac OS _and_ Java 1.6 only the profile default should be
activated. Finally, for the Mac OS platform the profile tools-jar-mac
_and_ jdk1.5 should be activated for Java 1.5; while only profile
tools-jar-mac should be activated for Java 1.6.
It seems to me that activation of profiles is exclusive, i.e., only one profile
is activated at a time. For instance, when using mvn help:active-profiles on a
Linux machine with Java 1.5 SDK, I see only profile jdk1.5 activated, but
what I was expecting is that default would be activated as well. Is there any
way to achieve automatic activation of multiple profiles apart from explicitly
stating profiles via -P on the command line.
-- Thorsten
--
View this message in context:
http://www.nabble.com/Activation-of-multiple-profiles-at-the-same-time-tp22576838p22576838.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven vs. Hudson
The comparison would be better if you said Hudson vs CruseControl or Maven vs Ant --Original Message-- From: Łukasz Warchoł To: users@maven.apache.org ReplyTo: Maven Users List Sent: Mar 18, 2009 6:50 AM Subject: Maven vs. Hudson Hello, Can anybody tell me what are de differences between Maven and Hudson? Thanks in advance, Luke bob.aie...@ieee.org - http://www.linkedin.com/in/BobAiello - Sent via BlackBerry
RE: Install artifact during build
Does anyone know how to accomplish this (using local repository)? -Original Message- From: Wendy Smoak [mailto:wsm...@gmail.com] Sent: Monday, March 16, 2009 10:39 AM To: Maven Users List Subject: Re: Install artifact during build On Mon, Mar 16, 2009 at 7:31 AM, Will Hoover java.whoo...@gmail.com wrote: Is there a way to install an artifact based upon a path defined in pom? I need to have a parent pom that installs a set of proprietary artifacts based upon a path provided by a child pom... Is there a way to do this? Are you trying to install additional jars into your local Maven repository, or something else? -- Wendy - 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
Searching for a repo1.maven.org administrator
Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Install artifact during build
either write a plugin... and how do you get that into their local repository... or maybe use the exec plugin 2009/3/18 Will Hoover java.whoo...@gmail.com Does anyone know how to accomplish this (using local repository)? -Original Message- From: Wendy Smoak [mailto:wsm...@gmail.com] Sent: Monday, March 16, 2009 10:39 AM To: Maven Users List Subject: Re: Install artifact during build On Mon, Mar 16, 2009 at 7:31 AM, Will Hoover java.whoo...@gmail.com wrote: Is there a way to install an artifact based upon a path defined in pom? I need to have a parent pom that installs a set of proprietary artifacts based upon a path provided by a child pom... Is there a way to do this? Are you trying to install additional jars into your local Maven repository, or something else? -- Wendy - 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: Searching for a repo1.maven.org administrator
AFAIK, There is no single point of contact. for #1 try contacting ibm for #2 try contacting bouncycastle for #3 try contacting eclipse 2009/3/18 Costin Caraivan ccarai...@axway.com Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
Oh, and before I forget, you will not be able to get the bad artifacts fixed... only superceded with newer versions... once an artifact is in repo1 it's there for good 2009/3/18 Stephen Connolly stephen.alan.conno...@gmail.com AFAIK, There is no single point of contact. for #1 try contacting ibm for #2 try contacting bouncycastle for #3 try contacting eclipse 2009/3/18 Costin Caraivan ccarai...@axway.com Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
I know that some stuff is just pulled in from elsewhere, but do you want to tell me that things get uploaded there with 0 review? :| Stephen Connolly-2 wrote: AFAIK, There is no single point of contact. for #1 try contacting ibm for #2 try contacting bouncycastle for #3 try contacting eclipse 2009/3/18 Costin Caraivan ccarai...@axway.com Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578774.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
If I establish to the repo1 maintainers that I own the mycompany.com, then I am responsible for all artifacts with com.mycompany as the group Id. repo1 will not stop me pushing bad artifacts... Note I'm not saying that this is the way it should be... 2009/3/18 Costin Caraivan ccarai...@axway.com I know that some stuff is just pulled in from elsewhere, but do you want to tell me that things get uploaded there with 0 review? :| Stephen Connolly-2 wrote: AFAIK, There is no single point of contact. for #1 try contacting ibm for #2 try contacting bouncycastle for #3 try contacting eclipse 2009/3/18 Costin Caraivan ccarai...@axway.com Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22578774.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
Stephen Connolly-2 wrote: If I establish to the repo1 maintainers that I own the mycompany.com, then I am responsible for all artifacts with com.mycompany as the group Id. repo1 will not stop me pushing bad artifacts... Note I'm not saying that this is the way it should be... Thanks for the reply. However, couldn't some minimap checks be made? Like checking that all the dependencies can be found on the repo or the repos specified in the poms? -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22579516.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Searching for a repo1.maven.org administrator
Costin Caraivan wrote: Stephen Connolly-2 wrote: If I establish to the repo1 maintainers that I own the mycompany.com, then I am responsible for all artifacts with com.mycompany as the group Id. repo1 will not stop me pushing bad artifacts... Note I'm not saying that this is the way it should be... Thanks for the reply. However, couldn't some minimap checks be made? Like checking that all the dependencies can be found on the repo or the repos specified in the poms? Sorry, that was supposed to be *minimal* :) -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22578599p22579520.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
how to EMMA-instrument dependencies
Hi, I have a Maven 2 project that depends on a number of other Maven 2 projects that are built locally and installed into the local repository. I need to instrument some of the dependency JARs with the EMMA coverage tool and have Maven run unit tests against instrumented JARs rather than the original dependencies. The emma-maven-plugin (http://mojo.codehaus.org/emma-maven-plugin) does not seem to be of much help as it does not seem to support this scenario. Of course, it would be ideal if the emma-maven-plugin had support for this. In fact, the plugin has an 'instrumentationPaths' parameter which can be used to instrument classes from arbitrary directories; so I think dependencies can be copied, unpacked, instrumented this way and passed to maven-surefire-plugin via the 'classesDirectory' parameter; but in this case both the instrumented classes and original dependencies both appear on the test classpath, which sounds wrong. Actually, I can bypass emma-maven-plugin and run EMMA instrumentor via exec-maven-plugin, but again, it looks like the only way to pass the instrumented classes to surefire is via the 'classesDirectory' or 'additionalClasspathElements' parameter, which is the same problem as above, which makes me think this is not solely emma-maven-plugin's problem (hence posting to this list). What would be the right Maven way to achieve the goal? I am new to Maven so I am sorry if I am missing something obvious. I spent several days trying to find a solution, to no success. In fact, I have some control over the dependency projects so I think I can build them so that the resulting JARs will contain instrumented classes (or I can instrument JARs separately and 'install:install-file' them as separate components), but this is undesirable. I hope I am making sense. Thank you, Vasiliy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: how to EMMA-instrument dependencies
Hi
From my experience with emma I use a ant call after the compilation phase.
Ant is going much more power than the emma plugin
!--
pour instrumenter l'appli web
mvn install -P instrument
--
profile
idinstrument/id
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprocess-classes/phase
configuration
tasks
ant
antfile=${basedir}/instrument_for_coverage.xml
target name=instrument/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
And use the overwrite mode in the ant, then only your class are going to be
instrumended if you active this option :
target name=instrument depends=init
echoInstrumenting the classes/echo
emma enabled=${emma.enabled}
instr instrpathref=ServeurJava.classpath
metadatafile=${metadatafile}
merge=true
mode=overwrite
filter value=${emma.filter} /
/instr
/emma
/target
Thus running
Mvn package -P instrument
produce an instrumented war
And
Mvn package
Produce a regular one
Good luck, emma rocks !!
-Message d'origine-
De : vasiliy.bara...@sun.com [mailto:vasiliy.bara...@sun.com]
Envoyé : mercredi 18 mars 2009 15:32
À : users@maven.apache.org
Objet : how to EMMA-instrument dependencies
Hi,
I have a Maven 2 project that depends on a number of other Maven 2 projects
that are built locally and installed into the local repository.
I need to instrument some of the dependency JARs with the EMMA coverage tool
and have Maven run unit tests against instrumented JARs rather than the
original dependencies. The emma-maven-plugin
(http://mojo.codehaus.org/emma-maven-plugin) does not seem to be of much help
as it does not seem to support this scenario.
Of course, it would be ideal if the emma-maven-plugin had support for this. In
fact, the plugin has an 'instrumentationPaths' parameter which can be used to
instrument classes from arbitrary directories; so I think dependencies can be
copied, unpacked, instrumented this way and passed to maven-surefire-plugin via
the 'classesDirectory' parameter; but in this case both the instrumented
classes and original dependencies both appear on the test classpath, which
sounds wrong.
Actually, I can bypass emma-maven-plugin and run EMMA instrumentor via
exec-maven-plugin, but again, it looks like the only way to pass the
instrumented classes to surefire is via the 'classesDirectory' or
'additionalClasspathElements' parameter, which is the same problem as above,
which makes me think this is not solely emma-maven-plugin's problem (hence
posting to this list).
What would be the right Maven way to achieve the goal? I am new to Maven so I
am sorry if I am missing something obvious. I spent several days trying to find
a solution, to no success.
In fact, I have some control over the dependency projects so I think I can
build them so that the resulting JARs will contain instrumented classes (or I
can instrument JARs separately and 'install:install-file'
them as separate components), but this is undesirable.
I hope I am making sense.
Thank you,
Vasiliy
-
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: Is there a way to verify/check/repair a local repository ?
I don't even know what that has to do with it but ok here goes:I currently have: -rw-r--r-- 1 tich tich 173558 2009-03-12 03:52 common-op-25-20090311.225250-1.jar -rw-r--r-- 1 tich tich 1719 2009-03-12 03:52 common-op-25-20090311.225250-1.pom -rw-r--r-- 1 tich tich 175402 2009-03-12 18:20 common-op-25-20090312.212423-6.jar -rw-r--r-- 1 tich tich 1719 2009-03-12 18:20 common-op-25-20090312.212423-6.pom -rw-r--r-- 1 tich tich 175402 2009-03-13 10:10 common-op-25-20090313.122002-8.jar -rw-r--r-- 1 tich tich 1719 2009-03-13 10:10 common-op-25-20090313.122002-8.pom -rw-r--r-- 1 tich tich 175398 2009-03-16 11:15 common-op-25-20090316.04-11.jar -rw-r--r-- 1 tich tich 1719 2009-03-16 11:15 common-op-25-20090316.04-11.pom -rw-r--r-- 1 tich tich 177137 2009-03-16 19:18 common-op-25-20090317.001852-13.jar -rw-r--r-- 1 tich tich 1719 2009-03-16 19:18 common-op-25-20090317.001852-13.pom -rw-r--r-- 1 tich tich 175398 2009-03-16 11:15 common-op-25-SNAPSHOT.jar -rw-r--r-- 1 tich tich 1719 2009-03-16 11:15 common-op-25-SNAPSHOT.pom Notice the size of -SNAPSHOT and how it matches the -11 build and not the latest -13? Now for my metadata files: -rw-r--r-- 1 tich tich348 2009-03-18 09:29 maven-metadata-imc public-snapshots.xml -rw-r--r-- 1 tich tich 40 2009-03-18 09:29 maven-metadata-imc public-snapshots.xml.sha1 -rw-r--r-- 1 tich tich348 2009-03-18 09:29 maven-metadata-imc repo.xml -rw-r--r-- 1 tich tich348 2009-03-16 19:18 maven-metadata-imc.repo.xml -rw-r--r-- 1 tich tich 40 2009-03-18 09:29 maven-metadata-imc repo.xml.sha1 -rw-r--r-- 1 tich tich 40 2009-03-16 19:18 maven-metadata-imc.repo.xml.sha1 They all have the same thing: groupIdcom.imc/groupId artifactIdcommon-op/artifactId version25-SNAPSHOT/version versioning snapshot timestamp20090317.001852/timestamp buildNumber13/buildNumber /snapshot lastUpdated20090317001853/lastUpdated /versioning Now let's look at the META-INF for both 11 and 13. $ cat META-INF/MANIFEST.MF Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 10.0-b19 (Sun Microsystems Inc.) Built-By: teamcity Implementation-Title: common-op Implementation-Version: 25.0.38 Specification-Title: common-op Specification-Version: 25.0.38 Class-Path: $ cat META-INF/MANIFEST.MF Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 10.0-b19 (Sun Microsystems Inc.) Built-By: teamcity Implementation-Title: common-op Implementation-Version: 25.0.40 Specification-Title: common-op Specification-Version: 25.0.40 Class-Path: On Tue, Mar 17, 2009 at 9:32 PM, Rusty Wright rusty.wri...@gmail.comwrote: The META-INF inside the jars. Tim wrote: If you mean the metadata xml files in that 25-SNAPSHOT directory w/ the jars then no those are correct.Otherwise, I don't know what you mean by META-INF/maven. On Tue, Mar 17, 2009 at 10:17 AM, Mark Struberg strub...@yahoo.de wrote: have you checked if it isn't only the META-INF/maven contents? LieGrue, strub --- Tim che...@gmail.com schrieb am Di, 17.3.2009: Von: Tim che...@gmail.com Betreff: Re: Is there a way to verify/check/repair a local repository ? An: Maven Users List users@maven.apache.org Datum: Dienstag, 17. März 2009, 16:04 I'm actually having the same problem.After alot of debugging I noticed something interesting. -rw-r--r-- 1 tich tich 1482491 common-util-25-20090313.151759-9.jar -rw-r--r-- 1 tich tich 1482490 common-util-25-20090317.001243-13.jar -rw-r--r-- 1 tich tich 1482491 common-util-25-SNAPSHOT.jar I've snipped out all the non relevant info. Notice the size of -SNAPSHOT? It is actually different from the size of the latest released version (snapshot -13). Since the -SNAPSHOT jar is used in the classpath instead of the actual -2009xxx. versions it will fail the build. It seems that something in maven's mechanism for replacing the SNAPSHOT jars will occasionally break. I haven't had time to look into exactly what it is but this is likely the source of your build errors. Notice that this only effects -SNAPSHOT jars so I don't know if that is true in your scenario. On Tue, Mar 17, 2009 at 8:56 AM, Julien CARSIQUE jcarsi...@nuxeo.com wrote: Hello, I had issues building my project but strangely it was building fine on other computers. So, I tried the following steps: mv ~/.m2/repository ~/.m2/repository.old = build ok mv ~/.m2/repository ~/.m2/repository.new mv ~/.m2/repository.old ~/.m2/repository cp -rf ~/.m2/repository.new/* ~/.m2/repository/ = build ok Using diff, I saw that a few files differ (xml, pom, jar, sha1, ...) so it seems there was something broken in my local repository. Deleting it is not a very convenient solution. Is there a way to verify/check/repair a local repository (I tried -U option without success) ? Thanks, -- Julien Carsique, Nuxeo (Paris, France) www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org Nuxeo ECM
Re: Install artifact during build
Sry is this a dependency jar?In which case, just use:
scopesystem/scope
systemPath${some.path.property}/systemPath
On Mon, Mar 16, 2009 at 9:48 AM, Will Hoover java.whoo...@gmail.com wrote:
Yeah, I want to install the jars into a user's local repository based upon
a
path provided in a child projects pom (if not performed in a previous
build)
-Original Message-
From: Wendy Smoak [mailto:wsm...@gmail.com]
Sent: Monday, March 16, 2009 10:39 AM
To: Maven Users List
Subject: Re: Install artifact during build
On Mon, Mar 16, 2009 at 7:31 AM, Will Hoover java.whoo...@gmail.com
wrote:
Is there a way to install an artifact based upon a path defined in
pom? I need to have a parent pom that installs a set of proprietary
artifacts based upon a path provided by a child pom... Is there a way to
do this?
Are you trying to install additional jars into your local Maven repository,
or something else?
--
Wendy
-
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
--
Douglas Adams - I love deadlines. I like the whooshing sound they make as
they fly by.
Re: how to EMMA-instrument dependencies
Thank you, but this does not really solve my problem. The problem is not
that I cannot instrument dependency JARs. The problem is I cannot
cleanly get instrumented JARs into the unit test classpath.
Vasiliy
COURCY Michael wrote:
Hi
From my experience with emma I use a ant call after the compilation phase.
Ant is going much more power than the emma plugin
!--
pour instrumenter l'appli web
mvn install -P instrument
--
profile
idinstrument/id
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprocess-classes/phase
configuration
tasks
ant
antfile=${basedir}/instrument_for_coverage.xml
target
name=instrument/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
And use the overwrite mode in the ant, then only your class are going to be instrumended if you active this option :
target name=instrument depends=init
echoInstrumenting the classes/echo
emma enabled=${emma.enabled}
instr instrpathref=ServeurJava.classpath
metadatafile=${metadatafile}
merge=true
mode=overwrite
filter value=${emma.filter} /
/instr
/emma
/target
Thus running
Mvn package -P instrument
produce an instrumented war
And
Mvn package
Produce a regular one
Good luck, emma rocks !!
-Message d'origine-
De : vasiliy.bara...@sun.com [mailto:vasiliy.bara...@sun.com]
Envoyé : mercredi 18 mars 2009 15:32
À : users@maven.apache.org
Objet : how to EMMA-instrument dependencies
Hi,
I have a Maven 2 project that depends on a number of other Maven 2 projects that are built locally and installed into the local repository.
I need to instrument some of the dependency JARs with the EMMA coverage tool and have Maven run unit tests against instrumented JARs rather than the original dependencies. The emma-maven-plugin
(http://mojo.codehaus.org/emma-maven-plugin) does not seem to be of much help
as it does not seem to support this scenario.
Of course, it would be ideal if the emma-maven-plugin had support for this. In
fact, the plugin has an 'instrumentationPaths' parameter which can be used to
instrument classes from arbitrary directories; so I think dependencies can be
copied, unpacked, instrumented this way and passed to maven-surefire-plugin via
the 'classesDirectory' parameter; but in this case both the instrumented
classes and original dependencies both appear on the test classpath, which
sounds wrong.
Actually, I can bypass emma-maven-plugin and run EMMA instrumentor via
exec-maven-plugin, but again, it looks like the only way to pass the
instrumented classes to surefire is via the 'classesDirectory' or
'additionalClasspathElements' parameter, which is the same problem as above,
which makes me think this is not solely emma-maven-plugin's problem (hence
posting to this list).
What would be the right Maven way to achieve the goal? I am new to Maven so I
am sorry if I am missing something obvious. I spent several days trying to find
a solution, to no success.
In fact, I have some control over the dependency projects so I think I can build them so that the resulting JARs will contain instrumented classes (or I can instrument JARs separately and 'install:install-file'
them as separate components), but this is undesirable.
I hope I am making sense.
Thank you,
Vasiliy
-
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:
RE: how to EMMA-instrument dependencies
I see, well unless you instrument your local repository ... I don't really see
a simple and *clean* solution.
Emma offer an option to instrument code by providing its own classloader, but
it means you have to inteact with classworld maven classloader and thus write a
plugin for that :
http://maven.apache.org/guides/mini/guide-maven-classloading.html
Should be possible but there's a real work to do.
-Message d'origine-
De : vasiliy.bara...@sun.com [mailto:vasiliy.bara...@sun.com]
Envoyé : mercredi 18 mars 2009 16:48
À : Maven Users List
Objet : Re: how to EMMA-instrument dependencies
Thank you, but this does not really solve my problem. The problem is not
that I cannot instrument dependency JARs. The problem is I cannot cleanly get
instrumented JARs into the unit test classpath.
Vasiliy
COURCY Michael wrote:
Hi
From my experience with emma I use a ant call after the compilation phase.
Ant is going much more power than the emma plugin
!--
pour instrumenter l'appli web
mvn install -P instrument
--
profile
idinstrument/id
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprocess-classes/phase
configuration
tasks
ant
antfile=${basedir}/instrument_for_coverage.xml
target name=instrument/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
And use the overwrite mode in the ant, then only your class are going to be
instrumended if you active this option :
target name=instrument depends=init
echoInstrumenting the classes/echo
emma enabled=${emma.enabled}
instr instrpathref=ServeurJava.classpath
metadatafile=${metadatafile}
merge=true
mode=overwrite
filter value=${emma.filter} /
/instr
/emma
/target
Thus running
Mvn package -P instrument
produce an instrumented war
And
Mvn package
Produce a regular one
Good luck, emma rocks !!
-Message d'origine-
De : vasiliy.bara...@sun.com [mailto:vasiliy.bara...@sun.com] Envoyé :
mercredi 18 mars 2009 15:32 À : users@maven.apache.org Objet : how to
EMMA-instrument dependencies
Hi,
I have a Maven 2 project that depends on a number of other Maven 2 projects
that are built locally and installed into the local repository.
I need to instrument some of the dependency JARs with the EMMA
coverage tool and have Maven run unit tests against instrumented JARs
rather than the original dependencies. The emma-maven-plugin
(http://mojo.codehaus.org/emma-maven-plugin) does not seem to be of much help
as it does not seem to support this scenario.
Of course, it would be ideal if the emma-maven-plugin had support for this.
In fact, the plugin has an 'instrumentationPaths' parameter which can be used
to instrument classes from arbitrary directories; so I think dependencies can
be copied, unpacked, instrumented this way and passed to
maven-surefire-plugin via the 'classesDirectory' parameter; but in this case
both the instrumented classes and original dependencies both appear on the
test classpath, which sounds wrong.
Actually, I can bypass emma-maven-plugin and run EMMA instrumentor via
exec-maven-plugin, but again, it looks like the only way to pass the
instrumented classes to surefire is via the 'classesDirectory' or
'additionalClasspathElements' parameter, which is the same problem as above,
which makes me think this is not solely emma-maven-plugin's problem (hence
posting to this list).
What would be the right Maven way to achieve the goal? I am new to Maven so I
am sorry if I am missing something obvious. I spent several days trying to
find a solution, to no success.
Re: how to EMMA-instrument dependencies
What you really want is to attach additional artifacts to your build with an
emma-instrumented classifier...
[Random but relevant]This will probably break the maven-ear-plugin on your
build... ;-) [/Random but relevant]
My understanding is that issues with instrumented jars using classifiers and
forked builds and fun like that is why clover-maven-plugin is less than
perfect...
I know that there are changes to maven which will make the coverage
situation nicer... I suspect people are holding off to see what they are
-Stephen
2009/3/18 COURCY Michael mcourcy-exte...@sigma.fr
I see, well unless you instrument your local repository ... I don't really
see a simple and *clean* solution.
Emma offer an option to instrument code by providing its own classloader,
but it means you have to inteact with classworld maven classloader and thus
write a plugin for that :
http://maven.apache.org/guides/mini/guide-maven-classloading.html
Should be possible but there's a real work to do.
-Message d'origine-
De : vasiliy.bara...@sun.com [mailto:vasiliy.bara...@sun.com]
Envoyé : mercredi 18 mars 2009 16:48
À : Maven Users List
Objet : Re: how to EMMA-instrument dependencies
Thank you, but this does not really solve my problem. The problem is not
that I cannot instrument dependency JARs. The problem is I cannot cleanly
get instrumented JARs into the unit test classpath.
Vasiliy
COURCY Michael wrote:
Hi
From my experience with emma I use a ant call after the compilation
phase.
Ant is going much more power than the emma plugin
!--
pour instrumenter l'appli web
mvn install -P instrument
--
profile
idinstrument/id
build
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phaseprocess-classes/phase
configuration
tasks
ant
antfile=${basedir}/instrument_for_coverage.xml
target name=instrument/
/ant
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
/plugins
/build
/profile
And use the overwrite mode in the ant, then only your class are going to
be instrumended if you active this option :
target name=instrument depends=init
echoInstrumenting the classes/echo
emma enabled=${emma.enabled}
instr instrpathref=ServeurJava.classpath
metadatafile=${metadatafile}
merge=true
mode=overwrite
filter value=${emma.filter} /
/instr
/emma
/target
Thus running
Mvn package -P instrument
produce an instrumented war
And
Mvn package
Produce a regular one
Good luck, emma rocks !!
-Message d'origine-
De : vasiliy.bara...@sun.com [mailto:vasiliy.bara...@sun.com] Envoyé :
mercredi 18 mars 2009 15:32 À : users@maven.apache.org Objet : how to
EMMA-instrument dependencies
Hi,
I have a Maven 2 project that depends on a number of other Maven 2
projects that are built locally and installed into the local repository.
I need to instrument some of the dependency JARs with the EMMA
coverage tool and have Maven run unit tests against instrumented JARs
rather than the original dependencies. The emma-maven-plugin
(http://mojo.codehaus.org/emma-maven-plugin) does not seem to be of much
help as it does not seem to support this scenario.
Of course, it would be ideal if the emma-maven-plugin had support for
this. In fact, the plugin has an 'instrumentationPaths' parameter which can
be used to instrument classes from arbitrary directories; so I think
dependencies can be copied, unpacked, instrumented this way and passed to
maven-surefire-plugin via the 'classesDirectory' parameter; but in this case
both the instrumented classes and original dependencies both appear on the
test classpath, which sounds wrong.
Actually, I can bypass emma-maven-plugin and run EMMA instrumentor via
exec-maven-plugin, but again, it looks like the only way to pass the
instrumented classes to surefire is via the 'classesDirectory' or
'additionalClasspathElements'
Re: Searching for a repo1.maven.org administrator
http://maven.apache.org/guides/mini/guide-central-repository-upload.html http://maven.apache.org/guides/mini/guide-maven-evangelism.html there's a list of automatically synced repos at https://svn.apache.org/repos/asf/maven/repository-tools/trunk/src/bin/synchronize/m2-sync/sync.csv On Wed, Mar 18, 2009 at 6:08 AM, Bond, Timothy tim.b...@softwareag.com wrote: Ran into #1 a few weeks ago, there is claim of a bad class file noted here: https://issues.apache.org/bugzilla/show_bug.cgi?id=28069 -- Tim -Original Message- From: Costin Caraivan [mailto:ccarai...@axway.com] Sent: Wednesday, March 18, 2009 8:58 AM To: users@maven.apache.org Subject: Searching for a repo1.maven.org administrator Hello, I would like to contact the administrators of repo1.maven.org for a corrupted jars and some incorrect poms on repo1. Or at least, I want to get some pointer about who to contact so we can fix the problems. A short list of the problems: 1. com.ibm.icu:icu4j:2.6.1 seems to be corrupt. Running Proguard on a project having this dependency makes Proguard crash. Other versions don't have this problem, just the jar on repo1. 2. bouncycastle:bcprov-jdk13:132 is missing. org.apache.rampart:rampart-project:1.4 requires this dependency, which can't be found. I know about exclusions, but I'd rather fix the problem directly where it should be fixed. This might be something related to our corporate mirror, I'll double check that later. 3. All the org.eclipse poms are broken. They use version ranges which can't be resolved by Maven. BTW, this is the second time I'm reporting this... I would file bugs for these, but I don't know under which *category* to file them. Thank you, Costin. PS: Don't tell me about fixing the problems in the local repository, I'm willing to help to get them fixed, I just need a contact person. To fix them the *right* way. -- View this message in context: http://www.nabble.com/Searching-for-a-repo1.maven.org-administrator-tp22 578599p22578599.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Relative Path to a Local Repo
If there's no maven solution here, I will see if I can get an environment variable set up as a solution. It would still be nice to able to have a relative path in the settings.xml file. By definition, the settings.xml file is NOT for project-specific stuff. Therefore the very notion of relative path is invalid. I don't see this being changed or fixed any time soon, and don't in fact consider it a bug. The easiest thing would probably be to teach your users how to use subst in DOS, or include a setup.bat file in your project archive that runs subst and creates a virtual drive say M: which always points to the latest repo which is inside the latest project you've sent them, and then point settings.xml at the new M drive. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Relative Path to a Local Repo
Is there any way to specify the local repo to use from the command line? I was not able to figure that out either but if it's possible to do that would represent a perfect solution. On Wed, Mar 18, 2009 at 1:00 PM, Wayne Fay wayne...@gmail.com wrote: If there's no maven solution here, I will see if I can get an environment variable set up as a solution. It would still be nice to able to have a relative path in the settings.xml file. By definition, the settings.xml file is NOT for project-specific stuff. Therefore the very notion of relative path is invalid. I don't see this being changed or fixed any time soon, and don't in fact consider it a bug. The easiest thing would probably be to teach your users how to use subst in DOS, or include a setup.bat file in your project archive that runs subst and creates a virtual drive say M: which always points to the latest repo which is inside the latest project you've sent them, and then point settings.xml at the new M drive. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Relative Path to a Local Repo
Jeremy Sager schrieb: Is there any way to specify the local repo to use from the command line? I was not able to figure that out either but if it's possible to do that would represent a perfect solution. mvn -Dmaven.repo.local=path ... -Tim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
mvn weblogic:undeploy NoClassDefError L10nLookup
All, Just recently I am getting the following error when I try to undeploy to my local weblogic. java.lang.NoClassDefFoundError: weblogic/i18ntools/L10nLookup at weblogic.deploy.internal.DeployerTextFormatter.(DeployerTextFormatter.java:20) at weblogic.Deployer.(Deployer.java:29) I am using the command mvn weblogic:undeploy. The issue just poped-up last week and is not dependent on project or which weblogic server I use on my local workstation. Anyone have any ideas? -- View this message in context: http://www.nabble.com/mvn-weblogic%3Aundeploy-NoClassDefError-L10nLookup-tp22587379p22587379.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Maven vs. Hudson
Yes good question You use maven to define your projects for building your jar, war and ear You use hudson to run these projects in an automated way. /Anders On 18/03/2009, at 11.50, Łukasz Warchoł wrote: Hello, Can anybody tell me what are de differences between Maven and Hudson? Thanks in advance, Luke - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Activation of multiple profiles at the same time
I can get default and jdk to activate together, but not the os with them; given
the following profiles.xml:
?xml version=1.0?
profilesXml
xmlns=http://maven.apache.org/xsd/profiles-1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/xsd/profiles-1.0.0.xsd;
profiles
profile
idjdk1.5/id
activation
activeByDefaultfalse/activeByDefault
jdk1.5/jdk
/activation
/profile
profile
idunix/id
activation
activeByDefaultfalse/activeByDefault
os
familyunix/family
/os
/activation
/profile
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
etc.
I get the following output:
$ mvn enforcer:display-info help:active-profiles
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'enforcer'.
[INFO]
[INFO] Building People Locator
[INFO]task-segment: [enforcer:display-info]
[INFO]
[INFO] [enforcer:display-info]
[INFO] Maven Version: 2.0.10
[INFO] JDK Version: 1.5.0_17 normalized as: 1.5.0-17
[INFO] OS Info: Arch: i386 Family: unix Name: linux Version: 2.6.24-21-server
[INFO]
[INFO] Building People Locator
[INFO]task-segment: [help:active-profiles] (aggregator-style)
[INFO]
[INFO] [help:active-profiles]
[INFO]
Active Profiles for Project 'edu.berkeley:people_locator:war:1.1-SNAPSHOT':
The following profiles are active:
- jdk1.5 (source: profiles.xml)
- default (source: profiles.xml)
No matter what I use between the os tags it never activates (arch, family,
name).
COURCY Michael wrote:
It seems to me that activation of profiles is exclusive, i.e., only one profile is activated at a time.
No you can cumulate profiles
profiles
profile
idid1/id
activationactiveByDefaulttrue/activeByDefault/activation
/profile
profile
idid2/id
activationactiveByDefaulttrue/activeByDefault/activation
/profile
/profiles
Mvn help:active-profiles
The following profiles are active:
- id1 (source: pom)
- id2 (source: pom)
- dev (source: settings.xml)
- delphi (source: settings.xml)
- delphi (source: settings.xml)
-Message d'origine-
De : TM [mailto:thorsten.moel...@unibas.ch]
Envoyé : mercredi 18 mars 2009 12:08
À : users@maven.apache.org
Objet : Activation of multiple profiles at the same time
Hello,
I'm facing some behavior regarding activation of multiple profiles within a
pom.xml, which is contrary to what I was expecting. Maybe someone can help.
I have a pom consisting of three profiles:
profiles
profile!-- Set tools.jar for most SUN JDKs. --
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
toolsJAR${java.home}/../lib/tools.jar/toolsJAR
/properties
/profile
profile!-- Mac OSX Java JDK doesn't has separate tools.jar. --
idtools-jar-mac/id
activation
activeByDefaultfalse/activeByDefault
os
familyMac/family
/os
/activation
properties
toolsJAR${java.home}/../Classes/classes.jar/toolsJAR
/properties
/profile
!--
Add external dependency to StAX API (JSR-173) and Woodstox (which is an
implementation of JSR-173). Both are not part of JDK 1.5. Starting from
JDK 1.6 the built-in implementation is used.
--
profile
idjdk1.5/id
activation
activeByDefaultfalse/activeByDefault
jdk1.5/jdk
/activation
dependencies
dependency
groupIdorg.codehaus.woodstox/groupId
artifactIdwoodstox-core-asl/artifactId
version4.0.3/version
/dependency
/dependencies
/profile
/profiles
What I want to achieve is that for platforms other than Mac OS _and_ Java version 1.5.* the profiles
default _and_ jdk1.5 will be activated. For platforms other than Mac OS _and_ Java 1.6 only the
profile default should be activated. Finally, for the Mac OS platform the
Re: different behaviour of surefire with maven 2.0.10
Sorry, I am not sure the zip went through. Here are the relevant classes... On Wed, Mar 18, 2009 at 11:48 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Hi All, Has anyone experiencing the same problem? Up to maven 2.0.9 I was used to test the project with a command line similar to: mvn -D__TEST__=true test The test code uses System.getProperty(__TEST__) and gets the value passed on the command line. With maven 2.0.10 this doe snot happen, so the tests do not pass because of the missing property. Is this the intended behaviour? Or is it a bug? I am attaching a test project if anyone is kind to spend some time to try it out. Thanks in advance. -- Ste -- Ste - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: compile-time only depend - how to reference without generating transitive dependency?
On 18/03/2009, sebb seb...@gmail.com wrote: AIUI, compile scope means compile, test and run, and generates a transitive dependency. There are some dependencies that are compile-time only, for example annotations, and Java specification jars - i.e. API-only jars that have no implementation. What is the best way to define such a dependency? The Maven site suggests using provided, but this does not solve the problem. Maybe there should be acompile-only scope? Note that in the case of annotation jars, these are not needed at run-time. In the case of API-only jars, at run-time one would use a different jar which has the full implementation. This is useful for public specs which might not have open source implementations. The API-only jars allow one to compile. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: different behaviour of surefire with maven 2.0.10
maven 2.0.10 uses surefire 2.4.3 which will break your test scenario, you need to pin down your sure fire to 2.4.2 and i think 2.0.9 uses 2.4.2 -D On Wed, Mar 18, 2009 at 3:52 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Sorry, I am not sure the zip went through. Here are the relevant classes... On Wed, Mar 18, 2009 at 11:48 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Hi All, Has anyone experiencing the same problem? Up to maven 2.0.9 I was used to test the project with a command line similar to: mvn -D__TEST__=true test The test code uses System.getProperty(__TEST__) and gets the value passed on the command line. With maven 2.0.10 this doe snot happen, so the tests do not pass because of the missing property. Is this the intended behaviour? Or is it a bug? I am attaching a test project if anyone is kind to spend some time to try it out. Thanks in advance. -- Ste -- Ste - 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: different behaviour of surefire with maven 2.0.10
Hi Dan, thanks fo the quick reply. But do you mean that this is the correct behaviour of surefire 2.4.3? It seems odd to me. Ste On Thu, Mar 19, 2009 at 12:07 AM, Dan Tran dant...@gmail.com wrote: maven 2.0.10 uses surefire 2.4.3 which will break your test scenario, you need to pin down your sure fire to 2.4.2 and i think 2.0.9 uses 2.4.2 -D On Wed, Mar 18, 2009 at 3:52 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Sorry, I am not sure the zip went through. Here are the relevant classes... On Wed, Mar 18, 2009 at 11:48 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Hi All, Has anyone experiencing the same problem? Up to maven 2.0.9 I was used to test the project with a command line similar to: mvn -D__TEST__=true test The test code uses System.getProperty(__TEST__) and gets the value passed on the command line. With maven 2.0.10 this doe snot happen, so the tests do not pass because of the missing property. Is this the intended behaviour? Or is it a bug? I am attaching a test project if anyone is kind to spend some time to try it out. Thanks in advance. -- Ste -- Ste - 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: Release plug-in failing to resolve env vars.
I would then have to maintain multiple lists of mirrors for each site
which is error prone.
Currently to add one new repo I only need to add the repo to the profile
(or base pom) and a single entry in the mirror section.
-Original Message-
From: Santosh Patel [mailto:santosh@gmail.com]
Sent: 17 March 2009 17:09
To: Maven Users List
Subject: Re: Release plug-in failing to resolve env vars.
hi,
Sorry but could you explain the need for this proxyURL thing.
Is this a network proxy?
why dont you try adding it in the active profile as a
property in the settings.xml. I presume it can be done that
way, probably.
Santosh
On Tue, Mar 17, 2009 at 7:05 PM, Nord, James jn...@nds.com wrote:
I copied the maven-clean-plugin from a backup local repo
and it then
fails resolving the clean-plugins parent.
[INFO] Downloading:
${env.proxyURL}/central/org/apache/maven/plugins/maven-plugins/10/mave
n-
plugins-10.pom
[INFO] Downloading:
${env.proxyURL}/central/org/apache/maven/plugins/maven-plugins/10/mave
n-
plugins-10.pom
-Original Message-
From: Santos Patel [mailto:santos.pa...@tcs.com]
Sent: 17 March 2009 13:01
To: Maven Users List
Subject: RE: Release plug-in failing to resolve env vars.
hi,
Can't seem to find out any obvious errors or bugs over here.
Try downloading and installing the maven-clean-plugin
manually. Then
check to see if the same thing pops up for some other plugin.
add the downloaded plugin using
mvn install:install-file
Santosh
=-=-=
Notice: The information contained in this e-mail message and/or
attachments to it may contain confidential or privileged
information. If you are not the intended recipient, any
dissemination, use, review, distribution, printing or
copying of the
information contained in this e-mail message and/or
attachments to
it are strictly prohibited. If you have received this
communication
in error, please notify us by reply e-mail or telephone and
immediately and permanently delete the message and any
attachments.
Thank you
**
This e-mail is confidential, the property
of NDS Ltd
and intended for the addressee only. Any dissemination, copying or
distribution of this message or any attachments by anyone
other than
the intended recipient is strictly prohibited. If you have received
this message in error, please immediately notify the
postmas...@nds.com and destroy the original message.
Messages sent to
and from NDS may be monitored. NDS cannot guarantee any message
delivery method is secure or error-free. Information could be
intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses.
We do not accept responsibility for any errors or omissions in this
message and/or attachment that arise as a result of
transmission. You
should carry out your own virus checks before opening any
attachment.
Any views or opinions presented are solely those of the
author and do
not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless
necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex,
TW18 4EX, United Kingdom. A company registered in England and Wales
Registered no. 3080780 VAT no. GB 603 8808 40-00
**
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Santosh Patel
**
This e-mail is confidential, the property of NDS Ltd and intended for the
addressee only. Any dissemination, copying or distribution of this message or
any attachments by anyone other than the intended recipient is strictly
prohibited. If you have received this message in error, please immediately
notify the postmas...@nds.com and destroy the original message. Messages sent
to and from NDS may be monitored. NDS cannot guarantee any message delivery
method is secure or error-free. Information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or contain viruses. We do not
accept responsibility for any errors or omissions in this message and/or
attachment that arise as a result of transmission. You should carry out your
own virus checks before opening any attachment. Any views or opinions presented
are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines,
Re: compile-time only depend - how to reference without generating transitive dependency?
Do the imports only have an effect at compile time? For example, if you have
package impl.zzz;
import api.yyy.Yyy;
public class Xyz implements Yyy {
}
When you run the app the jvm won't need to have the yyy.Yyy class available?
Even if that's true it seems dubious to me because it seems to me that that
means your code is always referring to the concrete class Xyz when it should be
using the interface Yyy. For example, how could you do
Yyy y = new Xyz();
Would that run without the interface class on the classpath?
sebb wrote:
On 18/03/2009, sebb seb...@gmail.com wrote:
AIUI, compile scope means compile, test and run, and generates a
transitive dependency.
There are some dependencies that are compile-time only, for example
annotations, and Java specification jars - i.e. API-only jars that
have no implementation.
What is the best way to define such a dependency?
The Maven site suggests using provided, but this does not solve the problem.
Maybe there should be acompile-only scope?
Note that in the case of annotation jars, these are not needed at run-time.
In the case of API-only jars, at run-time one would use a different
jar which has the full implementation. This is useful for public specs
which might not have open source implementations. The API-only jars
allow one to compile.
-
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: different behaviour of surefire with maven 2.0.10
see this issue for details https://jira.codehaus.org/browse/SUREFIRE-121 -D On Wed, Mar 18, 2009 at 4:25 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Hi Dan, thanks fo the quick reply. But do you mean that this is the correct behaviour of surefire 2.4.3? It seems odd to me. Ste On Thu, Mar 19, 2009 at 12:07 AM, Dan Tran dant...@gmail.com wrote: maven 2.0.10 uses surefire 2.4.3 which will break your test scenario, you need to pin down your sure fire to 2.4.2 and i think 2.0.9 uses 2.4.2 -D On Wed, Mar 18, 2009 at 3:52 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Sorry, I am not sure the zip went through. Here are the relevant classes... On Wed, Mar 18, 2009 at 11:48 PM, Stefano Fornari stefano.forn...@gmail.com wrote: Hi All, Has anyone experiencing the same problem? Up to maven 2.0.9 I was used to test the project with a command line similar to: mvn -D__TEST__=true test The test code uses System.getProperty(__TEST__) and gets the value passed on the command line. With maven 2.0.10 this doe snot happen, so the tests do not pass because of the missing property. Is this the intended behaviour? Or is it a bug? I am attaching a test project if anyone is kind to spend some time to try it out. Thanks in advance. -- Ste -- Ste - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: compile-time only depend - how to reference without generating transitive dependency?
On 19/03/2009, Rusty Wright rusty.wri...@gmail.com wrote:
Do the imports only have an effect at compile time? For example, if you
have
package impl.zzz;
import api.yyy.Yyy;
public class Xyz implements Yyy {
}
When you run the app the jvm won't need to have the yyy.Yyy class
available?
Yes, that's what I wrote.
At runtime:
- annotation jars are not needed
- code jars are needed, but they may be different from the ones used to compile.
Can I get back to my original question, which is:
How does one express a dependency on a jar which is only needed at
compile time, such that the dependency is not propagated?
Even if that's true it seems dubious to me because it seems to me that that
means your code is always referring to the concrete class Xyz when it should
be using the interface Yyy. For example, how could you do
Yyy y = new Xyz();
Would that run without the interface class on the classpath?
sebb wrote:
On 18/03/2009, sebb seb...@gmail.com wrote:
AIUI, compile scope means compile, test and run, and generates a
transitive dependency.
There are some dependencies that are compile-time only, for example
annotations, and Java specification jars - i.e. API-only jars that
have no implementation.
What is the best way to define such a dependency?
The Maven site suggests using provided, but this does not solve the
problem.
Maybe there should be acompile-only scope?
Note that in the case of annotation jars, these are not needed at
run-time.
In the case of API-only jars, at run-time one would use a different
jar which has the full implementation. This is useful for public specs
which might not have open source implementations. The API-only jars
allow one to compile.
-
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: compile-time only depend - how to reference without generating transitive dependency?
On 19 Mar 2009, at 09:19, sebb seb...@gmail.com wrote:
On 19/03/2009, Rusty Wright rusty.wri...@gmail.com wrote:
Do the imports only have an effect at compile time? For example,
if you
have
package impl.zzz;
import api.yyy.Yyy;
public class Xyz implements Yyy {
}
When you run the app the jvm won't need to have the yyy.Yyy class
available?
Yes, that's what I wrote.
At runtime:
- annotation jars are not needed
- code jars are needed, but they may be different from the ones used
to compile.
Can I get back to my original question, which is:
How does one express a dependency on a jar which is only needed at
compile time, such that the dependency is not propagated?
Mark it as optionaltrue/optional ?
Optional dependencies appear on the compilation classpath but afaik
won't be propagated to dependent projects..
Even if that's true it seems dubious to me because it seems to me
that that
means your code is always referring to the concrete class Xyz when
it should
be using the interface Yyy. For example, how could you do
Yyy y = new Xyz();
Would that run without the interface class on the classpath?
sebb wrote:
On 18/03/2009, sebb seb...@gmail.com wrote:
AIUI, compile scope means compile, test and run, and generates a
transitive dependency.
There are some dependencies that are compile-time only, for example
annotations, and Java specification jars - i.e. API-only jars that
have no implementation.
What is the best way to define such a dependency?
The Maven site suggests using provided, but this does not solve
the
problem.
Maybe there should be acompile-only scope?
Note that in the case of annotation jars, these are not needed at
run-time.
In the case of API-only jars, at run-time one would use a different
jar which has the full implementation. This is useful for public
specs
which might not have open source implementations. The API-only jars
allow one to compile.
-
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
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
