jira.codehaus.org

[MNG-1423] best practices: setting up multi-module build

Related — Thu, 18 Dec 2008 07:37:31 -0600 (CST)

Things to consider for a multi-module build are:

o version management
o release management

Current I am (jvz) using the Geronimo build at Apache as an example of this.

[MNG-1425] best practices: the location of configuration files vs resources

Thu, 18 Dec 2008 07:38:12 -0600 (CST)

This may collapse into one of the other best practices issues, but this will hold the thought for now. Vincent maybe you can link in some thoughts from the mailing list?

[MNG-1441] Starting thinking about a proper distributed repository mechanism a la CPAN

Mon, 25 Aug 2008 14:40:01 -0500 (CDT)

We might want to actually contact the folks at CPAN to see if we could learn from them or piggy back upon their setup.

[MNG-1463] best practices: plugin inheritance for a multi project build

Thu, 18 Dec 2008 07:37:57 -0600 (CST)

The standard way of creating a malleable build as Chris calls it. I believe he had a way he liked. This is a place holder to collect that information.

[MNG-1468] best practices: version management in multi project builds

Related — Thu, 18 Dec 2008 07:57:51 -0600 (CST)

How to manage versions from a single place in a multi project build.

The reference in the wiki can be found here:

http://docs.codehaus.org/display/MAVEN/Maven+Best+Practices

[MNG-1701] Validate that a plugin is not configured twice in the pom

Duplicate — Mon, 28 Dec 2009 18:56:42 -0600 (CST)

Check that there're no two <plugin> elements of the same plugin

[MNG-1867] deprecate system scope, analyse other use cases

Duplicate — Wed, 30 Dec 2009 18:44:01 -0600 (CST)

possibly can avoid all use cases for system scope through proper use of alternate resolvers. Gather use cases (see MNG-1471) to ensure.

[MNG-2834] "from the specified remote repositories" message incorrect

Sat, 13 Dec 2008 18:35:07 -0600 (CST)

I am getting this message on a not found dependency:

