Re: War plugin (2.1-beta-1,*] problem
You really made my day. Thank you very very much. You're welcome! I dont know how to thank you. Just take a little time once in a while to answer a question in this list Yourself ... :) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deployment in Repository without version in file name?
Another idea might be:
1. In Your Maven project, create a text file with the following content:
http://your-nexus/your-nexus-repo/${project.artifactId}-${project.version}.${project.packaging}
2. Use the 'resources:copy-resources' with 'filtering=true' to copy the
file somewhere and get its tokens replaced (see
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html).
3. Use wget with the -i (--input-file=FILE) option and the '-O' option.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Using release plugin with multi-module project
Are you using a pluginManagement section in your parent POM? The following
works for me (I'm using Maven 2.2.1):
...
build
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
version2.1/version
configuration
preparationGoalsclean install/preparationGoals
goalsdeploy site-deploy/goals
/configuration
/plugin
/plugins
/pluginManagement
/build
...
Good luck.
Craig
-Original Message-
From: Michael Remijan [mailto:mjremi...@yahoo.com]
Sent: Tuesday, February 15, 2011 9:23 PM
To: users@maven.apache.org
Subject: Using release plugin with multi-module project
I'm trying to use the release plugin for the first time on a multi-module
project. Given that my project looks like this:
/Parent
/Project-A
/Project-B (had a dependency on Project-A)
the problem I'm having is when the release plugin goes to build Project-B it
fails with an error saying it can't find Project-A. The release plugin will
successfully take the version of Project-A and remove the -SNAPSHOT so that's
OK. Also, the release plugin will successfully alter the pom of Project-B and
remove the -SNAPSHOT on the dependency to Project-A. However Project-B still
can't find Project-A when it the release plugin tries to build it.
I've posted before and received a suggestion to use the following:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
preparationGoalsclean install/preparationGoals
/configuration
/plugin
I've put this into the top level packagingpom/packaging of my multi-module
project. I've also put this into the sub modules as well. When I run
release:prepare, I see on the console the top level pom gets clean install
[INFO] [INFO]
[INFO] [INFO] Building Project Parent
[INFO] [INFO]task-segment: [clean, install]
[INFO] [INFO]
however sub modules aren't doing this too. For sub modules I only see comple,
not install...
[INFO] [INFO]
[INFO] [INFO] Building Project A
[INFO] [INFO]
[INFO] [INFO] [buildnumber:create {execution: default}]
[INFO] [INFO] Storing buildNumber: Tuesday, February 15, 2011 8:15:25 PM CST at
timestamp: 1297822525811
[INFO] [INFO] [resources:resources {execution: default-resources}]
[INFO] [INFO] [compiler:compile {execution: default-compile}]
[INFO] [INFO] Compiling 5 source files to C:\Parent\Project-A\target\classes
Suggestions?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven3 - maven-checkstyle-plugin:2.5 - Property ${basedir} has not been set
Hi all,
I've configured checkstyle for a project.
1. If I use the default check style, all works.
2. If I use a absolute path in file system
configLocation//xxx\yyy\Checkstyle\ISPA_checkstyle.xml/configLocation
The same error as with 3. Happens!
3. If I use:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-checkstyle-plugin/artifactId
version${version_maven-checkstyle-plugin}/version
configuration
configLocation/preferences/XXX_checkstyle.xml/configLocation
/configuration
/plugin
The following happens:
[INFO] Generating Checkstyle report--- maven-checkstyle-plugin:2.5
[DEBUG] executeCheckstyle start headerLocation : LICENSE.txt
[DEBUG] Adding the outputDirectory
file:/D:/IDE/workspaces/current/score_common/target/classes/ to the
Checkstyle class path
[DEBUG] request.getConfigLocation() /preferences/XXX_checkstyle.xml
[DEBUG] The resource '/preferences/XXX_checkstyle.xml' was found as
jar:file:/D:/Documents%20and%20Settings/XHAUSF/.m2/repository/com/xxx/sc
ore/buildExtension/0.0.1-SNAPSHOT/buildExtension-0.0.1-SNAPSHOT.jar!/pre
ferences/XXX_checkstyle.xml.
[DEBUG] headerLocation LICENSE.txt
[DEBUG] The resource 'LICENSE.txt' was found as
jar:file:/D:/Documents%20and%20Settings/XHAUSF/.m2/repository/org/apache
/maven/plugins/maven-checkstyle-plugin/2.5/maven-checkstyle-plugin-2.5.j
ar!/LICENSE.txt.
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 17.625s
[INFO] Finished at: Wed Feb 16 12:03:40 CET 2011
[INFO] Final Memory: 22M/58M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site
(default-site) on project score_common: Error during page generation:
Error rendering Maven report: Failed during checkstyle execution: Failed
during checkstyle configuration: unable to read
D:\IDE\workspaces\current\score_common\target\checkstyle-checker.xml -
unable to parse configuration stream - Property ${basedir} has not been
set - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site
(default-site) on project score_common: Error during page generation
It's great to know, that it find my settings on the classpath in the
buildextension ;-) But wtf is the problem with the basedir?
Any idea ??
Fredy
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Missing links in site generation of multi-module project
I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig
Disabling lifecycle with assembly plugin
Hi all, I'm having a problem with maven assembly plugin. It happens that I have a child pom with relative paths and when I hit assembly:assembly the environment becomes corrupted (that doesn't happen if I hit mvn install, package whatever in both project's pom directory or in the root of the major project). What I want is to disable the lifecycle when I hit assembly:assembly. I don't want it to perform package, install, etc. Is that possible? Any other ideas are welcomed :) Best regards, thank you in advance, -- Rui
Re: Missing links in site generation of multi-module project
I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using release plugin with multi-module project
Yes I am using Maven 2.2.1 and it may not be an option to update to Maven 3.0.
I have put the release-plugin configuration into pluginManagement as you
suggested. I ran effectivePom and I see the following configuration in each of
my module projects
plugin
artifactIdmaven-release-plugin/artifactId
version2.0-beta-8/version
configuration
preparationGoalsclean install/preparationGoals
/configuration
/plugin
However, release:prepare still fails because dependencies between the modules
cannot be resolved.
Besides changing to Maven 3, any additional suggestions?
From: Anders Hammar and...@hammar.net
To: Maven Users List users@maven.apache.org; Michael Remijan
mjremi...@yahoo.com
Sent: Tuesday, February 15, 2011 11:55 PM
Subject: Re: Using release plugin with multi-module project
Based on the description of the issue I assume you're using Maven 2.x? Maven
3.0 has been improved (issues fixed) with regards to resolving artifacts within
a multi-module build. So if possible I would suggest you upgrade and you will
not run into these issues.
If you can't upgrade for some reason, try putting the release plugin
configuration in the pluginManagement section of the parent. Or do you have it
there already?
Then, in the module you're having issues execute:
mvn help:effective-pom
and check that the configuration really is present or if it overwritten by some
other configuration.
/Anders
On Wed, Feb 16, 2011 at 03:23, Michael Remijan mjremi...@yahoo.com wrote:
I'm trying to use the release plugin for the first time on a multi-module
project. Given that my project looks like this:
/Parent
/Project-A
/Project-B (had a dependency on Project-A)
the problem I'm having is when the release plugin goes to build Project-B it
fails with an error saying it can't find Project-A. The release plugin will
successfully take the version of Project-A and remove the -SNAPSHOT so
that's OK. Also, the release plugin will successfully alter the pom of
Project-B and remove the -SNAPSHOT on the dependency to Project-A. However
Project-B still can't find Project-A when it the release plugin tries to
build it.
I've posted before and received a suggestion to use the following:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-release-plugin/artifactId
configuration
preparationGoalsclean install/preparationGoals
/configuration
/plugin
I've put this into the top level packagingpom/packaging of my
multi-module project. I've also put this into the sub modules as well. When
I run release:prepare, I see on the console the top level pom gets clean
install
[INFO] [INFO]
[INFO] [INFO] Building Project Parent
[INFO] [INFO]task-segment: [clean, install]
[INFO] [INFO]
however sub modules aren't doing this too. For sub modules I only see
comple, not install...
[INFO] [INFO]
[INFO] [INFO] Building Project A
[INFO] [INFO]
[INFO] [INFO] [buildnumber:create {execution: default}]
[INFO] [INFO] Storing buildNumber: Tuesday, February 15, 2011 8:15:25 PM CST
at timestamp: 1297822525811
[INFO] [INFO] [resources:resources {execution: default-resources}]
[INFO] [INFO] [compiler:compile {execution: default-compile}]
[INFO] [INFO] Compiling 5 source files to C:\Parent\Project-A\target\classes
Suggestions?
Re: Disabling lifecycle with assembly plugin
that goal is deprecated if I recall correctly use the single goal instead - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 16 Feb 2011 12:40, Rui Vilão rpvi...@gmail.com wrote: Hi all, I'm having a problem with maven assembly plugin. It happens that I have a child pom with relative paths and when I hit assembly:assembly the environment becomes corrupted (that doesn't happen if I hit mvn install, package whatever in both project's pom directory or in the root of the major project). What I want is to disable the lifecycle when I hit assembly:assembly. I don't want it to perform package, install, etc. Is that possible? Any other ideas are welcomed :) Best regards, thank you in advance, -- Rui
plugin versions
Hi, One of the main advantage of Maven is its uniform build system that uses centrally located plugins. In our development environment, we have base POM where all plugin versions are explicitly mentioned as below example. plugin artifactIdmaven-compiler-plugin/artifactId version2.3.1/version /plugin But, there is latest version of this plugin 2.3.2 available which we didnt notice. What is the best practice to make sure our build system using latest stable plugins apart from manually upgrading versions in some common base POM? Thanks, Prashant
Re: plugin versions
On Wed, 16 Feb 2011 19:35:07 +0530 Prashu Negu prashu.n...@gmail.com wrote: Hi, One of the main advantage of Maven is its uniform build system that uses centrally located plugins. In our development environment, we have base POM where all plugin versions are explicitly mentioned as below example. plugin artifactIdmaven-compiler-plugin/artifactId version2.3.1/version /plugin But, there is latest version of this plugin 2.3.2 available which we didnt notice. What is the best practice to make sure our build system using latest stable plugins apart from manually upgrading versions in some common base POM? The versions plugin can help you [1] Especially, the display-plugin-updates goal tells you which plugin could be updated [2] : So just try a mvn versions:display-plugin-updates [1] http://mojo.codehaus.org/versions-maven-plugin/ [2] http://mojo.codehaus.org/versions-maven-plugin/display-plugin-updates-mojo.html -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: plugin versions
note that it will tell you about updates, not whether those updates require a newer version of maven to be used - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 16 Feb 2011 14:16, chemit che...@codelutin.com wrote: On Wed, 16 Feb 2011 19:35:07 +0530 Prashu Negu prashu.n...@gmail.com wrote: Hi, One of the main advantage of Maven is its uniform build system that uses centrally located plugins. In our development environment, we have base POM where all plugin versions are explicitly mentioned as below example. plugin artifactIdmaven-compiler-plugin/artifactId version2.3.1/version /plugin But, there is latest version of this plugin 2.3.2 available which we didnt notice. What is the best practice to make sure our build system using latest stable plugins apart from manually upgrading versions in some common base POM? The versions plugin can help you [1] Especially, the display-plugin-updates goal tells you which plugin could be updated [2] : So just try a mvn versions:display-plugin-updates [1] http://mojo.codehaus.org/versions-maven-plugin/ [2] http://mojo.codehaus.org/versions-maven-plugin/display-plugin-updates-mojo.html -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Topologically sorting dependencies?
Well, here's how I did it. It sure ain't pretty, but it works!
Briefly, I grab the set of artifacts from a MavenProject. Usually because
I'm doing this from within a plugin whose dependency resolution has been set
to test, these artifacts are resolved already, which is convenient, and I
don't bother to handle the case where they aren't already resolved. Then I
invoke MavenProjectBuilder#buildFromRepository() on each of them to get
project information about each of them. Now I have a list of
MavenProjects. I hand them to a new ProjectSorter, which does the
topological sort I require, and keeps me blissfully ignorant of how exactly
Maven does its reactor sorting.
Finally, for each one, I grab its Artifact, and add it in order to the
returned list. I threw in an ArtifactFilter in case I want to weed out
results.
Hopefully this will be useful for other people in similar situations. Even
more hopefully someone will come along and ask pointedly why I went to all
the trouble to rewrite the ArtifactWhosieWhatsit#sort() method, and I will
reply because I didn't happen upon it. :-)
Best,
Laird
public static final ListArtifact topologicallySort(final MavenProject
project, MavenProjectBuilder builder, final ArtifactRepository
localRepository, final ArtifactFilter filter) throws
ProjectBuildingException, MissingProjectException,
DuplicateProjectException, CycleDetectedException {
if (project == null) {
throw new IllegalArgumentException(project == null);
}
ListArtifact returnValue = null;
@SuppressWarnings(unchecked)
final SetArtifact artifacts = (SetArtifact)project.getArtifacts();
if (artifacts != null) {
returnValue = new ArrayListArtifact();
if (!artifacts.isEmpty()) {
final ListMavenProject projects = new ArrayListMavenProject();
projects.add(project);
if (builder == null) {
builder = new DefaultMavenProjectBuilder();
}
for (final Artifact artifact : artifacts) {
if (artifact != null) {
final MavenProject artifactProject =
builder.buildFromRepository(artifact,
project.getRemoteArtifactRepositories(), localRepository);
assert artifactProject != null;
projects.add(artifactProject);
}
}
final ProjectSorter sorter = new ProjectSorter(projects);
final ListMavenProject sortedProjects =
sorter.getSortedProjects();
assert sortedProjects != null;
assert sortedProjects.size() == projects.size();
final Map projectArtifactMap = project.getArtifactMap();
assert projectArtifactMap != null;
for (final MavenProject p : sortedProjects) {
if (p != null) {
final Artifact artifact = p.getArtifact();
if (artifact != null) {
final Artifact resolvedArtifact =
(Artifact)projectArtifactMap.get(artifact.getGroupId() + : +
artifact.getArtifactId());
if (resolvedArtifact != null (filter == null ||
filter.include(resolvedArtifact))) {
returnValue.add(resolvedArtifact);
}
}
}
}
}
}
return returnValue;
}
Re: Topologically sorting dependencies?
I should also mention I can't guarantee the assertion statements, as there's
no documentation indicating, for example, whether Project.getArtifactMap
ever returns null. I'm also supplying what I *think* is the proper key
format for the map, but can't be sure, as that isn't documented either. I
ended up just looking at the source code and hoping that this key format is
not an internal detail of the class.
Best,
Laird
On Wed, Feb 16, 2011 at 10:11 AM, Laird Nelson ljnel...@gmail.com wrote:
Well, here's how I did it. It sure ain't pretty, but it works!
Briefly, I grab the set of artifacts from a MavenProject. Usually because
I'm doing this from within a plugin whose dependency resolution has been set
to test, these artifacts are resolved already, which is convenient, and I
don't bother to handle the case where they aren't already resolved. Then I
invoke MavenProjectBuilder#buildFromRepository() on each of them to get
project information about each of them. Now I have a list of
MavenProjects. I hand them to a new ProjectSorter, which does the
topological sort I require, and keeps me blissfully ignorant of how exactly
Maven does its reactor sorting.
Finally, for each one, I grab its Artifact, and add it in order to the
returned list. I threw in an ArtifactFilter in case I want to weed out
results.
Hopefully this will be useful for other people in similar situations. Even
more hopefully someone will come along and ask pointedly why I went to all
the trouble to rewrite the ArtifactWhosieWhatsit#sort() method, and I will
reply because I didn't happen upon it. :-)
Best,
Laird
public static final ListArtifact topologicallySort(final MavenProject
project, MavenProjectBuilder builder, final ArtifactRepository
localRepository, final ArtifactFilter filter) throws
ProjectBuildingException, MissingProjectException,
DuplicateProjectException, CycleDetectedException {
if (project == null) {
throw new IllegalArgumentException(project == null);
}
ListArtifact returnValue = null;
@SuppressWarnings(unchecked)
final SetArtifact artifacts = (SetArtifact)project.getArtifacts();
if (artifacts != null) {
returnValue = new ArrayListArtifact();
if (!artifacts.isEmpty()) {
final ListMavenProject projects = new ArrayListMavenProject();
projects.add(project);
if (builder == null) {
builder = new DefaultMavenProjectBuilder();
}
for (final Artifact artifact : artifacts) {
if (artifact != null) {
final MavenProject artifactProject =
builder.buildFromRepository(artifact,
project.getRemoteArtifactRepositories(), localRepository);
assert artifactProject != null;
projects.add(artifactProject);
}
}
final ProjectSorter sorter = new ProjectSorter(projects);
final ListMavenProject sortedProjects =
sorter.getSortedProjects();
assert sortedProjects != null;
assert sortedProjects.size() == projects.size();
final Map projectArtifactMap = project.getArtifactMap();
assert projectArtifactMap != null;
for (final MavenProject p : sortedProjects) {
if (p != null) {
final Artifact artifact = p.getArtifact();
if (artifact != null) {
final Artifact resolvedArtifact =
(Artifact)projectArtifactMap.get(artifact.getGroupId() + : +
artifact.getArtifactId());
if (resolvedArtifact != null (filter == null ||
filter.include(resolvedArtifact))) {
returnValue.add(resolvedArtifact);
}
}
}
}
}
}
return returnValue;
}
RE: Missing links in site generation of multi-module project
Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - 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: Disabling lifecycle with assembly plugin
Hi,
Thanks for the quick response.
I did that and now I'm getting the following error (see bellow).
My descriptor is very simple:
assembly xmlns=
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=
http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
http://maven.apache.org/xsd/assembly-1.1.0.xsd;
idbin/id
formats
formatdir/format
/formats
fileSets
fileSet
directory${project.basedir}/folder//directory
includes
includedoc/**/include
/includes
outputDirectory//outputDirectory
/fileSet
/fileSets
The thing is, everything is copied as expected, but I get the following
error.
Thanks,
Rui
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to create
assembly: Error creating assembly archive bin: You must set at least one
file.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to create
assembly: Error creating assembly archive bin: You must set at least one
file.
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:468)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by:
org.apache.maven.plugin.assembly.archive.ArchiveCreationException: Error
creating assembly archive bin: You must set at least one file.
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:196)
at
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:409)
... 19 more
Caused by: org.codehaus.plexus.archiver.ArchiverException: You must set at
least one file.
at
org.codehaus.plexus.archiver.dir.DirectoryArchiver.execute(DirectoryArchiver.java:49)
at
org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:871)
at
org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:512)
at
org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:192)
... 20 more
On Wed, Feb 16, 2011 at 1:47 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
that goal is deprecated if I recall correctly use the single goal instead
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 16 Feb 2011 12:40, Rui Vilão rpvi...@gmail.com wrote:
Hi all,
I'm having a problem with maven assembly plugin. It happens that I have a
child pom with relative paths and when I hit assembly:assembly the
environment becomes corrupted (that doesn't happen if I hit mvn install,
package whatever in both project's pom directory or in the root of the
major
project). What I want is to disable the lifecycle when I hit
assembly:assembly. I don't want it to perform package, install, etc.
Is that possible?
Any other ideas are welcomed :)
Best regards, thank you in advance,
--
Rui
Re: Missing links in site generation of multi-module project
http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas PS sorry, dense too :) Harpel, Craig wrote: Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - 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: Can a parent adopt a child (pom module/project)?
No. You should work the other way around; start with the pom and use m2eclipse to set up the eclipse project. /Anders (mobile) Den 16 feb 2011 01.32 skrev Andrew Hughes ahhug...@gmail.com: Hey, Is it possible for a parent to effectively inject (or override) this section of a module's pom.xml? parent groupIdcom.acme/groupId artifactIdproject-acme/artifactId verison1.0.0-SNAPSHOT/version /parent This request might seem a little odd, so I will explain... We have a number of generated pom files (via a eclipse export). None of these multi-module pom's have a (common) parent. Consequently I can't easily run a shared configuration. Also, I would like to avoid editing each of the generated pom.xml files, because once we do another export our changes are lost. Thanks for reading :)
RE: Missing links in site generation of multi-module project
Got it! Yes, I can confirm that 2.3-SNAPSHOT does indeed fix my problem. Thanks a lot!! Craig -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 11:01 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project http://maven.apache.org/guides/development/guide-testing-development-plugins.html HTH, -Lukas PS sorry, dense too :) Harpel, Craig wrote: Sorry for being dense, but I don't see a 2.3-SNAPSHOT; where can I grab it from? -Original Message- From: Lukas Theussl [mailto:ltheu...@apache.org] Sent: Wednesday, February 16, 2011 7:49 AM To: Maven Users List Subject: Re: Missing links in site generation of multi-module project I tested your project with maven 2, using site-plugin-2.2 I can reproduce the problem, using current 2.3-SNAPSHOT it's fixed. Can you confirm? -Lukas Harpel, Craig wrote: I'm hoping somebody can tell me what I'm doing wrong here. I have a multi-module project that I've trimmed down to the bare minimum but still represent my original structure: Example_maven_aggregator ---Project1 ---Project2 ---sub-aggregator --SubProject1 --SubProject2 --SubProject3 --SubProject4 When I generate the site (with either Maven 2 or Maven 3), I don't get links for Project1 and Project2 on the main page, just bold text. Is this: a) A known issue? b) A lack of understanding/misconfiguration on my part? My project is available here: git://github.com/corruptedbuffer/example_maven_aggregator.git You'll have to change the site you're deploying to in order to test it (mvn site-deploy). Thanks. Craig - 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: Call System.setProperty(java.awt.headless, true)?
That pretty much kills this idea. Too bad AWT doesn't have an *api* for creating a local headless bubble. On Tue, Feb 15, 2011 at 11:35 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: stupid phone. stop sending empty messages. ok. what i was trying to say us that there are enough people out there who use mvn exec:exec to run their swing apps - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 16 Feb 2011 02:53, Jesse Glick jesse.gl...@oracle.com wrote: On 02/13/2011 04:54 PM, Benson Margulies wrote: It seems to me that it might be a legitimate idea for maven itself to just set headless, at least when invoked from the shell. So long as this is done from the CLI entry point classes, or bin/mvn, and not in core classes where it could cause problems when running embedded in some other container such as an IDE. - 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
subversion vs maven
Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: subversion vs maven
How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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: subversion vs maven
Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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: subversion vs maven
You first need analyze the change level in every component, maybe split a project in more subprojects, so the 'static' code could be managed like a external library, this is, compile it and upload to Maven Proxy, and the changeable code only get from subversion. 2011/2/16 Leon Rosenberg rosenberg.l...@gmail.com How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 -- Cesar De la Cruz Rojas * - * Sennior Software Engineer - Follow me in Facebook : http://www.facebook.com/aquiles.geo Twitter http://twitter.com/ageo Picture blog http://ageo.deviantart.com
RE: subversion vs maven
There is an option Incremental build - only build changed modules under the advanced section of the Build options (for an M2 build). If checked, Hudson will only build any modules with changes from SCM and any modules which depend on those changed modules, using Maven's -amd -pl group1:artifact1,group1:artifact2 command-line options. If the SCM reports no changes to any modules, however, all modules will be built. See http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode for more information on the Maven behavior this utilizes. This functionality requires Maven 2.1 or later, and will not have any impact if Build modules in parallel is selected. Any follow-up on this should be directed at the Jenkins or Hudson users lists. /James -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: 16 February 2011 17:18 To: Leon Rosenberg Cc: Maven Users List Subject: Re: subversion vs maven Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. 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 **
Re: subversion vs maven
Oh, the -pl option seems to be one of the possible solutions. Thank you!! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:21 AM, Nord, James jn...@nds.com wrote: There is an option Incremental build - only build changed modules under the advanced section of the Build options (for an M2 build). If checked, Hudson will only build any modules with changes from SCM and any modules which depend on those changed modules, using Maven's -amd -pl group1:artifact1,group1:artifact2 command-line options. If the SCM reports no changes to any modules, however, all modules will be built. See http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode for more information on the Maven behavior this utilizes. This functionality requires Maven 2.1 or later, and will not have any impact if Build modules in parallel is selected. Any follow-up on this should be directed at the Jenkins or Hudson users lists. /James -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: 16 February 2011 17:18 To: Leon Rosenberg Cc: Maven Users List Subject: Re: subversion vs maven Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. 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
Re: subversion vs maven
Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent
Re: subversion vs maven
You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.com wrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- Cesar De la Cruz Rojas * - * Sennior Software Engineer - Follow me in Facebook : http://www.facebook.com/aquiles.geo Twitter http://twitter.com/ageo Picture blog http://ageo.deviantart.com
Re: subversion vs maven
trust me, not so easy :) our project has like 20 subsystems which all have 5-10 sub-projects. Our core is extracted into a separate dependency maintained by another team, it is also managed by maven ( ~30 subsystems, 10-50 projects each ). Yes, daily updates happen on 5-10 projects, that is why I don't want to build the full build but only the changed projects and their dependents ( web apps ). Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:37 AM, a.geo aquiles@gmail.com wrote: You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- Cesar De la Cruz Rojas - Sennior Software Engineer - Follow me in Facebook : http://www.facebook.com/aquiles.geo Twitter http://twitter.com/ageo Picture blog http://ageo.deviantart.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: subversion vs maven
This is what Build Management Servers can do for you. It could poll each project each morning and only build the ones that have changes. Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 11:47 AM To: users@maven.apache.org Subject: subversion vs maven Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: subversion vs maven
If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that? -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:37 PM To: a.geo Cc: Maven Users List; Jeff Subject: Re: subversion vs maven trust me, not so easy :) our project has like 20 subsystems which all have 5-10 sub-projects. Our core is extracted into a separate dependency maintained by another team, it is also managed by maven ( ~30 subsystems, 10-50 projects each ). Yes, daily updates happen on 5-10 projects, that is why I don't want to build the full build but only the changed projects and their dependents ( web apps ). Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:37 AM, a.geo aquiles@gmail.com wrote: You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- Cesar De la Cruz Rojas --- -- Sennior Software Engineer --- -- Follow me in Facebook : http://www.facebook.com/aquiles.geo Twitter http://twitter.com/ageo Picture blog http://ageo.deviantart.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: subversion vs maven
yes, we could set this up. However there's 2 things: - We're working with SNAPSHOT versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would make it slow I could run a CI / Hundson / whatever other build management server on my laptop...but then it would not be quicker then just the full build :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that? -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:37 PM To: a.geo Cc: Maven Users List; Jeff Subject: Re: subversion vs maven trust me, not so easy :) our project has like 20 subsystems which all have 5-10 sub-projects. Our core is extracted into a separate dependency maintained by another team, it is also managed by maven ( ~30 subsystems, 10-50 projects each ). Yes, daily updates happen on 5-10 projects, that is why I don't want to build the full build but only the changed projects and their dependents ( web apps ). Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:37 AM, a.geo aquiles@gmail.com wrote: You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1 -- s2-project2 -- s2-project3 -- subsystem3 -- s3-project1 Thank you for any ideas! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.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 -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- Cesar De la Cruz Rojas --- -- Sennior
Re: setting permissions of basedir in maven-assembly-plugin
On 02/15/2011 12:58 PM, Steve Cohen wrote: I can set the permissions of fileSets and moduleSets and dependencySets in the maven-assembly-plugin, but it seems from the online documentation that I can't do so on the baseDir. What is more, when assembling a zip format, the perms default to 777. At least that's what I get when I unzip the file (having erased the basedir previously so that there's no chance of previous permissions persisting). Is there any way to control this? I am using my own assembly descriptor. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org This worked for me: fileSets fileSet outputDirectory//outputDirectory fileMode750/fileMode directoryMode750/directoryMode includes include.//include /includes /fileSet ... Is there a THOROUGH description of include/exclude wildcards anywhere? I had to hunt and peck my way through all kinds of possibilities before I found something that worked as I wanted it to. For example excludes exclude**/exclude /excludes didn't work because the root directory was included in the exclusion, yet, without the include I had above, the root directory was not included. This topic could do with a bit of rigorous documentation that seems lacking. It's treated as self-evidently obvious how this works, and usually it is, but then you have these odd cases to scratch your head on. I think the problem here is that includes has a dual meaning. It's main meaning is whether the set should be included in the archive, but it also has this subsidary use that defines where the modes should apply and the two are not in synch. Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Deployment in Repository without version in file name?
you can also use the dependency plugin to copy/fetch files and strip
off the version.
On Wed, Feb 16, 2011 at 3:37 AM, Marc Rohlfs pomar...@googlemail.com wrote:
Another idea might be:
1. In Your Maven project, create a text file with the following content:
http://your-nexus/your-nexus-repo/${project.artifactId}-${project.version}.${project.packaging}
2. Use the 'resources:copy-resources' with 'filtering=true' to copy the file
somewhere and get its tokens replaced (see
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html).
3. Use wget with the -i (--input-file=FILE) option and the '-O' option.
-
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
maven antrun plugin with sql task closing the maven process itself
Hi, I'm using maven antrun plugin to shutdown the hsqldb connection after the unit test. I have binded the antrun run goal with the post-integration-test. And in that goal I'm actually running a sql script having shutdown command. when I run the mvn post-integration-test in the parent directory, hsqldb connection is closing gracefully. But after the execution of the shutdown.sql script in antrun. Its stopping there without leaving any message (such as build error, build failure, build success). And also it is not executing the tests of the remaining submodules. I'm kind of confused with this behavior of maven antrun. Can any one help in this regard. Thanks, Santhosh -- View this message in context: http://maven.40175.n5.nabble.com/maven-antrun-plugin-with-sql-task-closing-the-maven-process-itself-tp3387689p3387689.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: subversion vs maven
You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U. The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:52 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven yes, we could set this up. However there's 2 things: - We're working with SNAPSHOT versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would make it slow I could run a CI / Hundson / whatever other build management server on my laptop...but then it would not be quicker then just the full build :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that? -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:37 PM To: a.geo Cc: Maven Users List; Jeff Subject: Re: subversion vs maven trust me, not so easy :) our project has like 20 subsystems which all have 5-10 sub-projects. Our core is extracted into a separate dependency maintained by another team, it is also managed by maven ( ~30 subsystems, 10-50 projects each ). Yes, daily updates happen on 5-10 projects, that is why I don't want to build the full build but only the changed projects and their dependents ( web apps ). Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:37 AM, a.geo aquiles@gmail.com wrote: You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update. So I was thinking - is there any way to configure maven to build only the projects which were updated by SVN ( e.g. in the script time )? Most likely there is no direct answer...however, I think that I could find a way to gather the project names which were updated in the shell script - then I could pass the list of project names to maven command. Is there any way to make sure that those and dependent projects would be built in the right order? The project structure is: parent -- subsystem1 -- s1-project1 -- s1-project2 -- subsystem2 -- s2-project1
Re: subversion vs maven
Theoretically - yes Practically - no We were using the approach with CI and snapshots from the repo long time ago, however in a lot of cases we came to a case where the project does not compile or work as expected when having different snapshot versions, or takes just a very long time to at least package the project you're working on, so in the long term to make it quick, safe and making sure that all my modified but not committed modules get into the app from my local, not external repo ( in case they're older ) - we just do the build on our boxes. Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com 2011/2/16 Thiessen, Todd (Todd) tthies...@avaya.com: You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U. The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:52 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven yes, we could set this up. However there's 2 things: - We're working with SNAPSHOT versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would make it slow I could run a CI / Hundson / whatever other build management server on my laptop...but then it would not be quicker then just the full build :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that? -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:37 PM To: a.geo Cc: Maven Users List; Jeff Subject: Re: subversion vs maven trust me, not so easy :) our project has like 20 subsystems which all have 5-10 sub-projects. Our core is extracted into a separate dependency maintained by another team, it is also managed by maven ( ~30 subsystems, 10-50 projects each ). Yes, daily updates happen on 5-10 projects, that is why I don't want to build the full build but only the changed projects and their dependents ( web apps ). Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:37 AM, a.geo aquiles@gmail.com wrote: You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which takes ~30-40 minutes. But I want to build only specific projects and their dependents. Regards Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 9:54 AM, Leon Rosenberg rosenberg.l...@gmail.com wrote: How about hudson? Hudson can watch for svn changes and trigger builds on commit. regards Leon On Wed, Feb 16, 2011 at 5:46 PM, Zilvinas Vilutis cika...@gmail.com wrote: Hello Maven Users! Probably this question was already asked, so if there is an answer which I could not find - please point me to the right place. I'm working on an enterprise project where maven integration plays a huge role. However the project is big as a lot of teams are working on it and it takes quite some time to build it ( 30-40 minutes ), which I need to do every morning after an svn update.
Re: maven antrun plugin with sql task closing the maven process itself
is there a fork / no fork mode? Use no-fork to create a separate JVM instance for hsqldb...if possible Regards - nothing is impossible -- View this message in context: http://maven.40175.n5.nabble.com/maven-antrun-plugin-with-sql-task-closing-the-maven-process-itself-tp3387689p3388333.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: subversion vs maven
Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install. You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Just a thought. Hope it helps. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 3:12 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven Theoretically - yes Practically - no We were using the approach with CI and snapshots from the repo long time ago, however in a lot of cases we came to a case where the project does not compile or work as expected when having different snapshot versions, or takes just a very long time to at least package the project you're working on, so in the long term to make it quick, safe and making sure that all my modified but not committed modules get into the app from my local, not external repo ( in case they're older ) - we just do the build on our boxes. Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com 2011/2/16 Thiessen, Todd (Todd) tthies...@avaya.com: You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U. The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:52 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven yes, we could set this up. However there's 2 things: - We're working with SNAPSHOT versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would make it slow I could run a CI / Hundson / whatever other build management server on my laptop...but then it would not be quicker then just the full build :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that? -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:37 PM To: a.geo Cc: Maven Users List; Jeff Subject: Re: subversion vs maven trust me, not so easy :) our project has like 20 subsystems which all have 5-10 sub- projects. Our core is extracted into a separate dependency maintained by another team, it is also managed by maven ( ~30 subsystems, 10-50 projects each ). Yes, daily updates happen on 5-10 projects, that is why I don't want to build the full build but only the changed projects and their dependents ( web apps ). Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 10:37 AM, a.geo aquiles@gmail.com wrote: You mus consider a core section, that contain your business main code, usually you don't change it. Around it, is the implementation of the requirement. 2011/2/16 Jeff predato...@gmail.com Maybe this question will expose my ignorance, but I thought most build systems only build the things that have changed unless you do a clean each time or are starting from a fresh checkout as opposed to doing an svn update and then running the build. Being new to Maven myself, there could there be an option in the POM that might be forcing a full build each time? I would think that as long as you aren't specifying clean in your build kickoff process or otherwise forcing a full biuld, you should only be getting the incremental build, no? Am I off in my understanding? On Wed, Feb 16, 2011 at 10:18 AM, Zilvinas Vilutis cika...@gmail.comwrote: Yes, However it does a full build which
Re: subversion vs maven
You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. Exactly :) When doing it incrementally - that's how it should work when building only changed projects and their dependents, what the original question was So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Yeah, this sounds good when working in a dev environment. However I'm on my own in the customers' office where network latency is not enough to download the artifacts quickly. Anyways, in this case - if I changed my code yesterday and did not commit it to SVN - then the downloaded snapshot would be newer and will be put in my webapp's war. In most cases - other people are updating the same projects as I'm working on so they would almost all the time match the right projects to be built. And my projects would not get built during the full-build - they would already exist in my local repo so they would be picked up when building the war. I guess I will try to make the most use of the maven reactor ( http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode ) to use the --project-list ( for specifying updated projects ) and --also-make-dependents parameters is exactly what I want. Thank you all for ideas help! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 1:22 PM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install. You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Just a thought. Hope it helps. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 3:12 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven Theoretically - yes Practically - no We were using the approach with CI and snapshots from the repo long time ago, however in a lot of cases we came to a case where the project does not compile or work as expected when having different snapshot versions, or takes just a very long time to at least package the project you're working on, so in the long term to make it quick, safe and making sure that all my modified but not committed modules get into the app from my local, not external repo ( in case they're older ) - we just do the build on our boxes. Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com 2011/2/16 Thiessen, Todd (Todd) tthies...@avaya.com: You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U. The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:52 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven yes, we could set this up. However there's 2 things: - We're working with SNAPSHOT versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would make it slow I could run a CI / Hundson / whatever other build management server on my laptop...but then it would not be quicker then just the full build :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 11:41 AM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: If you have a CI server already building everything, why do you need to build everything every morning? Can't you just checkout only the one module you need to change and build that? -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:37 PM To: a.geo Cc: Maven Users List;
RE: subversion vs maven
This sounds like you need to do more svn updates on projects you are working on. My suggestion would be to do that SVN update on those projects, resolve any conflicts, and then run the maven install. This will make your version into the latest in your repository. It may also help if you checked in your code a little quicker. You might be letting your code get to far out of sync. Russell Collins Sr. Software Engineer CoreLogic Spatial Solutions Do or do not, there is no try. - Yoda -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 2:41 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. Exactly :) When doing it incrementally - that's how it should work when building only changed projects and their dependents, what the original question was So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Yeah, this sounds good when working in a dev environment. However I'm on my own in the customers' office where network latency is not enough to download the artifacts quickly. Anyways, in this case - if I changed my code yesterday and did not commit it to SVN - then the downloaded snapshot would be newer and will be put in my webapp's war. In most cases - other people are updating the same projects as I'm working on so they would almost all the time match the right projects to be built. And my projects would not get built during the full-build - they would already exist in my local repo so they would be picked up when building the war. I guess I will try to make the most use of the maven reactor ( http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode ) to use the --project-list ( for specifying updated projects ) and --also-make-dependents parameters is exactly what I want. Thank you all for ideas help! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 1:22 PM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install. You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Just a thought. Hope it helps. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 3:12 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven Theoretically - yes Practically - no We were using the approach with CI and snapshots from the repo long time ago, however in a lot of cases we came to a case where the project does not compile or work as expected when having different snapshot versions, or takes just a very long time to at least package the project you're working on, so in the long term to make it quick, safe and making sure that all my modified but not committed modules get into the app from my local, not external repo ( in case they're older ) - we just do the build on our boxes. Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com 2011/2/16 Thiessen, Todd (Todd) tthies...@avaya.com: You could control your dependencies by checking out which ever dependencies you care about and ensure you build those as well. Normally, you would just want the snapshot versions anyway. There is also a properity in your settings.xml file to instruct maven to never check for updates. To get latest snapshot artifacts you would have to issue a mvn -U. The whole idea here is that you should only every be compiling and downloading what you need. Let your CI server do the full builds. You should rarely have to. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 1:52 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven yes, we could set this up. However there's 2 things: - We're working with SNAPSHOT versions most of the time with CI you can hardly control when to use YOUR code versus from the repo in a big projcet - I'm working in a client's office and the network latency between our office and clients office would
Re: subversion vs maven
This sounds like you need to do more svn updates on projects you are working on. My suggestion would be to do that SVN update on those projects, resolve any conflicts, and then run the maven install. This will make your version into the latest in your repository. That's what I do every morning before starting work, as I've wrote in the original e-mail. I'm in a different timezone from other teams, so I don't really need updating more often. I do SVN update, resolve conflicts run the full build to make sure that all dependencies are built, that they compile and that all changes are added to the webapp ( war ). However, doing an SVN update does not let me avoid doing the full build :) I mean, yes when you're working on 2-3 projects at the same time - then yes, it is easy to update them manually from time to time. But when during SVN updates you get updates which require updates from other projects and you don't know which ones - then a full build is required, or at least full SVN update and then building all the updated projects, installing to your local repo and building the app war. Yes, it is possible to build them manually, and copy to your app manually to save time, but it would take like 10-15 minutes to do that for ~5 projects, instead of that I'm looking for an automated solution which would do the job in 15 minutes for me, so I could drink coffee during that time :) Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 1:54 PM, Collins, Russell rcoll...@corelogic.com wrote: This sounds like you need to do more svn updates on projects you are working on. My suggestion would be to do that SVN update on those projects, resolve any conflicts, and then run the maven install. This will make your version into the latest in your repository. It may also help if you checked in your code a little quicker. You might be letting your code get to far out of sync. Russell Collins Sr. Software Engineer CoreLogic Spatial Solutions Do or do not, there is no try. - Yoda -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 2:41 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. Exactly :) When doing it incrementally - that's how it should work when building only changed projects and their dependents, what the original question was So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Yeah, this sounds good when working in a dev environment. However I'm on my own in the customers' office where network latency is not enough to download the artifacts quickly. Anyways, in this case - if I changed my code yesterday and did not commit it to SVN - then the downloaded snapshot would be newer and will be put in my webapp's war. In most cases - other people are updating the same projects as I'm working on so they would almost all the time match the right projects to be built. And my projects would not get built during the full-build - they would already exist in my local repo so they would be picked up when building the war. I guess I will try to make the most use of the maven reactor ( http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode ) to use the --project-list ( for specifying updated projects ) and --also-make-dependents parameters is exactly what I want. Thank you all for ideas help! Žilvinas Vilutis Mobile: (+370) 652 38353 E-mail: cika...@gmail.com On Wed, Feb 16, 2011 at 1:22 PM, Thiessen, Todd (Todd) tthies...@avaya.com wrote: Ok. You should be able to achieve the same result by configuring your settings.xml file to never update snapshots. That way you have more control. When you want to get latest snapshots, issue mvn -U install. You don't need to do a full build AND you will only be using artifacts in your local repository. Sounds like its exactly what you want. So when you get in in the morning, issue a mvn -U install on your module, and you will get latest artifacts installed to your local repo (don't have to do a full build). For the rest of the day, do a mvn install to do your module builds and snapshots won't get updated. Just a thought. Hope it helps. -Original Message- From: Zilvinas Vilutis [mailto:cika...@gmail.com] Sent: Wednesday, February 16, 2011 3:12 PM To: Maven Users List Cc: Thiessen, Todd (Todd) Subject: Re: subversion vs maven Theoretically - yes Practically - no We were using the approach with CI and snapshots from the repo long time ago, however in a lot of cases we came to
Re: eclipse:eclipse maven 3.0.1 not adding dependency
On Tue, Feb 8, 2011 at 8:13 PM, Mathias Nilsson wicket.program...@gmail.com wrote: Hi again, I have fixed this now but it didn't help with just mvn clean:clean install to get it in the local repository. I also needed to mvn eclipse:eclipse on all referencing projects to get it to work. This was not necessary when working on the pc. When you say I have fixed this, it is very important to specify *how* you fixed this. This is needed so that others facing the same problem can use your knowledge to fix their problems. I note in other emails later that you are still having problems. Therefore it's may also be possible that your fix is not correct, but since I don't know what you did I can't help.
Re: eclipse:eclipse maven 3.0.1 not adding dependency
On Wed, Feb 16, 2011 at 2:44 AM, Mathias Nilsson wicket.program...@gmail.com wrote: I still can't build my applications. My dependency to my own project is not included! It will be included if I build it to repository and delete it from eclipse! Did you follow my original advice? Stop trying to get mvn eclipse:eclipse to work. Create a fresh workspace and then manually configure your eclipse projects so that they are working. Once they are working you can then compare the working copy with the broken mvn eclipse:eclipse copy. You need to look at .project and .classpath files.
Re: Call System.setProperty(java.awt.headless, true)?
On 02/15/2011 11:35 PM, Stephen Connolly wrote: there are enough people out there who use mvn exec:exec to run their swing apps Do you mean exec:java? (exec:exec -Dexec.executable=java would be unaffected.) It's not a very good idea to run an arbitrary app this way, since there are plenty of opportunities for the result to be subtly different than running the app in its own JVM, and you have no opportunity to customize VM options. But it is probably true that a lot of people do it anyway. Perhaps exec:java should fork unless explicitly requested to run in-VM. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Repository Confusion
I have an internal repository, Archiva, setup and running. I uploaded a library using the Admin UI that comes with Archiva. On my personal machine I can fetch the library with Maven but on 2 others I can't get it. When I browse the repository I see it added a timestamp to the jar name. Is this expected? Could I have something configured wrong on the other 2 machines? I tried deleting my entire local repository to see if I could get it to fail locally but it still works on my 1 machine.
Re: Repository Confusion
Hi Shay, Was the settings.xml properly configured in the other 2 machines? Btw, you may want to move this over to users@archiva.a.o instead :) Thanks, Deng On Thu, Feb 17, 2011 at 1:03 PM, Shay Thompson sthom...@adobe.com wrote: I have an internal repository, Archiva, setup and running. I uploaded a library using the Admin UI that comes with Archiva. On my personal machine I can fetch the library with Maven but on 2 others I can't get it. When I browse the repository I see it added a timestamp to the jar name. Is this expected? Could I have something configured wrong on the other 2 machines? I tried deleting my entire local repository to see if I could get it to fail locally but it still works on my 1 machine. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Repository Confusion
Settings.xml is exactly the same on all machines. I wasn't aware of an archiva list nor am I sure this is an archiva problem.. *shrug* -Original Message- From: odeach...@gmail.com [mailto:odeach...@gmail.com] On Behalf Of Deng Ching Sent: Wednesday, February 16, 2011 11:39 PM To: Maven Users List Subject: Re: Repository Confusion Hi Shay, Was the settings.xml properly configured in the other 2 machines? Btw, you may want to move this over to users@archiva.a.o instead :) Thanks, Deng On Thu, Feb 17, 2011 at 1:03 PM, Shay Thompson sthom...@adobe.com wrote: I have an internal repository, Archiva, setup and running. I uploaded a library using the Admin UI that comes with Archiva. On my personal machine I can fetch the library with Maven but on 2 others I can't get it. When I browse the repository I see it added a timestamp to the jar name. Is this expected? Could I have something configured wrong on the other 2 machines? I tried deleting my entire local repository to see if I could get it to fail locally but it still works on my 1 machine. - 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: Repository Confusion
You are asking about your Maven settings.xml? The file should be called settings.xml (note case!) not Settings.xml on platforms and filesystems that filename case-sensitive. For example, Settings.xml would work on Windows/NTFS but not on Unix or Linux, where only settings.xml (lowercase) would work. Kind regards, Ben. On 17/02/11 13:41, Shay Thompson wrote: Settings.xml is exactly the same on all machines. -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Repository Confusion
Outlook likes to capitalize. My file has a lower-case s. -Original Message- From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] Sent: Wednesday, February 16, 2011 11:58 PM To: Maven Users List Cc: Shay Thompson Subject: Re: Repository Confusion You are asking about your Maven settings.xml? The file should be called settings.xml (note case!) not Settings.xml on platforms and filesystems that filename case-sensitive. For example, Settings.xml would work on Windows/NTFS but not on Unix or Linux, where only settings.xml (lowercase) would work. Kind regards, Ben. On 17/02/11 13:41, Shay Thompson wrote: Settings.xml is exactly the same on all machines. -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre
Re: eclipse:eclipse maven 3.0.1 not adding dependency
My problem now is that even if I have added my project as reference Spring won´t recognize my beans. Is there a change with this for 2x and 3x? Why isn't my project added as a var as it always has on the pc? -- View this message in context: http://maven.40175.n5.nabble.com/eclipse-eclipse-maven-3-0-1-not-adding-dependency-tp3330388p3388969.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: Repository Confusion
What's the exact error you're getting in Maven for the 2 machines? -Deng On Thu, Feb 17, 2011 at 2:35 PM, Shay Thompson sthom...@adobe.com wrote: Outlook likes to capitalize. My file has a lower-case s. -Original Message- From: Ben Caradoc-Davies [mailto:ben.caradoc-dav...@csiro.au] Sent: Wednesday, February 16, 2011 11:58 PM To: Maven Users List Cc: Shay Thompson Subject: Re: Repository Confusion You are asking about your Maven settings.xml? The file should be called settings.xml (note case!) not Settings.xml on platforms and filesystems that filename case-sensitive. For example, Settings.xml would work on Windows/NTFS but not on Unix or Linux, where only settings.xml (lowercase) would work. Kind regards, Ben. On 17/02/11 13:41, Shay Thompson wrote: Settings.xml is exactly the same on all machines. -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
