[jira] Commented: (MRELEASE-632) allowTimestampedSnapshots=true still fails with snapshot dependencies
[ https://jira.codehaus.org/browse/MRELEASE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273450#comment-273450 ] sebastien glon commented on MRELEASE-632: - I have the sme issue with version 2.2 allowTimestampedSnapshots=true still fails with snapshot dependencies - Key: MRELEASE-632 URL: https://jira.codehaus.org/browse/MRELEASE-632 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.1 Reporter: Eyal Goren Attachments: maven-release-plugin-2.1.jar, maven-release-plugin-2.1.pom, pom.xml Hi, I am using version 2.1 and I still recieve: [ERROR] BUILD FAILURE [INFO] [INFO] Can't release project due to non released dependencies : org.apache.maven.plugins:maven-nar-plugin:maven-plugin:2.1-SNAPSHOT:runtime in project 'Multi language build sample' (com.hp.pmo.test:HelloBuild:pom:2.0-SNA PSHOT) Even when I add -DallowTimestampedSnapshots=true to the command line (here: http://jira.codehaus.org/browse/MRELEASE-452 it was said that in 2.1 it should be solved?) I am attaching the pom.xml I used to define the plugin management. And the pom and jar of the plugin on my environment -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEJB-54) EJB Plugin can not auto-generate ejb-jar.xmljboss.xml
EJB Plugin can not auto-generate ejb-jar.xmljboss.xml -- Key: MEJB-54 URL: https://jira.codehaus.org/browse/MEJB-54 Project: Maven 2.x EJB Plugin Issue Type: Bug Affects Versions: 2.3 Environment: windows os,maven3 Reporter: Zeng.haojie Priority: Critical EJB Plugin just can generate jar like the JAR Plugin,But It doesn't auto-generate the ejb-jar.xmljboss.xml. So U have to create the xml files yourself,then put it at the resources folder. If EJB Plugin have more advanced features than JAR plugin? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-624) Broken checksum files, xalan:xalan, xalan:serializer 2.7.1
[ https://jira.codehaus.org/browse/MEV-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273473#comment-273473 ] Julien HENRY commented on MEV-624: -- Are you sure this is fixed? I'm still facing the same issue with serializer. I have the following error in Nexus: The artifact /xalan/serializer/2.7.1/serializer-2.7.1.jar and it's remote checksums does not match in repository central! Broken checksum files, xalan:xalan, xalan:serializer 2.7.1 -- Key: MEV-624 URL: https://jira.codehaus.org/browse/MEV-624 Project: Maven Evangelism Issue Type: Bug Components: Checksum Failure Reporter: Max Bowsher Assignee: Juven Xu Downloading: http://maven2.mxtelecom.com/repository/xalan/xalan/2.7.1/xalan-2.7.1.jar 3101K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '75f1d83ce27bab5f29fff034fc74aa9f7266f22a'; remote = 'SHA1(xalan-2.7.1.jar)=' - RETRYING Downloading: http://maven2.mxtelecom.com/repository/xalan/xalan/2.7.1/xalan-2.7.1.jar 3101K downloaded Downloading: http://maven2.mxtelecom.com/repository/xalan/serializer/2.7.1/serializer-2.7.1.jar 271K downloaded [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '4b4b18df434451249bb65a63f2fb69e215a6a020'; remote = 'SHA1(serializer-2.7.1.jar)=' - RETRYING Please fix these broken checksums -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MJAVADOC-297) NullPointerException in AbstractFixJavadocMojo.writeParamTag()
[
https://jira.codehaus.org/browse/MJAVADOC-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273506#comment-273506
]
Robert Scholte commented on MJAVADOC-297:
-
Extracted this ocde fragment from the tagged class.
{code}
private void writeParamTag( final StringBuffer sb, final JavaMethod javaMethod,
final JavaEntityTags javaEntityTags, String[]
params )
{
params = fixQdox173( params );
String paramName = params[0];
if ( !fixTag( PARAM_TAG ) )
{
// write original param tag if found
String originalJavadocTag = javaEntityTags.getJavadocParamTag(
paramName );
if ( originalJavadocTag != null )
{
sb.append( originalJavadocTag );
}
return;
}
boolean found = false;
JavaParameter javaParam = javaMethod.getParameterByName( paramName );
if ( javaParam == null )
{
// is generic?
TypeVariable[] typeParams = javaMethod.getTypeParameters();
for ( int i = 0; i typeParams.length; i++ )
{
if ( typeParams[i].getGenericValue().equals( paramName ) )
{
found = true;
}
}
}
else
{
found = true;
}
if ( !found )
{
if ( getLog().isWarnEnabled() )
{
StringBuffer warn = new StringBuffer();
warn.append( Fixed unknown param ' ).append( paramName
).append( ' defined in );
warn.append( getJavaMethodAsString( javaMethod ) );
getLog().warn( warn.toString() );
}
if ( sb.toString().endsWith( EOL ) )
{
sb.delete( sb.toString().lastIndexOf( EOL ),
sb.toString().length() );
}
}
else
{
String originalJavadocTag = javaEntityTags.getJavadocParamTag(
paramName );
if ( originalJavadocTag != null )
{
sb.append( originalJavadocTag );
String s = @ + PARAM_TAG + + paramName;
if ( StringUtils.removeDuplicateWhitespace( originalJavadocTag
).trim().endsWith( s ) )
{
sb.append( );
sb.append( getDefaultJavadocForType( javaParam.getType() )
);
}
}
}
}
{code}
The NPE is caused in one of the final lines: {{sb.append(
getDefaultJavadocForType( javaParam.getType() ) );}}
{{sb}} can't be {{null}} since it's already used, so it has to be {{javaParam}}.
Two options I can think of: @param is empty or it has an invalid name.
Shouldn't be too hard to find out.
NullPointerException in AbstractFixJavadocMojo.writeParamTag()
--
Key: MJAVADOC-297
URL: https://jira.codehaus.org/browse/MJAVADOC-297
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.7
Environment: graham-leggetts-macbook-pro-3:patricia-db-trunk minfrin$
mvn --version
Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_20
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x version: 10.5.8 arch: x86_64 Family: mac
Reporter: Graham Leggett
While attempting to run the javadoc:fix goal against source code, v2.7 of the
javadoc plugin crashed as follows:
{noformat}[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.writeParamTag(AbstractFixJavadocMojo.java:1958)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1842)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocTags(AbstractFixJavadocMojo.java:1747)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateJavadocComment(AbstractFixJavadocMojo.java:1658)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.updateEntityComment(AbstractFixJavadocMojo.java:1527)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.fixMethodComment(AbstractFixJavadocMojo.java:1391)
at
org.apache.maven.plugin.javadoc.AbstractFixJavadocMojo.processFix(AbstractFixJavadocMojo.java:993)
at
[jira] Commented: (MANTTASKS-174) Mirror declaration replaces url from distributionManagement
[
https://jira.codehaus.org/browse/MANTTASKS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273507#comment-273507
]
Eric Quilantang commented on MANTTASKS-174:
---
same behavior occurs when remoterepository is defined inside
artifact:deploy. The mirror inside settings.xml replaces the url
completely.
Mirror declaration replaces url from distributionManagement
---
Key: MANTTASKS-174
URL: https://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}
mirrors
mirror
idnexus/id
mirrorOfexternal:*/mirrorOf
urlhttps://xxx.com/nexus/content/groups/public/url
/mirror
/mirrors
{code}
a pom.xml file with a distributionManagement section
{code}
distributionManagement
snapshotRepository
idsonatype-nexus-snapshots/id
nameSonatype Nexus Snapshots/name
urlhttp://oss.sonatype.org/content/repositories/snapshots/url
/snapshotRepository
/distributionManagement
{code}
and a build.xml file with the following deploy task:
{code}
target name=deploy depends=-check
artifact:pom id=gin-pom file=pom.xml /
artifact:deploy file=${gin.jar.file}
pom refid=gin-pom /
attach file=${gin.javadoc.file} classifier=javadoc
/
/artifact:deploy
/target
{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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MANTTASKS-174) Mirror declaration replaces url from distributionManagement
[
https://jira.codehaus.org/browse/MANTTASKS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273508#comment-273508
]
Eric Quilantang commented on MANTTASKS-174:
---
When I remove the Mirror override clause in AbstractArtifactTask, the task
works as expected for me.
It's not clear to me why I would ever want my remote distribution to be
overridden since my mirror usually points to my Nexus public group.
code found in updateRepositoryWithSettings( RemoteRepository repository )
Mirror declaration replaces url from distributionManagement
---
Key: MANTTASKS-174
URL: https://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}
mirrors
mirror
idnexus/id
mirrorOfexternal:*/mirrorOf
urlhttps://xxx.com/nexus/content/groups/public/url
/mirror
/mirrors
{code}
a pom.xml file with a distributionManagement section
{code}
distributionManagement
snapshotRepository
idsonatype-nexus-snapshots/id
nameSonatype Nexus Snapshots/name
urlhttp://oss.sonatype.org/content/repositories/snapshots/url
/snapshotRepository
/distributionManagement
{code}
and a build.xml file with the following deploy task:
{code}
target name=deploy depends=-check
artifact:pom id=gin-pom file=pom.xml /
artifact:deploy file=${gin.jar.file}
pom refid=gin-pom /
attach file=${gin.javadoc.file} classifier=javadoc
/
/artifact:deploy
/target
{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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
