[jira] Created: (MECLIPSE-485) wtpdefaultserver output as "null"
wtpdefaultserver output as "null"
-
Key: MECLIPSE-485
URL: http://jira.codehaus.org/browse/MECLIPSE-485
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.5.1
Environment: Windows XP SP3, JDK 1.6, Eclipse 3.4, WTP 3.0
Reporter: Ari Meyer
Priority: Minor
Attachments: pom.xml, pom.xml, pom.xml
Hi,
I always see the "wtpdefaultserver" output as "null" on the command line:
[INFO]
[INFO] Building core project classes (JPA project)
[INFO]task-segment: [eclipse:eclipse, install]
[INFO]
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 2.0.
Downloading:
http://repo1.maven.org/maven2/com/microsoft/sqljdbc/1.1/sqljdbc-1.1.pom
Downloading:
http://repo1.maven.org/maven2/com/oracle/ojdbc14/10.2.0.1.0/ojdbc14-10.2.0.1.0.pom
Downloading: http://repo1.maven.org/maven2/com/imanage/k3/5.0/k3-5.0.pom
[INFO] no exact wtp server match.
[INFO] Using as WTP server : null
...
[INFO] Building war assembly
[INFO]task-segment: [eclipse:eclipse, install]
[INFO]
[INFO] Preparing eclipse:eclipse
[INFO] No goals needed for project - skipping
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 2.0.
[INFO] no exact wtp server match.
[INFO] Using as WTP server : null
...
[INFO] Building ear assembly
[INFO]task-segment: [eclipse:eclipse, install]
[INFO]
[INFO] Preparing eclipse:eclipse
[INFO] [ear:generate-application-xml]
[INFO] Generating application.xml
[INFO] [eclipse:eclipse]
[INFO] Adding support for WTP version 2.0.
[INFO] no exact wtp server match.
[INFO] Using as WTP server : null
It doesn't seem to cause any complications, and everything runs fine (which is
all I really care about ;-), but I don't know if I'm doing something wrong. In
my parent POM I'm setting it as:
Oracle WebLogic Server v10.3 at localhost
(the server name as displayed in Eclipse)
I tried also with "Oracle WebLogic Server v10.3" (the server type), but that
didn't work either. It's unclear what I'm exactly supposed to put as the
value, as the docs only show:
wtpdefaultserver What WTP defined server to use for deployment informations.
* Type: java.lang.String
* Required: No
* Expression: ${eclipse.wtpdefaultserver}
I'm guessing, though, that it should be the server name as displayed in
Eclipse, correct?
Thanks for the good work!
Ari
BTW: I was only able to attach 3 of the 4 POMs I use, but in any case, I only
define it in the parent POM.
--
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: (MWAR-168) "Dependency Has Changed" Incorrectly Reported
[
http://jira.codehaus.org/browse/MWAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146955#action_146955
]
Stephane Nicoll commented on MWAR-168:
--
this is a new feature and this is a "known" problem but thanks for the bug
hunting which will help fixing it :)
You can safely ignore it (or you can disable the cache to avoid the message)
> "Dependency Has Changed" Incorrectly Reported
> -
>
> Key: MWAR-168
> URL: http://jira.codehaus.org/browse/MWAR-168
> Project: Maven 2.x War Plugin
> Issue Type: Bug
>Affects Versions: 2.1-alpha-2
>Reporter: gotama
>
> In maven-war-plugin 2.1-alpha-2, execute the following on a war project:
> mvn clean;
> mvn install;
> mvn install;
> The 3rd command incorrectly lists messages for each dependency as follows:
> [INFO] Dependency[Dependency {groupId=com.mycompany, artifactId=myartifact,
> version=8.6.1, type=jar}]
> has changed (was Dependency {groupId=com.mycompany, artifactId=myartifact,
> version=8.6.1, type=jar}).
> The first time that mvn install is run, dependencies are added to:
> target\myapp-war-1.1-SNAPSHOT\WEB-INF\lib
> The second invocation of mvn install appears to fail in comparing the
> existing jars in the above path with what is in the repository. The message
> states the dependencies have changed when in fact they have not.
> This problem does not exist in maven-war-plugin 2.0.2.
--
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: (MRELEASE-362) Support tagging nested projects
[
http://jira.codehaus.org/browse/MRELEASE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146963#action_146963
]
Stijn Maller commented on MRELEASE-362:
---
I agree with Russell, when doing a multi-project build I expected the release
plugin to individually tag all my projects. Instead it only tags the "parent"
project. (parent as in project aggregation, not project inheritance) I can see
how this could be more or less useful if all your projects are nested under the
parent. In this case at least everything will be tagged, albeit with the same
tag.
|
| project A 1.0 (multimodule aggregator for B and C)
|
| project B 2.1
|
| project C 3.4
A, B and C get tagged with "project A_1.0"
However, in our project the projects are next to the aggregate build, meaning
almost nothing gets tagged. (Project A does not contain much more then the pom
itself)
|
| project A 1.0 (multimodule aggregator for B and C) 1.0
|
| project B 2.1
|
| project C 3.4
=> Every release we build project A will be tagged. (Although it almost never
changes itself)
Project B and C on the other hand change constantly but have to be tagged
manually.
> Support tagging nested projects
> ---
>
> Key: MRELEASE-362
> URL: http://jira.codehaus.org/browse/MRELEASE-362
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
>Affects Versions: 2.0-beta-6
>Reporter: Michael Johns
>Priority: Minor
>
> We have a non-standard situation here. I can _almost_ get Maven to support
> it, but I can't cross the last hurdle of tagging and releasing the project.
> The business case is that we have a core product that is built with Maven and
> a customer implementation of that product that is also built with Maven.
> Each builds just fine on their own. They are both first-class projects. The
> second project depends on the first. Each project has multiple modules.
> The situation we want to support is parallel development of both projects.
> If a developer makes a change in the Core product, we don't want to have to
> go through a tag/release cycle in order to pull that change into the Customer
> project. (Yes, this is non-standard and not the best idea, but we have few
> options due to time and resources.) To accomplish this, we linked the second
> project into the first using svn:externals. We then created a new profile in
> our pom.xml that pulls in the "parent" pom.xml from the second project as a
> module. Let me see if I can visually represent it:
> Core Product
> - Core Product Module 1
> - Core Product Module 2
> - Core Product Module 3
> - Customer Project <== linked via svn:externals and included as a module
> in the "Core Product" pom.xml via a profile
> - Customer Project Module 1
> - Customer Project Module 2
> - Customer Project Module 3
> Note that the version numbers for the Customer projects are different than
> those in the Core Product.
> This works like a champ when running most plug-ins against it. For example,
> I can run the eclipse plug-in against it (using the special profile), and all
> project dependencies are resolved correctly between the two. The problem
> comes when I try to tag and release them together. This is the command I'm
> using:
> {code}
> mvn -P customer --batch-mode -Darguments="-P customer"
> -DpreparationGoals="jar:test-jar install" -Dresume=false -Dgoals="deploy
> site-deploy" clean install release:prepare release:perform release:clean
> {code}
> The "customer" profile is the one that pulls in the customer projects. This
> command (executed in Continuum) works like a champ to release our other
> projects. But when I run it against this project, here's what happens:
> # Updates versions on all projects (both Core and Customer) to drop SNAPSHOT
> # Installs all projects
> # Tags Core project
> #* Does *not* tag Customer project (*this is the problem*)
> #* Tagged Core project still points to external projects' trunk (this is a
> SVN issue, not a Maven issue)
> # Updates versions on all projects (both Core and Customer) to next SNAPSHOT
> # Checks out tagged project
> #* Project still points to Customer project's trunk (again, a SVN issue)
> # Builds projects
> #* Build fails on external projects because they point to the new SNAPSHOT
> version of main project (due to SVN issue)
> So ignoring the SVN issues, here's what I'd like to see supported by the
> release plug-in:
> * When tagging, also tag the Customer project that is included via a module.
> It is a stand-alone project, so it has all of the necessary information in
> the pom.
> I know this is a bit convoluted, so please let me know if you need
> clarification. I could potentially attach some of our
[jira] Created: (WAGON-241) Misleading error messages when local repository is not writable
Misleading error messages when local repository is not writable --- Key: WAGON-241 URL: http://jira.codehaus.org/browse/WAGON-241 Project: Maven Wagon Issue Type: Bug Components: wagon-http Affects Versions: 1.0-beta-2 Environment: Linux - Ubuntu 8.04 Server - JDK Sun 1.6.0_06 - Maven 2.0.9 Reporter: Clement Denis Priority: Minor Attachments: unwritable_local_repository.txt When the local repository is not writable, the error messages when downloading an artifact does not allow to pin down the issue quickly. Maven only reports that the artifact cannot be downloaded, and the root cause is displayed as : Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository No message in the trace indicates a problem with the local repository. The full trace with a clean local repository is 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] Created: (MNG-3742) Exclusion of transitive dependiencies does not work
Exclusion of transitive dependiencies does not work --- Key: MNG-3742 URL: http://jira.codehaus.org/browse/MNG-3742 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: Grzegorz Borkowski Attachments: pom.xml I create empty project with jar-type pom. I add dependency on log4j 1.2.15 (the most up-to-date version). Build fails, because log4j declares in its pom dependencies on some Sun librareis, which are not available for Maven to download. They should be marked optional in log4j pom, but they are not (they claim it will be fixed in 1.2.16, but it is not released yet). So I exclude dependienices, according to the document: http://docs.codehaus.org/display/MAVENUSER/Dependency+Mechanism However, build still fails, as Maven still tries to download excluded libraries. This seems a bug in Maven. This is easilyt reproducable from comand-line, NetBeans or Eclipse. See my pom 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] Commented: (SUREFIRE-377) When JUnit and TestNG tests are in same project, only one set gets run
[ http://jira.codehaus.org/browse/SUREFIRE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146966#action_146966 ] Rune Engseth commented on SUREFIRE-377: --- I agree with Pawel When adopting TestNG into an existing project with lots of existing JUnit 4.4 tests, it would be nice if both types of tests could be run at once. If Pawel's additional check would fix this, is it possible to add this to the next SNAPSHOT version? > When JUnit and TestNG tests are in same project, only one set gets run > -- > > Key: SUREFIRE-377 > URL: http://jira.codehaus.org/browse/SUREFIRE-377 > Project: Maven Surefire > Issue Type: Bug > Components: TestNG support >Affects Versions: 2.4 >Reporter: Dan Fabulich > Fix For: 2.4 > > Attachments: surefire377.patch, testng-junit-together.zip > > > The attached Maven project has two tests: one JUnit test and one TestNG test. > According to the documentation, in this case TestNG should run both tests. > Run "mvn test". Only the TestNG test will run. If you modify the pom to set > the property "junit=true", only the JUnit test will run. > > org.apache.maven.plugins > maven-surefire-plugin > 2.4-SNAPSHOT > > > > junit > true > > > -- 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: (MASSEMBLY-342) NPE when filtering fileSet
[
http://jira.codehaus.org/browse/MASSEMBLY-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146967#action_146967
]
Petar Tahchiev commented on MASSEMBLY-342:
--
OK,
after discussing this with the Maved SHARED team, we agreed that this is more a
Maven Assembly issue. So I will attach a zip containing a new patch and
integration-tests.
> NPE when filtering fileSet
> --
>
> Key: MASSEMBLY-342
> URL: http://jira.codehaus.org/browse/MASSEMBLY-342
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Environment: Windows XP, cygwin, Java 1.5.0.9
>Reporter: Peter Verhás
>Assignee: John Casey
>Priority: Critical
> Fix For: 2.2-beta-3
>
> Attachments: massembly-342.txt
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I get NPE when I specify filtering in an assembly descriptor. The
> {{src/assembly/bin.xml}} file (referenced by the {{pom.xml}} as an assembly
> descriptor) is the following:
> {code}
>
> bin
>
> zip
>
> false
>
>
> lib
>
>
>
>
> target
>
>
> *.jar
>
>
>
> true
>
> INSTALL*
> README*
> LICENSE*
> NOTICE*
>
>
>
>
> {code}
> This causes
> {code}
> $ mvn -e assembly:assembly
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'assembly'.
> [INFO]
>
> [INFO] Building Unnamed - verhas.com:isoapui8583:jar:1.0.0
> [INFO]task-segment: [assembly:assembly] (aggregator-style)
> [INFO]
>
> [INFO] Preparing assembly:assembly
> [INFO]
>
> [INFO] Building Unnamed - verhas.com:isoapui8583:jar:1.0.0
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> Downloading:
> http://repo1.maven.org/maven2/xmlbeans/xbean/2.3.0-trunk-patched/xbean-2.3.0-trunk-patched.pom
> Downloading:
> http://repo1.maven.org/maven2/groovy/groovy-all/1.5.2/groovy-all-1.5.2.pom
> Downloading:
> http://repo1.maven.org/maven2/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.pom
> Downloading:
> http://repo1.maven.org/maven2/cweb-extser/cweb-extser/0.1-b2-dev/cweb-extser-0.1-b2-dev.pom
> Downloading:
> http://repo1.maven.org/maven2/jPOS/jpos/1.6.2-r2626/jpos-1.6.2-r2626.pom
> [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] Nothing to compile - all classes are up to date
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\surefire-reports
> ---
> T E S T S
> ---
> Running com.verhas.soapui.jpos.TestServer
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec
> Running com.verhas.soapui.jpos.TestClient
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec
> Running com.verhas.soapui.jpos.TestClientServer
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> Running com.verhas.soapui.jpos.TestConstants
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] [jar:jar]
> [INFO] Building jar:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\isoapui8583-1.0.0.jar
> [INFO] [assembly:assembly]
> [INFO] Reading assembly descriptor: src/assembly/doc.xml
> [INFO] Reading assembly descriptor: src/assembly/bin.xml
> [INFO] Reading assembly descriptor: src/assembly/src.xml
> [INFO] Building zip:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\isoapui8583-1.0.0-doc.zip
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at java.io
[jira] Updated: (MASSEMBLY-342) NPE when filtering fileSet
[
http://jira.codehaus.org/browse/MASSEMBLY-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petar Tahchiev updated MASSEMBLY-342:
-
Attachment: massembly-342.zip
Here is the zip file with the new patch and the integration-tests.
> NPE when filtering fileSet
> --
>
> Key: MASSEMBLY-342
> URL: http://jira.codehaus.org/browse/MASSEMBLY-342
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Environment: Windows XP, cygwin, Java 1.5.0.9
>Reporter: Peter Verhás
>Assignee: John Casey
>Priority: Critical
> Fix For: 2.2-beta-3
>
> Attachments: massembly-342.txt, massembly-342.zip
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I get NPE when I specify filtering in an assembly descriptor. The
> {{src/assembly/bin.xml}} file (referenced by the {{pom.xml}} as an assembly
> descriptor) is the following:
> {code}
>
> bin
>
> zip
>
> false
>
>
> lib
>
>
>
>
> target
>
>
> *.jar
>
>
>
> true
>
> INSTALL*
> README*
> LICENSE*
> NOTICE*
>
>
>
>
> {code}
> This causes
> {code}
> $ mvn -e assembly:assembly
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'assembly'.
> [INFO]
>
> [INFO] Building Unnamed - verhas.com:isoapui8583:jar:1.0.0
> [INFO]task-segment: [assembly:assembly] (aggregator-style)
> [INFO]
>
> [INFO] Preparing assembly:assembly
> [INFO]
>
> [INFO] Building Unnamed - verhas.com:isoapui8583:jar:1.0.0
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> Downloading:
> http://repo1.maven.org/maven2/xmlbeans/xbean/2.3.0-trunk-patched/xbean-2.3.0-trunk-patched.pom
> Downloading:
> http://repo1.maven.org/maven2/groovy/groovy-all/1.5.2/groovy-all-1.5.2.pom
> Downloading:
> http://repo1.maven.org/maven2/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.pom
> Downloading:
> http://repo1.maven.org/maven2/cweb-extser/cweb-extser/0.1-b2-dev/cweb-extser-0.1-b2-dev.pom
> Downloading:
> http://repo1.maven.org/maven2/jPOS/jpos/1.6.2-r2626/jpos-1.6.2-r2626.pom
> [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] Nothing to compile - all classes are up to date
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\surefire-reports
> ---
> T E S T S
> ---
> Running com.verhas.soapui.jpos.TestServer
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec
> Running com.verhas.soapui.jpos.TestClient
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec
> Running com.verhas.soapui.jpos.TestClientServer
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> Running com.verhas.soapui.jpos.TestConstants
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] [jar:jar]
> [INFO] Building jar:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\isoapui8583-1.0.0.jar
> [INFO] [assembly:assembly]
> [INFO] Reading assembly descriptor: src/assembly/doc.xml
> [INFO] Reading assembly descriptor: src/assembly/bin.xml
> [INFO] Reading assembly descriptor: src/assembly/src.xml
> [INFO] Building zip:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\isoapui8583-1.0.0-doc.zip
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at java.io.File.(File.java:222)
> at
> org.apache.maven.shared.model.fileset.util.FileSetManager.scan(FileSetM
[jira] Closed: (MAVENUPLOAD-2198) Please upload simple-4.0.1 to central Maven 2 repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary S. Weaver closed MAVENUPLOAD-2198. --- Resolution: Incomplete Going to close this and open up a new bug for uploading v4.0.2 instead so there won't be any confusion. > Please upload simple-4.0.1 to central Maven 2 repo > -- > > Key: MAVENUPLOAD-2198 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2198 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Gary S. Weaver > Attachments: simple-web-4.0.1-bundle.jar, simple-web-4.0.1.jar > > > Simple ( http://www.simpleframework.org/ ) is self described as: "The goal of > Simple is to bring the power of simplicity to the world of server side Java. > The primary focus of the project is to provide a truly embeddable Java based > HTTP engine capable of handling enormous loads. Simple provides a truly > asynchronous service model, request completion is driven using an internal, > transparent, monitoring system. This allows Simple to vastly outperform most > popular Java based servers in a multi-tier environment, as it requires only a > very limited number of threads to handle very high quantities of concurrent > clients. Simple has consistently out performed both commercial and open > source Java Servlet engines and has a fully comprehensive API that is as > usable for experienced Java developers as it is for beginners. Best of all, > Simple is completely free, and is released under the terms of the GNU Lesser > General Public License, LGPL, which ensures its availability for use by open > source and proprietary developers alike." > Simple is also mentioned here (where I found reference to it): > http://java-source.net/open-source/web-servers > I think it would make a good addition to the central Maven 2 repository, and > I'd consider using it in a project I'm developing. I also mentioned it on the > maven users mailing list. > I will attempt to contact the developer to inform him of this. > Bundle 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] Commented: (MASSEMBLY-260) Empty archive-tmp appears in target folder after assembly created.
[
http://jira.codehaus.org/browse/MASSEMBLY-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146975#action_146975
]
Petar Tahchiev commented on MASSEMBLY-260:
--
Hi Matthew,
I tried Maven 2.0.9, assembly 2.2-beta-1, 2.2-beta-2, 2.2-beta-3-SNAPSHOT, but
I can't reproduce this issue. Can you package your project source and give it
to me, so that I can give it a shot?
> Empty archive-tmp appears in target folder after assembly created.
> --
>
> Key: MASSEMBLY-260
> URL: http://jira.codehaus.org/browse/MASSEMBLY-260
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Environment: I'm using Maven 2.0.7, and maven-assembly-plugin version
> 2.2-beta-1.
>Reporter: Matthew Tordoff
>
> I have created a custom assembly which packages up 3 directories within my
> projects root directory as a zip file. This file can be seen as follows:
>
> My Format
>
> zip
>
>
>
> ${basedir}\folderA
> \folderA
>
> **\**
>
>
>
> ${basedir}\folderB
> \folderB
>
> **\**
>
>
>
> ${basedir}\folderC
> \folderC
>
> **\**
>
>
>
>
> My POM.xml is packaging type 'pom', and in my base directory I have the
> following file structure:
> basedir --> pom.xml
>--> my_package_format.xml
>--> folderA
>--> folderB
>--> folderC
> Note: I do not have the src directory. I am using this module purely to
> package up DB files to be distributed as a ZIP.
> I have appropriately connected the plugin to the build cycle, however, after
> I perform "mvn package" I am left with 2 things - 1) The correctly produced
> ZIP file and 2) an erroneous empty directory "archive-tmp". I am assuming
> that this folder is normally created to be populated by the appropriate
> contents of the src folder and subsequently packaged in some manner, however,
> since I dont have a src directory it is never getting deleted.
> Any more information required then please let me know.
> Matt
--
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: (MRELEASE-378) Check snapshots phase ignores plugin dependencies
Check snapshots phase ignores plugin dependencies
-
Key: MRELEASE-378
URL: http://jira.codehaus.org/browse/MRELEASE-378
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-7
Reporter: Mark Hobson
The check snapshots phase ignores snapshot plugin dependencies and the project
can be released. For example:
{noformat}
...
myPluginGroup
myPluginArtifact
myGroup
myArtifact
1.0-SNAPSHOT
...
{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] Commented: (MRELEASE-273) Regression: NullPointerException at end of standalone "release:perform"
[
http://jira.codehaus.org/browse/MRELEASE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146978#action_146978
]
Guillaume Jeudy commented on MRELEASE-273:
--
the issue occurs when you run "mvn release:perform
-DconnectionUrl=scm:svn:." in a directory WITH a pom as well.
> Regression: NullPointerException at end of standalone "release:perform"
> ---
>
> Key: MRELEASE-273
> URL: http://jira.codehaus.org/browse/MRELEASE-273
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
> Environment: Maven 2.0.7, maven-release-plugin 2.0-alpha-6
>Reporter: Max Bowsher
>Priority: Blocker
> Attachments: release.bug
>
>
> I executed "mvn release:perform -DconnectionUrl=scm:svn:..". The actual
> performing succeeded, but then the plugin failed with a NullPointerException
> - it seems that the plugin attempts to unconditionally run code analogous to
> "mvn release:clean", but this is inappropriate because release:perform is not
> supposed to require a project to be able to run.
> Output:
> {noformat}
> [INFO]
>
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
> [INFO] Total time: 28 seconds
> [INFO] Finished at: Thu Aug 02 12:53:49 BST 2007
> [INFO] Final Memory: 13M/23M
> [INFO]
>
> [INFO] Cleaning up after release...
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [DEBUG] Trace
> java.lang.NullPointerException
> at
> org.apache.maven.shared.release.util.ReleaseUtil.getReleasePom(ReleaseUtil.java:73)
> at
> org.apache.maven.shared.release.util.ReleaseUtil.getStandardPom(ReleaseUtil.java:61)
> at
> org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.getPomBackup(AbstractBackupPomsPhase.java:37)
> at
> org.apache.maven.shared.release.phase.AbstractBackupPomsPhase.deletePomBackup(AbstractBackupPomsPhase.java:51)
> at
> org.apache.maven.shared.release.phase.CreateBackupPomsPhase.clean(CreateBackupPomsPhase.java:70)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.clean(DefaultReleaseManager.java:427)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:324)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:267)
> at
> org.apache.maven.shared.release.DefaultReleaseManager.perform(DefaultReleaseManager.java:260)
> at
> org.apache.maven.plugins.release.PerformReleaseMojo.execute(PerformReleaseMojo.java:102)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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)
> [INFO]
>
> [INFO] Total ti
[jira] Closed: (MAVENUPLOAD-2179) Upload Stripes-1.5 to Maven Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2179. --- Assignee: Carlos Sanchez Resolution: Fixed > Upload Stripes-1.5 to Maven Repository > -- > > Key: MAVENUPLOAD-2179 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2179 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Tim Fennell >Assignee: Carlos Sanchez > > Could you please upload the stripes-1.5 bundle to the public maven > repository. Thank! -- 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-2185) Update JUnit to 4.5
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed MAVENUPLOAD-2185. --- Assignee: Carlos Sanchez Resolution: Fixed added junit and junit-dep 4.5 > Update JUnit to 4.5 > --- > > Key: MAVENUPLOAD-2185 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2185 > Project: Maven Upload Requests > Issue Type: Improvement >Reporter: Benjamin Reed >Assignee: Carlos Sanchez > > JUnit 4.5 was released on 2008/08/08 -- is it possible to get it upgraded in > the maven repo? > The previous release appears to have a rather sordid history: > http://jira.codehaus.org/browse/MAVENUPLOAD-1651 > I don't want to open up a can of worms, just would like to update to the > latest if 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] Created: (MCLEAN-37) Make verbose mode default to Maven's global debug mode
Make verbose mode default to Maven's global debug mode -- Key: MCLEAN-37 URL: http://jira.codehaus.org/browse/MCLEAN-37 Project: Maven 2.x Clean Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Benjamin Bentmann Priority: Minor If a user specifies "-X" on the command line, the intention is to get debug output. The plugin should respect this, too. -- 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: (MCLEAN-37) Make verbose mode default to Maven's global debug mode
[ http://jira.codehaus.org/browse/MCLEAN-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MCLEAN-37. --- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.3 Done in [r692102|http://svn.apache.org/viewvc?view=rev&revision=692102]. > Make verbose mode default to Maven's global debug mode > -- > > Key: MCLEAN-37 > URL: http://jira.codehaus.org/browse/MCLEAN-37 > Project: Maven 2.x Clean Plugin > Issue Type: Improvement >Affects Versions: 2.2 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.3 > > > If a user specifies "-X" on the command line, the intention is to get debug > output. The plugin should respect this, too. -- 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: (MPIR-138) Complet Polish translation
Complet Polish translation -- Key: MPIR-138 URL: http://jira.codehaus.org/browse/MPIR-138 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Environment: ALL Reporter: Bartlomiej Kuczynski Priority: Trivial Attachments: project-info-report_pl.properties I make complete Polish translation of project-info-report.properties, but when I compile and install plug-in I local repository and I try to use it with Polish locales I got only English communicates and messages on sides. Could someone check this file (in attachment). -- 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: (MASSEMBLY-342) NPE when filtering fileSet
[
http://jira.codehaus.org/browse/MASSEMBLY-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MASSEMBLY-342.
Resolution: Fixed
applied, thanks.
> NPE when filtering fileSet
> --
>
> Key: MASSEMBLY-342
> URL: http://jira.codehaus.org/browse/MASSEMBLY-342
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Environment: Windows XP, cygwin, Java 1.5.0.9
>Reporter: Peter Verhás
>Assignee: John Casey
>Priority: Critical
> Fix For: 2.2-beta-3
>
> Attachments: massembly-342.txt, massembly-342.zip
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> I get NPE when I specify filtering in an assembly descriptor. The
> {{src/assembly/bin.xml}} file (referenced by the {{pom.xml}} as an assembly
> descriptor) is the following:
> {code}
>
> bin
>
> zip
>
> false
>
>
> lib
>
>
>
>
> target
>
>
> *.jar
>
>
>
> true
>
> INSTALL*
> README*
> LICENSE*
> NOTICE*
>
>
>
>
> {code}
> This causes
> {code}
> $ mvn -e assembly:assembly
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'assembly'.
> [INFO]
>
> [INFO] Building Unnamed - verhas.com:isoapui8583:jar:1.0.0
> [INFO]task-segment: [assembly:assembly] (aggregator-style)
> [INFO]
>
> [INFO] Preparing assembly:assembly
> [INFO]
>
> [INFO] Building Unnamed - verhas.com:isoapui8583:jar:1.0.0
> [INFO]
>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> Downloading:
> http://repo1.maven.org/maven2/xmlbeans/xbean/2.3.0-trunk-patched/xbean-2.3.0-trunk-patched.pom
> Downloading:
> http://repo1.maven.org/maven2/groovy/groovy-all/1.5.2/groovy-all-1.5.2.pom
> Downloading:
> http://repo1.maven.org/maven2/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.pom
> Downloading:
> http://repo1.maven.org/maven2/cweb-extser/cweb-extser/0.1-b2-dev/cweb-extser-0.1-b2-dev.pom
> Downloading:
> http://repo1.maven.org/maven2/jPOS/jpos/1.6.2-r2626/jpos-1.6.2-r2626.pom
> [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] Nothing to compile - all classes are up to date
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\surefire-reports
> ---
> T E S T S
> ---
> Running com.verhas.soapui.jpos.TestServer
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec
> Running com.verhas.soapui.jpos.TestClient
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.047 sec
> Running com.verhas.soapui.jpos.TestClientServer
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> Running com.verhas.soapui.jpos.TestConstants
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] [jar:jar]
> [INFO] Building jar:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\isoapui8583-1.0.0.jar
> [INFO] [assembly:assembly]
> [INFO] Reading assembly descriptor: src/assembly/doc.xml
> [INFO] Reading assembly descriptor: src/assembly/bin.xml
> [INFO] Reading assembly descriptor: src/assembly/src.xml
> [INFO] Building zip:
> p:\projects\BASE24-soapui\BICISO-SOAPUI\target\isoapui8583-1.0.0-doc.zip
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at java.io.File.(File.java:222)
> at
> org.apache.maven.shared.model.fileset.util.FileSetManager.scan(FileSetManager.java:598)
> at
> org.apache.maven.shared.model.fileset.u
[jira] Commented: (MENFORCER-50) Version rule with dashes are not inspected correctly
[ http://jira.codehaus.org/browse/MENFORCER-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147010#action_147010 ] Brian Fox commented on MENFORCER-50: There are proposals already to handle updating the syntax, as well as the ongoing work for Maven 3.0 to use Mercury. > Version rule with dashes are not inspected correctly > > > Key: MENFORCER-50 > URL: http://jira.codehaus.org/browse/MENFORCER-50 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Paul Benedict >Assignee: Brian Fox > > I know it's possible to say [2.0,) for anything within the 2.0 series. > The same was not possible with the latest Maven 2.1 release: > [2.1.0-M1,) does not pass for version 2.1.0-M1-RC12 > I should be accepting anything within the M1 build range. -- 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: (MDEP-180) Copy-dependencies useRepositoryLayout doesn't match with maven layout
[ http://jira.codehaus.org/browse/MDEP-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marvin Froeder updated MDEP-180: Attachment: dependency.patch > Copy-dependencies useRepositoryLayout doesn't match with maven layout > - > > Key: MDEP-180 > URL: http://jira.codehaus.org/browse/MDEP-180 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 >Reporter: Marvin Froeder >Assignee: Brian Fox > Attachments: dependency.patch > > > When I'm using useRepositoryLayout is a small issue on version folders: > Folder should be called 0.3.0-SNAPSHOT > Instead of the folder is created as 0.3.0-20080903.153705-125 > And on artifacts names: > Artifact should be called > maven-osgi-compiler-plugin-0.3.0-20080904.004710-136.jar > Instead of maven-osgi-compiler-plugin-0.3.0-SNAPSHOT.jar -- 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-352) warning is misleading
warning is misleading - Key: MASSEMBLY-352 URL: http://jira.codehaus.org/browse/MASSEMBLY-352 Project: Maven 2.x Assembly Plugin Issue Type: Bug Reporter: Brian Fox [WARNING] Configuration options: 'appendAssemblyId' is set to false, and 'classifier' is missing. Instead of attaching the assembly file: D:\svn\Maven\enforcer\enforcer-api\src\site\resources\custom-rule.zip. zip, it will become the file for main project artifact. NOTE: If multiple descriptors or descriptor-formats are provided for this project, the value of this file will be non-deterministic! I'm not using attached (tried with assembly and single goals) so i don't need this warning. I could see it being usefull for goals that attach but not for others. -- 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: (MNGSITE-66) Bad link on the intro to repositories page
Bad link on the intro to repositories page -- Key: MNGSITE-66 URL: http://jira.codehaus.org/browse/MNGSITE-66 Project: Maven 2 Project Web Site Issue Type: Bug Reporter: Eric Haszlakiewicz Priority: Minor On the page: http://maven.apache.org/guides/introduction/introduction-to-repositories.html The "The Hype About Repository Managers" link at the bottom of the page points at: http://www.devzuz.org/blogs/oching/2007/11/05/119423340.html when it should point at this instead: http://blogs.exist.com/oching/2007/11/05/the-hype-about-repository-managers/ -- 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: (MDEP-180) Copy-dependencies useRepositoryLayout doesn't match with maven layout
[ http://jira.codehaus.org/browse/MDEP-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-180. -- Resolution: Fixed Fix Version/s: 2.1 > Copy-dependencies useRepositoryLayout doesn't match with maven layout > - > > Key: MDEP-180 > URL: http://jira.codehaus.org/browse/MDEP-180 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug > Components: copy-dependencies >Affects Versions: 2.0 >Reporter: Marvin Froeder >Assignee: Brian Fox > Fix For: 2.1 > > Attachments: dependency.patch > > > When I'm using useRepositoryLayout is a small issue on version folders: > Folder should be called 0.3.0-SNAPSHOT > Instead of the folder is created as 0.3.0-20080903.153705-125 > And on artifacts names: > Artifact should be called > maven-osgi-compiler-plugin-0.3.0-20080904.004710-136.jar > Instead of maven-osgi-compiler-plugin-0.3.0-SNAPSHOT.jar -- 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: (MASSEMBLY-293) not filtered in multimodule build, but are
[ http://jira.codehaus.org/browse/MASSEMBLY-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MASSEMBLY-293 started by John Casey. > not filtered in multimodule build, but are > - > > Key: MASSEMBLY-293 > URL: http://jira.codehaus.org/browse/MASSEMBLY-293 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-2 > Environment: Windows XP >Reporter: Torsten Reinhard >Assignee: John Casey > Fix For: 2.2-beta-3 > > Attachments: install.xml, update-db2.sh > > > Filtering doesn´t work in a multimodule build if I use instead of > - if I build the module separately, it works > Shouldn´t the behaviour be the same? I have not looked into the code, but I > expect one thing is collection the files (however the filelist is expressed), > the other is filtering them. It seems, as the separation of functionality is > mixed in here? > See the attached file(s) as example. -- 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-3743) pluginManagement not consulted when building from lifecycle forked via javdoc reports
pluginManagement not consulted when building from lifecycle forked via javdoc reports - Key: MNG-3743 URL: http://jira.codehaus.org/browse/MNG-3743 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.1.0-M1 Reporter: John Casey Priority: Blocker Fix For: 2.1.0-M1 if you use java5 generics or java 1.4 assertions, and you have the compiler plugin configured with source and target parameters inside a plugin entry in the pluginManagement section of the POM, this configuration is not used when building from a forked lifecycle spawned from a report. The classic example here is the javadoc reports, which trigger the compilation of sources (for some reason). -- 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-3743) pluginManagement not consulted when building from lifecycle forked via javdoc reports
[ http://jira.codehaus.org/browse/MNG-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3743: Assignee: John Casey Fix Version/s: 2.1.0-M1 > pluginManagement not consulted when building from lifecycle forked via javdoc > reports > - > > Key: MNG-3743 > URL: http://jira.codehaus.org/browse/MNG-3743 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > Fix For: 2.1.0-M1 > > > if you use java5 generics or java 1.4 assertions, and you have the compiler > plugin configured with source and target parameters inside a plugin entry in > the pluginManagement section of the POM, this configuration is not used when > building from a forked lifecycle spawned from a report. The classic example > here is the javadoc reports, which trigger the compilation of sources (for > some reason). -- 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-3743) pluginManagement not consulted when building from lifecycle forked via javdoc reports
[ http://jira.codehaus.org/browse/MNG-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3743 started by John Casey. > pluginManagement not consulted when building from lifecycle forked via javdoc > reports > - > > Key: MNG-3743 > URL: http://jira.codehaus.org/browse/MNG-3743 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > Fix For: 2.1.0-M1 > > > if you use java5 generics or java 1.4 assertions, and you have the compiler > plugin configured with source and target parameters inside a plugin entry in > the pluginManagement section of the POM, this configuration is not used when > building from a forked lifecycle spawned from a report. The classic example > here is the javadoc reports, which trigger the compilation of sources (for > some reason). -- 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-3743) pluginManagement not consulted when building from lifecycle forked via javdoc reports
[ http://jira.codehaus.org/browse/MNG-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147034#action_147034 ] John Casey commented on MNG-3743: - ok, the reason this is triggering compilation is because javadoc:test-aggregate forks to generate-test-sources, which is later than the compile lifecycle phase. > pluginManagement not consulted when building from lifecycle forked via javdoc > reports > - > > Key: MNG-3743 > URL: http://jira.codehaus.org/browse/MNG-3743 > Project: Maven 2 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.1.0-M1 >Reporter: John Casey >Assignee: John Casey >Priority: Blocker > Fix For: 2.1.0-M1 > > > if you use java5 generics or java 1.4 assertions, and you have the compiler > plugin configured with source and target parameters inside a plugin entry in > the pluginManagement section of the POM, this configuration is not used when > building from a forked lifecycle spawned from a report. The classic example > here is the javadoc reports, which trigger the compilation of sources (for > some reason). -- 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: (MPIR-133) OutOfMemort when generating site
[ http://jira.codehaus.org/browse/MPIR-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147035#action_147035 ] Bartlomiej Kuczynski commented on MPIR-133: --- NOT A BUG. Try add to ~/.bashrc: export MAVEN_OPTS="-Xmx1024m -Xms512m" There are the same options like in JVM (maven add this option when start JVM). It should help. > OutOfMemort when generating site > > > Key: MPIR-133 > URL: http://jira.codehaus.org/browse/MPIR-133 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: redhat linux, jdk 1.5, maven 2.0.9 >Reporter: Lars Vonk > > Following exception occurs when running "mvn clean site" on project info > reports plugin. > 18-Aug-2008 14:49:04 [INFO] > > 18-Aug-2008 14:49:04 [ERROR] FATAL ERROR > 18-Aug-2008 14:49:04 [INFO] > > 18-Aug-2008 14:49:04 [INFO] Java heap space > 18-Aug-2008 14:49:04 [INFO] > > 18-Aug-2008 14:49:04 [DEBUG] Trace > 18-Aug-2008 14:49:04 java.lang.OutOfMemoryError: Java heap space > 18-Aug-2008 14:49:04 at java.util.zip.ZipEntry.initFields(Native > Method) > 18-Aug-2008 14:49:04 at > java.util.zip.ZipEntry.(ZipEntry.java:100) > 18-Aug-2008 14:49:04 at > java.util.zip.ZipFile$3.nextElement(ZipFile.java:437) > 18-Aug-2008 14:49:04 at > java.util.zip.ZipFile$3.nextElement(ZipFile.java:415) > 18-Aug-2008 14:49:04 at > java.util.jar.JarFile$1.nextElement(JarFile.java:221) > 18-Aug-2008 14:49:04 at > java.util.jar.JarFile$1.nextElement(JarFile.java:220) > 18-Aug-2008 14:49:04 at > java.util.Collections.list(Collections.java:3406) > 18-Aug-2008 14:49:04 at > org.apache.maven.shared.jar.JarAnalyzer.(JarAnalyzer.java:105) > 18-Aug-2008 14:49:04 at > org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDependencyDetails(Dependencies.java:282) > 18-Aug-2008 14:49:04 at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.hasSealed(DependenciesRenderer.java:1278) > 18-Aug-2008 14:49:04 at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyFileDetails(DependenciesRenderer.java:423) > 18-Aug-2008 14:49:04 at > org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody(DependenciesRenderer.java:268) > This only occurs with 2.1, using 2.0.1 explicitly works fine. I increased the > Xmx to 1024m, but the problem persists. -- 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: (MSITE-340) use ${project.reporting.outputEncoding} as default value for "outputEncoding" parameter and default to UTF-8
[
http://jira.codehaus.org/browse/MSITE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSITE-340.
---
Assignee: Herve Boutemy
Resolution: Fixed
Fix Version/s: 2.0-beta-8
done in r692259
> use ${project.reporting.outputEncoding} as default value for "outputEncoding"
> parameter and default to UTF-8
>
>
> Key: MSITE-340
> URL: http://jira.codehaus.org/browse/MSITE-340
> Project: Maven 2.x Site Plugin
> Issue Type: New Feature
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
> Fix For: 2.0-beta-8
>
>
> see [Reporting Encoding
> Configuration|http://docs.codehaus.org/display/MAVEN/Reporting+Encoding+Configuration]
> proposal
--
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: (MDEPLOY-48) deploy:deploy-file does not support deploying sources jars too
[ http://jira.codehaus.org/browse/MDEPLOY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147047#action_147047 ] Philip Schlesinger commented on MDEPLOY-48: --- Someone please fix this. We could really use this. > deploy:deploy-file does not support deploying sources jars too > -- > > Key: MDEPLOY-48 > URL: http://jira.codehaus.org/browse/MDEPLOY-48 > Project: Maven 2.x Deploy Plugin > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Geoffrey De Smet > > deploy:deploy does, but deploy:deploy-file doesn't have a parameter to tell > him where the sources jar is: > mvn deploy:deploy-file -Dfile=$artifactFile -DpomFile=$pomFile -Durl=$toRepo -- 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
