[jira] Created: (MAVENUPLOAD-2518) netbeans ant tasks for creating netbeans modules (as shipped with netbeans 6.7)
netbeans ant tasks for creating netbeans modules (as shipped with netbeans 6.7) --- Key: MAVENUPLOAD-2518 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2518 Project: Maven Upload Requests Issue Type: Wish Reporter: Milos Kleint Attachments: tasks67.jar netbeans ant tasks to create netbeans modules. the jar is coming straight from the netbeans binary download of NetBeans 6.0 FCS. The jar is located at netbeans/harness/tasks.jar in the binary distro. It's required by the nbm-maven-plugin from codehaus.org released under dual license CDDL 1.0 + GPL 2.0 with classpath exception I'm technically not a developer of the ant tasks, but I'm a Netbeans.org contributor for 8 years , employed by Sun Microsystems. -- 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-2517) jsch-0.1.42
jsch-0.1.42 --- Key: MAVENUPLOAD-2517 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2517 Project: Maven Upload Requests Issue Type: Task Reporter: Joerg Schaible JSch is a pure Java implementation of SSH2. Version bump. -- 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: (MSHADE-18) Configure META-INF/MANIFEST.MF
[ http://jira.codehaus.org/browse/MSHADE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183493#action_183493 ] Alexander Wagner commented on MSHADE-18: nice work > Configure META-INF/MANIFEST.MF > -- > > Key: MSHADE-18 > URL: http://jira.codehaus.org/browse/MSHADE-18 > Project: Maven 2.x Shade Plugin > Issue Type: Task >Affects Versions: 1.0-beta-1 >Reporter: Alexander Wagner >Assignee: Herve Boutemy > Fix For: 1.0 > > > Creating a possibility to configuring the manifest file for e.g. main-class > Maybe like this: http://maven.apache.org/guides/mini/guide-manifest.html -- 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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183497#action_183497 ] Jean-Marc Borer commented on MNG-4228: -- So if I understand well: lightweight wagon is based on Sun's Java implementation and http wagon is based on Apache's HttpClient lib, right? Anyway Artifactory (http://www.jfrog.org/products.php) uses plain vanilla httpclient lib version 3 and is able to access the internet through our NTLM corporate proxy. Why is then wagon no able to do that? I was able my self to build a small example with httpclient 3 that works fine... Great that at least the previous behavior of maven is restored. When is 2.2.1 planned to be released? > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183499#action_183499 ] Oleg Kalnichevski commented on MNG-4228: @Jean-Marc There are several versions of the NTLM authentication scheme [1]. HttpClient 3.x _partially_ supports only what is known as NTLMv1. Depending on the version of the ISA proxy and its configuration this may or may not be sufficient. Oleg [1] http://en.wikipedia.org/wiki/NTLM > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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: (MJAVADOC-238) No timeout set for URLConnection which can cause build to get stuck
[ http://jira.codehaus.org/browse/MJAVADOC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183501#action_183501 ] Vincent Siveton commented on MJAVADOC-238: -- Fixed in [r793854|http://svn.apache.org/viewvc?rev=793854&view=rev], snapshot deployed Please test it so I could close it. > No timeout set for URLConnection which can cause build to get stuck > --- > > Key: MJAVADOC-238 > URL: http://jira.codehaus.org/browse/MJAVADOC-238 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Bugittaa Pahasti > > I encountered a release build getting stuck. Stack trace revealed that the > culprit was an infinite default timeout in URLConnection. > [INFO]at java.net.URL.openStream(URL.java:1007) > [INFO]at > org.apache.maven.plugin.javadoc.JavadocUtil.fetchURL(JavadocUtil.java:742) > [INFO]at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addLinkArguments(AbstractJavadocMojo.java:2982) > [INFO]at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addStandardDocletOptions(AbstractJavadocMojo.java:3667) > [INFO]at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1548) > [INFO]at > org.apache.maven.plugin.javadoc.JavadocJar.execute(JavadocJar.java:182) > [INFO]at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > The simple fix is to call setConnectTimeout and setReadTimeout with some > sensible default value (jdk 1.5 methods, so might need to use reflection to > preseve jdk 1.4 compatibility). -- 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: (MECLIPSE-569) eclipse:eclipse does not add all libraries to .classpath
[ http://jira.codehaus.org/browse/MECLIPSE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183503#action_183503 ] Peter Horlock commented on MECLIPSE-569: - Eclipse plugin 2.7 is affected too! :-( > eclipse:eclipse does not add all libraries to .classpath > > > Key: MECLIPSE-569 > URL: http://jira.codehaus.org/browse/MECLIPSE-569 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath) >Affects Versions: 2.6 > Environment: Ubuntu 9.04, sun java 1.6, maven 2.1.0 and maven 2.0.9 >Reporter: Armands Graube > Attachments: pom.xml > > > Maven eclipse plugin 2.6 does not add aspectj:aspectjtools:1.5.3 library > entries to .classpath file, could not reproduce with other libraries. When > changed back to eclipse plugin 2.5, .classpath contains alll the correct > entries. Not sure, maybe this has to do something with the specific library? > Attached sample pom.xml where you get the library added to .classpath if > uncommented version 2.5 and not add if uncommented version 2.6 -- 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: (MJAVADOC-229) javadoc:javadoc goal fails with Maven 2.0.10 or 2.1.0, but works with 2.0.9
[
http://jira.codehaus.org/browse/MJAVADOC-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-229.
Resolution: Not A Bug
I tried to call "mvn javadoc:javadoc" on the camel-web project, rev 793860 [1].
I just added the fusesource repo [2] for maven-jaxb-schemagen-plugin and lock
down the javadoc-plugin to 2.5.
I always get the following error with Maven 2.0.9, 2.0.10, 2.1 and 2.2:
{noformat}
[INFO] An error has occurred in JavaDocs report generation:Exit code: 1 -
javadoc: error - invalid flag: -author
{noformat}
It is the correct behaviour and as Peter said, you need to add the
useStandardDocletOptions parameter using specific doclet:
{noformat}
false
{noformat}
[1] http://svn.apache.org/repos/asf/camel/trunk/components/camel-web
[2] http://repo.fusesource.com/maven2/
> javadoc:javadoc goal fails with Maven 2.0.10 or 2.1.0, but works with 2.0.9
> ---
>
> Key: MJAVADOC-229
> URL: http://jira.codehaus.org/browse/MJAVADOC-229
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Mac OS X 10.5.6
> Java 1.5.0_16
> Maven 2.0.10 or 2.1.0
> maven-javadoc-plugin 2.5
>Reporter: Jonathan Harlap
>
> Attempting to use the maven-javadoc-plugin with a pom.xml that works with
> Maven 2.0.9 fails to work with 2.0.10 or 2.1.0. The error message produced
> is:
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 -
> javadoc: error - invalid flag: -author
> The javadoc plugin configuration from the pom.xml is:
> {code:xml}
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
>
>
> javadoc
>
> compile
>
>
>
> UTF-8
> false
> public
> com.sinfoma.sintransfer.rest.services.resources
>
> com.sun.jersey.wadl.resourcedoc.ResourceDoclet
>
>
>
> com.sun.jersey.contribs
> wadl-resourcedoc-doclet
>
> ${jersey-release-version}
>
>
>
>
> com.sun.jersey
> jersey-server
> ${jersey-release-version}
>
>
>
> xerces
> xercesImpl
> 2.9.1
>
>
> -output
> ${project.build.outputDirectory}/resourcedoc.xml
>
>
> {code}
> With the following additional configuration in the active profile:
> {code:xml}
>
> org.apache.maven.plugins
>
> maven-javadoc-plugin
>
>
>
> com.sun.jersey.contribs
>
> maven-wadl-plugin
> ${jersey-release-version}
>
>
>
> com.sun.jersey.contribs
>
> wadl-resourcedoc-doclet
>
> ${jersey-release-version}
>
>
>
>
> com.sun.jersey
> jersey-server
> ${jersey-release-version}
>
>
>
> xerces
> xercesImpl
> 2.9.1
>
>
> javax.xml.bind
> jaxb-api
> 2.1
>
>
> com.sun.xml.bind
> jaxb-impl
> 2.1.10
>
>
> javax.activation
> activation
> 1.1
>
>
> javax.xml.stream
> stax-api
> 1.0
>
>
[jira] Closed: (MJAVADOC-234) plugin fails on Java 6 with version 2.5 but works fine for 2.4
[
http://jira.codehaus.org/browse/MJAVADOC-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-234.
Resolution: Not A Bug
With javadoc-plugin:2.5, you need to add the useStandardDocletOptions parameter
when using a specific doclet. See MJAVADOC-229 for details.
> plugin fails on Java 6 with version 2.5 but works fine for 2.4
> --
>
> Key: MJAVADOC-234
> URL: http://jira.codehaus.org/browse/MJAVADOC-234
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: OS X and Linux on Java 1.6.0, Maven 2.1.0
>Reporter: james strachan
>
> I get this error
> {code}
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 -
> javadoc: error - invalid flag: -bottom
> Command line
> was:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/javadoc
> -J-Xmx500m @options
> {code}
> when running javadoc:javadoc.
> Though using 2.4 it works fine
--
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: (MJAVADOC-237) maven javadoc fails for alternate doclets since maven 2.0.10
[ http://jira.codehaus.org/browse/MJAVADOC-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-237. Resolution: Not A Bug With javadoc-plugin:2.5, you need to add the useStandardDocletOptions parameter when using a specific doclet. See MJAVADOC-229 for details. > maven javadoc fails for alternate doclets since maven 2.0.10 > > > Key: MJAVADOC-237 > URL: http://jira.codehaus.org/browse/MJAVADOC-237 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Sebastian Dietrich > > running mvn site for alternate doclets as described in > http://maven.apache.org/plugins/maven-javadoc-plugin/examples/alternate-doclet.html > fails since 2.0.10 (was working under 2.0.9) > see http://www.nabble.com/Building-camel-failing-td22656916.html -- 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: (MJAVADOC-233) mvn javadoc:javadoc fails if project pom name contains multiple lines
[ http://jira.codehaus.org/browse/MJAVADOC-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-233: - Affects Version/s: (was: 2.5) 2.3 > mvn javadoc:javadoc fails if project pom name contains multiple lines > - > > Key: MJAVADOC-233 > URL: http://jira.codehaus.org/browse/MJAVADOC-233 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: ubuntu 8.10, jdk 6. >Reporter: Pablo Graña > > If the project name in the pom contains a new line (at least a CR LF pair), > mvn javadoc:javadoc fails with this error: > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - Illegal package name: "2.1.1-SNAPSHOT" > javadoc: error - Illegal package name: "" > javadoc: error - Illegal package name: "2.1.1-SNAPSHOT" > javadoc: error - Illegal package name: "" > javadoc: warning - No source files for package b > javadoc: warning - No source files for package API > javadoc: warning - No source files for package b > javadoc: warning - No source files for package API > Command line was:/usr/lib/jvm/java-6-sun-1.6.0.10/jre/../bin/javadoc @options > @packages > This is the relevant pom fragment: > 4.0.0 > a.b > aa > ejb >a > b > > This is the relevant fragment of the target/site/apidocs/options file: > -doctitle > 'a > b 2.1.1-SNAPSHOT API' > -use > -version > -windowtitle > 'a > b 2.1.1-SNAPSHOT API'gpablo > If I remove de line from the project name, it works fine. -- 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: (MJAVADOC-233) mvn javadoc:javadoc fails if project pom name contains multiple lines
[ http://jira.codehaus.org/browse/MJAVADOC-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-233. Resolution: Duplicate It seems that you used 2.3 instead of 2.5. Using 2.4 or more (MJAVADOC-149) should fix your issue. > mvn javadoc:javadoc fails if project pom name contains multiple lines > - > > Key: MJAVADOC-233 > URL: http://jira.codehaus.org/browse/MJAVADOC-233 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.3 > Environment: ubuntu 8.10, jdk 6. >Reporter: Pablo Graña > > If the project name in the pom contains a new line (at least a CR LF pair), > mvn javadoc:javadoc fails with this error: > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 - > javadoc: error - Illegal package name: "2.1.1-SNAPSHOT" > javadoc: error - Illegal package name: "" > javadoc: error - Illegal package name: "2.1.1-SNAPSHOT" > javadoc: error - Illegal package name: "" > javadoc: warning - No source files for package b > javadoc: warning - No source files for package API > javadoc: warning - No source files for package b > javadoc: warning - No source files for package API > Command line was:/usr/lib/jvm/java-6-sun-1.6.0.10/jre/../bin/javadoc @options > @packages > This is the relevant pom fragment: > 4.0.0 > a.b > aa > ejb >a > b > > This is the relevant fragment of the target/site/apidocs/options file: > -doctitle > 'a > b 2.1.1-SNAPSHOT API' > -use > -version > -windowtitle > 'a > b 2.1.1-SNAPSHOT API'gpablo > If I remove de line from the project name, it works fine. -- 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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183511#action_183511 ] Jean-Marc Borer commented on MNG-4228: -- @Oleg I totally agree with you, but: 1) httpclient 3.x works for me out of the box with my proxy 2) maven 2.2.0 fails where maven 2.1.0 succeeds to access the web So I am wondering what is wrong anyway with the lib that wagon uses in maven 2.2.0 since httpclient 3.x works with my proxy? Something is "wronger" than just using another lib... > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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: (MSITE-171) Site plugin uses plain dependencies for reactor projects instead of results of earlier modules
[ http://jira.codehaus.org/browse/MSITE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183512#action_183512 ] Benson Margulies commented on MSITE-171: Isn't this the same problem that causes it to re-fetch all the dependencies over and over, ignoring the local repo? > Site plugin uses plain dependencies for reactor projects instead of results > of earlier modules > -- > > Key: MSITE-171 > URL: http://jira.codehaus.org/browse/MSITE-171 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-5 > Environment: Win XP, Linux >Reporter: Alex Rau > Attachments: install_site_runs.log, site_fails.log, > subsequent_site_runs.log > > > When creating a multi-module site the site plugin uses dependencies from > related modules from the repository instead of using artifacts from the same > execution. > That causes inconsistent reports on the sites. An example: > Project A has modules B and C defined. B is build first and a site for > project B is created. Then project C is build using a dependency either from > the local or remote repository. Therefore the site contains results which > rely on a build with an "out-dated" artifact used as dependency. This leads > to plainly wrong results when examining surefire-reports as Project C should > have been build with the (current) artifact of project B (taken from the same > execution of the site 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] Created: (MNG-4239) NoSuchMethodError org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
NoSuchMethodError
org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
Key: MNG-4239
URL: http://jira.codehaus.org/browse/MNG-4239
Project: Maven 2
Issue Type: Bug
Affects Versions: 3.0-alpha-3
Reporter: Igor Fedorenko
>From m2eclipse-user mailing list
>http://www.nabble.com/m2eclipse-0.9.9-dev-problems-with-Apache-ServiceMix-component-projects-such-as-servicemix-camel-td24475825.html#a24475825
{quote}
I receive the following errors in my eclipse log attempting to use m2eclipse
0.9.9-dev with project
https://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-camel/trunk.
I have tried using the embedded Maven runtime as well as the external Maven
2.2.0 release with no success.
Thoughts?
!ENTRY org.eclipse.core.resources 2 566 2009-07-14 04:17:22.357
!MESSAGE Errors during build.
!SUBENTRY 1 org.maven.ide.eclipse 2 75 2009-07-14 04:17:22.357
!MESSAGE Errors running builder 'Maven Project Builder' on project
'servicemix-camel'.
!SUBENTRY 1 org.maven.ide.eclipse 2 75 2009-07-14 04:17:22.357
!MESSAGE
org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
!STACK 0
java.lang.NoSuchMethodError:
org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.mergeModels(ProcessRemoteResourcesMojo.java:903)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:520)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:322)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:206)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
at
org.maven.ide.eclipse.internal.embedder.MavenImpl.execute(MavenImpl.java:164)
at
org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.executePostBuild(DefaultBuildParticipant.java:138)
at
org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.build(DefaultBuildParticipant.java:77)
at
org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:125)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
at
org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
at org.eclipse.core.internal.resources.Project.build(Project.java:94)
at
org.eclipse.jdt.internal.ui.util.CoreUtility$BuildJob.run(CoreUtility.java:160)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.eclipse.core.jobs 4 2 2009-07-14 04:25:09.719
!MESSAGE An internal error occurred during: "Updating Maven Configuration".
!STACK 0
java.lang.NoSuchMethodError:
org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.mergeModels(ProcessRemoteResourcesMojo.java:903)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:520)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:322)
at
org.apache.maven.lifecycl
[jira] Closed: (MJAVADOC-232) copied doc-files folder contains svn meta files
[ http://jira.codehaus.org/browse/MJAVADOC-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-232. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.6 fixed in [r793901|http://svn.apache.org/viewvc?rev=793901&view=rev], snapshot deployed > copied doc-files folder contains svn meta files > --- > > Key: MJAVADOC-232 > URL: http://jira.codehaus.org/browse/MJAVADOC-232 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.4, 2.5 > Environment: Maven 2.0.10, 2.0.9, XP SP2, Ubuntu 8.04, JDK6 >Reporter: Michael Osipov >Assignee: Vincent Siveton > Fix For: 2.6 > > Attachments: list.txt > > > I have included a png into src/main/javadoc/package/doc-files. Turned the > appropriate switch on. Files lands in the jar, so does SVN meta files. > Reproduce with: > checkout http://svn.fckeditor.net/FCKeditor.Java/trunk/ r3582. > cd java-code > mvn > examine the javadoc jar and navigate to: net/fckeditor/connector/doc-files > I have scanned the source of the javadoc and subsequent plugins and default > excludes for svn are applied. > Check the attached list. -- 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-4239) NoSuchMethodError org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
[
http://jira.codehaus.org/browse/MNG-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4239.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 3.0-alpha-3
Restored API in [r793910|http://svn.apache.org/viewvc?view=rev&revision=793910].
> NoSuchMethodError
> org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
>
>
> Key: MNG-4239
> URL: http://jira.codehaus.org/browse/MNG-4239
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 3.0-alpha-3
>Reporter: Igor Fedorenko
>Assignee: Benjamin Bentmann
> Fix For: 3.0-alpha-3
>
>
> From m2eclipse-user mailing list
> http://www.nabble.com/m2eclipse-0.9.9-dev-problems-with-Apache-ServiceMix-component-projects-such-as-servicemix-camel-td24475825.html#a24475825
> {quote}
> I receive the following errors in my eclipse log attempting to use m2eclipse
> 0.9.9-dev with project
> https://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-camel/trunk.
> I have tried using the embedded Maven runtime as well as the external Maven
> 2.2.0 release with no success.
> Thoughts?
> !ENTRY org.eclipse.core.resources 2 566 2009-07-14 04:17:22.357
> !MESSAGE Errors during build.
> !SUBENTRY 1 org.maven.ide.eclipse 2 75 2009-07-14 04:17:22.357
> !MESSAGE Errors running builder 'Maven Project Builder' on project
> 'servicemix-camel'.
> !SUBENTRY 1 org.maven.ide.eclipse 2 75 2009-07-14 04:17:22.357
> !MESSAGE
> org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
> !STACK 0
> java.lang.NoSuchMethodError:
> org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.mergeModels(ProcessRemoteResourcesMojo.java:903)
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.getProjects(ProcessRemoteResourcesMojo.java:520)
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.configureVelocityContext(ProcessRemoteResourcesMojo.java:665)
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:413)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:322)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:206)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:182)
> at
> org.maven.ide.eclipse.internal.embedder.MavenImpl.execute(MavenImpl.java:164)
> at
> org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.executePostBuild(DefaultBuildParticipant.java:138)
> at
> org.maven.ide.eclipse.internal.project.DefaultBuildParticipant.build(DefaultBuildParticipant.java:77)
> at
> org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:125)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
> at
> org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
> at
> org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
> at org.eclipse.core.internal.resources.Project.build(Project.java:94)
> at
> org.eclipse.jdt.internal.ui.util.CoreUtility$BuildJob.run(CoreUtility.java:160)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.eclipse.core.jobs 4 2 2009-07-14 04:25:09.719
> !MESSAGE An internal error occurred during: "Updating Maven Configuration".
> !STACK 0
> java.lang.NoSuchMethodError:
> org.apache.maven.project.inheritance.ModelInheritanceAssembler.assembleModelInheritance(Lorg/apache/maven/model/Model;Lorg/apache/maven/model/Model;)V
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.mergeModels(ProcessRemoteResourcesM
[jira] Created: (MNG-4240) Direct dependencies with scope == provided will not have their transitive dependencies resolved for compiling and testing
Direct dependencies with scope == provided will not have their transitive dependencies resolved for compiling and testing - Key: MNG-4240 URL: http://jira.codehaus.org/browse/MNG-4240 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.2.0 Reporter: John Casey -- 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-4240) Direct dependencies with scope == provided will not have their transitive dependencies resolved for compiling and testing
[ http://jira.codehaus.org/browse/MNG-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4240: Description: While provided-scoped dependencies should never be passed *forward* from the current artifact (should not be resolved when the declaring project is itself used as a dependency), it is critical that provided scope and its full dependency sub-tree is resolved for compilation and testing. Fix Version/s: 2.2.1 > Direct dependencies with scope == provided will not have their transitive > dependencies resolved for compiling and testing > - > > Key: MNG-4240 > URL: http://jira.codehaus.org/browse/MNG-4240 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.0 >Reporter: John Casey > Fix For: 2.2.1 > > > While provided-scoped dependencies should never be passed *forward* from the > current artifact (should not be resolved when the declaring project is itself > used as a dependency), it is critical that provided scope and its full > dependency sub-tree is resolved for compilation and testing. -- 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: (MJAVADOC-232) copied doc-files folder contains svn meta files
[ http://jira.codehaus.org/browse/MJAVADOC-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183538#action_183538 ] Michael Osipov commented on MJAVADOC-232: - Works great, thanks for the patch! > copied doc-files folder contains svn meta files > --- > > Key: MJAVADOC-232 > URL: http://jira.codehaus.org/browse/MJAVADOC-232 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.4, 2.5 > Environment: Maven 2.0.10, 2.0.9, XP SP2, Ubuntu 8.04, JDK6 >Reporter: Michael Osipov >Assignee: Vincent Siveton > Fix For: 2.6 > > Attachments: list.txt > > > I have included a png into src/main/javadoc/package/doc-files. Turned the > appropriate switch on. Files lands in the jar, so does SVN meta files. > Reproduce with: > checkout http://svn.fckeditor.net/FCKeditor.Java/trunk/ r3582. > cd java-code > mvn > examine the javadoc jar and navigate to: net/fckeditor/connector/doc-files > I have scanned the source of the javadoc and subsequent plugins and default > excludes for svn are applied. > Check the attached list. -- 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-2457) Maven Config Processor 1.6 Upload Request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183539#action_183539 ] Leandro commented on MAVENUPLOAD-2457: -- I'm deploying to Sonatype OSS Repository (https://docs.sonatype.com/display/NX/OSS+Repository+Hosting), this issue can be closed now. Thank you > Maven Config Processor 1.6 Upload Request > - > > Key: MAVENUPLOAD-2457 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2457 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Leandro > > Hi, I'm leader developer of the Maven Config Processor Plugin and would like > to upload the version 1.6 of the plugin to the Maven Central Repository. > Thanks -- 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-4240) Direct dependencies with scope == provided will not have their transitive dependencies resolved for compiling and testing
[ http://jira.codehaus.org/browse/MNG-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183540#action_183540 ] John Casey commented on MNG-4240: - The big issue here that needs verification and/or fixing is that when a direct dependency is marked scope == provided, the transitive dependencies *below* that provided-scope dependency still need to be resolved for the purposes of testing. For example, assume I'm developing an extension for Maven and I declare a direct dependency on maven-core with scope == provided. My real interest in maven-core is DefaultMaven, to be used to spawn separate, second-level builds (I know, there are many many _other_ reasons this might not work, but just go with it). In this case, maven-core has a dependency on maven-project which is critical. DefaultMaven depends on DefaultMavenProjectBuilder to read POMs and return MavenProject instances. If I create unit tests that attempt to execute my extension class, those unit tests will require the maven-project artifact (along with many others) to be present before a valid runtime environment for the unit test can be created. If maven-project is excluded from dependency resolution, the unit test will fail with a NoClassDefFoundError. The place where a problem could arise in all of this is when/if my direct dependency with provided scope itself declares a dependency with scope == provided. Surefire most likely cannot create a valid runtime environment in this case unless it traverses *every* provided- and non-provided-scope dependency. Since the code makes the assumption that those provided-scope dependencies will be present at runtime, the calculation for creating that runtime environment for the purposes of unit testing may become very difficult. > Direct dependencies with scope == provided will not have their transitive > dependencies resolved for compiling and testing > - > > Key: MNG-4240 > URL: http://jira.codehaus.org/browse/MNG-4240 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.0 >Reporter: John Casey > Fix For: 2.2.1 > > > While provided-scoped dependencies should never be passed *forward* from the > current artifact (should not be resolved when the declaring project is itself > used as a dependency), it is critical that provided scope and its full > dependency sub-tree is resolved for compilation and testing. -- 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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MNG-4228: - Follow up with the discussion in this issue related to NTLMv2 code in httpclient... > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183542#action_183542 ] John Casey commented on MNG-4228: - @Jean-Marc Maybe you can provide us with some of this miracle code, then? We're always looking for good patches... Maven 2.1.0 did *not* use the httpclient-driven wagon; it uses the Sun implementation. Also, Artifactory may have different licensing requirements than Maven, which may allow them to use code derived from jCIFS that is known to support NTLMv2 according to some other threads I've read. A big part of the problem here is that I don't have access to an NTLMv2 proxy for testing, nor would I really know whether/how I could set one up on a VirtualBox/VMWare appliance for testing. This is the root problem when dealing with proxy issues, since there are a million flavors and they all seem to have different quirks. Are you sure you're behind an NTLM *v2* proxy, or is it just v1? We're just using httpclient, there are no tricks or hacks. We have a client instance initialized inside the HttpWagon (actually, AbstractHttpWagon, IIRC) and it's used in the same manner as I've ever seen httpclient used anywhere. There's nothing special about it, but we may not have exactly the same configuration code as you do. So, I could use a look at your working example, to compare notes. BTW, I'll start trying to release Maven 2.2.1 as soon as our issue count hits zero for this version. As time goes on, we may shift some issues out to 2.2.2 or 2.3, and we may discover some new regressions that need addressing before the release. But in any case, I'm working as hard as I can to get this release done ASAP. As always, users can help out immensely by providing sample code and failing test cases that can be used to create integration tests. > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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: (MSHARED-106) Update to Doxia 1.0
[ http://jira.codehaus.org/browse/MSHARED-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSHARED-106. --- Assignee: Herve Boutemy Resolution: Fixed Fix Version/s: maven-reporting-impl 2.0.5 Fixed in r770986. > Update to Doxia 1.0 > --- > > Key: MSHARED-106 > URL: http://jira.codehaus.org/browse/MSHARED-106 > Project: Maven Shared Components > Issue Type: Task > Components: maven-reporting-impl >Affects Versions: maven-reporting-impl 2.0.4.1 >Reporter: Dennis Lundberg >Assignee: Herve Boutemy > Fix For: maven-reporting-impl 2.0.5 > > -- 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: (MSHARED-106) Update to Doxia 1.0
Update to Doxia 1.0 --- Key: MSHARED-106 URL: http://jira.codehaus.org/browse/MSHARED-106 Project: Maven Shared Components Issue Type: Task Components: maven-reporting-impl Affects Versions: maven-reporting-impl 2.0.4.1 Reporter: Dennis Lundberg -- 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: (MSHARED-107) Update to Doxia 1.1.1
Update to Doxia 1.1.1 - Key: MSHARED-107 URL: http://jira.codehaus.org/browse/MSHARED-107 Project: Maven Shared Components Issue Type: Task Components: maven-reporting-impl Affects Versions: maven-reporting-impl 2.0.5 Reporter: Dennis Lundberg -- 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: (MSHARED-107) Update to Doxia 1.1.1
[ http://jira.codehaus.org/browse/MSHARED-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MSHARED-107. --- Assignee: Dennis Lundberg Resolution: Fixed Fix Version/s: maven-reporting-impl 2.1 > Update to Doxia 1.1.1 > - > > Key: MSHARED-107 > URL: http://jira.codehaus.org/browse/MSHARED-107 > Project: Maven Shared Components > Issue Type: Task > Components: maven-reporting-impl >Affects Versions: maven-reporting-impl 2.0.4.2 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: maven-reporting-impl 2.1 > > -- 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: (MSITE-409) Incorrect URLs in multi-module project
[ http://jira.codehaus.org/browse/MSITE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183556#action_183556 ] Benson Margulies commented on MSITE-409: The proposed fix doesn't do the job. The code still tries to follow the project hierarchy. > Incorrect URLs in multi-module project > -- > > Key: MSITE-409 > URL: http://jira.codehaus.org/browse/MSITE-409 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0 >Reporter: Benson Margulies > Attachments: tc.patch.diff > > > I have a top-level pom and some modules. One of the modules serves as a > parent for most, but not all, of the rest. > Thus, for most, the parent is ../parent, and for that the parent is the > top-level project itself. > I ran: > mvn site:stage -DstagingDirectory=/Users/benson/stage > It takes a very long time. > All of my child links came out incorrectly: e.g: > href="../../Users/benson/x/trunk/greenhouse/etrog/../../../../hudson.basistech.net/home/projects/etrog">RLPJ > Buildtools > There aren't distinct subdirectories in the staged dir for those of my > modules that use the parent. Actually, now that I look, I see that the ones > that parent into ../parent are subdirectories of 'parent' instead of > subdirectories of the top-level. But the links are still all wrong. -- 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: (MSITE-409) Incorrect URLs in multi-module project
[ http://jira.codehaus.org/browse/MSITE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies updated MSITE-409: --- Attachment: tc.patch.diff Here is a test case. > Incorrect URLs in multi-module project > -- > > Key: MSITE-409 > URL: http://jira.codehaus.org/browse/MSITE-409 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: multi module >Affects Versions: 2.0 >Reporter: Benson Margulies > Attachments: tc.patch.diff > > > I have a top-level pom and some modules. One of the modules serves as a > parent for most, but not all, of the rest. > Thus, for most, the parent is ../parent, and for that the parent is the > top-level project itself. > I ran: > mvn site:stage -DstagingDirectory=/Users/benson/stage > It takes a very long time. > All of my child links came out incorrectly: e.g: > href="../../Users/benson/x/trunk/greenhouse/etrog/../../../../hudson.basistech.net/home/projects/etrog">RLPJ > Buildtools > There aren't distinct subdirectories in the staged dir for those of my > modules that use the parent. Actually, now that I look, I see that the ones > that parent into ../parent are subdirectories of 'parent' instead of > subdirectories of the top-level. But the links are still all wrong. -- 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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183565#action_183565 ] Oleg Kalnichevski commented on MNG-4228: > Follow up with the discussion in this issue related to NTLMv2 code in > httpclient... No, it is NOT. This has _nothing_ to do with HttpClient. SUN _licensed_ the NTLM protocol from Microsoft, the luxury we obviously do not have. Besides, they make use of native code accessing native Windows APIs somewhere in their NTLM implementation, which makes NTLM auth in JRE HTTP Windows only. HttpClient 4.0 supports NTLMv2 through JCIFS on all platforms. Unfortunately due to licensing issues we cannot ship or even import JCIFS code. This is a purely licensing issue and it has nothing to do with HttpClient. This is the reason why the use of NTLM is strongly discouraged. Oleg > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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-436) assembly id not available as property for filtering
assembly id not available as property for filtering
---
Key: MASSEMBLY-436
URL: http://jira.codehaus.org/browse/MASSEMBLY-436
Project: Maven 2.x Assembly Plugin
Issue Type: Improvement
Affects Versions: 2.2-beta-4
Environment: all
Reporter: Bjorn
I'm building a project for multiple platforms (using multiple assembly
descriptors) and need the assembly information (for example one of my
assemblies is called "gtk-linux-x86_64") in the deployment package. Preferably
by resource filtering. This information is available in my descriptors as the
assembly id. Unfortunately this id is not accessible.
Besides resource filtering the assembly id could also be used in the descriptor
itself and could reduce duplication of information.
Example where ID is used as a platform classifier:
gtk-linux-x86_64
dir
/lib
org.eclipse:org.eclipse.swt:jar:${assembly.id}
--
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-164) Complete the German translation
Complete the German translation --- Key: MPIR-164 URL: http://jira.codehaus.org/browse/MPIR-164 Project: Maven 2.x Project Info Reports Plugin Issue Type: Task Affects Versions: 2.1.1 Reporter: Dennis Lundberg The German translation is missing 30 property keys. -- 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-164) Complete the German translation
[ http://jira.codehaus.org/browse/MPIR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183566#action_183566 ] Dennis Lundberg commented on MPIR-164: -- An attempt at a patch for this was committed in [r794041|http://svn.apache.org/viewvc?view=rev&revision=794041] Can a native German speaker please review it? > Complete the German translation > --- > > Key: MPIR-164 > URL: http://jira.codehaus.org/browse/MPIR-164 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1.1 >Reporter: Dennis Lundberg > > The German translation is missing 30 property keys. -- 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: (MPIR-164) Complete the German translation
[ http://jira.codehaus.org/browse/MPIR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MPIR-164: - Assignee: Dennis Lundberg Fix Version/s: 2.1.2 > Complete the German translation > --- > > Key: MPIR-164 > URL: http://jira.codehaus.org/browse/MPIR-164 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1.1 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.1.2 > > > The German translation is missing 30 property keys. -- 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: (MEAR-106) Plugin includes ejb libraries twice, e.g. JBoss Seam
Plugin includes ejb libraries twice, e.g. JBoss Seam
-
Key: MEAR-106
URL: http://jira.codehaus.org/browse/MEAR-106
Project: Maven 2.x Ear Plugin
Issue Type: Bug
Reporter: Elias Ross
-- Problem --
Same EJB library appears multiple times, causing class loading issues,
especially for JBoss Seam.
Contents of ear:
META-INF/
META-INF/MANIFEST.MF
lib/
jboss-seam-2.1.2.jar
...
lib/jboss-seam-2.1.2.jar
-- To reproduce --
Add a dependency to the pom.xml, including JBoss Seam as an ejb type.
org.jboss.seam
jboss-seam
ejb
Also include it as part of the configuration:
org.apache.maven.plugins
maven-ear-plugin
2.3.2
5
3.0
lib
4
com.parkme:loader=${ear.name}.ear
lib
${ear.name}
...
org.jboss.seam
jboss-seam
Note that Seam requires this module to be deployed as an EJB module, so
exclusion does NOT work.
--
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: (MEAR-106) Plugin includes ejb libraries twice, e.g. JBoss Seam
[
http://jira.codehaus.org/browse/MEAR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MEAR-106:
---
Attachment: MEAR-106.zip
The attached demo project was created from your description but does not
reproduce the issue.
It's possible that some other module of the EAR erroneously depends on the seam
JAR with type=jar instead of type=ejb. You could run "mvn dependency:tree" on
the EAR project and look out for multiple occurrences of
"org.jboss.seam:jboss-seam".
> Plugin includes ejb libraries twice, e.g. JBoss Seam
> -
>
> Key: MEAR-106
> URL: http://jira.codehaus.org/browse/MEAR-106
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Reporter: Elias Ross
> Attachments: MEAR-106.zip
>
>
> -- Problem --
> Same EJB library appears multiple times, causing class loading issues,
> especially for JBoss Seam.
> Contents of ear:
> META-INF/
> META-INF/MANIFEST.MF
> lib/
> jboss-seam-2.1.2.jar
> ...
> lib/jboss-seam-2.1.2.jar
> -- To reproduce --
> Add a dependency to the pom.xml, including JBoss Seam as an ejb type.
>
> org.jboss.seam
> jboss-seam
> ejb
>
> Also include it as part of the configuration:
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.2
>
> 5
> 3.0
> lib
>
> 4
>
> com.parkme:loader=${ear.name}.ear
> lib
> ${ear.name}
>
>
> ...
>
> org.jboss.seam
> jboss-seam
>
>
>
> Note that Seam requires this module to be deployed as an EJB module, so
> exclusion does NOT work.
--
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: (MCOMPILER-91) source and output directories should be configurable
[ http://jira.codehaus.org/browse/MCOMPILER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reopened MCOMPILER-91: -- > source and output directories should be configurable > > > Key: MCOMPILER-91 > URL: http://jira.codehaus.org/browse/MCOMPILER-91 > Project: Maven 2.x Compiler Plugin > Issue Type: New Feature >Reporter: Paul Gier >Assignee: Paul Gier > Attachments: maven-compiler-plugin.patch, maven-compiler-plugin.patch > > > I have a project with two test source trees. These sources are kept separate > from each other because they need to be compiled and processed with different > parameters. > Currently there is no way in maven to have two separate source trees for the > tests other than using a profile. > It should be possible to configure the source and output directories in the > plugin so that each source tree can be compiled with different parameters. -- 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-91) source and output directories should be configurable
[ http://jira.codehaus.org/browse/MCOMPILER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCOMPILER-91: - Fix Version/s: (was: 2.1) > source and output directories should be configurable > > > Key: MCOMPILER-91 > URL: http://jira.codehaus.org/browse/MCOMPILER-91 > Project: Maven 2.x Compiler Plugin > Issue Type: New Feature >Reporter: Paul Gier >Assignee: Paul Gier > Attachments: maven-compiler-plugin.patch, maven-compiler-plugin.patch > > > I have a project with two test source trees. These sources are kept separate > from each other because they need to be compiled and processed with different > parameters. > Currently there is no way in maven to have two separate source trees for the > tests other than using a profile. > It should be possible to configure the source and output directories in the > plugin so that each source tree can be compiled with different parameters. -- 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: (MCOMPILER-91) source and output directories should be configurable
[ http://jira.codehaus.org/browse/MCOMPILER-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCOMPILER-91. Resolution: Won't Fix > source and output directories should be configurable > > > Key: MCOMPILER-91 > URL: http://jira.codehaus.org/browse/MCOMPILER-91 > Project: Maven 2.x Compiler Plugin > Issue Type: New Feature >Reporter: Paul Gier >Assignee: Paul Gier > Attachments: maven-compiler-plugin.patch, maven-compiler-plugin.patch > > > I have a project with two test source trees. These sources are kept separate > from each other because they need to be compiled and processed with different > parameters. > Currently there is no way in maven to have two separate source trees for the > tests other than using a profile. > It should be possible to configure the source and output directories in the > plugin so that each source tree can be compiled with different parameters. -- 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: (MEAR-106) Plugin includes ejb libraries twice, e.g. JBoss Seam
[
http://jira.codehaus.org/browse/MEAR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183570#action_183570
]
Elias Ross commented on MEAR-106:
-
Here's the dependency tree output:
$ mvn dependency:tree | grep seam
[INFO] +- org.jboss.seam:jboss-seam:ejb:2.1.2:compile
[INFO] +- org.jboss.seam:jboss-seam-ui:jar:2.1.2:compile
[INFO] | +- org.jboss.seam:jboss-seam-jul:jar:2.1.2:compile
[INFO] +- org.jboss.seam:jboss-seam-debug:jar:2.1.2:compile
> Plugin includes ejb libraries twice, e.g. JBoss Seam
> -
>
> Key: MEAR-106
> URL: http://jira.codehaus.org/browse/MEAR-106
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Reporter: Elias Ross
> Attachments: MEAR-106.zip
>
>
> -- Problem --
> Same EJB library appears multiple times, causing class loading issues,
> especially for JBoss Seam.
> Contents of ear:
> META-INF/
> META-INF/MANIFEST.MF
> lib/
> jboss-seam-2.1.2.jar
> ...
> lib/jboss-seam-2.1.2.jar
> -- To reproduce --
> Add a dependency to the pom.xml, including JBoss Seam as an ejb type.
>
> org.jboss.seam
> jboss-seam
> ejb
>
> Also include it as part of the configuration:
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.2
>
> 5
> 3.0
> lib
>
> 4
>
> com.parkme:loader=${ear.name}.ear
> lib
> ${ear.name}
>
>
> ...
>
> org.jboss.seam
> jboss-seam
>
>
>
> Note that Seam requires this module to be deployed as an EJB module, so
> exclusion does NOT work.
--
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: (MEAR-106) Plugin includes ejb libraries twice, e.g. JBoss Seam
[
http://jira.codehaus.org/browse/MEAR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183570#action_183570
]
Elias Ross edited comment on MEAR-106 at 7/14/09 4:12 PM:
--
Here's the dependency tree output:
$ mvn dependency:tree | grep seam
[INFO] +- org.jboss.seam:jboss-seam:ejb:2.1.2:compile
[INFO] +- org.jboss.seam:jboss-seam-ui:jar:2.1.2:compile
[INFO] | +- org.jboss.seam:jboss-seam-jul:jar:2.1.2:compile
[INFO] +- org.jboss.seam:jboss-seam-debug:jar:2.1.2:compile
It could be a transient dependency as you suggest, that doesn't appear in the
tree but somehow gets added anyway.
I'll poke around a bit more and see if this is the case. I wish I had a test
case for you.
was (Author: genman):
Here's the dependency tree output:
$ mvn dependency:tree | grep seam
[INFO] +- org.jboss.seam:jboss-seam:ejb:2.1.2:compile
[INFO] +- org.jboss.seam:jboss-seam-ui:jar:2.1.2:compile
[INFO] | +- org.jboss.seam:jboss-seam-jul:jar:2.1.2:compile
[INFO] +- org.jboss.seam:jboss-seam-debug:jar:2.1.2:compile
> Plugin includes ejb libraries twice, e.g. JBoss Seam
> -
>
> Key: MEAR-106
> URL: http://jira.codehaus.org/browse/MEAR-106
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Reporter: Elias Ross
> Attachments: MEAR-106.zip
>
>
> -- Problem --
> Same EJB library appears multiple times, causing class loading issues,
> especially for JBoss Seam.
> Contents of ear:
> META-INF/
> META-INF/MANIFEST.MF
> lib/
> jboss-seam-2.1.2.jar
> ...
> lib/jboss-seam-2.1.2.jar
> -- To reproduce --
> Add a dependency to the pom.xml, including JBoss Seam as an ejb type.
>
> org.jboss.seam
> jboss-seam
> ejb
>
> Also include it as part of the configuration:
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.2
>
> 5
> 3.0
> lib
>
> 4
>
> com.parkme:loader=${ear.name}.ear
> lib
> ${ear.name}
>
>
> ...
>
> org.jboss.seam
> jboss-seam
>
>
>
> Note that Seam requires this module to be deployed as an EJB module, so
> exclusion does NOT work.
--
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: (MEAR-106) Plugin includes ejb libraries twice, e.g. JBoss Seam
[
http://jira.codehaus.org/browse/MEAR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elias Ross closed MEAR-106.
---
Resolution: Not A Bug
Looks like the diagnostics of Benjamin Bentmann was right. Although
"dependency:tree" did not mention this .jar, it was indeed a duplicate
dependency and included correctly by the plugin. Seems maybe a bug in the
dependency plugin then? ;-)
> Plugin includes ejb libraries twice, e.g. JBoss Seam
> -
>
> Key: MEAR-106
> URL: http://jira.codehaus.org/browse/MEAR-106
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
>Reporter: Elias Ross
> Attachments: MEAR-106.zip
>
>
> -- Problem --
> Same EJB library appears multiple times, causing class loading issues,
> especially for JBoss Seam.
> Contents of ear:
> META-INF/
> META-INF/MANIFEST.MF
> lib/
> jboss-seam-2.1.2.jar
> ...
> lib/jboss-seam-2.1.2.jar
> -- To reproduce --
> Add a dependency to the pom.xml, including JBoss Seam as an ejb type.
>
> org.jboss.seam
> jboss-seam
> ejb
>
> Also include it as part of the configuration:
>
> org.apache.maven.plugins
> maven-ear-plugin
> 2.3.2
>
> 5
> 3.0
> lib
>
> 4
>
> com.parkme:loader=${ear.name}.ear
> lib
> ${ear.name}
>
>
> ...
>
> org.jboss.seam
> jboss-seam
>
>
>
> Note that Seam requires this module to be deployed as an EJB module, so
> exclusion does NOT work.
--
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: (MJAVADOC-238) No timeout set for URLConnection which can cause build to get stuck
[ http://jira.codehaus.org/browse/MJAVADOC-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-238: - Assignee: Vincent Siveton Fix Version/s: 2.6 > No timeout set for URLConnection which can cause build to get stuck > --- > > Key: MJAVADOC-238 > URL: http://jira.codehaus.org/browse/MJAVADOC-238 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5 >Reporter: Bugittaa Pahasti >Assignee: Vincent Siveton > Fix For: 2.6 > > > I encountered a release build getting stuck. Stack trace revealed that the > culprit was an infinite default timeout in URLConnection. > [INFO]at java.net.URL.openStream(URL.java:1007) > [INFO]at > org.apache.maven.plugin.javadoc.JavadocUtil.fetchURL(JavadocUtil.java:742) > [INFO]at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addLinkArguments(AbstractJavadocMojo.java:2982) > [INFO]at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.addStandardDocletOptions(AbstractJavadocMojo.java:3667) > [INFO]at > org.apache.maven.plugin.javadoc.AbstractJavadocMojo.executeReport(AbstractJavadocMojo.java:1548) > [INFO]at > org.apache.maven.plugin.javadoc.JavadocJar.execute(JavadocJar.java:182) > [INFO]at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > The simple fix is to call setConnectTimeout and setReadTimeout with some > sensible default value (jdk 1.5 methods, so might need to use reflection to > preseve jdk 1.4 compatibility). -- 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: (MJAVADOC-231) tagletpath does not seem to work
[
http://jira.codehaus.org/browse/MJAVADOC-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton closed MJAVADOC-231.
Assignee: Vincent Siveton
Resolution: Fixed
Fix Version/s: 2.6
fixed in [r794098|http://svn.apache.org/viewvc?rev=794098&view=rev], snapshot
deployed
> tagletpath does not seem to work
>
>
> Key: MJAVADOC-231
> URL: http://jira.codehaus.org/browse/MJAVADOC-231
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Benson Margulies
>Assignee: Vincent Siveton
> Fix For: 2.6
>
>
> I get ClassNotFound errors when I try to use tagletpath to indicate the
> location of taglet classes that are just sitting out, not in a jar.
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 -
> javadoc: error - Error - Exception java.lang.ClassNotFoundException thrown
> while trying to register Taglet org.odftoolkit.doctag.OdfLinkTaglet...
> javadoc: error - Error - Exception java.lang.ClassNotFoundException thrown
> while trying to register Taglet org.odftoolkit.doctag.AttributeNameTaglet...
>
> org.apache.maven.plugins
> maven-javadoc-plugin
>
> ODFDOM
> src/resources/overview.html
>
> http://java.sun.com/javase/6/docs/api/
>
> http://xerces.apache.org/xerces-j/apiDocs/
>
> true
> ODFDOM API v${project.version} -
> http://odftoolkit
>
>
>
> org.odftoolkit.doctag.OdfLinkTaglet
> ${basedir}/target/classes
>
>
>
> org.odftoolkit.doctag.AttributeNameTaglet
> ${basedir}/target/classes
>
>
>
>
--
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-164) Complete the German translation
[ http://jira.codehaus.org/browse/MPIR-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183587#action_183587 ] Benjamin Bentmann commented on MPIR-164: Reviewed in [r794113|http://svn.apache.org/viewvc?view=rev&revision=794113], thanks for spotting this Dennis! > Complete the German translation > --- > > Key: MPIR-164 > URL: http://jira.codehaus.org/browse/MPIR-164 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task >Affects Versions: 2.1.1 >Reporter: Dennis Lundberg >Assignee: Dennis Lundberg > Fix For: 2.1.2 > > > The German translation is missing 30 property keys. -- 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: (MJAVADOC-230) aggregate report requires to have aggregate=true configuration parameter
[ http://jira.codehaus.org/browse/MJAVADOC-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-230. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.6 Patch applied in [r794114|http://svn.apache.org/viewvc?rev=794114&view=rev] > aggregate report requires to have aggregate=true configuration parameter > > > Key: MJAVADOC-230 > URL: http://jira.codehaus.org/browse/MJAVADOC-230 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5 > Environment: Maven 2.0.9 > Windows XP SP2 >Reporter: Gabriel Forro >Assignee: Vincent Siveton >Priority: Minor > Fix For: 2.6 > > Attachments: MJAVADOC-230-maven-javadoc-plugin.patch > > > Project setup: I have a multi-module project (standard nested layout). The > reports are configured in the parent project. I use the "aggregate" report to > create an aggregated javadoc by the maven-javadoc-plugin: > > > > aggregate > > > > Problem: The aggregate report is ignored, when I launch the "mvn site" > command, unless the aggregated parameter is set to true in the > maven-javadoc-plugin configuration. So the following setup is required in > pom.xml: > > > > UTF-8 > true > > > aggregate > > > > Desired functionality: Launch the aggregate goal, if it is declared in the > report section. Do not require the aggregate parameter=true setting (it is a > duplication and also the aggregate parameter is deprecated). The following > setup should be enough in pom.xml: > > > > UTF-8 > > > aggregate > > > > Comment: > The aggregate goal works fine (it does not require to have the aggregate=true > parameter), if it is launched directly. That is by the "mvn > javadoc:aggregate" command. > It just does not work, when it is launched indirectly through the site plugin > as a report. -- 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-398) release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
[
http://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183605#action_183605
]
Antony Stubbs commented on MRELEASE-398:
I also have this problem. Is there a work-around?
> release:prepare: endlessly asking for the next development version on a
> multi-module project when not entering the expected value
> -
>
> Key: MRELEASE-398
> URL: http://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
>Reporter: Thorsten Heit
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules
> which were released recently. When trying to release my project,
> release:prepare doesn't stop asking me for a dependency's next development
> version as long as I'm entering a version string that doesn't equal the
> expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve
> them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project
> Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set
> to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of
> snapshot dependencies, not when asking for the new version of the project
> itself.
--
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-4228) [regression] Authorization failed: Not authorized by proxy.
[ http://jira.codehaus.org/browse/MNG-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183614#action_183614 ] Marco Noto commented on MNG-4228: - Guys, thanks for your work ... I don't consider it a big problem using version 2.1.0 for some time ;) > [regression] Authorization failed: Not authorized by proxy. > --- > > Key: MNG-4228 > URL: http://jira.codehaus.org/browse/MNG-4228 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Settings >Affects Versions: 2.2.0 > Environment: Windows XP, java version "1.6.0_04" >Reporter: Marco Noto >Assignee: John Casey >Priority: Blocker > Fix For: 2.2.1 > > Attachments: NTLMV21.RAR, TestNTLMAuth.java > > > I can not access any external repository using the version 2.2.0. If I go > back to 2.1.0 everything works properly. > For example: > mvn -U eclipse:eclipse > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'eclipse'. > [INFO] org.apache.maven.plugins: checking for updates from central > [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be > retrieved from repository: central due > to an error: Authorization failed: Not authorized by proxy. > [INFO] Repository 'central' will be blacklisted -- 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
