[jira] Commented: (MNG-3057) properties not expanded in generated POMs when building A/B/C nested projects
[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166845#action_166845
]
Benjamin Bentmann commented on MNG-3057:
John, the removal of the license header was a regression of MNG-2820 for which
I just added a (disabled) IT.
> properties not expanded in generated POMs when building A/B/C nested projects
> -
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.7
>Reporter: George Armhold
>Assignee: John Casey
> Fix For: 2.1.0
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-install-parent.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
>$ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-392) Big slowdown on Linux when upgrading assembly plugin from 2.2-beta-1 to 2.2-beta-3
Big slowdown on Linux when upgrading assembly plugin from 2.2-beta-1 to
2.2-beta-3
--
Key: MASSEMBLY-392
URL: http://jira.codehaus.org/browse/MASSEMBLY-392
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-3
Environment: Java 1.6
Maven 2.0.9
Linux (Redhat)
Reporter: Fredrik Arvidsson
Our build on Linux (redhat) has more than doubled in time since we upgraded the
assembly plugin from 2.2-beta-1 to 2.2-beta-3.
I did some testing with a tiny project for different versions of the assembly
plugin:
2.2-beta-1: 9 seconds
2.2-beta-2: 17 seconds
2.2-beta-3: 30 seconds
The project is really small, it contains only 1 source file. The assembly
plugin declaration in the pom is:
{noformat}
maven-assembly-plugin
2.2-beta-3
src/main/assembly/descriptor.xml
${project.build.directory}/dist
${project.build.directory}/assembly/work
true
${parent.version}
${buildNumber}
${timestamp}
${copyright}
assemble
single
package
{noformat}
The descriptor.xml includes a few local files and then about 20 jars from
dependencies, most of them are included through the transitive mechanism.
{noformat}
bin
zip
src/main/bin
bin
*
774
src/main/resources
resources
*
target
lib
*.jar
false
lib
{noformat}
Any idea what causes the slowdown? How can we avoid id?
We are running Java 1.6 and Maven 2.0.9. We use an Artifactory proxy but it
should not be a factor as I run the tests repeatedly so everything should be in
the local repo.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (DOXIA-291) Wrong classid in SwfMacro
Wrong classid in SwfMacro
-
Key: DOXIA-291
URL: http://jira.codehaus.org/browse/DOXIA-291
Project: Maven Doxia
Issue Type: Bug
Components: Core
Reporter: Denis Knauer
There is a missing ": D" (without space) in the classid of the SwfMacro.
The actual version looks like:
{code:title=SwfMacro.java|borderStyle=solid}
content.append( "http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=";
)
.append( version ).append( "\" width=\"" ).append( width ).append(
"\" height=\"" ).append( height )
.append( "\" id=\"" ).append( id ).append( "\">" ).append( EOL );
{code}
Ist must be:
{code:title=SwfMacro.java|borderStyle=solid}
content.append( "http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=";
)
.append( version ).append( "\" width=\"" ).append( width ).append(
"\" height=\"" ).append( height )
.append( "\" id=\"" ).append( id ).append( "\">" ).append( EOL );
{code}
The swf File is not included correctly otherwise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-4049) FATAL ERROR
FATAL ERROR
---
Key: MNG-4049
URL: http://jira.codehaus.org/browse/MNG-4049
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: Matthew Corby-Eaglen
{code}
$ mvn -v
Maven version: 2.0.10
Java version: 1.4.2_05
OS name: "sunos" version: "5.10" arch: "x86" Family: "unix"
$ mvn clean install
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Error building POM (may not be this project's POM).
Project ID: unknown
POM Location: /data/cruisecontrol/projects/WebAppPom/pom.xml
Reason: Parse error reading POM. Reason: Unrecognised association: 'inherited'
(position: START_TAG seen ...\n\t\t\t\t\t... @42:17)
for project unknown at /data/cruisecontrol/projects/WebAppPom/pom.xml
[INFO]
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Parse error reading POM.
Reason: Unrecognised association: 'inherited' (position: START_TAG seen
...\n\t\t\t\t\t... @42:17) for project unknown at
/data/cruisecontrol/projects/WebAppPom/pom.xml
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
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:324)
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.InvalidProjectModelException: Parse error
reading POM. Reason: Unrecognised association: 'inherited' (position: START_TAG
seen ...\n\t\t\t\t\t... @42:17) for project unknown
at /data/cruisecontrol/projects/WebAppPom/pom.xml
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1591)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1552)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:503)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
... 11 more
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
Unrecognised association: 'inherited' (position: START_TAG seen
...\n\t\t\t\t\t... @42:17)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3Reader.java:3323)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Reader.java:894)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2542)
at
org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4998)
at
org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1587)
... 17 more
[INFO]
[INFO] Total time: < 1 second
[INFO] Finished at: Tue Feb 24 12:08:51 CET 2009
[INFO] Final Memory: 1M/2M
[INFO]
{code}
pom has the following in plugins:
{code}
...
true
...
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4049) FATAL ERROR
[
http://jira.codehaus.org/browse/MNG-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166850#action_166850
]
Matthew Corby-Eaglen commented on MNG-4049:
---
does not happen in 2.0.9 - switching back for the time being.
> FATAL ERROR
> ---
>
> Key: MNG-4049
> URL: http://jira.codehaus.org/browse/MNG-4049
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.10
>Reporter: Matthew Corby-Eaglen
>
> {code}
> $ mvn -v
> Maven version: 2.0.10
> Java version: 1.4.2_05
> OS name: "sunos" version: "5.10" arch: "x86" Family: "unix"
> $ mvn clean install
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: unknown
> POM Location: /data/cruisecontrol/projects/WebAppPom/pom.xml
> Reason: Parse error reading POM. Reason: Unrecognised association:
> 'inherited' (position: START_TAG seen
> ...\n\t\t\t\t\t... @42:17) for project unknown at
> /data/cruisecontrol/projects/WebAppPom/pom.xml
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parse error reading POM.
> Reason: Unrecognised association: 'inherited' (position: START_TAG seen
> ...\n\t\t\t\t\t... @42:17) for project unknown at
> /data/cruisecontrol/projects/WebAppPom/pom.xml
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
> 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:324)
> 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.InvalidProjectModelException: Parse error
> reading POM. Reason: Unrecognised association: 'inherited' (position:
> START_TAG seen ...\n\t\t\t\t\t... @42:17) for
> project unknown at /data/cruisecontrol/projects/WebAppPom/pom.xml
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1591)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1552)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:503)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> ... 11 more
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
> Unrecognised association: 'inherited' (position: START_TAG seen
> ...\n\t\t\t\t\t... @42:17)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3Reader.java:3323)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Reader.java:894)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2542)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4998)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1587)
> ... 17 more
> [INFO]
>
> [INFO] Total time: < 1 second
> [INFO] Finished at: Tue Feb 24 12:08:51 CET 2009
> [INFO] Final Memory: 1M/2M
> [INFO]
>
> {code}
> pom has the following in plugins:
> {code}
> ...
>
>
> true
>
>
> ...
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one o
[jira] Closed: (MNG-4049) FATAL ERROR
[
http://jira.codehaus.org/browse/MNG-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4049.
-
Assignee: Brett Porter
Resolution: Not A Bug
2.0.10 is simply picking up incorrect syntax in your POM that other versions
haven't. There has never been an flag in dependencies - you can
safely delete it from your pom.xml
> FATAL ERROR
> ---
>
> Key: MNG-4049
> URL: http://jira.codehaus.org/browse/MNG-4049
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.10
>Reporter: Matthew Corby-Eaglen
>Assignee: Brett Porter
>
> {code}
> $ mvn -v
> Maven version: 2.0.10
> Java version: 1.4.2_05
> OS name: "sunos" version: "5.10" arch: "x86" Family: "unix"
> $ mvn clean install
> [INFO] Scanning for projects...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: unknown
> POM Location: /data/cruisecontrol/projects/WebAppPom/pom.xml
> Reason: Parse error reading POM. Reason: Unrecognised association:
> 'inherited' (position: START_TAG seen
> ...\n\t\t\t\t\t... @42:17) for project unknown at
> /data/cruisecontrol/projects/WebAppPom/pom.xml
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Parse error reading POM.
> Reason: Unrecognised association: 'inherited' (position: START_TAG seen
> ...\n\t\t\t\t\t... @42:17) for project unknown at
> /data/cruisecontrol/projects/WebAppPom/pom.xml
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
> 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:324)
> 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.InvalidProjectModelException: Parse error
> reading POM. Reason: Unrecognised association: 'inherited' (position:
> START_TAG seen ...\n\t\t\t\t\t... @42:17) for
> project unknown at /data/cruisecontrol/projects/WebAppPom/pom.xml
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1591)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1552)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:503)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> ... 11 more
> Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException:
> Unrecognised association: 'inherited' (position: START_TAG seen
> ...\n\t\t\t\t\t... @42:17)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parsePlugin(MavenXpp3Reader.java:3323)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseBuild(MavenXpp3Reader.java:894)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Reader.java:2542)
> at
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:4998)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1587)
> ... 17 more
> [INFO]
>
> [INFO] Total time: < 1 second
> [INFO] Finished at: Tue Feb 24 12:08:51 CET 2009
> [INFO] Final Memory: 1M/2M
> [INFO]
>
> {code}
> pom has the following in plugins:
> {code}
> ...
>
>
> true
>
>
[jira] Closed: (MSHADE-42) Reactor builds do not use shaded jar
[ http://jira.codehaus.org/browse/MSHADE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MSHADE-42. -- Assignee: Brett Porter Resolution: Won't Fix the linked issue (MNG-2720) fixes this problem properly in Maven 2.1.0. > Reactor builds do not use shaded jar > > > Key: MSHADE-42 > URL: http://jira.codehaus.org/browse/MSHADE-42 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Dave Meibusch >Assignee: Brett Porter > Attachments: MSHADE-42-alternate.diff, MSHADE-42.patch > > > I have a multi-module project with several of the modules using shade to > create uber jars. > One the modules depends on an uber jar module. When doing a reactor build, > this module is built with a compile classpath containing: >/xxx/yyy/uberjar-module/target/classes > rather than the shaded uber jar created (and installed) earlier in the > reactor build. > When the module is built alone, the dependency in the compile classpath is > correctly the shaded jar in the local repository. > I don't know enough about the internals of reactor builds to determine if > this is a deficiency of the shade plugin or Maven's reactor mechanism. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCOMPILER-30) Compiler fork executable fails when the path has spaces
[
http://jira.codehaus.org/browse/MCOMPILER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MCOMPILER-30:
--
Fix Version/s: (was: 2.0.2)
> Compiler fork executable fails when the path has spaces
> ---
>
> Key: MCOMPILER-30
> URL: http://jira.codehaus.org/browse/MCOMPILER-30
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
>Affects Versions: 2.0.1
>Reporter: Carlos Sanchez
>
> JAVA_1_3_HOME=C:\Program Files\Java\jdk1.3.1_18
>
> maven-compiler-plugin
>
> true
> 1.3
> ${JAVA_1_3_HOME}/bin/javac
>
>
> Fails with
> Failure executing javac, but could not parse the error:
> 'C:\Program' is not recognized as an internal or external command,
> operable program or batch file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCOMPILER-94) compiler sets artifact file to target/classes, even if nothing is compiled
compiler sets artifact file to target/classes, even if nothing is compiled
--
Key: MCOMPILER-94
URL: http://jira.codehaus.org/browse/MCOMPILER-94
Project: Maven 2.x Compiler Plugin
Issue Type: Bug
Affects Versions: 2.0.2
Reporter: Brett Porter
consider the following parent project:
{code:xml}
...
pom
maven-compiler-plugin
compile
...
{code}
This is technically incorrect, you're asking to compile a project with no
sources, but it is needed for inheritence. The compiler should gracefully skip
all functions, however it sets the artifact from the POM to the target/classes
directory, which is incorrect if nothing was compiled.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4045) Matching plugin versions also removes custom configurations
[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166858#action_166858
]
Brett Porter commented on MNG-4045:
---
where is the report configuration in this POM?
> Matching plugin versions also removes custom configurations
> ---
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9, 2.0.10
>Reporter: Paul Benedict
>
> I was locking down my Maven Changes Plugin version with the following config:
> {code}
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.1
>
>
>
> changes-report
>
>
>
>
>
> {code}
> And then I created the site and noticed the report was empty. The report
> markup was there, of course, but it generated like my changes.xml was blank.
> I could run changes:changes-report just fine. However, when I then removed
> the tag and tried site:site again, the report output was present as
> expected.
> Here's an interesting line from the debug output when is specified:
> {quote}[DEBUG] The following artifacts were filtered out for plugin:
> org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
> the core of Maven:{quote}
> My theory is that because my plugin version has an exact match on the
> version, my specified plugin configuration is tossed. That certainly seems
> like a bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4048) Allow to resolve dependencies using version range from reactor
[ http://jira.codehaus.org/browse/MNG-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-4048: -- Fix Version/s: 2.0.x > Allow to resolve dependencies using version range from reactor > -- > > Key: MNG-4048 > URL: http://jira.codehaus.org/browse/MNG-4048 > Project: Maven 2 > Issue Type: Improvement > Components: Dependencies >Affects Versions: 2.0.10, 2.1.0-M1 >Reporter: Benjamin Bentmann > Fix For: 2.0.x > > > Currently, the reactor can only resolve dependencies that are specified using > a simple version like "1.1-SNAPSHOT". If a consumer declares the dependeny > version as "[1.0,)", reactor resolution is no longer possible. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4047) NPE in resolver if artifact defined with a version range
[ http://jira.codehaus.org/browse/MNG-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166859#action_166859 ] Brett Porter commented on MNG-4047: --- would you mind trying this with Maven 2.0.10? > NPE in resolver if artifact defined with a version range > > > Key: MNG-4047 > URL: http://jira.codehaus.org/browse/MNG-4047 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0.9 > Environment: Mac OS X, Maven 2.0.9 >Reporter: Alex Miller > Attachments: out.txt > > > I'm seeing the following NPE when calling the ArtifactResolver with an > Artifact defined by a VersionRange. Here the version for this artifact is > defined as "[1.0.0-SNAPSHOT,1.1.0-SNAPSHOT)" and the 1.0.0-SNAPSHOT artifact > is in my local repository. > java.lang.NullPointerException: version was null for > org.terracotta:terracotta-test-api > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:362) > at > org.apache.maven.artifact.repository.layout.DefaultRepositoryLayout.pathOf(DefaultRepositoryLayout.java:47) > at > org.apache.maven.artifact.repository.DefaultArtifactRepository.pathOf(DefaultArtifactRepository.java:110) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:125) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74) > at > org.terracotta.maven.plugins.tc.DsoArtifactResolverImpl.resolveArtifact(DsoArtifactResolverImpl.java:82) > at > org.terracotta.maven.plugins.tc.ManifestMojo.generateRequiredBundles(ManifestMojo.java:336) > at > org.terracotta.maven.plugins.tc.ManifestMojo.createManifest(ManifestMojo.java:272) > at > org.terracotta.maven.plugins.tc.ManifestMojo.execute(ManifestMojo.java:205) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > The tc-maven-plugin source can be perused here: > http://svn.terracotta.org/svn/forge/projects/tc-maven-plugin/trunk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4045) Matching plugin versions also removes custom configurations
[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166860#action_166860
]
Paul Benedict commented on MNG-4045:
Isn't the part of the configuration? If I mislabeled this issue, I
apologize. So the reportSets get tossed?
> Matching plugin versions also removes custom configurations
> ---
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9, 2.0.10
>Reporter: Paul Benedict
>
> I was locking down my Maven Changes Plugin version with the following config:
> {code}
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.1
>
>
>
> changes-report
>
>
>
>
>
> {code}
> And then I created the site and noticed the report was empty. The report
> markup was there, of course, but it generated like my changes.xml was blank.
> I could run changes:changes-report just fine. However, when I then removed
> the tag and tried site:site again, the report output was present as
> expected.
> Here's an interesting line from the debug output when is specified:
> {quote}[DEBUG] The following artifacts were filtered out for plugin:
> org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
> the core of Maven:{quote}
> My theory is that because my plugin version has an exact match on the
> version, my specified plugin configuration is tossed. That certainly seems
> like a bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3602) Schedule and release Doxia-1.1
[ http://jira.codehaus.org/browse/MNG-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166861#action_166861 ] Brett Porter commented on MNG-3602: --- Dennis - my mistake. Testing so far has shown 1.1 to be working if it is placed in the core, both with old and new versions of the site. > Schedule and release Doxia-1.1 > -- > > Key: MNG-3602 > URL: http://jira.codehaus.org/browse/MNG-3602 > Project: Maven 2 > Issue Type: Task >Affects Versions: 2.0.10 >Reporter: Lukas Theussl > Fix For: 2.1.0 > > > See http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-4045) Matching plugin versions also removes custom configurations
[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-4045:
--
Attachment: MNG-4045.zip
see attached test project where it works just fine
> Matching plugin versions also removes custom configurations
> ---
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9, 2.0.10
>Reporter: Paul Benedict
> Attachments: MNG-4045.zip
>
>
> I was locking down my Maven Changes Plugin version with the following config:
> {code}
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.1
>
>
>
> changes-report
>
>
>
>
>
> {code}
> And then I created the site and noticed the report was empty. The report
> markup was there, of course, but it generated like my changes.xml was blank.
> I could run changes:changes-report just fine. However, when I then removed
> the tag and tried site:site again, the report output was present as
> expected.
> Here's an interesting line from the debug output when is specified:
> {quote}[DEBUG] The following artifacts were filtered out for plugin:
> org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
> the core of Maven:{quote}
> My theory is that because my plugin version has an exact match on the
> version, my specified plugin configuration is tossed. That certainly seems
> like a bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4045) Matching plugin versions also removes custom configurations
[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4045.
-
Assignee: Brett Porter
Resolution: Cannot Reproduce
this wasn't a direct cut and paste (there is a missing element), so
there's a chance it was mistyped in your original POM.
If it is correct, I would put this down to a different version of the changes
plugin behaving differently based on the existence of src/changes/changes.xml.
The report is not generated if that file is missing in 2.1. Maybe it is in a
different version that you get with the version removed. Either way, this isn't
a Maven issue AFAICT.
> Matching plugin versions also removes custom configurations
> ---
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9, 2.0.10
>Reporter: Paul Benedict
>Assignee: Brett Porter
> Attachments: MNG-4045.zip
>
>
> I was locking down my Maven Changes Plugin version with the following config:
> {code}
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.1
>
>
>
> changes-report
>
>
>
>
>
> {code}
> And then I created the site and noticed the report was empty. The report
> markup was there, of course, but it generated like my changes.xml was blank.
> I could run changes:changes-report just fine. However, when I then removed
> the tag and tried site:site again, the report output was present as
> expected.
> Here's an interesting line from the debug output when is specified:
> {quote}[DEBUG] The following artifacts were filtered out for plugin:
> org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
> the core of Maven:{quote}
> My theory is that because my plugin version has an exact match on the
> version, my specified plugin configuration is tossed. That certainly seems
> like a bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3057) properties not expanded in generated POMs when building A/B/C nested projects
[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166879#action_166879
]
John Casey commented on MNG-3057:
-
Thanks, Benjamin, that saved me some time. :)
> properties not expanded in generated POMs when building A/B/C nested projects
> -
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.7
>Reporter: George Armhold
>Assignee: John Casey
> Fix For: 2.1.0
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-install-parent.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
>$ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (MNG-3379) Parallel resolution of artifacts
[ http://jira.codehaus.org/browse/MNG-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MNG-3379: - We need to follow up on the ConcurrentModificationException that's happening intermittently under stress. The discussion is here: http://www.nabble.com/Synchronization-issue-with-parallel-downloads-td22136382.html > Parallel resolution of artifacts > > > Key: MNG-3379 > URL: http://jira.codehaus.org/browse/MNG-3379 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Don Brown >Assignee: Brett Porter > Fix For: 2.1.0 > > Attachments: parallel-resolution-2.diff, parallel-resolution-3.diff, > parallel-resolution.diff > > > Artifacts should be resolved in parallel, grouped by group id's to get around > the lack of synchronization in the local repository. The patch does the > following: > * Use a ThreadPoolExecutor to parallelize artifact resolution, but takes care > not to resolve multiple artifacts from the same group id simultaneously. > (requires Java 5) > * Makes the http wagon the default instead of the poor performing http-client > Disadvantages: > * Requires Java 5, but the backport jars could be substituted pretty easily > * Breaks some plugins due to commons-logging being in the Maven uber jar > (required by commons-httpclient), notably the apt plugin (maybe more should > use the isolatedRealm setting?) > * Screws up the progress monitor as multiple threads are updating it > Advantages: > * Much faster when combined with the http wagon (WAGON-98). I was seeing 40% > improvement on some test builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3057) properties not expanded in generated POMs when building A/B/C nested projects
[
http://jira.codehaus.org/browse/MNG-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-3057.
---
Resolution: Fixed
Added new interpolation strategy that uses raw contents of the POM XML file,
and interpolates it from that string. This is a two-stage process, where the
first stage interpolator isolates the version elements and hands the value off
to the second-stage interpolator to actually resolve any expressions. Then, the
result is re-inserted into the XML.
Also, adjusted the handling for artifacts with type == pom during
install/deploy, such that the accompanying file is forcibly set to the
artifact's file, to work around MCOMPILER-94. Attachments should be handled
separately, since they have their own Artifact instance. I've modified the
integration test for MNG-3057 to inject the configuration from MCOMPILER-94
just to be sure it works.
> properties not expanded in generated POMs when building A/B/C nested projects
> -
>
> Key: MNG-3057
> URL: http://jira.codehaus.org/browse/MNG-3057
> Project: Maven 2
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.0.7
>Reporter: George Armhold
>Assignee: John Casey
> Fix For: 2.1.0
>
> Attachments: example.tar.gz, generated-poms.tar.gz,
> InstallMojo.java.patch, InstallMojo.java.patch,
> InstallMojo.quoteReplacement.patch, maven-install-parent.patch
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Using Maven version: 2.0.8-SNAPSHOT, svn r547427.
> I checked out and built 2.0.8 because I was interested in Jason van Zyl's
> patch for MNG-2619- "building from the middle pom of a
> (parent,child,grandchild) heirarchy fails". The fix works for the most part,
> but there still seems to be a problem with the poms that get generated during
> the install goal. The poms that get installed into .m2/repository do not
> have properties interpolated. If I run maven like:
>$ mvn install -Dglobal-version=1.0.0
> I get poms with the string "${global-version}" embedded in the resulting poms
> rather than what I specify on the command line (or in settings.xml). The
> build works properly aside from this, and if I do "mvn help:effective-pom"
> the properties are correctly interpolated.
> I've attached a tarfile with an example A/B/C build structure that exhibits
> this behavior, as well as the generated poms.
> Many thanks for your attention.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MDEPLOY-94) Variables in the version element in pom.xml need to be expanded before deployment
[
http://jira.codehaus.org/browse/MDEPLOY-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MDEPLOY-94.
-
Assignee: John Casey
Resolution: Duplicate
This is a problem in the core of Maven, not in the deploy plugin. It's been
resolved in MNG-3057, and will be available for use in Maven 2.1.0.
> Variables in the version element in pom.xml need to be expanded before
> deployment
> -
>
> Key: MDEPLOY-94
> URL: http://jira.codehaus.org/browse/MDEPLOY-94
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
>Reporter: Brian Jackson
>Assignee: John Casey
>
> We use an external tool to manage our releases (instead of
> maven-release-plugin). The version in our pom.xml is declared as:
> ${build.number}
> The actual version number is passed in during a release deployment on the
> command line "mvn deploy -Dbuild.number=1.2.3"
> The pom.xml is deployed literally without the variable replaced with the
> actual value. This causes problems, in particular multi-module releases are
> impossible since the parent pom can't be resolved properly as well as this
> issue with Nexus https://issues.sonatype.org/browse/NEXUS-1552
> I started digging into the code and see deployment is deferred to the
> DefaultArtifactDeployer
> http://maven.apache.org/ref/current/xref/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.html
> Can I somehow install a custom ArtifactTransformation that expands these
> variables before deployment? How would I install it in my builds? Would I
> build it as a Plexus component and add it as a plugin dependency of
> maven-deploy-plugin? If someone could give me a little guidance I'd be happy
> to implement it, test it and submit a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4043) Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL
[ http://jira.codehaus.org/browse/MNG-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-4043. --- Assignee: John Casey (was: Brett Porter) Resolution: Fixed Wagon 1.0-beta-5 is in use now, which has this issue resolved. > Resolve or rollback WebDAV wagon deployment issue where hostname is > improperly extracted from URL > - > > Key: MNG-4043 > URL: http://jira.codehaus.org/browse/MNG-4043 > Project: Maven 2 > Issue Type: Bug > Components: Deployment >Affects Versions: 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > Fix For: 2.1.0 > > > See WAGON-244. > This is one of the most serious problems we've had reported for Maven > 2.1.0-M1, and should be driven to some sort of resolution before 2.1.0-final > is released. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTRUN-51) Problems with multiple antrun declarations in multiproject
[
http://jira.codehaus.org/browse/MANTRUN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166900#action_166900
]
Florian Kolbe commented on MANTRUN-51:
--
Moving the dependency snippet to the build tag of the module did not help for
me (mvn 2.0.9) but moving it to this snippet of the parent pom:
maven-antrun-plugin
1.1
ant
ant-optional
1.5.3-1
> Problems with multiple antrun declarations in multiproject
> --
>
> Key: MANTRUN-51
> URL: http://jira.codehaus.org/browse/MANTRUN-51
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.0, 1.1
> Environment: maven 2.0.4, antrun 1.0 & 1.1, jdk 1.5.0_06, windows xp
>Reporter: Fredrik Vraalsen
>
> I'm using antrun in my project to create an IzPack installation. The plugin
> configuration is below.
> When maven is run from the top-level project, the ant taskdef fails because
> it cannot find the IzPackTask class. However, when I run maven from the
> subproject itself, it works fine. Not sure if this is related to
> http://jira.codehaus.org/browse/MANTRUN-49. The error message from maven is
> at the bottom.
> {noformat}
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> package
>
>
>classname="com.izforge.izpack.ant.IzPackTask"/>
>input="${project.build.directory}/classes/izPack.xml"
> output="${project.build.directory}/CorasTool-${coras.version}-installer.jar"
> basedir="${project.build.directory}"/>
>
>
>
> run
>
>
>
>
>
> izpack
> standalone-compiler
> 3.8.0
>
>
>
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error executing ant tasks
> Embedded error: taskdef class com.izforge.izpack.ant.IzPackTask cannot be
> found
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> tasks
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> 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:256)
> 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.plugin.MojoExecutionException: Error executing
> ant tasks
> at
> org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:77)
> at
> org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:72)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 16 more
> Caused by: taskdef class com.i
[jira] Issue Comment Edited: (MANTRUN-51) Problems with multiple antrun declarations in multiproject
[
http://jira.codehaus.org/browse/MANTRUN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166900#action_166900
]
Florian Kolbe edited comment on MANTRUN-51 at 2/24/09 11:58 AM:
Moving the dependency snippet to the build tag of the module did not help for
me (mvn 2.0.9) but moving it to this snippet of the parent pom:
{code:xml}
maven-antrun-plugin
1.1
ant
ant-optional
1.5.3-1
{code}
was (Author: in-fke):
Moving the dependency snippet to the build tag of the module did not help
for me (mvn 2.0.9) but moving it to this snippet of the parent pom:
maven-antrun-plugin
1.1
ant
ant-optional
1.5.3-1
> Problems with multiple antrun declarations in multiproject
> --
>
> Key: MANTRUN-51
> URL: http://jira.codehaus.org/browse/MANTRUN-51
> Project: Maven 2.x Antrun Plugin
> Issue Type: Bug
>Affects Versions: 1.0, 1.1
> Environment: maven 2.0.4, antrun 1.0 & 1.1, jdk 1.5.0_06, windows xp
>Reporter: Fredrik Vraalsen
>
> I'm using antrun in my project to create an IzPack installation. The plugin
> configuration is below.
> When maven is run from the top-level project, the ant taskdef fails because
> it cannot find the IzPackTask class. However, when I run maven from the
> subproject itself, it works fine. Not sure if this is related to
> http://jira.codehaus.org/browse/MANTRUN-49. The error message from maven is
> at the bottom.
> {noformat}
>
> org.apache.maven.plugins
> maven-antrun-plugin
>
>
> package
>
>
>classname="com.izforge.izpack.ant.IzPackTask"/>
>input="${project.build.directory}/classes/izPack.xml"
> output="${project.build.directory}/CorasTool-${coras.version}-installer.jar"
> basedir="${project.build.directory}"/>
>
>
>
> run
>
>
>
>
>
> izpack
> standalone-compiler
> 3.8.0
>
>
>
> [INFO] [antrun:run {execution: default}]
> [INFO] Executing tasks
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error executing ant tasks
> Embedded error: taskdef class com.izforge.izpack.ant.IzPackTask cannot be
> found
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
> tasks
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> 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:256)
> 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.plugin.MojoExecutionException: Error executing
> ant tasks
> at
[jira] Commented: (MNG-4045) Matching plugin versions also removes custom configurations
[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166901#action_166901
]
Paul Benedict commented on MNG-4045:
Brett, I think you misunderstood the issue. The changes.xml file is always
present. It's only when I put in the of the plugin that it does not
generate in the site goal.
> Matching plugin versions also removes custom configurations
> ---
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9, 2.0.10
>Reporter: Paul Benedict
>Assignee: Brett Porter
> Attachments: MNG-4045.zip
>
>
> I was locking down my Maven Changes Plugin version with the following config:
> {code}
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.1
>
>
>
> changes-report
>
>
>
>
>
> {code}
> And then I created the site and noticed the report was empty. The report
> markup was there, of course, but it generated like my changes.xml was blank.
> I could run changes:changes-report just fine. However, when I then removed
> the tag and tried site:site again, the report output was present as
> expected.
> Here's an interesting line from the debug output when is specified:
> {quote}[DEBUG] The following artifacts were filtered out for plugin:
> org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
> the core of Maven:{quote}
> My theory is that because my plugin version has an exact match on the
> version, my specified plugin configuration is tossed. That certainly seems
> like a bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3139) The skin does not exist: Unable to determine the release version
[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3139. --- Resolution: Fixed Patch applied, thanks Benjamin. > The skin does not exist: Unable to determine the release version > > > Key: MNG-3139 > URL: http://jira.codehaus.org/browse/MNG-3139 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.7 >Reporter: eyal david >Assignee: John Casey > Fix For: 2.0.11, 2.1.0 > > Attachments: cached-metadata.patch > > > hi I have problem generating site when im using the command mvn site > it performs all stagegs and when it came to site generation the message is > shown : > The skin does not exist: Unable to determine the release version > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.skins > -DartifactId=maven > -default-skin \ > -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file > org.apache.maven.skins:maven-default-skin:jar:RELEASE > do u have an idea what is the problem ? > p.s the jar is registered in my local repository and in the remote repository > thank u -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MNG-2690) DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly
[
http://jira.codehaus.org/browse/MNG-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on MNG-2690 started by John Casey.
> DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError
> correctly
> --
>
> Key: MNG-2690
> URL: http://jira.codehaus.org/browse/MNG-2690
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.4
>Reporter: Aaron Digulla
>Assignee: John Casey
> Fix For: 2.1.0
>
>
> If maven tries to download a file which doesn't exist and it believes there
> is no other place where it can get the file, you can have the situation that
> Maven tries to invoke a Plugin without a complete classpath. In the log,
> you'll see something like this:
> Downloading:
> http://repository.codehaus.org/org/codehaus/mojo/dependency-maven-plugin/1.0/dependency-maven-plugin-1.0.pom
> Downloading:
> http://repo1.maven.org/maven2/org/codehaus/mojo/dependency-maven-plugin/1.0/dependency-maven-plugin-1.0.jar
> 15K downloaded
> As you can see, Maven tries to download the POM from a different site than
> the JAR. Now, the classpath of the JAR is incomplete because the POM is
> missing. Things get really nasty when Maven tries to access the plugin.
> You'll get:
> java.lang.NoClassDefFoundError:
> Lorg/codehaus/plexus/archiver/manager/ArchiverManager;
> which tells you exactly nothing since you have no idea who wants that class.
> The cause of the problem is that PlexusContainer doesn't catch errors (well,
> Java says you shouldn't but the user would really like to see what's going
> on).
> My fix was to duplicate the catch in DefaultPluginManager.getConfiguredMojo()
> (around line 530):
> catch ( NoClassDefFoundError e )
> {
> throw new PluginManagerException( "Unable to find the mojo '" +
> mojoDescriptor.getRoleHint() +
> "' in the plugin '" + pluginDescriptor.getPluginLookupKey() +
> "' because of NoClassDefFoundError:", e );
> }
> This way, I get at least an idea which plugin is causing the problem.
> But I guess the container should be fixed to catch these errors.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-228) site missing module in maven-archetype-j2ee-simple archetype plugin
site missing module in maven-archetype-j2ee-simple archetype plugin --- Key: ARCHETYPE-228 URL: http://jira.codehaus.org/browse/ARCHETYPE-228 Project: Maven Archetype Issue Type: Bug Components: Generator Reporter: Esteban DUGUEPEROUX Priority: Minor Hi, When I create a j2ee-simple project from archetype n°10 the main pom.xml specify a site module but without site directory. Then at each j2ee project creation I need to delete the relevant line in pom.xml. Can we have a site directory generated or the relevant line in pom.xml deleted. Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-228) site missing module in maven-archetype-j2ee-simple archetype plugin
[ http://jira.codehaus.org/browse/ARCHETYPE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166907#action_166907 ] Esteban DUGUEPEROUX commented on ARCHETYPE-228: --- And the following XML header shouldn't be compulsory ? http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> > site missing module in maven-archetype-j2ee-simple archetype plugin > --- > > Key: ARCHETYPE-228 > URL: http://jira.codehaus.org/browse/ARCHETYPE-228 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Esteban DUGUEPEROUX >Priority: Minor > > Hi, > When I create a j2ee-simple project from archetype n°10 the main pom.xml > specify a site module but without site directory. > Then at each j2ee project creation I need to delete the relevant line in > pom.xml. > Can we have a site directory generated or the relevant line in pom.xml > deleted. > Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPLUGIN-146) Implement pluginXml parameter for maven-plugin-plugin
Implement pluginXml parameter for maven-plugin-plugin - Key: MPLUGIN-146 URL: http://jira.codehaus.org/browse/MPLUGIN-146 Project: Maven 2.x Plugin Tools Issue Type: New Feature Components: Plugin Plugin Affects Versions: 2.5 Reporter: John Casey Priority: Critical Fix For: 2.5.1 This is admittedly an edge case, but we have had it come up before... QDox doesn't store annotation information in binaries, which means that mojos inheriting from another mojo in a different plugin have no way to express the mojo parameters inherited from the parent class. The plugin.xml files are not merged in any way. This leaves hand-authoring plugin.xml files as the only option for such cases. Since we've just changed the behavior of the plugin-plugin in MPLUGIN-106 to throw an exception if no mojos are detected (as opposed to simply printing a warning), this last-ditch option is no longer available for users. We should provide a new parameter in the plugin-plugin called something like 'pluginXml' which simply circumvents all mojo detection logic and instead uses the supplied file as the plugin descriptor. This is sort of a nuclear option, but it allows advanced plugin developers the flexibility to extend other plugins, or basically do whatever they need to do. Testing is up to the developer when they take this option, of course, to ensure that the defined mojos can actually be loaded and used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-146) Implement pluginXml parameter for maven-plugin-plugin
[ http://jira.codehaus.org/browse/MPLUGIN-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MPLUGIN-146: --- Fix Version/s: 2.5.1 > Implement pluginXml parameter for maven-plugin-plugin > - > > Key: MPLUGIN-146 > URL: http://jira.codehaus.org/browse/MPLUGIN-146 > Project: Maven 2.x Plugin Tools > Issue Type: New Feature > Components: Plugin Plugin >Affects Versions: 2.5 >Reporter: John Casey >Priority: Critical > Fix For: 2.5.1 > > > This is admittedly an edge case, but we have had it come up before... > QDox doesn't store annotation information in binaries, which means that mojos > inheriting from another mojo in a different plugin have no way to express the > mojo parameters inherited from the parent class. The plugin.xml files are not > merged in any way. This leaves hand-authoring plugin.xml files as the only > option for such cases. > Since we've just changed the behavior of the plugin-plugin in MPLUGIN-106 to > throw an exception if no mojos are detected (as opposed to simply printing a > warning), this last-ditch option is no longer available for users. > We should provide a new parameter in the plugin-plugin called something like > 'pluginXml' which simply circumvents all mojo detection logic and instead > uses the supplied file as the plugin descriptor. This is sort of a nuclear > option, but it allows advanced plugin developers the flexibility to extend > other plugins, or basically do whatever they need to do. Testing is up to the > developer when they take this option, of course, to ensure that the defined > mojos can actually be loaded and used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3139) The skin does not exist: Unable to determine the release version
[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166912#action_166912 ] Benjamin Bentmann commented on MNG-3139: Merged to 2.0.x in [r747533|http://svn.eu.apache.org/viewvc?view=rev&revision=747533]. > The skin does not exist: Unable to determine the release version > > > Key: MNG-3139 > URL: http://jira.codehaus.org/browse/MNG-3139 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.7 >Reporter: eyal david >Assignee: John Casey > Fix For: 2.0.11, 2.1.0 > > Attachments: cached-metadata.patch > > > hi I have problem generating site when im using the command mvn site > it performs all stagegs and when it came to site generation the message is > shown : > The skin does not exist: Unable to determine the release version > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.skins > -DartifactId=maven > -default-skin \ > -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file > org.apache.maven.skins:maven-default-skin:jar:RELEASE > do u have an idea what is the problem ? > p.s the jar is registered in my local repository and in the remote repository > thank u -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3139) The skin does not exist: Unable to determine the release version
[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3139: --- Fix Version/s: 3.0-alpha-3 Merged to 3.x in [r747536|http://svn.eu.apache.org/viewvc?view=rev&revision=747536]. > The skin does not exist: Unable to determine the release version > > > Key: MNG-3139 > URL: http://jira.codehaus.org/browse/MNG-3139 > Project: Maven 2 > Issue Type: Bug > Components: Sites & Reporting >Affects Versions: 2.0.7 >Reporter: eyal david >Assignee: John Casey > Fix For: 2.0.11, 2.1.0, 3.0-alpha-3 > > Attachments: cached-metadata.patch > > > hi I have problem generating site when im using the command mvn site > it performs all stagegs and when it came to site generation the message is > shown : > The skin does not exist: Unable to determine the release version > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.maven.skins > -DartifactId=maven > -default-skin \ > -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file > org.apache.maven.skins:maven-default-skin:jar:RELEASE > do u have an idea what is the problem ? > p.s the jar is registered in my local repository and in the remote repository > thank u -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-39) Add a includePom option to the sources:jar goal
[
http://jira.codehaus.org/browse/MSOURCES-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSOURCES-39:
Description:
Adds an includePom option that will result in inclusion of the project's pom
file into the generates sources jar file.
{noformat}
Index:
src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
===
--- src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
(revision 691652)
+++ src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.j
+++ ava
(working copy)
@@ -69,6 +69,14 @@
* @since 2.0.4
*/
protected boolean excludeResources;
+
+/**
+ * Specifies whether or not to include the pom file in the sources-jar.
+ *
+ * @parameter expression="${includePom}" default-value="false"
+ * @since 2.0.5
+ */
+protected boolean includePom;
/**
* Used for attaching the source jar to the project.
@@ -186,6 +194,15 @@
protected void archiveProjectContent( MavenProject project, Archiver
archiver )
throws MojoExecutionException
{
+
+ if (includePom) {
+ try {
+ archiver.addFile(project.getFile(),
project.getFile().getName());
+ } catch (ArchiverException e) {
+ throw new MojoExecutionException("Error
adding pom file to target jar file.", e);
+ }
+ }
+
for ( Iterator i = getSources( project ).iterator(); i.hasNext(); )
{
String s = (String) i.next();
{noformat}
was:
Adds an includePom option that will result in inclusion of the project's pom
file into the generates sources jar file.
Index:
src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
===
--- src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
(revision 691652)
+++ src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.j
+++ ava
(working copy)
@@ -69,6 +69,14 @@
* @since 2.0.4
*/
protected boolean excludeResources;
+
+/**
+ * Specifies whether or not to include the pom file in the sources-jar.
+ *
+ * @parameter expression="${includePom}" default-value="false"
+ * @since 2.0.5
+ */
+protected boolean includePom;
/**
* Used for attaching the source jar to the project.
@@ -186,6 +194,15 @@
protected void archiveProjectContent( MavenProject project, Archiver
archiver )
throws MojoExecutionException
{
+
+ if (includePom) {
+ try {
+ archiver.addFile(project.getFile(),
project.getFile().getName());
+ } catch (ArchiverException e) {
+ throw new MojoExecutionException("Error
adding pom file to target jar file.", e);
+ }
+ }
+
for ( Iterator i = getSources( project ).iterator(); i.hasNext(); )
{
String s = (String) i.next();
> Add a includePom option to the sources:jar goal
> ---
>
> Key: MSOURCES-39
> URL: http://jira.codehaus.org/browse/MSOURCES-39
> Project: Maven 2.x Source Plugin
> Issue Type: Improvement
>Reporter: Moritz Havelock
>Priority: Minor
>
> Adds an includePom option that will result in inclusion of the project's pom
> file into the generates sources jar file.
> {noformat}
> Index:
> src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
> ===
> --- src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
> (revision 691652)
> +++ src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.j
> +++ ava
> (working copy)
> @@ -69,6 +69,14 @@
> * @since 2.0.4
> */
> protected boolean excludeResources;
> +
> +/**
> + * Specifies whether or not to include the pom file in the sources-jar.
> + *
> + * @parameter expression="${includePom}" default-value="false"
> + * @since 2.0.5
> + */
> +protected boolean includePom;
>
> /**
> * Used for attaching the source jar to the project.
> @@ -186,6 +194,15 @@
> protected void archiveProjectContent( MavenProject project, Archiver
> archiver )
> throws MojoExecutionException
> {
> +
> + if (includePom) {
> + try {
> + archiver.addFile(project.getFile(),
> project.getFile().getName());
> + } catch (ArchiverException e) {
> + throw new MojoExecutionException("Error
> adding pom file
[jira] Created: (MAVENUPLOAD-2367) QDWizard sync
QDWizard sync - Key: MAVENUPLOAD-2367 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2367 Project: Maven Upload Requests Issue Type: Wish Reporter: bflorat Attachments: net.sf.qdwizard.sh Please add this repository for synchronization http://qdwizard.sourceforge.net/repository/ Thanks, Bertrand Florat, QDWizard admin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3870) Cannot use Wagon ftp on Mac OSX
[
http://jira.codehaus.org/browse/MNG-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166923#action_166923
]
Patrick Moore commented on MNG-3870:
Brett,
Retesting. We use "deploy" to push via ssh to the production server. Works fine
on windows. But now that I am on the Mac I get
http://jira.codehaus.org/browse/MDEPLOY-62
(Obviously this is *not* an ftp issue.)
Doing more ftp testing -- but ftp looks o.k. now.
> Cannot use Wagon ftp on Mac OSX
> ---
>
> Key: MNG-3870
> URL: http://jira.codehaus.org/browse/MNG-3870
> Project: Maven 2
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 2.1.0-M1
> Environment: mvn -version
> Using Java version: 1.6
> Maven version: 2.1.0-M1
> Java version: 1.6.0_07
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.5" arch: "x86_64" family: "mac"
>Reporter: Patrick Moore
>Assignee: Brett Porter
>
> Seems to be MacOSX-specific. I have used Wagon ftp to deploy files to a ftp
> server on windows. Using the same configuration that successfully "mvn
> deploy"'s on windows fails on Mac OSX.
> Please note that Wagon-ftp-1.0-beta-4 jars are downloaded and in the MacOSX
> repository. So this seems different than: MNG-2227 (but maybe not?)
> mvn -Dmaven.test.skip=true -e deploy
> Using Java version: 1.6
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Reactor build order:
> [INFO] Amplafi Hivemind
> [INFO] Amplafi Test
> [INFO] Tapestry Javaforge Acegi
> [INFO] Amplafi Json
> [INFO] Amplafi Sworddance
> [INFO] Amplafi Flow - Core
> [INFO] Flow - Web
> [INFO] Amplafi - James Mailet
> [INFO] Amplafi Wireservice - Foundation
> [INFO] Amplafi Wireservice - IO Management
> [INFO] Amplafi Wireservice - Core
> [INFO] Amplafi Wireservice - Web
> [INFO] Amplafi Project
> [INFO]
>
> [INFO] Building Amplafi Hivemind
> [INFO]task-segment: [deploy]
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Not compiling test sources
> [INFO] [surefire:test]
> [INFO] Tests are skipped.
> [INFO] [jar:jar]
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Preparing source:test-jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [WARNING] Removing: test-jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] No goals needed for project - skipping
> [INFO] [source:test-jar {execution: attach-sources}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] [javadoc:jar {execution: attach-javadocs}]
> [INFO] Building jar:
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [install:install]
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-test-sources.jar
> [INFO] Installing
> /Users/patmoore/projects/amplafi/amplafi-hivemind/target/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> to
> /Users/patmoore/.m2/repository/com/amplafi/amplafi-hivemind/0.8-SNAPSHOT/amplafi-hivemind-0.8-SNAPSHOT-javadoc.jar
> [INFO] [deploy:deploy]
> altDeploymentRepository =
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Using alternate deployment repository
> amplafi.public::default::ftp://amplafi.com/httpdocs/repository
> [INFO] Retrieving previous build number from amplafi.public
> [INFO]
>
[jira] Updated: (MSOURCES-39) Add an includePom option to the sources:jar goal
[
http://jira.codehaus.org/browse/MSOURCES-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MSOURCES-39:
Assignee: Dennis Lundberg
Affects Version/s: 2.0.4
Fix Version/s: 2.1
Summary: Add an includePom option to the sources:jar goal (was:
Add a includePom option to the sources:jar goal)
> Add an includePom option to the sources:jar goal
>
>
> Key: MSOURCES-39
> URL: http://jira.codehaus.org/browse/MSOURCES-39
> Project: Maven 2.x Source Plugin
> Issue Type: Improvement
>Affects Versions: 2.0.4
>Reporter: Moritz Havelock
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.1
>
>
> Adds an includePom option that will result in inclusion of the project's pom
> file into the generates sources jar file.
> {noformat}
> Index:
> src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
> ===
> --- src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
> (revision 691652)
> +++ src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.j
> +++ ava
> (working copy)
> @@ -69,6 +69,14 @@
> * @since 2.0.4
> */
> protected boolean excludeResources;
> +
> +/**
> + * Specifies whether or not to include the pom file in the sources-jar.
> + *
> + * @parameter expression="${includePom}" default-value="false"
> + * @since 2.0.5
> + */
> +protected boolean includePom;
>
> /**
> * Used for attaching the source jar to the project.
> @@ -186,6 +194,15 @@
> protected void archiveProjectContent( MavenProject project, Archiver
> archiver )
> throws MojoExecutionException
> {
> +
> + if (includePom) {
> + try {
> + archiver.addFile(project.getFile(),
> project.getFile().getName());
> + } catch (ArchiverException e) {
> + throw new MojoExecutionException("Error
> adding pom file to target jar file.", e);
> + }
> + }
> +
> for ( Iterator i = getSources( project ).iterator(); i.hasNext(); )
> {
> String s = (String) i.next();
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSOURCES-39) Add an includePom option to the sources:jar goal
[
http://jira.codehaus.org/browse/MSOURCES-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSOURCES-39.
---
Resolution: Fixed
Fixed in r747562.
I have applied your patch with modifications and added a test case. Thanks!
> Add an includePom option to the sources:jar goal
>
>
> Key: MSOURCES-39
> URL: http://jira.codehaus.org/browse/MSOURCES-39
> Project: Maven 2.x Source Plugin
> Issue Type: Improvement
>Affects Versions: 2.0.4
>Reporter: Moritz Havelock
>Assignee: Dennis Lundberg
>Priority: Minor
> Fix For: 2.1
>
>
> Adds an includePom option that will result in inclusion of the project's pom
> file into the generates sources jar file.
> {noformat}
> Index:
> src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
> ===
> --- src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.java
> (revision 691652)
> +++ src/main/java/org/apache/maven/plugin/source/AbstractSourceJarMojo.j
> +++ ava
> (working copy)
> @@ -69,6 +69,14 @@
> * @since 2.0.4
> */
> protected boolean excludeResources;
> +
> +/**
> + * Specifies whether or not to include the pom file in the sources-jar.
> + *
> + * @parameter expression="${includePom}" default-value="false"
> + * @since 2.0.5
> + */
> +protected boolean includePom;
>
> /**
> * Used for attaching the source jar to the project.
> @@ -186,6 +194,15 @@
> protected void archiveProjectContent( MavenProject project, Archiver
> archiver )
> throws MojoExecutionException
> {
> +
> + if (includePom) {
> + try {
> + archiver.addFile(project.getFile(),
> project.getFile().getName());
> + } catch (ArchiverException e) {
> + throw new MojoExecutionException("Error
> adding pom file to target jar file.", e);
> + }
> + }
> +
> for ( Iterator i = getSources( project ).iterator(); i.hasNext(); )
> {
> String s = (String) i.next();
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-34) Allow the artifact type to be changed
[ http://jira.codehaus.org/browse/MSOURCES-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSOURCES-34: Assignee: Dennis Lundberg Fix Version/s: 2.1 Summary: Allow the artifact type to be changed (was: Allow change artifact type) > Allow the artifact type to be changed > - > > Key: MSOURCES-34 > URL: http://jira.codehaus.org/browse/MSOURCES-34 > Project: Maven 2.x Source Plugin > Issue Type: Improvement >Affects Versions: 2.0.4 > Environment: Any >Reporter: Marvin Froeder >Assignee: Dennis Lundberg > Fix For: 2.1 > > Attachments: type.patch > > > At current time the type generated by this plugin is hard coded: > AbstractSourceJarMojo line 177: > projectHelper.attachArtifact( project, "java-source", > getClassifier(), outputFile ); > If this "java-source" is moved to some getType it will allow me to extends > this abstract class instead of duplicating this source. > Then I use org.ops4j.maven-inherit-plugin. > I can provide patch if required. > VELO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSOURCES-34) Allow the artifact type to be changed
[ http://jira.codehaus.org/browse/MSOURCES-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSOURCES-34. --- Resolution: Fixed Fixed in r747570. The patch didn't apply anymore, but the changes were easy to make by hand. > Allow the artifact type to be changed > - > > Key: MSOURCES-34 > URL: http://jira.codehaus.org/browse/MSOURCES-34 > Project: Maven 2.x Source Plugin > Issue Type: Improvement >Affects Versions: 2.0.4 > Environment: Any >Reporter: Marvin Froeder >Assignee: Dennis Lundberg > Fix For: 2.1 > > Attachments: type.patch > > > At current time the type generated by this plugin is hard coded: > AbstractSourceJarMojo line 177: > projectHelper.attachArtifact( project, "java-source", > getClassifier(), outputFile ); > If this "java-source" is moved to some getType it will allow me to extends > this abstract class instead of duplicating this source. > Then I use org.ops4j.maven-inherit-plugin. > I can provide patch if required. > VELO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-20) Allow Source plugin to specify alternate DistributionManagement
[ http://jira.codehaus.org/browse/MSOURCES-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSOURCES-20: Fix Version/s: (was: 2.1) > Allow Source plugin to specify alternate DistributionManagement > --- > > Key: MSOURCES-20 > URL: http://jira.codehaus.org/browse/MSOURCES-20 > Project: Maven 2.x Source Plugin > Issue Type: Improvement >Affects Versions: 2.0.3 >Reporter: James William Dumay > Attachments: maven-source-plugin.patch > > > The following patch allows the source plugin to specify alternate repository > locations for deployment of its attached artifacts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2720) Multiproject dependencies not accurate for project.compileClasspathElements when run from root project
[ http://jira.codehaus.org/browse/MNG-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-2720: --- Fix Version/s: 3.0-alpha-3 Merged to 3.x in [r747588|http://svn.eu.apache.org/viewvc?view=rev&revision=747588]. > Multiproject dependencies not accurate for project.compileClasspathElements > when run from root project > -- > > Key: MNG-2720 > URL: http://jira.codehaus.org/browse/MNG-2720 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0.4 >Reporter: Jeff Genender >Assignee: John Casey > Fix For: 2.1.0, 3.0-alpha-3 > > > In a plugin I wrote (jspc), needs the dependency jars. It asks for this with > the request for the project.compileClasspathElements. In a multiproject > environment, when each project is built individually, it seems correct. > Example (when run with -X ina subproject dir) showing classpath: > /Users/mbp/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar > /Users/mbp/.m2/repository/taglibs/standard/1.1.2/standard-1.1.2.jar > /Users/mbp/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar > /Users/mbp/.m2/repository/tldtestapp/testexttld/1/testexttld-1.jar > <-NOTICE HERE - THIS IS AN ARTIFACT FROM ANOTHER SUBPROJECT > /Users/mbp/.m2/repository/javax/servlet/jstl/1.1.2/jstl-1.1.2.jar] > When it is run from the Top level/Root project...here is the output: > Users/mbp/.m2/repository/javax/servlet/jsp-api/2.0/jsp-api-2.0.jar > /Users/mbp/.m2/repository/javax/servlet/servlet-api/2.4/servlet-api-2.4.jar > /Users/mbp/.m2/repository/taglibs/standard/1.1.2/standard-1.1.2.jar > /Users/mbp/Desktop/jsp-example/TestTldProject/target/classes >INSTEAD > /Users/mbp/.m2/repository/javax/servlet/jstl/1.1.2/jstl-1.1.2.jar] > The second project has a dependency on the testexttld-1.jar because it > contains tag libs which must be wrapped in a jar. When run from a top level, > it uses the other project's classes directory instead of the JAR artifact. > WIth JSPC and taglibs, this makes it so it cannot work. If I have a > dependency on a jar, that jar should be the dependency as expected and not a > classes directory. For full explanation and example see here: > http://jira.codehaus.org/browse/MJSPC-4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSOURCES-37) CLONE -maven-source-plugin causes generate-sources phase to execute twice
[ http://jira.codehaus.org/browse/MSOURCES-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSOURCES-37. --- Resolution: Duplicate > CLONE -maven-source-plugin causes generate-sources phase to execute twice > - > > Key: MSOURCES-37 > URL: http://jira.codehaus.org/browse/MSOURCES-37 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.0.1 >Reporter: md > > Due to the lack of documentation, I configured the plugin as follows, in > order to install sources when doing "mvn install": > > org.apache.maven.plugins > maven-source-plugin > > > install > > jar > > > > > Unfortunately, "mvn install" causes the generate-sources phase to execute > twice, which can manifest for example in an antrun-task executing twice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MSOURCES-31) forking lifecycle of source:jar goal results in release-plugin error
[ http://jira.codehaus.org/browse/MSOURCES-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSOURCES-31. --- Resolution: Duplicate > forking lifecycle of source:jar goal results in release-plugin error > > > Key: MSOURCES-31 > URL: http://jira.codehaus.org/browse/MSOURCES-31 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.0.4 > Environment: maven 2.0.8 >Reporter: Sandro Sonntag >Priority: Blocker > > In my complex scenario the release plugin fails because the source:jar goal > forks a new lifcycle "generate-sources". > "source:jar" is decalared in the project pom to build automaticly. The error > occours if there are plugins attached on the "generate-sources" phase > how need artifacts of the reactor build. > In my case the xdoclet and attributes plugins are attached. > The following error occoures if I use the release plugin: > Missing: > -- > 1) de.kqv.ec.tarif:tarif-freundschaftswerbung-businesslogic:jar:1.0 > Try downloading the file manually from the project website. > Then, install it using the command: > mvn install:install-file -DgroupId=de.kqv.ec.tarif > -DartifactId=tarif-freundschaftswerbung-businesslogic -Dversion=1.0 > -Dpackaging=jar - > Dfile=/path/to/file > Alternatively, if you host your own repository you can deploy the > file there: > mvn deploy:deploy-file -DgroupId=de.kqv.ec.tarif > -DartifactId=tarif-freundschaftswerbung-businesslogic -Dversion=1.0 > -Dpackaging=jar -Df > ile=/path/to/file -Durl=[url] -DrepositoryId=[id] > Path to dependency: > 1) > de.kqv.ec.tarif:tarif-freundschaftswerbung-businesslogic-ejb:ejb:1.0 > 2) > de.kqv.ec.tarif:tarif-freundschaftswerbung-businesslogic:jar:1.0 > If I remove the source plugin all workes fine. There is no possible > workaround know. A solution could be to remove the "execute phase" of the > plugin. I cant > imagine that somebody use the goal standalone. I thing its a general Maven > design problem. > Forking a phase sould only be executed if the goal is running standalone. But > I´m not the expert. > Greetings Sandro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSOURCES-30) Should not output INFO message when maven is run in quiet mode
[ http://jira.codehaus.org/browse/MSOURCES-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166930#action_166930 ] Dennis Lundberg commented on MSOURCES-30: - The logging statement comes from a dependency of the Source Plugin: Plexus Archiver. > Should not output INFO message when maven is run in quiet mode > -- > > Key: MSOURCES-30 > URL: http://jira.codehaus.org/browse/MSOURCES-30 > Project: Maven 2.x Source Plugin > Issue Type: Bug >Affects Versions: 2.0.4 >Reporter: Mauritz Lovgren >Priority: Minor > > Currently, the source plugin produces INFO statement for created source jars > even if maven is run in quite mode. > This produces unwanted output to system.out during build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-13) No-Forking mojos for use within a POM instead of CLI
[ http://jira.codehaus.org/browse/MSOURCES-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSOURCES-13: Fix Version/s: (was: 2.1) > No-Forking mojos for use within a POM instead of CLI > > > Key: MSOURCES-13 > URL: http://jira.codehaus.org/browse/MSOURCES-13 > Project: Maven 2.x Source Plugin > Issue Type: Improvement >Affects Versions: 2.0.3 > Environment: ALL >Reporter: Ben Tatham > Attachments: nofork.patch, nofork.patch > > > The exiting jar at test-jar mojos will always cause a lifecycle fork and > generate-sources. This can cause all kinds of undesired side effects when > using the source plugin with a pom, instead of CLI. I propose a simple fix > (patch attached) to extend these two mojos in no-forking mode. I can't think > of a better name for them. > This behaviour is similar to the difference between assembly:assembly and > assembly:attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-24) jar misses resources from "generate-resources" phase
[ http://jira.codehaus.org/browse/MSOURCES-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSOURCES-24: Fix Version/s: (was: 2.1) > jar misses resources from "generate-resources" phase > > > Key: MSOURCES-24 > URL: http://jira.codehaus.org/browse/MSOURCES-24 > Project: Maven 2.x Source Plugin > Issue Type: Improvement >Affects Versions: 2.0.3 > Environment: Maven 2.0.7 >Reporter: Benjamin Bentmann >Priority: Minor > > When the goal source:jar is run directly from the command-line, the plugin > will miss resource files that get generated during the "generate-resources" > phase as the mojo currently only requires the "generate-sources" phase. > Increasing the lifecycle requirements of the mojo to "generate-resources" > would also cause "process-sources" to get run. I cannot judge whether this > would cause any harm to existing plugin users. One might further consider to > increase the lifecycle requirement to "process-resources" so that both > sources and resources are in a consistent state before being packaged. > Taking [MSOURCES-22|http://jira.codehaus.org/browse/MSOURCES-22] into > account, it might be advisable to separate the packaging of sources and > resources into two distinct mojos. The first mojo would only package the > (compile) source files and would therefore only require the > "generate-/process-sources" phase. The second mojo would package the source > files and the resources (similar to the current jar goal), requiring the > phase "generate-/process-resources". In contrast to adding a configuration > option to exclude resources, introducing a new mojo would allow to tune the > lifecycle requirements, hopefully supporting more use-cases for the plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSOURCES-23) test-jar misses sources from "generate-test-sources" phase
[ http://jira.codehaus.org/browse/MSOURCES-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSOURCES-23: Fix Version/s: (was: 2.1) > test-jar misses sources from "generate-test-sources" phase > -- > > Key: MSOURCES-23 > URL: http://jira.codehaus.org/browse/MSOURCES-23 > Project: Maven 2.x Source Plugin > Issue Type: Improvement >Affects Versions: 2.0.3 > Environment: Maven 2.0.7 >Reporter: Benjamin Bentmann >Priority: Minor > > When the goal source:test-jar is run directly from the command-line, the > plugin will miss source files that get generated during the > "generate-test-sources" phase as the mojo currently only requires the > "generate-sources" phase. > Though simply increasing the mojos lifecycle requirement would solve the > problem, it kind of looks ugly to have the lengthy and potentially failing > "compile" phase get run just to package test sources (first time I realize > practical limitations of Maven's simple waterfall lifecycle compared to > partially ordered goals...). An additional mojo like "generated-test-jar" > might therefore be the best solution to keep the majority of use-cases fast > but support the more sophisticated cases as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2368) Please upload maven-concordion-plugin 1.0.0
Please upload maven-concordion-plugin 1.0.0 --- Key: MAVENUPLOAD-2368 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2368 Project: Maven Upload Requests Issue Type: Wish Reporter: Jose M Beas -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4045) Matching plugin versions also removes custom configurations
[
http://jira.codehaus.org/browse/MNG-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166932#action_166932
]
Brett Porter commented on MNG-4045:
---
that's what I understood, and is consistent with my comment. does the attached
sample project work for you?
> Matching plugin versions also removes custom configurations
> ---
>
> Key: MNG-4045
> URL: http://jira.codehaus.org/browse/MNG-4045
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0.9, 2.0.10
>Reporter: Paul Benedict
>Assignee: Brett Porter
> Attachments: MNG-4045.zip
>
>
> I was locking down my Maven Changes Plugin version with the following config:
> {code}
>
>
> org.apache.maven.plugins
> maven-changes-plugin
> 2.1
>
>
>
> changes-report
>
>
>
>
>
> {code}
> And then I created the site and noticed the report was empty. The report
> markup was there, of course, but it generated like my changes.xml was blank.
> I could run changes:changes-report just fine. However, when I then removed
> the tag and tried site:site again, the report output was present as
> expected.
> Here's an interesting line from the debug output when is specified:
> {quote}[DEBUG] The following artifacts were filtered out for plugin:
> org.apache.maven.plugins:maven-changes-plugin:2.1 because they're already in
> the core of Maven:{quote}
> My theory is that because my plugin version has an exact match on the
> version, my specified plugin configuration is tossed. That certainly seems
> like a bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2368) Please upload maven-concordion-plugin 1.0.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166934#action_166934 ] Jose M Beas commented on MAVENUPLOAD-2368: -- Sorry, I've made a wrong submit of this issue and the Contributor URL is wrong. I think it should be http://jmbeas.blogspot.com > Please upload maven-concordion-plugin 1.0.0 > --- > > Key: MAVENUPLOAD-2368 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2368 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jose M Beas > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MAVENUPLOAD-2368) Please upload maven-concordion-plugin 1.0.0
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166934#action_166934 ] Jose M Beas edited comment on MAVENUPLOAD-2368 at 2/24/09 6:08 PM: --- Sorry, I've made a wrong submit of this issue and the Contributor URL is wrong. I think it should be http://maven-concordion.googlecode.com. was (Author: jmbeas): Sorry, I've made a wrong submit of this issue and the Contributor URL is wrong. I think it should be http://jmbeas.blogspot.com > Please upload maven-concordion-plugin 1.0.0 > --- > > Key: MAVENUPLOAD-2368 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2368 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Jose M Beas > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3379) Parallel resolution of artifacts
[ http://jira.codehaus.org/browse/MNG-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166935#action_166935 ] Brett Porter commented on MNG-3379: --- I was able to reproduce this once, I'm looking into ways to test it more reliably, and also checking all the code that gets touched for sync issues. > Parallel resolution of artifacts > > > Key: MNG-3379 > URL: http://jira.codehaus.org/browse/MNG-3379 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Don Brown >Assignee: Brett Porter > Fix For: 2.1.0 > > Attachments: parallel-resolution-2.diff, parallel-resolution-3.diff, > parallel-resolution.diff > > > Artifacts should be resolved in parallel, grouped by group id's to get around > the lack of synchronization in the local repository. The patch does the > following: > * Use a ThreadPoolExecutor to parallelize artifact resolution, but takes care > not to resolve multiple artifacts from the same group id simultaneously. > (requires Java 5) > * Makes the http wagon the default instead of the poor performing http-client > Disadvantages: > * Requires Java 5, but the backport jars could be substituted pretty easily > * Breaks some plugins due to commons-logging being in the Maven uber jar > (required by commons-httpclient), notably the apt plugin (maybe more should > use the isolatedRealm setting?) > * Screws up the progress monitor as multiple threads are updating it > Advantages: > * Much faster when combined with the http wagon (WAGON-98). I was seeing 40% > improvement on some test builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MERCURY-101) adjust logging to only show downloaded files on INFO level
adjust logging to only show downloaded files on INFO level -- Key: MERCURY-101 URL: http://jira.codehaus.org/browse/MERCURY-101 Project: Mercury Issue Type: Improvement Components: Repository Affects Versions: 1.0-alpha-6 Reporter: Oleg Gusakov Assignee: Oleg Gusakov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3379) Parallel resolution of artifacts
[ http://jira.codehaus.org/browse/MNG-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166945#action_166945 ] Brett Porter commented on MNG-3379: --- reviewing coverage details for artifact resolution, I've narrowed it down to just DefaultWagonManager that is not thread safe (but is expected to be) > Parallel resolution of artifacts > > > Key: MNG-3379 > URL: http://jira.codehaus.org/browse/MNG-3379 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Don Brown >Assignee: Brett Porter > Fix For: 2.1.0 > > Attachments: parallel-resolution-2.diff, parallel-resolution-3.diff, > parallel-resolution.diff > > > Artifacts should be resolved in parallel, grouped by group id's to get around > the lack of synchronization in the local repository. The patch does the > following: > * Use a ThreadPoolExecutor to parallelize artifact resolution, but takes care > not to resolve multiple artifacts from the same group id simultaneously. > (requires Java 5) > * Makes the http wagon the default instead of the poor performing http-client > Disadvantages: > * Requires Java 5, but the backport jars could be substituted pretty easily > * Breaks some plugins due to commons-logging being in the Maven uber jar > (required by commons-httpclient), notably the apt plugin (maybe more should > use the isolatedRealm setting?) > * Screws up the progress monitor as multiple threads are updating it > Advantages: > * Much faster when combined with the http wagon (WAGON-98). I was seeing 40% > improvement on some test builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3379) Parallel resolution of artifacts
[ http://jira.codehaus.org/browse/MNG-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166946#action_166946 ] Brett Porter commented on MNG-3379: --- the only potential problem I could find under current usage is the one triggered here, which is a bug in Plexus but can be externally synchronized. This wouldn't have tripped Don up as his branch was taken before the additional component configuration step was taken (for setting the HTTP headers). I'm working on a test case in Maven for this and will then synchronize it properly. Other potential problem spots: a number of configuration maps in DefaultWagonManager that are only modified on initialization (if they were modified during a multithreaded scenario there'd be a problem). Also, the repository list passed in to the resolution must not be modifiable as it isn't cloned. > Parallel resolution of artifacts > > > Key: MNG-3379 > URL: http://jira.codehaus.org/browse/MNG-3379 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Don Brown >Assignee: Brett Porter > Fix For: 2.1.0 > > Attachments: parallel-resolution-2.diff, parallel-resolution-3.diff, > parallel-resolution.diff > > > Artifacts should be resolved in parallel, grouped by group id's to get around > the lack of synchronization in the local repository. The patch does the > following: > * Use a ThreadPoolExecutor to parallelize artifact resolution, but takes care > not to resolve multiple artifacts from the same group id simultaneously. > (requires Java 5) > * Makes the http wagon the default instead of the poor performing http-client > Disadvantages: > * Requires Java 5, but the backport jars could be substituted pretty easily > * Breaks some plugins due to commons-logging being in the Maven uber jar > (required by commons-httpclient), notably the apt plugin (maybe more should > use the isolatedRealm setting?) > * Screws up the progress monitor as multiple threads are updating it > Advantages: > * Much faster when combined with the http wagon (WAGON-98). I was seeing 40% > improvement on some test builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2369) Multithreaded Test Case 1.01
Multithreaded Test Case 1.01 Key: MAVENUPLOAD-2369 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2369 Project: Maven Upload Requests Issue Type: Bug Reporter: Brett Porter Assignee: Brett Porter -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MAVENUPLOAD-2369) Multithreaded Test Case 1.01
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MAVENUPLOAD-2369. - Resolution: Fixed > Multithreaded Test Case 1.01 > > > Key: MAVENUPLOAD-2369 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2369 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Brett Porter >Assignee: Brett Porter > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3379) Parallel resolution of artifacts
[ http://jira.codehaus.org/browse/MNG-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-3379. - Resolution: Fixed sync issue fixed. Added a test case that can reproduce in most scenarios though it does rely on timing as Plexus is not testable in that fashion at the moment > Parallel resolution of artifacts > > > Key: MNG-3379 > URL: http://jira.codehaus.org/browse/MNG-3379 > Project: Maven 2 > Issue Type: New Feature > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Don Brown >Assignee: Brett Porter > Fix For: 2.1.0 > > Attachments: parallel-resolution-2.diff, parallel-resolution-3.diff, > parallel-resolution.diff > > > Artifacts should be resolved in parallel, grouped by group id's to get around > the lack of synchronization in the local repository. The patch does the > following: > * Use a ThreadPoolExecutor to parallelize artifact resolution, but takes care > not to resolve multiple artifacts from the same group id simultaneously. > (requires Java 5) > * Makes the http wagon the default instead of the poor performing http-client > Disadvantages: > * Requires Java 5, but the backport jars could be substituted pretty easily > * Breaks some plugins due to commons-logging being in the Maven uber jar > (required by commons-httpclient), notably the apt plugin (maybe more should > use the isolatedRealm setting?) > * Screws up the progress monitor as multiple threads are updating it > Advantages: > * Much faster when combined with the http wagon (WAGON-98). I was seeing 40% > improvement on some test builds. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DOXIA-291) Wrong classid in SwfMacro
[
http://jira.codehaus.org/browse/DOXIA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed DOXIA-291.
---
Assignee: Lukas Theussl
Resolution: Fixed
Fixed in r747674
> Wrong classid in SwfMacro
> -
>
> Key: DOXIA-291
> URL: http://jira.codehaus.org/browse/DOXIA-291
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.0
>Reporter: Denis Knauer
>Assignee: Lukas Theussl
> Fix For: 1.1
>
>
> There is a missing ": D" (without space) in the classid of the SwfMacro.
> The actual version looks like:
> {code:title=SwfMacro.java|borderStyle=solid}
> content.append( " " )
> .append(
> "codebase=\"http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=";
> )
> .append( version ).append( "\" width=\"" ).append( width
> ).append( "\" height=\"" ).append( height )
> .append( "\" id=\"" ).append( id ).append( "\">" ).append( EOL );
> {code}
> Ist must be:
> {code:title=SwfMacro.java|borderStyle=solid}
> content.append( " classid=\"clsid:D27CDB6E-AE6D-11cf-96B8-44455354\" " )
> .append(
> "codebase=\"http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=";
> )
> .append( version ).append( "\" width=\"" ).append( width
> ).append( "\" height=\"" ).append( height )
> .append( "\" id=\"" ).append( id ).append( "\">" ).append( EOL );
> {code}
> The swf File is not included correctly otherwise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DOXIA-291) Wrong classid in SwfMacro
[
http://jira.codehaus.org/browse/DOXIA-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated DOXIA-291:
Affects Version/s: 1.0
Fix Version/s: 1.1
> Wrong classid in SwfMacro
> -
>
> Key: DOXIA-291
> URL: http://jira.codehaus.org/browse/DOXIA-291
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core
>Affects Versions: 1.0
>Reporter: Denis Knauer
> Fix For: 1.1
>
>
> There is a missing ": D" (without space) in the classid of the SwfMacro.
> The actual version looks like:
> {code:title=SwfMacro.java|borderStyle=solid}
> content.append( " " )
> .append(
> "codebase=\"http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=";
> )
> .append( version ).append( "\" width=\"" ).append( width
> ).append( "\" height=\"" ).append( height )
> .append( "\" id=\"" ).append( id ).append( "\">" ).append( EOL );
> {code}
> Ist must be:
> {code:title=SwfMacro.java|borderStyle=solid}
> content.append( " classid=\"clsid:D27CDB6E-AE6D-11cf-96B8-44455354\" " )
> .append(
> "codebase=\"http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=";
> )
> .append( version ).append( "\" width=\"" ).append( width
> ).append( "\" height=\"" ).append( height )
> .append( "\" id=\"" ).append( id ).append( "\">" ).append( EOL );
> {code}
> The swf File is not included correctly otherwise.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2387) on in settings is misleading
[ http://jira.codehaus.org/browse/MNG-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=166954#action_166954 ] Brett Porter commented on MNG-2387: --- I added an integration test as well. It'd be great if you could also submit those in future :) Thanks for the patch! > on in settings is misleading > - > > Key: MNG-2387 > URL: http://jira.codehaus.org/browse/MNG-2387 > Project: Maven 2 > Issue Type: Task > Components: Settings >Reporter: Brett Porter > Fix For: 2.0.x > > Attachments: MNG-2387-maven-settings.patch > > > see: > http://mail-archives.apache.org/mod_mbox/maven-users/200510.mbox/%3c84fb18c70510171532v1d655221n36b66fb10a018...@mail.gmail.com%3e -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2387) on in settings is misleading
[ http://jira.codehaus.org/browse/MNG-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-2387. - Assignee: Brett Porter Resolution: Fixed Fix Version/s: (was: 2.0.x) 2.1.0 2.0.11 > on in settings is misleading > - > > Key: MNG-2387 > URL: http://jira.codehaus.org/browse/MNG-2387 > Project: Maven 2 > Issue Type: Task > Components: Settings >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 2.0.11, 2.1.0 > > Attachments: MNG-2387-maven-settings.patch > > > see: > http://mail-archives.apache.org/mod_mbox/maven-users/200510.mbox/%3c84fb18c70510171532v1d655221n36b66fb10a018...@mail.gmail.com%3e -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