from the specified remote repositories:
ggg-dev (http://mvn.ggg.be/maven2/dev),
apache.snapshots (http://svn.apache.org/maven-snapshot-repository),
ggg-deploy (http://mvn.ggg.be/maven2/deploy),
snapshots (http://snapshots.maven.codehaus.org/maven2),
central (http://repo1.maven.org/maven2)

But that dependency (commons-collections:commons-collections:jar:2.0) is in ibiblio.
However, we don't use ibiblio, because we configured our repositories like this:

<repositories>
<repository>
<id>central</id>
<name>ggg deploy repository</name>
<url>http://mvn.ggg.be/maven2/deploy</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>ggg-dev</id>
<name>ggg dev repository</name>
<url>http://mvn.ggg.be/maven2/dev</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>ggg-deploy</id>
<name>ggg deploy repository</name>
<url>http://mvn.schaubroeck.be/maven2/deploy</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>ggg-dev</id>
<name>Schaubroeck dev repository</name>
<url>http://mvn.schaubroeck.be/maven2/dev</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>

So the following lines of "from the specified remote repositories" are incorrect:
apache.snapshots (http://svn.apache.org/maven-snapshot-repository),
snapshots (http://snapshots.maven.codehaus.org/maven2),
central (http://repo1.maven.org/maven2)

PS: especially those snapshots in there scared me... I deleted my entire repo, verified that we do not include snapshot repo's and still they show up in that list.

[MNG-2872] Don't append artifactId when parent pom already has artifactId in URL

Related — Tue, 12 Jan 2010 11:21:16 -0600 (CST)

I want to define the url for all my projects from one central pom. the pom project itself has the same url structure as the child projects.

This is for all urls that can be inherited, e.g. distribution site, deployment url, etc.

I would like to specify some complete url like

protocol:/my.server.com/some/path/to/the/${groupId}/${artifactId}

For example, with the actual implementation I get either the parent pom site deployed to the groupId directory, or I get the child projects deployed to the grouId/artifactId/artifactId directory.

At the moment I have add the urls on every project, although they always have the same pattern.

[MNG-3529] mvn -Da=" " throws an excepltion

Duplicate — Tue, 9 Feb 2010 07:23:43 -0600 (CST)

Doing,

mvn -Da=" "

throws,

---------------------------------------------------
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java:146)
at java.lang.StringBuffer.setLength(StringBuffer.java:154)
at org.apache.maven.cli.MavenCli$CLIManager.cleanArgs(MavenCli.java:793)
at org.apache.maven.cli.MavenCli$CLIManager.parse(MavenCli.java:746)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:100)
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:585)
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)

[MNG-3844] Review inheritance of SCM info

Related — Tue, 12 Jan 2010 11:21:20 -0600 (CST)

Consider this parent POM snippet:

<scm>
  <url>http://parent.url/viewvc</url>
  <connection>http://parent.url/scm</connection>
  <developerConnection>https://parent.url/scm</developerConnection>
  <tag>parent-tag</tag>
</scm>

And now this child POM snippet:

<scm>
  <developerConnection>https://child.url/scm</developerConnection>
</scm>

This delivers the effective child POM:

<scm>
  <url>http://parent.url/viewvc/child</url>
  <connection>http://parent.url/scm/child</connection>
  <developerConnection>https://child.url/scm</developerConnection>
</scm>

i.e. <url> and <connection> are still inherited.

This appears neither sensible nor consistent with other inheritance rules (e.g. <ciManagement> and <issueManagement> are only inherited if completely omitted in the child).

[MNG-3926] Spaces if properties are not preserved if using CDATA

Tue, 12 Jan 2010 11:50:32 -0600 (CST)

Using a property like this one:

results into an empty property (see effective-pom):

which is wrong.
See also the XML spec:

"Note that a CDATA section containing only white space or a reference to an entity whose replacement text is character references expanding to white space do not match the nonterminal S"

which also stats that white spaces inside CDATA must not be trimmed away.

[MNG-3928] Maven Integration with Bash

Fri, 27 Mar 2009 07:59:55 -0500 (CDT)

Maven already has a mini guide on this located here: http://maven.apache.org/guides/mini/guide-bash-m2-completion.html

However, I have significantly enhanced the bash completion for Maven using mostly automated means. Please review the attached m2 script and if it is found to be a worthy update, then simply use the contents of the script as a drop in replacement for the current one.

Thanks!

[MNG-4099] Password encryption CLI switches should prompt for password if missing

Tue, 12 Jan 2010 11:21:17 -0600 (CST)

The -emp and -ep CLI switches should prompt for a password if the user omits it. This would help to avoid having to escape shell characters in strong passwords.

Note that the docs mention that these switches prompt for a password when they do not:
http://maven.apache.org/guides/mini/guide-encryption.html

[MNG-4485] Informational messages could be clearer regarding goal execution

Mon, 7 Dec 2009 00:20:11 -0600 (CST)

As the lifecycle of projects are executed, these type of informational messages are emitted:
[INFO] — maven-clean-plugin:2.3:clean (default-clean) @ project-name ---

Based on my own team, I think there are three things to note:

The plugin:version::goal can easily be confused with the the dependency artifactId:version:classifier format. Seriously.
I don't think the @ symbol is natural to describe the project.
The execution name probably could be suppressed unless DEBUG was on.

How about?
[INFO] — maven-clean-plugin:2.3 executing goal "clean" for project Project Name ---

[MNG-864] Fail the build with a nice error message if a property to be interpolated in pom.xml is not defined

Wed, 5 Sep 2007 02:23:31 -0500 (CDT)

There are uses cases with pom.xml requiring an environment-specific property to be defined. If those property are not provided by the user in a settings.xm, profiles.xml or a command-line system property then m2 should fail the build with a nice error explaiing the reason.

[MNG-1142] restriction of [1.6,) and [1.5,1.6.2) in that order results in 1.6.2 instead of 1.6.1

Duplicate — Sat, 13 Dec 2008 18:34:42 -0600 (CST)

got this by adding ant [1.6,) to it0034, and ant [1.5,1.6.2) to one of its deps (deeper).

I think this is caused by the fact that versions are resolved too early instead of retaining the restriction, but it needs a further look.

[MNG-1204] don't show disabled repositories in artifact exceptions

Thu, 11 Jan 2007 01:50:59 -0600 (CST)

don't show disabled repositories in artifact exceptions

[MNG-1974] Improve repository searching for artifacts

Related — Sat, 13 Dec 2008 18:34:55 -0600 (CST)

Currently, if there are multiple repositories defined in poms and or settings, each time an artifact is retreived, it searches through the list, displaying warnings that couldn't be found for each repository. There are 2 enhancements that I can think of:

1. Don't print warning when it can't be found in the repository, unless it can't be found anywhere. This is just a neusance and clutters the screen. If it printed the url when it actually found it, I would be able to see where it came from and that's more than sufficient.
2. When looking for a jar, try looking where you just found the pom. I can't think of a good reason why it would be good to grab a jar from a repo different than where we found the pom. In this case, it just throws up a bunch more warnings when it should know where exactly to find the jar.

[MNG-2017] Dependencies with scope system and version range make the build fail

Related — Mon, 9 Nov 2009 09:48:28 -0600 (CST)

Same as ~~MNG-1363~~ but this time for direct dependencies, it shouldn't try to resolve versions for system scope deps

<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<scope>system</scope>
<version>[1.4,)</version>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>

No versions are present in the repository for the artifact with a range [1.4,)
com.sun:tools:jar:null

from the specified remote repositories:
central (http://test.maven.codehaus.org/maven2)

[INFO] ----------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: No versions are present in the repository for the artifact with a range [1.4,)
com.sun:tools:jar:null

from the specified remote repositories:
central (http://test.maven.codehaus.org/maven2)

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:274)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
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:585)
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.artifact.versioning.OverConstrainedVersionException: No versions are present in the repository for the artifact with a range [1.4,)
com.sun:tools:jar:null

from the specified remote repositories:
central (http://test.maven.codehaus.org/maven2)

at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:265)
at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:67)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:182)
at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1120)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:369)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more

