Re: Where to find repos to download the following jars?
Here : http://download.java.net/maven/1/ Take care it is a legacy layout (maven1) ... On Sat, Sep 6, 2008 at 11:50 AM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, Try here : http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/download.jsp -- Olivier 2008/9/6 thomas2004 [EMAIL PROTECTED]: 1) com.sun.jdmk:jmxtools:jar:1.2.1 2) com.sun.jmx:jmxri:jar:1.2.1 -- View this message in context: http://www.nabble.com/Where-to-find-repos-to-download-the-following-jars--tp19344017p19344017.html Sent from the Maven - Users mailing list archive 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: Looking for Eclipse Artifact Repo
I've heard of this one : http://repo1.maven.org/eclipse/ Don't know if it's complete or up-to-date ... Manuel On Sun, Aug 17, 2008 at 2:42 PM, Mac-Systems [EMAIL PROTECTED]wrote: Hello, anyone can point were to find Eclipse Artifacts like org.eclipse.swt.* ? Searching the Eclipse Site and different Blogs haven't bring any results. thx, Jens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven WAR with self-classes as package
Did you make a clean command before ?
On Thu, Jul 31, 2008 at 10:53 AM, zm [EMAIL PROTECTED] wrote:
It didn't work as expected ... :(
I have the following in my pon.xml:
build
outputDirectoryWebContent/WEB-INF/classes/outputDirectory
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0.1/version
executions
goalexplode/goal
/executions
configuration
archiveClassestrue/archiveClasses
dependentWarIncludes
**/resources/*.*
/dependentWarIncludes
webResources
resource
!-- this is
relative to the pom.xml directory --
directory${basedir}/WebContent/directory
/resource
/webResources
/configuration
/plugin
/plugins
/build
The problem is that it creates a jar file inside lib dir, as expected and
just like I need it. But still it doesn't delete the classes from the
WEB-INF\classes folder.
I've found http://jira.codehaus.org/browse/MWAR-82 this reported issue ,
with no solution ... probably was tested, but still I don't get the desired
results.
Any idea?
Thanks
Wendy Smoak-3 wrote:
On Wed, Jul 30, 2008 at 10:27 AM, zm [EMAIL PROTECTED] wrote:
I have a WAR project that builds correctly in Maven2.
What I want to know, is if there is a way of making maven to do an
internal
JAR package of the WAR classes.
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
archiveClasses - boolean - Whether a JAR file will be created for the
classes in the webapp. Using this optional configuration parameter
will make the generated classes to be archived into a jar file and the
classes directory will then be excluded from the webapp. Default value
is false.
(There is a configuration example on the Usage page, just replace the
parameter name inside the configuration element, or ask if you need a
complete example.)
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Maven-WAR-with-self-classes-as-package-tp18738442p18750322.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn exec:java is giving error
I've done the same test you did and it works fine (see attached log file). Manuel -- Xebia IT Architects FR : http://blog.xebia.fr EN : http://blog.xebia.com On Tue, Jul 29, 2008 at 2:24 AM, Abhishek Sanoujam [EMAIL PROTECTED]wrote: Hi all, I am new to maven and I was trying to run a simple java program from maven. But its NOT working and complaining that the plugin does not exist or no valid version could be found. Here is the detailed output: $ mvn exec:java -Dexec.mainClass=simpleproject.App [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-exec-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Jul 29 05:45:32 IST 2008 [INFO] Final Memory: 1M/2M [INFO] I created a simple project using: $ mvn archetype:create -DgroupId=simpleproject -DartifactId=simpleMavenProject It contains a default HelloWorld app in simpleproject.App.java which is what I am trying to run. NOTE: If I use the full name of the exec-maven plugin, it is working. $ mvn org.codehaus.mojo:exec-maven-plugin:1.1:java -Dexec.mainClass=simpleproject.App The above works. Any reason why mvn exec:java -Dexec.mainClass=simpleproject.App is not working??? I am using maven-2.0.9 $ mvn -version Maven version: 2.0.9 Java version: 1.5.0_13 OS name: mac os x version: 10.5.2 arch: i386 Family: unix Thanks for the help in advance. Regards, Abhishek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] C:\Tempmvn archetype:create -DgroupId=simpleproject -DartifactId=simpleMavenProject [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] [archetype:create] [WARNING] This goal is deprecated. Please use mvn archetype:generate instead [INFO] Defaulting package to group ID: simpleproject 4K downloaded [INFO] [INFO] Using following parameters for creating OldArchetype: maven-archetype-quickstart:RELEASE [INFO] [INFO] Parameter: groupId, Value: simpleproject [INFO] Parameter: packageName, Value: simpleproject [INFO] Parameter: basedir, Value: C:\Temp [INFO] Parameter: package, Value: simpleproject [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: artifactId, Value: simpleMavenProject [INFO] * End of debug info from resources from generated POM *** [INFO] OldArchetype created in dir: C:\Temp\simpleMavenProject [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 15 seconds [INFO] Finished at: Tue Jul 29 09:54:54 CEST 2008 [INFO] Final Memory: 8M/14M [INFO] C:\Tempcd simpleMavenProject C:\Temp\simpleMavenProjectmvn clean compile exec:java -Dexec.mainClass=simpleproject.App [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'exec'. [INFO] [INFO] Building simpleMavenProject [INFO]task-segment: [clean, compile, exec:java] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Compiling 1 source file to C:\Temp\simpleMavenProject\target\classes [INFO] Preparing exec:java [INFO] No goals needed for project - skipping [INFO] [exec:java] Hello World! [INFO]
Re: Is there any way to pass JVM arguments to a process other than MAVEN_OPTS
Maybe you can try using systemPorperties as describe here :
http://mojo.codehaus.org/exec-maven-plugin/usage.html
Exemple :
project
build
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
version1.1-beta-2/version
executions
execution
goals
goaljava/goal
/goals
/execution
/executions
configuration
mainClasscom.example.Main/mainClass
arguments
argumentargument1/argument
/arguments
systemProperties
systemProperty
keymyproperty/key
valuemyvalue/value
/systemProperty
/systemProperties
/configuration
/plugin
/plugins
/build
/project
--
Xebia IT Architects
FR : http://blog.xebia.fr
EN : http://blog.xebia.com
On Mon, Jul 28, 2008 at 12:04 PM, seanoc [EMAIL PROTECTED] wrote:
other than using MAVEN_OPTS.
I'm looking to pass a configuration file, for example
-Dcxf.config.file=${basedir}/CherryServer.cxf
I've tried below but this doesn't work..
profile
idserver/id
build
defaultGoaltest/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
execution
phasetest/phase
goals
goalexec/goal
/goals
configuration
executablejava/executable
arguments
argument-classpath/argument
classpath/
argument-Dcxf.config.file=${basedir}/CherryServer.cxf/argument
argumentdemo.hw_https.server.Server/argument
/arguments
/configuration
/execution
/executions
/plugin
/plugins
/build
/profile
--
View this message in context:
http://www.nabble.com/Is-there-any-way-to-pass-JVM-arguments-to-a-process-other-than-MAVEN_OPTS-tp18687327p18687327.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and BIRT Report Generation Engine
Reading this ML, I foudn out another maven2 repository that can help you http://repo1.maven.org/eclipse At least there is some BIRT dependencies maybe in a good version (ex: org.eclipse.birt.chart.engine/2.1.0) Manuel -- Xebia IT Architects FR : http://blog.xebia.fr EN : http://blog.xebia.com On Mon, Jul 28, 2008 at 7:00 PM, Doug Douglass [EMAIL PROTECTED]wrote: Ian, We maven-ized our local/custom build of OpenReports, which has dependencies on BIRT. We created a separate pom project to manage the entire set of BIRT dependencies as a single unit and had to manually install most the dependencies into our repository manager. Note, we haven't used the BIRT features of OpenReports much so I can't say the versions are perfect. They do produce a successful compile/package of the OpenReports war, I just can't confirm the runtime behavior. Here's the pom with only a few minor company-specific elements removed... ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdYOUR GROUP ID HERE/groupId artifactIdeclipse-birt-bundle/artifactId nameEclipse BiRT Bundle/name version2.2.0-1-SNAPSHOT/version packagingpom/packaging dependencies !-- Most of these dependencies required manual installation into our repositories so we could match as closely as possible the version that were delivered with OpenReports 3.0.0. If/when the Eclipse projects artifacts are deployed publicly and consistently then we can update this bundle POM and track their versions. -- dependency groupIdorg.eclipse.birt/groupId artifactIdchartengine/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdcore/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIddataadapter/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdengine/artifactId version2.2/version exclusions exclusion groupIddom4j/groupId artifactIddom4j/artifactId /exclusion /exclusions /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdmodel/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIdscript/artifactId version2.2/version /dependency dependency groupIdorg.eclipse.birt/groupId artifactIddte/artifactId version2.2/version /dependency !-- EMF (Eclipse Modeling Framework ) -- dependency groupIdorg.eclipse.emf/groupId artifactIdecore/artifactId version2.2.2.v200702131851/version /dependency dependency groupIdorg.eclipse.emf/groupId artifactIdecore-xmi/artifactId version2.2.2.v200702131851/version /dependency dependency groupIdorg.eclipse.emf/groupId artifactIdcommon/artifactId version2.2.1.v200702131851/version /dependency !-- W3C -- dependency groupIdorg.w3c/groupId artifactIdflute/artifactId version1.2/version /dependency dependency groupIdorg.w3c/groupId artifactIdsac/artifactId version1.3/version /dependency !-- Commons -- dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3/version !-- removing unwanted transitive dependencies -- exclusions exclusion artifactIdjunit/artifactId groupIdjunit/groupId /exclusion /exclusions /dependency dependency groupIdcommons-cli/groupId artifactIdcommons-cli/artifactId version1.0/version !-- removing unwanted transitive dependencies -- exclusions exclusion artifactIdcommons-lang/artifactId groupIdcommons-lang/groupId /exclusion exclusion artifactIdcommons-logging/artifactId groupIdcommons-logging/groupId /exclusion /exclusions /dependency dependency groupIdcommons-discovery/groupId artifactIdcommons-discovery/artifactId version0.2/version /dependency !-- misc -- dependency groupIdcom.lowagie/groupId artifactIditext/artifactId version1.3/version /dependency dependency groupIdcom.ibm.icu/groupId artifactIdicu4j/artifactId version3.6.1/version /dependency dependency groupIdrhino/groupId artifactIdjs/artifactId version1.6R2/version /dependency /dependencies /project On Mon, Jul 28, 2008 at 10:24 AM, Ian Coleman [EMAIL PROTECTED] wrote: Maven gurus: I'm still finding my way with Maven, and am trying to convert a project from Ant to maven2. The biggest blocker I've found is integration with BIRT. The application I'm converting uses BIRT extensively, but
Re: packaging wars
I'm not sure to complete understand your needs but I think using war overlays may fill your needs : http://maven.apache.org/plugins/maven-war-plugin/overlays.html Create one war with the common stuff Create another with the specific stuff war and with a dependency of type war to the common war. It will merge the common-war with the specific war ... Manuel On Thu, Jul 24, 2008 at 10:23 PM, Jean-Paul Vallée [EMAIL PROTECTED] wrote: Hi, I want to use maven for creating portlets. The portlets will be deployed on a liferay portal So the problem i want to solve is: I do not want to make my portlets specific to a portal implementation, so using maven, i want to create 2 artifacts: com.mycompany:portlet-foo and com.mycompany:portlet-liferay-specific-foo com.mycompany:portlet-liferay-specific-foo depending on com.mycompany:portlet-foo i want in the com.mycompany:portlet-liferay-specific-foo project only the delta(i mean the specific files and modification needed by liferay, pluto, jboss...) and when packaging com.mycompany:portlet-liferay-specific-foo i want it integrate also the files and structure from com.mycompany:portlet-foo As this i could have a solution to have my portlets not specific to a portal solution Other question, even it is not specific to maven (sorry), is there a portlet container plugin that could just make me test my 'not specific' portlets. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to skip JAR creation
Do you want to use an external program to create the jar ? On this point, I'm joining Jeff Otherwise, you can target plugin goals directly by calling : mvn exec:exec Manuel On Fri, Jul 25, 2008 at 9:39 AM, syllepsa [EMAIL PROTECTED] wrote: Hi, Is it possible to turn off JAR building? I just want to run external program via maven-exec-plugin. Thank you in advance Mariusz -- View this message in context: http://www.nabble.com/How-to-skip-JAR-creation-tp18646725p18646725.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: building a resources artifact
Maybe you can use the assembly plugin
http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html
On Fri, Jul 25, 2008 at 12:03 PM, Julien CARSIQUE [EMAIL PROTECTED]wrote:
Hi,
I need to build an artifact containing only resources, no Java source.
These resources are in scr/main/... in a project with pom packaging type.
I tried with maven-jar-plugin with no success, the built jar is empty of
the wanted resources :
[INFO] [jar:jar {execution: resources_common}]
[WARNING] JAR will be empty - no content was marked for inclusion!
How can I do this ?
Here is the plugin definition :
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
execution
idresources_common/id
phasepackage/phase
goals
goaljar/goal
/goals
configuration
classifierresources_common/classifier
includes
include**/resources_common/include
/includes
/configuration
/execution
/executions
/plugin
--
Julien CARSIQUE, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[EMAIL PROTECTED] | Tel: +33 1 40 33 79 87 / +33 6 09 06 38 03
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there a standard way to provide build time properties to an application?
You mean dynamically create the properties file before packaging ? On Fri, Jul 25, 2008 at 4:05 PM, Brewster, Richard [EMAIL PROTECTED]wrote: The general idea is to create a properties file and package it in the jar or war on the classpath, so it can be read at runtime. Thanks, Richard Brewster Senior Associate Perrin Quarles Associates [EMAIL PROTECTED] (434) 817-2640
Re: Merging applicationContexts
You can put xml or properties file in jar too. Simply add them into src/main/resources of your server module Manuel On Fri, Jul 25, 2008 at 5:02 PM, Matt Walsh [EMAIL PROTECTED] wrote: I'm a little new to Maven (about 3 weeks), so I apologize if this is a n00b question. I have a question about how to better structure my current application. Currently, the parent project has three modules: client, server, and common. Common depends on nothing. It simply hold beans and service interfaces that are common across the app. Server depends on Common. Client depends on Server. Common and Server are packaged as JARs. Client is packaged as a WAR. When I want to deploy my application, I simply build the client and all is well. This means I have to put all my Spring related configurations in the client. I was hoping there was a way to avoid this by putting it in the Server module, but I don't see how that's possible if the Server module is packaged as a JAR. Am I going about this the wrong way? -- Matthew Walsh [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Variables in pom specified from external file
I once use maven-property-plugin
http://arsenalist.com/2007/02/07/maven-properties-plugin-download/
but I don't if it works for project/version ...
On Thu, Jul 24, 2008 at 10:47 AM, Stephen Connolly
[EMAIL PROTECTED] wrote:
Property expansion in ./project/version and /project/parent/version is not
supported by Maven 2 (and AFAIK will never be supported as it makes builds
irreproducible)
Yes, I know that it currently kinda works if you remember to define the
property in the command line or settings.xml... but it is not officially
supported
-Stephen
On Thu, Jul 24, 2008 at 9:36 AM, Carlos Alonso [EMAIL PROTECTED]
wrote:
Hi all.
I've been searching along both google and mailing list archives without
answer and I'm thinking that there's no possibility to achieve what I
want.
The question is: can I define some property for my pom.xml as a variable
i.e. version${version}/version and have it set up from an external
properties file? (neither profile nor settings.xml)
I already know that, by filtering resources there's a chance to perform
this whithin resource files, but I don't know if I can do it in the pom.
Thanks in advance.
Carlos.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Overriding parent's distribution management
I'm facing the same problem here at my client's. We have a team internal repository use and visible only to our team. We have a company-wide repository where we only put some of the internaly-released artefacts. This way we can filter which version is visible, usable, used by the other teams. Then we have a third repository when we need to share artefacts with a external company. This third repository exists because my client don't want this external company to see (and possibly steal) any artefact (with sources) produced internally. We have also have specific contractual rules for this third repository. What is maven best-practices for this ? - We want the first repo accessible with the default 'mvn deploy' command - The second repo accessible with profile activation : mvn -P deploy-internal deploy - The third repo accessible with profile activation : mvn -P deploy-public deploy The real problem is to have a default behavior on 'mvn deploy' command ... I've already look at the stage plugin but it does not fit our needs (and by the way don't work at all). Thanks ! Manuel -- http://blog.xebia.fr http://blog.xebia.com On Fri, May 16, 2008 at 6:36 PM, Clifton [EMAIL PROTECTED] wrote: Thank you for asking this question. I had the very same problem and I'd love to hear a best practices approach. My workaround, not the best, is to define them separately in profiles. Then you can use cmd line properties to activate one or the other in the activation section of the profile. It may not work in your case if you actually want certain pieces to deploy with different dist mgmt settings than others in a single build command. Krishnamurthi, Venkat wrote: Hi, I'm trying to override a parent pom's distribution management through the child's pom. (Deploy the artifacts in different directories). When I tried adding a distributionManagement element in the child pom, it is still picking up the details from the parent's pom. Please help me resolve this issue. Thanks and Regards, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/running-mvn-idea%3Aidea-tp17232616p17279055.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 Dependency on java source folder rather than jar file
Why don't you simply checkout the two projects and make a Eclipse dependency between them ? Just for dev purpose of course, keep the maven dependency configuration) .. Manuel On Fri, May 16, 2008 at 4:34 PM, BenDave [EMAIL PROTECTED] wrote: Hi, I am working on 2 projects, one is Dependant on the other. The usual way of dealing with this is to add a dependency to a jar file located in the repository. This works fine but the source project (on which the target project depends) is constantly evolving, as we are doing some iterative development. The source and target project are modified at the same time. Consequently i don't want to work off a jar file of the source project, because generating jar files and deploying them to the repository takes too long (only 20 seconds but it adds up when this is done dozens / hundreds of times per day ). I do not want to merge these two projects into one as the source is a common project and is being used by other projects too, I need these two projects to be distinct. So the solution is to indicate to maven a source folder which the target project depends on rather than a JAR file. Can this be achieved ? Thanks, -- View this message in context: http://www.nabble.com/Maven-2-Dependency-on-java-source-folder-rather-than-jar-file-tp17276237p17276237.html Sent from the Maven - Users mailing list archive at Nabble.com. -- Xebia IT Architects Mail: [EMAIL PROTECTED] Mobile: +33 6 13 43 59 92 Xebia blogue ! http://blog.xebia.fr
