[jira] Commented: (MAVENUPLOAD-2733) Maven plugin for hadoop
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209008#action_209008 ] Juven Xu commented on MAVENUPLOAD-2733: --- please use this service instead: http://nexus.sonatype.org/oss-repository-hosting.html > Maven plugin for hadoop > > > Key: MAVENUPLOAD-2733 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2733 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Kay Kay >Assignee: Juven Xu > > Maven Plugin for Hadoop . > I am the original author of the project - available here at - > http://github.com/akkumar/maven-hadoop . > Contributor Name + URL found in: source files and README file -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-2734) upload JAXB 2.2 impl to maven central
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209007#action_209007 ] Juven Xu commented on MAVENUPLOAD-2734: --- oh, man, please use this service instead: http://nexus.sonatype.org/oss-repository-hosting.html > upload JAXB 2.2 impl to maven central > - > > Key: MAVENUPLOAD-2734 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hello, > can you please upload following artifacts to maven central? > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ > http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ > Thanks, > Pavel -- 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-2708) Upload of jasypt 1.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2708. - Resolution: Fixed see https://issues.sonatype.org/browse/OSSRH-211 > Upload of jasypt 1.6 > > > Key: MAVENUPLOAD-2708 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2708 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Daniel Fernández >Assignee: Juven Xu > > http://www.jasypt.org/jasypt-1.6-bundle.jar > http://www.jasypt.org > http://www.jasypt.org/team.html > Jasypt is a java library which allows the developer to add basic encryption > capabilities to > his/her projects with minimum effort, and without the need of having deep > knowledge on how > cryptography works. -- 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: (MANTTASKS-174) Mirror declaration replaces url from distributionManagement
Mirror declaration replaces url from distributionManagement
---
Key: MANTTASKS-174
URL: http://jira.codehaus.org/browse/MANTTASKS-174
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: deploy task
Affects Versions: 2.1.0
Environment: Ant 1.7.1, Maven ant tasks 2.1.0
Reporter: Robert Munteanu
Given a ~/.m2/settings.xml file containing a mirror element
{code}
nexus
external:*
https://xxx.com/nexus/content/groups/public
{code}
a pom.xml file with a distributionManagement section
{code}
sonatype-nexus-snapshots
Sonatype Nexus Snapshots
http://oss.sonatype.org/content/repositories/snapshots
{code}
and a build.xml file with the following deploy task:
{code}
{code}
When running ant deploy the deployment is done on xxx.com instead of
oss.sonatype.org . Removing the mirror from the settings file solves the
problem.
--
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-519) release plugin fails on version ranges
[ http://jira.codehaus.org/browse/MRELEASE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208980#action_208980 ] Stephen Cooper commented on MRELEASE-519: - Further information: In my local repository, I had versions 3.0.3 and 3.0.4-SNAPSHOT of the dependency for my project. When I erased all versions of that dependency (protocols), then 2.0 worked - it downloaded version 3.0.3 and used that. With this work-around, you could downgrade this issue from critical to major, or perhaps even minor. However, the fact remains that it behaves differently from 2.0-beta-9 to 2.0. Thanks! > release plugin fails on version ranges > -- > > Key: MRELEASE-519 > URL: http://jira.codehaus.org/browse/MRELEASE-519 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 > Environment: Mac OS X 10.6, maven 2.2.1 >Reporter: Stephen Cooper >Priority: Critical > > I have the following dependency in my pom.xml > >com.ften.protocols >protocols >[3.0.0,) >compile > > I downloaded the source for maven-release 2.0 and installed locally. > If I specify 2.0-beta-9, then mvn release:perform functions as it should. If > I specify maven-release-plugin version 2.0, I get the following error: > [INFO] Checking dependencies and plugins for snapshots ... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for com.ften.protocols:protocols > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > com.ften.protocols:protocols > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) > at > org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:562) -- 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-519) release plugin fails on version ranges
[ http://jira.codehaus.org/browse/MRELEASE-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208974#action_208974 ] Stephen Cooper commented on MRELEASE-519: - full stack trace: [INFO] Trace java.lang.NullPointerException: version was null for com.ften.protocols:protocols at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:562) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkArtifact(CheckDependencySnapshotsPhase.java:278) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkArtifact(CheckDependencySnapshotsPhase.java:269) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkProject(CheckDependencySnapshotsPhase.java:147) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.execute(CheckDependencySnapshotsPhase.java:109) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:203) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:140) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:103) at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:211) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > release plugin fails on version ranges > -- > > Key: MRELEASE-519 > URL: http://jira.codehaus.org/browse/MRELEASE-519 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0 > Environment: Mac OS X 10.6, maven 2.2.1 >Reporter: Stephen Cooper >Priority: Critical > > I have the following dependency in my pom.xml > >com.ften.protocols >protocols >[3.0.0,) >compile > > I downloaded the source for maven-release 2.0 and installed locally. > If I specify 2.0-beta-9, then mvn release:perform functions as it should. If > I specify maven-release-plugin version 2.0, I get the following error: > [INFO] Checking dependencies and plugins for snapshots ... > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] version was null for com.ften.protocols:protocols > [INFO] > > [INFO] Trace > java.lang.NullPointerException: version was null for > com.ften.protocols:protocols > at > org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) > at > org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:562) -- 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 infor
[jira] Created: (MRELEASE-519) release plugin fails on version ranges
release plugin fails on version ranges -- Key: MRELEASE-519 URL: http://jira.codehaus.org/browse/MRELEASE-519 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0 Environment: Mac OS X 10.6, maven 2.2.1 Reporter: Stephen Cooper Priority: Critical I have the following dependency in my pom.xml com.ften.protocols protocols [3.0.0,) compile I downloaded the source for maven-release 2.0 and installed locally. If I specify 2.0-beta-9, then mvn release:perform functions as it should. If I specify maven-release-plugin version 2.0, I get the following error: [INFO] Checking dependencies and plugins for snapshots ... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] version was null for com.ften.protocols:protocols [INFO] [INFO] Trace java.lang.NullPointerException: version was null for com.ften.protocols:protocols at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.isSnapshot(DefaultArtifact.java:562) -- 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-121) Maven-war-plugin not installing war. Installs ".jar" and renames it to ".war"
[ http://jira.codehaus.org/browse/MWAR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208952#action_208952 ] Wendy Smoak commented on MWAR-121: -- Rich, this issue is already closed as "Won't Fix" indicating that the developers don't consider it a valid bug. You might want to bring it up on the mailing list if you feel it should be re-opened. Otherwise, nothing is likely to happen with it. > Maven-war-plugin not installing war. Installs ".jar" and renames it to ".war" > - > > Key: MWAR-121 > URL: http://jira.codehaus.org/browse/MWAR-121 > Project: Maven 2.x WAR Plugin > Issue Type: Bug > Environment: Windows XP > Maven 2.0.7 > JDK 1.5.0_10 >Reporter: Dave Rathnow >Assignee: Stephane Nicoll > Attachments: war.zip > > > I'm trying to use the maven-war-plugin to install a war into my local > repository. "mvn clean install" runs fine and completes succesfully. If I > look under the target" directory in the project folder, there is, amoung > other things, a .jar and .war file. Both have been built properly. However, > if I look in my local repository, there is a .war file but when I open it, it > is actually the .jar file renamed to .war. > The attached zip file contains the pom for the project, the parent pom and > the output from the command "mvn clean install -X > output.log" -- 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-121) Maven-war-plugin not installing war. Installs ".jar" and renames it to ".war"
[ http://jira.codehaus.org/browse/MWAR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208951#action_208951 ] rich zaleski commented on MWAR-121: --- It would be great if this would be fixed. It seems the maven-source-plugin works properly, but the maven-war-plugin does not. I would like to generate primary and secondary artifacts using a single pom file. It seems overly complex to have to make modules out of everything. org.apache.maven.plugins maven-jar-plugin default-jar package jar maven-war-plugin cds_commons attach-war package war org.apache.maven.plugins maven-source-plugin attach-sources package jar < /plugins> > Maven-war-plugin not installing war. Installs ".jar" and renames it to ".war" > - > > Key: MWAR-121 > URL: http://jira.codehaus.org/browse/MWAR-121 > Project: Maven 2.x WAR Plugin > Issue Type: Bug > Environment: Windows XP > Maven 2.0.7 > JDK 1.5.0_10 >Reporter: Dave Rathnow >Assignee: Stephane Nicoll > Attachments: war.zip > > > I'm trying to use the maven-war-plugin to install a war into my local > repository. "mvn clean install" runs fine and completes succesfully. If I > look under the target" directory in the project folder, there is, amoung > other things, a .jar and .war file. Both have been built properly. However, > if I look in my local repository, there is a .war file but when I open it, it > is actually the .jar file renamed to .war. > The attached zip file contains the pom for the project, the parent pom and > the output from the command "mvn clean install -X > output.log" -- 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-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI
[ http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208948#action_208948 ] Dmitry Grigoriev commented on MSITE-159: Workaround mentioned by M. Rohrmoser does not work even in URL path component. I'd like to have just a couple of attributes for few particular menu items: > Absolute URI rendered as relative URI if absolute URI related to domain of > POM URI > -- > > Key: MSITE-159 > URL: http://jira.codehaus.org/browse/MSITE-159 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: relative links >Reporter: Ted Husted > > Under site-beta5 > if the POM references a URI like > http://struts.apache.org > absolute URLs used in the site.xml file are converted to relative references. > For example a reference to to "http://struts.apache.org/1.x"; becomes "1.x", > and a reference to > just "http://struts.apache.org"; becomes an empty string. > If the documentation is being used offline, there are many cases when we want > to refer people back to the website, to be sure the current information is > used. The best use case is a download page that determines the mirror via > CGI. > Another use case is referring to a sister site in the domain, that might > refer to another version. If used locally, the other site might not be in the > relative location. > Switching back to beta4 cures the behavior, and absolute URIs remain > absolute, as expected. -- 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-4556) Relocation can't be used on Root Pom.
Relocation can't be used on Root Pom. - Key: MNG-4556 URL: http://jira.codehaus.org/browse/MNG-4556 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.9 Environment: Windows, Eclipse, Dos. Reporter: Pierre Devreux Priority: Minor We slit our project in several modules. All modules have a parent. In this parent, we define among other things, groupID, and we don't define GroupID in module (they inherit of him). Now we wan't to relocate our groupID. But if we define relocation in parent, it is not taken into account in module. We have to define relocation in each module. -- 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-2734) upload JAXB 2.2 impl to maven central
upload JAXB 2.2 impl to maven central - Key: MAVENUPLOAD-2734 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2734 Project: Maven Upload Requests Issue Type: Wish Reporter: Pavel Bucek Hello, can you please upload following artifacts to maven central? http://download.java.net/maven/2/com/sun/xml/bind/jaxb-impl/2.2/ http://download.java.net/maven/2/com/sun/xml/bind/jaxb-osgi/2.2/ http://download.java.net/maven/2/com/sun/xml/bind/jaxb-xjc/2.2/ http://download.java.net/maven/2/com/sun/xml/bind/jaxb1-impl/2.2/ Thanks, Pavel -- 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-2694) Bad JAXB API 2.2 artifact in maven central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Bucek closed MAVENUPLOAD-2694. Resolution: Fixed already fixed > Bad JAXB API 2.2 artifact in maven central repo > --- > > Key: MAVENUPLOAD-2694 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2694 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hi, > I'm working on JAXB at Sun Microsystems and we released JAXB API 2.2 five > days ago. I wanted to file a "WISH" request to publish it (with reference > impl as well) in central repo BUT I found out that something is already there. > In manifest file from > http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.2/jaxb-api-2.2.jar is > clearly declared: > Specification-Version: 2.1 > which states that this api jar is for JAXB 2.1 and should be named > jaxb-api-2.1.jar. Additionally - it is two years old (so it really can't be > 2.2). I don't know who published this but it definitely isn't > jaxb-api-2.2.jar. Correct artifact can be found here: > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ > Can you remove this artifact or replace it with > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ ? > Regards, > Pavel -- 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-2694) Bad JAXB API 2.2 artifact in maven central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208938#action_208938 ] Pavel Bucek commented on MAVENUPLOAD-2694: -- ahm, yes, you are right. Kind of strange way processing problems (I would expect person who fixed that will comment this issue..), BUT thanks a lot, unknown person! Regards, Pavel > Bad JAXB API 2.2 artifact in maven central repo > --- > > Key: MAVENUPLOAD-2694 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2694 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hi, > I'm working on JAXB at Sun Microsystems and we released JAXB API 2.2 five > days ago. I wanted to file a "WISH" request to publish it (with reference > impl as well) in central repo BUT I found out that something is already there. > In manifest file from > http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.2/jaxb-api-2.2.jar is > clearly declared: > Specification-Version: 2.1 > which states that this api jar is for JAXB 2.1 and should be named > jaxb-api-2.1.jar. Additionally - it is two years old (so it really can't be > 2.2). I don't know who published this but it definitely isn't > jaxb-api-2.2.jar. Correct artifact can be found here: > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ > Can you remove this artifact or replace it with > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ ? > Regards, > Pavel -- 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-2694) Bad JAXB API 2.2 artifact in maven central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208930#action_208930 ] Juven Xu commented on MAVENUPLOAD-2694: --- although I don't where does the jaxb-api-2.2.jar in central come from? but seems it's fixed already: http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/jaxb-api-2.2.jar.md5 http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.2/jaxb-api-2.2.jar.md5 these 2 values are identical > Bad JAXB API 2.2 artifact in maven central repo > --- > > Key: MAVENUPLOAD-2694 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2694 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hi, > I'm working on JAXB at Sun Microsystems and we released JAXB API 2.2 five > days ago. I wanted to file a "WISH" request to publish it (with reference > impl as well) in central repo BUT I found out that something is already there. > In manifest file from > http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.2/jaxb-api-2.2.jar is > clearly declared: > Specification-Version: 2.1 > which states that this api jar is for JAXB 2.1 and should be named > jaxb-api-2.1.jar. Additionally - it is two years old (so it really can't be > 2.2). I don't know who published this but it definitely isn't > jaxb-api-2.2.jar. Correct artifact can be found here: > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ > Can you remove this artifact or replace it with > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ ? > Regards, > Pavel -- 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: (SCM-487) support --parents option for svn copy (tag commands) (svn 1.5 required)
[ http://jira.codehaus.org/browse/SCM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208929#action_208929 ] Daniel Wurst commented on SCM-487: -- I think it is very important to have this possiblity to independenty tag sub-projects, but for compatibility reasons I'd suggest to make it a provider configuration (in ). > support --parents option for svn copy (tag commands) (svn 1.5 required) > --- > > Key: SCM-487 > URL: http://jira.codehaus.org/browse/SCM-487 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-svn >Affects Versions: 1.2 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 1.x > > > With the release if guys doesn't have created full layout with the tags path, > the release plugin failed. > We can created full directory structure with --parents cli option -- 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: (MAVENUPLOAD-2694) Bad JAXB API 2.2 artifact in maven central repo
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MAVENUPLOAD-2694 started by Juven Xu. > Bad JAXB API 2.2 artifact in maven central repo > --- > > Key: MAVENUPLOAD-2694 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2694 > Project: Maven Upload Requests > Issue Type: Bug >Reporter: Pavel Bucek >Assignee: Juven Xu > > Hi, > I'm working on JAXB at Sun Microsystems and we released JAXB API 2.2 five > days ago. I wanted to file a "WISH" request to publish it (with reference > impl as well) in central repo BUT I found out that something is already there. > In manifest file from > http://repo1.maven.org/maven2/javax/xml/bind/jaxb-api/2.2/jaxb-api-2.2.jar is > clearly declared: > Specification-Version: 2.1 > which states that this api jar is for JAXB 2.1 and should be named > jaxb-api-2.1.jar. Additionally - it is two years old (so it really can't be > 2.2). I don't know who published this but it definitely isn't > jaxb-api-2.2.jar. Correct artifact can be found here: > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ > Can you remove this artifact or replace it with > http://download.java.net/maven/2/javax/xml/bind/jaxb-api/2.2/ ? > Regards, > Pavel -- 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-361) eclipse plugin and WTP generating warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208927#action_208927 ] Anders Åberg commented on MECLIPSE-361: --- Does anyone know the status of this issue? Any way to contribute to solving it? Although the workaround suggested by Paul works for the "Problems" view, a warning icon is still showing on the project. Not a big problem but now real warnings are always hidden. > eclipse plugin and WTP generating warnings in Europa > - > > Key: MECLIPSE-361 > URL: http://jira.codehaus.org/browse/MECLIPSE-361 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5 > Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the > last maven-eclipse-plugin 2.5-SNAPSHOT >Reporter: Yann Albou >Priority: Minor > Attachments: wtpTest.zip > > > The issue is regarding warnings in Europa and WTP: > "Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be > exported or published. Runtime ClassNotFoundExceptions may result." > 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.5-SNAPSHOT => I get the same behaviour in EUROPA (WARNINGS) > 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.4 => I get the same behaviour in EUROPA (WARNINGS) > 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse > 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or > 2.5-SNAPSHOT => Everything is perfect, no more warnings > I create a simple test in order to reproduce the issue. > This test is a multi module application composed of 1 Ejb module and 1 Ear > module. > So at the top level Just run "mvn install eclipse:eclipse" > And then in an europa workspace import the projetcs and you should see the > warnings on the EJB module. > It will behave the same way if it exists other modules. > I notice that, in the case you update parameters on the eclipse plugin you > will need to remove projects from workspace and import them again. > otherwise some old parameter will stay in the eclipse cache... > let me know if you need other tests > Yann. -- 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: (MANTRUN-129) Please add as 'skip' parameter
Please add as 'skip' parameter -- Key: MANTRUN-129 URL: http://jira.codehaus.org/browse/MANTRUN-129 Project: Maven 2.x Antrun Plugin Issue Type: New Feature Affects Versions: 1.3 Reporter: Benson Margulies In some structures involving parent poms, it is very helpful when plugin have a 'skip' parameter, so that an execution which is inherited through an entire forest of projects can be selectively turned on and off. Other plugins have this. -- 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-2683) Please upload the new org.igniterealtime Tinder 1.2.0 bundle
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guus der Kinderen closed MAVENUPLOAD-2683. -- Resolution: Fixed This issue is now redundant. Syncing has taken place through the Sonatype OSS Repo Hosting. See https://issues.sonatype.org/browse/OSSRH-200 for more details. > Please upload the new org.igniterealtime Tinder 1.2.0 bundle > > > Key: MAVENUPLOAD-2683 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2683 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Guus der Kinderen >Assignee: Juven Xu > Attachments: tinder-1.2.1-bundle.jar > > > We've just released version 1.2.0 of Tinder. Please upload the corresponding > bundle to the repository. -- 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: (MRELEASE-518) Unresolvable dependency
[ http://jira.codehaus.org/browse/MRELEASE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MRELEASE-518. -- Resolution: Not A Bug Assignee: Benjamin Bentmann The POM you mentioned (as well the other SCM JARs) are in the central repository: http://repo2.maven.org/maven2/org/apache/maven/scm/maven-scm-providers/1.2/. You apparently have an issue with your network setup, try the [maven user list|http://maven.apache.org/mail-lists.html] for help. > Unresolvable dependency > --- > > Key: MRELEASE-518 > URL: http://jira.codehaus.org/browse/MRELEASE-518 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: perform >Affects Versions: 2.0-beta-9 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) > Java version: 1.6.0_14 > Java home: C:\Programme\Java\jdk1.6.0_14\jre > Default locale: de_DE, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Ruediger Gubler >Assignee: Benjamin Bentmann > > We want to switch from beta-8 to beta-9 of the release plug-in. > We have the following entry in our pom.xml: > > org.apache.maven.plugins > maven-release-plugin > 2.0-beta-9 > > deploy > > > Now we get the following error: > Unable to get resource > 'org.apache.maven.scm:maven-scm-providers:pom:1.2' from repository -- 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-518) Unresolvable dependency
Unresolvable dependency --- Key: MRELEASE-518 URL: http://jira.codehaus.org/browse/MRELEASE-518 Project: Maven 2.x Release Plugin Issue Type: Bug Components: perform Affects Versions: 2.0-beta-9 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_14 Java home: C:\Programme\Java\jdk1.6.0_14\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" Reporter: Ruediger Gubler We want to switch from beta-8 to beta-9 of the release plug-in. We have the following entry in our pom.xml: org.apache.maven.plugins maven-release-plugin 2.0-beta-9 deploy Now we get the following error: Unable to get resource 'org.apache.maven.scm:maven-scm-providers:pom:1.2' from repository -- 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: (SUREFIRE-599) Logs console output multiple times (no. of times log output = the no. of test being run) for JUnit/XMLUnit tests
Logs console output multiple times (no. of times log output = the no. of test being run) for JUnit/XMLUnit tests Key: SUREFIRE-599 URL: http://jira.codehaus.org/browse/SUREFIRE-599 Project: Maven Surefire Issue Type: Bug Components: JUnit 3.x support Affects Versions: 2.5 Environment: Ubuntu 9.04 Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+) Java version: 1.6.0_16 OS name: "linux" version: "2.6.31-17-generic" arch: "i386" Family: "unix" JUnit 3.8.2 Log4j 1.2.14 Reporter: Mahender Didwania I have a test class (named ATest) written by extending the JUnit TestCase class. This class has a few test methods which all call the same method on a class (named A) with different parameters, exactly once each. Now the class A which is being tested logs to console using Apache log4j's ConsoleAppender, at INFO level. In the first test method, a message is logged once (which is how it should be). In the second test method, every log message is repeated once (so gets logged twice instead of once). In the third test method, every log message is logged thrice. ... and so on. Please note that the method in class A is invoked only once by the written source-code in each of the test methods and logs only once. -- 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