[MNG-2038] A mini guide covering the interplay between SCM and maven releases

Thu, 14 Jun 2007 23:31:25 -0500 (CDT)

Emmanuel Venisse asked if I would contribute this document, so here it is. It is a step by step guide which covers releasing a project using maven, but also demonstrates some best practices when it comes to making branches, tags, and of course versions, all while touching on how maven makes these practices so much less of a headache.

[MNG-2116] Add strict mode, to avoid any stubbing, dummying, etc. activities to account for missing data.

Sun, 27 Dec 2009 14:05:40 -0600 (CST)

Currently, Maven will create a stub POM when it cannot find one on the remote repository. However, there are cases where we need to have the ability to verify that all the components of an application or some other type of build are present. Therefore, we need a strict mode for Maven, which will suppress any stubbing activities like this.

[MNG-2187] Improve error message when the pom is encoded in the wrong charset

Related — Sun, 27 Dec 2009 14:27:10 -0600 (CST)

When the pom is encoded in a charset different than the one declared in the xml header (UTF8 by default) and containing an special char (ó or something like that), under Sun's JDK there's no error but under IBM JDK it crashes with
sun.io.MalformedInputException

It'd be good if we could check first the encoding or capture the exception and show an error message instead.

[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ----------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).

Project ID: unknown

Reason: Failed to build model from file '/home/demo/plexus-compiler/pom.xml'.
Error: 'null'

[INFO] ----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to build model from file '/home/demo/plexus-compiler/pom.xml'.
Error: 'null'
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
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.project.ProjectBuildingException: Failed to build model from file '/home/demo/plexus-compiler/pom.xml'.
Error: 'null'
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1103)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:289)
at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
... 12 more
Caused by: sun.io.MalformedInputException
at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java(Compiled Code))
at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java(Inlined Compiled Code))
at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java(Compiled Code))
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java(Compiled Code))
at java.io.InputStreamReader.read(InputStreamReader.java:208)
at java.io.Reader.read(Reader.java:113)
at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:212)
at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:200)
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1117)
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1094)
... 17 more
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Wed Mar 29 04:25:41 PST 2006
[INFO] Final Memory: 2M/5M
[INFO] ----------------------------------------------------------------------------

[MNG-2194] no downloading attempts of non-existing artifact

Mon, 28 Dec 2009 19:32:04 -0600 (CST)

I'm converting a project to maven 2. Some dependencies do not exist in
ibiblio, so I've 'installed' these into my local repository.

I'm unhappy because every time I perform a run, there is a significant
delay (sometimes) when maven tries to download these non-existent
artifacts. I get these messages:
Downloading: http://repo1.maven.org/maven2/......./...pom

How can I prevent maven's attempt to download these non-existent
artifacts? I'm most interested in eliminating the delay.

I know I can run with the 'offline' option. This is OK as long as I'm
sure all existing artifacts that are already downloaded into my cache.
So I can do this until I build on a system with no local cache of add a
new dependency to my projects, at which time the delay is experienced
due to these non-existent artifacts.

[MNG-2197] Add a MavenProject.addArtifact() method

Thu, 11 Jan 2007 02:04:03 -0600 (CST)

See http://www.nabble.com/MavenProject.addArtifact%28%29-t1369889.html#a3700811